Add new spec: Decentralized Identifiers v1.1

[msporny]

URL

https://www.w3.org/TR/did-1.1/

Rationale

I need to cite definitions from Decentralized Identifiers v1.1 in a few new DID Method specifications and it doesn't look like it is included in the specref database (I can't get DFNs to show up when including did-1.1 or did in xref in the downstream specs). I'm not positive that this is the right place to add the spec such that it gets included in the DFN exports for webref/specref/etc.

Additional properties

{}

[browser-specs-bot]

Changes to index.json

This update would trigger the following changes in index.json:

Add spec (1)

{
  "url": "https://www.w3.org/TR/did-1.1/",
  "seriesComposition": "full",
  "shortname": "did-1.1",
  "series": {
    "shortname": "did",
    "currentSpecification": "did-1.1",
    "title": "Decentralized Identifiers (DIDs)",
    "shortTitle": "DIDs",
    "releaseUrl": "https://www.w3.org/TR/did/",
    "nightlyUrl": "https://w3c.github.io/did/"
  },
  "seriesVersion": "1.1",
  "organization": "W3C",
  "groups": [
    {
      "name": "Decentralized Identifier Working Group",
      "url": "https://www.w3.org/groups/wg/did/"
    }
  ],
  "release": {
    "url": "https://www.w3.org/TR/did-1.1/",
    "status": "First Public Working Draft",
    "filename": "Overview.html"
  },
  "nightly": {
    "url": "https://w3c.github.io/did/",
    "status": "Editor's Draft",
    "alternateUrls": [],
    "repository": "https://github.com/w3c/did",
    "sourcePath": "index.html",
    "filename": "index.html"
  },
  "title": "Decentralized Identifiers (DIDs) v1.1",
  "source": "w3c",
  "shortTitle": "DIDs",
  "categories": [],
  "standing": "good"
}

Tests

These changes look good! 😎

[tidoust]

@deniak The repository used for DID v1.1 was renamed. As a result, the link to the Editor's Draft that appears in all published versions of DID (v1.0 and FPWD of v1.1) now yield a 404.

I prepared https://github.com/w3c/w3c.github.io/pull/132 to add a redirect. Would it be possible to update the W3C API to return the new ED at https://w3c.github.io/did/ ?

[deniak]

Would it be possible to update the W3C API to return the new ED at https://w3c.github.io/did/ ?

Sure! I just updated the ED link for these specs. @tidoust, so far, I'm not monitoring that kind of changes but I'm guessing we should have some tooling in place to update the ED and create the redirects from time to time.

[tidoust]

@tidoust, so far, I'm not monitoring that kind of changes but I'm guessing we should have some tooling in place to update the ED and create the redirects from time to time.

I don't disagree ;) For specs that enter browser-specs, something will fail, either at the browser-specs level when the list gets built, or at the crawl level in Webref. So we'll end up detecting the problem, which seems a good thing. The reported errors isn't always going to be fantastically explicit (here, complaint was that the filename property was null, which is a consequence of the ED URL returning a 404) but at least something will fail.

[tidoust]

@browser-specs-bot pr

[tidoust]

@msporny said:

I can't get DFNs to show up when including did-1.1 or did in xref in the downstream specs

Adding the spec to browser-specs is the right first step. There are a couple of additional steps (on me) for definitions to propagate to the xref database. That may take up to a day or so.

Now, note that, as far as I can tell, did-1.1 does not export any definition, and ReSpec only allows to reference definitions from other specs that are explicitly flagged as exported. You will have to add class="export" to the definitions that you need to reference from another spec!

[msporny]

Now, note that, as far as I can tell, did-1.1 does not export any definition, and ReSpec only allows to reference definitions from other specs that are explicitly flagged as exported.

Acknowledged, I'm planning on changing that (exporting certain definitions) over the coming weeks, but needed to fix the CID spec references first (since that was breaking TR publications for DID spec).