Structured Fields to Blazon Sentence Serializer
Serialize already independently reviewed ordered English field/charge phrases; not automatic agreement, syntax or legal blazon generation.
Description
A blazon orders a field description and charge descriptions according to an adopted convention.
A blazon orders a field description and charge descriptions according to an adopted convention.1
Joining already ordered phrases does not determine their grammar or heraldic correctness.
When to use Structured Fields to Blazon Sentence Serializer
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 Structured Fields to Blazon Sentence Serializer and understand its results
- Establish the source tradition, viewing frame, coordinate units and independently annotated features.
- Enter fieldPhrase, callerOrderedChargePhrases, using the field meanings and rules below, then run the tool.
- Read result.blazonSentence, 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 |
|---|---|---|---|
| fieldPhrase | Field phrase | string | Required |
| callerOrderedChargePhrases | Caller ordered charge phrases | list of string | Required |
Require a nonblank field phrase and an ordered charge-phrase list that may be empty. Every supplied phrase must be nonblank and contain no full stop or CR/LF. Preserve original phrase text, join field and charges with comma-space, and append one full stop.
blazon=join([fieldPhrase,...chargePhrases],", ")+"." 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.blazonSentence | blazon Sentence | string |
{
"input": {
"fieldPhrase": "Or",
"callerOrderedChargePhrases": [
"a lion gules",
"a chief azure"
]
},
"output": {
"result": {
"blazonSentence": "Or, a lion gules, a chief azure."
}
}
}Limitations and assumptions
The caller supplies correct phrases and order. No capitalization, grammar, number agreement, tincture rules or charge recognition is performed.
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 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
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.