EventAvailability request message

Tabular overview of all nodes, which may occur in this message. See legend below for description of table columns.
Note: Some sibling elements or complete sub-trees of the hierarchy may be defined as mutually exclusive alternative choices. This information cannot be expressed in this tabular overview. Please refer to schema diagram for a graphical representation of the message schema.

NodeDescriptionValuesOccursExample
<EventAvailabilityRQ>
Event availability request root element (Jonview)1
<Event>
1..N
@EventCode
Event code.
1 INSPB2
@Quantity
Herein a number specific for the event (product) has to be given; it belongs to a unit applicable for the specific product (feet, days, nights, hours, minutes, ...).
0..1 45
<StartDate/>
Start date in ISO 8601 format (yyyy-mm-dd).
1 2013-08-13
<NumberOfPersons/>
Number of persons per event incl. children.
[1] to []1 1
<Child>
Child elements per event - one per requested child.0..N
@Age
Age of child in years (allowed values are 0-18).
The age should be specified for the StartDate.
[0] to [18]1
</Child>
</Event>
</EventAvailabilityRQ>

Legend

ColumnDescription
NodeName of message node (element or attribute). Nodes in bold type are mandatory, if their parent element occurs in the message. Point mouse cursor at table cell to view complete XPath.
DescriptionDescription of meaning and usage of the node.
ValuesList of predefined values (each in square brackets) or range of values ("[a] to [z]") allowed for the node, if formally defined in the schema.
OccursMinimum and maximum number of times the node must/may occur, if its parent element occurs in the message. Examples:
0..3 Node is optional and may occur up to 3 times.
1..N Node must occur at least one (mandatory) and may occur any number of times.
2 Node must occur exactly twice.
ExampleExample value for the node.

XML Schema documentation generated with XX/1 server