diff --git a/index.html b/index.html index a1a508e..580b6a4 100644 --- a/index.html +++ b/index.html @@ -1,324 +1,410 @@ - + Solid WebID Profile - - - + + + + -
-
- -
-
-
-
-

Solid WebID Profile

-

Version 1.0.0, Editor’s Draft, 2024-03-04

+
+
+

Solid WebID Profile

-
- More details about this document +

Version 1.0.0, Editor’s Draft, 2024-03-04

-
-
This version
-
- https://solid.github.io/webid-profile/ -
-
+
+ More details about this document -
-
Latest version
-
- https://solid.github.io/webid-profile/ -
-
+
+
This version
+
+ https://solid.github.io/webid-profile/ +
+
-
-
Latest published version
-
- https://solid.github.io/webid-profile/ -
-
+
+
Latest published version
+
+ https://solid.github.io/webid-profile/ +
+
-
-
Editors
-
- Virginia - Balseiro -
+
+
Editors
+
+ Virginia + Balseiro +
-
- Timea - Turdean -
+
+ Jeff + Zucker +
-
- Jeff - Zucker -
-
- -
-
Authors
+
+ Sarven + Capadisli +
+
-
- Tim - Berners-Lee -
+
+
Former editors
+
+ Timea + Turdean +
+
-
- Sarven - Capadisli -
+
+
Authors
-
Virginia Balseiro
+
+ Tim + Berners-Lee +
-
Timea Turdean
+
Sarven Capadisli
-
Jeff Zucker
-
+
Virginia Balseiro
-
-
Created
-
- -
-
+
Timea Turdean
-
-
Published
-
- -
-
+
Jeff Zucker
+
+ +
+
Created
+
+ +
+
+ +
+
Published
+
+ +
+
Modified
@@ -333,267 +419,245 @@

Version 1.0.0, Editor’s Draft, 2024-

-
-
Repository
-
- GitHub -
-
- Issues -
-
+
+
Feedback
+
GitHub solid/webid-profile (pull requests, new issue, open issues)
+
-
-
Language
-
- English -
-
+
+
Language
+
+ English +
+
-
-
Document Status
-
- Editor’s Draft -
-
+
+
Version
+
1.0.0
+
-
-
Policy
-
-
-
Rule
-
- Offer -
-
Unique Identifier
-
- https://solidproject.org/TR/webid-profile#document-policy-offer -
-
Target
-
- https://solidproject.org/TR/webid-profile -
-
Permission
-
-
-
Assigner
-
- W3C Solid Community Group -
-
Action
-
- -
-
-
-
-
-
-
+
+
Policy
+
+
+
Rule
+
+ Offer +
+
Unique Identifier
+
+ https://solid.github.io/webid-profile/#document-policy-offer +
+
Target
+
+ https://solid.github.io/webid-profile/ +
+
Permission
+
+
+
Assigner
+
+ W3C Solid Community Group +
+
Action
+
+ +
+
+
+
+
+
+

Copyright © 2022-2024 the Contributors to Solid WebID Profile specification, published by the Solid Community Group under the W3C Community Contributor License Agreement (CLA). A human-readable summary is available. All code snippets are in the public domain, CC0.

+
+
@@ -653,7 +717,7 @@

Status of This Document

-
-

+
+

1. Introduction -

+

This section is non-normative.

@@ -804,7 +872,7 @@

Table of Contents

There are different circumstances under which profiles are used or shared, including:

-
    +
    • Communication and use of multiple profiles for different purposes.
    • Connectivity of multiple profiles and cross-context recognition.
    • Cascade of profile information.
      • @@ -837,14 +905,8 @@

      Table of Contents

-
-

Terminology

+
+

1.1 Terminology

This section is non-normative.

@@ -877,34 +939,22 @@

Terminology

-
- Solid Profile +
+ Solid Profile
A Solid profile is a description of a social agent's identity within the Solid ecosystem, which can be used to describe their persona, preferences, abilities, affiliations, social activities and relationships, characteristics, and digital presence, as well as to aid in the discovery of storage and location of specific data.
-
- Extended Solid Profile +
+ Extended Solid Profile
An extended Solid profile is an additional profile document that provides supplemental description to a Solid profile to help distribute and manage information about a WebID for use in different circumstances. Extended profile documents can be used for various purposes, such as organizing information or limiting access to certain data.
-
- Preferences Document +
+ Preferences Document
A preferences document is a specific resource intended to store data which helps authorized applications accommodate the user's preferences, such as settings, personalization details, and pointers to the user's private data. @@ -913,13 +963,8 @@

Terminology

-
-

Namespaces

+
+

1.2 Namespaces

@@ -994,51 +1039,51 @@

Namespaces

-
-

Conformance

+
+

1.3 Conformance

This section describes the conformance model of the Solid WebID Profile..

-
+

Normative and Informative Content

-

All assertions, diagrams, examples, and notes are non-normative, as are all sections explicitly marked non-normative. Everything else is normative.

-

The key words “MUST”, “MUST NOT”, “SHOULD”, and “MAY” are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

-

The key words “strongly encouraged”, “strongly discouraged”, “encouraged", “discouraged", “can", “cannot”, “could”, “could not”, “might”, and “might not” are used for non-normative content.

+

All assertions, diagrams, examples, and notes are non-normative, as are all sections explicitly marked non-normative. Everything else is normative.

+

The key words “MUST”, “MUST NOT”, “SHOULD”, and “MAY” are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

+

The key words “strongly encouraged”, “strongly discouraged”, “encouraged", “discouraged", “can", “cannot”, “could”, “could not”, “might”, and “might not” are used for non-normative content.

-
+

Specification Category

The Solid WebID Profile identifies the following Specification Category to distinguish the types of conformance: notation/syntax, processor behavior, protocol.

-
+

Classes of Products

The Solid WebID Profile identifies the following Classes of Products for conforming implementations. These products are referenced throughout this specification.

-
Reader Application
+
Reader Application
A Solid app that issues HTTP requests to consume content pertaining to WebID Profiles.
-
Writer Application
+
Writer Application
A Solid app that issues HTTP requests to produce and consume content pertaining to WebID Profiles.
-
Server
+
Server
A Solid Server that responds to HTTP requests processing payloads pertaining to Solid WebID Profiles.
-
+

Interoperability

-
Reader Application–Server interoperability
+
Reader Application–Server interoperability
Interoperability of implementations for Reader Applications and Servers is tested by evaluating an implementation’s ability to request and respond to HTTP messages that conform to this specification.
-
Writer Application–Server interoperability
+
Writer Application–Server interoperability
Interoperability of implementations for Writer Applications and Servers is tested by evaluating an implementation’s ability to request and respond to HTTP messages that conform to this specification.
@@ -1047,13 +1092,8 @@

Interoperability

-
-

Discovery

+
+

2. Discovery

A Solid profile is comprised of statements expressing a social agent's identity, which can be found in one or more resources. The discovery @@ -1070,12 +1110,11 @@

Discovery

A profile can be assembled by collecting all statements that have the WebID as the subject or the object, regardless of their originating documents, as illustrated below.

- +
Solid Profile Discovery Overview
+ -
Solid Profile Discovery Overview
-
+
Note:

Depending on the established access control rules, certain resources may be inaccessible to specific applications or agents.

@@ -1084,23 +1123,20 @@
Note:
-
+

Reading and Writing Profiles

-
-

Reading Profile

+
+

3.1 Reading Profile

-

- To retrieve a representation of a Solid WebID Profile, Reader Application MUST make +

+ To retrieve a representation of a Solid WebID Profile, Reader Application MUST make an HTTP GET request targeting a Solid WebID Profile resource and include an Accept header requesting a representation in text/turtle or application/ld+json.

-
-

Solid WebID Profile

+
+

Solid WebID Profile

The Solid WebID Profile has the following properties:

    @@ -1112,8 +1148,7 @@

    Solid WebID extending the profile.

-
+
Note:

The Solid WebID Profiles may include other information pertaining to scenarios in @@ -1122,7 +1157,7 @@

Note:
-
+

Preferences Document

The Preferences Document has the following properties:

@@ -1132,65 +1167,59 @@

Preferences Document

-
-

Extended Profile Documents

+
+

Extended Profile Documents

-

The Extended Profile Documents are also self-describing +

The Extended Profile Documents are also self-describing Solid WebID Profiles and share the same data model. Reader Applications retrieve representations of Extended Profile Documents the same way as they retrieve Solid WebID Profiles.

-

- Reader +

+ Reader Application MAY retrieve a representation of an Extended Profile Document.

-
-

Updating Profile

+
+

3.2 Updating Profile

-

Writer Applications perform write operations against Solid Protocol servers.

-
+

Writer Applications perform write operations against Solid Protocol servers.

+
Note:
-

To promote self-describing resources and efficient discovery and reuse of profile - information, implementations and authors are encouraged to prioritize using the Solid - WebID Profile before resorting to an Extended WebID Profile. +

To promote self-describing resources and efficient discovery and reuse of profile + information, implementations and authors are encouraged to prioritize using the Solid + WebID Profile before resorting to an Extended WebID Profile.

-

- Writer +

+ Writer Application MUST use an HTTP PUT or PATCH request targeting the Solid WebID Profile to be updated.

-

+

Solid WebID Profile might include protected properties, such as solid:oidcIssuer.

-

- Servers MUST NOT allow +

+ Servers MUST NOT allow HTTP PUT or PATCH on a Solid WebID Profile to update its protected triples; if the server receives such a request, it MUST respond with a 409 status code.

-

- Servers MUST respond with a 422 +

+ Servers MUST respond with a 422 status code [RFC4918] when unable to process the contained instructions, including unrecognised JSON-LD context in representation data, semantically erroneous Solid WebID Profile or Preferences Document data.

-
-

Extending a Profile

+
+

3.3 Extending a Profile

-

- Writer +

+ Writer Application MUST use an HTTP PUT or PATCH request targeting the Extended Profile to be created.

-

- Writer +

+ Writer Application MUST use an HTTP PUT or PATCH request targeting the Extended Profile to be updated

- -
+
Note:
-

While the rdfs:seeAlso property is recommended to establish links to extended profiles or additional information, the use of the owl:sameAs property is encouraged when connecting two WebIDs that denote the same entity, as shown in the example: <https://dbpedia.org/resource/Tim_Berners-Lee> owl:sameAs <https://www.w3.org/People/Berners-Lee/card#i>.

+

While the rdfs:seeAlso property is recommended to establish links to extended profiles or additional information, the use of the owl:sameAs property is encouraged when connecting two WebIDs that denote the same entity, as shown in the example: <https://dbpedia.org/resource/Tim_Berners-Lee> owl:sameAs <https://www.w3.org/People/Berners-Lee/card#i>.

-
-

Private Preferences

+
+

4. Private Preferences

The Preferences Document is a resource intended to hold @@ -1267,13 +1287,8 @@

Private Preferences

-
-

Identity Provider

+
+

5. Identity Provider

The solid:oidcIssuer predicate denotes a Solid OIDC Identity Provider @@ -1283,13 +1298,13 @@

Identity Provider

-
-

Inbox

+
+

6. Inbox

A Solid WebID Profile can advertise an inbox with the ldp:inbox property [LDN] to allow applications to send and discover notifications about activities, interactions, and new information - for the attention of the owner of the WebID. It is discouraged for Solid WebID Profiles to advertise more than one inbox. + for the attention of the owner of the WebID. It is discouraged for Solid WebID Profiles to advertise more than one inbox.

Applications can create an inbox (see resource @@ -1299,13 +1314,8 @@

Inbox

-
-

Other predicates

+
+

7. Other predicates

A user, a server or an application with appropriate permissions can add @@ -1321,320 +1331,204 @@

Other predicates

-
-

References

+
+

A. Changelog

-
-

Normative References

+

This section is non-normative.

+ +

The following summary of editorial, substantive, and registry changes are classified using the W3C Process Document Classes of Changes [W3C-PROCESS]:

+
+
+ +
+

B. Acknowledgements

+
+

The Community Group gratefully acknowledges the work that led to the creation of this specification, and extends sincere appreciation to those individuals that worked on technologies and specifications that deeply influenced our work.

+ +

The Community Group would like to thank the following individuals for their useful comments, both large and small, that have led to changes to this specification over the years:

+ +
    +
  • Aaron Coburn
    • +
  • Abdurrahman Ibrahim Ghanem
    • +
  • Alain Bourgeois
    • +
  • Amy Guy
    • +
  • Andrei Sambra
    • +
  • Angelo Veltens
    • +
  • Arne Hassel
    • +
  • Daniel Bakas
    • +
  • Dmitri Zagidulin
    • +
  • elf Pavlik
    • +
  • Emelia Smith
    • +
  • Frederick Gibson
    • +
  • Henry Story
    • +
  • Herbert Van de Sompel
    • +
  • Jackson Morgan
    • +
  • Jeff Zucker
    • +
  • Jordan Shurmer
    • +
  • Kingsley Kidehen
    • +
  • Kjetil Kjernsmo
    • +
  • Matt Farmer
    • +
  • Matthieu Bosquet
    • +
  • Melvin Carvalho
    • +
  • Michiel de Jong
    • +
  • Mitzi László
    • +
  • Nicola Greco
    • +
  • mrkvon
    • +
  • Nick Mondada
    • +
  • Noel de Martin
    • +
  • Patrick Hochstenbach
    • +
  • Pete Edwards
    • +
  • Ruben Verborgh
    • +
  • Rui Zhao
    • +
  • Samu Lang
    • +
  • Sandro Hawke
    • +
  • Sarven Capadisli
    • +
  • Seila Gonzalez Estrecha
    • +
  • Ted Thibodeau Jr
    • +
  • Tim Berners-Lee
    • +
  • Timea Turdean
    • +
  • Virginia Balseiro
    • +
  • Wouter Termont
    • +
+
+
+ +
+

C. References

+
+
+

C.1 Normative References

[DC-TERMS]
- Dublin Core Metadata Terms, version 1.1. DCMI Usage Board. DCMI. 11 October 2010. DCMI + Dublin Core Metadata Terms, version 1.1. DCMI Usage Board. DCMI. 11 October 2010. DCMI Recommendation. URL: - http://dublincore.org/documents/2010/10/11/dcmi-terms/ + http://dublincore.org/documents/2010/10/11/dcmi-terms/
[FETCH]
- Fetch Standard. Anne van Kesteren. WHATWG. Living Standard. URL: - https://fetch.spec.whatwg.org/ + Fetch Standard. Anne van Kesteren. WHATWG. Living Standard. URL: + https://fetch.spec.whatwg.org/
[IANA-MEDIA-TYPES]
- Media Types. IANA. URL: - https://www.iana.org/assignments/media-types/ + Media Types. IANA. URL: + https://www.iana.org/assignments/media-types/
[LDN]
- Linked Data Notifications. Sarven Capadisli; Amy Guy. W3C. 2 May 2017. W3C + Linked Data Notifications. Sarven Capadisli; Amy Guy. W3C. 2 May 2017. W3C Recommendation. URL: - https://www.w3.org/TR/ldn/ + https://www.w3.org/TR/ldn/
[LDP]
- Linked Data Platform 1.0. Steve Speicher; John Arwe; Ashok Malhotra. W3C. 26 + Linked Data Platform 1.0. Steve Speicher; John Arwe; Ashok Malhotra. W3C. 26 February 2015. W3C Recommendation. URL: - https://www.w3.org/TR/ldp/ + https://www.w3.org/TR/ldp/
[RDF-SCHEMA]
- RDF Schema 1.1. Dan Brickley; Ramanathan Guha. W3C. 25 February 2014. + RDF Schema 1.1. Dan Brickley; Ramanathan Guha. W3C. 25 February 2014. W3C Recommendation. URL: - https://www.w3.org/TR/rdf-schema/ + https://www.w3.org/TR/rdf-schema/
[RDF11-CONCEPTS]
- RDF 1.1 Concepts and Abstract Syntax. Richard Cyganiak; David Wood; Markus Lanthaler. W3C. 25 + RDF 1.1 Concepts and Abstract Syntax. Richard Cyganiak; David Wood; Markus Lanthaler. W3C. 25 February 2014. W3C Recommendation. URL: - https://www.w3.org/TR/rdf11-concepts/ + https://www.w3.org/TR/rdf11-concepts/
[RFC2119]
- Key words for use in RFCs to Indicate Requirement - Levels. S. Bradner. IETF. March 1997. Best Current Practice. + Key words for use in RFCs to Indicate Requirement + Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: - https://datatracker.ietf.org/doc/html/rfc2119 + https://datatracker.ietf.org/doc/html/rfc2119
[RFC3986]
- Uniform Resource Identifier (URI): Generic - Syntax. T. Berners-Lee; R. Fielding; L. Masinter. IETF. January + Uniform Resource Identifier (URI): Generic + Syntax. T. Berners-Lee; R. Fielding; L. Masinter. IETF. January 2005. Internet Standard. URL: - https://datatracker.ietf.org/doc/html/rfc3986 + https://datatracker.ietf.org/doc/html/rfc3986
[RFC6454]
- The Web Origin Concept. A. Barth. IETF. December 2011. Proposed Standard. URL: - https://datatracker.ietf.org/doc/html/rfc6454 + The Web Origin Concept. A. Barth. IETF. December 2011. Proposed Standard. URL: + https://datatracker.ietf.org/doc/html/rfc6454
[RFC8174]
- Ambiguity of Uppercase vs Lowercase in RFC 2119 Key - Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: - https://datatracker.ietf.org/doc/html/rfc8174 + Ambiguity of Uppercase vs Lowercase in RFC 2119 Key + Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: + https://datatracker.ietf.org/doc/html/rfc8174
[RFC9110]
- HTTP Semantics. R. Fielding, M. Nottingham, J. Reschke, Editors. IETF. June 2022. + HTTP Semantics. R. Fielding, M. Nottingham, J. Reschke, Editors. IETF. June 2022. Internet Standard. URL: - https://www.rfc-editor.org/rfc/rfc9110 + https://www.rfc-editor.org/rfc/rfc9110
[RFC9112]
- HTTP/1.1. R. Fielding, M. Nottingham, J. Reschke, Editors. IETF. June 2022. + HTTP/1.1. R. Fielding, M. Nottingham, J. Reschke, Editors. IETF. June 2022. Internet Standard. URL: - https://www.rfc-editor.org/rfc/rfc9112 + https://www.rfc-editor.org/rfc/rfc9112
[SOLID-OIDC]
- SOLID-OIDC. Aaron Coburn; elf Pavlik; Dmitri Zagidulin. W3C Solid + SOLID-OIDC. Aaron Coburn; elf Pavlik; Dmitri Zagidulin. W3C Solid Community Group. 28 March 2022. Version 0.1.0. URL: - https://solidproject.org/TR/oidc + https://solidproject.org/TR/oidc
[SOLID-PROTOCOL]
- Solid Protocol. Sarven Capadisli; Tim Berners-Lee; Ruben Verborgh; - Kjetil Kjernsmo. W3C Solid Community Group. 17 December - 2021. Version 0.9.0. URL: - https://solidproject.org/TR/protocol + Solid Protocol. Sarven Capadisli; Tim Berners-Lee; Kjetil Kjernsmo. W3C Solid Community Group. 12 May + 2024. Draft Community Group Report, Version 0.11.0. URL: + https://solidproject.org/TR/protocol
[WAC]
- Web Access Control. Sarven Capadisli. W3C Solid Community Group. 11 July - 2021. Draft. URL: - https://solidproject.org/TR/wac + Web Access Control. Sarven Capadisli. W3C Solid Community Group. 12 May + 2024. Draft Community Group Report, Version 1.0.0. URL: + https://solidproject.org/TR/wac
[WEBARCH]
- Architecture of the World Wide Web, Volume One. Ian Jacobs; Norman Walsh. W3C. 15 December 2004. W3C + Architecture of the World Wide Web, Volume One. Ian Jacobs; Norman Walsh. W3C. 15 December 2004. W3C Recommendation. URL: - https://www.w3.org/TR/webarch/ + https://www.w3.org/TR/webarch/
[WEBID]
- WebID 1.0. Andrei Sambra; Stéphane Corlosquet. W3C WebID Community + WebID 1.0. Andrei Sambra; Stéphane Corlosquet. W3C WebID Community Group. 5 March 2014. W3C Editor’s Draft. URL: - https://www.w3.org/2005/Incubator/webid/spec/identity/ + https://www.w3.org/2005/Incubator/webid/spec/identity/
-
-

Informative References

+
+

C.2 Informative References

[COGA-USABLE]
-
- Making content usable for people with cognitive and - learning disabilities. Lisa Seeman-Horwitz; Rachael Bradley Montgomery; Steve - Lee; Ruoxi Ran. W3C. 11 December 2020. W3C Working Draft. - URL: - https://www.w3.org/TR/coga-usable/ -
+
Making Content Usable for People with Cognitive and Learning Disabilities. Lisa Seeman-Horwitz; Rachael Bradley Montgomery; Steve Lee; Ruoxi Ran. W3C. 29 April 2021. W3C Working Group Note. URL: https://www.w3.org/TR/coga-usable/
[PRIVACY-PRINCIPLES]
-
- Privacy Principles. Robin Berjon; Jeffrey Yasskin. W3C. 12 May 2022. W3C - Group Draft Note. URL: - https://www.w3.org/TR/privacy-principles/ -
+
Privacy Principles. Robin Berjon; Jeffrey Yasskin. W3C. 18 May 2024. W3C Group Draft Note. URL: https://www.w3.org/TR/privacy-principles/
[SECURITY-PRIVACY-QUESTIONNAIRE]
-
- Self-Review Questionnaire: Security and Privacy. Theresa O'Connor; Peter Snyder. W3C. 23 March 2021. W3C - Note. URL: - https://www.w3.org/TR/security-privacy-questionnaire/ -
-
- W3C Accessibility Guidelines (WCAG) 3.0. Jeanne F Spellman; Rachael Bradley Montgomery; Shawn - Lauriat; Michael Cooper. W3C. 21 January 2021. W3C Working - Draft. URL: - https://www.w3.org/TR/wcag-3.0/ -
+
Self-Review Questionnaire: Security and Privacy. Theresa O'Connor; Peter Snyder. W3C. 16 December 2021. W3C Group Note. URL: https://www.w3.org/TR/security-privacy-questionnaire/
+
+ [WCAG-3.0] +
+
W3C Accessibility Guidelines (WCAG) 3.0. Jeanne F Spellman; Alastair Campbell; Kevin White; Rachael Bradley Montgomery; Charles Adams. W3C. 16 May 2024. W3C Working Draft. URL: https://www.w3.org/TR/wcag-3.0/
+
[W3C-PROCESS]
+
W3C Process Document. Elika J. Etemad / fantasai; Florian Rivoal; W3C Process Community Group. 3 November 2023. URL: https://www.w3.org/Consortium/Process/