Update description of "Feature at Risk 3": blank node graph names are now allowed in RDF
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Tue, 09 Jul 2013 22:18:25 +0200
changeset 1758 1eddcdaa5bc4
parent 1757 414d758240a5
child 1759 63805798e5cf
Update description of "Feature at Risk 3": blank node graph names are now allowed in RDF

... the syntax spec has already been updated.
spec/latest/json-ld-api/index.html
--- a/spec/latest/json-ld-api/index.html	Tue Jul 09 22:15:18 2013 +0200
+++ b/spec/latest/json-ld-api/index.html	Tue Jul 09 22:18:25 2013 +0200
@@ -3127,7 +3127,7 @@
       <cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
       of [[RDF11-CONCEPTS]].</p>
 
-    <div class="issue atrisk" data-number="3" title="Allow blank nodes to be used as graph name or property">
+    <div class="issue atrisk" data-number="3" title="Allow blank nodes to be used as properties">
       <p class="atrisk-head">Note: This feature is
         <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and
         may be removed from this specification based on feedback. Please send feedback to
@@ -3135,7 +3135,7 @@
         For the current status see
         <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
       <p>RDF does not currently allow a <tref>blank node</tref> to be
-        used as <tref>graph name</tref> or <tref>property</tref>, while JSON-LD
+        used as <tref>property</tref>, while JSON-LD
         does. <tref title="JSON-LD-RDF Converter">JSON-LD-RDF Converters</tref>
         can work around this restriction, when converting JSON-LD to RDF, by
         converting such <tref title="blank node">blank nodes</tref> to