LNK-243: Make it clear that URIs are actually IRIs

.github/workflows/main.yaml

@@ -42,13 +42,13 @@ jobs:
           git remote add upstream https://github.com/linkml/linkml-model
           git fetch upstream --tags
       - name: Validate all metamodel files
-        uses: NeverBlink-OSS/linkml-scala-action@v0.17.1
+        uses: NeverBlink-OSS/linkml-scala-action@v0.17.2
         with:
           working-directory: linkml_model/model/schema
           files: "*.yaml"
           import-map: "import_map.json"
       - name: Lint the main metamodel file
-        uses: NeverBlink-OSS/linkml-scala-action@v0.17.1
+        uses: NeverBlink-OSS/linkml-scala-action@v0.17.2
         with:
           working-directory: linkml_model/model/schema
           files: "meta.yaml"

linkml_model/model/schema/meta.yaml

@@ -238,9 +238,10 @@ slots:
     rank: 99
     domain: element
     description: >-
-      The native URI of the element. This is always within the namespace of the containing schema.
-      Contrast with the assigned URI, via class_uri or slot_uri
+      The native IRI (URI) of the element. This is always within the namespace of the containing schema.
+      Contrast with the assigned IRI, via class_uri or slot_uri
     comments:
+      - IRIs are allowed, name is kept for backwards compatibility.
       - Formed by combining the default_prefix with the normalized element name
     range: uriorcurie
     readonly: filled in by the schema loader or schema view
@@ -708,7 +709,9 @@ slots:
       - public ID
     domain: enum_definition
     range: uriorcurie
-    description: URI of the enum that provides a semantic interpretation of the element in a linked data context. The URI may come from any namespace and may be shared between schemas
+    description: IRI (URI) of the enum that provides a semantic interpretation of the element in a linked data context. The IRI may come from any namespace and may be shared between schemas
+    comments:
+      - IRIs are allowed, name is kept for backwards compatibility.
     ifabsent: class_curie
     in_subset:
       - SpecificationSubset
@@ -1324,8 +1327,9 @@ slots:
     domain: class_definition
     range: uriorcurie
     description: >-
-      URI of the class that provides a semantic interpretation of the element in a linked data context. The URI may come from any namespace and may be shared between schemas
+      IRI (URI) of the class that provides a semantic interpretation of the element in a linked data context. The IRI may come from any namespace and may be shared between schemas
     comments:
+      - IRIs are allowed, name is kept for backwards compatibility.
       - Assigning class_uris can provide additional hooks for interoperation, indicating a common conceptual model
     ifabsent: class_curie
     in_subset:
@@ -1565,8 +1569,9 @@ slots:
     range: uriorcurie
     ifabsent: slot_curie
     description: >-
-      URI of the class that provides a semantic interpretation of the slot in a linked data context. The URI may come from any namespace and may be shared between schemas.
+      IRI (URI) of the class that provides a semantic interpretation of the slot in a linked data context. The IRI may come from any namespace and may be shared between schemas.
     comments:
+      - IRIs are allowed, name is kept for backwards compatibility.
       - Assigning slot_uris can provide additional hooks for interoperation, indicating a common conceptual model
       - To use a URI or CURIE as a range, create a class with the URI or CURIE as the class_uri
     in_subset:
@@ -2430,8 +2435,9 @@ slots:
     range: uriorcurie
     alias: uri
     inherited: true
-    description: The uri that defines the possible values for the type definition
+    description: The IRI (URI) that defines the possible values for the type definition
     comments:
+      - IRIs are allowed, name is kept for backwards compatibility.
       - uri is typically drawn from the set of URI's defined in OWL (https://www.w3.org/TR/2012/REC-owl2-syntax-20121211/#Datatype_Maps)
       - every root type must have a type uri
     in_subset:

linkml_model/model/schema/types.yaml

@@ -126,7 +126,13 @@
     uri: xsd:anyURI
     base: URIorCURIE
     repr: str
-    description: a URI or a CURIE
+    description: an IRI (URI) or a CURIE
+    comments:
+      - IRIs are allowed, name is kept for backwards compatibility.
+      - Loaders should always attempt CURIE to IRI expansion.
+      - Loaders may emit warnings if a value looks like an CURIE, but a prefix is missing.
+      - Dumpers should always perform IRI to CURIE compaction, picking the longest prefix if multiple match.
+      - Dumpers should not write IRIs which would be re-interpreted as CURIEs.
     notes: >-
       If you are authoring schemas in LinkML YAML, the type is referenced with the lower case "uriorcurie".
 
@@ -136,7 +142,7 @@
     repr: str
     description: a compact URI
     comments:
-      - in RDF serializations this MUST be expanded to a URI
+      - in RDF serializations this MUST be expanded to an IRI
       - in non-RDF serializations MAY be serialized as the compact representation
     notes: >-
       If you are authoring schemas in LinkML YAML, the type is referenced with the lower case "curie".
@@ -146,11 +152,9 @@
     uri: xsd:anyURI
     base: URI
     repr: str
-    description: a complete URI
+    description: a complete IRI (URI)
     comments:
-      - >-
-        in RDF serializations a slot with range of uri is treated as a literal or type xsd:anyURI unless it is an identifier or
-        a reference to an identifier, in which case it is translated directly to a node
+      - IRIs are allowed, name is kept for backwards compatibility.
     notes: >-
       If you are authoring schemas in LinkML YAML, the type is referenced with the lower case "uri".
     close_mappings:
@@ -168,7 +172,7 @@
   langstring:
     uri: linkml:LocalizedText
     base: LocalizedText
     repr: str # TODO for LinkML-Py maintainers: change this
     description: >-
       String with optional localization variants. Either a plain, non-langauge-tagged string or a multi-language mapping with at least one value.
       In JSON, plain strings should be mapped to JSON strings, and multi-language strings should be represented as a dictionary object of a language tag to a value in that language.