W3C home > Mailing lists > Public > public-rdf-star@w3.org > February 2021

Re: Why nested triples?

From: Ghislain ATEMEZING <ghislain.atemezing@gmail.com>
Date: Fri, 19 Feb 2021 13:15:57 +0100
Message-ID: <CA+Ogc+eHDH-8WYrVkrGBLOPWd1uDTzZnk9E153tsx_QT5B0dkA@mail.gmail.com>
To: Pierre-Antoine Champin <pierre-antoine.champin@ercim.eu>
Cc: Antoine Zimmermann <antoine.zimmermann@emse.fr>, "public-rdf-star@w3.org" <public-rdf-star@w3.org>
Hello,
In GraphDB (v 9.4.0), I've just seen that you can add in .ttls something
like this:

<< <<mdk:person1 rdf:type foaf:Person>> dcterms:created
"2020-11-03"^^xsd:date >> prov-o:wasGeneratedBy << <<mdk:person1
foaf:birthPlace dbpedia:Paris>> dcterms:creator mdu:admin >> .

HTH
Ghislain

On Thu, Feb 18, 2021 at 4:55 PM Pierre-Antoine Champin <
pierre-antoine.champin@ercim.eu> wrote:

>
> On 18/02/2021 15:02, Antoine Zimmermann wrote:
> > (...)
> >
> > However, I have seen discussions that may serve as counter arguments:
> > when asked why embedded triples are limited to single triples rather
> > than sets of triples, it has been answered that RDF* is used to model
> > property-graph-like annotations that only concern one edge at a time.
> > In this case, nested triples should not be allowed, using the same
> > arguments (as far as I know, it is not possible to nest
> > edge-annotations in property graph systems).
> I don't have any reference handy (sorry), but I have been told that some
> property-graph systems have a notion of meta-property, which could
> justify at least a 2nd level of nesting.
>
>

-- 

"*Love all, trust a few, do wrong to none*" (W. Shakespeare)
Web: http://atemezing.org
Received on Friday, 19 February 2021 12:16:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 19 February 2021 12:16:25 UTC