Skip to content

Main content

TEI Witness Support Count Tool

Count supplied TEI-style witness/reading incidences after explicit omissions; no XML parsing or textual reconstruction.

Loading tool…

Description

Count distinct eligible and supporting witnesses.

Digital editions connect textual witnesses, anchors, page images and source-specific labels. Literal identifier agreement and numerical offsets preserve a supplied convention without proving textual authority, complete coverage or correct editorial interpretation.

Count distinct eligible and supporting witnesses.

When to use this tool

Use TEI Witness Support Count when checking supplied edition identifiers, ordering or coordinate conventions.

How to use the tool and how it works

  1. Enter witnessIds, readingIds, selectedReading, omittedWitnesses. Keep parallel arrays aligned. 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 eligibleWitnesses, supportingWitnesses. Use the output convention below.

Count distinct eligible and supporting witnesses. Require aligned witnessIds/readingIds; exclude omittedWitnesses, deduplicate IDs and count witnesses having at least one selectedReading record.1

Input fieldMeaning and unitsAccepted input
witnessIdsWitness IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
readingIdsReading IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
selectedReadingSelected ReadingRequired. Text; maximum UTF-16 length 8192.
omittedWitnessesOmitted WitnessesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
Output fieldInterpretationReturned shape
eligibleWitnessesEligible WitnessesRequired. Safe integer.
supportingWitnessesSupporting WitnessesRequired. Safe integer.
json
{
  "input": {
    "witnessIds": [
      "w1",
      "w1",
      "w2"
    ],
    "readingIds": [
      "a",
      "b",
      "a"
    ],
    "selectedReading": "a",
    "omittedWitnesses": [
      "w2"
    ]
  },
  "output": {
    "eligibleWitnesses": 1,
    "supportingWitnesses": 1
  }
}

Limitations and assumptions

  • A witness can have conflicting records yet count as supporting; no textual stemma or source independence is inferred.
  • 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

Inspect the original edition and its encoding model before treating local record agreement as meaningful textual or historical evidence.

References

  1. Calculation and input contract: digital-humanities/tei-witness-support-count — tool.io

Similar or alternative tools