CanonicalReference — JSON-LD
const url = 'https://textrefs.org/id/ref/example.json';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://textrefs.org/id/ref/example.jsonParameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”CanonicalReference record as JSON-LD.
object
Successor IRI. Only present when status is deprecated, withdrawn, or blocked.
Flat registry key: lowercase, starts with [a-z0-9], allows . _ -
Flat registry key: lowercase, starts with [a-z0-9], allows . _ -
object
An IRI (RFC 3987), not a URI (RFC 3986). The registry publishes resolver targets that carry non-ASCII characters, such as …/Investigaciones_filosóficas_(edición_A). RFC 3986 forbids those characters, so a validator that enforces the uri format rejects records this site serves. The generated JSON Schema declares iri for the same reason.
An IRI (RFC 3987), not a URI (RFC 3986). The registry publishes resolver targets that carry non-ASCII characters, such as …/Investigaciones_filosóficas_(edición_A). RFC 3986 forbids those characters, so a validator that enforces the uri format rejects records this site serves. The generated JSON Schema declares iri for the same reason.
Example
{ "status": "draft", "type": "CanonicalReference", "resolver_targets": []}No registry object found at this identifier. The site is static, so the
host cannot build a per-path error body. It serves the site’s own 404
page instead: text/html, with the same navigation as every other
page. A client detects the miss from the status code, not from the body.
The site’s HTML 404 page.