Next: 1.3.2.1 <TicketType>
Up: 1.3 Cascading performance definitions
Previous: 1.3.1.3 <PerformanceSpaceReference>
Contents
Index
1.3.2 <Tickets>
The <Tickets> element is an optional container element that lets you
define what tickets are available for an event and who to contact
in order to go about purchasing them.
Attributes
May Contain
- choice:
-
- <TicketType>
- , optional
and repeatable. Each <TicketType> describes the cost and purchase
of a single class of ticket.
- <UnTicketed>
- , 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>
- , 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)>
- (),
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)>
- (),
optional and repeatable
- <Property>
- , optional and repeatable
Contained Within
- <Event>
- , optional
- <Schedule>
- , optional
- <Performance>
- , optional
Subsections
Next: 1.3.2.1 <TicketType>
Up: 1.3 Cascading performance definitions
Previous: 1.3.1.3 <PerformanceSpaceReference>
Contents
Index
Alex Fiennes
2010-04-13