1.3.2.1 <TicketType>

Each <TicketType> element represents a single type or price band of ticket that can be purchased for an event.

Attributes

supplierSpecificId

, optional

May Contain

<Title>

compulsory. The structured name of this ticket type.

choice

a <TicketType> must define its pricing in one of the following ways. If it isn't possible to accurately model the <TicketType> with either of these then it probably means that you should split it into 2 or more separate <TicketType> elements.

concrete price

 

<Price>

(), compulsory. The price that all tickets of this ticket type will cost.

<FormattedPrice>

optional

price range

if there is not a single price then you must define the minimum and maximum price.

<MinPrice>

(), compulsory. The minimum price that you would be charged for tickets of this ticket type. Semantically the same as <Price> but named <MinPrice>

<MaxPrice>

(), compulsory. The maximum price that you would be charged for tickets of this ticket type. Semantically the same as <Price> but named <MaxPrice>

<FormattedPrice>

optional

unparseable price

If it isn't possible to define a <TicketType> in concrete parseable values, whether single or a range, then you can utilise a <FormattedPrice> description of how the pricing works. Suppliers should only utilise this when it isn't possible to use the parseable values as it restricts Consumers and prevents them from being able to make algorithmic decisions based on price such as sorting or filtering.

<FormattedPrice>

compulsory

<Description(Reference)>

(), optional and repeatable

<Link(Reference)>

(), optional and repeatable

<Property>

, optional and repeatable