Spec names

Hi all,

as decided during the last call, here is a proposal of a consistent 
naming for the specs in our charter.

1. Versionless names
Some of these names are already used, some have been changed for the 
sake of consistency.The idea is that all (including the existing ones) 
would now point to the latest version.

rdf-primer
rdf-concepts
rdf-mt
rdf-n-quads (currently n-quads)
rdf-n-triples (currently from n-triples)
rdf-trig (currently trig)
rdf-turtle (currently turtle)
rdf-xml  (currently rdf-syntax-grammar, which does not make much sense 
anymore)
rdf-schema

sparql-overview
sparql-query
sparql-update
sparql-results-json
sparql-results-xml
sparql-service-description
sparql-federated-query
sparql-entailment
sparql-protocol
sparql-results-csv-tsv

There was a suggestion in the call to also prepend RDF to the sparql- 
documents. I didn't follow it because
- it makes very long "short names"
- it raises the question of other RDF-related specifications, such as 
json-ld or shacl...


2. Versionned name infix

For the version-specific shortnames, replace rdf- by rdf12- and sparql- 
by sparql12- .

E.g.

rdf12-primer
rdf12-concepts
...
sparql12-overview
sparql12-query
...


3. Versionned name postfix

For the version-specific shortnames, append -12 at the end.

E.g.

rdf-primer-12
rdf-concepts-12
...
sparql-overview-12
sparql-query-12
...

Received on Friday, 16 December 2022 17:18:13 UTC