- From: Guus Schreiber <guus.schreiber@vu.nl>
- Date: Fri, 21 Feb 2014 13:35:57 +0100
- To: Markus Lanthaler <markus.lanthaler@gmx.net>, 'Public RDF comments list' <public-rdf-comments@w3.org>
- CC: 'Yves Raimond' <yves.raimond@bbc.co.uk>, 'RDF WG' <public-rdf-wg@w3.org>
Markus, Response to the JSON-LD comments. On 19-02-14 13:07, Markus Lanthaler wrote: [..] > Section 5.2 > "JSON-LD also provides a way to serialize RDF datasets through the use of the @graph keyword." -> can be removed, this is already clear from the very first sentence > "Each JSON object corresponds to an RDF resource" -> JSON object *in the example above* (this is not generally true) > I don't really like the keyword aliasing in the example, but if you alias it, please use "url" instead of "uri". Also, please include the full absolute IRIs instead of bob#me, alice#me, and wd:Q12418. Rename "born" to "birthdate", "friends" to "knows" and get rid of the array (also for interest) and type-coerce "creator" to @id as well. So, in the end, the example should look as follows > > 01 { > 02 "@context": "example-context.json", > 03 "url": "http://example.org/bob#me", > 04 "type": "Person", > 05 "birthdate": "1990-07-04", > 06 "knows": "http://example.org/alice#me", > 07 "interest": { > 08 "url": "http://www.wikidata.org/entity/Q12418", > 09 "title": "Mona Lisa", > 10 "subject_of": "http://data.europeana.eu/item/04802/243FA8618938F4117025F17A8B813C5F9AA4D619", > 11 "creator": "http://dbpedia.org/resource/Leonardo_da_Vinci" > 12 } > 13 } > > Unless someone thinks otherwise, I would prefer it this way though (to make it more recognizable as JSON-LD and to show the why there's a @type: @id in the context; keyword aliasing is really an advanced feature IMO): > > 01 { > 02 "@context": "example-context.json", > 03 "@id": "http://example.org/bob#me", > 04 "@type": "Person", > 05 "birthdate": "1990-07-04", > 06 "knows": "http://example.org/alice#me", > 07 "interest": { > 08 "@id": "http://www.wikidata.org/entity/Q12418", > 09 "title": "Mona Lisa", > 10 "subject_of": "http://data.europeana.eu/item/04802/243FA8618938F4117025F17A8B813C5F9AA4D619", > 11 "creator": "http://dbpedia.org/resource/Leonardo_da_Vinci" > 12 } > 13 } OK, this example is indeed better. Will change accordingly, with explanatory text > > "The @context key on line 2 points to a JSON document" -> to a *JSON-LD context document* > > Since the context is so crucial for all of this, I think it is important to include it directly in this section. It would also be good to mention that it can be directly embedded into the document instead. > Here's an optimized version of the context (without the keyword aliases) > > 01 { > 02 "@context": { > 03 "foaf": "http://xmlns.com/foaf/0.1/", > 04 "Person": "foaf:Person", > 05 "interest": "foaf:topic_interest", > 06 "knows": { > 07 "@id": "foaf:knows", > 08 "@type": "@id" > 09 }, > 10 "birthdate": { > 11 "@id": "http://schema.org/birthDate", > 12 "@type": "http://www.w3.org/2001/XMLSchema#date" > 13 }, > 14 "dcterms": "http://purl.org/dc/terms/", > 15 "title": "dcterms:title", > 16 "creator": "dcterms:creator", > 17 "subject_of": { > 18 "@reverse": "dcterms:subject", > 19 "@type": "@id" > 20 } > 21 } > 22 } Yves and I can live with including the context in Sec. 5.2 and deleting the appendix. Changed accordingly. To prevent people having to read through a very long Sec. 5 (which is a long-standing worry from me, as you know) I have added a reading tip to the start of the section: [[ Tip: we suggest to read Sec. 5.1 on the Turtle-related syntaxes and to read the sections on JSON-LD, RDFa and RDF/XML only when you are interested in that particular usage of RDF. ]] Se the new version [1]. Thanks again, Guus [1] https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-primer/index.html# [..]
Received on Friday, 21 February 2014 12:36:27 UTC