Build now traps the fact that the shortname for CSS 2.1 and RDF 1.1 N-Quads do not match those used in the W3C API. This update aligns the shortnames accordingly.
For CSS 2.1, shortname was CSS2 instead of CSS21, probably because we used /TR/CSS2/ at some point. Note: Reffy will need a short update as it uses the shortname to run dedicated pre-processing on the spec to extract definitions. I cannot think of other consequences that we need to worry about.
For RDF 1.1 N-Quads, the canonical /TR URL returned by the W3C API ends with /TR/n-quads/, but the shortname is rdf11-n-quads. The longer shortname is inconsistent with the URL but consistent with the rdf12-n-quads shortname and allows the code to put both n-quads entries in the same series, as done in the W3C API: https://api.w3.org/specification-series/rdf-n-quads/specifications
Build now traps the fact that the shortname for CSS 2.1 and RDF 1.1 N-Quads do not match those used in the W3C API. This update aligns the shortnames accordingly.
For CSS 2.1, shortname was
CSS2instead ofCSS21, probably because we used/TR/CSS2/at some point. Note: Reffy will need a short update as it uses the shortname to run dedicated pre-processing on the spec to extract definitions. I cannot think of other consequences that we need to worry about.For RDF 1.1 N-Quads, the canonical /TR URL returned by the W3C API ends with
/TR/n-quads/, but the shortname isrdf11-n-quads. The longer shortname is inconsistent with the URL but consistent with therdf12-n-quadsshortname and allows the code to put both n-quads entries in the same series, as done in the W3C API: https://api.w3.org/specification-series/rdf-n-quads/specifications