W3C home > Mailing lists > Public > public-rdf-comments@w3.org > May 2012

Re: JSON-LD Syntax request for FPWD via RDF WG

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Wed, 23 May 2012 21:14:58 -0400
Message-ID: <4FBD8B92.8090400@digitalbazaar.com>
To: RDF Comments <public-rdf-comments@w3.org>
CC: 'Linked JSON' <public-linked-json@w3.org>
On 05/23/2012 07:39 AM, Richard Cyganiak wrote:
> As I've said before: The JSON-LD syntax spec doesn't explain how to
> serialize an RDF graph to JSON-LD or how to parse a JSON-LD document
> to an RDF graph. This may or may not be appropriate given the
> intended audience.

It's not appropriate for the intended audience. The JSON-LD API is the
intended audience for the toRDF/fromRDF algorithm.

> But I don't really see how RDF-WG could publish an FPWD that isn't
> formally connected to RDF in any way.

What's the goal here? Why does the connection need to be /formal/? We
say this in the spec:

JSON-LD is a specification for representing Linked Data in JSON. A
common way of working with Linked Data is through RDF, the Resource
Description Framework. RDF can be expressed using JSON-LD by associating
JSON-LD concepts such as @id and @type with the equivalent IRIs in RDF.
Further information about RDF may be found in the [RDF-PRIMER].

Would modifying this statement to make it abundantly clear that all of
RDF can be represented in JSON-LD help? We also show a number of
examples in TURTLE and their equivalent in JSON-LD:


We say this in the section titled "Identifying the Subject":

The subject is the first piece of information needed by the JSON-LD
processor in order to create the (subject, property, object) tuple, also
known as a triple.

Could you answer these questions, it would help me understand where
you're coming from:

1. What is the goal with making a "formal" connection to RDF?
2. What would a "formal" connection to RDF look like?
3. Where does it state that a "formal" connection to RDF is a
    requirement for publishing a document via RDF WG? Why isn't a
    number of examples and language making it clear that JSON-LD
    can represent RDF enough?

> Elsewhere in this thread, Gregg has proposed what I thought was a
> reasonable and workable approach to that problem. What you say below
> seems to disagree with Gregg.

Wow... I'm missing that entire thread because I'm not subscribed to
public-rdf-comments. I'll go read that now.

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
Founder/CEO - Digital Bazaar, Inc.
blog: PaySwarm Website for Developers Launched
Received on Thursday, 24 May 2012 01:15:30 UTC

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