- Implementers as well as DID method specification authors might use + [=DID URL authors=] might use additional DID parameters that are not listed here. For maximum interoperability, it is RECOMMENDED that DID parameters use the DID Document Properties Extensions mechanism [[?DID-EXTENSIONS-PROPERTIES]], to avoid collision with other uses of the same DID parameter with different semantics.
-- DID parameters might be used if there is a clear use case where the parameter - needs to be part of a URL that references a resource with more - precision than using the DID alone. It is expected that DID parameters - are not used if the same functionality can be expressed by passing - input metadata to a DID resolver. -
-The DID resolution and the DID URL dereferencing functions can be influenced by passing or - to a DID resolver that are + to a DID resolver, or a DID URL dereferencer that are not part of the DID URL. This is comparable to HTTP, where certain parameters could either be included in an HTTP URL, or - alternatively passed as HTTP headers during the dereferencing process. The - important distinction is that DID parameters that are part of the DID - URL should be used to specify what resource is being - identified, whereas input metadata that is not part of the DID URL - should be used to control how that resource is resolved or - dereferenced. + alternatively passed as HTTP headers during the dereferencing process.
+If [=Resolve=] or [=Dereference=] is called with a resolution option of the same name as a DID parameter in the input DID URL, the resolution option MUST override the DID parameters, when interpreted by the Resolver or Dereferencer, respectively.