| ID
| Requirement
| Notes
|
| 2.7.1.
| The document reader shall create one or more Record 2 sequences for each category represented in a contract artifact.
|
|
| 2.7.2.
| If an Alt GEN is being used for a category, the document reader shall create a Record 2 sequence for the category.
|
|
| 2.7.3.
| The document reader shall insert one of the following into each Record 2 sequence:
· One or more Record 3 table numbers or
· Alt GEN
|
|
| 2.7.4.
| The document reader shall assign a number to each Record 2 sequence.
|
|
| 2.7.5.
| When a category consists of multiple sequences, the sequence with the most specific Record 2 data shall have the lowest number. Sequence numbers shall increase as each sequence becomes less specific.
|
|
| 2.7.6.
| When a sequence consists of multiple Record 3 table numbers, each one shall be separated by a relational indicator.
|
|
| 2.7.7.
| If an STR is being used for category, all of its sequences shall be copied to the contract rule.
Do we want to say anything about how Volaro needs to structure geographies in Record 2’s? (e.g. not send city specific record 2’s when nation, zone, area is applicable)
|
|
| 2.7.8.
| Reuse of User Created Zones shall be allowed for participating carriers only.
|
|
| 2.7.9.
| Any instruction requesting the creation of a User Zone shall be ignored.
|
|
| 2.7.10.
| The geography values of the Record 2 shall match those listed in the contract artifact and not be listed broken down toat a more granular level.
For example, if an artifact states “for travel between US and Great Britain,” the LOCs should state Country US and Country GB, not individual cities in each country.
|
|
