decide on the short names of the specifications

[ghurlbot]

due 22 Dec 2022

[gkellogg]

From email chain, I think we come up with the following shortnames:

• RDF12-NEW
• RDF12-CONCEPTS
• RDF12-N-QUADS
• RDF12-N-TRIPLES
• RDF12-PRIMER
• RDF12-SCHEMA
• RDF12-MT – Perhaps RDF12-SEMANTICS would be more obvious
• RDF12-TRIG
• RDF12-TURTLE
• RDF12-XML

and for SPARQL:

• SPARQL12-OVERVIEW
• SPARQL12-QUERY
• SPARQL12-UPDATE
• SPARQL12-SERVICE-DESCRIPTION
• SPARQL12-FEDERATED-QUERY
• SPARQL12-RESULTS-JSON
• SPARQL12-RESULTS-CSV-TSV
• SPARQL12-XMLRES – Perhaps SPARQL12-RESULTS-XML would be more consistent
• SPARQL12-ENTAILMENT
• SPARQL12-PROTOCOL
• SPARQL12-HTTP-RDF-UPDATE

That's 21 documents! Although many may need only minimal editorial work.

[TallTed]

I like the suggested switches to RDF12-SEMANTICS and SPARQL12-RESULTS-XML.

I suggest that RDF12-XML should be changed to RDF12-RDFXML to avoid confusion that's been constant about the relationships between RDF and XML.

I'm happy with the other names as above.

[Tpt]

SPARQL12-HTTP-RDF-UPDATE seems a bit confusing to me. The previous document was named "SPARQL 1.1 Graph Store HTTP Protocol". What about something like SPARQL12-HTTP-GRAPH-STORE-PROTOCOL?

[TallTed]

SPARQL12-HTTP-RDF-UPDATE has a strong potential to confuse relative to SPARQL12-UPDATE (which is already RDF over HTTP...). I would support either SPARQL12-HTTP-GRAPH-STORE-PROTOCOL or SPARQL12-GRAPH-STORE-PROTOCOL for this doc.

[afs]

+1 to sparql12-graph-store-protocol.

[afs]

+1 to rdf12-rdfxml

[ktk]

Updated proposal by @TallTed (via Zoom chat, in here for logging)

RDF12-NEW
RDF12-CONCEPTS
RDF12-PRIMER
RDF12-SCHEMA
RDF12-SEMANTICS
RDF12-SYNTAX-N-QUADS
RDF12-SYNTAX-N-TRIPLES
RDF12-SYNTAX-TRIG
RDF12-SYNTAX-TURTLE
RDF12-SYNTAX-RDFXML

SPARQL12-CONCEPTS
SPARQL12-QUERY
SPARQL12-UPDATE
SPARQL12-SERVICE-DESCRIPTION
SPARQL12-FEDERATED-QUERY
SPARQL12-RESULTS-JSON
SPARQL12-RESULTS-CSV-TSV
SPARQL12-RESULTS-XML
SPARQL12-ENTAILMENT
SPARQL12-PROTOCOL
SPARQL12-GRAPH-STORE-PROTOCOL

[TallTed]

RDF12-NEW
RDF12-CONCEPTS
RDF12-PRIMER
RDF12-SCHEMA
RDF12-SEMANTICS
RDF12-SYNTAX-N-QUADS
RDF12-SYNTAX-N-TRIPLES
RDF12-SYNTAX-TRIG
RDF12-SYNTAX-TURTLE
RDF12-SYNTAX-RDFXML

SPARQL12-NEW
SPARQL12-CONCEPTS
SPARQL12-QUERY
SPARQL12-UPDATE
SPARQL12-SERVICE-DESCRIPTION
SPARQL12-FEDERATED-QUERY
SPARQL12-RESULTS-JSON
SPARQL12-RESULTS-CSV-TSV
SPARQL12-RESULTS-XML
SPARQL12-ENTAILMENT
SPARQL12-PROTOCOL
SPARQL12-GRAPH-STORE-PROTOCOL

[afs]

(The argument made for "syntax-" was just the one case of "rdf12-xml" be coming "rdf12-rdfxml")

I don't think the "syntax-" and "results-" adds much help to people

They require more typing of a longer prefix for browser autocomplete to pick one URL.

[domel]

RDF12-[SYNTAX]-RDFXML

I prefer to remove the RDF substring from the RDFXML. Note that "RDF/XML Syntax Specification" (RDF 1.0) was changed to "RDF 1.1 XML Syntax". I think that the next version will have the title "RDF 1.2 XML Syntax". If so, RDF12-[SYNTAX]-XML is a better option.

[gkellogg]

@afs said:

I don't think the "syntax-" and "results-" adds much help to people

Does this mean you'd prefer the following for SPARQL result formats?

• SPARQL12-JSON
• SPARQL12-CSV-TSV
• SPARQL12-XML

As for RDF/XML, my preference would be RDF12-XML followed by RDF12-RDFXML, but I think that's redundant. Lastly, RDF12-XML-SYNTAX, but don't favor adding SYNTAX to any other concrete format.

Note that the JSON-LD group will likely end up publishing JSON-LD12, JSON-LD12-API, and JSON-LD12-FRAMING eventually.