Skip to content

Main content

TEI Rendition Pointer Token Tool

Prefix a supplied local TEI rendition identifier with a fragment marker without validating XML names or resolving a document.

Loading tool…

Description

Prefix a supplied rendition identifier with a fragment marker.

Digital editions separate source readings, editorial uncertainty, witness locators, image requests, identifiers and rights statements. XML character/attribute rules differ from display labels, while URI fragments and TEI pointers need their target-document context. An identifier key or formatted token does not authenticate a witness, validate an edition or authorize reuse.

Prefix a supplied rendition identifier with a fragment marker.

When to use this tool

Use TEI Rendition Pointer Token when you already have renditionId and need to prefix a supplied rendition identifier with a fragment marker.

How to use the tool and how it works

  1. Enter renditionId. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read pointer. Use the output convention below.

Require renditionId nonempty with no whitespace or #; return #+renditionId literally.1

A rendition pointer refers to rendering information in its document context. Prefixing an identifier alone does not verify that the referenced rendition exists or that the complete TEI record is valid.2

Input fieldMeaning and unitsAccepted input
renditionIdNonempty text without whitespace or #; punctuation beyond XML names can still pass.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
pointerPointerRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "renditionId": "rend17"
  },
  "output": {
    "pointer": "#rend17"
  }
}

Limitations and assumptions

  • The grammar permits punctuation beyond XML names and performs no percent encoding. No TEI target, XML name validity, URI validity or document reference is resolved.
  • 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

Validate the complete XML/TEI document or IIIF request when technical conformance matters, and inspect the original witness and rights record for editorial use. Preserve uncertain readings, source order and attribution rather than treating local tokens as verified scholarly interpretations.

References

  1. Calculation and input contract: digital-humanities/tei-rendition-pointer-token — tool.io

  2. TEI P5: Rendition attributes — TEI Consortium

Similar or alternative tools