--- a/spec/latest/json-ld-api/index.html	Tue Mar 26 18:30:46 2013 +0100
+++ b/spec/latest/json-ld-api/index.html	Tue Mar 26 18:57:59 2013 +0100
@@ -916,8 +916,13 @@
               <code class="error"><a href="#idl-def-JsonLdErrorCode.invalid-local-context">invalid local context</a></code>
               error has been detected and processing is aborted.</li>
             <li>If <i>context</i> has an <code>@base</code> key:
-              <p class="issue atrisk">This feature is at risk as the fact that a document may
-                have multiple base IRIs is potentially confusing for developers.</p>
+              <p class="issue atrisk" data-number="223" title="Feature at risk">This feature is
+                at risk as the fact that a document may have multiple base IRIs
+                is potentially confusing for developers. It is also being discussed whether
+                relative IRIs are allowed as values of <code>@base</code> or whether
+                the empty string should be used to explicitly specify that there isn't
+                a base IRI, which could be used to ensure that relative IRIs remain
+                relative when expanding.</p>
               <ol class="algorithm">
                 <li>Initialize <i>value</i> to the value associated with the
                   <code>@base</code> key.</li>

--- a/spec/latest/json-ld-syntax/index.html	Tue Mar 26 18:30:46 2013 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Tue Mar 26 18:57:59 2013 +0100
@@ -787,8 +787,12 @@
 <section>
   <h2>Base IRI</h2>
 
-  <p class="issue atrisk">This feature is at risk as the fact that a document may
-    have multiple base IRIs is potentially confusing for developers.</p>
+  <p class="issue atrisk" data-number="223" title="Feature at risk">This feature is
+    at risk as the fact that a document may have multiple base IRIs is potentially
+    confusing for developers. It is also being discussed whether relative IRIs
+    are allowed as values of <code>@base</code> or whether the empty string
+    should be used to explicitly specify that there isn't a base IRI, which
+    could be used to ensure that relative IRIs remain relative when expanding.</p>
 
   <p>JSON-LD allows <tref>IRI</tref>s to be specified in a relative form which is
     resolved against the document base according
@@ -3016,6 +3020,13 @@
   <p>If the <tref>context definition</tref> has a <code>@base</code> key,
     its value MUST be an <tref>absolute IRI</tref> or <tref>null</tref>.</p>
 
+  <p class="issue atrisk" data-number="223" title="Feature at risk">This feature is
+    at risk as the fact that a document may have multiple base IRIs is potentially
+    confusing for developers. It is also being discussed whether relative IRIs
+    are allowed as values of <code>@base</code> or whether the empty string
+    should be used to explicitly specify that there isn't a base IRI, which
+    could be used to ensure that relative IRIs remain relative when expanding.</p>
+
   <p>If the <tref>context definition</tref> has a <code>@vocab</code> key,
     its value MUST be a <tref>absolute IRI</tref>, a <tref>compact IRI</tref>,
     a <tref>term</tref>, or <tref>null</tref>.</p>