From 524a524a02cf87f251ce96aa87e02201cb0c307d Mon Sep 17 00:00:00 2001 From: Pierre-Antoine Champin Date: Wed, 9 Jun 2021 12:40:42 +0200 Subject: [PATCH] add issue #170 in vocabulary section as per the resolution at https://w3c.github.io/rdf-star/Minutes/2021-06-04.html#r02 --- cg-spec/editors_draft.html | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/cg-spec/editors_draft.html b/cg-spec/editors_draft.html index 63490acd..fa5f97bd 100644 --- a/cg-spec/editors_draft.html +++ b/cg-spec/editors_draft.html @@ -2659,7 +2659,7 @@

Other uses of the unstar mapping

-
+

Referential opacity

The way the unstar mapping is defined, the denotation of an embedded triple does not only depend on the denotation of its component terms, but also on their syntactical form (for IRIs and literals). This behavior is referred to as referential opacity. A consequence is that two different triples, that would be semantically equivalent if asserted, are not automatically considered to denote the same thing when embedded. In the example below, assuming D-entailment: while `"42"^^xsd:integer` and `"042"^^xsd:integer` denote the same thing (namely, the number 42), the two embedded triples are allowed to have different denotations, and so the entailment does not hold.

@@ -2790,6 +2790,10 @@

RDF-star vocabulary

This issue was raised to introduce IRIs to be used with [[SPARQL11-SERVICE-DESCRIPTION]], in order for a SPARQL-star endpoint to advertise its support for RDF-star. +
+ This issue proposes to introduce a vocabulary for locally overriding the opaque semantics of embedded triples, making them transparent in some contexts. +
+