Clarify that the profile parameter keeps URIs and not IRIs
authorMarkus Lanthaler <>
Tue, 09 Apr 2013 18:28:47 +0200
changeset 1572 42e6e35c4a8e
parent 1571 2d46b94af937
child 1573 83da380c21a7
Clarify that the profile parameter keeps URIs and not IRIs

IRIs can contain spaces, double quotes and other stuff which would need to be encoded.
--- a/spec/latest/json-ld/index.html	Tue Apr 09 11:49:05 2013 -0400
+++ b/spec/latest/json-ld/index.html	Tue Apr 09 18:28:47 2013 +0200
@@ -3634,7 +3634,7 @@
-          <p>A a non-empty list of space-separated URI-encoded URIs identifying specific
+          <p>A a non-empty list of space-separated URIs identifying specific
             constraints or conventions that apply to a JSON-LD document according [[RFC6906]].
             A profile does not change the semantics of the resource representation
             when processed without profile knowledge, so that clients both with
@@ -3655,8 +3655,10 @@
             parameter has to be enclosed in quotes (<code>"</code>) because it contains
             special characters and, if multiple profiles are combined, whitespace.</p>
           <p>When processing the "profile" media type parameter, it is important to
-            apply URI-decoding before processing the URI (such as comparing it to
-            known profiles).
+            note that its value is contains one or more URIs and not IRIs. In some cases
+            it might therefore be necessary to convert between IRIs and URIs as specified in
+            <cite><a href="">section 3 Relationship between IRIs and URIs</a></cite>
+            of [[RFC3987]].</p>