Fix casing of linkml:Uriorcurie.

The IRI of the "uriorcurie" data type is `https://w3id.org/linkml/Uriorcurie`, _not_ `.../uriOrCurie`. Not sure where I got the incorrect casing from.
mapping-commons · Jul 23, 2024 · b0754c9 · b0754c9
1 parent 9f4a7b8
commit b0754c9
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/examples/schema/extension-slots.sssom.tsv b/examples/schema/extension-slots.sssom.tsv
@@ -11,7 +11,7 @@
 #    type_hint: xsd:integer
 #  - slot_name: ext_baz
 #    property: EXPROP:bazProperty
-#    type_hint: linkml:uriOrCurie
+#    type_hint: linkml:Uriorcurie
 #  - slot_name: ext_foo
 #    property: EXPROP:fooProperty
 #ext_foo: Foo A

diff --git a/src/docs/spec-formats-tsv.md b/src/docs/spec-formats-tsv.md
@@ -153,7 +153,7 @@ A SSSOM/TSV reader MUST check the validity of the extension definitions listed i
 
 A SSSOM/TSV reader MUST, upon encountering a non-standard YAML key in the metadata block or an unknown TSV column, check that the name of the key or of the column matches the `slot_name` of one of the extension definitions listed in the mapping set’s `extension_definitions` slot. If there is no match, the non-standard slot MUST be discarded.
 
-Upon encountering a non-standard slot whose corresponding definition has a `type_hint` of `https://w3id.org/linkml/uriOrCurie`, the reader SHOULD check that the value is a CURIE and is resolvable using the mapping set’s `curie_map`.
+Upon encountering a non-standard slot whose corresponding definition has a `type_hint` of `https://w3id.org/linkml/Uriorcurie`, the reader SHOULD check that the value is a CURIE and is resolvable using the mapping set’s `curie_map`.
 
 
 ## Compatibility with previous versions of the specification