Re: Remaining RDF documents pushed and boilerplate for SPARQL

This is great! Thanks a lot, Gregg

On 18/01/2023 01:25, Gregg Kellogg wrote:
> I’ve pushed up and merged the initial content for the remaining RDF 
> specs, and pushed up boilerplate content for the SPARQL documents. All 
> the documents referenced from the Set of Documents [1] should 
> de-reference with essentially the 1.1 content modulo the updates I 
> described for Concepts.
>
> RDF 1.2 Recommendations:
>
>  1. What’s New in RDF 1.2 <https://w3c.github.io/rdf-new/spec/>
>  2. RDF 1.2 Concepts and Abstract Syntax (this document)
>  3. RDF 1.2 N-Quads <https://w3c.github.io/rdf-n-quads/spec/>
>  4. RDF 1.2 N-Triples <https://w3c.github.io/rdf-n-triples/spec/>
>  5. RDF 1.2 Primer <https://w3c.github.io/rdf-primer/spec/>
>  6. RDF 1.2 Schema <https://w3c.github.io/rdf-schema/spec/>
>  7. RDF 1.2 Semantics <https://w3c.github.io/rdf-semantics/spec/>
>  8. RDF 1.2 TriG <https://w3c.github.io/rdf-trig/spec/>
>  9. RDF 1.2 Turtle <https://w3c.github.io/rdf-turtle/spec/>
> 10. RDF 1.2 XML Syntax <https://w3c.github.io/rdf-xml/spec/>
>
> SPARQL 1.2 Recommendations:
>
>  1. What’s New in SPARQL 1.2 <https://w3c.github.io/sparql-new/spec/>
>  2. SPARQL 1.2 Concepts <https://w3c.github.io/sparql-concepts/spec/>
>  3. SPARQL 1.2 Query Language <https://w3c.github.io/sparql-query/spec/>
>  4. SPARQL 1.2 Update <https://w3c.github.io/sparql-update/spec/>
>  5. SPARQL 1.2 Service Description
>     <https://w3c.github.io/sparql-service-description/spec/>
>  6. SPARQL 1.2 Federated Query
>     <https://w3c.github.io/sparql-federated-query/spec/>
>  7. SPARQL 1.2 Query Results JSON Format
>     <https://w3c.github.io/sparql-results-json/spec/>
>  8. SPARQL 1.2 Query Results CSV and TSV Formats
>     <https://w3c.github.io/sparql-results-csv-tsv/spec/>
>  9. SPARQL 1.2 Query Results XML Formats
>     <https://w3c.github.io/sparql-results-xml/spec/>
> 10. SPARQL 1.2 Entailment Regimes
>     <https://w3c.github.io/sparql-entailment/spec/>
> 11. SPARQL 1.2 Protocol <https://w3c.github.io/sparql-protocol/spec/>
> 12. SPARQL 1.2 Graph Store HTTP Protocol
>     <https://w3c.github.io/sparql-http-rdf-update/spec/>
>
>
> Gregg Kellogg
> gregg@greggkellogg.net
>
> [1] https://w3c.github.io/rdf-concepts/spec/#related

>
>> On Jan 16, 2023, at 11:31 AM, Gregg Kellogg <gregg@greggkellogg.net> 
>> wrote:
>>
>> I pushed the first of the RDF specs to GitHub, which you can see at 
>> https://w3c.github.io/rdf-concepts/spec. This is essentially just RDF 
>> 1.1 Concepts with minor updates for references and updated ReSpec. I 
>> did create a “Set of Documents” section [1], which is intended to be 
>> shared among all the specs, and will automatically note “this 
>> document”. Common files go into the /spec/common directory, although 
>> there’s no easy way I know of to synchronize them between the 
>> different repositories (Git submodules are certainly a possibility, 
>> but may be more trouble then they’re worth).
>>
>> Additionally, I made a number of fixes to definitions, while 
>> preserving any old fragment identifiers so that documents which may 
>> link to, say, #dfn-nodes will still go to the right place, even 
>> though the proper exported term is #dfn-node. Also, in some cases 
>> there are terms defined duplicately in different specs (e.g., 
>> “entailment-regime” (#dfn-entaiilment-regime) should be defined in 
>> RDF Semantics, not RDF Concepts, which you may debate).
>>
>> I haven’t otherwise addressed 1.2 vs 1.1 issues, and the former 
>> editors, acknowledges, and changes sections are largely untouched. At 
>> some point, issues should be created for Errata, and RDF-star updates 
>> that should be made in this, and other, specs.
>>
>> ReSpec supports a term indexing feature, which you can see at [2] 
>> which we can use, at least temporarily, to note terms defined in this 
>> spec, and imported from other specs.
>>
>> There is also a problem ReSpec reports ("ReSpec doesn't support 
>> expanding this kind of reference.”), which seems to be a ReSpec bug 
>> introduced by creating temporary bibliographic entries, and is 
>> reported at [3]. Presumably, the error will go away when the issue is 
>> addressed.
>>
>> Based on feedback to this general layout (no normative updates 
>> intended), I can upload other RDF documents which use a similar 
>> structure.
>>
>> Note that I will not be on the Thursday call this week, due to travel.
>>
>> Gregg Kellogg
>> gregg@greggkellogg.net
>>
>> [1] https://w3c.github.io/rdf-concepts/spec/#related

>> [2] https://w3c.github.io/rdf-concepts/spec/#index

>> [3] https://github.com/w3c/respec/issues/4362

>