pbcore 0.2.0 → 0.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/lib/pbcore-2.1.xsd +1902 -0
- data/lib/pbcore.rb +17 -0
- data/lib/pbcore/annotation.rb +1 -1
- data/lib/pbcore/asset_date.rb +1 -1
- data/lib/pbcore/asset_type.rb +1 -1
- data/lib/pbcore/audience_level.rb +1 -1
- data/lib/pbcore/audience_rating.rb +1 -1
- data/lib/pbcore/content_element.rb +11 -0
- data/lib/pbcore/contributor/contributor.rb +1 -1
- data/lib/pbcore/contributor/role.rb +1 -1
- data/lib/pbcore/coverage/coverage.rb +1 -1
- data/lib/pbcore/creator/creator.rb +1 -1
- data/lib/pbcore/creator/role.rb +1 -1
- data/lib/pbcore/description.rb +1 -1
- data/lib/pbcore/element.rb +17 -61
- data/lib/pbcore/extension.rb +11 -2
- data/lib/pbcore/extension/embedded.rb +14 -7
- data/lib/pbcore/factories.rb +2 -4
- data/lib/pbcore/genre.rb +1 -1
- data/lib/pbcore/identifier.rb +1 -1
- data/lib/pbcore/instantiation.rb +2 -2
- data/lib/pbcore/instantiation/alternative_modes.rb +1 -1
- data/lib/pbcore/instantiation/annotation.rb +1 -1
- data/lib/pbcore/instantiation/channel_configuration.rb +1 -1
- data/lib/pbcore/instantiation/colors.rb +1 -1
- data/lib/pbcore/instantiation/data_rate.rb +1 -1
- data/lib/pbcore/instantiation/date.rb +1 -1
- data/lib/pbcore/instantiation/digital.rb +1 -1
- data/lib/pbcore/instantiation/dimensions.rb +1 -1
- data/lib/pbcore/instantiation/duration.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/annotation.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/aspect_ratio.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/bit_depth.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/data_rate.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/duration.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/encoding.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/frame_rate.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/frame_size.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/identifier.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/language.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/playback_speed.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/sampling_rate.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/standard.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/time_start.rb +1 -1
- data/lib/pbcore/instantiation/essence_track/type.rb +1 -1
- data/lib/pbcore/instantiation/extension.rb +16 -7
- data/lib/pbcore/instantiation/file_size.rb +1 -1
- data/lib/pbcore/instantiation/generations.rb +1 -1
- data/lib/pbcore/instantiation/identifier.rb +1 -1
- data/lib/pbcore/instantiation/language.rb +1 -1
- data/lib/pbcore/instantiation/location.rb +1 -1
- data/lib/pbcore/instantiation/media_type.rb +1 -1
- data/lib/pbcore/instantiation/physical.rb +1 -1
- data/lib/pbcore/instantiation/relation/identifier.rb +1 -1
- data/lib/pbcore/instantiation/relation/type.rb +1 -1
- data/lib/pbcore/instantiation/rights.rb +0 -1
- data/lib/pbcore/instantiation/rights/link.rb +1 -1
- data/lib/pbcore/instantiation/rights/summary.rb +1 -1
- data/lib/pbcore/instantiation/standard.rb +1 -1
- data/lib/pbcore/instantiation/time_start.rb +1 -1
- data/lib/pbcore/instantiation/tracks.rb +1 -1
- data/lib/pbcore/instantiation_document.rb +2 -2
- data/lib/pbcore/publisher/publisher.rb +1 -1
- data/lib/pbcore/publisher/role.rb +1 -1
- data/lib/pbcore/relation/identifier.rb +1 -1
- data/lib/pbcore/relation/type.rb +1 -1
- data/lib/pbcore/rights_summary/link.rb +1 -1
- data/lib/pbcore/rights_summary/summary.rb +1 -1
- data/lib/pbcore/subject.rb +1 -1
- data/lib/pbcore/title.rb +1 -1
- data/lib/pbcore/version.rb +1 -1
- data/lib/pbcore/vocab.rb +6 -0
- metadata +5 -4
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 1b73a92c3b5ee2c05b18c519077beb2952ac546595eb6f12304c0e276f7af48b
|
|
4
|
+
data.tar.gz: 7648662adcfbfd4b2e6f82e896fa49d51898353e670106264eb02e43a6a19769
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: e5f41721756eef3d067c33725f115f7552d0ddc4ded015946afc3609eeda97228931c26c8a03892bd2fbddf54a2931dbbcc46e108a8947186ce631c38f24c35d
|
|
7
|
+
data.tar.gz: 1c0831980ab0de12d8528ef43fef87c5718ddc291fcb75e68e472fd98a808a8b9c3571f7ef6a501dc85819f5ae5cc702c254e1ab564543aa774f86a4a17fcb45
|
data/lib/pbcore-2.1.xsd
ADDED
|
@@ -0,0 +1,1902 @@
|
|
|
1
|
+
<?xml version="1.0" ?>
|
|
2
|
+
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
|
|
3
|
+
xmlns="http://www.pbcore.org/PBCore/PBCoreNamespace.html"
|
|
4
|
+
targetNamespace="http://www.pbcore.org/PBCore/PBCoreNamespace.html"
|
|
5
|
+
elementFormDefault="qualified" version="2.1draft3">
|
|
6
|
+
<xsd:annotation>
|
|
7
|
+
<xsd:documentation xml:lang="en">This is the PBCore version 2.1draft3 XML schema. All
|
|
8
|
+
element descriptions can be found at http://www.pbcore.org</xsd:documentation>
|
|
9
|
+
</xsd:annotation>
|
|
10
|
+
<!-- Change Log:
|
|
11
|
+
20150717
|
|
12
|
+
- Added the 'source, ref, version, annotation' collection of attributes to all elements where they are not yet
|
|
13
|
+
currently available.
|
|
14
|
+
- Added supplemental attribute groups 'titleTypeSource, titleTypeRef,
|
|
15
|
+
titleTypeVersion, titleTypeAnnotation'; 'subjectTypeSource, subjectTypeRef,
|
|
16
|
+
subjectTypeVersion, subjectTypeAnnotation'; 'descriptionTypeSource, descriptionTypeRef,
|
|
17
|
+
descriptionTypeVersion, descriptionTypeAnnotation'; 'segmentTypeSource, segmentTypeRef,
|
|
18
|
+
segmentTypeVersion, segmentTypeAnnotation'; 'affiliationSource, affiliationRef,
|
|
19
|
+
affiliationVersion, affiliationAnnotation'; and 'partTypeSource, partTypeRef, partTypeVersion, and
|
|
20
|
+
partTypeAnnotation' to allow for the sourcing of information in the 'titleType,' 'subjectType,'
|
|
21
|
+
'descriptionType,' 'segmentType', 'affiliation' and 'partType' attributes.
|
|
22
|
+
- Updated descriptions for all elements and attributes.
|
|
23
|
+
-->
|
|
24
|
+
<!-- the pbcoreCollection root element -->
|
|
25
|
+
<xsd:element name="pbcoreCollection" type="pbcoreCollectionType">
|
|
26
|
+
<xsd:annotation>
|
|
27
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreCollection element groups
|
|
28
|
+
multiple pbcoreDescriptionDocument XML into one container element to allow for a
|
|
29
|
+
serialized output. Uses might include API returns or other web service
|
|
30
|
+
output.</xsd:documentation>
|
|
31
|
+
<xsd:documentation xml:lang="en">Best practice: This element is not intended to be
|
|
32
|
+
equivalent to the archive/library concept of a 'collection.' Please see
|
|
33
|
+
pbcoreAssetType for information on how PBCore can be used to express information
|
|
34
|
+
about collections. The element is only applicable to XML expressions of PBCore. This
|
|
35
|
+
container enables a similar function to RSS; pbcoreCollection would be similar to
|
|
36
|
+
rss:channel and pbcoreDescription document to rss:item.</xsd:documentation>
|
|
37
|
+
</xsd:annotation>
|
|
38
|
+
</xsd:element>
|
|
39
|
+
<!-- the pbcoreDescriptionDocument root element -->
|
|
40
|
+
<xsd:element name="pbcoreDescriptionDocument" type="pbcoreDescriptionDocumentType">
|
|
41
|
+
<xsd:annotation>
|
|
42
|
+
<xsd:documentation xml:lang="en">Definition: the pbcoreDescriptionDocument element is a
|
|
43
|
+
root XML element for the expression of an individual PBCore record.
|
|
44
|
+
pbcoreDescriptionDocument can be used to express intellectual content only (e.g. a
|
|
45
|
+
series or collection level record with no associated instantiations), or
|
|
46
|
+
intellectual content with one or more instantiations (e.g. an episode of a program
|
|
47
|
+
with copies/instantiations on videotape and digital file). This element is only
|
|
48
|
+
applicable to XML expressions of PBCore.</xsd:documentation>
|
|
49
|
+
</xsd:annotation>
|
|
50
|
+
</xsd:element>
|
|
51
|
+
<!-- the pbcoreInstantiationDocument root element -->
|
|
52
|
+
<xsd:element name="pbcoreInstantiationDocument" type="instantiationType">
|
|
53
|
+
<xsd:annotation>
|
|
54
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreInstantiation element is the
|
|
55
|
+
equivalent of the instantiation element, but used for the expression of an
|
|
56
|
+
instantiation record at the root of an XML document. This is most commonly used when
|
|
57
|
+
referenced from other schemas, or if you want to create and express a single,
|
|
58
|
+
stand-alone instantiation.</xsd:documentation>
|
|
59
|
+
<xsd:documentation xml:lang="en">Best practice: This is most commonly used when
|
|
60
|
+
Intellectual Content (in other words, descriptive metadata) is not expressed using
|
|
61
|
+
PBCore, but rather another standard such as MODS or Dublin Core.</xsd:documentation>
|
|
62
|
+
</xsd:annotation>
|
|
63
|
+
</xsd:element>
|
|
64
|
+
<!-- the pbcoreCollectionType -->
|
|
65
|
+
<xsd:complexType name="pbcoreCollectionType">
|
|
66
|
+
<xsd:annotation>
|
|
67
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreCollectionType schema type allows
|
|
68
|
+
the addition of attributes that describe the PBCoreCollection. The attributes define
|
|
69
|
+
the title, the description, the source, the reference and the date of the
|
|
70
|
+
collection.</xsd:documentation>
|
|
71
|
+
</xsd:annotation>
|
|
72
|
+
<xsd:sequence>
|
|
73
|
+
<xsd:element maxOccurs="unbounded" minOccurs="1" ref="pbcoreDescriptionDocument">
|
|
74
|
+
<xsd:annotation>
|
|
75
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreDescriptionDocument
|
|
76
|
+
element assembles together all of PBCore knowledge items into a single data
|
|
77
|
+
record organized in a hierarchical structure. For PBCore these knowledge
|
|
78
|
+
items are metadata descriptions of media, including all the knowledge items
|
|
79
|
+
and metadata terms and values associated with its content and
|
|
80
|
+
containers.</xsd:documentation>
|
|
81
|
+
</xsd:annotation>
|
|
82
|
+
</xsd:element>
|
|
83
|
+
</xsd:sequence>
|
|
84
|
+
<xsd:attribute name="collectionTitle" type="xsd:string">
|
|
85
|
+
<xsd:annotation>
|
|
86
|
+
<xsd:documentation xml:lang="en">Definition: The collectionTitle attribute is a
|
|
87
|
+
title or label for the group of individual serialized XML records contained
|
|
88
|
+
within one pbcoreCollection element.</xsd:documentation>
|
|
89
|
+
</xsd:annotation>
|
|
90
|
+
</xsd:attribute>
|
|
91
|
+
<xsd:attribute name="collectionDescription" type="xsd:string">
|
|
92
|
+
<xsd:annotation>
|
|
93
|
+
<xsd:documentation xml:lang="en">Definition: The collectionDescription attribute is
|
|
94
|
+
a description group of individual serialized XML records contained within one
|
|
95
|
+
pbcoreCollection element.</xsd:documentation>
|
|
96
|
+
</xsd:annotation>
|
|
97
|
+
</xsd:attribute>
|
|
98
|
+
<xsd:attribute name="collectionSource" type="xsd:string">
|
|
99
|
+
<xsd:annotation>
|
|
100
|
+
<xsd:documentation xml:lang="en">Definition: The collectionSource attribute
|
|
101
|
+
indicates an organization, application, or individual for group of individual
|
|
102
|
+
XML records contained within a pbcoreCollection element.</xsd:documentation>
|
|
103
|
+
</xsd:annotation>
|
|
104
|
+
</xsd:attribute>
|
|
105
|
+
<xsd:attribute name="collectionRef" type="xsd:string">
|
|
106
|
+
<xsd:annotation>
|
|
107
|
+
<xsd:documentation xml:lang="en">Definition: The collectionRef attribute provides a
|
|
108
|
+
URL for the source organization, application, or individual for a group of XML
|
|
109
|
+
records contained within a pbcoreCollection element.</xsd:documentation>
|
|
110
|
+
</xsd:annotation>
|
|
111
|
+
</xsd:attribute>
|
|
112
|
+
<xsd:attribute name="collectionDate" type="xsd:string">
|
|
113
|
+
<xsd:annotation>
|
|
114
|
+
<xsd:documentation xml:lang="en">Definition: The collectionDate attribute provides
|
|
115
|
+
the date of of creation for a pbcoreCollection XML document.</xsd:documentation>
|
|
116
|
+
</xsd:annotation>
|
|
117
|
+
</xsd:attribute>
|
|
118
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
119
|
+
</xsd:complexType>
|
|
120
|
+
<!-- pbcoreDescriptionDocumentType -->
|
|
121
|
+
<xsd:complexType name="pbcoreDescriptionDocumentType">
|
|
122
|
+
<xsd:annotation>
|
|
123
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreDescriptionDocumentType schema
|
|
124
|
+
type allows its use as a single asset or repeated use in the
|
|
125
|
+
pbcoreCollection.</xsd:documentation>
|
|
126
|
+
</xsd:annotation>
|
|
127
|
+
<xsd:sequence>
|
|
128
|
+
<!-- the pbcore asset type -->
|
|
129
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreAssetType"
|
|
130
|
+
type="sourceVersionStringType">
|
|
131
|
+
<xsd:annotation>
|
|
132
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreAssetType element is a
|
|
133
|
+
broad definition of the type of intellectual content being described. Asset
|
|
134
|
+
types might include those without associated instantiations (a collection or
|
|
135
|
+
series), or those with instantiations (programs, episodes, clips, etc.)" </xsd:documentation>
|
|
136
|
+
<xsd:documentation xml:lang="en">Best practice: The asset type should broadly
|
|
137
|
+
describe all related instantiations -- for example, if an asset includes
|
|
138
|
+
many instantiations representing different generations of a program, the
|
|
139
|
+
asset type 'program' remains accurate for all of them." </xsd:documentation>
|
|
140
|
+
</xsd:annotation>
|
|
141
|
+
</xsd:element>
|
|
142
|
+
<!-- the pbcore asset date - this element may occur many times with different date types -->
|
|
143
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreAssetDate"
|
|
144
|
+
type="dateStringType">
|
|
145
|
+
<xsd:annotation>
|
|
146
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreAssetDate element is
|
|
147
|
+
intended to reflect dates associated with the Intellectual
|
|
148
|
+
Content.</xsd:documentation>
|
|
149
|
+
<xsd:documentation xml:lang="en">Best practice: By contrast, instantiationDate
|
|
150
|
+
is intended to reflect date information for the specific instance. For
|
|
151
|
+
example, if you have a VHS copy of Gone With The Wind, the pbcoreAssetDate
|
|
152
|
+
would be 1939, while the instantiationDate of the VHS copy could be 1985.
|
|
153
|
+
pbcoreAssetDate may also be used to reflect availability dates, etc. Date
|
|
154
|
+
types should be specified using the @dateType attribute. Dates or time-based
|
|
155
|
+
events related to the content of the asset, on the other hand, would be
|
|
156
|
+
described in the 'coverage' element -- so, while the storyline of Gone with
|
|
157
|
+
the Wind takes place in the nineteenth century, this information should be
|
|
158
|
+
noted in the Coverage field, not the assetDate field. Best practice is to
|
|
159
|
+
use ISO 8601 or some other date/time standard if
|
|
160
|
+
possible.</xsd:documentation>
|
|
161
|
+
</xsd:annotation>
|
|
162
|
+
</xsd:element>
|
|
163
|
+
<!-- the pbcore identifier - this element may occur as many times as
|
|
164
|
+
desired; however, an identifier source attribute is required. -->
|
|
165
|
+
<xsd:element maxOccurs="unbounded" minOccurs="1" name="pbcoreIdentifier"
|
|
166
|
+
type="requiredSourceVersionStringType">
|
|
167
|
+
<xsd:annotation>
|
|
168
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreIdentifier element
|
|
169
|
+
provides an identifier that can apply to the asset. This identifier should
|
|
170
|
+
not be limited to a specific instantiation, but rather is shared by or
|
|
171
|
+
common to all instantiations of an asset. It can also hold a URL or URI that
|
|
172
|
+
points to the asset.</xsd:documentation>
|
|
173
|
+
<xsd:documentation xml:lang="en">Best practice: Identify the asset by means of a
|
|
174
|
+
string or number corresponding to an established or formal identification
|
|
175
|
+
system if one exists. Otherwise, use an identification method that is in use
|
|
176
|
+
within your agency, station, production company, office, or
|
|
177
|
+
institution.</xsd:documentation>
|
|
178
|
+
</xsd:annotation>
|
|
179
|
+
</xsd:element>
|
|
180
|
+
<!-- the pbcore title - this element may occur as many times as
|
|
181
|
+
desired, optionally, a titleType attribute may appear -->
|
|
182
|
+
<xsd:element maxOccurs="unbounded" minOccurs="1" name="pbcoreTitle"
|
|
183
|
+
type="titleStringType">
|
|
184
|
+
<xsd:annotation>
|
|
185
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreTitle element is a name
|
|
186
|
+
or label relevant to the asset.</xsd:documentation>
|
|
187
|
+
<xsd:documentation xml:lang="en">Best practice: An asset may have many types of
|
|
188
|
+
titles, an asset may have, such as a series title, episode title, segment
|
|
189
|
+
title, or project title; therefore the element is
|
|
190
|
+
repeatable.</xsd:documentation>
|
|
191
|
+
</xsd:annotation>
|
|
192
|
+
</xsd:element>
|
|
193
|
+
<!-- the pbcore subject - this element may occur as many times as
|
|
194
|
+
desired, optional attributes can note subjectType as well as time annotations -->
|
|
195
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreSubject"
|
|
196
|
+
type="subjectStringType">
|
|
197
|
+
<xsd:annotation>
|
|
198
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreSubject element is used
|
|
199
|
+
to assign topic headings or keywords that portray the intellectual content
|
|
200
|
+
of the asset. A subject is expressed by keywords, key phrases, or even
|
|
201
|
+
specific classification codes. Controlled vocabularies, authorities, formal
|
|
202
|
+
classification codes, as well as folksonomies and user-generated tags, may
|
|
203
|
+
be employed when assigning descriptive subject terms.</xsd:documentation>
|
|
204
|
+
</xsd:annotation>
|
|
205
|
+
</xsd:element>
|
|
206
|
+
<!-- the pbcore description - this element may occur as many times
|
|
207
|
+
as desired, however if it does occur, then a description tag is
|
|
208
|
+
required. optionally, the description type may appear - but
|
|
209
|
+
it has a limited vocabulary -->
|
|
210
|
+
<xsd:element maxOccurs="unbounded" minOccurs="1" name="pbcoreDescription"
|
|
211
|
+
type="descriptionStringType">
|
|
212
|
+
<xsd:annotation>
|
|
213
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreDescription element uses
|
|
214
|
+
free-form text or a narrative to report general notes, abstracts, or
|
|
215
|
+
summaries about the intellectual content of an asset. The information may be
|
|
216
|
+
in the form of an individual program description, anecdotal interpretations,
|
|
217
|
+
or brief content reviews. The description may also consist of outlines,
|
|
218
|
+
lists, bullet points, rundowns, edit decision lists, indexes, or tables of
|
|
219
|
+
content.</xsd:documentation>
|
|
220
|
+
</xsd:annotation>
|
|
221
|
+
</xsd:element>
|
|
222
|
+
<!-- the pbcore genre - this element may occur as many times as desired. -->
|
|
223
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreGenre"
|
|
224
|
+
type="sourceVersionStartEndStringType">
|
|
225
|
+
<xsd:annotation>
|
|
226
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreGenre element describes
|
|
227
|
+
the Genre of the asset, which can be defined as a categorical description
|
|
228
|
+
informed by the topical nature or a particular style or form of the
|
|
229
|
+
content.</xsd:documentation>
|
|
230
|
+
<xsd:documentation xml:lang="en">Best practice: Genre refers to the intellectual
|
|
231
|
+
content of the asset, whereas the element pbcoreAssetType defines a broader
|
|
232
|
+
structural category; i.e. an asset might have the Asset Type of Segment,
|
|
233
|
+
with a Genre of News, together defining a news segment.</xsd:documentation>
|
|
234
|
+
</xsd:annotation>
|
|
235
|
+
</xsd:element>
|
|
236
|
+
<!-- the pbcore relation - this element may occur as many times as
|
|
237
|
+
desired. -->
|
|
238
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreRelation">
|
|
239
|
+
<xsd:annotation>
|
|
240
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreRelation element contains
|
|
241
|
+
the pbcoreRelationType and pbcoreRelationIdentifier elements. In order to
|
|
242
|
+
properly use these two elements they must be nested with the pbcoreRelation
|
|
243
|
+
element, and pbcoreRelation must contain both pbcoreRelationType and
|
|
244
|
+
pbcoreRelationIdentifier if it is included.</xsd:documentation>
|
|
245
|
+
</xsd:annotation>
|
|
246
|
+
<xsd:complexType>
|
|
247
|
+
<xsd:sequence>
|
|
248
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="pbcoreRelationType"
|
|
249
|
+
type="sourceVersionStringType">
|
|
250
|
+
<xsd:annotation>
|
|
251
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreRelationType
|
|
252
|
+
element describes the relationship between the asset being
|
|
253
|
+
describe by the pbcore document and any other asset. Ideally it
|
|
254
|
+
would contain text from a controlled vocabulary for describing
|
|
255
|
+
relationships. There is some depth to what a relationship could
|
|
256
|
+
be. The assets can be related as different episodes in a series,
|
|
257
|
+
different tapes in a box set, or different versions of an
|
|
258
|
+
original, among others.</xsd:documentation>
|
|
259
|
+
<xsd:documentation xml:lang="en">Best practice: The assets may be
|
|
260
|
+
related in that they are different discrete parts of a single
|
|
261
|
+
intellectual unit, one may be a derivative of another, or they
|
|
262
|
+
may be different versions that are distinct enough to be
|
|
263
|
+
described as separate assets.</xsd:documentation>
|
|
264
|
+
</xsd:annotation>
|
|
265
|
+
</xsd:element>
|
|
266
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="pbcoreRelationIdentifier"
|
|
267
|
+
type="sourceVersionStringType">
|
|
268
|
+
<xsd:annotation>
|
|
269
|
+
<xsd:documentation xml:lang="en">Definition: The
|
|
270
|
+
pbcoreRelationIdentifier element contains the identifier of the
|
|
271
|
+
related asset. In the case that the related asset has a PBCore
|
|
272
|
+
record, this identifier should correspond with the
|
|
273
|
+
pbcoreIdentifier of the related asset. However, it is possible
|
|
274
|
+
to use this element with a record that isn't in PBCore, in which
|
|
275
|
+
case the source attribute should identify the source of the
|
|
276
|
+
identifier.</xsd:documentation>
|
|
277
|
+
</xsd:annotation>
|
|
278
|
+
</xsd:element>
|
|
279
|
+
</xsd:sequence>
|
|
280
|
+
</xsd:complexType>
|
|
281
|
+
</xsd:element>
|
|
282
|
+
<!-- the pbcore coverage - this element may occur as many times as
|
|
283
|
+
desired, and within it a Spatial or a Temporal coverageType -->
|
|
284
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreCoverage">
|
|
285
|
+
<xsd:annotation>
|
|
286
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreCoverage element is a
|
|
287
|
+
container for sub-elements 'coverage' and
|
|
288
|
+
'coverageType'.</xsd:documentation>
|
|
289
|
+
</xsd:annotation>
|
|
290
|
+
<xsd:complexType>
|
|
291
|
+
<xsd:sequence>
|
|
292
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="coverage"
|
|
293
|
+
type="sourceVersionStartEndStringType">
|
|
294
|
+
<xsd:annotation>
|
|
295
|
+
<xsd:documentation xml:lang="en">Definition: The coverage element
|
|
296
|
+
refers to either the geographic location or the time period
|
|
297
|
+
covered by the asset's intellectual content. For geographic
|
|
298
|
+
locations ('spatial' descriptors), it is expressed by keywords
|
|
299
|
+
such as place names (e.g. 'Alaska' or 'Washington, DC'), numeric
|
|
300
|
+
coordinates or geo-spatial data. For time-based events
|
|
301
|
+
('temporal' descriptors), it is expressed by using a date,
|
|
302
|
+
period, era, or time-based event that is portrayed or covered in
|
|
303
|
+
the intellectual content (e.g. '2007' or 'Victorian Era'). The
|
|
304
|
+
PBCore metadata element coverage houses the actual spatial or
|
|
305
|
+
temporal keywords. The companion element coverageType is used to
|
|
306
|
+
identify the type of keywords that are being
|
|
307
|
+
used.</xsd:documentation>
|
|
308
|
+
</xsd:annotation>
|
|
309
|
+
</xsd:element>
|
|
310
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="coverageType">
|
|
311
|
+
<xsd:annotation>
|
|
312
|
+
<xsd:documentation xml:lang="en">Definition: The coverageType
|
|
313
|
+
element is used to identify the actual type of keywords that are
|
|
314
|
+
being used by its companion metadata element coverage.
|
|
315
|
+
coverageType provides a picklist of two possible types - spatial
|
|
316
|
+
or temporal - because coverage in intellectual content may be
|
|
317
|
+
expressed spatially by geographic location or it may also be
|
|
318
|
+
expressed temporally by a date, period, era, or time-based
|
|
319
|
+
event." </xsd:documentation>
|
|
320
|
+
</xsd:annotation>
|
|
321
|
+
<xsd:simpleType>
|
|
322
|
+
<xsd:restriction base="xsd:string">
|
|
323
|
+
<xsd:enumeration value="Spatial"/>
|
|
324
|
+
<xsd:enumeration value="Temporal"/>
|
|
325
|
+
</xsd:restriction>
|
|
326
|
+
</xsd:simpleType>
|
|
327
|
+
</xsd:element>
|
|
328
|
+
</xsd:sequence>
|
|
329
|
+
</xsd:complexType>
|
|
330
|
+
</xsd:element>
|
|
331
|
+
<!-- the pbcore audienceLevel - this may occur as many times as desired
|
|
332
|
+
within the document -->
|
|
333
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreAudienceLevel"
|
|
334
|
+
type="sourceVersionStringType">
|
|
335
|
+
<xsd:annotation>
|
|
336
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreAudienceLevel element
|
|
337
|
+
identifies a type of audience, viewer, or listener for whom the media item
|
|
338
|
+
is primarily designed or educationally useful.</xsd:documentation>
|
|
339
|
+
</xsd:annotation>
|
|
340
|
+
</xsd:element>
|
|
341
|
+
<!-- the pbcore audienceRating - this may occur as many times as desired
|
|
342
|
+
within the document -->
|
|
343
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreAudienceRating"
|
|
344
|
+
type="sourceVersionStringType">
|
|
345
|
+
<xsd:annotation>
|
|
346
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreAudienceRating element
|
|
347
|
+
designates the type of users for whom the intellectual content of a media
|
|
348
|
+
item is intended or judged appropriate. This element differs from the
|
|
349
|
+
element pbcoreAudienceLevel in that it utilizes standard ratings that have
|
|
350
|
+
been crafted by the broadcast television and film industries and that are
|
|
351
|
+
used as flags for audience or age-appropriate materials.</xsd:documentation>
|
|
352
|
+
</xsd:annotation>
|
|
353
|
+
</xsd:element>
|
|
354
|
+
<!-- the pbcore creator - may appear as many times as
|
|
355
|
+
necessary, but when it does appear, the creator tag is required. the
|
|
356
|
+
creatorRole tag is optional. -->
|
|
357
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreCreator">
|
|
358
|
+
<xsd:annotation>
|
|
359
|
+
<xsd:documentation xml:lang="en">The pbcoreCreator element is a container for
|
|
360
|
+
sub-elements 'creator' and 'creatorRole'.</xsd:documentation>
|
|
361
|
+
</xsd:annotation>
|
|
362
|
+
<xsd:complexType>
|
|
363
|
+
<xsd:sequence>
|
|
364
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="creator"
|
|
365
|
+
type="affiliatedStringType">
|
|
366
|
+
<xsd:annotation>
|
|
367
|
+
<xsd:documentation xml:lang="en">Definition: The creator element
|
|
368
|
+
identifies the primary person, people, or organization(s)
|
|
369
|
+
responsible for creating the asset. Note that non-primary names
|
|
370
|
+
and roles should be included within the pbcoreContributor
|
|
371
|
+
container. Best practice: We recommend providing a consistent
|
|
372
|
+
internal standard for entering proper names and organizational
|
|
373
|
+
names, such as 'Last name, First name, Middle name,' or 'Main
|
|
374
|
+
group, subdivision.' We also recommend supplying separate
|
|
375
|
+
pbcoreCreator containers for each creator to be named for a
|
|
376
|
+
resource. </xsd:documentation>
|
|
377
|
+
</xsd:annotation>
|
|
378
|
+
</xsd:element>
|
|
379
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="creatorRole"
|
|
380
|
+
type="sourceVersionStringType">
|
|
381
|
+
<xsd:annotation>
|
|
382
|
+
<xsd:documentation xml:lang="en">Definition: The creatorRole element
|
|
383
|
+
is used to identify the role played by the person, people or
|
|
384
|
+
organization(s) identified in the companion descriptor creator.
|
|
385
|
+
The PBCore schema allows for creatorRole to be repeated in the
|
|
386
|
+
pbcoreCreator container element. This can be useful when a
|
|
387
|
+
single person or organization is associated with multiple roles
|
|
388
|
+
in an asset.</xsd:documentation>
|
|
389
|
+
</xsd:annotation>
|
|
390
|
+
</xsd:element>
|
|
391
|
+
</xsd:sequence>
|
|
392
|
+
</xsd:complexType>
|
|
393
|
+
</xsd:element>
|
|
394
|
+
<!-- the pbcore contributor - this element may appear as many times
|
|
395
|
+
as necessary, but when it does appear, the contributor tag must
|
|
396
|
+
appear inside it. the contributor role is optional. -->
|
|
397
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreContributor">
|
|
398
|
+
<xsd:annotation>
|
|
399
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreContributor element is a
|
|
400
|
+
container for sub-elements 'contributor' and
|
|
401
|
+
'contributorRole'.</xsd:documentation>
|
|
402
|
+
</xsd:annotation>
|
|
403
|
+
<xsd:complexType>
|
|
404
|
+
<xsd:sequence>
|
|
405
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="contributor"
|
|
406
|
+
type="affiliatedStringType">
|
|
407
|
+
<xsd:annotation>
|
|
408
|
+
<xsd:documentation xml:lang="en">Definition: The contributor element
|
|
409
|
+
identifies a person, people, or organization that has made
|
|
410
|
+
substantial creative contributions to the asset. This
|
|
411
|
+
contribution is considered to be secondary to the primary
|
|
412
|
+
author(s) (person or organization) identified in the descriptor
|
|
413
|
+
creator. Best practice: We recommend providing a consistent
|
|
414
|
+
internal standard for entering proper names and organizational
|
|
415
|
+
names, such as 'Last name, First name, Middle name,' or 'Main
|
|
416
|
+
group, subdivision.' We also recommend supplying separate
|
|
417
|
+
pbcoreCreator containers for each creator to be named for a
|
|
418
|
+
resource.</xsd:documentation>
|
|
419
|
+
</xsd:annotation>
|
|
420
|
+
</xsd:element>
|
|
421
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="contributorRole"
|
|
422
|
+
type="contributorStringType">
|
|
423
|
+
<xsd:annotation>
|
|
424
|
+
<xsd:documentation xml:lang="en">Definition: The contributorRole
|
|
425
|
+
element is used to identify the role played by the person,
|
|
426
|
+
people or organizations identified in the companion element
|
|
427
|
+
contributor. The PBCore schema allows for contributorRole to be
|
|
428
|
+
repeated in the pbcoreContributor container element. This can be
|
|
429
|
+
useful when a single person or organization is associated with
|
|
430
|
+
multiple roles in an asset.</xsd:documentation>
|
|
431
|
+
</xsd:annotation>
|
|
432
|
+
</xsd:element>
|
|
433
|
+
</xsd:sequence>
|
|
434
|
+
</xsd:complexType>
|
|
435
|
+
</xsd:element>
|
|
436
|
+
<!-- the pbcore publisher - this follows the same guidelines as the
|
|
437
|
+
contributor and the creator. this may exist as many times as
|
|
438
|
+
we wish, but inside it there must be a publisher tag. a
|
|
439
|
+
publisherRole tag is optional. -->
|
|
440
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcorePublisher">
|
|
441
|
+
<xsd:annotation>
|
|
442
|
+
<xsd:documentation xml:lang="en">Definition: The pbcorePublisher element is a
|
|
443
|
+
container for sub-elements 'publisher' and
|
|
444
|
+
'publisherRole.'</xsd:documentation>
|
|
445
|
+
</xsd:annotation>
|
|
446
|
+
<xsd:complexType>
|
|
447
|
+
<xsd:sequence>
|
|
448
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="publisher"
|
|
449
|
+
type="affiliatedStringType">
|
|
450
|
+
<xsd:annotation>
|
|
451
|
+
<xsd:documentation xml:lang="en">Definition: The publisher element
|
|
452
|
+
identifies a person, people, or organization primarily
|
|
453
|
+
responsible for distributing or making the asset available to
|
|
454
|
+
others. The publisher may be a person, a business, organization,
|
|
455
|
+
group, project or service. Best practice: We recommend providing
|
|
456
|
+
a consistent internal standard for entering proper names and
|
|
457
|
+
organizational names, such as 'Last name, First name, Middle
|
|
458
|
+
name,' or 'Main group, subdivision.' We also recommend supplying
|
|
459
|
+
separate pbcoreCreator containers for each creator to be named
|
|
460
|
+
for a resource.</xsd:documentation>
|
|
461
|
+
</xsd:annotation>
|
|
462
|
+
</xsd:element>
|
|
463
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="publisherRole"
|
|
464
|
+
type="sourceVersionStringType">
|
|
465
|
+
<xsd:annotation>
|
|
466
|
+
<xsd:documentation xml:lang="en">Definition: The publisherRole
|
|
467
|
+
element is used to identify the role played by the specific
|
|
468
|
+
publisher or publishing entity identified in the companion
|
|
469
|
+
descriptor publisher. The PBCore schema allows for publisherRole
|
|
470
|
+
to be repeated in the pbcorePublisher container element. This
|
|
471
|
+
can be useful when a single person or organization is associated
|
|
472
|
+
with multiple roles in an asset.</xsd:documentation>
|
|
473
|
+
</xsd:annotation>
|
|
474
|
+
</xsd:element>
|
|
475
|
+
</xsd:sequence>
|
|
476
|
+
</xsd:complexType>
|
|
477
|
+
</xsd:element>
|
|
478
|
+
<!-- the pbcore rights - this may appear as many times as needed -->
|
|
479
|
+
<xsd:element name="pbcoreRightsSummary" type="rightsSummaryType" maxOccurs="unbounded"
|
|
480
|
+
minOccurs="0">
|
|
481
|
+
<xsd:annotation>
|
|
482
|
+
<xsd:documentation xml:lang="en">Definition: Th pbcoreRightsSummary element is a
|
|
483
|
+
container for sub-elements 'rightsSummary', 'rightsLink', and
|
|
484
|
+
'rightsEmbedded' used to describe Rights for the asset.</xsd:documentation>
|
|
485
|
+
</xsd:annotation>
|
|
486
|
+
</xsd:element>
|
|
487
|
+
<!-- the pbcore instantiation - this contains all the details on how
|
|
488
|
+
the asset is actualized -->
|
|
489
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreInstantiation"
|
|
490
|
+
type="instantiationType">
|
|
491
|
+
<xsd:annotation>
|
|
492
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationType element
|
|
493
|
+
contains sub-elements that describe a single instantiation of an asset. The
|
|
494
|
+
definition is malleable but it should be thought of as any discreet and
|
|
495
|
+
tangible unit that typically (though not always) comprises a whole
|
|
496
|
+
representation of the asset. For example, an original master videotape, a
|
|
497
|
+
preservation master video file, and a low-bitrate access copy would all be
|
|
498
|
+
considered Instantiations of a single video program. All of the sub-elements
|
|
499
|
+
held by this element are used to describe the instantiation specifically,
|
|
500
|
+
not necessarily the asset as a whole." </xsd:documentation>
|
|
501
|
+
</xsd:annotation>
|
|
502
|
+
</xsd:element>
|
|
503
|
+
<!-- PBCore Annotation -->
|
|
504
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreAnnotation"
|
|
505
|
+
type="annotationStringType">
|
|
506
|
+
<xsd:annotation>
|
|
507
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreAnnotation element allows
|
|
508
|
+
the addition of any supplementary information about the metadata used to
|
|
509
|
+
describe the PBCore record. pbcoreAnnotation clarifies element values,
|
|
510
|
+
terms, descriptors, and vocabularies that may not be otherwise sufficiently
|
|
511
|
+
understood.</xsd:documentation>
|
|
512
|
+
</xsd:annotation>
|
|
513
|
+
</xsd:element>
|
|
514
|
+
<!-- PBCore Part -->
|
|
515
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcorePart" type="pbcorePartType">
|
|
516
|
+
<xsd:annotation>
|
|
517
|
+
<xsd:documentation xml:lang="en">Definition: The pbcorePart element may be used
|
|
518
|
+
to split up a single asset so as to enable the use of all available elements
|
|
519
|
+
at the pbcoreDescriptionDocument level to describe the intellectual content
|
|
520
|
+
of individual segments of an asset." </xsd:documentation>
|
|
521
|
+
<xsd:documentation xml:lang="en">Best practice: Splitting up an asset in this
|
|
522
|
+
way allows for defining and describing segments, stories, episodes or other
|
|
523
|
+
divisions within the asset, such as individual films in a compilation reel,
|
|
524
|
+
or distinct segments of a news show when each may have their own titles,
|
|
525
|
+
creators, publishers, or other specific intellectual content information
|
|
526
|
+
that does not apply across the whole asset.</xsd:documentation>
|
|
527
|
+
</xsd:annotation>
|
|
528
|
+
</xsd:element>
|
|
529
|
+
<!-- PBCore Extension -->
|
|
530
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="pbcoreExtension"
|
|
531
|
+
type="extensionType">
|
|
532
|
+
<xsd:annotation>
|
|
533
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreExtension element can be
|
|
534
|
+
used as either a wrapper containing a specific element from another standard
|
|
535
|
+
OR embedded xml containing the extension.</xsd:documentation>
|
|
536
|
+
<xsd:documentation xml:lang="en">Best practice: Use it to supplement other
|
|
537
|
+
metadata sub-elements of the PBCore description document in which it
|
|
538
|
+
appears.</xsd:documentation>
|
|
539
|
+
</xsd:annotation>
|
|
540
|
+
</xsd:element>
|
|
541
|
+
<!-- For Readability - DescriptionDocument sequence end -->
|
|
542
|
+
</xsd:sequence>
|
|
543
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
544
|
+
<!-- For Readability - DescriptionDocument complexType end -->
|
|
545
|
+
</xsd:complexType>
|
|
546
|
+
<!-- the pbcore instantiationType -->
|
|
547
|
+
<xsd:complexType name="instantiationType">
|
|
548
|
+
<xsd:annotation>
|
|
549
|
+
<xsd:documentation xml:lang="en">Definition: The pbcoreinstantiationType schema type
|
|
550
|
+
uses a common structure to allow for a single instantiation or multiple
|
|
551
|
+
instantiations within a pbcoreDocumentDescription.</xsd:documentation>
|
|
552
|
+
</xsd:annotation>
|
|
553
|
+
<xsd:sequence>
|
|
554
|
+
<!-- the pbcore instantiationIdentifier -->
|
|
555
|
+
<xsd:element maxOccurs="unbounded" minOccurs="1" name="instantiationIdentifier"
|
|
556
|
+
type="requiredSourceVersionStringType">
|
|
557
|
+
<xsd:annotation>
|
|
558
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationIdentifier element
|
|
559
|
+
contains an unambiguous reference or identifier for a particular
|
|
560
|
+
instantiation of an asset.</xsd:documentation>
|
|
561
|
+
<xsd:documentation xml:lang="en">Best practice: Identify the media item (whether
|
|
562
|
+
analog or digital) by means of a string or number corresponding to an
|
|
563
|
+
established or formal identification system if one exists. Otherwise, use an
|
|
564
|
+
identification method that is in use within your agency, station, production
|
|
565
|
+
company, office, or institution.</xsd:documentation>
|
|
566
|
+
</xsd:annotation>
|
|
567
|
+
</xsd:element>
|
|
568
|
+
<!-- the pbcore instantiationDate -->
|
|
569
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="instantiationDate"
|
|
570
|
+
type="dateStringType">
|
|
571
|
+
<xsd:annotation>
|
|
572
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationDate element is a
|
|
573
|
+
date associated with an instantiation.</xsd:documentation>
|
|
574
|
+
<xsd:documentation xml:lang="en">Best practice: Use ISO 8601 or some other
|
|
575
|
+
date/time standard if possible.</xsd:documentation>
|
|
576
|
+
</xsd:annotation>
|
|
577
|
+
</xsd:element>
|
|
578
|
+
<!-- the pbcore instantiationDimensions -->
|
|
579
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="instantiationDimensions"
|
|
580
|
+
type="technicalStringType">
|
|
581
|
+
<xsd:annotation>
|
|
582
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationDimensions element
|
|
583
|
+
specifies either the dimensions of a physical instantiation, or the
|
|
584
|
+
high-level visual dimensions of a digital instantiation.</xsd:documentation>
|
|
585
|
+
<xsd:documentation xml:lang="en">Best practice: For physical dimensions, usage
|
|
586
|
+
examples might be 7" for an audio reel. When describing visual dimensions,
|
|
587
|
+
use this for high-level descriptors such as 1080p. Use the element frameSize
|
|
588
|
+
to describe the pixel dimensions of a visual resource.</xsd:documentation>
|
|
589
|
+
</xsd:annotation>
|
|
590
|
+
</xsd:element>
|
|
591
|
+
<!-- the pbcore instantiationPhysical -->
|
|
592
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationPhysical"
|
|
593
|
+
type="sourceVersionStringType">
|
|
594
|
+
<xsd:annotation>
|
|
595
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationPhysical element
|
|
596
|
+
is used to identify the format of a particular instantiation as it exists in
|
|
597
|
+
a physical form that occupies physical space (e.g., a tape on a shelf). This
|
|
598
|
+
includes physical digital media, such as a DV tape, audio CD or authored
|
|
599
|
+
DVD, as well as analog media.</xsd:documentation>
|
|
600
|
+
<xsd:documentation xml:lang="en">Best practice: PBCore provides a controlled
|
|
601
|
+
vocabulary for media objects, though any controlled vocabulary can be used
|
|
602
|
+
as long as it is referenced. For digital storage carriers that contain
|
|
603
|
+
portable file-based media, such as data CDs, LTO tapes or hard drives, use
|
|
604
|
+
instantiationDigital to convey the mime type of the file instead of
|
|
605
|
+
describing the carrier.</xsd:documentation>
|
|
606
|
+
</xsd:annotation>
|
|
607
|
+
</xsd:element>
|
|
608
|
+
<!-- the pbcore instantiationDigital -->
|
|
609
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationDigital"
|
|
610
|
+
type="sourceVersionStringType">
|
|
611
|
+
<xsd:annotation>
|
|
612
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationDigital element is
|
|
613
|
+
used to identify the format of a particular instantiation of an asset as it
|
|
614
|
+
exists as a digital file on a server, hard drive, or other digital storage
|
|
615
|
+
medium. Digital instantiations should be expressed as a formal Internet MIME
|
|
616
|
+
types.</xsd:documentation>
|
|
617
|
+
<xsd:documentation xml:lang="en">Best practice: instantiationDigital should only
|
|
618
|
+
be used to describe the MIME type of the digital file itself. There are
|
|
619
|
+
multiple options to convey more information about the storage medium or
|
|
620
|
+
location of the digital file, which are discussed in more detail on the
|
|
621
|
+
PBCore site.</xsd:documentation>
|
|
622
|
+
</xsd:annotation>
|
|
623
|
+
</xsd:element>
|
|
624
|
+
<!-- the pbcore instantiationStandard -->
|
|
625
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationStandard"
|
|
626
|
+
type="instantiationStandardStringType">
|
|
627
|
+
<xsd:annotation>
|
|
628
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationStandard element +
|
|
629
|
+
can be used, if the instantiation is a physical item, to refer to the
|
|
630
|
+
broadcast standard of the video signal (e.g. NTSC, PAL), or the audio
|
|
631
|
+
encoding (e.g. Dolby A, vertical cut). If the instantiation is a digital
|
|
632
|
+
item, instantiationStandard should be used to express the container format
|
|
633
|
+
of the digital file (e.g. MXF).</xsd:documentation>
|
|
634
|
+
<xsd:documentation xml:lang="en">Best practice: While the usage described in the
|
|
635
|
+
definition is best practice for 2.1, this usage is likely to change if new
|
|
636
|
+
elements are added for PBCore 3.0.</xsd:documentation>
|
|
637
|
+
</xsd:annotation>
|
|
638
|
+
</xsd:element>
|
|
639
|
+
<!-- the pbcore instantiationLocation -->
|
|
640
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="instantiationLocation"
|
|
641
|
+
type="sourceVersionStringType">
|
|
642
|
+
<xsd:annotation>
|
|
643
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationLocation element
|
|
644
|
+
may contain information about a specific location for an instantiation, such
|
|
645
|
+
as an organization's name, departmental name, shelf ID and contact
|
|
646
|
+
information. The instantiationLocation for a digital file should include
|
|
647
|
+
domain, path or URI to the file.</xsd:documentation>
|
|
648
|
+
<xsd:documentation xml:lang="en">Best practice: For digital files,
|
|
649
|
+
instantiationLocation should always include a path or URI to the file. There
|
|
650
|
+
are multiple ways to convey additional information about the location of a
|
|
651
|
+
carrier or storage medium of the digital file, which are expressed on the
|
|
652
|
+
PBCore site.</xsd:documentation>
|
|
653
|
+
</xsd:annotation>
|
|
654
|
+
</xsd:element>
|
|
655
|
+
<!-- the pbcore instantiationmMediaType -->
|
|
656
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationMediaType"
|
|
657
|
+
type="sourceVersionStringType">
|
|
658
|
+
<xsd:annotation>
|
|
659
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationMediaType element
|
|
660
|
+
identifies the general, high level nature of the content of an
|
|
661
|
+
instantiation. It uses categories that show how content is presented to an
|
|
662
|
+
observer, e.g., as a sound, text or moving image.</xsd:documentation>
|
|
663
|
+
</xsd:annotation>
|
|
664
|
+
</xsd:element>
|
|
665
|
+
<!-- the pbcore instantiationGenerations -->
|
|
666
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="instantiationGenerations"
|
|
667
|
+
type="sourceVersionStringType">
|
|
668
|
+
<xsd:annotation>
|
|
669
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationGeneration element
|
|
670
|
+
identifies the use type and provenance of the instantiation. The generation
|
|
671
|
+
of a video tape may be an "Original Master" or "Dub", the generation of a
|
|
672
|
+
film reel may be an "Original Negative" or "Composite Positive", an
|
|
673
|
+
audiotape may be a "Master" or "Mix Element", an image may be a "Photograph"
|
|
674
|
+
or a "Photocopy.</xsd:documentation>
|
|
675
|
+
</xsd:annotation>
|
|
676
|
+
</xsd:element>
|
|
677
|
+
<!-- the pbcore instantiationFileSize -->
|
|
678
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationFileSize"
|
|
679
|
+
type="technicalStringType">
|
|
680
|
+
<xsd:annotation>
|
|
681
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationFileSize element
|
|
682
|
+
indicates the file size of a digital instantiation. It should contain only
|
|
683
|
+
numerical values. As a standard, express the file size in bytes. Units of
|
|
684
|
+
Measure should be declared in the unitsOfMeasure
|
|
685
|
+
attribute.</xsd:documentation>
|
|
686
|
+
</xsd:annotation>
|
|
687
|
+
</xsd:element>
|
|
688
|
+
<!-- the pbcore instantiationTimeStart -->
|
|
689
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationTimeStart"
|
|
690
|
+
type="sourceVersionStringType">
|
|
691
|
+
<xsd:annotation>
|
|
692
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationTimeStart element
|
|
693
|
+
describes the point at which playback begins for a time-based instantiation.
|
|
694
|
+
It is likely that the content on a tape may begin an arbitrary amount of
|
|
695
|
+
time after the beginning of the instantiation. Best practice is to use a
|
|
696
|
+
timestamp format such as HH:MM:SS[:|;]FF or HH:MM:SS.mmm or
|
|
697
|
+
S.mmm.</xsd:documentation>
|
|
698
|
+
</xsd:annotation>
|
|
699
|
+
</xsd:element>
|
|
700
|
+
<!-- the pbcore instantiationDuration -->
|
|
701
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationDuration"
|
|
702
|
+
type="sourceVersionStringType">
|
|
703
|
+
<xsd:annotation>
|
|
704
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationDuration element
|
|
705
|
+
provides a timestamp for the overall length or duration of a time-based
|
|
706
|
+
media item. It represents the playback time. Best practice is to use a
|
|
707
|
+
timestamp format such as HH:MM:SS[:|;]FF or HH:MM:SS.mmm or
|
|
708
|
+
S.mmm.</xsd:documentation>
|
|
709
|
+
</xsd:annotation>
|
|
710
|
+
</xsd:element>
|
|
711
|
+
<!-- the pbcore instantiationDataRate -->
|
|
712
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationDataRate"
|
|
713
|
+
type="technicalStringType">
|
|
714
|
+
<xsd:annotation>
|
|
715
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationDataRate element
|
|
716
|
+
expresses the amount of data in a digital media file that is encoded,
|
|
717
|
+
delivered or distributed, for every second of time. This should be expressed
|
|
718
|
+
as numerical data, with the units of measure declared in the unitsOfMeasure
|
|
719
|
+
attribute. For example, if the audio file is 56 kilobits/second, then 56
|
|
720
|
+
should be the value of instantiationDataRate and the attribute
|
|
721
|
+
unitsOfMeasure should be kilobits/second.</xsd:documentation>
|
|
722
|
+
</xsd:annotation>
|
|
723
|
+
</xsd:element>
|
|
724
|
+
<!-- the pbcore instantiationColors -->
|
|
725
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationColors"
|
|
726
|
+
type="sourceVersionStringType">
|
|
727
|
+
<xsd:annotation>
|
|
728
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationColors element
|
|
729
|
+
indicates the overall color, grayscale, or black and white nature of the
|
|
730
|
+
presentation of an instantiation, as a single occurrence or combination of
|
|
731
|
+
occurrences in or throughout the instantiation.</xsd:documentation>
|
|
732
|
+
</xsd:annotation>
|
|
733
|
+
</xsd:element>
|
|
734
|
+
<!-- the pbcore instantiationTracks -->
|
|
735
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationTracks"
|
|
736
|
+
type="sourceVersionStringType">
|
|
737
|
+
<xsd:annotation>
|
|
738
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationTracks element is
|
|
739
|
+
simply intended to indicate the number and type of tracks that are found in
|
|
740
|
+
a media item, whether it is analog or digital. (e.g. 1 video track, 2 audio
|
|
741
|
+
tracks, 1 text track, 1 sprite track, etc.) Other configuration information
|
|
742
|
+
specific to these identified tracks should be described using
|
|
743
|
+
instantiationChannelConfiguration.</xsd:documentation>
|
|
744
|
+
<xsd:documentation xml:lang="en">Best practice: Best practices is to use
|
|
745
|
+
essenceTracks, as this element has been deprecated.</xsd:documentation>
|
|
746
|
+
</xsd:annotation>
|
|
747
|
+
</xsd:element>
|
|
748
|
+
<!-- the pbcore instantiationChannelConfiguration -->
|
|
749
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationChannelConfiguration"
|
|
750
|
+
type="sourceVersionStringType">
|
|
751
|
+
<xsd:annotation>
|
|
752
|
+
<xsd:documentation xml:lang="en">Definition: The
|
|
753
|
+
instantiationChannelConfiguration element is designed to indicate, at a
|
|
754
|
+
general narrative level, the arrangement or configuration of specific
|
|
755
|
+
channels or layers of information within an instantiation's tracks. Examples
|
|
756
|
+
are 2-track mono, 8- track stereo, or video track with alpha
|
|
757
|
+
channel.</xsd:documentation>
|
|
758
|
+
</xsd:annotation>
|
|
759
|
+
</xsd:element>
|
|
760
|
+
<!-- the pbcore instantiationLanguage -->
|
|
761
|
+
<xsd:element name="instantiationLanguage" type="threeLetterStringType"
|
|
762
|
+
maxOccurs="unbounded" minOccurs="0">
|
|
763
|
+
<xsd:annotation>
|
|
764
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationLanguage element
|
|
765
|
+
identifies the primary language of the tracks’ audio or text. Languages must
|
|
766
|
+
be indicated using 3-letter codes standardized in ISO 639-2 or 639-3. If an
|
|
767
|
+
instantiation includes more than one language, the element can be repeated.
|
|
768
|
+
Alternately, both languages can be expressed in one element by separating
|
|
769
|
+
two three-letter codes with a semicolon, i.e.
|
|
770
|
+
<instantiationLanguage>eng;fre</instantiationLanguage>. + Best practice:
|
|
771
|
+
Alternative audio or text tracks and their associated languages should be
|
|
772
|
+
identified using the element
|
|
773
|
+
instantiationAlternativeModes.</xsd:documentation>
|
|
774
|
+
</xsd:annotation>
|
|
775
|
+
</xsd:element>
|
|
776
|
+
<!-- the pbcore instantiationAlternativeModes -->
|
|
777
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="instantiationAlternativeModes"
|
|
778
|
+
type="sourceVersionStringType">
|
|
779
|
+
<xsd:annotation>
|
|
780
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationAlternativeModes
|
|
781
|
+
element is a catch-all metadata element that identifies equivalent
|
|
782
|
+
alternatives to the primary visual, sound or textual information that exists
|
|
783
|
+
in an instantiation. These are modes that offer alternative ways to see,
|
|
784
|
+
hear, and read the content of an instantiation. Examples include DVI
|
|
785
|
+
(Descriptive Video Information), SAP (Supplementary Audio Program),
|
|
786
|
+
ClosedCaptions, OpenCaptions, Subtitles, Language Dubs, and Transcripts. For
|
|
787
|
+
each instance of available alternativeModes, the mode and its associated
|
|
788
|
+
language should be identified together, if applicable. Examples include 'SAP
|
|
789
|
+
in English,' 'SAP in Spanish,' 'Subtitle in French,' 'OpenCaption in
|
|
790
|
+
Arabic.'</xsd:documentation>
|
|
791
|
+
</xsd:annotation>
|
|
792
|
+
</xsd:element>
|
|
793
|
+
<!-- the pbcore instantiationEssenceTrack -->
|
|
794
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="instantiationEssenceTrack"
|
|
795
|
+
type="essenceTrackType">
|
|
796
|
+
<xsd:annotation>
|
|
797
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationEssenceTrack
|
|
798
|
+
element is an XML container element that allows for grouping of related
|
|
799
|
+
essenceTrack elements and their repeated use. Use instantiationEssenceTrack
|
|
800
|
+
element to describe the individual streams that comprise an instantiation,
|
|
801
|
+
such as audio, video, timecode, etc.</xsd:documentation>
|
|
802
|
+
<xsd:documentation xml:lang="en">Best practice: Essence tracks can exist in
|
|
803
|
+
either the digital or physical realm. In the digital realm, they may refer
|
|
804
|
+
to the separate audio and video tracks within a digital file. In the
|
|
805
|
+
physical realm, they may refer to the video and audio tracks contained on a
|
|
806
|
+
single video tape.</xsd:documentation>
|
|
807
|
+
</xsd:annotation>
|
|
808
|
+
</xsd:element>
|
|
809
|
+
<!-- the pbcore InstantiationRelation - this element may occur as many times as
|
|
810
|
+
desired. if it does occur, the instantiationRelationIdentifier must appear,
|
|
811
|
+
also the relationType must also appear -->
|
|
812
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="instantiationRelation">
|
|
813
|
+
<xsd:annotation>
|
|
814
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationRelation element
|
|
815
|
+
is a container for sub-elements instantiationRelationType and
|
|
816
|
+
instantiationRelationIdentifier to describe relationships to other
|
|
817
|
+
instantiations.</xsd:documentation>
|
|
818
|
+
</xsd:annotation>
|
|
819
|
+
<xsd:complexType>
|
|
820
|
+
<xsd:sequence>
|
|
821
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="instantiationRelationType"
|
|
822
|
+
type="sourceVersionStringType">
|
|
823
|
+
<xsd:annotation>
|
|
824
|
+
<xsd:documentation xml:lang="en">Definition: The
|
|
825
|
+
instantiationRelationType element describes the relation between
|
|
826
|
+
the instantiation being described and another
|
|
827
|
+
instantiation.</xsd:documentation>
|
|
828
|
+
<xsd:documentation xml:lang="en">Best practice: Use to express
|
|
829
|
+
relationships between instantiations, for example to note that
|
|
830
|
+
they are different discrete parts of a single intellectual unit,
|
|
831
|
+
generationally related, derivative of another, or different
|
|
832
|
+
versions.</xsd:documentation>
|
|
833
|
+
</xsd:annotation>
|
|
834
|
+
</xsd:element>
|
|
835
|
+
<xsd:element maxOccurs="1" minOccurs="1"
|
|
836
|
+
name="instantiationRelationIdentifier" type="sourceVersionStringType">
|
|
837
|
+
<xsd:annotation>
|
|
838
|
+
<xsd:documentation xml:lang="en">Definition: The
|
|
839
|
+
instantiationRelationIdentifier element is used to provide a
|
|
840
|
+
name, locator, accession, identification number or ID where the
|
|
841
|
+
related item can be obtained or found.</xsd:documentation>
|
|
842
|
+
<xsd:documentation xml:lang="en">Best practice: We recommend using a
|
|
843
|
+
unique identifier or global unique ID in this
|
|
844
|
+
element.</xsd:documentation>
|
|
845
|
+
</xsd:annotation>
|
|
846
|
+
</xsd:element>
|
|
847
|
+
</xsd:sequence>
|
|
848
|
+
</xsd:complexType>
|
|
849
|
+
</xsd:element>
|
|
850
|
+
<!-- the pbcore instantiationRights -->
|
|
851
|
+
<xsd:element name="instantiationRights" type="rightsSummaryType" maxOccurs="unbounded"
|
|
852
|
+
minOccurs="0">
|
|
853
|
+
<xsd:annotation>
|
|
854
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationRights element is
|
|
855
|
+
a container for sub-elements rightsSummary, rightsLink and rightsEmbedded to
|
|
856
|
+
describe rights particular to this instantiation." </xsd:documentation>
|
|
857
|
+
<xsd:documentation xml:lang="en">Best practice: This element contains rights
|
|
858
|
+
information that is specific to an instantiation of an asset, such as rights
|
|
859
|
+
conferred in a donation agreement that apply only to a single donated
|
|
860
|
+
item.</xsd:documentation>
|
|
861
|
+
</xsd:annotation>
|
|
862
|
+
</xsd:element>
|
|
863
|
+
<!-- the pbcore instantiationAnnotation -->
|
|
864
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="instantiationAnnotation"
|
|
865
|
+
type="annotationStringType">
|
|
866
|
+
<xsd:annotation>
|
|
867
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationAnnotation element
|
|
868
|
+
is used to add any supplementary information about an instantiation of the
|
|
869
|
+
instantiation or the metadata used to describe it. It clarifies element
|
|
870
|
+
values, terms, descriptors, and vocabularies that may not be otherwise
|
|
871
|
+
sufficiently understood.</xsd:documentation>
|
|
872
|
+
</xsd:annotation>
|
|
873
|
+
</xsd:element>
|
|
874
|
+
<!-- the pbcore instantiationPart -->
|
|
875
|
+
<xsd:element name="instantiationPart" type="instantiationType" maxOccurs="unbounded"
|
|
876
|
+
minOccurs="0">
|
|
877
|
+
<xsd:annotation>
|
|
878
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationPart element is a
|
|
879
|
+
container that allows the instantiation to be split into multiple parts,
|
|
880
|
+
which can describe the parts of a multi-section instantiation, e.g., a
|
|
881
|
+
multi-disk DVD or vitagraph record and 35mm reel that are intended for
|
|
882
|
+
synchronous playback. It contains all of the elements that a
|
|
883
|
+
pbcoreInstantiation element would typically contain.</xsd:documentation>
|
|
884
|
+
</xsd:annotation>
|
|
885
|
+
</xsd:element>
|
|
886
|
+
<!-- the pbcore instantiationExtension -->
|
|
887
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="instantiationExtension"
|
|
888
|
+
type="extensionType">
|
|
889
|
+
<xsd:annotation>
|
|
890
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationExtension element
|
|
891
|
+
can be used as either a wrapper containing a specific element from another
|
|
892
|
+
standard OR embedded xml containing the extension.</xsd:documentation>
|
|
893
|
+
<xsd:documentation xml:lang="en">Best practice: Use it to supplement other
|
|
894
|
+
metadata sub-elements of 'instantiationPart' or
|
|
895
|
+
'pbcoreInstantiationDocument' in which it appears.</xsd:documentation>
|
|
896
|
+
</xsd:annotation>
|
|
897
|
+
</xsd:element>
|
|
898
|
+
</xsd:sequence>
|
|
899
|
+
<!-- instantiationStartEndTimeGroup -->
|
|
900
|
+
<xsd:attributeGroup ref="startEndTimeGroup">
|
|
901
|
+
<xsd:annotation>
|
|
902
|
+
<xsd:documentation xml:lang="en">Definition: The instantiation level attribute group
|
|
903
|
+
startEndTimeGroup may be used when there is a multi-part instantiation and time
|
|
904
|
+
notation is important. </xsd:documentation>
|
|
905
|
+
</xsd:annotation>
|
|
906
|
+
</xsd:attributeGroup>
|
|
907
|
+
<xsd:attributeGroup ref="sourceVersionGroup">
|
|
908
|
+
<xsd:annotation>
|
|
909
|
+
<xsd:documentation xml:lang="en">Definition: The instantiation level attribute group
|
|
910
|
+
sourceVersionGroup may be used when there is a multi-part instantiation and
|
|
911
|
+
notation is important. </xsd:documentation>
|
|
912
|
+
</xsd:annotation>
|
|
913
|
+
</xsd:attributeGroup>
|
|
914
|
+
</xsd:complexType>
|
|
915
|
+
<!-- the pbcore instantiation essenceTrackType -->
|
|
916
|
+
<xsd:complexType name="essenceTrackType">
|
|
917
|
+
<xsd:annotation>
|
|
918
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackType schema type uses a
|
|
919
|
+
common structure to allow for grouping of the essence related elements and their
|
|
920
|
+
repeated use.</xsd:documentation>
|
|
921
|
+
</xsd:annotation>
|
|
922
|
+
<xsd:sequence>
|
|
923
|
+
<!-- the pbcore instantiation essenceTrackType -->
|
|
924
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackType"
|
|
925
|
+
type="sourceVersionStringType">
|
|
926
|
+
<xsd:annotation>
|
|
927
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackType element refers
|
|
928
|
+
to the media type of the decoded data. Tracks may possibly be of these
|
|
929
|
+
types: video, audio, caption, metadata, image, etc.</xsd:documentation>
|
|
930
|
+
</xsd:annotation>
|
|
931
|
+
</xsd:element>
|
|
932
|
+
<!-- the pbcore instantiation essenceTrackIdentifier -->
|
|
933
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="essenceTrackIdentifier"
|
|
934
|
+
type="sourceVersionStringType">
|
|
935
|
+
<xsd:annotation>
|
|
936
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackIdentifier element
|
|
937
|
+
is an identifier of the track. Several audiovisual containers include such
|
|
938
|
+
identifier schema to identify each track, such as MPEG2 PIDs or QuickTime
|
|
939
|
+
Track IDs.</xsd:documentation>
|
|
940
|
+
</xsd:annotation>
|
|
941
|
+
</xsd:element>
|
|
942
|
+
<!-- the pbcore instantiation essenceTrackStandard -->
|
|
943
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackStandard"
|
|
944
|
+
type="sourceVersionStringType">
|
|
945
|
+
<xsd:annotation>
|
|
946
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackStandard element
|
|
947
|
+
should be be used with file-based instantiations to describe the broadcast
|
|
948
|
+
standard of the video signal (e.g. NTSC, PAL) or to further clarify the
|
|
949
|
+
standard of the essenceTrackEncoding format.</xsd:documentation>
|
|
950
|
+
</xsd:annotation>
|
|
951
|
+
</xsd:element>
|
|
952
|
+
<!-- the pbcore instantiation essenceTrackEncoding -->
|
|
953
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackEncoding"
|
|
954
|
+
type="sourceVersionStringType">
|
|
955
|
+
<xsd:annotation>
|
|
956
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackEncoding element
|
|
957
|
+
essenceTrackEncoding identifies how the actual information in an
|
|
958
|
+
instantiation is compressed, interpreted, or formulated using a particular
|
|
959
|
+
scheme. Identifying the encoding used is beneficial for a number of reasons,
|
|
960
|
+
including as a way to achieve reversible compression; for the construction
|
|
961
|
+
of document indices to facilitate searching and access; or for efficient
|
|
962
|
+
distribution of the information across data networks with differing
|
|
963
|
+
bandwidths or pipeline capacities. Human-readable encoding value should be
|
|
964
|
+
placed here. Use @ref to identify the codec ID.</xsd:documentation>
|
|
965
|
+
<xsd:documentation xml:lang="en">Best practice: Use @source to describe the type
|
|
966
|
+
of encoding reference used, such as fourcc. In @ref, use a URI/URL from the
|
|
967
|
+
source to identify the codec utilized by its container
|
|
968
|
+
format.</xsd:documentation>
|
|
969
|
+
</xsd:annotation>
|
|
970
|
+
</xsd:element>
|
|
971
|
+
<!-- the pbcore instantiation essenceTrackDataRate -->
|
|
972
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackDataRate"
|
|
973
|
+
type="technicalStringType">
|
|
974
|
+
<xsd:annotation>
|
|
975
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackDataRate element
|
|
976
|
+
measures the amount of data used per time interval for encoded data. The
|
|
977
|
+
data rate can be calculated by dividing the total data size of the track's
|
|
978
|
+
encoded data by a time unit. By default use bytes per
|
|
979
|
+
second.</xsd:documentation>
|
|
980
|
+
</xsd:annotation>
|
|
981
|
+
</xsd:element>
|
|
982
|
+
<!-- the pbcore instantiation essenceTrackFrameRate -->
|
|
983
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackFrameRate"
|
|
984
|
+
type="technicalStringType">
|
|
985
|
+
<xsd:annotation>
|
|
986
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackFrameRate element
|
|
987
|
+
is relevant to tracks of video track type only. The frame rate is calculated
|
|
988
|
+
by dividing the total number of frames by the duration of the video track.
|
|
989
|
+
By default measure frame rate in frames per second expressed as fps as a
|
|
990
|
+
unit of measure. e.g., 24 fps.</xsd:documentation>
|
|
991
|
+
<xsd:documentation xml:lang="en">Best practice: Example:
|
|
992
|
+
1920x1080.</xsd:documentation>
|
|
993
|
+
</xsd:annotation>
|
|
994
|
+
</xsd:element>
|
|
995
|
+
<!-- the pbcore instantiation essenceTrackPlaybackSpeed -->
|
|
996
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackPlaybackSpeed"
|
|
997
|
+
type="technicalStringType">
|
|
998
|
+
<xsd:annotation>
|
|
999
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackPlaybackSpeed
|
|
1000
|
+
element specifies the rate of units against time at which the media track
|
|
1001
|
+
should be rendered for human consumption. e.g., 15ips (inches per
|
|
1002
|
+
second).</xsd:documentation>
|
|
1003
|
+
</xsd:annotation>
|
|
1004
|
+
</xsd:element>
|
|
1005
|
+
<!-- the pbcore instantiation essenceTrackSamplingRate -->
|
|
1006
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackSamplingRate"
|
|
1007
|
+
type="technicalStringType">
|
|
1008
|
+
<xsd:annotation>
|
|
1009
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackSamplingRate
|
|
1010
|
+
element measures how often data is sampled when information from the audio
|
|
1011
|
+
portion from an instantiation is digitized. For a digital audio signal, the
|
|
1012
|
+
sampling rate is measured in kilohertz and is an indicator of the perceived
|
|
1013
|
+
playback quality of the media item (the higher the sampling rate, the
|
|
1014
|
+
greater the fidelity).</xsd:documentation>
|
|
1015
|
+
</xsd:annotation>
|
|
1016
|
+
</xsd:element>
|
|
1017
|
+
<!-- the pbcore instantiation essenceTrackBitDepth -->
|
|
1018
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackBitDepth"
|
|
1019
|
+
type="technicalStringType">
|
|
1020
|
+
<xsd:annotation>
|
|
1021
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackBitDepth element
|
|
1022
|
+
specifies how much data is sampled when information is digitized, encoded,
|
|
1023
|
+
or converted for an instantiation (specifically, audio, video, or image).
|
|
1024
|
+
Bit depth is measured in bits and generally implies an arbitrary perception
|
|
1025
|
+
of quality during playback of an instantiation (the higher the bit depth,
|
|
1026
|
+
the greater the fidelity). </xsd:documentation>
|
|
1027
|
+
</xsd:annotation>
|
|
1028
|
+
</xsd:element>
|
|
1029
|
+
<!-- the pbcore instantiation essenceTrackFrameSize -->
|
|
1030
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackFrameSize"
|
|
1031
|
+
type="technicalStringType">
|
|
1032
|
+
<xsd:annotation>
|
|
1033
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackFrameSize element
|
|
1034
|
+
measures the width and height of the encoded video or image track. The frame
|
|
1035
|
+
size refers to the size of the encoded pixels and not the size of the
|
|
1036
|
+
displayed image. It may be expressed as combination of pixels measured
|
|
1037
|
+
horizontally vs. the number of pixels of image/resolution data stacked
|
|
1038
|
+
vertically (interlaced and progressive scan).</xsd:documentation>
|
|
1039
|
+
</xsd:annotation>
|
|
1040
|
+
</xsd:element>
|
|
1041
|
+
<!-- the pbcore instantiation essenceTrackAspectRatio -->
|
|
1042
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackAspectRatio"
|
|
1043
|
+
type="technicalStringType">
|
|
1044
|
+
<xsd:annotation>
|
|
1045
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackAspectRatio element
|
|
1046
|
+
indicates the ratio of horizontal to vertical proportions in the display of
|
|
1047
|
+
a static image or moving image.</xsd:documentation>
|
|
1048
|
+
</xsd:annotation>
|
|
1049
|
+
</xsd:element>
|
|
1050
|
+
<!-- the pbcore instantiation essenceTrackTimeStart -->
|
|
1051
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackTimeStart"
|
|
1052
|
+
type="sourceVersionStringType">
|
|
1053
|
+
<xsd:annotation>
|
|
1054
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackTimeStart element
|
|
1055
|
+
provides a time stamp for the beginning point of playback for a time-based
|
|
1056
|
+
essence track. It is likely that the content on a tape may begin an
|
|
1057
|
+
arbitrary amount of time after the beginning of the
|
|
1058
|
+
instantiation.</xsd:documentation>
|
|
1059
|
+
<xsd:documentation xml:lang="en">Best practice: Use in combination with
|
|
1060
|
+
essenceTrackDuration to identify a sequence or segment of an essence track
|
|
1061
|
+
that has a fixed start time and end time. Best practice is to use a
|
|
1062
|
+
timestamp format such as HH:MM:SS[:|;]FF or HH:MM:SS.mmm or
|
|
1063
|
+
S.mmm.</xsd:documentation>
|
|
1064
|
+
</xsd:annotation>
|
|
1065
|
+
</xsd:element>
|
|
1066
|
+
<!-- the pbcore instantiation essenceTrackDuration -->
|
|
1067
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="essenceTrackDuration"
|
|
1068
|
+
type="sourceVersionStringType">
|
|
1069
|
+
<xsd:annotation>
|
|
1070
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackDuration element
|
|
1071
|
+
provides a timestamp for the overall length or duration of a track. It
|
|
1072
|
+
represents the track playback time. Best practice is to use a timestamp
|
|
1073
|
+
format such as HH:MM:SS[:|;]FF or HH:MM:SS.mmm or S.mmm.</xsd:documentation>
|
|
1074
|
+
</xsd:annotation>
|
|
1075
|
+
</xsd:element>
|
|
1076
|
+
<!-- the pbcore instantiation essenceTrackLanguage -->
|
|
1077
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="essenceTrackLanguage"
|
|
1078
|
+
type="threeLetterStringType">
|
|
1079
|
+
<xsd:annotation>
|
|
1080
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackLanguage element
|
|
1081
|
+
identifies the primary language of the tracks' audio or
|
|
1082
|
+
text.</xsd:documentation>
|
|
1083
|
+
<xsd:documentation xml:lang="en">Best practice: Alternative audio or text tracks
|
|
1084
|
+
and their associated languages should be identified using the element
|
|
1085
|
+
alternativeModes.</xsd:documentation>
|
|
1086
|
+
</xsd:annotation>
|
|
1087
|
+
</xsd:element>
|
|
1088
|
+
<!-- the pbcore instantiation essenceTrackAnnotation -->
|
|
1089
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="essenceTrackAnnotation"
|
|
1090
|
+
type="annotationStringType">
|
|
1091
|
+
<xsd:annotation>
|
|
1092
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackAnnotation element
|
|
1093
|
+
can store any supplementary information about a track or the metadata used
|
|
1094
|
+
to describe it. It clarifies element values, terms, descriptors, and
|
|
1095
|
+
vocabularies that may not be otherwise sufficiently
|
|
1096
|
+
understood.</xsd:documentation>
|
|
1097
|
+
</xsd:annotation>
|
|
1098
|
+
</xsd:element>
|
|
1099
|
+
<!-- the pbcore instantiation essenceExtension -->
|
|
1100
|
+
<xsd:element maxOccurs="unbounded" minOccurs="0" name="essenceTrackExtension"
|
|
1101
|
+
type="extensionType">
|
|
1102
|
+
<xsd:annotation>
|
|
1103
|
+
<xsd:documentation xml:lang="en">Definition: The essenceTrackExtension element
|
|
1104
|
+
can be used as either a wrapper containing a specific element from another
|
|
1105
|
+
standard OR embedded xml containing the extension. The essenceTrackExtension
|
|
1106
|
+
element is a container to accomodate track-level metadata from external
|
|
1107
|
+
systems. Use it to supplement other metadata sub-elements of
|
|
1108
|
+
instantiationEssenceTrack in which it appears.</xsd:documentation>
|
|
1109
|
+
</xsd:annotation>
|
|
1110
|
+
</xsd:element>
|
|
1111
|
+
</xsd:sequence>
|
|
1112
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1113
|
+
</xsd:complexType>
|
|
1114
|
+
<!-- extensionType -->
|
|
1115
|
+
<xsd:complexType name="extensionType">
|
|
1116
|
+
<xsd:annotation>
|
|
1117
|
+
<xsd:documentation xml:lang="en">Definition: The extensionType schema type uses a common
|
|
1118
|
+
structure to allow for the use of multiple, qualified extensions at the asset,
|
|
1119
|
+
instantiation and essence levels.</xsd:documentation>
|
|
1120
|
+
</xsd:annotation>
|
|
1121
|
+
<xsd:choice>
|
|
1122
|
+
<xsd:element maxOccurs="unbounded" minOccurs="1" name="extensionWrap">
|
|
1123
|
+
<xsd:annotation>
|
|
1124
|
+
<xsd:documentation xml:lang="en">Definition: The extensionWrap element serves as
|
|
1125
|
+
a container for the elements extensionElement, extensionValue, and
|
|
1126
|
+
extensionAuthorityUsed.</xsd:documentation>
|
|
1127
|
+
</xsd:annotation>
|
|
1128
|
+
<xsd:complexType>
|
|
1129
|
+
<xsd:sequence>
|
|
1130
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="extensionElement"
|
|
1131
|
+
type="xsd:string">
|
|
1132
|
+
<xsd:annotation>
|
|
1133
|
+
<xsd:documentation xml:lang="en">Definition: The extensionElement
|
|
1134
|
+
element should contain the name of an element used from another
|
|
1135
|
+
metadata standard, in the case that an element from another +
|
|
1136
|
+
metadata standard is used. While we recommend the usage of an
|
|
1137
|
+
existing standard, this element can also be used to define local
|
|
1138
|
+
elements that may not be part of an existing standard." </xsd:documentation>
|
|
1139
|
+
<xsd:documentation xml:lang="en">Best practice: These extensions
|
|
1140
|
+
fulfill the metadata requirements for communities identifying
|
|
1141
|
+
and describing their own types of media with specialized, custom
|
|
1142
|
+
terminologies.</xsd:documentation>
|
|
1143
|
+
</xsd:annotation>
|
|
1144
|
+
</xsd:element>
|
|
1145
|
+
<xsd:element maxOccurs="1" minOccurs="1" name="extensionValue"
|
|
1146
|
+
type="xsd:string">
|
|
1147
|
+
<xsd:annotation>
|
|
1148
|
+
<xsd:documentation xml:lang="en">Definition: The extensionValue
|
|
1149
|
+
element is used to express the data value of the label indicated
|
|
1150
|
+
by extensionElement.</xsd:documentation>
|
|
1151
|
+
</xsd:annotation>
|
|
1152
|
+
</xsd:element>
|
|
1153
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="extensionAuthorityUsed"
|
|
1154
|
+
type="xsd:anyURI">
|
|
1155
|
+
<xsd:annotation>
|
|
1156
|
+
<xsd:documentation xml:lang="en">Definition: The
|
|
1157
|
+
extensionAuthorityUsed element identifies the authority used for
|
|
1158
|
+
the extensionElement.</xsd:documentation>
|
|
1159
|
+
<xsd:documentation xml:lang="en">Best practice: If metadata
|
|
1160
|
+
extensions to PBCore are assigned to a media item with the
|
|
1161
|
+
element extensionElement, and the terms used are derived from a
|
|
1162
|
+
specific authority or metadata scheme, use
|
|
1163
|
+
extensionAuthorityUsed to identify whose metadata extensions are
|
|
1164
|
+
being used.</xsd:documentation>
|
|
1165
|
+
</xsd:annotation>
|
|
1166
|
+
</xsd:element>
|
|
1167
|
+
</xsd:sequence>
|
|
1168
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1169
|
+
</xsd:complexType>
|
|
1170
|
+
</xsd:element>
|
|
1171
|
+
<xsd:element maxOccurs="unbounded" minOccurs="1" name="extensionEmbedded"
|
|
1172
|
+
type="embeddedType">
|
|
1173
|
+
<xsd:annotation>
|
|
1174
|
+
<xsd:documentation xml:lang="en">Definition: The extensionEmbedded element
|
|
1175
|
+
allows the inclusion of xml from another schema, e.g. TEI, METS,
|
|
1176
|
+
etc.</xsd:documentation>
|
|
1177
|
+
</xsd:annotation>
|
|
1178
|
+
</xsd:element>
|
|
1179
|
+
</xsd:choice>
|
|
1180
|
+
</xsd:complexType>
|
|
1181
|
+
<!-- pbcorePartType -->
|
|
1182
|
+
<xsd:complexType name="pbcorePartType">
|
|
1183
|
+
<xsd:annotation>
|
|
1184
|
+
<xsd:documentation xml:lang="en">Definition: The pbcorePartType schema type uses a
|
|
1185
|
+
common structure to allow for the repeating of descriptive sub-documents to define
|
|
1186
|
+
different segments, episodes etc., just as super-element 'pbcoreDescriptionDocument'
|
|
1187
|
+
can be collected and used to describe higher-level media
|
|
1188
|
+
programs.</xsd:documentation>
|
|
1189
|
+
</xsd:annotation>
|
|
1190
|
+
<xsd:complexContent>
|
|
1191
|
+
<xsd:extension base="pbcoreDescriptionDocumentType">
|
|
1192
|
+
<xsd:attributeGroup ref="startEndTimeGroup">
|
|
1193
|
+
<xsd:annotation>
|
|
1194
|
+
<xsd:documentation xml:lang="en">Definition: The group of attributes
|
|
1195
|
+
"startTime', 'endTime' and 'timeAnnotation' could be used when a there
|
|
1196
|
+
is a multipart asset and time notation is important.
|
|
1197
|
+
</xsd:documentation>
|
|
1198
|
+
</xsd:annotation>
|
|
1199
|
+
</xsd:attributeGroup>
|
|
1200
|
+
<xsd:attribute name="partType" type="xsd:string">
|
|
1201
|
+
<xsd:annotation>
|
|
1202
|
+
<xsd:documentation>Definition: The partType attribute is used to indicate
|
|
1203
|
+
the nature of the part into which the asset has been
|
|
1204
|
+
divided.</xsd:documentation>
|
|
1205
|
+
</xsd:annotation>
|
|
1206
|
+
</xsd:attribute>
|
|
1207
|
+
<xsd:attribute name="partTypeSource" type="xsd:string">
|
|
1208
|
+
<xsd:annotation>
|
|
1209
|
+
<xsd:documentation>Definition: The partTypeSource attribute provides the
|
|
1210
|
+
name of the authority used to declare data value of the partType
|
|
1211
|
+
attribute.</xsd:documentation>
|
|
1212
|
+
<xsd:documentation>Best practice: This might be the name of a controlled
|
|
1213
|
+
vocabulary, namespace or authority list, such as the official PBCore
|
|
1214
|
+
vocabulary. We recommend a consistent and human readable
|
|
1215
|
+
use.</xsd:documentation>
|
|
1216
|
+
</xsd:annotation>
|
|
1217
|
+
</xsd:attribute>
|
|
1218
|
+
<xsd:attribute name="partTypeRef" type="xsd:string">
|
|
1219
|
+
<xsd:annotation>
|
|
1220
|
+
<xsd:documentation>Definition: The partTypeRef attribute is used to supply a
|
|
1221
|
+
source's URI for the value of the attribute
|
|
1222
|
+
titleTypeSource.</xsd:documentation>
|
|
1223
|
+
<xsd:documentation>Best practice: The partTypeRef attribute can be used to
|
|
1224
|
+
point to a term in a controlled vocabulary, or a URI associated with a
|
|
1225
|
+
source.</xsd:documentation>
|
|
1226
|
+
</xsd:annotation>
|
|
1227
|
+
</xsd:attribute>
|
|
1228
|
+
<xsd:attribute name="titleTypeVersion" type="xsd:string">
|
|
1229
|
+
<xsd:annotation>
|
|
1230
|
+
<xsd:documentation>Definition: The partTypeVersion attribute identifies any
|
|
1231
|
+
version information about the authority or convention used to express
|
|
1232
|
+
data of this element.</xsd:documentation>
|
|
1233
|
+
</xsd:annotation>
|
|
1234
|
+
</xsd:attribute>
|
|
1235
|
+
<xsd:attribute name="titleTypeAnnotation" type="xsd:string">
|
|
1236
|
+
<xsd:annotation>
|
|
1237
|
+
<xsd:documentation>Definition: The partTypeAnnotation attribute includes
|
|
1238
|
+
narrative information intended to clarify the nature of data used in the
|
|
1239
|
+
element.</xsd:documentation>
|
|
1240
|
+
<xsd:documentation>Best practice: This attribute can be used as a notes
|
|
1241
|
+
field to include any additional information about the element or
|
|
1242
|
+
associated attributes</xsd:documentation>
|
|
1243
|
+
</xsd:annotation>
|
|
1244
|
+
</xsd:attribute>
|
|
1245
|
+
</xsd:extension>
|
|
1246
|
+
</xsd:complexContent>
|
|
1247
|
+
</xsd:complexType>
|
|
1248
|
+
<!-- dateStringType -->
|
|
1249
|
+
<xsd:complexType name="dateStringType">
|
|
1250
|
+
<xsd:annotation>
|
|
1251
|
+
<xsd:documentation xml:lang="en">Definition: The dateStringType schema type allows for
|
|
1252
|
+
the addition of the dateType attribute.</xsd:documentation>
|
|
1253
|
+
</xsd:annotation>
|
|
1254
|
+
<xsd:simpleContent>
|
|
1255
|
+
<xsd:extension base="xsd:string">
|
|
1256
|
+
<xsd:attribute name="dateType" type="xsd:string">
|
|
1257
|
+
<xsd:annotation>
|
|
1258
|
+
<xsd:documentation xml:lang="en">Definition: The dateType attribute
|
|
1259
|
+
classifies by named type the date-related data of the element e.g.,
|
|
1260
|
+
created, broadcast, dateAvailableStart.</xsd:documentation>
|
|
1261
|
+
<xsd:documentation xml:lang="en">Best practice: Used to clarify how the date
|
|
1262
|
+
is related to the asset or instantiation. Date Created may be the most
|
|
1263
|
+
common, but the element could also be used to describe the Date
|
|
1264
|
+
Accessioned or Date Deaccessioned, for example.</xsd:documentation>
|
|
1265
|
+
</xsd:annotation>
|
|
1266
|
+
</xsd:attribute>
|
|
1267
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1268
|
+
</xsd:extension>
|
|
1269
|
+
</xsd:simpleContent>
|
|
1270
|
+
</xsd:complexType>
|
|
1271
|
+
<!-- sourceVersionStringType -->
|
|
1272
|
+
<xsd:complexType name="sourceVersionStringType">
|
|
1273
|
+
<xsd:annotation>
|
|
1274
|
+
<xsd:documentation xml:lang="en">Definition: The sourceVersionStringType schema type is
|
|
1275
|
+
used with a number of elements to allow the attachment of the attributes: source,
|
|
1276
|
+
ref, version and annotation.</xsd:documentation>
|
|
1277
|
+
</xsd:annotation>
|
|
1278
|
+
<xsd:simpleContent>
|
|
1279
|
+
<xsd:extension base="xsd:string">
|
|
1280
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1281
|
+
</xsd:extension>
|
|
1282
|
+
</xsd:simpleContent>
|
|
1283
|
+
</xsd:complexType>
|
|
1284
|
+
<!-- requiredSourceVersionStringType -->
|
|
1285
|
+
<xsd:complexType name="requiredSourceVersionStringType">
|
|
1286
|
+
<xsd:annotation>
|
|
1287
|
+
<xsd:documentation xml:lang="en">Definition: The requiredSourceVersionStringType schema
|
|
1288
|
+
type type is the same as sourceVersionStringType with the addition that the source
|
|
1289
|
+
attribute is required instead of optional.</xsd:documentation>
|
|
1290
|
+
</xsd:annotation>
|
|
1291
|
+
<xsd:simpleContent>
|
|
1292
|
+
<xsd:extension base="xsd:string">
|
|
1293
|
+
<xsd:attribute name="source" type="xsd:string" use="required">
|
|
1294
|
+
<xsd:annotation>
|
|
1295
|
+
<xsd:documentation xml:lang="en">Definition: The source attribute provides
|
|
1296
|
+
the name of the authority used to declare the value of the
|
|
1297
|
+
element.</xsd:documentation>
|
|
1298
|
+
<xsd:documentation xml:lang="en">Best practice: Different elements will use
|
|
1299
|
+
the source attribute slightly differently. For example, identifier
|
|
1300
|
+
source (required) should be the name of the organization, institution,
|
|
1301
|
+
system or namespace that the identifier came from, such as "PBS NOLA
|
|
1302
|
+
Code" or an institutional database identifier. For other elements, this
|
|
1303
|
+
might be the name of a controlled vocabulary, namespace or authority
|
|
1304
|
+
list, such as Library of Congress Subject Headings. We recommend a
|
|
1305
|
+
consistent and human readable use.</xsd:documentation>
|
|
1306
|
+
</xsd:annotation>
|
|
1307
|
+
</xsd:attribute>
|
|
1308
|
+
<xsd:attribute name="ref" type="xsd:string">
|
|
1309
|
+
<xsd:annotation>
|
|
1310
|
+
<xsd:documentation xml:lang="en">Definition: The ref attribute is used to
|
|
1311
|
+
supply a source's URI for the value of the element.</xsd:documentation>
|
|
1312
|
+
<xsd:documentation xml:lang="en">Best practice: Attribute ref can be used to
|
|
1313
|
+
point to a term in a controlled vocabulary, or a URI associated with a
|
|
1314
|
+
source.</xsd:documentation>
|
|
1315
|
+
</xsd:annotation>
|
|
1316
|
+
</xsd:attribute>
|
|
1317
|
+
<xsd:attribute name="version" type="xsd:string">
|
|
1318
|
+
<xsd:annotation>
|
|
1319
|
+
<xsd:documentation xml:lang="en">Definition: The version attribute
|
|
1320
|
+
identifies any version information about the authority or convention
|
|
1321
|
+
used to express data of this element.</xsd:documentation>
|
|
1322
|
+
<xsd:documentation xml:lang="en">Best practice: This attribute can be used
|
|
1323
|
+
as a notes field to include any additional information about the element
|
|
1324
|
+
or associated attributes.</xsd:documentation>
|
|
1325
|
+
</xsd:annotation>
|
|
1326
|
+
</xsd:attribute>
|
|
1327
|
+
<xsd:attribute name="annotation" type="xsd:string">
|
|
1328
|
+
<xsd:annotation>
|
|
1329
|
+
<xsd:documentation xml:lang="en">Definition: The annotation attribute
|
|
1330
|
+
includes narrative information intended to clarify the nature of data
|
|
1331
|
+
used in the element.</xsd:documentation>
|
|
1332
|
+
</xsd:annotation>
|
|
1333
|
+
</xsd:attribute>
|
|
1334
|
+
</xsd:extension>
|
|
1335
|
+
</xsd:simpleContent>
|
|
1336
|
+
</xsd:complexType>
|
|
1337
|
+
<!-- titleStringType -->
|
|
1338
|
+
<xsd:complexType name="titleStringType">
|
|
1339
|
+
<xsd:annotation>
|
|
1340
|
+
<xsd:documentation xml:lang="en">Definition: The titleStringType schema type allows for
|
|
1341
|
+
the addition of a titleType attribute as well as the standard sourceVersionGroup
|
|
1342
|
+
attributes and a startEndTimeGroup or attributes.</xsd:documentation>
|
|
1343
|
+
</xsd:annotation>
|
|
1344
|
+
<xsd:simpleContent>
|
|
1345
|
+
<xsd:extension base="xsd:string">
|
|
1346
|
+
<xsd:attribute name="titleType" type="xsd:string">
|
|
1347
|
+
<xsd:annotation>
|
|
1348
|
+
<xsd:documentation xml:lang="en">Definition: The titleType attribute is used
|
|
1349
|
+
to indicate the type of title being assigned to the asset, such as
|
|
1350
|
+
series title, episode title or project title.</xsd:documentation>
|
|
1351
|
+
</xsd:annotation>
|
|
1352
|
+
</xsd:attribute>
|
|
1353
|
+
<xsd:attribute name="titleTypeSource" type="xsd:string">
|
|
1354
|
+
<xsd:annotation>
|
|
1355
|
+
<xsd:documentation xml:lang="en">Definition: The titleTypeSource attribute
|
|
1356
|
+
is used to provides the name of the authority used to declare data value
|
|
1357
|
+
of the titleType attribute.</xsd:documentation>
|
|
1358
|
+
<xsd:documentation xml:lang="en">Best practice: This might be the name of a
|
|
1359
|
+
controlled vocabulary, namespace or authority list, such as the official
|
|
1360
|
+
PBCore vocabulary. We recommend a consistent and human readable
|
|
1361
|
+
use.</xsd:documentation>
|
|
1362
|
+
</xsd:annotation>
|
|
1363
|
+
</xsd:attribute>
|
|
1364
|
+
<xsd:attribute name="titleTypeRef" type="xsd:string">
|
|
1365
|
+
<xsd:annotation>
|
|
1366
|
+
<xsd:documentation xml:lang="en">Definition: The titleTypeRef attribute is
|
|
1367
|
+
used to supply a source's URI for the value of the attribute
|
|
1368
|
+
titleTypeSource.</xsd:documentation>
|
|
1369
|
+
<xsd:documentation xml:lang="en">Best practice: Attribute titleTypeRef can
|
|
1370
|
+
be used to point to a term in a controlled vocabulary, or a URI
|
|
1371
|
+
associated with a source.</xsd:documentation>
|
|
1372
|
+
</xsd:annotation>
|
|
1373
|
+
</xsd:attribute>
|
|
1374
|
+
<xsd:attribute name="titleTypeVersion" type="xsd:string">
|
|
1375
|
+
<xsd:annotation>
|
|
1376
|
+
<xsd:documentation xml:lang="en">Definition: The titleTypeVersion attribute
|
|
1377
|
+
identifies any version information about the authority or convention
|
|
1378
|
+
used to express data of this element.</xsd:documentation>
|
|
1379
|
+
</xsd:annotation>
|
|
1380
|
+
</xsd:attribute>
|
|
1381
|
+
<xsd:attribute name="titleTypeAnnotation" type="xsd:string">
|
|
1382
|
+
<xsd:annotation>
|
|
1383
|
+
<xsd:documentation xml:lang="en">Definition: The titleTypeAnnotation
|
|
1384
|
+
attribute includes narrative information intended to clarify the nature
|
|
1385
|
+
of data used in the element.</xsd:documentation>
|
|
1386
|
+
<xsd:documentation xml:lang="en">Best practice: This attribute can be used
|
|
1387
|
+
as a notes field to include any additional information about the element
|
|
1388
|
+
or associated attributes.</xsd:documentation>
|
|
1389
|
+
</xsd:annotation>
|
|
1390
|
+
</xsd:attribute>
|
|
1391
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1392
|
+
<xsd:attributeGroup ref="startEndTimeGroup"/>
|
|
1393
|
+
</xsd:extension>
|
|
1394
|
+
</xsd:simpleContent>
|
|
1395
|
+
</xsd:complexType>
|
|
1396
|
+
<!-- subjectStringType -->
|
|
1397
|
+
<xsd:complexType name="subjectStringType">
|
|
1398
|
+
<xsd:annotation>
|
|
1399
|
+
<xsd:documentation xml:lang="en">Definition: The subjectStringType schema type allows
|
|
1400
|
+
for the addition of a subjectType attribute as well as the standard
|
|
1401
|
+
sourceVersionGroup attributes and a startEndTimeGroup or
|
|
1402
|
+
attributes.</xsd:documentation>
|
|
1403
|
+
</xsd:annotation>
|
|
1404
|
+
<xsd:simpleContent>
|
|
1405
|
+
<xsd:extension base="xsd:string">
|
|
1406
|
+
<xsd:attribute name="subjectType" type="xsd:string">
|
|
1407
|
+
<xsd:annotation>
|
|
1408
|
+
<xsd:documentation xml:lang="en">Definition: The subjectType attribute is
|
|
1409
|
+
used to indicate the type of subject being assigned to the attribute
|
|
1410
|
+
subjectType, such as 'topic,' 'personal name,' or
|
|
1411
|
+
'keyword'.</xsd:documentation>
|
|
1412
|
+
</xsd:annotation>
|
|
1413
|
+
</xsd:attribute>
|
|
1414
|
+
<xsd:attribute name="subjectTypeSource" type="xsd:string">
|
|
1415
|
+
<xsd:annotation>
|
|
1416
|
+
<xsd:documentation xml:lang="en">Definition: The subjectTypeSource attribute
|
|
1417
|
+
provides the name of the authority used to declare the value of the
|
|
1418
|
+
attribute subjectType.</xsd:documentation>
|
|
1419
|
+
<xsd:documentation xml:lang="en">Best practice: This might be the name of a
|
|
1420
|
+
controlled vocabulary, namespace or authority list, such as the official
|
|
1421
|
+
PBCore vocabulary. We recommend a consistent and human readable
|
|
1422
|
+
use.</xsd:documentation>
|
|
1423
|
+
</xsd:annotation>
|
|
1424
|
+
</xsd:attribute>
|
|
1425
|
+
<xsd:attribute name="subjectTypeRef" type="xsd:string">
|
|
1426
|
+
<xsd:annotation>
|
|
1427
|
+
<xsd:documentation xml:lang="en">Definition: The subjectTypeRef attribute is
|
|
1428
|
+
used to supply a source's URI for the value of the attribute
|
|
1429
|
+
subjectType.</xsd:documentation>
|
|
1430
|
+
<xsd:documentation xml:lang="en">Best practice: Attribute subjectTypeRef can
|
|
1431
|
+
be used to point to a term in a controlled vocabulary, or a URI
|
|
1432
|
+
associated with a source.</xsd:documentation>
|
|
1433
|
+
</xsd:annotation>
|
|
1434
|
+
</xsd:attribute>
|
|
1435
|
+
<xsd:attribute name="subjectTypeVersion" type="xsd:string">
|
|
1436
|
+
<xsd:annotation>
|
|
1437
|
+
<xsd:documentation xml:lang="en">Definition: The subjectTypeVersion
|
|
1438
|
+
attribute identifies any version information about the authority or
|
|
1439
|
+
convention used to express data of the attribute
|
|
1440
|
+
subjectType.</xsd:documentation>
|
|
1441
|
+
</xsd:annotation>
|
|
1442
|
+
</xsd:attribute>
|
|
1443
|
+
<xsd:attribute name="subjectTypeAnnotation" type="xsd:string">
|
|
1444
|
+
<xsd:annotation>
|
|
1445
|
+
<xsd:documentation xml:lang="en">Definition: The subjectTypeAnnotation
|
|
1446
|
+
attribute includes narrative information intended to clarify the nature
|
|
1447
|
+
of data used in the attribute subjectType.</xsd:documentation>
|
|
1448
|
+
<xsd:documentation xml:lang="en">Best practice: This attribute can be used
|
|
1449
|
+
as a notes field to include any additional information about the element
|
|
1450
|
+
or associated attributes.</xsd:documentation>
|
|
1451
|
+
</xsd:annotation>
|
|
1452
|
+
</xsd:attribute>
|
|
1453
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1454
|
+
<xsd:attributeGroup ref="startEndTimeGroup"/>
|
|
1455
|
+
</xsd:extension>
|
|
1456
|
+
</xsd:simpleContent>
|
|
1457
|
+
</xsd:complexType>
|
|
1458
|
+
<!-- descriptionStringType -->
|
|
1459
|
+
<xsd:complexType name="descriptionStringType">
|
|
1460
|
+
<xsd:annotation>
|
|
1461
|
+
<xsd:documentation xml:lang="en">Definition: The descriptionType schema type is a
|
|
1462
|
+
complex group of attributes that help define the description type, as well as
|
|
1463
|
+
allowing for descriptions of segments and relevant times.</xsd:documentation>
|
|
1464
|
+
</xsd:annotation>
|
|
1465
|
+
<xsd:simpleContent>
|
|
1466
|
+
<xsd:extension base="xsd:string">
|
|
1467
|
+
<xsd:attribute name="descriptionType" type="xsd:string">
|
|
1468
|
+
<xsd:annotation>
|
|
1469
|
+
<xsd:documentation xml:lang="en">Definition: The descriptionType attribute
|
|
1470
|
+
is used to indicate the type of description being assigned to the
|
|
1471
|
+
element, such as 'abstract,' 'summary,' or 'physical
|
|
1472
|
+
description.'</xsd:documentation>
|
|
1473
|
+
</xsd:annotation>
|
|
1474
|
+
</xsd:attribute>
|
|
1475
|
+
<xsd:attribute name="descriptionTypeSource" type="xsd:string">
|
|
1476
|
+
<xsd:annotation>
|
|
1477
|
+
<xsd:documentation xml:lang="en">Definition: The descriptionTypeSource
|
|
1478
|
+
attribute provides the name of the authority used to declare data value
|
|
1479
|
+
of the attribute descriptionType.</xsd:documentation>
|
|
1480
|
+
<xsd:documentation xml:lang="en">Best practice: This might be the name of a
|
|
1481
|
+
controlled vocabulary, namespace or authority list, such as the official
|
|
1482
|
+
PBCore recommended vocabulary. We recommend a consistent and human
|
|
1483
|
+
readable use.</xsd:documentation>
|
|
1484
|
+
</xsd:annotation>
|
|
1485
|
+
</xsd:attribute>
|
|
1486
|
+
<xsd:attribute name="descriptionTypeRef" type="xsd:string">
|
|
1487
|
+
<xsd:annotation>
|
|
1488
|
+
<xsd:documentation xml:lang="en">Definition: The descriptionTypeRef
|
|
1489
|
+
attribute is used to supply a source's URI for the value of the
|
|
1490
|
+
attribute descriptionType.</xsd:documentation>
|
|
1491
|
+
<xsd:documentation xml:lang="en">Best practice: The descriptionTypeRef
|
|
1492
|
+
attribute can be used to point to a term in a controlled vocabulary, or
|
|
1493
|
+
a URI associated with a source.</xsd:documentation>
|
|
1494
|
+
</xsd:annotation>
|
|
1495
|
+
</xsd:attribute>
|
|
1496
|
+
<xsd:attribute name="descriptionTypeVersion" type="xsd:string">
|
|
1497
|
+
<xsd:annotation>
|
|
1498
|
+
<xsd:documentation xml:lang="en">Definition: The descriptionTypeVersion
|
|
1499
|
+
attribute identifies any version information about the authority or
|
|
1500
|
+
convention used to express data of the attribute
|
|
1501
|
+
descriptionType.</xsd:documentation>
|
|
1502
|
+
</xsd:annotation>
|
|
1503
|
+
</xsd:attribute>
|
|
1504
|
+
<xsd:attribute name="descriptionTypeAnnotation" type="xsd:string">
|
|
1505
|
+
<xsd:annotation>
|
|
1506
|
+
<xsd:documentation xml:lang="en">Definition: The descriptionTypeAnnotation
|
|
1507
|
+
attribute includes narrative information intended to clarify the nature
|
|
1508
|
+
of data used in the element.</xsd:documentation>
|
|
1509
|
+
<xsd:documentation xml:lang="en">Best practice: This attribute can be used
|
|
1510
|
+
as a notes field to include any additional information about the element
|
|
1511
|
+
or associated attributes.</xsd:documentation>
|
|
1512
|
+
</xsd:annotation>
|
|
1513
|
+
</xsd:attribute>
|
|
1514
|
+
<xsd:attribute name="segmentType" type="xsd:string">
|
|
1515
|
+
<xsd:annotation>
|
|
1516
|
+
<xsd:documentation xml:lang="en">Definition: The segmentType attribute is
|
|
1517
|
+
used to define the type of content contained in a
|
|
1518
|
+
segment.</xsd:documentation>
|
|
1519
|
+
<xsd:documentation xml:lang="en">Best practice: We recommend using
|
|
1520
|
+
description and descriptionType instead of
|
|
1521
|
+
segmentType.'</xsd:documentation>
|
|
1522
|
+
</xsd:annotation>
|
|
1523
|
+
</xsd:attribute>
|
|
1524
|
+
<xsd:attribute name="segmentTypeSource" type="xsd:string">
|
|
1525
|
+
<xsd:annotation>
|
|
1526
|
+
<xsd:documentation xml:lang="en">Definition: The segmentTypeSource attribute
|
|
1527
|
+
provides the name of the authority used to declare data value of the
|
|
1528
|
+
attribute segmentType.</xsd:documentation>
|
|
1529
|
+
<xsd:documentation xml:lang="en">Best practice: This might be the name of a
|
|
1530
|
+
controlled vocabulary, namespace or authority list, such as the official
|
|
1531
|
+
PBCore recommended vocabulary.</xsd:documentation>
|
|
1532
|
+
</xsd:annotation>
|
|
1533
|
+
</xsd:attribute>
|
|
1534
|
+
<xsd:attribute name="segmentTypeRef" type="xsd:string">
|
|
1535
|
+
<xsd:annotation>
|
|
1536
|
+
<xsd:documentation xml:lang="en">Definition: The segmentTypeRef attribute is
|
|
1537
|
+
used to supply a source's URI for the value of the attribute
|
|
1538
|
+
segmentType.</xsd:documentation>
|
|
1539
|
+
<xsd:documentation xml:lang="en">Best practice: Attribute segmentTypeRef can
|
|
1540
|
+
be used to point to a term in a controlled vocabulary, or a URI
|
|
1541
|
+
associated with a source.</xsd:documentation>
|
|
1542
|
+
</xsd:annotation>
|
|
1543
|
+
</xsd:attribute>
|
|
1544
|
+
<xsd:attribute name="segmentTypeVersion" type="xsd:string">
|
|
1545
|
+
<xsd:annotation>
|
|
1546
|
+
<xsd:documentation xml:lang="en">Definition: The segmentTypeVersion
|
|
1547
|
+
attribute identifies any version information about the authority or
|
|
1548
|
+
convention used to express data of the attribute
|
|
1549
|
+
segmentType.</xsd:documentation>
|
|
1550
|
+
</xsd:annotation>
|
|
1551
|
+
</xsd:attribute>
|
|
1552
|
+
<xsd:attribute name="segmentTypeAnnotation" type="xsd:string">
|
|
1553
|
+
<xsd:annotation>
|
|
1554
|
+
<xsd:documentation xml:lang="en">Definition: The segmentTypeAnnotation
|
|
1555
|
+
attribute includes narrative information intended to clarify the nature
|
|
1556
|
+
of data used in the attribute segmentType.</xsd:documentation>
|
|
1557
|
+
<xsd:documentation xml:lang="en">Best practice: This attribute can be used
|
|
1558
|
+
as a notes field to include any additional information about the element
|
|
1559
|
+
or associated attributes.</xsd:documentation>
|
|
1560
|
+
</xsd:annotation>
|
|
1561
|
+
</xsd:attribute>
|
|
1562
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1563
|
+
<xsd:attributeGroup ref="startEndTimeGroup"/>
|
|
1564
|
+
</xsd:extension>
|
|
1565
|
+
</xsd:simpleContent>
|
|
1566
|
+
</xsd:complexType>
|
|
1567
|
+
<!-- sourceVersionStartEndStringType -->
|
|
1568
|
+
<xsd:complexType name="sourceVersionStartEndStringType">
|
|
1569
|
+
<xsd:annotation>
|
|
1570
|
+
<xsd:documentation xml:lang="en">Definition: The sourceVersionStartEndStringType adds
|
|
1571
|
+
attributes that define the source of the string with the option of time related
|
|
1572
|
+
attributes</xsd:documentation>
|
|
1573
|
+
</xsd:annotation>
|
|
1574
|
+
<xsd:simpleContent>
|
|
1575
|
+
<xsd:extension base="xsd:string">
|
|
1576
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1577
|
+
<xsd:attributeGroup ref="startEndTimeGroup"/>
|
|
1578
|
+
</xsd:extension>
|
|
1579
|
+
</xsd:simpleContent>
|
|
1580
|
+
</xsd:complexType>
|
|
1581
|
+
<!-- affiliatedStringType -->
|
|
1582
|
+
<xsd:complexType name="affiliatedStringType">
|
|
1583
|
+
<xsd:annotation>
|
|
1584
|
+
<xsd:documentation xml:lang="en">Definition: The affiliatedStringType adds attributes of
|
|
1585
|
+
affiliation and time relevance.</xsd:documentation>
|
|
1586
|
+
</xsd:annotation>
|
|
1587
|
+
<xsd:simpleContent>
|
|
1588
|
+
<xsd:extension base="xsd:string">
|
|
1589
|
+
<xsd:attribute name="affiliation" type="xsd:string">
|
|
1590
|
+
<xsd:annotation>
|
|
1591
|
+
<xsd:documentation xml:lang="en">Definition: The affiliation attribute is
|
|
1592
|
+
used to indicate the organization with which an agent is associated or
|
|
1593
|
+
affiliated.</xsd:documentation>
|
|
1594
|
+
</xsd:annotation>
|
|
1595
|
+
</xsd:attribute>
|
|
1596
|
+
<xsd:attribute name="affiliationSource" type="xsd:string">
|
|
1597
|
+
<xsd:annotation>
|
|
1598
|
+
<xsd:documentation xml:lang="en">Definition: The affiliationSource attribute
|
|
1599
|
+
provides the name of the authority used to declare the value of the
|
|
1600
|
+
attribute affiliation.</xsd:documentation>
|
|
1601
|
+
<xsd:documentation xml:lang="en">Best practice: This might be the name of a
|
|
1602
|
+
controlled vocabulary, namespace or authority list, such as the official
|
|
1603
|
+
PBCore recommended vocabulary.</xsd:documentation>
|
|
1604
|
+
</xsd:annotation>
|
|
1605
|
+
</xsd:attribute>
|
|
1606
|
+
<xsd:attribute name="affiliationRef" type="xsd:string">
|
|
1607
|
+
<xsd:annotation>
|
|
1608
|
+
<xsd:documentation xml:lang="en">Definition: The affilationRef attribute is
|
|
1609
|
+
used to supply a source's URI for the value of the attribute
|
|
1610
|
+
affiliation.</xsd:documentation>
|
|
1611
|
+
<xsd:documentation xml:lang="en">Best practice: Attribute affiliationRef can
|
|
1612
|
+
be used to point to a term in a controlled vocabulary, or a URI
|
|
1613
|
+
associated with a source.</xsd:documentation>
|
|
1614
|
+
</xsd:annotation>
|
|
1615
|
+
</xsd:attribute>
|
|
1616
|
+
<xsd:attribute name="affiliationVersion" type="xsd:string">
|
|
1617
|
+
<xsd:annotation>
|
|
1618
|
+
<xsd:documentation xml:lang="en">Definition: The affiliationVersion
|
|
1619
|
+
attribute identifies any version information about the authority or
|
|
1620
|
+
convention used to express data of the attribute
|
|
1621
|
+
affiliation.</xsd:documentation>
|
|
1622
|
+
</xsd:annotation>
|
|
1623
|
+
</xsd:attribute>
|
|
1624
|
+
<xsd:attribute name="affiliationAnnotation" type="xsd:string">
|
|
1625
|
+
<xsd:annotation>
|
|
1626
|
+
<xsd:documentation xml:lang="en">Definition: The affiliationAnnotation
|
|
1627
|
+
attribute includes narrative information intended to clarify the nature
|
|
1628
|
+
of data used in the attribute affiliation.</xsd:documentation>
|
|
1629
|
+
<xsd:documentation xml:lang="en">Best practice: This attribute can be used
|
|
1630
|
+
as a notes field to include any additional information about the element
|
|
1631
|
+
or associated attributes.</xsd:documentation>
|
|
1632
|
+
</xsd:annotation>
|
|
1633
|
+
</xsd:attribute>
|
|
1634
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1635
|
+
<xsd:attributeGroup ref="startEndTimeGroup"/>
|
|
1636
|
+
</xsd:extension>
|
|
1637
|
+
</xsd:simpleContent>
|
|
1638
|
+
</xsd:complexType>
|
|
1639
|
+
<!-- contributorStringType -->
|
|
1640
|
+
<xsd:complexType name="contributorStringType">
|
|
1641
|
+
<xsd:annotation>
|
|
1642
|
+
<xsd:documentation xml:lang="en">Definition: The contributorString helps define the
|
|
1643
|
+
portrayal role as well as the general source and version group
|
|
1644
|
+
attributes.</xsd:documentation>
|
|
1645
|
+
</xsd:annotation>
|
|
1646
|
+
<xsd:simpleContent>
|
|
1647
|
+
<xsd:extension base="xsd:string">
|
|
1648
|
+
<xsd:attribute name="portrayal" type="xsd:string">
|
|
1649
|
+
<xsd:annotation>
|
|
1650
|
+
<xsd:documentation xml:lang="en">Definition: The portrayal attribute
|
|
1651
|
+
identifies any roles or characters performed by a
|
|
1652
|
+
contributor.</xsd:documentation>
|
|
1653
|
+
</xsd:annotation>
|
|
1654
|
+
</xsd:attribute>
|
|
1655
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1656
|
+
</xsd:extension>
|
|
1657
|
+
</xsd:simpleContent>
|
|
1658
|
+
</xsd:complexType>
|
|
1659
|
+
<!-- technicalStringType -->
|
|
1660
|
+
<xsd:complexType name="technicalStringType">
|
|
1661
|
+
<xsd:annotation>
|
|
1662
|
+
<xsd:documentation xml:lang="en">Definition: The technicalStringType schema type adds
|
|
1663
|
+
the attributes of unitsOfMeasure and annotation.</xsd:documentation>
|
|
1664
|
+
</xsd:annotation>
|
|
1665
|
+
<xsd:simpleContent>
|
|
1666
|
+
<xsd:extension base="xsd:string">
|
|
1667
|
+
<xsd:attribute name="unitsOfMeasure" type="xsd:string">
|
|
1668
|
+
<xsd:annotation>
|
|
1669
|
+
<xsd:documentation xml:lang="en">Definition: The unitsOfMeasure attribute
|
|
1670
|
+
defines the unit used in the containing element, e.g. pixels, GB, Mb/s,
|
|
1671
|
+
ips, fps, kHz, inches, lines, dpi.</xsd:documentation>
|
|
1672
|
+
<xsd:documentation xml:lang="en">Best practice: We recommend standardizing
|
|
1673
|
+
the notation that is most widely recognized in your institution and
|
|
1674
|
+
using with consistency.</xsd:documentation>
|
|
1675
|
+
</xsd:annotation>
|
|
1676
|
+
</xsd:attribute>
|
|
1677
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1678
|
+
</xsd:extension>
|
|
1679
|
+
</xsd:simpleContent>
|
|
1680
|
+
</xsd:complexType>
|
|
1681
|
+
<!-- instantiationDigitalStringType -->
|
|
1682
|
+
<xsd:complexType name="instantiationStandardStringType">
|
|
1683
|
+
<xsd:annotation>
|
|
1684
|
+
<xsd:documentation xml:lang="en">Definition: The instantiationStandardStringType schema
|
|
1685
|
+
type allows for the addition of a profile attribute along with the
|
|
1686
|
+
sourceVersionGroup.</xsd:documentation>
|
|
1687
|
+
</xsd:annotation>
|
|
1688
|
+
<xsd:simpleContent>
|
|
1689
|
+
<xsd:extension base="xsd:string">
|
|
1690
|
+
<xsd:attribute name="profile" type="xsd:string">
|
|
1691
|
+
<xsd:annotation>
|
|
1692
|
+
<xsd:documentation xml:lang="en">Definition: The profile attribute is used
|
|
1693
|
+
to further quantify the profile of the container format (e.g.
|
|
1694
|
+
Op1a).</xsd:documentation>
|
|
1695
|
+
<xsd:documentation xml:lang="en">Best practice: This attribute can be used
|
|
1696
|
+
as a notes field to include any additional information about the element
|
|
1697
|
+
or associated attributes.</xsd:documentation>
|
|
1698
|
+
</xsd:annotation>
|
|
1699
|
+
</xsd:attribute>
|
|
1700
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1701
|
+
</xsd:extension>
|
|
1702
|
+
</xsd:simpleContent>
|
|
1703
|
+
</xsd:complexType>
|
|
1704
|
+
<!-- annotationStringType -->
|
|
1705
|
+
<xsd:complexType name="annotationStringType">
|
|
1706
|
+
<xsd:annotation>
|
|
1707
|
+
<xsd:documentation xml:lang="en">Definition: The stringType schema type added an
|
|
1708
|
+
annotationType attribute and a reference.</xsd:documentation>
|
|
1709
|
+
</xsd:annotation>
|
|
1710
|
+
<xsd:simpleContent>
|
|
1711
|
+
<xsd:extension base="xsd:string">
|
|
1712
|
+
<xsd:attribute name="annotationType" type="xsd:string">
|
|
1713
|
+
<xsd:annotation>
|
|
1714
|
+
<xsd:documentation xml:lang="en">Definition: Use the attribute
|
|
1715
|
+
annotationType to indicate the type of annotation being assigned to the
|
|
1716
|
+
asset, such as a comment, clarification, or cataloging
|
|
1717
|
+
note.</xsd:documentation>
|
|
1718
|
+
</xsd:annotation>
|
|
1719
|
+
</xsd:attribute>
|
|
1720
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1721
|
+
</xsd:extension>
|
|
1722
|
+
</xsd:simpleContent>
|
|
1723
|
+
</xsd:complexType>
|
|
1724
|
+
<!-- rightsSummaryType -->
|
|
1725
|
+
<xsd:complexType name="rightsSummaryType">
|
|
1726
|
+
<xsd:annotation>
|
|
1727
|
+
<xsd:documentation xml:lang="en">Definition: The rightsSumaryType schema type allows the
|
|
1728
|
+
use of rights at the asset level and the instantiation level. The rights can be
|
|
1729
|
+
expressed as a summary or a link or an embedded XML record. These can also contain
|
|
1730
|
+
time relations.</xsd:documentation>
|
|
1731
|
+
</xsd:annotation>
|
|
1732
|
+
<xsd:choice>
|
|
1733
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="rightsSummary"
|
|
1734
|
+
type="sourceVersionStringType">
|
|
1735
|
+
<xsd:annotation>
|
|
1736
|
+
<xsd:documentation xml:lang="en">Definition: The rightsSummary element is used
|
|
1737
|
+
as a general free-text element to identify information about copyrights and
|
|
1738
|
+
property rights held in and over an asset or instantiation, whether they are
|
|
1739
|
+
open access or restricted in some way. If dates, times and availability
|
|
1740
|
+
periods are associated with a right, include them. End user permissions,
|
|
1741
|
+
constraints and obligations may also be identified as
|
|
1742
|
+
needed.</xsd:documentation>
|
|
1743
|
+
<xsd:documentation xml:lang="en">Best practice: For rights information that
|
|
1744
|
+
applies to the asset as a whole, use this element within the container
|
|
1745
|
+
pbcoreRightsSummary. For rights information that is specific to an
|
|
1746
|
+
instantiation of an asset, use it within the container
|
|
1747
|
+
instantiationRights.</xsd:documentation>
|
|
1748
|
+
</xsd:annotation>
|
|
1749
|
+
</xsd:element>
|
|
1750
|
+
<xsd:element maxOccurs="1" minOccurs="0" name="rightsLink" type="rightsLinkType">
|
|
1751
|
+
<xsd:annotation>
|
|
1752
|
+
<xsd:documentation xml:lang="en">Definition: The rightsLink element is a URI
|
|
1753
|
+
pointing to a declaration of rights.</xsd:documentation>
|
|
1754
|
+
</xsd:annotation>
|
|
1755
|
+
</xsd:element>
|
|
1756
|
+
<xsd:element name="rightsEmbedded" type="embeddedType" maxOccurs="1" minOccurs="0">
|
|
1757
|
+
<xsd:annotation>
|
|
1758
|
+
<xsd:documentation xml:lang="en">Definition: The rightsEmbedded element allows
|
|
1759
|
+
the inclusion of xml from another rights standard, e.g. ODRL, METS, etc. The
|
|
1760
|
+
included XML then defines the rights for the PBCore asset and/or PBCore
|
|
1761
|
+
instantiation.</xsd:documentation>
|
|
1762
|
+
</xsd:annotation>
|
|
1763
|
+
</xsd:element>
|
|
1764
|
+
</xsd:choice>
|
|
1765
|
+
<xsd:attributeGroup ref="startEndTimeGroup"/>
|
|
1766
|
+
</xsd:complexType>
|
|
1767
|
+
<!-- rightsLinkType -->
|
|
1768
|
+
<xsd:complexType name="rightsLinkType">
|
|
1769
|
+
<xsd:annotation>
|
|
1770
|
+
<xsd:documentation xml:lang="en">Definition: The rightsLinkType schema type allows for
|
|
1771
|
+
the addition of an annotation attribute to the rightsLink.</xsd:documentation>
|
|
1772
|
+
</xsd:annotation>
|
|
1773
|
+
<xsd:simpleContent>
|
|
1774
|
+
<xsd:extension base="xsd:anyURI">
|
|
1775
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1776
|
+
</xsd:extension>
|
|
1777
|
+
</xsd:simpleContent>
|
|
1778
|
+
</xsd:complexType>
|
|
1779
|
+
<!-- embeddedType -->
|
|
1780
|
+
<xsd:complexType name="embeddedType">
|
|
1781
|
+
<xsd:annotation>
|
|
1782
|
+
<xsd:documentation xml:lang="en">Definition: The embeddedType schema type allows for the
|
|
1783
|
+
addition of an annotation attribute to the embeddedType.</xsd:documentation>
|
|
1784
|
+
</xsd:annotation>
|
|
1785
|
+
<xsd:sequence>
|
|
1786
|
+
<xsd:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
|
|
1787
|
+
</xsd:sequence>
|
|
1788
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1789
|
+
</xsd:complexType>
|
|
1790
|
+
<!-- threeLetterStringType -->
|
|
1791
|
+
<xsd:complexType name="threeLetterStringType">
|
|
1792
|
+
<xsd:annotation>
|
|
1793
|
+
<xsd:documentation xml:lang="en">Definition: The threeletterStringType adds the
|
|
1794
|
+
sourceVersionGroup to threelettercode for source references.</xsd:documentation>
|
|
1795
|
+
</xsd:annotation>
|
|
1796
|
+
<xsd:simpleContent>
|
|
1797
|
+
<xsd:extension base="threeLetterCode">
|
|
1798
|
+
<xsd:attributeGroup ref="sourceVersionGroup"/>
|
|
1799
|
+
</xsd:extension>
|
|
1800
|
+
</xsd:simpleContent>
|
|
1801
|
+
</xsd:complexType>
|
|
1802
|
+
<!-- threelettercode Algorithm -->
|
|
1803
|
+
<xsd:simpleType name="threeLetterCode">
|
|
1804
|
+
<xsd:annotation>
|
|
1805
|
+
<xsd:documentation xml:lang="en">Definition: This algorithm controls the language
|
|
1806
|
+
element to insure the use of three letter codes.</xsd:documentation>
|
|
1807
|
+
</xsd:annotation>
|
|
1808
|
+
<xsd:restriction base="xsd:string">
|
|
1809
|
+
<xsd:pattern value="([a-z]{3}((;[a-z]{3})?)*)?"/>
|
|
1810
|
+
<!-- allows for null -->
|
|
1811
|
+
</xsd:restriction>
|
|
1812
|
+
</xsd:simpleType>
|
|
1813
|
+
<!-- sourceVersionGroup -->
|
|
1814
|
+
<xsd:attributeGroup name="sourceVersionGroup">
|
|
1815
|
+
<xsd:annotation>
|
|
1816
|
+
<xsd:documentation xml:lang="en">Definition: The grouping of attributes: source,
|
|
1817
|
+
reference, version and annotation.</xsd:documentation>
|
|
1818
|
+
</xsd:annotation>
|
|
1819
|
+
<xsd:attribute name="source" type="xsd:string" use="optional">
|
|
1820
|
+
<xsd:annotation>
|
|
1821
|
+
<xsd:documentation xml:lang="en">Definition: The source attribute provides the name
|
|
1822
|
+
of the authority used to declare the value of the element.</xsd:documentation>
|
|
1823
|
+
<xsd:documentation xml:lang="en">Best practice: Different elements will use the
|
|
1824
|
+
source attribute slightly differently. For example, identifier source (required)
|
|
1825
|
+
should be the name of the organization, institution, system or namespace that
|
|
1826
|
+
the identifier came from, such as "PBS NOLA Code" or an institutional database
|
|
1827
|
+
identifier. For other elements, this might be the name of a controlled
|
|
1828
|
+
vocabulary, namespace or authority list, such as Library of Congress Subject
|
|
1829
|
+
Headings. We recommend a consistent and human readable use.</xsd:documentation>
|
|
1830
|
+
</xsd:annotation>
|
|
1831
|
+
</xsd:attribute>
|
|
1832
|
+
<xsd:attribute name="ref" type="xsd:string">
|
|
1833
|
+
<xsd:annotation>
|
|
1834
|
+
<xsd:documentation xml:lang="en">Definition: The ref attribute is used to supply a
|
|
1835
|
+
source's URI for the value of the element.</xsd:documentation>
|
|
1836
|
+
<xsd:documentation xml:lang="en">Best practice: Attribute ref can be used to point
|
|
1837
|
+
to a term in a controlled vocabulary, or a URI associated with a
|
|
1838
|
+
source.</xsd:documentation>
|
|
1839
|
+
</xsd:annotation>
|
|
1840
|
+
</xsd:attribute>
|
|
1841
|
+
<xsd:attribute name="version" type="xsd:string">
|
|
1842
|
+
<xsd:annotation>
|
|
1843
|
+
<xsd:documentation xml:lang="en">Definition: The version attribute identifies any
|
|
1844
|
+
version information about the authority or convention used to express data of
|
|
1845
|
+
this element.</xsd:documentation>
|
|
1846
|
+
</xsd:annotation>
|
|
1847
|
+
</xsd:attribute>
|
|
1848
|
+
<xsd:attribute name="annotation" type="xsd:string">
|
|
1849
|
+
<xsd:annotation>
|
|
1850
|
+
<xsd:documentation xml:lang="en">Definition: The annotation attribute includes
|
|
1851
|
+
narrative information intended to clarify the nature of data used in the
|
|
1852
|
+
element.</xsd:documentation>
|
|
1853
|
+
<xsd:documentation xml:lang="en">Best practice: This attribute can be used as a
|
|
1854
|
+
notes field to include any additional information about the element or
|
|
1855
|
+
associated attributes.</xsd:documentation>
|
|
1856
|
+
</xsd:annotation>
|
|
1857
|
+
</xsd:attribute>
|
|
1858
|
+
</xsd:attributeGroup>
|
|
1859
|
+
<!-- startEndTimeGroup -->
|
|
1860
|
+
<xsd:attributeGroup name="startEndTimeGroup">
|
|
1861
|
+
<xsd:annotation>
|
|
1862
|
+
<xsd:documentation xml:lang="en">Definition: The grouping of attributes: startTime,
|
|
1863
|
+
endTime and timeAnnotation.</xsd:documentation>
|
|
1864
|
+
</xsd:annotation>
|
|
1865
|
+
<xsd:attribute name="startTime" type="xsd:string">
|
|
1866
|
+
<xsd:annotation>
|
|
1867
|
+
<xsd:documentation xml:lang="en">Definition: The startTime attribute combines with
|
|
1868
|
+
the endTime attribute to define a specific media segment within a broader
|
|
1869
|
+
timeline of an asset and/or instantiation.</xsd:documentation>
|
|
1870
|
+
<xsd:documentation xml:lang="en">Best practice: This is a free text attribute and
|
|
1871
|
+
can be applied at the asset or instantiation level. When used at the asset
|
|
1872
|
+
level, it may be used to talk generally about the start/end time of a segment
|
|
1873
|
+
(e.g. "30 minutes"), or by providing a timestamp to a specific point in an
|
|
1874
|
+
instantiation. If you're doing that for element at the asset level, we suggest
|
|
1875
|
+
referencing the instantiation ID you are referring to in timeAnnotation. One
|
|
1876
|
+
example would be if a six-hour long tape was broken into multiple programs, and
|
|
1877
|
+
each instantiation might have its start time labeled as when the instantiation
|
|
1878
|
+
began in the timeline of the broader tape. Another example for this usage might
|
|
1879
|
+
be a digital file created from a VHS tape that contains multiple segments. In
|
|
1880
|
+
the digital copy, color bars are removed from the beginning, and black from the
|
|
1881
|
+
end of the digital instantiation. Time references referring to the segments on
|
|
1882
|
+
the physical VHS are no longer relevant; therefore it's important to tie start
|
|
1883
|
+
and end time references to a specific instantiation, e.g. use the asset ID and
|
|
1884
|
+
timestamp.</xsd:documentation>
|
|
1885
|
+
</xsd:annotation>
|
|
1886
|
+
</xsd:attribute>
|
|
1887
|
+
<xsd:attribute name="endTime" type="xsd:string">
|
|
1888
|
+
<xsd:annotation>
|
|
1889
|
+
<xsd:documentation xml:lang="en">Definition: The endTime attribute combines with a
|
|
1890
|
+
similar value in the startTime attribute to define a specific media segment
|
|
1891
|
+
within a broader timeline of an asset and/or instantiation.</xsd:documentation>
|
|
1892
|
+
</xsd:annotation>
|
|
1893
|
+
</xsd:attribute>
|
|
1894
|
+
<xsd:attribute name="timeAnnotation" type="xsd:string">
|
|
1895
|
+
<xsd:annotation>
|
|
1896
|
+
<xsd:documentation xml:lang="en">Definition: The timeAnnotation attribute includes
|
|
1897
|
+
narrative information intended to clarify any time-oriented nature of data used
|
|
1898
|
+
in the element.</xsd:documentation>
|
|
1899
|
+
</xsd:annotation>
|
|
1900
|
+
</xsd:attribute>
|
|
1901
|
+
</xsd:attributeGroup>
|
|
1902
|
+
</xsd:schema>
|