W3C home > Mailing lists > Public > public-rdf-star@w3.org > November 2020

Re: owl:sameAs/referential opacity Re: Can RDFstar be defined as only syntactic sugar on top of RDF (Re: weakness of embedded triples)

From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
Date: Tue, 17 Nov 2020 18:02:53 -0500
To: public-rdf-star@w3.org
Message-ID: <9c2481df-d2ab-d650-7c93-b616303dc1ff@gmail.com>
As far as I know "triple token" is not part of RDF* so determining what is
being argued about here is difficult.


peter


On 11/17/20 5:18 PM, thomas lörtsch wrote:
> Just a quick check:
>
>> On 17. Nov 2020, at 18:11, Pierre-Antoine Champin <pierre-antoine.champin@ercim.eu> wrote:
> […]
>
>>> +
>>>
>>> Both "modes" used side by side would solve this problem:
>>>
>>> 	<< :a :b :c >> :denies :d .
>>> 	:a :b :c {| :exclaims :e |}
>>>
>> No, because his concrete syntax would produce exactly the same abstract syntax as your previous example -- at least in my understanding, but I trust that Olaf would agree (see https://github.com/w3c/rdf-star/issues/9#issuecomment-708608422).
>>
>> From the very beginning, embedded triples in RDF* are totally identified by their subject+predicate+object, there is now way to distinguish different mentions (tokens) of the same triple.
> You mean
>>> 	:a :b :c {| :d :e |}
> is meant to annotate all triple tokens of type
> 	:a :b :c .
> everywhere, anywhere?
>
>> As I understand, this was a deliberate design choice.
> And with what rationale?
>
>
> Thomas
Received on Tuesday, 17 November 2020 23:03:13 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 17 November 2020 23:03:16 UTC