Skip to content

Main content

Historical Text Editorial Emendation Token

Pair explicit source and emended readings with editorial provenance without generating an emendation.

Loading tool…

Description

Pair explicit source and emended readings with editorial provenance.

Historical records separate source readings, remembered dates, documentary dates, place identifiers and editorial conventions. Supplied certainty or witness labels are annotations rather than authenticated evidence. Original spellings, calendar styles and accession-year conventions need their documentary context before chronological interpretation.

Pair explicit source and emended readings with editorial provenance.

When to use this tool

Use Historical Text Editorial Emendation Token when you already have sourceReading, suppliedEmendation, editorialSource and need to pair explicit source and emended readings with editorial provenance.

How to use the tool and how it works

  1. Enter sourceReading, suppliedEmendation, editorialSource. 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 token. Use the output convention below.

Enter sourceReading, suppliedEmendation, editorialSource using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
sourceReadingSource ReadingRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedEmendationSupplied EmendationRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
editorialSourceEditorial SourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "sourceReading": "reading A",
    "suppliedEmendation": "reading B",
    "editorialSource": "Editor A"
  },
  "output": {
    "token": "[\"reading A\",\"reading B\",\"Editor A\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without generating an emendation. Sources and asserted relationships are not independently authenticated.
  • 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

Consult the original source, edition and provenance for a historical claim. Apply an appropriate calendar or documentary analysis when actual conversion, identity or interpretation is needed; a transcription key or uncertainty marker does not establish those results.

References

  1. Calculation and input contract: history/historical-text-editorial-emendation-token — tool.io

Similar or alternative tools