Added issue marker in authoring guidelines appendix that this should probably become a normative syntax specification, including EBNF. This relates to issue #135.
authorGregg Kellogg <gregg@kellogg-assoc.com>
Mon, 25 Jun 2012 11:24:57 -0700
changeset 757 a7008dce7c8e
parent 753 11dcd6b0cb8c
child 758 c632e5e5302e
Added issue marker in authoring guidelines appendix that this should probably become a normative syntax specification, including EBNF. This relates to issue #135.
spec/latest/json-ld-syntax/index.html
--- a/spec/latest/json-ld-syntax/index.html	Sun Jun 24 18:55:44 2012 -0700
+++ b/spec/latest/json-ld-syntax/index.html	Mon Jun 25 11:24:57 2012 -0700
@@ -2341,6 +2341,10 @@
 For the time being, a simple list of plain english guidelines are provided.
 </p>
 
+<p class="issue">Per
+  <a href="http://lists.w3.org/Archives/Public/public-rdf-wg/2012Jun/0111.html">Andy S's comment</a>,
+  consider making this a normative syntax definition along with EBNF.</p>
+
 <ol>
 <li>A JSON-LD document is composed of a single <tref>subject definition</tref> or an <tref>array</tref> of <tref title="subject definition">subject definitions</tref>.</li>
 <li>The value of <code>@id</code> MUST be a <tref>term</tref>, a <tref>compact IRI</tref>, or an <tref>IRI</tref>.</li>