change all mentions of URIs to IRIs

Author: mr-c

draft-4/Process.yml

@@ -67,10 +67,10 @@ $graph:
     - name: location
       type: string?
       doc: |
-        A URI that identifies the file resource.  This may be a relative
-        reference, in which case it must be resolved using the base URI of the
+        An IRI that identifies the file resource.  This may be a relative
+        reference, in which case it must be resolved using the base IRI of the
         document.  The location may refer to a local or remote resource; the
-        implementation must use the URI to retrieve file content.  If an
+        implementation must use the IRI to retrieve file content.  If an
         implementation is unable to retrieve the file content stored at a
         remote resource (due to unsupported protocol, access denied, or other
         issue) it must signal an error.
@@ -175,7 +175,7 @@ $graph:
         _type: "@id"
         identity: true
       doc: |
-        The format of the file.  This must be a URI of a concept node that
+        The format of the file.  This must be a IRI of a concept node that
         represents the file format, preferrably defined within an ontology.
         If no ontology is available, file formats may be tested by exact match.
 
@@ -223,11 +223,11 @@ $graph:
     - name: location
       type: string?
       doc: |
-        A URI that identifies the directory resource.  This may be a relative
-        reference, in which case it must be resolved using the base URI of the
+        An IRI that identifies the directory resource.  This may be a relative
+        reference, in which case it must be resolved using the base IRI of the
         document.  The location may refer to a local or remote resource.  If
         the `listing` field is not set, the implementation must use the
-        location URI to retrieve directory listing.  If an implementation is
+        location IRI to retrieve directory listing.  If an implementation is
         unable to retrieve the directory listing stored at a remote resource (due to
         unsupported protocol, access denied, or other issue) it must signal an
         error.
@@ -349,7 +349,7 @@ $graph:
       doc: |
         Only valid when `type: File` or is an array of `items: File`.
 
-        For input parameters, this must be one or more URIs of a concept nodes
+        For input parameters, this must be one or more IRIs of a concept nodes
         that represents file formats which are allowed as input to this
         parameter, preferrably defined within an ontology.  If no ontology is
         available, file formats may be tested by exact match.
@@ -715,7 +715,7 @@ $graph:
   doc: |
     This field consists of an array of type definitions which must be used when
     interpreting the `inputs` and `outputs` fields.  When a `type` field
-    contain a URI, the implementation must check if the type is defined in
+    contain a IRI, the implementation must check if the type is defined in
     `schemaDefs` and use that definition.  If the type is not found in
     `schemaDefs`, it is an error.  The entries in `schemaDefs` must be
     processed in the order listed such that later schema definitions may refer

draft-4/concepts.md

@@ -10,6 +10,9 @@
 
 **Uniform Resource Identifier (URI) Generic Syntax**: https://tools.ietf.org/html/rfc3986)
 
+**Internationalized Resource Identifiers (IRIs)**:
+https://tools.ietf.org/html/rfc3987
+
 **Portable Operating System Interface (POSIX.1-2008)**: http://pubs.opengroup.org/onlinepubs/9699919799/
 
 **Resource Description Framework (RDF)**: http://www.w3.org/RDF/
@@ -376,7 +379,7 @@ platform's CWL implementation.
 
 A CWL input object document may similarly begin with `#!/usr/bin/env
 cwl-runner` and be marked as executable.  In this case, the input object
-must include the field `cwl:tool` supplying a URI to the default CWL
+must include the field `cwl:tool` supplying a IRI to the default CWL
 document that should be executed using the fields of the input object as
 input parameters.