Documentation for ATIS-Draft-03-00-79

Complex Type: MessageHeader

[Table of contents]

Super-types: None
Sub-types: None
Name MessageHeader
Used by (from the same schema document) Complex Type AdvisoryInformation , Complex Type DirectoryAdvancedRequest , Complex Type InformationRequest , Complex Type InformationResponse , Complex Type ParkingSpaceReply , Complex Type ParkingSpaceRequest , Complex Type RouteRequest , Complex Type TravelerSettingsReply , Complex Type TravelerSettingsRequest , Complex Type ParkingLotInformation
Abstract no
XML Instance Representation
<...>
<sender> ContactSetting </sender> [1]
<messageID> tmdd:Message-number </messageID> [1]
<responseTo> tmdd:Message-number </responseTo> [0..1]
<timeStamp> DateTimePair </timeStamp> [1]
<revision> MSG-Revision </revision> [0..1]
<msgCount> xs:unsignedShort </msgCount> [1]
</...>
Diagram
h-617697835 h1583845268 h1583845268 h1210973722 h1968347596
Schema Component Representation
<xs:complexType name="MessageHeader">
<xs:sequence>
<xs:element name="sender" type=" ContactSetting "/>
<xs:element name="messageID" type=" tmdd:Message-number "/>
<-- the id of this message -->
<xs:element name="responseTo" type=" tmdd:Message-number " minOccurs="0"/>
<-- the id of the message to which this is a reply -->
<xs:element name="timeStamp" type=" DateTimePair "/>
<-- the time at which this message was issued and sent -->
<xs:element name="revision" type=" MSG-Revision " minOccurs="0"/>
<-- An enumeration of all valid adopted revisions of the standard itself presumed to be the most current adopted std is not specified this is the definitive place to see what structural definition is being used. -->
<xs:element name="msgCount">
<xs:simpleType>
<xs:restriction base=" xs:unsignedShort "/>
</xs:simpleType>
</xs:element>
<-- the seq cnt of messages, used in some systems when following the C2C rules to detect a dropped or lost message -->
</xs:sequence>
</xs:complexType>