Register DID service names

[mmccool]

• Actually register (with appropriate DID repo) the WotThing and WotDirectory service names

[mmccool]

Below is the email with instructions that I got from Manu Sporny. There is currently only one other service type registered, for DIDComm, which I plan to use as a template. However, it seems that a JSON-LD context file (and URL) are also needed. I have created this PR: w3c/did-extensions#486

Registration isn't required, but is encouraged. There is a "Service Types" section in the DID Specification Registries:

https://w3c.github.io/did-spec-registries/#service-types

You can name a service type anything you'd like (as long as it doesn't
clash with anything else in the document)... though they typically
take the following form:

WotThing
WotDirectory

Also, ensure that the JSON-LD Context you include in the DID Document
defines both of those class names above.

You can raise a PR to add those service types in this section:

https://github.com/w3c/did-spec-registries/blob/main/index.html#L1527

on this repo:

https://github.com/w3c/did-spec-registries/pulls

[mmccool]

The URL I am proposing for the context file: https://www.w3.org/2021/wot/discovery/did
This is similar to the one we already have in the spec but adds a "did" suffix since I think we want a context file that ONLY defines these two terms. Also, we may need to add an assertion to specify this URL in the WoT Discovery spec which would be a normative change. On the other hand, if it is specified in the DID Registry perhaps that can be considered the normative reference and updating the example in our spec would be sufficient - although we also need to add that reference. To discuss. Obviously making normative changes in our spec during CR will be difficult (I'm hoping however that we can ask for "Director approval" if it is necessary).

[mmccool]

Need to update the WoT Discovery spec to match the DID registry, including the @context. To do (1 at least, 2 and 3 need to be discussed):

1. Update the examples to include the @context (informative, not a problem)
2. Add a normative reference to DID registry (normative reference... don't need to add an assertion to WoT Discovery)
3. Add an assertion defining the @context (new assertion - normative content)

We definitely need special permission for doing 3 during CR period; not sure about 2. Need to talk to @plehegar...

McCool: will create PR (to Editor's version) updating the example to be consistent with what has been submitted to DID registration.

[mmccool]

Could also add an editor's note to this section about this issue. Since it is at risk, we could also convert the whole thing to an informative section and call it "experimental". Also note that if we remove or change 6.5 we have to change the "DID Considerations" (section 12/12.1).

[mmccool]

Have updated DID PR to be consistent with Discovery spec, but not yet merged into DID repo - needs a dereferencable ontology file. Registrations are technically separate, but we should finalize it before the end of the current charter.

[mmccool]

PR in DID registry is completed and reviews have passed, now just waiting for merge. See w3c/did-extensions#486