https://www.w3.org/TR/rdf11-concepts/#section-Datatypes
A datatype consists of a lexical space, a value space and a lexical-to-value mapping, and is denoted by one or more IRIs.
i.e. a datatype indicates how to map the string representation to a value.
The http://www.w3.org/2001/XMLSchema describes several useful datatypes,
such as http://www.w3.org/2001/XMLSchema#decimal, which maps e.g. “3.2” to the number 3+1/5.
Deprecated name for http://ns.nuke24.net/Datatypes/URIResource
Lexical space: URIs.
Value space: Any resource that can be named by a URI.
The lexical-to-value mapping of a given URI is the resource identified by that URI. For HTTP and hash URIs, the resource is always a byte sequence, possibly with some metadata attached (e.g. `Content-Type` hints at the content’s `http://purl.org/dc/terms/format`), but other URI schemes may allow references to more abstract resources.
Note that http://www.w3.org/2001/XMLSchema#anyURI
(as documented here)
does not specify the value as being the target of the URI.
Deocding a string by `anyURI` results the URI itself;
i.e. basically a string with a flat on it saying “I am a URI”.
Lexical space: Valid RDF+XML documents with a single root node.
Value space: All resources. The value is that which is described by the ‘root’ node.
If there are multiple root nodes, then the document has no ‘value’ (unless
Lexical space: Valid JSON-encoded values.
Value space: floating-point numbers, character strings, lists, and JavaScript objects. JavaScript objects are not given any additional meaning; they are simply a mapping of attribute name to value (without the connotation of being a ‘collection’ per se!)
Value space: All resources. The value is that described by a JSON-encoded object, as interpreted according to JSON-LD.
Pares the data as multi-channel audio data, essentially. More details in the P0025 documentation.
A directory encoded as TEF. A text-based archive format where files are represented as:
=file FILENAME_GOES_HERE.TXT ANY-METADATA: GOES HERE CONTENT GOES HERE
Capital letter indicate placeholders. See https://github.com/TOGoS/TEF for more info. Content encoding follows TEF v0.3.0 conventions. The last newline before the ‘=’ of a new entry is not considered part of the content. (What about the last newline before end of file? Hmm, may need to update the TEF spec.)
Lexical space: any text that might be interpreted by an English speaker.
Value space: any resource.
e.g. “Dan and Joh’s small red Shop-Vac”, “WSITEM-200354”, and “urn:oid:1.3.6.1.4.1.44868.260.200354” would all resolve to our small red Shop-Vac, since URIs are a subset of English descriptions.
This is obviously an extremely informal, ill-defined datatype, but it’s here as an escape hatch for when I want to talk about a thing that is otherwise hard to build a URI for.
Lexical space: strings of the format: data URI + [whitespace + datatype URI]
Value space: All resources.
Mapping: The first URI indicates the encoded form of the value. May often be a ‘data:’ URI. Each URI following names a datatype whose lexical->value mapping should be applied, in order, to resolve the represented value.
This datatype may be useful even when only one datatype is applied, since it allows you to type non-literals in RDF!
It also provides a universal format for referencing:
- Literal strings (just put a data: URI and be done with it)
- Other web resources (any other URI)
- Other literal values (decimal numbers, rational numbers, lists…)
- Interpretation of any of the above based on any other datatype!
For some suggested alternative uses of this datatype’s URI, especially regarding use in JavaScript/JSON objects, see TS34Encoded Datatype.
Deprecated alias for http://ns.nuke24.net/Datatypes/TS34Encoded
Subject of document. Identical to http://ns.nuke24.net/TOGVM/Datatypes/RDFXMLValue
when the document is an RDF+XML document, but is defined
for other formats, such as TOGoS Binary/Text Blocks.
See The Subject Datatype for more info and mappings for specific formats.