This topic explains the key points of each of the message definitions used in the CSV sample.
In the CSV message set, messageset.mset has a Tagged/Delimited String physical format called CSV. Within this, Messaging Standard is set to CSV - Comma Separated Values. This causes:
This message illustrates the most simple comma separated value message model. In order to create a model for this message it is necessary to decompose the message and understand its structure. This diagram identifies the key items of metadata in this example CSV message, and shows the logical structure of the message as defined in the message set.
See Description of Comma Separated Value (CSV) sample messages for a textual description of the message as an alternative to the image.
You can view the CSV_1 message in the sample message set, to examine its structure and logical properties. Note that the message contains a single element called 'customer' which repeats from 0 to -1 (unbounded) times. You can examine the "CSV" physical properties of the message as defined in the model. Features that are worth noting include:
This message adds a header record to the CSV message from CSV_1. This diagram identifies the key items of metadata in this example CSV message, and shows the logical structure of the message as defined in the message set.
See Description of Comma Separated Value (CSV) sample messages for a textual description of the message as an alternative to the image.
You can view the CSV_2 message in the sample message set, to compare it's structure and logical properties with those of CSV_1. Features that are worth noting include:
You can examine the "CSV" physical properties of the message as defined in the model. Features that are worth noting include:
This message adds a trailer record to the CSV message from CSV_2. This diagram identifies the key items of metadata in this example CSV message, and shows the logical structure of the message as defined in the message set.
See Description of Comma Separated Value (CSV) sample messages for a textual description of the message as an alternative to the image.
You can view the CSV_3 message in the sample message set, to compare it's structure and logical properties with those of CSV_2. Features that are worth noting include:
You can examine the "CSV" physical properties of the message as defined in the model. Features that are worth noting include:
This model correctly parses the instance message, but it also matches a message with multiple trailer records and with trailer records out of sequence. To avoid this a more elaborate model is needed. CSV_4 is an example of this.
This message is an alternative approach to modeling the same message as CSV_3. This model is based on the assumption that the trailer record is the last record in the message and is always present. This diagram identifies the key items of metadata in this example CSV message, and shows the logical structure of the message as defined in the message set.
See Description of Comma Separated Value (CSV) sample messages for a textual description of the message as an alternative to the image.
You can view the CSV_4 message in the sample message set, to compare it's structure and logical properties with those of CSV_3. Features that are worth noting include:
You can examine the "CSV" physical properties of the message as defined in the model. Features that are worth noting include:
This model correctly parses the instance message. It always parses the last record as the trailer, and all preceding records as customer records.
This message introduces the use of tags in a CSV message to make the model more flexible. If the first field of each CSV record is a unique identifier then it can be used as a tag. This makes modeling the header and trailer much simpler and allows greater flexibility. This diagram identifies the key items of metadata in this example CSV message, and shows the logical structure of the message as defined in the message set.
See Description of Comma Separated Value (CSV) sample messages for a textual description of the message as an alternative to the image.
You can view the CSV_5 message in the sample message set, to examine it's structure and logical properties. Features that are worth noting include:
You can examine the "CSV" physical properties of the message as defined in the model. Features that are worth noting include:
The CSV message has unique tags on each record, which makes the model becomes much simpler. It also means that the message can include alternate record types, as in CSV_6.
This message builds on the message from CSV_5 to add a choice of different customer record in the body of the message. Using tags this becomes very simple. This diagram identifies the key items of metadata in this example CSV message, and shows the logical structure of the message as defined in the message set.
See Description of Comma Separated Value (CSV) sample messages for a textual description of the message as an alternative to the image.
You can view the CSV_6 message in the sample message set, to compare it's structure and logical properties with those of CSV_5. Features that are worth noting include:
You can examine the "CSV" physical properties of the message as defined in the model. Features that are worth noting include: