From 2b62fb3b83d455da919904c7d2787292acc40d8b Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sun, 26 Jan 2025 20:05:13 -0500 Subject: [PATCH] Update to use DID-EXTENSIONS reference. --- index.html | 38 +++++++++++++++++++------------------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/index.html b/index.html index 7367bc9e..84bba767 100644 --- a/index.html +++ b/index.html @@ -688,8 +688,8 @@

Some examples contain terms, both property names and values, that are not defined in this specification. These are indicated with a comment (`// external (property name|value)`). Such terms, when used in a [=DID -document=], are expected to be registered in the DID Specification Registries -[[?DID-SPEC-REGISTRIES]] with links to both a formal definition and a JSON-LD +document=], are expected to be registered in the repository of DID Extensions +[[?DID-EXTENSIONS]] with links to both a formal definition and a JSON-LD context.

@@ -1048,7 +1048,7 @@

Data Model

is labeled "Properties", and the space below it, "Representation-specific entries". Six labeled rectangles appear in the diagram, three lying above the dotted grey line and three below it. A large green rectangle, labeled "DID -Specification Registries", encloses the four leftmost rectangles (upper left, +Extensions", encloses the four leftmost rectangles (upper left, upper center, lower left, and lower center). The two leftmost rectangles (upper left and lower left) are outlined in blue and labeled in blue, as follows. The upper left rectangle is labeled "Core Properties", and contains @@ -1195,14 +1195,14 @@

Extensibility

  1. For maximum interoperability, it is RECOMMENDED that extensions use the -W3C DID Specification Registries mechanism [[?DID-SPEC-REGISTRIES]]. The use of +repository of DID Extensions [[?DID-EXTENSIONS]]. The use of this mechanism for new properties or other extensions is the only specified mechanism that ensures that two different [=representations=] will be able to work together.
  2. [=Representations=] MAY define other extensibility mechanisms, including ones -that do not require the use of the DID Specification Registries. Such extension +that do not require the use of the DID Extensions. Such extension mechanisms SHOULD support lossless conversion into any other conformant [=representation=]. Extension mechanisms for a [=representation=] SHOULD define a mapping of all properties and [=representation=] syntax into the Extensibility

    It is always possible for two specific implementations to agree out-of-band to use a mutually understood extension or [=representation=] that is not -recorded in the DID Specification Registries [[?DID-SPEC-REGISTRIES]]; +recorded in the repository of DID Extensions [[?DID-EXTENSIONS]]; interoperability between such implementations and the larger ecosystem will be less reliable.

    @@ -1659,8 +1659,8 @@

    Production and Consumption

    In addition to the [=representations=] defined in this specification, implementers can use other [=representations=], providing each such [=representation=] is properly specified (including rules for -interoperable handling of properties not listed in the DID Specification -Registries [[?DID-SPEC-REGISTRIES]]). See [[[#extensibility]]] +interoperable handling of properties not listed in the repository of +DID Extensions [[?DID-EXTENSIONS]]). See [[[#extensibility]]] for more information.

    @@ -1701,8 +1701,8 @@

    Production and Consumption

  3. In order to maximize interoperability, [=representation=] specification -authors SHOULD register their [=representation=] in the DID Specification -Registries [[?DID-SPEC-REGISTRIES]]. +authors SHOULD register their [=representation=] in the repository of +DID Extensions [[?DID-EXTENSIONS]].
@@ -1759,8 +1759,8 @@

Production and Consumption

entry=] across all known [=representations=] and place the entry into a [=representation-specific entries=] map which is returned after the [=consumption=] process completes. A list of -all known [=representation-specific entries=] is available in the -DID Specification Registries [[?DID-SPEC-REGISTRIES]]. +all known [=representation-specific entries=] is available in the repository of +DID Extensions [[?DID-EXTENSIONS]].
  • A [=conforming consumer=] MUST add all [=non-representation-specific @@ -2238,8 +2238,8 @@

    Production

    In order to achieve interoperability across different [=representations=], -all JSON-LD Contexts and their terms SHOULD be registered in the DID -Specification Registries [[?DID-SPEC-REGISTRIES]]. +all JSON-LD Contexts and their terms SHOULD be registered in the repository of +DID Extensions [[?DID-EXTENSIONS]].

    @@ -2432,8 +2432,8 @@

    Method Syntax

  • To reduce the chances of `method-name` conflicts, a [=DID method=] -specification SHOULD be registered in the DID Specification Registries -[[?DID-SPEC-REGISTRIES]]. +specification SHOULD be registered in the repository of DID Extensions +[[?DID-EXTENSIONS]].
  • A [=DID method=] MAY define multiple `method-specific-id` formats. @@ -2647,7 +2647,7 @@

    Security Considerations

    Choosing DID Resolvers

    -The DID Specification Registries [[?DID-SPEC-REGISTRIES]] contains an +The repository of DID Extensions [[?DID-EXTENSIONS]] contains an informative list of [=DID method=] names and their corresponding [=DID method=] specifications. Implementers need to bear in mind that there is no central authority to mandate which [=DID method=] specification is to be used @@ -3134,7 +3134,7 @@

    DID Documents

    See -Verification Method Types [[?DID-SPEC-REGISTRIES]] for optional extensions +Verification Method Types [[?DID-EXTENSIONS]] for optional extensions and other verification method types.

    @@ -4195,7 +4195,7 @@

    Revision History

    representations including JSON and JSON-LD.
  • -The introduction of a DID Specifications Registry for the purposes of +The introduction of a repository of DID Extensions for the purposes of registering extension properties, representations, DID Resolution input metadata and output metadata, DID Document metadata, DID parameters, and DID Methods.