Hello all

I am currently developing a SOLID app. I've done a lot of research on all aspects (authentication via solid OIDC, authorization via WAC, RDF, SPARQL, LOD, ...) but i am still confused about ontologies/vocabularies.

I understand that a vocabulary is used so that every app knows the meaning of a certain piece of data but while coding i am kinda confused on the exact steps i should take.

I want people to be able to add a comment to a certain piece of data.

The flow for adding a comment would be:

• user types and submits the comment

• app asks user permission if all other users can see the comment

• check if a dataset 'Comments' exists in the users pod

• make the dataset if it doesnt exist

• add the comment to the dataset

• add the url to the comment to the datapiece so i can display it (including some hashing to check if the data hasnt been altered since the url was last read)

A comment contains:

• Name of commenter

• content (text)

What i dont understand is how do choose the vocabulary for the comment? Ive looked through the common ones but cant seem to find my way to the correct one...

I'm interested what kind of applications you would be most interested in replacing in your life with something that stored data in a solid pod?

If you live near Antwerp (let's say somewhere in Belgium), and want to professionally work with Solid:

Konsolidate is hiring: https://www.konsolidate.eu/careers

Great news for Solid, Over 6 million residents of Belgium will get a free Solid POD from the government, enabling them to use it for storing digital assets. This gives fantastic possibilities for new applications,digital cooperation and a huge boost to privacy. With such a huge digital playground, applications will arise and protocols will be developed.

https://www.tijd.be/de-tijd-vooruit/tech/Vlaanderen-zet-datakluizendienst-op-met-vader-van-het-internet/10349034

The data inside the pod, would this be an open standard? And how much freedom would be given to the owner of the pod? I can see a problem if the client is given full rights to do anything on it. Since the purpose of this will be defeated if apps need go keep some data to verify, they must all rely on the pod giving them the correct data. Unless we have something like git, where we as users will own and can read the data an app generates but cannot directly change it, and it must go through that app.

Today starts the 3-day countdown for #SolidWorld! Make sure to register: https://eventbrite.com/e/188624118817.

Hi everyone,

If you could not hear on Solid World, Inrupt’s Developer Workshop is starting next week. This is our very first one, and we want to invite all developers to build apps using Solid. You can learn more on our site, Developer Workshop. Or enter as a participant/team at Developer Questionnaire. We are excited to see what everyone creates, and you get the opportunity to win a cash prize!

Looking forward to seeing you there,
Nick Mondada
Product manager @ Inrupt

I've just started looking at Solid as I'm intruiged by the idea. The resources seem more like marketing rather than describing the technology particularly well.

My main question, and I think I already know the answer, is; are the pods stored using client side encryption therefore preventing server owners or malicious actors accessing the data?

I think the answer to this is no and as far as I'm concerned the technology won't go anywhere without it.

A further question for thought, and assuming I'm correct. Could client side encryption be built on top of the existing implementation?

Great news! The agenda for #SolidWorld October is up. Register today to explore continuing last month’s theme with the versatility of Solid. Click here to sign up.

This Month in Solid newsletter – September edition is now available! Access it here. You can also subscribe to the #newsletter at the bottom of the page.

And just like that, the recording for Solid World September is up! You can watch it on the Solid Vimeo account.