Blazon Word Order Validator (English convention)
Audit caller independently annotated blazon stage order against explicit English-convention edition order; not an unrestricted natural-language grammar parser.
Description
Blazon-order review can compare annotated stage ordinals with an explicitly expected sequence.
Blazon-order review can compare annotated stage ordinals with an explicitly expected sequence.1
Detecting a positional mismatch is different from parsing grammar or validating a complete blazon.
When to use Blazon Word Order Validator (English convention)
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 Blazon Word Order Validator (English convention) and understand its results
- Establish the source tradition, viewing frame, coordinate units and independently annotated features.
- Enter annotatedFieldStageOrdinals, callerExpectedStageOrdinals, using the field meanings and rules below, then run the tool.
- Read result.matchesCallerOrder, result.firstOrderMismatchIndex, 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 |
|---|---|---|---|
| annotatedFieldStageOrdinals | Annotated field stage ordinals | list of number | Required |
| callerExpectedStageOrdinals | Caller expected stage ordinals | list of number | Required |
Supply nonempty aligned observed and expected stage-ordinal lists, each entry a safe integer 0..16. Find the first positional inequality and return its zero-based index, or −1 if all positions agree. Also return the full-match boolean.
firstMismatch=findIndex(observed_i≠expected_i); matches=(firstMismatch=−1) 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.matchesCallerOrder | matches Caller Order | boolean |
| result.firstOrderMismatchIndex | first Order Mismatch Index | number |
{
"input": {
"annotatedFieldStageOrdinals": [
0,
1,
2,
3
],
"callerExpectedStageOrdinals": [
0,
1,
2,
3
]
},
"output": {
"result": {
"matchesCallerOrder": true,
"firstOrderMismatchIndex": -1
}
}
}Limitations and assumptions
The stage annotations and expected sequence are caller-defined. The tool does not parse words, require ordinal uniqueness or validate full blazon grammar.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Structured Fields to Blazon Sentence Serializer: A blazon orders a field description and charge descriptions according to an adopted convention. For a complementary comparison, 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.
References
Similar or alternative tools
- Structured Fields to Blazon Sentence Serializer
A blazon orders a field description and charge descriptions according to an adopted convention.
- 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.