- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Wed, 30 Oct 2013 13:58:38 +0100
- To: "'Matt Wuerstl'" <mwuerstl@4qbase.com>
- Cc: <public-rdf-comments@w3.org>
Hi Matt, Thank you for your feedback on the JSON-LD specifications. This is an official response to RDF-ISSUE-168: blogPost vs. post, which is being tracked here: https://www.w3.org/2011/rdf-wg/track/issues/168 You had previously reported an issue with the description of example 54 in the JSON-LD specification. Specifically, you mentioned that use of "blogPost" in the explanation was wrong and that "post" should be used instead. This is correct and has been fixed in the following commit: https://github.com/json-ld/json-ld.org/commit/73c87b1816eee2617d8cad333fe4be 479b58c5a6 We believe that this addresses the issue that you reported. Please respond as soon as possible to this email to tell us whether or not you are satisfied with the fix. Thanks, Markus -- Markus Lanthaler @markuslanthaler -------------- Original Message ------------------ From: Matt Wuerstl Sent: Monday, October 28, 2013 10:40 PM To: public-rdf-comments@w3.org Subject: JSON-LD spec question In section 6.16 Data Indexing of the latest JSON-LD spec an example of data indexing is given that is confusing. In Example 54, the term “post” is defined as: "post": { "@id": "schema:blogPost", "@container": "@index" } And then the subsequent descriptive text refers to the “blogPost” term: In the example above, the blogPost term has been marked as an index map. The en, de, and ja keys will be ignored semantically, but preserved syntactically, by the JSON-LD Processor. This allows a developer to access the German version of the blogPost using the following code snippet: obj.blogPost.de. Shouldn’t this text be referencing the “post” term as it was defined in the context? And referenced in code as org.post.de? Thanks for the clarification. Regards, Matt
Received on Wednesday, 30 October 2013 12:59:16 UTC