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

Re: [JSON] Survey for design requirements

From: Richard Cyganiak <richard@cyganiak.de>
Date: Mon, 7 Mar 2011 10:19:32 +0000
Cc: RDF Working Group <public-rdf-wg@w3.org>
Message-Id: <A72C1B21-7264-4A53-A346-7A1CE396F37F@cyganiak.de>
To: Manu Sporny <msporny@digitalbazaar.com>
Hi Manu,

On 7 Mar 2011, at 04:45, Manu Sporny wrote:
> http://www.w3.org/2011/rdf-wg/wiki/TF-JSON#RDF_in_JSON_Use_Cases

Thanks, this is very helpful!

I renamed two of the use cases to hopefully better highlight their differences. Also added more text to Andy's.

I wasn't quite able to make sense of this one:
http://www.w3.org/2011/rdf-wg/wiki/TF-JSON#RDF_REST_Web_Services

The web services that Frank is using. Do they already provide RDF, or just plain old JSON? If we assume that the operators of the web service already adopted some sort of JSON+RDF technology, then that would better be a separate use case, written from their POV. If we assume that these web services are just plain JSON at the moment, then I'd like to understand why Frank doesn't simply stick with doing everything in JSON. Why does he want to “add semantics to the data”, and what does that mean?

Thanks,
Richard



> 
> Anyone that is interested should feel free to add their use cases to the
> use cases section of the wiki linked to above.
> 
> -- manu
> 
> -- 
> Manu Sporny (skype: msporny, twitter: manusporny)
> President/CEO - Digital Bazaar, Inc.
> blog: Towards Universal Web Commerce
> http://digitalbazaar.com/2011/01/31/web-commerce/
> 
Received on Monday, 7 March 2011 10:21:14 UTC

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