Description
Mark hasLanguage for nonempty language.
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.
Mark hasLanguage for nonempty language.
When to use this tool
Use RDF Data Type Language Conflict when you need one explicit RDF term or scope consistency check.
How to use the tool and how it works
- Enter datatype, language. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read hasLanguage, conflictingDatatype. Inspect hasLanguage, conflictingDatatype before interpreting the associated values.
Mark hasLanguage for nonempty language. Report conflictingDatatype only when a language is present and datatype is nonempty and different from the exact rdf:langString IRI.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| datatype | Datatype | Required. Text; maximum UTF-16 length 8192. |
| language | Language | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| hasLanguage | Has Language | Required. Boolean. |
| conflictingDatatype | Conflicting Datatype | Required. Boolean. |
{
"input": {
"datatype": "http://www.w3.org/2001/XMLSchema#string",
"language": "en"
},
"output": {
"hasLanguage": true,
"conflictingDatatype": true
}
}Limitations and assumptions
- An empty datatype is not flagged; language grammar, term construction, and a complete RDF dataset are not validated.
- 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.