A unique identifier for W3C specifications

[kael]

It'd be nice if the W3C specifications had a unique ID that we could use to query APIs similarly to what is done with other standardization instances specifications.

IETF Internet-Drafts & RFC have an ID in the form of urn:ietf:id:draft-blank-ietf-bimi-02 and urn:ietf:rfc:9114, and can be used with the IETF API.

Similarly, there exists the same for ETSI specifications, e.g urn:etsi:102818 and XSF specifications (with spec versioning) e.g urn:xmpp:feature-fallback:0.

[jackromo888]

https://github.com/WICG/admin/issues/154#issue-1344161655

[cwilso]

Somewhat related to #138, and also to the general theme of "Incubation, Implementation, and Interoperability."

[kael]

As an addendum, each RFC ID has also a corresponding DOI as defined by RFC 7669.

[marcoscaceres]

I think this is outside the scope of the WICG, tbh... but would be something more general for the W3C.

At the same time, I'm sure where to move this issue to, but it's probably not something we can tackle in the WICG.

@cwilso, maybe something for the AB as it's organization wide?

[marcoscaceres]

I'm included to close this as it's not a WICG issue...

@dontcallmedom maybe you can suggest where this discussion should move to?

[dontcallmedom]

At least for Technical reports, I think the unique ID is the "This version" URI, which in particular can be used with the W3C API to retrieve information about a specific version of a spec. But this approach doesn't apply to Community Groups (such as the WICG).

@kael I'm not sure if your request is about unique identifiers for specific versions of WICG documents, for Community Groups documents more generally, or if the "This Version" URI of W3C technical reports (see also ow W3C manages spec versions ) doesn't fulfil the requirements you had in mind.

[kael]

I'm not sure if your request is about unique identifiers for specific versions of WICG documents, for Community Groups documents more generally, or if the "This Version" URI of W3C technical reports

I was thinking more about using CURIE - an URN - for W3C specifications ID as there are for IETF, ETSI or ISO specifications.

Looking at the WebConcept specs list, it uses the W3C spec URL as its URI, whereas IETF or OASIS specs have an URN as an URI.

Versioning would be interesting, ISO URN handles versioning (IIRC).

The main request is about having a CURIE, URN-style, for W3C specifications, though - perhaps the issue should re-titled.

As an aside, making the W3C API opened the IETF way would be neat.

Cheers.