W3C home > Mailing lists > Public > public-linked-json@w3.org > January 2012

Provenance in JSON-LD

From: Alexandre Passant <alex@seevl.net>
Date: Tue, 17 Jan 2012 02:58:09 +0000
Message-ID: <CALF6uCnmiG6_pcEjzr-Rioc5oDJaBjk3pWbcqOPC_wjskPevpw@mail.gmail.com>
To: public-linked-json@w3.org
Hi,

I'm trying to imagine how to add (basic) provenance information in
JSON-LD. The use-case is on re-distribution of existing data, in order
to indicate when it has been fetched, from which website, etc.

I'm thinking of a @graph keyword:

"age": {
    "@value": "31",
    "@type": "http://www.w3.org/2001/XMLSchema#integer",
    "@graph" : [{
        "@id" : "http://example.org/foaf",
        "created" : "2012-01-17",
   }, {
        "@id" : "http://dbpedia.org/data/JohnDoe",
        "created" : "2012-01-11",
   }
}

This would create (using TRIX):

## Graph 1
<http://example.org/foaf> { :ex :age "31 }
## Graph 2
<http://dbpedia.org/data/JohnDoe> { :ex :age "31 }
## Graph metadata
: {
<http://dbpedia.org/data/JohnDoe> created "2012-01-11" .
<http://example.org/foaf> created "2012-01-17" .
}

I know that the graph issue is still under consideration by the RDF
WG, so this output may change. Yet, I think the requirement is strong
enough to address it. Opinions ?

BTW, is there currently a way in JSON-LD to define extensions ? So
that, I could define my own semantics of @graph (that some JSON-LD
parser may or may not understand) but this document would still be
compliant with the main JSON-LD spec. Or a way to ignore some keywords
in the parser (via @context) so that I can produce such document but
still be valid.

Best,

Alex.

-- 
Dr. Alexandre Passant - @terraces
Founder, CEO - http://seevl.net - @seevl
http://facebook.com/seevl.net - http://angel.co/seevl
Received on Tuesday, 17 January 2012 02:58:39 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:36 GMT