| |||||||||||||||||||||||||||||
prev next Table of Contents Common Elements | |||||||||||||||||||||||||||||
3.9 DeliveryItemListTypeThe schema representing the destination address for delivery of messages or reports is somewhat complex. The older schemas (2004/11 and 2007/02, which are still the current versions for some functions) used a hierarchy of types illustrated by this diagram: More recent schemas flatten this hierarchy in order to reduce the number of classes some development tools generate based on the schema, but the ultimate XML representation of destinations is the same. A catch-all type, DeliveryItemListType is defined that represents one or more elements of any of the 11 final types of destination, and is used in several places where a set of destinations is required. Note that DeliveryItemListType designates a set of destinations, not necessarily just one. Also note that DeliveryItemListType is a type, and therefore does not itself directly appear in an XML document - there would instead be one or more of the final destination types.
There are some restrictions on destinations appearing in Alternate elements. The schemas make recursive use of the same destination type definitions, but due to the internal representation of destinations Alternates cannot contain InsertList elements or Extension elements that include segments other than the default segment. It should be noted that the XML representation of destinations is not used by EasyLink systems internally. Since the XML supports, in most cases, a variety of ways to represent the data, a destination retrieved from the system may not match exactly the XML format that was originally supplied. Each of the 11 final types is described in subsequent pages as they appear in their final form. | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
prev next Table of Contents Common Elements | |||||||||||||||||||||||||||||
|