1.7.9 Shared Tickets Components

Utilised In

• <Tickets> (1.1.7)
• <TicketsOverride> (1.1.8.5)

Shared Attributes

Shared Child Elements

choice:

 

<TicketType>

1.7.9.1, optional and repeatable. Each <TicketType> describes the cost and purchase of a single class of ticket.

<UnTicketed>

1.7.9.2, non-repeatable

If neither <TicketType> nor <UnTicketed> are utilised then the <Tickets> status is explicitly undefined. It is preferable (although not compulsory) to include a <Description> as documented below.

<Contacts>

1.2.1, optional. A <Contacts> inside <Tickets> is intended to represent individuals or organisations who are able to sell or provide advice on the tickets contained within the <Tickets>.

<Description(Reference)>

1.4.2(1.4.2.1), optional and repeatable. This is primarily intended to convey humanly readable information about where to buy tickets and how much they cost. While it is preferable to supply structure information in the <TicketType> and <Contacts> elements, it may be useful to clarify this information with a supporting <Description> if there are relationships beween the structured elements that are hard to convey withing the constraints of their formats.
If you are unable to supply structured data then a single <Description> within a <Tickets> element is preferable to not providing any ticketing information at all.

<Link(Reference)>

1.4.3(1.4.3.1), optional and repeatable

<Property>

1.4.4, optional and repeatable