|
1
|
<?xml version="1.0"?>
|
|
2
|
<xs:schema targetNamespace="eml:project-2.0.0beta8" xmlns:doc="eml:documentation-2.0.0beta8" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:pro="eml:protocol-2.0.0beta8" xmlns:rp="eml:party-2.0.0beta8" xmlns:cov="eml:coverage-2.0.0beta8" xmlns:cit="eml:literature-2.0.0beta8" xmlns="eml:project-2.0.0beta8">
|
|
3
|
<xs:import namespace="eml:documentation-2.0.0beta8" schemaLocation="eml-documentation.xsd"/>
|
|
4
|
<xs:annotation>
|
|
5
|
<xs:documentation>
|
|
6
|
'$RCSfile: eml-project.xsd,v $'
|
|
7
|
Copyright: 2000 Regents of the University of California and the
|
|
8
|
National Center for Ecological Analysis and Synthesis
|
|
9
|
For Details: http://knb.ecoinformatics.org/
|
|
10
|
|
|
11
|
'$Author: berkley $'
|
|
12
|
'$Date: 2002/04/21 22:45:30 $'
|
|
13
|
'$Revision: 1.27 $'
|
|
14
|
|
|
15
|
This program is free software; you can redistribute it and/or modify
|
|
16
|
it under the terms of the GNU General Public License as published by
|
|
17
|
the Free Software Foundation; either version 2 of the License, or
|
|
18
|
(at your option) any later version.
|
|
19
|
|
|
20
|
This program is distributed in the hope that it will be useful,
|
|
21
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
22
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
23
|
GNU General Public License for more details.
|
|
24
|
|
|
25
|
You should have received a copy of the GNU General Public License
|
|
26
|
along with this program; if not, write to the Free Software
|
|
27
|
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
|
28
|
</xs:documentation>
|
|
29
|
<xs:appinfo>
|
|
30
|
<doc:moduleName>eml-project</doc:moduleName>
|
|
31
|
<doc:moduleDescription>
|
|
32
|
The EML Project Module describes the research context
|
|
33
|
in which the dataset was created, including description
|
|
34
|
of over-all motivations and goals, funding, personnel, description of the
|
|
35
|
study area etc. This is also the module to describe over-all sampling
|
|
36
|
methods for the project.
|
|
37
|
</doc:moduleDescription>
|
|
38
|
</xs:appinfo>
|
|
39
|
</xs:annotation>
|
|
40
|
<xs:import namespace="eml:party-2.0.0beta8" schemaLocation="eml-party.xsd"/>
|
|
41
|
<xs:import namespace="eml:coverage-2.0.0beta8" schemaLocation="eml-coverage.xsd"/>
|
|
42
|
<xs:import namespace="eml:literature-2.0.0beta8" schemaLocation="eml-literature.xsd"/>
|
|
43
|
<xs:import namespace="eml:protocol-2.0.0beta8" schemaLocation="eml-protocol.xsd"/>
|
|
44
|
<xs:element name="researchProject">
|
|
45
|
<xs:annotation>
|
|
46
|
<xs:appinfo>
|
|
47
|
<doc:tooltip>
|
|
48
|
Research project descriptor
|
|
49
|
</doc:tooltip>
|
|
50
|
<doc:summary>
|
|
51
|
Descriptor of research project in which context
|
|
52
|
the dataset was created. Container of all research projects in which context the
|
|
53
|
dataset was created.
|
|
54
|
</doc:summary>
|
|
55
|
<doc:description>
|
|
56
|
Research project element is a descriptor of
|
|
57
|
various programmatic aspects within which researchers
|
|
58
|
created this dataset. It can also include general research goals
|
|
59
|
and motivations, data collection methods, equations, formulas.
|
|
60
|
But see 'eml-protocol' for more areas to provide methodological detail.
|
|
61
|
eml-project elements describe various aspects of the
|
|
62
|
research project within which researchers created the associated dataset.
|
|
63
|
The association of a dataset with this project metadata is established
|
|
64
|
in eml-dataset
|
|
65
|
|
|
66
|
</doc:description>
|
|
67
|
<doc:example/>
|
|
68
|
<doc:lineage>
|
|
69
|
The researchProject element was introduced into EML 1.4. eml-project
|
|
70
|
was introduced in EML 2.0. It replaces eml-research, which was
|
|
71
|
introduced into EML 1.4 as replacement for eml-context.
|
|
72
|
</doc:lineage>
|
|
73
|
</xs:appinfo>
|
|
74
|
</xs:annotation>
|
|
75
|
<xs:complexType>
|
|
76
|
<xs:sequence>
|
|
77
|
<xs:element name="identifier" maxOccurs="unbounded">
|
|
78
|
<xs:annotation>
|
|
79
|
<xs:appinfo>
|
|
80
|
<doc:tooltip>
|
|
81
|
Unique identifier
|
|
82
|
</doc:tooltip>
|
|
83
|
<doc:summary>
|
|
84
|
The unique identifier of this metadata file or object.
|
|
85
|
</doc:summary>
|
|
86
|
<doc:description>
|
|
87
|
The identifier field provides a unique identifier for this
|
|
88
|
metadata documentation. It will most likely be part of a
|
|
89
|
sequence of numbers or letters that are meaningful in a
|
|
90
|
larger context, such as a metadata catalog. That larger
|
|
91
|
system can be identified in the "system" attribute. Multiple
|
|
92
|
identifiers can be listed corresponding to different catalog
|
|
93
|
systems.
|
|
94
|
</doc:description>
|
|
95
|
<doc:example><![CDATA[<identifier system="metacat">nceas.3.2</identifier>]]></doc:example>
|
|
96
|
<doc:lineage>
|
|
97
|
The 'identifier' field is derived from the eml-dataset
|
|
98
|
meta_file_id filed in EML 1.4.
|
|
99
|
</doc:lineage>
|
|
100
|
</xs:appinfo>
|
|
101
|
</xs:annotation>
|
|
102
|
<xs:complexType>
|
|
103
|
<xs:simpleContent>
|
|
104
|
<xs:extension base="xs:string">
|
|
105
|
<xs:attribute name="system" type="xs:string" use="optional">
|
|
106
|
<xs:annotation>
|
|
107
|
<xs:appinfo>
|
|
108
|
<doc:tooltip>Catalog system </doc:tooltip>
|
|
109
|
<doc:summary>
|
|
110
|
The catalog system in which this identifier is used.
|
|
111
|
</doc:summary>
|
|
112
|
<doc:description>
|
|
113
|
This element gives the name of the catalog system in which
|
|
114
|
this identifier is used. It is useful to determine the
|
|
115
|
scope of the identifier, and to determine the semantics
|
|
116
|
of the various subparts of the identifier. Unresolved issue:
|
|
117
|
can or should this be a URI/URL pointing to the catalog
|
|
118
|
system, or just the name?
|
|
119
|
</doc:description>
|
|
120
|
<doc:example><![CDATA[<identifier system="metacat">nceas.3.2</identifier>]]></doc:example>
|
|
121
|
<doc:lineage>
|
|
122
|
New to EML 2.0.
|
|
123
|
</doc:lineage>
|
|
124
|
</xs:appinfo>
|
|
125
|
</xs:annotation>
|
|
126
|
</xs:attribute>
|
|
127
|
</xs:extension>
|
|
128
|
</xs:simpleContent>
|
|
129
|
</xs:complexType>
|
|
130
|
</xs:element>
|
|
131
|
<xs:element name="title" type="xs:string" maxOccurs="unbounded">
|
|
132
|
<xs:annotation>
|
|
133
|
<xs:appinfo>
|
|
134
|
<doc:tooltip>Project Title</doc:tooltip>
|
|
135
|
<doc:summary>Title of the project.</doc:summary>
|
|
136
|
<doc:description>A descriptive title for the research project.</doc:description>
|
|
137
|
<doc:example>Species diversity in Tennessee riparian habitats.</doc:example>
|
|
138
|
<doc:lineage>Introduced into EML 1.4. </doc:lineage>
|
|
139
|
</xs:appinfo>
|
|
140
|
</xs:annotation>
|
|
141
|
</xs:element>
|
|
142
|
<xs:element name="personnel" maxOccurs="unbounded">
|
|
143
|
<xs:annotation>
|
|
144
|
<xs:appinfo>
|
|
145
|
<doc:tooltip>Personnel</doc:tooltip>
|
|
146
|
<doc:summary>Contact and role information for people involved in
|
|
147
|
the research project.</doc:summary>
|
|
148
|
<doc:description>
|
|
149
|
This element extends ResponsibleParty with role information.
|
|
150
|
Roles can be drawn from an enumerated list taken from
|
|
151
|
iso-party or the user can add their own roles.
|
|
152
|
</doc:description>
|
|
153
|
<doc:example>author, contentProvider, custodianSteward, distributor, editor,
|
|
154
|
metadataProvider, originator, pointOfContact, principalInvestigator,
|
|
155
|
processor, publisher, or user (ISO list). A user defined role might be somethng like:
|
|
156
|
fieldStationManager or information manager </doc:example>
|
|
157
|
<doc:lineage> This field was derived from the ISO 19115.3 standard
|
|
158
|
(iso-geo-md-2000June-draft), with the addition of a few new roleCode
|
|
159
|
values. </doc:lineage>
|
|
160
|
</xs:appinfo>
|
|
161
|
</xs:annotation>
|
|
162
|
<xs:complexType>
|
|
163
|
<xs:complexContent>
|
|
164
|
<xs:extension base="rp:ResponsibleParty">
|
|
165
|
<xs:sequence maxOccurs="unbounded">
|
|
166
|
<xs:element name="role" type="rp:RoleType"/>
|
|
167
|
</xs:sequence>
|
|
168
|
</xs:extension>
|
|
169
|
</xs:complexContent>
|
|
170
|
</xs:complexType>
|
|
171
|
</xs:element>
|
|
172
|
<xs:element name="abstract" minOccurs="0">
|
|
173
|
<xs:annotation>
|
|
174
|
<xs:appinfo>
|
|
175
|
<doc:tooltip> Abstract </doc:tooltip>
|
|
176
|
<doc:summary> Descriptive abstract.</doc:summary>
|
|
177
|
<doc:description>Descriptive abstract in paragraph of text.
|
|
178
|
</doc:description>
|
|
179
|
<doc:example/>
|
|
180
|
<doc:lineage>The abstract element was introduced into EML 1.4.
|
|
181
|
</doc:lineage>
|
|
182
|
</xs:appinfo>
|
|
183
|
</xs:annotation>
|
|
184
|
<xs:complexType>
|
|
185
|
<xs:sequence>
|
|
186
|
<xs:element name="paragraph" type="xs:string" maxOccurs="unbounded"/>
|
|
187
|
</xs:sequence>
|
|
188
|
</xs:complexType>
|
|
189
|
</xs:element>
|
|
190
|
<xs:element name="funding" minOccurs="0">
|
|
191
|
<xs:annotation>
|
|
192
|
<xs:appinfo>
|
|
193
|
<doc:tooltip>
|
|
194
|
Funding
|
|
195
|
</doc:tooltip>
|
|
196
|
<doc:summary>
|
|
197
|
Funding information.
|
|
198
|
</doc:summary>
|
|
199
|
<doc:description>
|
|
200
|
Grant and contract numbers, names and addresses of
|
|
201
|
funding sources described in paragraph of text.
|
|
202
|
</doc:description>
|
|
203
|
<doc:example/>
|
|
204
|
<doc:lineage>
|
|
205
|
The funding element was introduced into EML 1.4.
|
|
206
|
</doc:lineage>
|
|
207
|
</xs:appinfo>
|
|
208
|
</xs:annotation>
|
|
209
|
<xs:complexType>
|
|
210
|
<xs:sequence>
|
|
211
|
<xs:element name="paragraph" type="xs:string" maxOccurs="unbounded"/>
|
|
212
|
</xs:sequence>
|
|
213
|
</xs:complexType>
|
|
214
|
</xs:element>
|
|
215
|
<xs:element name="studyAreaDescription" minOccurs="0" maxOccurs="unbounded">
|
|
216
|
<xs:annotation>
|
|
217
|
<xs:appinfo>
|
|
218
|
<doc:tooltip> Description of the physical location of the research project.
|
|
219
|
</doc:tooltip>
|
|
220
|
<doc:summary> Description of the physical location of the research
|
|
221
|
project. Can include coverage of the research location, and
|
|
222
|
descriptions of climate, geology, distrubances.
|
|
223
|
</doc:summary>
|
|
224
|
<doc:description> Description of the physical location of the research
|
|
225
|
project. Can include descriptions of the geographic,
|
|
226
|
temporal, and taxonomic coverage of the research location and
|
|
227
|
descriptions of domains (themes) of interest such as climate, geology,
|
|
228
|
soils or distrubances or reference to citable biological or
|
|
229
|
geophysical classification systems such as the "Bailey..." or the ...
|
|
230
|
The descriptions may be either general descriptions in paragraph
|
|
231
|
form or specific values for named theme attributes such as
|
|
232
|
average rainfall. The "studyArea" is, in most cases, a larger geographical
|
|
233
|
area than the coverage represented in the "designDescription", that is,
|
|
234
|
studyArea represents the environmental context of the specific
|
|
235
|
coverages described in "designDescription>
|
|
236
|
</doc:description>
|
|
237
|
<doc:example/>
|
|
238
|
<doc:lineage/>
|
|
239
|
</xs:appinfo>
|
|
240
|
</xs:annotation>
|
|
241
|
<xs:complexType>
|
|
242
|
<xs:choice maxOccurs="unbounded">
|
|
243
|
<xs:element name="descriptor">
|
|
244
|
<xs:annotation>
|
|
245
|
<xs:appinfo>
|
|
246
|
<doc:tooltip> Description of non-coverage physical characteristics
|
|
247
|
of site
|
|
248
|
</doc:tooltip>
|
|
249
|
<doc:summary> Description of non-coverage physical characteristics
|
|
250
|
of site such as climate, geology, disturbances
|
|
251
|
</doc:summary>
|
|
252
|
<doc:description>
|
|
253
|
Descriptions of domains (themes) of interest such as climate, geology,
|
|
254
|
soils or distrubances or references to citable biological or
|
|
255
|
geophysical classification systems such as the "Bailey..." or the ...
|
|
256
|
The descriptions may be either general descriptions in paragraph
|
|
257
|
form or specific values for named theme attributes such as
|
|
258
|
average rainfall.
|
|
259
|
</doc:description>
|
|
260
|
<doc:example/>
|
|
261
|
<doc:lineage> New in EML 2.0.0 </doc:lineage>
|
|
262
|
|
|
263
|
</xs:appinfo>
|
|
264
|
</xs:annotation>
|
|
265
|
<xs:complexType>
|
|
266
|
<xs:sequence maxOccurs="unbounded">
|
|
267
|
<xs:element name="descriptorValue" maxOccurs="unbounded">
|
|
268
|
<xs:annotation>
|
|
269
|
<xs:appinfo>
|
|
270
|
<doc:tooltip> The value of a descriptor </doc:tooltip>
|
|
271
|
<doc:summary>The value of a descriptor as </doc:summary>
|
|
272
|
<doc:description>
|
|
273
|
The value of a descriptor. This may either be a general description
|
|
274
|
in paragraph form or the value part of a "name/value" pair where
|
|
275
|
the name is entered in the attribute "name_or_id". For example,
|
|
276
|
if the value of the "name" attribute" of the element "descriptor" is
|
|
277
|
"climate", and the value of the attribute "name_or_id" of the element
|
|
278
|
"descriptorValue" is "Annual Precipitation" then the value
|
|
279
|
of this element could be "12.5 inches".
|
|
280
|
</doc:description>
|
|
281
|
<doc:example> 12.5 inches, tundra-forest </doc:example>
|
|
282
|
<doc:lineage> EML 2.0.0 </doc:lineage>
|
|
283
|
</xs:appinfo>
|
|
284
|
</xs:annotation>
|
|
285
|
<xs:complexType>
|
|
286
|
<xs:simpleContent>
|
|
287
|
<xs:extension base="xs:string">
|
|
288
|
<xs:attribute name="name_or_id" type="xs:string" use="optional">
|
|
289
|
<xs:annotation>
|
|
290
|
<xs:appinfo>
|
|
291
|
<doc:tooltip> The name or ID of a descriptor value. </doc:tooltip>
|
|
292
|
<doc:summary> The name part of a name/value pair of a descriptor
|
|
293
|
or ID portion, if applicable of a classification.</doc:summary>
|
|
294
|
<doc:description> The name part of a name/value pair of a descriptor
|
|
295
|
or ID portion, if applicable of a classification. The values of
|
|
296
|
biogeophysical classification systems, e.g. Bailey-Ecoregions,
|
|
297
|
often take the form of an ID or Code along with a text representaiton. For example, the ID/Code M131 refers to the phrase
|
|
298
|
"Open Woodland -Tundra".
|
|
299
|
M131 is an unambiguous reference to a more detailed description.
|
|
300
|
If one is using a published classification system then there should be
|
|
301
|
a corresponding citation to the source, e.g., Bailey,R.G., 1996
|
|
302
|
"Ecosystem Geography".
|
|
303
|
</doc:description>
|
|
304
|
<doc:example> M131,Average Rainfall, </doc:example>
|
|
305
|
<doc:lineage> New in EML 2.0.0 </doc:lineage>
|
|
306
|
</xs:appinfo>
|
|
307
|
</xs:annotation>
|
|
308
|
</xs:attribute>
|
|
309
|
</xs:extension>
|
|
310
|
</xs:simpleContent>
|
|
311
|
</xs:complexType>
|
|
312
|
</xs:element>
|
|
313
|
<xs:element name="citation" type="cit:LitCitation" minOccurs="0" maxOccurs="unbounded"/>
|
|
314
|
</xs:sequence>
|
|
315
|
<xs:attribute name="name" type="xs:string" use="required"/>
|
|
316
|
<xs:attribute name="citableClassificationSystem" type="xs:boolean" use="required"/>
|
|
317
|
</xs:complexType>
|
|
318
|
</xs:element>
|
|
319
|
<xs:element name="citation" type="cit:LitCitation"/>
|
|
320
|
<xs:element name="coverage" type="cov:Coverage"/>
|
|
321
|
</xs:choice>
|
|
322
|
</xs:complexType>
|
|
323
|
</xs:element>
|
|
324
|
<xs:element name="designDescription" minOccurs="0" maxOccurs="unbounded">
|
|
325
|
<xs:annotation>
|
|
326
|
<xs:appinfo>
|
|
327
|
<doc:tooltip>Description of Research Design </doc:tooltip>
|
|
328
|
<doc:summary> A container element for descriptions of sampling methods,
|
|
329
|
protocols or citations.
|
|
330
|
</doc:summary>
|
|
331
|
<doc:description> This element is a container element for either general
|
|
332
|
paragraph descriptions of research design or more granular
|
|
333
|
descriptions of protocols and/or sampling methods. Literature
|
|
334
|
citations may also be used to describe the research design.
|
|
335
|
</doc:description>
|
|
336
|
<doc:example> x </doc:example>
|
|
337
|
<doc:lineage> New in EML 2.0.0 </doc:lineage>
|
|
338
|
</xs:appinfo>
|
|
339
|
</xs:annotation>
|
|
340
|
<xs:complexType>
|
|
341
|
<xs:choice maxOccurs="unbounded">
|
|
342
|
<xs:element name="sampling">
|
|
343
|
<xs:annotation>
|
|
344
|
<xs:appinfo>
|
|
345
|
<doc:tooltip> Description of sampling methods. </doc:tooltip>
|
|
346
|
<doc:summary> Description of sampling methods including the "coverage"
|
|
347
|
of the study, a description of the sampling procedures, and the
|
|
348
|
spatial sampling units.
|
|
349
|
</doc:summary>
|
|
350
|
<doc:description> See individual elements for more detailed descriptions. </doc:description>
|
|
351
|
<doc:example/>
|
|
352
|
<doc:lineage> Modification of the sampling element introduced into EML 1.4 </doc:lineage>
|
|
353
|
</xs:appinfo>
|
|
354
|
</xs:annotation>
|
|
355
|
<xs:complexType>
|
|
356
|
<xs:sequence>
|
|
357
|
<xs:element name="studyExtent">
|
|
358
|
<xs:annotation>
|
|
359
|
<xs:appinfo>
|
|
360
|
<doc:tooltip> Geographic, temporal, taxonomic coverage </doc:tooltip>
|
|
361
|
<doc:summary> A description of the specific areas sampled (geographic coverage)
|
|
362
|
and the sampling frequency (temporal coverage).
|
|
363
|
</doc:summary>
|
|
364
|
<doc:description> A "studyExtent" represents both a specific sampling area
|
|
365
|
and the sampling frequency (temporal boundaries, frequency
|
|
366
|
of occurrence). The geographic "studyExtent" is usually a surrogate
|
|
367
|
(representative area of) for the larger area documented in the
|
|
368
|
"studyAreaDescription". The "studyExtent" can be entered either in
|
|
369
|
non-structured paragraph form or using the structure of the "coverage" element.
|
|
370
|
</doc:description>
|
|
371
|
<doc:example/>
|
|
372
|
<doc:lineage> New in EML 2.0.0 </doc:lineage>
|
|
373
|
</xs:appinfo>
|
|
374
|
</xs:annotation>
|
|
375
|
<xs:complexType>
|
|
376
|
<xs:choice maxOccurs="unbounded">
|
|
377
|
<xs:element name="coverage"/>
|
|
378
|
<xs:element name="paragraph" type="xs:string"/>
|
|
379
|
</xs:choice>
|
|
380
|
</xs:complexType>
|
|
381
|
</xs:element>
|
|
382
|
<xs:element name="samplingDescription">
|
|
383
|
<xs:annotation>
|
|
384
|
<xs:appinfo>
|
|
385
|
<doc:tooltip>Sampling methods and procedures</doc:tooltip>
|
|
386
|
<doc:summary> A description of sampling methods and procedures </doc:summary>
|
|
387
|
<doc:description> This element allows for a text-based/human readable description
|
|
388
|
of the sampling procedures used in the research project.
|
|
389
|
The content of this element would be similar to a description of sampling procedures
|
|
390
|
found in the methods section of a journal article.
|
|
391
|
</doc:description>
|
|
392
|
<doc:example> x </doc:example>
|
|
393
|
<doc:lineage> x </doc:lineage>
|
|
394
|
</xs:appinfo>
|
|
395
|
</xs:annotation>
|
|
396
|
<xs:complexType>
|
|
397
|
<xs:sequence>
|
|
398
|
<xs:element name="paragraph" maxOccurs="unbounded"/>
|
|
399
|
</xs:sequence>
|
|
400
|
</xs:complexType>
|
|
401
|
</xs:element>
|
|
402
|
<xs:element name="spatialSamplingUnits" minOccurs="0">
|
|
403
|
<xs:annotation>
|
|
404
|
<xs:appinfo>
|
|
405
|
<doc:tooltip> Spatial sampling units </doc:tooltip>
|
|
406
|
<doc:summary> Spatial sampling units represent the "plot" sampled. </doc:summary>
|
|
407
|
<doc:description> A spatial sampling unit describes the specific geographic areas
|
|
408
|
sampled. For example, if a researcher places a single light source at a specific point
|
|
409
|
in a research location in order to attract insects to derive an estimate of the insect
|
|
410
|
population, then the sampling unit is the area illuminated by the light source
|
|
411
|
(in actual practice there might be multiple sampling unit in this case since
|
|
412
|
different species have different attraction rates). A sampling unit may also
|
|
413
|
be seen as the bounding box of a specific 3-meter square "plot". In the case of a
|
|
414
|
study in which the measurements from several disbursed "point collection"
|
|
415
|
devices are aggregated, then the sampling unit would be the area
|
|
416
|
of that aggregation. Spatial sampling units can either be described by
|
|
417
|
reference to a "coverage" description or by reference to the values in
|
|
418
|
a data table (usually a GIS layer)
|
|
419
|
</doc:description>
|
|
420
|
<doc:example> x </doc:example>
|
|
421
|
<doc:lineage> New in EML 2.0.0 </doc:lineage>
|
|
422
|
</xs:appinfo>
|
|
423
|
</xs:annotation>
|
|
424
|
<xs:complexType>
|
|
425
|
<xs:choice maxOccurs="unbounded">
|
|
426
|
<xs:element name="referencedEntityId">
|
|
427
|
<xs:annotation>
|
|
428
|
<xs:appinfo>
|
|
429
|
<doc:tooltip> The identifier of a spatial sampling entity. </doc:tooltip>
|
|
430
|
<doc:summary> The identifier of a entity described in the "entity" module.
|
|
431
|
This is usually a GIS layer.
|
|
432
|
</doc:summary>
|
|
433
|
<doc:description>
|
|
434
|
A value of a "referencedEntityId" element is reference to the identifier
|
|
435
|
of the "entity" module that provides the metadata for a data table
|
|
436
|
(RDBMS, GIS or "ascii" text) that has the actual spatial sampling unit values.
|
|
437
|
The "referencedEntityId" is an indirect pointer to the actual values.
|
|
438
|
The "referencedEntityId" can be thought of as a "foreign key" in a
|
|
439
|
relational database. </doc:description>
|
|
440
|
<doc:example> x </doc:example>
|
|
441
|
<doc:lineage> New in EML 2.0.0 </doc:lineage>
|
|
442
|
</xs:appinfo>
|
|
443
|
</xs:annotation>
|
|
444
|
</xs:element>
|
|
445
|
<xs:element name="coverage" type="cov:GeographicCoverage"/>
|
|
446
|
</xs:choice>
|
|
447
|
</xs:complexType>
|
|
448
|
</xs:element>
|
|
449
|
<xs:element name="citation" type="cit:LitCitation" minOccurs="0" maxOccurs="unbounded"/>
|
|
450
|
</xs:sequence>
|
|
451
|
</xs:complexType>
|
|
452
|
</xs:element>
|
|
453
|
<xs:element name="paragraph" type="xs:string"/>
|
|
454
|
<xs:element name="citation" type="cit:LitCitation"/>
|
|
455
|
<xs:element name="protocol" type="pro:ProtocolType"/>
|
|
456
|
</xs:choice>
|
|
457
|
</xs:complexType>
|
|
458
|
</xs:element>
|
|
459
|
</xs:sequence>
|
|
460
|
</xs:complexType>
|
|
461
|
</xs:element>
|
|
462
|
<xs:simpleType name="DescriptorType">
|
|
463
|
<xs:annotation>
|
|
464
|
<xs:appinfo>
|
|
465
|
<doc:tooltip>
|
|
466
|
Descriptor Theme Type
|
|
467
|
</doc:tooltip>
|
|
468
|
<doc:summary>
|
|
469
|
The type of descriptor theme or the name of a classification system.
|
|
470
|
</doc:summary>
|
|
471
|
<doc:description>
|
|
472
|
The descriptorType is used to represent either the name of a citable
|
|
473
|
classification system/controlled vocabulary such as the
|
|
474
|
"Bailey" classification of ... or a domain of physical descriptors such as
|
|
475
|
climate or disturbances.
|
|
476
|
</doc:description>
|
|
477
|
<doc:example>
|
|
478
|
climate, soils, hydrology, "bailey", biome, disturbance, geology
|
|
479
|
</doc:example>
|
|
480
|
<doc:lineage/>
|
|
481
|
</xs:appinfo>
|
|
482
|
</xs:annotation>
|
|
483
|
<xs:union>
|
|
484
|
<xs:simpleType>
|
|
485
|
<xs:restriction base="xs:string">
|
|
486
|
<xs:enumeration value="climate"/>
|
|
487
|
<xs:enumeration value="hydrology"/>
|
|
488
|
<xs:enumeration value="soils"/>
|
|
489
|
<xs:enumeration value="geology"/>
|
|
490
|
<xs:enumeration value="disturbance"/>
|
|
491
|
<xs:enumeration value="bailey"/>
|
|
492
|
<xs:enumeration value="biome"/>
|
|
493
|
</xs:restriction>
|
|
494
|
</xs:simpleType>
|
|
495
|
<xs:simpleType>
|
|
496
|
<xs:restriction base="xs:string"/>
|
|
497
|
</xs:simpleType>
|
|
498
|
</xs:union>
|
|
499
|
</xs:simpleType>
|
|
500
|
</xs:schema>
|