1.3.1 Performance location

The performance location is the only compulsory data that is required in the performance cascading framework. Therefore it is compulsory to define the default location for an <Event> that is where all <Performance> elements will take place if it is not overriden at a more specific level.

There are 3 different ways of defining the location of a performance:

<Venue>

() The information about both which location, and all the metadata associated with the location is embedded directly within the <Event> element itself. While ``simple'', this is very innefficient if you have multiple Events that are taking place in the same location as all the information is duplicated in each Event.

<VenueReference>

() The <Event> contains a reference to a <VenueDefinition> defined elsewhere in the IVES document. This has the advantage that if 2 Events are on at the same location then they can both point at the same <VenueDefinition> resulting in a much more compact IVES document.

<PerformanceSpaceReference>

() The <Event> contains a reference to a <PerformanceSpaceDefinition> (which is itself contained within a <VenueDefinition>) elsewhere in the IVES document. This is similar to a <VenueReference> but more fine grained as it permits the definition of a shared sub-space of a location.

Any situation which permits a location (<Event>, <Schedule> & <Performance>) can support any one of the above. Trying to utilise two or more elements as siblings will result in an invalid IVES document.