Description
Serialize notation and datatypeIri as typedIdentity.
RDF literals distinguish lexical spelling, datatype identifiers, language tags, and local blank-node scope. A token-shape check covers only part of RDF term validity.
Serialize notation and datatypeIri as typedIdentity.
When to use this tool
Use SKOS Notation Datatype Literal Pair when you need one explicit RDF term or scope consistency check.
How to use the tool and how it works
- Enter notation, datatypeIri. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read typedIdentity. Use the output convention below.
Require nonempty notation and a datatypeIri beginning with an IRI-scheme-like prefix. Serialize notation and datatypeIri as typedIdentity.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| notation | Notation | Required. Text; maximum UTF-16 length 8192. |
| datatypeIri | Datatype Iri | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| typedIdentity | Typed Identity | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"notation": "001.2",
"datatypeIri": "urn:example:classification"
},
"output": {
"typedIdentity": "[\"001.2\",\"urn:example:classification\"]"
}
}Limitations and assumptions
- The datatype identifier is not fully parsed or dereferenced; literal value equality and datatype validity are not established.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use a conforming RDF parser and the relevant datatype and language-tag rules for complete graph validation.
References
Similar or alternative tools
- RDF Language Tag Literal Pair
Require a simple ASCII language-tag shape, lowercase it, and serialize lexical with normalizedLanguage for identityKey.
- RDF Datatype Lexical Boundary Check
For integer accept optional sign and digits; for decimal additionally permit a decimal point without an exponent; for boolean accept true, false, 1, or 0.