Update to use DID-EXTENSIONS reference.

index.html

@@ -688,8 +688,8 @@ <h2>
 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.
       </p>
 
@@ -1048,7 +1048,7 @@ <h1>Data Model</h1>
 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 @@ <h2>Extensibility</h2>
       <ol>
         <li>
 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.
         </li>
       <li>
 [=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 <a
@@ -1212,7 +1212,7 @@ <h2>Extensibility</h2>
       <p class="note" title="Unregistered extensions are less reliable">
 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.
       </p>
@@ -1659,8 +1659,8 @@ <h2>Production and Consumption</h2>
 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.
       </p>
       <p>
@@ -1701,8 +1701,8 @@ <h2>Production and Consumption</h2>
         </li>
         <li>
 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]].
         </li>
       </ol>
 
@@ -1759,8 +1759,8 @@ <h2>Production and Consumption</h2>
 entry=] across all known [=representations=] and place the entry into a
 [=representation-specific entries=] <a data-cite="INFRA#maps">map</a>
 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]].
         </li>
         <li>
 A [=conforming consumer=] MUST add all [=non-representation-specific
@@ -2238,8 +2238,8 @@ <h3>Production</h3>
 
         <p>
 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]].
         </p>
 
         <p>
@@ -2432,8 +2432,8 @@ <h2>Method Syntax</h2>
         </li>
         <li>
 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]].
         </li>
         <li>
 A [=DID method=] MAY define multiple `method-specific-id` formats.
@@ -2647,7 +2647,7 @@ <h1>Security Considerations</h1>
       <h2>Choosing DID Resolvers</h2>
 
       <p>
-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 @@ <h2>DID Documents</h2>
       <p>
 See <a
 href="https://www.w3.org/TR/did-extensions-properties/#verification-method-types">
-Verification Method Types</a> [[?DID-SPEC-REGISTRIES]] for optional extensions
+Verification Method Types</a> [[?DID-EXTENSIONS]] for optional extensions
 and other verification method types.
       </p>
 
@@ -4195,7 +4195,7 @@ <h2>Revision History</h2>
 representations including JSON and JSON-LD.
       </li>
       <li>
-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.