- From: Pierre-Antoine Champin <pierre-antoine@w3.org>
- Date: Wed, 14 Dec 2022 14:45:07 +0100
- To: RDF-star WG <public-rdf-star-wg@w3.org>
- Message-ID: <7c770251-b247-4715-bac2-7445553ef18b@w3.org>
Hi all, I would like to discuss, in one of our next meetings, the naming convention for the future RDF specifications. There is some documentation about W3C good practices here: https://www.w3.org/2005/05/tr-versions After discussing with the sys team, having the version number in the middle of the short-name (e.g. rdf12-concepts) is possible. That being said, the current state of RDF recommendations is quite messy. For example: - the 1999 RDF-spec-syntax does not indicate anywhere that a more recent version is available - some specs have only a version-less short name (e.g. rdf-primer), which correspond to the 2014 (1.1) version, while others have a versioned short name (e.g. rdf11-concepts) for the 2014 version, and the version-less short name corresponds to the 2004 version (e.g. rdf-concepts) I made a map [1] of the genalogy of RDF specifications, indicating when they point to a more recent version, as well as what short names correspond to. This is also on github [2]. pa PS: at some point, it would be interesting to make a similar map for SPARQL [1] https://raw.githubusercontent.com/pchampin/rdf-genealogy/main/rdf-genealogy.svg [2] https://github.com/pchampin/rdf-genealogy
Attachments
- application/pgp-keys attachment: OpenPGP public key
Received on Wednesday, 14 December 2022 13:45:10 UTC