W3C home > Mailing lists > Public > public-linked-json@w3.org > March 2013

RE: [json-ld.org] JSON-LD in HTML (#231)

From: Markus Lanthaler <markus.lanthaler@gmx.net>
Date: Fri, 22 Mar 2013 20:08:39 +0100
To: "'Ivan Herman'" <ivan@w3.org>
Cc: "'W3C RDF WG'" <public-rdf-wg@w3.org>, "'JSON-LD JSON'" <public-linked-json@w3.org>
Message-ID: <026e01ce2730$aa493140$fedb93c0$@lanthaler@gmx.net>
On Friday, March 22, 2013 5:09 PM, Ivan Herman wrote:

> > [[[
> > If a processor extracts the JSON-LD content into RDF, it should
> expand the
> > JSON-LD fragment into an RDF dataset using the algorithm defined in
> > JSON-LD-API Convert to RDF Algorithm [JSON-LD-API]. If the HTML file
> > contains multiple JSON-LD script tags, or other RDF statements are
> > extracted, the result is the RDF merge of the datasets.
> >
> > Other processors implementing this mechanism may choose to return the
> > expanded JSON-LD output.
> > ]]]
> >
> > I'm specifically worried about the second paragraph. This suggest (to
> me at
> > least), that other (?) processors should return expanded JSON-LD
> output
> > instead of returning it as is.
> Ah! Markus, you are right, I missed that stuff. In my view, processors
> return RDF. Full stop...

My rewording (see below) I intentionally didn't use the word processor. What
processor are you talking about? A JSON-LD processor? It wouldn't make much
sense IMHO to restrict a JSON-LD processor to just extract RDF. As I said,
what's done with the data is completely up to the application extracting it.
We can say that if RDF is desired the specified algorithm should be used,
but that's it IMO.

Defining how such data may be used is beyond the scope of this
specification. The embedded JSON-LD document might be extracted as is or
converted to RDF.

If JSON-LD content is extracted as RDF, it should be expanded into an RDF
dataset using the Convert to RDF Algorithm [JSON-LD-API]. If multiple
embedded JSON-LD documents are extracted as RDF, the result is the RDF merge
of the extracted datasets.


Markus Lanthaler
Received on Friday, 22 March 2013 19:09:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:53:21 UTC