- From: Andy Seaborne <andy@apache.org>
- Date: Mon, 01 Jul 2013 15:11:20 +0100
- To: RDF-WG <public-rdf-wg@w3.org>
http://www.w3.org/2013/meeting/rdf-wg/2013-06-26#RDF__2f_JSON_as_Note == 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: http://docs.api.talis.com/platform-api/output-types/rdf-json There is a copy of that original in case docs.api.talis.com goes away: http://jena.apache.org/documentation/io/rdf-json.html == 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