diff --git a/index.html b/index.html index 8b5c2ed..8b12abc 100644 --- a/index.html +++ b/index.html @@ -360,7 +360,7 @@

DID Parameters

Implementers as well as DID method specification authors might use additional DID parameters that are not listed here. For maximum interoperability, it is RECOMMENDED that DID parameters use the DID - Specification Registries mechanism [[?DID-SPEC-REGISTRIES]], to avoid collision + Document Properties Extensions mechanism [[?DID-EXTENSIONS-PROPERTIES]], to avoid collision with other uses of the same DID parameter with different semantics.

@@ -497,7 +497,7 @@

DID Resolution Options

The possible properties within this structure and their possible values SHOULD - be registered in the DID Specification Registries [[?DID-SPEC-REGISTRIES]]. + be registered in the DID Resolution Extensions [[?DID-EXTENSIONS-RESOLUTION]]. This specification defines the following common input options:

@@ -561,7 +561,7 @@

DID Resolution Metadata

The possible properties within this structure and their possible values SHOULD - be registered in the DID Specification Registries [[?DID-SPEC-REGISTRIES]]. This + be registered in the DID Resolution Extensions [[?DID-EXTENSIONS-RESOLUTION]]. This specification defines the following common metadata properties:

@@ -584,7 +584,7 @@

DID Resolution Metadata

An error data structure defined in [[RFC9457]]. This property is REQUIRED when there is an error in the resolution process. The errors defined by this specification and can be found in Section . - Additional errors SHOULD be registered in the DID Specification Registries [[?DID-SPEC-REGISTRIES]]. + Additional errors SHOULD be registered in the DID Resolution Extensions [[?DID-EXTENSIONS-RESOLUTION]].
@@ -625,7 +625,7 @@

DID Document Metadata

The possible properties within this structure and their possible values SHOULD - be registered in the DID Specification Registries [[?DID-SPEC-REGISTRIES]]. + be registered in the DID Document Properties Extensions [[?DID-EXTENSIONS-PROPERTIES]]. This specification defines the following common metadata properties.

@@ -1081,7 +1081,7 @@

DID URL Dereferencing Options

The possible properties within this structure and their possible values SHOULD - be registered in the DID Specification Registries [[?DID-SPEC-REGISTRIES]]. + be registered in the DID Resolution Extensions [[?DID-EXTENSIONS-RESOLUTION]]. This specification defines the following common input options:

@@ -1121,7 +1121,7 @@

DID URL Dereferencing Metadata

The possible properties within this structure and their possible values SHOULD - be registered in the DID Specification Registries [[?DID-SPEC-REGISTRIES]]. This + be registered in the DID Resolution Extensions [[?DID-EXTENSIONS-RESOLUTION]]. This specification defines the following common metadata properties:

@@ -1141,7 +1141,7 @@

DID URL Dereferencing Metadata

An error data structure defined in [[RFC9457]]. This property is REQUIRED when there is an error in the dereferencing process. The errors defined in this specification can be found in Section . - Additional errors SHOULD be registered in the DID Specification Registries [[?DID-SPEC-REGISTRIES]]. + Additional errors SHOULD be registered in the DID Resolution Extensions [[?DID-EXTENSIONS-RESOLUTION]].
@@ -1173,7 +1173,7 @@

DID URL Content Metadata

The possible properties within this structure and their possible values SHOULD - be registered in the DID Specification Registries [[?DID-SPEC-REGISTRIES]]. This + be registered in the DID Resolution Extensions [[?DID-EXTENSIONS-RESOLUTION]]. This specification defines no common properties.

@@ -1514,8 +1514,8 @@

Metadata Structure

boolean, or null. The values within any complex data structure such as a map or list MUST be one of these data types as well. - All metadata property definitions registered in the DID Specification - Registries [[?DID-SPEC-REGISTRIES]] MUST define the value type, including any + All metadata property definitions registered in the DID Resolution Extensions + [[?DID-EXTENSIONS-RESOLUTION]] MUST define the value type, including any additional formats or restrictions to that value (for example, a string formatted as a date). It is RECOMMENDED that property definitions use strings for values. The entire metadata structure MUST be