Clarify, that when expanding an IRI, if suffix starts with // it can't be a CURIE.
authorGregg Kellogg <gregg@kellogg-assoc.com>
Thu, 19 Apr 2012 17:57:58 -0700
changeset 544 d78f856fffca
parent 543 22e0f5af3f54
child 545 0a13b196ea64
Clarify, that when expanding an IRI, if suffix starts with // it can't be a CURIE.
spec/latest/json-ld-api/index.html
--- a/spec/latest/json-ld-api/index.html	Thu Apr 19 16:53:28 2012 -0700
+++ b/spec/latest/json-ld-api/index.html	Thu Apr 19 17:57:58 2012 -0700
@@ -1086,7 +1086,9 @@
       <li>Otherwise, split the value into a <em>prefix</em> and <em>suffix</em> from the first occurrence of ':'.</li>
       <li>If the prefix is a '_' (underscore), the value represents a named <tref>blank node</tref>.</li>
       <li>If the <tref>active context</tref> contains a <tref>term</tref> mapping for <em>prefix</em> using
-        a case-sensitive comparison, generate an <tref>IRI</tref>
+        a case-sensitive comparison, and <em>suffix</em> does not does not begin with '//'
+        (i.e., it does not match a <em>hier-part</em> including
+        <em>authority</em> (as defined in [[!RFC3986]]), generate an <tref>IRI</tref>
         by prepending the mapped prefix to the (possibly empty) suffix using textual concatenation. Note that an empty
         suffix and no suffix (meaning the value contains no ':' string at all) are treated equivalently.</li>
       <li>Otherwise, use the value directly as an IRI.</li>