W3C home > Mailing lists > Public > public-rdf-wg@w3.org > March 2011

[JSON] Reviewing RDF in JSON specs

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Wed, 09 Mar 2011 15:34:02 -0500
Message-ID: <4D77E43A.4000001@digitalbazaar.com>
To: RDF WG <public-rdf-wg@w3.org>
After re-reading the feedback comments on the RDF in JSON Design
Requirements, it seems as if there are a number of misunderstandings
about what is possible in an RDF in JSON format:

http://www.w3.org/2011/rdf-wg/wiki/TF-JSON#RDF_in_JSON_Design_Requirements

"Time permitting, not a top priority"
"nice to have but should not consume this team's resources"
"Seems out-of-scope; do existing RDF-in-JSON solutions already have such
mechanisms?"
"time permitting"
"highly desirable if there's time"
etc.

You could read this feedback in two ways. The first is that it takes
time to come to consensus on each feature and we may need to cut the
feature because we can't come to consensus on it - that response is
perfectly valid. The second assumes that there is no working technical
solution and that the group will have to solve the technical problem
first and then come to consensus on the feature - I don't think this
response is valid.

I was careful to not write design requirements for features that did not
have at least one implemented solution. None of the design requirements
are proposing features that are not implemented in at least one of the
proposed RDF in JSON serialization formats. That is, if you think that
there is a major/untested/unimplemented technical hurdle or challenge to
one of the design requirements, you may want to read through the
serialization proposals.

I think we're getting to the point where some of us may argue vehemently
for or against a particular feature under the false premise that no
technical solution exists. This may send us down a rat hole and will
most likely waste precious telecon time. If you are not familiar with
all of the JSON serialization formats and are going to participate in
the discussion, please make sure that you have a handle on most of the
features that are provided by each serialization format:

http://www.w3.org/2011/rdf-wg/wiki/TF-JSON#Inputs

If you only have limited time, I believe just looking at the following 4
documents will be sufficient to understand the scope of the features
provided by the various serialization formats.

JSON-LD : http://json-ld.org/spec/ED/20110201/
RDF/JSON: http://n2.talis.com/wiki/RDF_JSON_Specification
JSN3    : http://webr3.org/apps/specs/jsn3/
JTriples: http://www.w3.org/wiki/JTriples

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: Payment Standards and Competition
http://digitalbazaar.com/2011/02/28/payment-standards/
Received on Wednesday, 9 March 2011 20:34:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:04:04 UTC