W3C home > Mailing lists > Public > semantic-web@w3.org > September 2007


From: Keith Alexander <k.j.w.alexander@gmail.com>
Date: Wed, 05 Sep 2007 18:04:48 +0100
To: "Richard Newman" <r.newman@reading.ac.uk>
Cc: semantic-web@w3.org
Message-ID: <op.tx6xqapn63ayaz@keith-alexanders-computer.local>

Hi Richard,

thanks for taking the time to respond.

>> The structure of an RDF/JSON document looks like this
>> {
> What about blank node subjects?

  Bnode IDs go here too (as you can see in the specification[1]).

> What is the value of "5"^^xsd:integer -- 5 or "5"?

The datatype is indicated by the datatype key, not by whether the value is  
quoted or not.

> What is the value of a blank node?

The blank node's id.

> Can you nest these structures?


> What do you do for non-ASCII strings?

JSON is encoded as UTF-8, not ASCII

> Linebreaks in strings?

Escape them as per JSON syntax with a backslash

> Do you handle named graphs?


> I would be unlikely to publish in this serialization: unlike other uses  
> of JSON, this one will only be of use to Javascript,

Actually, we are finding it pretty useful in PHP.

> where writing parsers for other languages is inconvenient. Everyone else  
> has Turtle.

Javascript has a Turtle parser too [2].

The motivation for this RDF/JSON format is not because there are not  
parsers for RDF/XML or Turtle, but merely to provide a way of serialising  
a useful default structure for RDF data.



[1] http://n2.talis.com/wiki/RDF_JSON_Specification
[2] http://www.kanzaki.com/works/2006/misc/0308turtle.html
Received on Wednesday, 5 September 2007 17:07:39 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:02 UTC