Re: Consolidating triple/edges

> On 14. Dec 2023, at 19:21, Andy Seaborne <andy@apache.org> wrote:
> 
> 
> 
> On 14/12/2023 16:46, Thomas Lörtsch wrote:
>> ## Unasserted vs Asserted
> 
> Just on this part:
> 
>> Why not define a property that not only references a token, but also creates the triple, e.g.:
>>    :liz :spouse :dick [id:1]{| :start 1964; :end 1974 |} .
>> mapping to
>>     id:1 rdfx:assertionOf << :liz :spouse :dick >>
>>         :start 1964; :end 1974 .
>> instead of
>>     id:1 rdfx:occurrenceOf << :liz :spouse :dick >>
>>         :start 1964; :end 1974 .
>>     :liz :spouse :dick .
> 
> Yes - that is the meaning of {| |}
> 
> Starting at:
>>> which would map to
>>>    id:1 rdfx:occurrenceOf << :liz :spouse :dick >> ;
>>>         :start 1964; :end 1974 .
>>> 
>>>    id:2 rdfx:occurrenceOf << :liz :spouse :dick >> ;
>>>         :start 1975; :end 1976 .
> 
> I added the
> 
>> and asserting:
>>   :liz :spouse :dick .

A misunderstanding: I’m proposing that the triple ':liz :spouse :dick .' doesn’t have to be added to be asserted. Instead the property rdfx:assertionOf asserts it, like owl:imports asserts a referenced ontology in the importing graph.

Because the property asserts the statement and adds an identifier to that occurrence it is possible to know exactly to which occurrence an annotation belongs (also if it is actually intended to be asserted or not, because if not, use another property like e.g. rdfx:quotes).


> because it wasn't in the description that started this:
> https://lists.w3.org/Archives/Public/public-rdf-star-wg/2023Dec/0024.html
> 
> As the original CG annotation syntax did assert, I assumed it was implied to happen as well.
> 
>    Andy
>

Received on Thursday, 14 December 2023 19:46:40 UTC