Next: 1.4.2.1 <PerformanceSpaceDefinition>
Up: 1.4 Shared Definitions
Previous: 1.4.1 <ContactDefinition>
Contents
Index
1.4.2 <VenueDefinition>
A <VenueDefinition> is a definition element containing the
same information as may be contained in a <Venue>, but outside the
scope of a given <Event>.
Attributes
- supplierDefinitionId
- compulsory. The id that uniquely identifies
this shared definition element to the supplier.
- VID
- compulsory. The VID that represents the unique ID of the
Venue that is being described. See http://www.ives.info for more information
on how to resolve VIDs and how to go about finding an existing VID
for a Venue or creating a new one if one has not yet been allocated.
- creationTime
- optional. See Shared timestamp attributes
()
- lastUpdateTime
- optional. See Shared timestamp attributes
()
Note that he previousVID attribute from <Venue> is not permitted
in <VenueDefinition> because this relates to how an <Event> relates
to a <Venue> rather than the shared definition in <VenueDefinition>.
If you wanted to model how the ``usage'' of a <VenueDefinition>
had changed with respect to an <Event> then you should utilise the
previousVID inside the appropriate <VenueReference> element.
May Contain
- <Title>
- , optional. If not defined then the name
of the Venue should be derived from the VID record.
- <Contacts>
- , optional. Contact information for
the Venue itself.
- Descriptive Elements
- ()
- <PerformanceSpaceDefinition>
- .
optional and repeatable. You may define one or more shareable details
about peformance spaces contained within the <VenueDefinition>. These
may be referred to directly by a <PerformanceSpaceReference> which
may be utilised instead of a <VenueReference> if you want to give
more precise information as to the location of an Event.
Please note that even if you only have a single <PerformanceSpaceDefinition>
under a <VenueDefinition> then a <VenueReference> does not
include the <PerformanceSpaceDefinition>. You need to explicitly reference
it via a <PerformanceSpaceReference> to include this information.
This is not the same behaviour as between a <Venue> : <PerformanceSpace>
relationship, but it is necessary to reduce ambiguity if additional
<PerformanceSpaceDefinition> elements get added to the <VenueDefinition>
in the future.
Contained Within
- <IvesMessage>
- optional and repeatable.
Subsections
Next: 1.4.2.1 <PerformanceSpaceDefinition>
Up: 1.4 Shared Definitions
Previous: 1.4.1 <ContactDefinition>
Contents
Index
Alex Fiennes
2010-04-13