Description
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.
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.
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.
When to use this tool
Use RDF Datatype Lexical Boundary Check when you need one explicit RDF term or scope consistency check.
How to use the tool and how it works
- Enter lexical, datatype. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid. Inspect valid before interpreting the associated values.
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. Return valid.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| lexical | Lexical | Required. Text; maximum UTF-16 length 8192. |
| datatype | Datatype | Required. Text; one of "integer", "decimal", "boolean"; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this narrowly scoped condition passes; it is not necessarily full-document validity. | Required. Boolean. |
{
"input": {
"lexical": "1e3",
"datatype": "decimal"
},
"output": {
"valid": false
}
}Limitations and assumptions
- This is a lexical shape check for three labels without datatype IRIs, XML whitespace processing, numeric conversion, or complete RDF validation.
- 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 Data Type Language Conflict
Mark hasLanguage for nonempty language.
- SKOS Notation Datatype Literal Pair
Serialize notation and datatypeIri as typedIdentity.