Description
Build a hand-shift reference from a restricted ASCII identifier.
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.
Build a hand-shift reference from a restricted ASCII identifier.
When to use this tool
Use TEI Hand Shift Reference when you already have scribeId and need to build a hand-shift reference from a restricted ASCII identifier.
How to use the tool and how it works
- Enter scribeId. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read reference. Use the output convention below.
Require first character ASCII letter or underscore, followed by ASCII letters, digits, underscore, dot or hyphen; return #+scribeId.1
A hand-shift reference can identify a descriptive hand record. The generated local fragment does not identify a scribe or resolve that target.2
XML names allow a wider character repertoire than this helper's ASCII subset. Passing this local grammar is separate from checking a document's identifiers and references.3
| Input field | Meaning and units | Accepted input |
|---|---|---|
| scribeId | ASCII letter/underscore first, then ASCII letters/digits/underscore/dot/hyphen; a restricted name grammar. | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| reference | Reference | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"scribeId": "hand_17"
},
"output": {
"reference": "#hand_17"
}
} Limitations and assumptions
- This is narrower than full Unicode XML naming. No scribe identity, target xml:id, TEI element or document-wide validity is verified.
- 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
-
Calculation and input contract: digital-humanities/tei-hand-shift-reference — tool.io
-
TEI P5: Handwriting shift — TEI Consortium
Similar or alternative tools
- TEI Rendition Pointer Token
Prefix a supplied rendition identifier with a fragment marker.
- Digital Edition Anchor Fragment
Percent-encode a supplied anchor identifier into a URL fragment.