1.7.7.1 <Performance>

A <Performance> represents a single period when the event is happening. This will normally be a conventional performance, but if the event has a <DropInEvent> element (1.1.3), then the performance will represent a single uninterrupted period of opening time.

The where, how long and how much of a given performance is dictated by the element that it is nested inside. If it is contained within the default <Schedule> then it is controlled by the <Venue>, <PerformanceDuration> and <Tickets> elements, whereas if it is contained within a <ScheduleExtension> (inside an <Extension>) then the above elements may be optionally overriden by <VenueOverride>, <PerformanceDurationOverride> and <TicketsOverride> elements contained within the same <Extension>.

Attributes

rescheduledFrom

optional. XML Schema datetime. If this performance was previously scheduled and / or advertised to begin at a different time, then this should contain the old time at which it was supposed to begin. This attribute may also be used in conjunction with the previousVID on <Venue> (1.1.6)

isCancelled

optional, boolean. If defined and if true then it means that this perormance is no longer going to take place. While it may seem counterintuitive to advertise a performance that is no longer going to happen, it may be invaluable to let Consumers know about the change of status for a performance so previously supplied information can be accurately updated.

isSoldOut

optional, boolean. If defined and true then it means that as far as the Supplier is aware, there are no more tickets available for this performance.

supplierSpecificId

optional, (see 1.6.1). If a Supplier is updating previously sent information with new times or cancellations, then it is probably safest to provide the same supplierSpecificId for both the original and the updated information as this reduces the chances of the Consumer targetting the wrong performance for the update. If this is not provided, then the startTime for the performance may be used to determine performances, but this is not guaranteed to be unambiguous, especially if there are different <Extension>s being used on the performance.

May Contain

choice

 

<StartDateTime>

XML Schema datetime. The date and time at which this performance begins. This should generally be the time at which the venue would like people to arrive which may be earlier than the actuall formal start of the performance itself. If the event is a drop-in event then the startTime will be the opening time of the venue.

<StartDate>

XML Schema date. If the date of the performance is known, but not the time then this should be used in preference to making up a potentially misleading time for <StartDateTime>. <StartDateTime> is preferred over <StartTime> where possible.

<StartUndefined>

1.7.7.1.1. Used to model a situation when the date of a performance is either not known or is thought to happen within a given datespan.

<Description>

1.4.2, optional and repeatable

<Link>

1.4.3, optional and repeatable

<Property>

1.4.4, optional and repeatable

Contained Within

<Schedule>

1.1.5, compulsory and repeatable

<ScheduleExtension>

1.1.8.1, compulsory and repeatable