Sarven Capadisli

I have a couple brief comments: Generally I like this. And, we should refer to existing stuff out there. Where applicable or available, terminology should be based on technical terms...

I came to the same conclusion based on my observation of its use in the community in that the "origin" part was sometimes overlooked or misapplied in the same way...

There is some overlap with #26 in that the user may have multiple licenses that they like / will use where possible, and perhaps one of them can be their...

>Should it be per-app or generic? In generic user preferences or app-specific preferences (or both)? Both are nice to have I think - the user may not yet have an...

First, I agree that there majority of the terms in this vocab can be reused from other vocabs. Second, this vocab was mostly experimental.. I don't think it is used...

Also a reminder that in addition to having this repository for the Solid vocabs, one of the other reasons was to explore what's used and needed for the Solid-universe.

See also https://github.com/solid/vocab/pull/18/files which drops the obvious candidates: description, name, icon, homepage.

Are there (experimental) Solid applications making use of those ontologies?

`foaf:name` is a sub property of `rdfs:label`. Apps should have some minimal built-in smarts to handle that, or pragmatically speaking, just treat them as interchangeably where meaningful. There are many...

wasGeneratedBy is fine but note that its value is an activity, not an entity (application). You can indeed attach the application on the activity. Well, when you encounter any HTTP...