- From: Pierre-Antoine Champin <pierre-antoine@w3.org>
- Date: Fri, 26 Jan 2024 15:19:18 +0100
- To: David Booth <david@dbooth.org>, public-rdf-star@w3.org
- Message-ID: <2f79b7fe-41cf-4308-b133-aed5ea8f456d@w3.org>
On 25/01/2024 23:07, David Booth wrote: > On 1/25/24 12:13, Pierre-Antoine Champin wrote: >> . . . >> https://htmlpreview.github.io/?https://github.com/w3c/rdf-star-wg/blob/main/docs/seeking-consensus-2024-01.html >> >> (source: >> https://github.com/w3c/rdf-star-wg/blob/main/docs/seeking-consensus-2024-01.md) > > Fantastic summary! But I am surprised that I do not see any option > to harmonize with named graphs. That seems like an obvious option to > consider, since :e (in your examples) is merely a fourth component > tacked onto the triple, and that's exactly what named graphs provide > -- see NQuads. > > Were named graphs already considered for RDF-star implementation and > rejected? If so, why? The general opinion is that this is inappropriate for a number of users, who use named graphs for different purposes (classing triples by provenance, or by permission, etc...). If adding quoted triples in a graph was creating "spurious" named graphs, this would potentially break, or at least interfere with, their business logic. Also, named graphs are not covered by RDF semantics (for exactly the same reason: there are so many different uses of named graphs out there that any fixed semantics would not be consistent with some of them). Our ambition is to provide a standard (if minimal) semantics for RDF-star quoted triples. Hope this helps. > Please forgive me if this is a naive question from a distant observer. > > Thanks, > David Booth >
Attachments
- application/pgp-keys attachment: OpenPGP public key
Received on Friday, 26 January 2024 14:19:23 UTC