Open jeff-zucker opened 2 years ago
Ok, I finally made time to read it too. I personally find it a bit long and at parts philosophical (which is no wonder after all the discussions we have). Since it is an intro for devs mostly, maybe we should keep it simple and to the point.
Example of what I call 'philosophical':
An example of too detailed:
"In cases where the owner of two profiles wants to link the identities together, the [owl:sameAs
]() predicate can be used. These links can occur in either or both of the profiles i.e. the relationship between the identities can be either uni-directional or bi-directional. For example a person might want to link from their personal profile to their work profile to have access to a CV in the work profile but might not want a link from the work profile to their personal profile in order to keep their home identity and work identity separate. See [use cases]()."
I would also expect information such as. This specification is about the Solid WebID Profile Document which is also referenced with Solid Profile.
- "...can obtain one or more WebIDs and thereafter they are considered the owner of the WebID..." -> what is an 'owner'? It is rather abstract and everyone will interpret how they want.
Owner is clearly defined in the protocol :
An owner is a person or a social entity that is considered to have the rights and responsibilities of a data storage. An owner is identified by a URI, and implicitly has control over all data in a storage. An owner is first set at storage provisioning time and can be changed.
-- https://solidproject.org/TR/protocol#owner
If we do not have a concept of an owner, how do you expect to describe what a private resource is?
I would also expect information such as. This specification is about the Solid WebID Profile Document which is also referenced with Solid Profile.
No, they are two different things. The first is a document, the second is a graph formed from statements with the WebID as subject in that document and in the documents it points to.
I would also expect information such as. This specification is about the Solid WebID Profile Document which is also referenced with Solid Profile.
No, they are two different things. The first is a document, the second is a graph formed from statements with the WebID as subject in that document and in the documents it points to.
So true! But maybe this is the info we should add here and make clear.
[@jeff-zucker:] [A Solid WebID Profile Document and a Solid Profile] are two different things. The first is a document, the second is a graph formed from statements with the WebID as subject in that document and in the documents it points to.
I'm not sure I would aggree with that. While used in different contexts, the Document and the Profile are i.m.o. the same thing, i.e. the data one gets when dereferencing the Identifier.
Are you pointing out that the Profile is only the part (subgraph) of the Document that has the Identifier as subject?
To replace current introduction and also current "other predicates" section in line with #52 and @VirginiaBalseiro 's suggestion to split off best practices and use cases