Description
Count literal public verse-to-fragment incidences without interpreting or resegmenting sacred text.
Text references and observance records depend on an explicit edition, numbering system, time origin, or supplied calendar convention. Literal identifiers can be counted or compared without interpreting a text or establishing a religious observance rule.
Count literal public verse-to-fragment incidences without interpreting or resegmenting sacred text.
When to use this tool
Use it for public verse split count when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter sourceVerseIds, fragmentIds. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read sourceVerses, distinctFragments, additionalFragments. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Group exact sourceVerseIds and count distinct fragmentIds within each group. Return source-verse count, total distinct verse/fragment incidences, and additionalFragments as their difference.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sourceVerseIds | Source Verse Ids | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| fragmentIds | Fragment Ids | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sourceVerses | Source Verses | Required. Safe integer. |
| distinctFragments | Distinct Fragments | Required. Safe integer. |
| additionalFragments | Additional Fragments | Required. Safe integer. |
{
"input": {
"sourceVerseIds": [
"v1",
"v1",
"v2"
],
"fragmentIds": [
"a",
"b",
"a"
]
},
"output": {
"sourceVerses": 2,
"distinctFragments": 3,
"additionalFragments": 1
}
}Limitations and assumptions
- Repeated identical pairs count once, while one fragment label used for different verses counts in each group. No text is segmented, quoted, interpreted, or validated against a canon.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For public verse split count, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- Public Verse ID Segment Count
Count explicit public-text reference segments without validating a canon-specific reference system.
- Edition Verse Range Length
Count integer verse indices in one supplied edition and chapter under explicit endpoint rules.