Version numbers - Githubissues

plehegar commented 3 years ago

This addresses #11

cc @dontcallmedom @ashimura

dontcallmedom commented 3 years ago

paging @tidoust and @deniak since this was at least analyzed in the context of the series management

deniak commented 3 years ago

With the work on the series, we started to store the version number as it appears in the title but there's a lack of consistency between the specs leading to different shortname strategy. For instance:

WebXR Hand Input Module - Level 1, shortname: webxr-hand-input-1, version number stored: 1
Personalization Semantics Content Module 1.0, shortname: personalization-semantics-content-1.0, version number stored: 1.0
Representing Content in RDF 1.0, shortname: Content-in-RDF10, version number stored: 1.0
Decentralized Identifiers (DIDs) v1.0, shortname: did-core, version number stored: 1.0

As you can see, the version appearing in the title can affect the choice of the shortname so since 2, 2.0, 2.0.0 are equivalent, I was wondering if we couldn't only allow the first format to avoid ambiguity. We aren't there yet, but I thinking there could be some confusion if a spec reaches a level 10+.

w3c / manual-of-style

Version numbers #13