Add issue marker for @base: null
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Tue, 20 Aug 2013 22:47:27 +0200
changeset 1906 7d043b618c45
parent 1905 a642f159fc3e
child 1907 cbfd79099c7d
Add issue marker for @base: null

This addresses #223
spec/latest/json-ld-api/index.html
spec/latest/json-ld/index.html
--- a/spec/latest/json-ld-api/index.html	Tue Aug 20 22:34:34 2013 +0200
+++ b/spec/latest/json-ld-api/index.html	Tue Aug 20 22:47:27 2013 +0200
@@ -929,6 +929,23 @@
         If <i>remote contexts</i> is not passed, it is initialized to an empty
         <tref>array</tref>.</p>
 
+      <div class="issue atrisk" data-number="10" title="Support for @base: null ">
+        <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
+          <a href="mailto:[email protected]">[email protected]</a>.
+          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>Unlike many other serialization formats, JSON-LD allows to specify that
+        there is no base IRI from within the document (by setting <code>@base</code> to
+        <tref>null</tref>). The result is that the algorithm for establishing a base IRI
+        as specified in <a href="http://tools.ietf.org/html/rfc3986#section-5.1">RFC3986 section 5.1</a>
+        is overridden so relative IRIs remain relative IRIs even in the case that an IRI
+        would be available in one of the outer layers (e.g., the IRI used to retrieve
+        the document or an application supplied base IRI). Based on implementer feedback,
+        the Working Group may decide to remove this feature from JSON-LD 1.0.</p>
+      </div>
+
       <ol class="algorithm">
         <li>Initialize <i>result</i> to the result of cloning
           <tref>active context</tref>.</li>
--- a/spec/latest/json-ld/index.html	Tue Aug 20 22:34:34 2013 +0200
+++ b/spec/latest/json-ld/index.html	Tue Aug 20 22:47:27 2013 +0200
@@ -957,7 +957,25 @@
     <tref title="relative IRI">relative IRIs</tref> to be expanded to
     <tref title="absolute IRI">absolute IRIs</tref>.</p>
 
-  <p>Please note that the <code>@base</code> will be ignored if used in external contexts.</p>
+  <div class="issue atrisk" data-number="10" title="Support for @base: null ">
+    <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
+      <a href="mailto:[email protected]">[email protected]</a>.
+      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>Unlike many other serialization formats, JSON-LD allows to specify that
+    there is no base IRI from within the document (by setting <code>@base</code> to
+    <tref>null</tref>). The result is that the algorithm for establishing a base IRI
+    as specified in <a href="http://tools.ietf.org/html/rfc3986#section-5.1">RFC3986 section 5.1</a>
+    is overridden so relative IRIs remain relative IRIs even in the case that an IRI
+    would be available in one of the outer layers (e.g., the IRI used to retrieve
+    the document or an application supplied base IRI). Based on implementer feedback,
+    the Working Group may decide to remove this feature from JSON-LD 1.0.</p>
+  </div>
+
+  <p>Please note that the <code>@base</code> will be ignored if used in
+    external contexts.</p>
 </section>
 
 <section class="informative">