next up previous contents index
Next: 1.1.8.1 <ScheduleExtension> Up: 1.1 Basic Event Structure Previous: 1.1.7 <Tickets>   Contents   Index


1.1.8 <Extension>

The <Extension> element is to be utilised if you have <Performance>s (1.7.7.1) that do not all share the same <PerformanceDuration> (1.1.4), <Venue> (1.1.6) and <Tickets> (1.1.7) values.

An <Extension> must contain a <ScheduleExtension> (that must itself contain at least one <Performance>). These performances will inherit the data (if any) defined in the <PerformanceDuration>, <Venue> and <Tickets> elements defined in the <Entry> unless they are specifically overridden by including one or more of <PerformanceDurationOverride> (1.1.8.2), <VenueOverride> (1.1.8.3) and <TicketsOverride> (1.1.8.5).

If every single performance of your event contains a different combination of venue, duration and tickets then it will be necessary to create an <Extension> for each individual performance.

Attributes

label
An optional, short, humanly readable phrase that may be used to label this <Extension>. If an <Event> has many <Extension>s, each of which containing many <Performance>s then the label attribute may be used to break up this list into manageable sections, and/or create a ``table of contents'' to jump to the performances that best fit your requirements.
notForPublicationBefore
datetime, optional attribute that Consumers should use to indicate the earliest time that they can publish the information about the <Extension> and its contained data. If an <Extension> is restricted then other parts of the <Event> may be publishable. Note that Consumers may forward a restricted <Extension> to another Consumer as an IVES document providing this attribute is retained.
supplierSpecificId
 
Contained Within

<Event>
1.1.2, optional and repeatable
May Contain

<ScheduleExtension>
1.1.8.1, compulsory. Lists the performances that this extension models.
<PerformanceDurationOverride>
1.1.8.2, optional. Permits you to define the duration of the performances in the <ScheduleExtension> if this is different from the <PerformanceDuration> for the <Event>.
<VenueOverride>
1.1.8.3, optional but not permitted with <VenueOverrideReference>. Inline definition of venue. This permits you to define the venue for the performances listed in the <ScheduleExtension> if this is different from the <Venue> defined for the <Event>. Please not that if you are utilising the same venue, but changing the <PerformanceSpace> that is being used, then you should still define the <VenueOverride> element.
<VenueOverrideReference>
1.1.8.4, optional but not permitted with <VenueOverride>. Same purpose as <VenueOverride> but references external <VenueDefinition> (1.1.6.2)
<TicketsOverride>
1.1.8.5, optional. Permits you to define the ticketing information for the performances listed in the <ScheduleExtension> if this is different from the definitions in <Tickets>. Please note that the <TicketsOverride> will replace all of the contents of <Tickets> and therefore you should list all of the <TicketType> elements that are usable for these performances rather than just the differences between the <Tickets> and the the <TicketsOverride>



Subsections
next up previous contents index
Next: 1.1.8.1 <ScheduleExtension> Up: 1.1 Basic Event Structure Previous: 1.1.7 <Tickets>   Contents   Index
Alex Fiennes 2009-10-09