diff --git a/index.html b/index.html index 8924d7c..e153897 100644 --- a/index.html +++ b/index.html @@ -203,7 +203,7 @@

Solid WebID Profile

-

Version 1.0.0, Editor’s Draft, 2022-06-22

+

Version 1.0.0, Editor’s Draft, 2023-09-04

More details about this document @@ -353,7 +353,7 @@

Version 1.0.0, Editor’s Draft, 2022- datatype="xsd:dateTime" datetime="2022-06-22T00:00:00Z" property="schema:dateModified" - >2022-06-222023-09-04 @@ -740,14 +740,48 @@

Table of Contents

>
  • - 3 + Reading and Writing Profiles +
      +
    1. + 3.1 + Reading Profile +
      2. +
    2. + 3.2 + Updating Profile +
      3. +
    3. + 3.3 + Extending a Profile +
      4. +
    +
    • +
  • + 4 Private Preferences
  • 4 + >5 Extended Profile Documents
      @@ -755,7 +789,7 @@

      Table of Contents

      4.1 + >5.1 Reading Extended Profile DocumentsTable of Contents
    1. 4.2 + >5.2 Writing Extended Profile DocumentsTable of Contents
    2. 5 + >6 Identity Provider
    3. 6 + >7 Storage
    4. 7 + >8 Inbox
    5. 8 + >9 Other predicates
      6. @@ -861,13 +895,19 @@

      Table of Contents

      This specification is for:

        +
      • + Server developers + that want to enable clients to send and retrieve information pertaining to Solid WebID Profiles; +
      • Application developers - that want to implement a client to use WebIDs and Solid - profiles. + that want to implement a client to produce and consume information pertaining to Solid WebID Profiles.
      @@ -1032,31 +1072,55 @@

      Namespaces

      -
      +

      Conformance

      -

      - 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”, “REQUIRED”, “SHALL”, “SHALL - NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and - “OPTIONAL” are to be interpreted as described in - BCP 14 - [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown - here. -

      +

      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.

      +
      +
      + +
      +

      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
      +
      A Solid app that issues HTTP requests to consume content pertaining to WebID Profiles.
      +
      Writer Application
      +
      A Solid app that issues HTTP requests to produce and consume content pertaining to WebID Profiles.
      +
      Server
      +
      A Solid Server that responds to HTTP requests processing payloads pertaining to Solid WebID Profiles.
      +
      +
      +
      + +
      +

      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
      +
      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.
      +
      +
      +
      @@ -1127,6 +1191,151 @@

      Discovering a complete Solid profile

      +
      +

      Reading and Writing Profiles

      +
      +

      Reading Profile

      +
      +

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

      +
      +
      +

      Solid WebID Profile

      +
      +

      The Solid WebID Profile has the following properties:

      +
        +
      • One rdf:type property whose object is foaf:Agent.
        • +
      • One pim:preferencesFile.
        • +
      • Zero or one ldp:inbox.
        • +
      • Zero or more pim:storage.
        • +
      • Zero or more rdfs:seeAlso to refer to related documents + extending the profile.
        • +
      +
      +
      +
      Note:
      +
      +

      The Solid WebID Profiles may include other information pertaining to scenarios in + which profiles are used or shared as mentioned in use + cases.

      +
      +
      +
      +
      +

      Preferences Document

      +
      +

      The Preferences Document has the following properties:

      +
        +
      • One rdf:type property whose object is pim:ConfigurationFile.
        • +
      • Zero or more rdfs:seeAlso.
        • +
      +
      +
      +
      +

      Extended Profile Documents

      +
      +

      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 + Application MAY retrieve a + representation of an Extended Profile Document. +

      +
      +
      +
      +
      +

      Updating Profile

      +
      +

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

      +
      +
      +
      +

      + 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 + 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 + 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

      +
      +

      Writer Applications perform write operations against Solid Protocol servers.

      + +

      Ownership by WebID URI entails that the social agent has authority over the representation of the resource it + identifies, including access to perform write operations targeting the Solid WebID Profile.

      +
      + +

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

      +

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

      +
      +
      +
      +
      +