Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create introduction.md #76

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

jeff-zucker
Copy link
Member

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

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

A central goal of Solid and of the Web is to "empower an equitable, informed and interconnected society" [ETHICAL-WEB]. In order to work together online towards these goals people and communities need a voice - a way to describe who they are; a discovery mechanism - a way to find the resources they need; and an identifying mechanism - a way to be found and trusted for purposes of collaboration. A person or organization's `Solid Profile` is a set of statements which fulfill or point to resources which fulfill one or more of those functions - identification and description of the profile owner, discovery of their resources and the resources of their social network. A Solid Profile is thus an entryway to a person or organization's presence in the "vast inter-twingled tapestry" [NELSON] that is the collaborative and empowering web.

### Identification
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These sections (Identifiication, Description, Discovery, etc), I feel, are getting into too much detail and stepping into comformance/requirements. I would keep them as a mention in the introduction but wouldn't have subsections of the introduction, as these are discussed in the text itself.

@timea-solid
Copy link
Member

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':

  • "...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.

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."

@timea-solid
Copy link
Member

I would also expect information such as. This specification is about the Solid WebID Profile Document which is also referenced with Solid Profile.

@jeff-zucker
Copy link
Member Author

  • "...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?

@jeff-zucker
Copy link
Member Author

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.

@timea-solid
Copy link
Member

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.

@woutermont
Copy link
Contributor

[@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?


### Identification

A profile is the center of a person or organization's social web, and it is also the center of their web of meaning. In the semantic web, every thing can have a URI that provides a definition of that thing. In Solid, the `WebID` is a URI that provides the definition of an agent. A social agent - a person or organization - can [obtain one or more WebIDs]() and thereafter they are considered the owner of the WebID and the WebID is understood to refer to them.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A social agent - a person or organization - can obtain one or more WebIDs and thereafter they are considered the owner of the WebID and the WebID is understood to refer to them.

While I agree that 'owner' has an attempted definition, it is a complex one, and one that is in th Solid context defined over storage, not over identity. For example: if my job gives me a WebID to use in professional activity, I have an identifier that refers to me, but I do not own it.


A profile is the center of a person or organization's social web, and it is also the center of their web of meaning. In the semantic web, every thing can have a URI that provides a definition of that thing. In Solid, the `WebID` is a URI that provides the definition of an agent. A social agent - a person or organization - can [obtain one or more WebIDs]() and thereafter they are considered the owner of the WebID and the WebID is understood to refer to them.

A WebID is a URI that, when dereferenced, leads to a a set of statements that have the WebID as subject. Taken together, these statements with the WebID as subject form a Solid Profile. The WebID denotes the agent in the sense that statements in the profile and elsewhere asserting that WebID has a given property assert that the person or organization the WebID denotes has that property. See [WebID]().
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Taken together, these statements with the WebID as subject form a Solid Profile.

So of the following ...

@prefix vcard:  <http://www.w3.org/2006/vcard/ns#> .

:id vcard:n _:name .
_:name vcard:given-name "Wouter" .
_:name vcard:family-name "Termont" .

... only :id vcard:n _:blank_node . is the Solid Profile?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants