- From: Pierre-Antoine Champin <pierre-antoine@w3.org>
- Date: Fri, 9 Dec 2022 09:06:06 +0100
- To: Gregg Kellogg <gregg@greggkellogg.net>, RDF-star Working Group <public-rdf-star-wg@w3.org>
Received on Friday, 9 December 2022 08:06:09 UTC
Looking at what happened for json-ld11-api : https://www.w3.org/standards/history/json-ld-api https://www.w3.org/standards/history/json-ld11-api I don't believe that there's any magic in it. Only that the former was explicitly superceded by the latter, and so it now redirects to the relevant spec. But yes, I'll check that with the sys team. pa On 08/12/2022 20:54, Gregg Kellogg wrote: > We discussed today using the “rdf12-“ prefix for our specs and repositories (e.g., “‘rdf12-concepts” for RDF 1.2 Concepts). But, not all specs used this convention. > > * n-triples > * n-quads > * turtle > * trig > * rdf-syntax-grammar > > I think for the infrastructure, it probably makes sense to append “12” to those shortnames (e.g., “n-triples12”) rather than starting a new convention. I believe that there’s some standard infrastructure that handles version numbers in shortnames, so that “n-triples” would end up refering to our spec, and “n-triples11” would (magically) refer to the 1.1 version. > > We should probably run this by Philippe and/or Dom. > > Gregg Kellogg > gregg@greggkellogg.net > >
Received on Friday, 9 December 2022 08:06:09 UTC