- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Thu, 01 Sep 2011 08:27:33 +0100
- To: public-linked-json@w3.org
On 01/09/11 06:02, Manu Sporny wrote: > On 08/31/2011 06:23 PM, Danny Ayers wrote: >> So essentially this is a transformation language & engine. Doesn't >> the fact that this level of engineering is needed suggest that the >> input format is too complex? > > You could look at the framing feature as a transformation language > and an algorithm, yes. > > It's not the input format (JSON-LD) that is complex - it's graphs. > Getting a regular structure out of a graph is a /very hard problem/. This is a strange statement - the framing example shows that the result is that to access the chapter title, you have to know, library->book->chapter->title. You can't just get the chapter title from a book without going through the whole library; books not in libraries don't exist. Graphs work named/indexed access, not by rooted traversal. That's the tradeoff being made - JSON-LD will give a way to publish specific data items as JSON and have a well-defined associated RDF triples. Great - tick. It's not a way to aggregate data from the web but that isn't the intention, Andy
Received on Thursday, 1 September 2011 07:28:13 UTC