How do we maintain the relationships between data elements embodied in segment level syntax notes?
You can qualify groups by the same occurrence indicators used for elements. You can also nest groups to a predefined number of levels (the XML default is more than high enough for ANSI ASC X12 needs). In addition, you have another type of “connector” than the sequence connector (the comma). This other connector, “|,” indicates either/or situations. For example, one could define the model for an element called “element-b” as follows: This model says that “element-b” either contains a single “a” element, or one or more pairs of “b” and “c” elements. If there is a “b,” there must be a “c,” and if there are more than one “b,” each in turn must have its own “c.” If neither of these states occurred, there must be one or more “e” elements, with an optional single “d” element and any number of optional “f” elements, but once you enter any “f” element you may not enter any more “e” elements. If “a,” “b/c” or “e” are not present, an error is
Related Questions
- What is the difference between Gold and Silver level compliance? Is Silver compliance just the elements marked as "National" in the Data Dictionary?
- Are there high level administration relationships in Ordnance Survey data derived from the Boundary-Line⢠product?
- How do we maintain the relationships between data elements embodied in segment level syntax notes?