W3C home > Mailing lists > Public > public-rdf-wg@w3.org > July 2013

Review of RDF/JSON

From: Andy Seaborne <andy@apache.org>
Date: Mon, 01 Jul 2013 15:11:20 +0100
Message-ID: <51D18E08.4080105@apache.org>
To: RDF-WG <public-rdf-wg@w3.org>

== Process

Either clarify the meaning of "normative"/"non-normative" in a Note 
(maybe frame as "if this were a REC then ...") or remove.

== Overall

The spec only covers graphs, not RDF datasets.
This is probably not worth addressing.

== 5 Examples

Add the corresponding N-triples to the examples.

== 6 Acknowledgements

This is a copy from another document.

Replace with a credit to Talis.

The original work is:

There is a copy of that original in case docs.api.talis.com goes away:

== Appendix A

The Content type registration should be made less formal - it's not 
actually being registered (can't be, not a REC?).  I suggest a simple:

The suggested media type for RDF/JSON is "application/rdf+json".

It is suggested that RDF/JSON files have the extension ".rj" (all 
lowercase) on all platforms.

JSON is encoded in Unicode, with a default encoding of UTF-8.  See 
RFC627, section 3 "Encoding".

and remove everything else.

By the way: Appendix A:

The encoding considerations of the SPARQL Query Results JSON Format
This is not the SPARQL Query Results JSON Format!

== References

Fix RDF-CONCEPTS reference

Remove RFC3023 (used in appendix A)
Received on Monday, 1 July 2013 14:11:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:02:15 UTC