- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Wed, 23 Mar 2011 21:59:53 +0000
- To: David Wood <david.wood@talis.com>
- CC: Sandro Hawke <sandro@w3.org>, Manu Sporny <msporny@digitalbazaar.com>, RDF WG <public-rdf-wg@w3.org>
On 23/03/11 20:48, David Wood wrote: > > On Mar 23, 2011, at 13:24, Sandro Hawke wrote: > >> Instead, I think the advantages of RDF show up on a different set of a >> problems. They show up mostly when you need to merge data from multiple >> independent sources. Once people see that working, they'll see plenty >> of reasons to use RDF. > > > Right. So that suggests that we focus our RDF-in-JSON efforts toward use cases where data is to be merged. > > We want a JSON format that allows RDF-in-JSON to be merged with other RDF-in-JSON files. > > Is that captured in any of the existing use cases? Do others disagree with this? Agree - add the key benefits of linking and merging Disagree about "RDF-in-JSON" We want a JSON format that allows RDF to be merged with other RDF files. 1/ Merging may not be done in JS app 2/ Don't want a subset of RDF so a subset of RDF ecosystem arises Andy > Regards, > Dave
Received on Wednesday, 23 March 2011 22:00:31 UTC