Notational Conventions

All parts of this standard are normative, with the exception of examples and sections explicitly marked as "Non-Normative". Some messages and aggregates my be annotated as “Candidate Recommendation”. These messages and aggregates have been approved by the ACORD membership but currently have no implementations or pilot testing. Messages and aggregates will stay in candidate recommendation status until they are implemented. Deprecated items are objects or processes that were implemented in a previous version of the standard. Deprecated items remain in the standard and schema to allow for backwards compatibility, but should not be implemented in a new project (unless you have a trading partner using them). Generally a note will indicate the reason for deprecation as well as the suggested replacement object or process.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

  1. MUST - This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the standard. This is tracked as a requirement.
  2. MUST NOT - This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the standard. This is tracked as a requirement.
  3. SHOULD - This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. This is tracked as a recommendation.
  4. SHOULD NOT - This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. This is tracked as a recommendation.
  5. A design rule indicates a general principal or rule that was used in the development of this standard.
  6. A business rule indicates a relationship between data elements and attributes that cannot be validated by a schema and should be implemented in code or some other manner.

Last edited Mar 26, 2016 at 9:26 PM by natewaite, version 1