Field First Tincture Position Checker
Check independently annotated first field-tincture token position; no grammatical identification from arbitrary words.
Description
A field-first check compares an annotated field-tincture position with the start of a token sequence.
A field-first check compares an annotated field-tincture position with the start of a token sequence.1
It requires prior annotation rather than recognizing the field from words automatically.
When to use Field First Tincture Position Checker
Use this tool to calculate or review the supplied observations under the stated rules. Establish the source tradition, viewing frame, coordinate units and independently annotated features.
How to use Field First Tincture Position Checker and understand its results
- Establish the source tradition, viewing frame, coordinate units and independently annotated features.
- Enter annotatedFieldTinctureTokenIndex, totalAnnotatedTokens, using the field meanings and rules below, then run the tool.
- Read result.fieldTinctureFirst, using the output meanings and calculation rules below.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| annotatedFieldTinctureTokenIndex | Annotated field tincture token index | number | Required |
| totalAnnotatedTokens | Total annotated tokens | number | Required |
Use total annotated tokens as an integer 1..128 and field-tincture index as an integer 0..total−1. Return whether the supplied index is zero.
fieldFirst=(fieldTokenIndex=0) Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Calculated observation or reference | object |
| result.fieldTinctureFirst | field Tincture First | boolean |
{
"input": {
"annotatedFieldTinctureTokenIndex": 0,
"totalAnnotatedTokens": 6
},
"output": {
"result": {
"fieldTinctureFirst": true
}
}
}Limitations and assumptions
No tokenization or field recognition is performed. The annotation and its relationship to the original text must be supplied.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Blazon Text Tokenizer to Structured Fields Parser: A blazon is a conventional verbal description of arms, while a restricted parser recognizes only an explicitly supported subset. For a complementary comparison, use Blazon Word Order Validator (English convention): Blazon-order review can compare annotated stage ordinals with an explicitly expected sequence.
References
-
Field First Tincture Position Checker — tool.io
Similar or alternative tools
- Blazon Text Tokenizer to Structured Fields Parser
A blazon is a conventional verbal description of arms, while a restricted parser recognizes only an explicitly supported subset.
- Blazon Word Order Validator (English convention)
Blazon-order review can compare annotated stage ordinals with an explicitly expected sequence.