|
1
|
<?xml version="1.0" encoding="ISO-8859-1"?>
|
|
2
|
<!-- edited with XMLSpy v2010 (http://www.altova.com) by Nick Spencer (Landcare Research) -->
|
|
3
|
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:res="eml://ecoinformatics.org/resource-2.0.1" xmlns:lit="eml://ecoinformatics.org/literature-2.0.1" xmlns:party="eml://ecoinformatics.org/party-2.0.1" xmlns:doc="eml://ecoinformatics.org/documentation-2.0.1" xmlns="http://www.bfn.de/misc-1.0.1" xmlns:dwg="http://rs.tdwg.org/dwc/geospatial/" targetNamespace="http://www.bfn.de/misc-1.0.1">
|
|
4
|
<xsd:import namespace="eml://ecoinformatics.org/literature-2.0.1" schemaLocation="eml-literature.xsd"/>
|
|
5
|
<xsd:import namespace="eml://ecoinformatics.org/party-2.0.1" schemaLocation="eml-party.xsd"/>
|
|
6
|
<xsd:import namespace="eml://ecoinformatics.org/documentation-2.0.1" schemaLocation="eml-documentation.xsd"/>
|
|
7
|
<xsd:import namespace="eml://ecoinformatics.org/resource-2.0.1" schemaLocation="eml-resource.xsd"/>
|
|
8
|
<xsd:import namespace="http://rs.tdwg.org/dwc/geospatial/" schemaLocation="tdwg_dw_geospatial.xsd"/>
|
|
9
|
<xsd:simpleType name="DEFCATEGORIE">
|
|
10
|
<xsd:restriction base="xsd:string">
|
|
11
|
<xsd:enumeration value="Disturbance and land user"/>
|
|
12
|
<xsd:enumeration value="Environment"/>
|
|
13
|
<xsd:enumeration value="Geology and geomorphology"/>
|
|
14
|
<xsd:enumeration value="Moisture"/>
|
|
15
|
<xsd:enumeration value="Not specified"/>
|
|
16
|
<xsd:enumeration value="Soil, chemical attributes"/>
|
|
17
|
<xsd:enumeration value="Soil, psysical attributes"/>
|
|
18
|
<xsd:enumeration value="Subplots"/>
|
|
19
|
<xsd:enumeration value="Topography"/>
|
|
20
|
<xsd:enumeration value=""/>
|
|
21
|
</xsd:restriction>
|
|
22
|
</xsd:simpleType>
|
|
23
|
<xsd:simpleType name="MEDIUMINT">
|
|
24
|
<xsd:restriction base="xsd:decimal">
|
|
25
|
<xsd:fractionDigits value="0"/>
|
|
26
|
<xsd:minInclusive value="-8388608"/>
|
|
27
|
<xsd:maxInclusive value="8388607"/>
|
|
28
|
</xsd:restriction>
|
|
29
|
</xsd:simpleType>
|
|
30
|
<xsd:simpleType name="PERCENT">
|
|
31
|
<xsd:restriction base="xsd:decimal">
|
|
32
|
<xsd:fractionDigits value="1"/>
|
|
33
|
<xsd:minInclusive value="0"/>
|
|
34
|
<xsd:maxInclusive value="100"/>
|
|
35
|
</xsd:restriction>
|
|
36
|
</xsd:simpleType>
|
|
37
|
<xsd:simpleType name="STRATUMINDEX">
|
|
38
|
<xsd:annotation>
|
|
39
|
<xsd:documentation xml:lang="en">
|
|
40
|
No layer
|
|
41
|
t1 Tree layer (high)
|
|
42
|
t2 Tree layer -middle-
|
|
43
|
t3 Tree layer -low-
|
|
44
|
s1 Shrub layer (high)
|
|
45
|
s2 Shrub layer -low-
|
|
46
|
hl Herb layer (hl)
|
|
47
|
jl Juvenile (jl)
|
|
48
|
sl Seedling (greater 1 year)
|
|
49
|
ml Moss layer (ml)
|
|
50
|
</xsd:documentation>
|
|
51
|
</xsd:annotation>
|
|
52
|
<xsd:restriction base="xsd:string">
|
|
53
|
<xsd:enumeration value=""/>
|
|
54
|
<xsd:enumeration value="t1"/>
|
|
55
|
<xsd:enumeration value="t2"/>
|
|
56
|
<xsd:enumeration value="t3"/>
|
|
57
|
<xsd:enumeration value="s1"/>
|
|
58
|
<xsd:enumeration value="s2"/>
|
|
59
|
<xsd:enumeration value="hl"/>
|
|
60
|
<xsd:enumeration value="jl"/>
|
|
61
|
<xsd:enumeration value="sl"/>
|
|
62
|
<xsd:enumeration value="ml"/>
|
|
63
|
</xsd:restriction>
|
|
64
|
</xsd:simpleType>
|
|
65
|
<xsd:simpleType name="SMALLINT">
|
|
66
|
<xsd:restriction base="xsd:decimal">
|
|
67
|
<xsd:fractionDigits value="0"/>
|
|
68
|
<xsd:minInclusive value="-32768"/>
|
|
69
|
<xsd:maxInclusive value="32767"/>
|
|
70
|
</xsd:restriction>
|
|
71
|
</xsd:simpleType>
|
|
72
|
<xsd:simpleType name="TINYINT">
|
|
73
|
<xsd:restriction base="xsd:decimal">
|
|
74
|
<xsd:fractionDigits value="0"/>
|
|
75
|
<xsd:minInclusive value="-128"/>
|
|
76
|
<xsd:maxInclusive value="127"/>
|
|
77
|
</xsd:restriction>
|
|
78
|
</xsd:simpleType>
|
|
79
|
<xsd:complexType name="relatedPlotType">
|
|
80
|
<xsd:annotation>
|
|
81
|
<xsd:documentation xml:lang="en">A plot or observation may be related spatially to another plot in order to express parent-child, sub-plot or contiguity. </xsd:documentation>
|
|
82
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
83
|
<xsd:appinfo>
|
|
84
|
<doc:moduleDocs>
|
|
85
|
<doc:moduleName>relatedSpatialItemType</doc:moduleName>
|
|
86
|
<doc:moduleDescription>
|
|
87
|
<section xmlns="">
|
|
88
|
<title>relatedSpatialItem - An item may be related spatially to other items.</title>
|
|
89
|
<para>An item (e.g. tree or plot) may be related spatially to other items in order to express parent-child, contiguity, or other type of links. This may include relative coordinates between them.</para>
|
|
90
|
</section>
|
|
91
|
</doc:moduleDescription>
|
|
92
|
<doc:recommendedUsage/>
|
|
93
|
<doc:standAlone>no</doc:standAlone>
|
|
94
|
</doc:moduleDocs>
|
|
95
|
</xsd:appinfo>
|
|
96
|
</xsd:annotation>
|
|
97
|
<xsd:sequence>
|
|
98
|
<xsd:element name="relatedPlot">
|
|
99
|
<xsd:annotation>
|
|
100
|
<xsd:documentation>The plot related or connect to in geometric space with the related plot identified and the nature of the relationship to be define. For example subplots, contiguous plots along transects etc. Normally this would be for parent-child (or sub-plot) relationships. A standard convention should be used with preference for the child entity to point back to its parent.</xsd:documentation>
|
|
101
|
</xsd:annotation>
|
|
102
|
<xsd:complexType>
|
|
103
|
<xsd:sequence>
|
|
104
|
<xsd:element name="relatedPlotID" type="xsd:string">
|
|
105
|
<xsd:annotation>
|
|
106
|
<xsd:documentation xml:lang="en">A reference to a specific related plot. This would be the parent plot identifer in most cases.</xsd:documentation>
|
|
107
|
</xsd:annotation>
|
|
108
|
</xsd:element>
|
|
109
|
<xsd:element name="plotRelationship" type="xsd:string">
|
|
110
|
<xsd:annotation>
|
|
111
|
<xsd:documentation xml:lang="en">The type of relationship e.g. subplots, contiguous plots along transects etc. </xsd:documentation>
|
|
112
|
</xsd:annotation>
|
|
113
|
</xsd:element>
|
|
114
|
</xsd:sequence>
|
|
115
|
</xsd:complexType>
|
|
116
|
</xsd:element>
|
|
117
|
<xsd:element name="relativeSpatialCoordinate" type="relativeSpatialCoordinateType" minOccurs="0">
|
|
118
|
<xsd:annotation>
|
|
119
|
<xsd:documentation>Two related plots may have their relative positions described in geometric space using the relative position with respect to the point of origin for the referenced plot.</xsd:documentation>
|
|
120
|
</xsd:annotation>
|
|
121
|
</xsd:element>
|
|
122
|
</xsd:sequence>
|
|
123
|
</xsd:complexType>
|
|
124
|
<xsd:complexType name="relatedItemType">
|
|
125
|
<xsd:annotation>
|
|
126
|
<xsd:documentation xml:lang="en">An item may be related or connected in some way to other items. For example fused stems, epiphytic relationships or mapped individuals or paired observations. </xsd:documentation>
|
|
127
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
128
|
<xsd:appinfo>
|
|
129
|
<doc:moduleDocs>
|
|
130
|
<doc:moduleName>relatedSpatialItemType</doc:moduleName>
|
|
131
|
<doc:moduleDescription>
|
|
132
|
<section xmlns="">
|
|
133
|
<title>relatedSpatialItem - An item may be related spatially to other items.</title>
|
|
134
|
<para>An item (e.g. tree or plot) may be related spatially to other items in order to express parent-child, contiguity, or other type of links. This may include relative coordinates between them.</para>
|
|
135
|
</section>
|
|
136
|
</doc:moduleDescription>
|
|
137
|
<doc:recommendedUsage/>
|
|
138
|
<doc:standAlone>no</doc:standAlone>
|
|
139
|
</doc:moduleDocs>
|
|
140
|
</xsd:appinfo>
|
|
141
|
</xsd:annotation>
|
|
142
|
<xsd:sequence>
|
|
143
|
<xsd:element name="relatedItem">
|
|
144
|
<xsd:annotation>
|
|
145
|
<xsd:documentation>Defining the related item and the nature of the relationship. </xsd:documentation>
|
|
146
|
</xsd:annotation>
|
|
147
|
<xsd:complexType>
|
|
148
|
<xsd:sequence>
|
|
149
|
<xsd:element name="relatedItemID" type="xsd:string">
|
|
150
|
<xsd:annotation>
|
|
151
|
<xsd:documentation xml:lang="en">A reference to a specific related item. This would be the item identifer elsewhere in the schema in most cases.</xsd:documentation>
|
|
152
|
</xsd:annotation>
|
|
153
|
</xsd:element>
|
|
154
|
<xsd:element name="itemRelationship" type="xsd:string">
|
|
155
|
<xsd:annotation>
|
|
156
|
<xsd:documentation xml:lang="en">The type of relationship e.g. relationships such as fused stems, epiphytic, forked stems, epicormic stems, mapped individuals. </xsd:documentation>
|
|
157
|
</xsd:annotation>
|
|
158
|
</xsd:element>
|
|
159
|
</xsd:sequence>
|
|
160
|
</xsd:complexType>
|
|
161
|
</xsd:element>
|
|
162
|
<xsd:element name="relativeSpatialCoordinate" type="relativeSpatialCoordinateType" minOccurs="0">
|
|
163
|
<xsd:annotation>
|
|
164
|
<xsd:documentation>Two related items may have their relative positions described in geometric space using the relative position with respect to the point of origin for a referenced plot or each other.</xsd:documentation>
|
|
165
|
</xsd:annotation>
|
|
166
|
</xsd:element>
|
|
167
|
</xsd:sequence>
|
|
168
|
</xsd:complexType>
|
|
169
|
<xsd:complexType name="simpleUserdefinedType">
|
|
170
|
<xsd:annotation>
|
|
171
|
<xsd:documentation xml:lang="en">Simple user-defined information types stored as a name-value pair. </xsd:documentation>
|
|
172
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
173
|
<xsd:appinfo>
|
|
174
|
<doc:moduleDocs>
|
|
175
|
<doc:moduleName>simpleUserdefinedType</doc:moduleName>
|
|
176
|
<doc:moduleDescription>
|
|
177
|
<section xmlns="">
|
|
178
|
<title>simpleUserdefined - Simpe user-defined information types stored with as a name-value pair.</title>
|
|
179
|
<para>Simpe user-defined information types stored with as a name-value pair. Includes mandatory link to the method used.</para>
|
|
180
|
</section>
|
|
181
|
</doc:moduleDescription>
|
|
182
|
<doc:recommendedUsage/>
|
|
183
|
<doc:standAlone>no</doc:standAlone>
|
|
184
|
</doc:moduleDocs>
|
|
185
|
</xsd:appinfo>
|
|
186
|
</xsd:annotation>
|
|
187
|
<xsd:sequence>
|
|
188
|
<xsd:element name="name" type="xsd:string">
|
|
189
|
<xsd:annotation>
|
|
190
|
<xsd:documentation xml:lang="en">The name of the user defined variable</xsd:documentation>
|
|
191
|
</xsd:annotation>
|
|
192
|
</xsd:element>
|
|
193
|
<xsd:element name="value" type="xsd:string">
|
|
194
|
<xsd:annotation>
|
|
195
|
<xsd:documentation source="VegBank" xml:lang="en">The value of the user-defined variable.</xsd:documentation>
|
|
196
|
</xsd:annotation>
|
|
197
|
</xsd:element>
|
|
198
|
<xsd:element name="methodID" type="xsd:string">
|
|
199
|
<xsd:annotation>
|
|
200
|
<xsd:documentation xml:lang="en">A reference to a specific method used to measure the user defined type. The individual method is defined within the element veg:method which is a container for all methods within the dataset.</xsd:documentation>
|
|
201
|
</xsd:annotation>
|
|
202
|
</xsd:element>
|
|
203
|
</xsd:sequence>
|
|
204
|
</xsd:complexType>
|
|
205
|
<xsd:complexType name="complexUserDefinedType">
|
|
206
|
<xsd:annotation>
|
|
207
|
<xsd:documentation xml:lang="en">Complex user-defined information types. This provides a means to extend the schema to accommodate related information that is more complex than can be accommodated with the simpleUserdefinedType.</xsd:documentation>
|
|
208
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
209
|
<xsd:appinfo>
|
|
210
|
<doc:moduleDocs>
|
|
211
|
<doc:moduleName>complexUserDefinedType</doc:moduleName>
|
|
212
|
<doc:moduleDescription>
|
|
213
|
<section xmlns="">
|
|
214
|
<title>complexUserDefined - Complex user-defined information types.</title>
|
|
215
|
<para>Complex user-defined information types stored. Te nature of these types are also defined by the user.</para>
|
|
216
|
</section>
|
|
217
|
</doc:moduleDescription>
|
|
218
|
<doc:recommendedUsage/>
|
|
219
|
<doc:standAlone>no</doc:standAlone>
|
|
220
|
</doc:moduleDocs>
|
|
221
|
</xsd:appinfo>
|
|
222
|
</xsd:annotation>
|
|
223
|
<xsd:sequence>
|
|
224
|
<xsd:any minOccurs="0"/>
|
|
225
|
</xsd:sequence>
|
|
226
|
</xsd:complexType>
|
|
227
|
<xsd:complexType name="partyWithRoleType">
|
|
228
|
<xsd:annotation>
|
|
229
|
<xsd:documentation xml:lang="en">Based on the the eml-party module - People/organization information and their role as related to the resource</xsd:documentation>
|
|
230
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
231
|
<xsd:appinfo>
|
|
232
|
<doc:moduleDocs>
|
|
233
|
<doc:moduleName>partyWithRoleType</doc:moduleName>
|
|
234
|
<doc:moduleDescription>
|
|
235
|
<section xmlns="">
|
|
236
|
<title>partyWithRole</title>
|
|
237
|
<para>The eml-party module describes a responsible party (person or
|
|
238
|
organization), and is typically used to name the originator or conrtributor of a
|
|
239
|
resource.</para>
|
|
240
|
</section>
|
|
241
|
</doc:moduleDescription>
|
|
242
|
<doc:recommendedUsage/>
|
|
243
|
<doc:standAlone>no</doc:standAlone>
|
|
244
|
</doc:moduleDocs>
|
|
245
|
</xsd:appinfo>
|
|
246
|
</xsd:annotation>
|
|
247
|
<xsd:sequence>
|
|
248
|
<xsd:element name="partyID" type="xsd:string">
|
|
249
|
<xsd:annotation>
|
|
250
|
<xsd:documentation xml:lang="en">A reference to a specific party. The individual party is defined with the element veg:partys which is a container for all the parties within the dataset.</xsd:documentation>
|
|
251
|
</xsd:annotation>
|
|
252
|
</xsd:element>
|
|
253
|
<xsd:element name="role">
|
|
254
|
<xsd:annotation>
|
|
255
|
<xsd:documentation xml:lang="en">Based on the the eml-party module - The role code field provides information on how a person or organization is related to a resource. </xsd:documentation>
|
|
256
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
257
|
</xsd:annotation>
|
|
258
|
<xsd:complexType/>
|
|
259
|
</xsd:element>
|
|
260
|
</xsd:sequence>
|
|
261
|
</xsd:complexType>
|
|
262
|
<xsd:complexType name="noteType">
|
|
263
|
<xsd:annotation>
|
|
264
|
<xsd:documentation xml:lang="en">Complex type for specifying additional comments or explanations pertaining to the element of concern</xsd:documentation>
|
|
265
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
266
|
<xsd:appinfo>
|
|
267
|
<doc:moduleDocs>
|
|
268
|
<doc:moduleName>noteType</doc:moduleName>
|
|
269
|
<doc:moduleDescription>
|
|
270
|
<section xmlns="">
|
|
271
|
<title>note - Complex type for specifying additional notes. </title>
|
|
272
|
<para>A Complex type for specifying additional notes.</para>
|
|
273
|
</section>
|
|
274
|
</doc:moduleDescription>
|
|
275
|
<doc:recommendedUsage/>
|
|
276
|
<doc:standAlone>no</doc:standAlone>
|
|
277
|
</doc:moduleDocs>
|
|
278
|
</xsd:appinfo>
|
|
279
|
</xsd:annotation>
|
|
280
|
<xsd:sequence>
|
|
281
|
<xsd:element name="text" type="xsd:string">
|
|
282
|
<xsd:annotation>
|
|
283
|
<xsd:documentation xml:lang="en">The text of the additional comments or explanations.</xsd:documentation>
|
|
284
|
</xsd:annotation>
|
|
285
|
</xsd:element>
|
|
286
|
<xsd:element name="date" type="xsd:date">
|
|
287
|
<xsd:annotation>
|
|
288
|
<xsd:documentation xml:lang="en">The date on which the note was stored in the database. Recorded in ISO 8601 date format: yyyy-mm-dd.</xsd:documentation>
|
|
289
|
</xsd:annotation>
|
|
290
|
</xsd:element>
|
|
291
|
<xsd:element name="type" type="xsd:string" minOccurs="0">
|
|
292
|
<xsd:annotation>
|
|
293
|
<xsd:documentation source="VegBank">The type of note: Database Management, Observation Author, Database User and Internal.</xsd:documentation>
|
|
294
|
<xsd:appinfo> "Database Management" notes are those added by the management team and may be queried and viewed by the public. "Database Use" notes are those entered by the users of the database and are publicly viewable. "Internal" notes are for management to use internally and will not be broadcast. </xsd:appinfo>
|
|
295
|
</xsd:annotation>
|
|
296
|
</xsd:element>
|
|
297
|
<xsd:element name="contributorID" type="xsd:string" minOccurs="0">
|
|
298
|
<xsd:annotation>
|
|
299
|
<xsd:documentation xml:lang="en">A reference to the specific individual who contributed the note. The identity of the contributor is defined within the element veg:parties [EML] which is a container for all parties within the dataset.</xsd:documentation>
|
|
300
|
</xsd:annotation>
|
|
301
|
</xsd:element>
|
|
302
|
</xsd:sequence>
|
|
303
|
</xsd:complexType>
|
|
304
|
<xsd:complexType name="MethodType">
|
|
305
|
<xsd:annotation>
|
|
306
|
<xsd:documentation xml:lang="en">A method followed in the creation of the dataset or measurement of a parameter. May link to a protocol and literature reference.A protocol may have many method or steps.</xsd:documentation>
|
|
307
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
308
|
<xsd:appinfo/>
|
|
309
|
</xsd:annotation>
|
|
310
|
<xsd:sequence>
|
|
311
|
<xsd:element name="description" type="xsd:string">
|
|
312
|
<xsd:annotation>
|
|
313
|
<xsd:documentation source="NVS" xml:lang="en">A full description of the type of method e.g., research/project or measured parameter or basal area of all stems > 10 cm dbh or counts of all saplings >1.35 m tall and less than 2 cm dbh.</xsd:documentation>
|
|
314
|
</xsd:annotation>
|
|
315
|
</xsd:element>
|
|
316
|
<xsd:element name="protocolID" type="xsd:string" minOccurs="0">
|
|
317
|
<xsd:annotation>
|
|
318
|
<xsd:documentation xml:lang="en">A reference to a protocol. The individual protocol is defined within the element veg:protocols which is a container for all protocols within the dataset.</xsd:documentation>
|
|
319
|
</xsd:annotation>
|
|
320
|
</xsd:element>
|
|
321
|
<xsd:element name="name" type="xsd:string">
|
|
322
|
<xsd:annotation>
|
|
323
|
<xsd:documentation xml:lang="en">Name associated with the method. For example, that signified by an ordinal value method such as cover class.</xsd:documentation>
|
|
324
|
</xsd:annotation>
|
|
325
|
</xsd:element>
|
|
326
|
<xsd:element name="citationID" type="xsd:string" minOccurs="0">
|
|
327
|
<xsd:annotation>
|
|
328
|
<xsd:documentation xml:lang="en">A reference to a specific citation of literature. The literature to which the citation pertains is defined within the element veg:literature [EML] which is a container for all the literature within the dataset.</xsd:documentation>
|
|
329
|
</xsd:annotation>
|
|
330
|
</xsd:element>
|
|
331
|
</xsd:sequence>
|
|
332
|
<xsd:attribute name="id" type="res:IDType" use="optional"/>
|
|
333
|
<xsd:attribute name="system" type="res:SystemType" use="optional"/>
|
|
334
|
<xsd:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
|
|
335
|
</xsd:complexType>
|
|
336
|
<xsd:complexType name="MeasurementType">
|
|
337
|
<xsd:annotation>
|
|
338
|
<xsd:documentation xml:lang="en">Specifies a simple measurement of an attribute.</xsd:documentation>
|
|
339
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
340
|
<xsd:appinfo>
|
|
341
|
<doc:moduleDocs>
|
|
342
|
<doc:moduleName>MeasurementType</doc:moduleName>
|
|
343
|
<doc:moduleDescription>
|
|
344
|
<section xmlns="">
|
|
345
|
<title>Measurement - A used specify a simple measurement of an attribute. </title>
|
|
346
|
<para>A complex type used specify a simple measurement of an attribute. </para>
|
|
347
|
</section>
|
|
348
|
</doc:moduleDescription>
|
|
349
|
<doc:recommendedUsage/>
|
|
350
|
<doc:standAlone>no</doc:standAlone>
|
|
351
|
</doc:moduleDocs>
|
|
352
|
</xsd:appinfo>
|
|
353
|
</xsd:annotation>
|
|
354
|
<xsd:sequence>
|
|
355
|
<xsd:element name="value" type="xsd:string">
|
|
356
|
<xsd:annotation>
|
|
357
|
<xsd:documentation source="Webster's dictionary" xml:lang="en">The amount or extent of a specified measurement of space, time, or quantity. (Usually numeric, but may be a code as well).</xsd:documentation>
|
|
358
|
</xsd:annotation>
|
|
359
|
</xsd:element>
|
|
360
|
<xsd:element name="upperValue" minOccurs="0">
|
|
361
|
<xsd:annotation>
|
|
362
|
<xsd:documentation>Proposed definition: To capture the upper bound of an aggregate value when expresses as catgeories. For example, an estimated value of 5-10% would be recorded the an upper bound of 10 and the lower bound of 5.</xsd:documentation>
|
|
363
|
</xsd:annotation>
|
|
364
|
</xsd:element>
|
|
365
|
<xsd:element name="lowerValue" minOccurs="0">
|
|
366
|
<xsd:annotation>
|
|
367
|
<xsd:documentation>Proposed definition: To capture the lower bound of an aggregate value when expresses as catgeories. For example, an estimated value of 5-10% would be recorded the an upper bound of 10 and the lower bound of 5.</xsd:documentation>
|
|
368
|
</xsd:annotation>
|
|
369
|
</xsd:element>
|
|
370
|
<xsd:element name="accuracy" type="xsd:decimal" minOccurs="0">
|
|
371
|
<xsd:annotation>
|
|
372
|
<xsd:documentation source="http://www.geod.nrcan.gc.ca/edu/gloss_e.php" xml:lang="en">The closeness of the estimate or measurement to its true (but unknown) value</xsd:documentation>
|
|
373
|
</xsd:annotation>
|
|
374
|
</xsd:element>
|
|
375
|
<xsd:element name="attributeID" type="xsd:string">
|
|
376
|
<xsd:annotation>
|
|
377
|
<xsd:documentation>Allows a measurement value to be qualified. Type, Units, etc.</xsd:documentation>
|
|
378
|
</xsd:annotation>
|
|
379
|
</xsd:element>
|
|
380
|
<xsd:element name="complexUserDefined" type="complexUserDefinedType" minOccurs="0" maxOccurs="unbounded">
|
|
381
|
<xsd:annotation>
|
|
382
|
<xsd:documentation>Complex user-defined information types. </xsd:documentation>
|
|
383
|
</xsd:annotation>
|
|
384
|
</xsd:element>
|
|
385
|
</xsd:sequence>
|
|
386
|
</xsd:complexType>
|
|
387
|
<xsd:complexType name="ObservationGroupingType">
|
|
388
|
<xsd:annotation>
|
|
389
|
<xsd:documentation xml:lang="en">A named grouping entity that can be used to define grouping events elsewhere in the dataset. These are a set of observation records that are grouped in the data management system owing to some common characteristic.</xsd:documentation>
|
|
390
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
391
|
<xsd:appinfo>
|
|
392
|
<doc:moduleDocs>
|
|
393
|
<doc:moduleName>ObservationGroupingType</doc:moduleName>
|
|
394
|
<doc:moduleDescription>
|
|
395
|
<section xmlns="">
|
|
396
|
<title>ObservationGrouping - A set of observation records that are grouped.</title>
|
|
397
|
<para>A set of observation records, of any kind, that are grouped in the data management system owing to some common characteristic. For example, records that represent revisits to the same area for monitoring purposes can be linked together through this entity. Note that some specific groupings are already defined in the vegschema and therefore they should not be repeated (e.g. the grouping of observations made on a specific plot during a specific time is a PlotObservation).</para>
|
|
398
|
</section>
|
|
399
|
</doc:moduleDescription>
|
|
400
|
<doc:recommendedUsage/>
|
|
401
|
<doc:standAlone>no</doc:standAlone>
|
|
402
|
</doc:moduleDocs>
|
|
403
|
</xsd:appinfo>
|
|
404
|
</xsd:annotation>
|
|
405
|
<xsd:sequence>
|
|
406
|
<xsd:element name="type">
|
|
407
|
<xsd:annotation>
|
|
408
|
<xsd:documentation>The grouping entity type. For example, grouping of individual organism observations for the purposes of describing a physical relationship. Recommended that a closed-list is developed and used.</xsd:documentation>
|
|
409
|
</xsd:annotation>
|
|
410
|
</xsd:element>
|
|
411
|
<xsd:element name="name">
|
|
412
|
<xsd:annotation>
|
|
413
|
<xsd:documentation>The unique name of a specific grouping entity that is subsequently referenced by specific observations.</xsd:documentation>
|
|
414
|
</xsd:annotation>
|
|
415
|
</xsd:element>
|
|
416
|
</xsd:sequence>
|
|
417
|
<xsd:attribute name="id" type="res:IDType" use="optional">
|
|
418
|
<xsd:annotation>
|
|
419
|
<xsd:documentation>Unique identifier (key) of the element. It can be unique locally to the data set for a given data element type (e.g., a grouping entity) or a GUID in which case it can be resolved to a location on the internet where the record is stored. Read fully description elsewhere.</xsd:documentation>
|
|
420
|
</xsd:annotation>
|
|
421
|
</xsd:attribute>
|
|
422
|
<xsd:attribute name="system" type="res:SystemType" use="optional"/>
|
|
423
|
<xsd:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
|
|
424
|
</xsd:complexType>
|
|
425
|
<xsd:complexType name="AttributeType">
|
|
426
|
<xsd:annotation>
|
|
427
|
<xsd:documentation xml:lang="en">The definition of a measured property. </xsd:documentation>
|
|
428
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
429
|
<xsd:appinfo>
|
|
430
|
<doc:moduleDocs>
|
|
431
|
<doc:moduleName>AttributeType</doc:moduleName>
|
|
432
|
<doc:moduleDescription>
|
|
433
|
<section xmlns="">
|
|
434
|
<title>Attribute - The definition of a measured property. </title>
|
|
435
|
<para>The definition of a measured property. An attribute has to be one of three types: nominal (unordered categorized variable), ordinal (ordered list of values) or ratio (a numerical variable, either discrete or continuous</para>
|
|
436
|
</section>
|
|
437
|
</doc:moduleDescription>
|
|
438
|
<doc:recommendedUsage/>
|
|
439
|
<doc:standAlone>no</doc:standAlone>
|
|
440
|
</doc:moduleDocs>
|
|
441
|
</xsd:appinfo>
|
|
442
|
</xsd:annotation>
|
|
443
|
<xsd:choice>
|
|
444
|
<xsd:element name="ordinal">
|
|
445
|
<xsd:annotation>
|
|
446
|
<xsd:documentation source="http://www.cliffsnotes.com/WileyCDA/Section/Statistics-Glossary.id-305499,articleId-30041.html" xml:lang="en">A scale using numbers or symbols to rank order; its intervals are unspecified.</xsd:documentation>
|
|
447
|
</xsd:annotation>
|
|
448
|
<xsd:complexType>
|
|
449
|
<xsd:sequence>
|
|
450
|
<xsd:element name="code"/>
|
|
451
|
<xsd:element name="methodID" type="xsd:string">
|
|
452
|
<xsd:annotation>
|
|
453
|
<xsd:documentation>A reference to a method that describes the context for the ordinal code, e.g., cover class code. The individual method is defined within the element veg:method which is a container for all methods within the dataset. </xsd:documentation>
|
|
454
|
</xsd:annotation>
|
|
455
|
</xsd:element>
|
|
456
|
<xsd:element name="definition">
|
|
457
|
<xsd:annotation>
|
|
458
|
<xsd:documentation>The definition of an ordinal number or symbol used to signify an ordered list. For example a cover class ordinal code such as 1 = >1-5 %</xsd:documentation>
|
|
459
|
</xsd:annotation>
|
|
460
|
</xsd:element>
|
|
461
|
<xsd:element name="upperLimit" type="PERCENT" minOccurs="0">
|
|
462
|
<xsd:annotation>
|
|
463
|
<xsd:documentation xml:lang="en">
|
|
464
|
Upper limit of the cover index in percent (only relevant when the value represents a cover class index)
|
|
465
|
</xsd:documentation>
|
|
466
|
<xsd:documentation xml:lang="de">
|
|
467
|
Obergrenze des Deckungsindex in Prozent.
|
|
468
|
</xsd:documentation>
|
|
469
|
</xsd:annotation>
|
|
470
|
</xsd:element>
|
|
471
|
<xsd:element name="lowerLimit" type="PERCENT" minOccurs="0">
|
|
472
|
<xsd:annotation>
|
|
473
|
<xsd:documentation xml:lang="en">
|
|
474
|
Lower limit of the cover index in percent
|
|
475
|
</xsd:documentation>
|
|
476
|
<xsd:documentation xml:lang="de">
|
|
477
|
Untergrenze des Deckungsindex in Prozent.
|
|
478
|
</xsd:documentation>
|
|
479
|
</xsd:annotation>
|
|
480
|
</xsd:element>
|
|
481
|
<xsd:element name="coverPercent" type="PERCENT" minOccurs="0">
|
|
482
|
<xsd:annotation>
|
|
483
|
<xsd:documentation xml:lang="en">
|
|
484
|
Average cover of the index in percent
|
|
485
|
</xsd:documentation>
|
|
486
|
<xsd:documentation xml:lang="de">
|
|
487
|
Mittlere Artm?chtigkeit des Deckungsindex in Prozent.
|
|
488
|
</xsd:documentation>
|
|
489
|
</xsd:annotation>
|
|
490
|
</xsd:element>
|
|
491
|
<xsd:element name="order" type="xsd:decimal" minOccurs="0">
|
|
492
|
<xsd:annotation>
|
|
493
|
<xsd:documentation xml:lang="en">Explicit order in the sequence of ordinal values to which this code belongs</xsd:documentation>
|
|
494
|
</xsd:annotation>
|
|
495
|
</xsd:element>
|
|
496
|
<xsd:element name="complexUserDefined" type="complexUserDefinedType" minOccurs="0" maxOccurs="unbounded"/>
|
|
497
|
</xsd:sequence>
|
|
498
|
</xsd:complexType>
|
|
499
|
</xsd:element>
|
|
500
|
<xsd:element name="quantitative">
|
|
501
|
<xsd:annotation>
|
|
502
|
<xsd:documentation>A numerical variable, either discrete or continuous may = interval and cardinal</xsd:documentation>
|
|
503
|
</xsd:annotation>
|
|
504
|
<xsd:complexType>
|
|
505
|
<xsd:sequence>
|
|
506
|
<xsd:element name="methodID" type="xsd:string">
|
|
507
|
<xsd:annotation>
|
|
508
|
<xsd:documentation>A reference to a specific method. The individual method is defined within the element veg:method which is a container for all methods within the dataset. </xsd:documentation>
|
|
509
|
</xsd:annotation>
|
|
510
|
<xsd:complexType/>
|
|
511
|
</xsd:element>
|
|
512
|
<xsd:element name="unit" type="xsd:string">
|
|
513
|
<xsd:annotation>
|
|
514
|
<xsd:documentation xml:lang="en">Unit of measurement (e.g. mm, cm, square meters, number of individuals)</xsd:documentation>
|
|
515
|
</xsd:annotation>
|
|
516
|
</xsd:element>
|
|
517
|
<xsd:element name="precision" type="xsd:decimal">
|
|
518
|
<xsd:annotation>
|
|
519
|
<xsd:documentation source="http://mdk12.org/instruction/curriculum/mathematics/glossary.shtml" xml:lang="en">The smallest place value to which the measurement is expressed (eg, if pi is represented as 3.14, then its precision is .01).
|
|
520
|
</xsd:documentation>
|
|
521
|
</xsd:annotation>
|
|
522
|
</xsd:element>
|
|
523
|
<xsd:element name="upperBound" type="xsd:decimal">
|
|
524
|
<xsd:annotation>
|
|
525
|
<xsd:documentation xml:lang="en">potential upper limit of the measurement</xsd:documentation>
|
|
526
|
</xsd:annotation>
|
|
527
|
</xsd:element>
|
|
528
|
<xsd:element name="lowerBound" type="xsd:decimal">
|
|
529
|
<xsd:annotation>
|
|
530
|
<xsd:documentation xml:lang="en">potential lower limit of the measurement</xsd:documentation>
|
|
531
|
</xsd:annotation>
|
|
532
|
</xsd:element>
|
|
533
|
</xsd:sequence>
|
|
534
|
</xsd:complexType>
|
|
535
|
</xsd:element>
|
|
536
|
<xsd:element name="qualitative">
|
|
537
|
<xsd:annotation>
|
|
538
|
<xsd:documentation>Unordered categorized variable = nominal</xsd:documentation>
|
|
539
|
</xsd:annotation>
|
|
540
|
<xsd:complexType>
|
|
541
|
<xsd:sequence>
|
|
542
|
<xsd:element name="methodID" type="xsd:string">
|
|
543
|
<xsd:annotation>
|
|
544
|
<xsd:documentation>A reference to a specific method. The individual method is defined within the element veg:method which is a container for all methods within the dataset. </xsd:documentation>
|
|
545
|
</xsd:annotation>
|
|
546
|
<xsd:complexType/>
|
|
547
|
</xsd:element>
|
|
548
|
<xsd:element name="code"/>
|
|
549
|
</xsd:sequence>
|
|
550
|
</xsd:complexType>
|
|
551
|
</xsd:element>
|
|
552
|
</xsd:choice>
|
|
553
|
<xsd:attribute name="id" type="res:IDType" use="optional"/>
|
|
554
|
<xsd:attribute name="system" type="res:SystemType" use="optional"/>
|
|
555
|
<xsd:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
|
|
556
|
</xsd:complexType>
|
|
557
|
<xsd:complexType name="ProtocolType">
|
|
558
|
<xsd:annotation>
|
|
559
|
<xsd:documentation xml:lang="en">An agreed protocol that is being followed in the creation of the dataset. May have many methods or steps.</xsd:documentation>
|
|
560
|
<xsd:documentation xml:lang="de"> </xsd:documentation>
|
|
561
|
<xsd:appinfo>
|
|
562
|
<doc:moduleDocs>
|
|
563
|
<doc:moduleName>ProtocolType</doc:moduleName>
|
|
564
|
<doc:moduleDescription>
|
|
565
|
<section xmlns="">
|
|
566
|
<title>Protocol - An agreed protocol that is being followed.</title>
|
|
567
|
<para>An agreed protocol that is being followed in the creation of the dataset. May have many methods or steps.</para>
|
|
568
|
</section>
|
|
569
|
</doc:moduleDescription>
|
|
570
|
<doc:recommendedUsage/>
|
|
571
|
<doc:standAlone>no</doc:standAlone>
|
|
572
|
</doc:moduleDocs>
|
|
573
|
</xsd:appinfo>
|
|
574
|
</xsd:annotation>
|
|
575
|
<xsd:sequence>
|
|
576
|
<xsd:element name="name">
|
|
577
|
<xsd:annotation>
|
|
578
|
<xsd:documentation>Name of the protocol.</xsd:documentation>
|
|
579
|
</xsd:annotation>
|
|
580
|
</xsd:element>
|
|
581
|
<xsd:element name="citationID" type="xsd:string">
|
|
582
|
<xsd:annotation>
|
|
583
|
<xsd:documentation>A reference to a specific citation of literature. The literature to which the citation pertains is defined within the element veg:literatures [EML] which is a container for all the literature within the dataset.</xsd:documentation>
|
|
584
|
</xsd:annotation>
|
|
585
|
</xsd:element>
|
|
586
|
<xsd:element name="partyWithRole" type="partyWithRoleType">
|
|
587
|
<xsd:annotation>
|
|
588
|
<xsd:documentation>The party involved in describing the protocol.</xsd:documentation>
|
|
589
|
</xsd:annotation>
|
|
590
|
</xsd:element>
|
|
591
|
</xsd:sequence>
|
|
592
|
<xsd:attribute name="id" type="res:IDType" use="optional"/>
|
|
593
|
<xsd:attribute name="system" type="res:SystemType" use="optional"/>
|
|
594
|
<xsd:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
|
|
595
|
</xsd:complexType>
|
|
596
|
<xsd:complexType name="geospatialType">
|
|
597
|
<xsd:annotation>
|
|
598
|
<xsd:documentation>Compex type for capturing geospatial location. Based on Darwin Core Geospatial extension. Includes an extension for depth and elevation following TDWG taxonOccurrence ontology and additions for coordinates based on a projected grid coordinate system. For example a map series, map sheet name and easting and northing coordinates.</xsd:documentation>
|
|
599
|
</xsd:annotation>
|
|
600
|
<xsd:sequence>
|
|
601
|
<xsd:element ref="dwg:DecimalLatitude" minOccurs="0">
|
|
602
|
<xsd:annotation>
|
|
603
|
<xsd:documentation>The latitude of the location from which the plot was observed, expressed in decimal degrees. Positive values are North of the Equator, negative values are South of the Equator.</xsd:documentation>
|
|
604
|
</xsd:annotation>
|
|
605
|
</xsd:element>
|
|
606
|
<xsd:element ref="dwg:DecimalLongitude" minOccurs="0">
|
|
607
|
<xsd:annotation>
|
|
608
|
<xsd:documentation>The longitude of the location from which the plot was observed, expressed in decimal degrees. Positive values are East of the Greenwich Meridian, negative values are West of the Greenwich Meridian.</xsd:documentation>
|
|
609
|
</xsd:annotation>
|
|
610
|
</xsd:element>
|
|
611
|
<xsd:element ref="dwg:GeodeticDatum" minOccurs="0">
|
|
612
|
<xsd:annotation>
|
|
613
|
<xsd:documentation>The geodetic datum to which the latitude and longitude refer.</xsd:documentation>
|
|
614
|
</xsd:annotation>
|
|
615
|
</xsd:element>
|
|
616
|
<xsd:element ref="dwg:CoordinateUncertaintyInMeters" minOccurs="0">
|
|
617
|
<xsd:annotation>
|
|
618
|
<xsd:documentation>The upper limit of the distance (in meters) from the given latitude and longitude describing a circle within which the whole of the described locality lies. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). The value should be greater than zero.</xsd:documentation>
|
|
619
|
</xsd:annotation>
|
|
620
|
</xsd:element>
|
|
621
|
<xsd:element ref="dwg:PointRadiusSpatialFit" minOccurs="0">
|
|
622
|
<xsd:annotation>
|
|
623
|
<xsd:documentation>A measure of how well the circle defined by the coordinates and uncertainty match the original spatial representation, as a ratio of the area of the circle to the area of the original spatial representation. Legal values are 0, greater than or equal to 1. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given georeference does not completely contain the original representation. The PointRadiusSpatialFit is undefined if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the PointRadiusSpatialFit is 1. Detailed explanations with graphical examples can be found in the Guide to Best Practices for Georeferencing (Chapman and Wieczorek, eds. 2006) http://www.gbif.org/prog/digit/Georeferencing.</xsd:documentation>
|
|
624
|
</xsd:annotation>
|
|
625
|
</xsd:element>
|
|
626
|
<xsd:element ref="dwg:FootprintWKT" minOccurs="0">
|
|
627
|
<xsd:annotation>
|
|
628
|
<xsd:documentation>A Well-Known Text (WKT; see http://en.wikipedia.org/wiki/Well-known_text) representation of the the shape (footprint) that defines the location of the occurrence. Example: the one-degree boundin box with opposite corners at (longitude=10, latitude=20) and (longitude=11, latitude=21) would be expressed in well-known text as POLYGON ((10 20, 11 20, 11 21, 10 21, 10 20))</xsd:documentation>
|
|
629
|
</xsd:annotation>
|
|
630
|
</xsd:element>
|
|
631
|
<xsd:element ref="dwg:FootprintSpatialFit" minOccurs="0">
|
|
632
|
<xsd:annotation>
|
|
633
|
<xsd:documentation>A measure of how well the geometry expressed in the footprint match the original spatial representation, as a ratio of the area of the footprint given to the area of the original spatial representation. Legal values are 0, greater than or equal to 1. A value of 1 is an exact match or 100% overlap. A value of 0 should be used if the given georeference does not completely contain the original representation. The FootprintSpatialFit is undefined if the original representation is a point without uncertainty and the given georeference is not that same point (without uncertainty). If both the original and the given georeference are the same point, the FootprintSpatialFit is 1. Detailed explanations with graphical examples can be found in the Guide to Best Practices for Georeferencing (Chapman and Wieczorek, eds. 2006). http://www.gbif.org/prog/digit/Georeferencing</xsd:documentation>
|
|
634
|
</xsd:annotation>
|
|
635
|
</xsd:element>
|
|
636
|
<xsd:element ref="dwg:VerbatimCoordinates" minOccurs="0">
|
|
637
|
<xsd:annotation>
|
|
638
|
<xsd:documentation>A text representation of the coordinate data (Latitude/ Longitude, UTM, TRS, etc.) from its original source if it cannot be separated into its component parts. Example: "470999 1234300".</xsd:documentation>
|
|
639
|
</xsd:annotation>
|
|
640
|
</xsd:element>
|
|
641
|
<xsd:element ref="dwg:VerbatimLatitude" minOccurs="0">
|
|
642
|
<xsd:annotation>
|
|
643
|
<xsd:documentation>A text representation of the Latitude part of the coordinate data from its original source. Example: 47d09'99"N</xsd:documentation>
|
|
644
|
</xsd:annotation>
|
|
645
|
</xsd:element>
|
|
646
|
<xsd:element ref="dwg:VerbatimLongitude" minOccurs="0">
|
|
647
|
<xsd:annotation>
|
|
648
|
<xsd:documentation>A text representation of the Longitude part of the coordinate data from its original source. Example: -122.43254</xsd:documentation>
|
|
649
|
</xsd:annotation>
|
|
650
|
</xsd:element>
|
|
651
|
<xsd:element ref="dwg:VerbatimCoordinateSystem" minOccurs="0">
|
|
652
|
<xsd:annotation>
|
|
653
|
<xsd:documentation>The name of the system in which the verbatim geographic coordinates were recorded. Examples: "decimal degrees", "degrees minutes seconds", "degrees decimal minutes", "UTM"</xsd:documentation>
|
|
654
|
</xsd:annotation>
|
|
655
|
</xsd:element>
|
|
656
|
<xsd:element ref="dwg:GeoreferenceProtocol" minOccurs="0">
|
|
657
|
<xsd:annotation>
|
|
658
|
<xsd:documentation>A reference to the methods used for determining the coordinates and uncertainties. Example: "http://manisnet.org/GeorefGuide.html".</xsd:documentation>
|
|
659
|
</xsd:annotation>
|
|
660
|
</xsd:element>
|
|
661
|
<xsd:element ref="dwg:GeoreferenceSources" minOccurs="0">
|
|
662
|
<xsd:annotation>
|
|
663
|
<xsd:documentation>A list of maps, gazetteers or other resources used to georeference the locality. The content of this concept is meant to be specific enough to allow anyone in the future to use the same resource to georeference the same locality. Example: "USGS 1:24000 Florence Montana Quad".</xsd:documentation>
|
|
664
|
</xsd:annotation>
|
|
665
|
</xsd:element>
|
|
666
|
<xsd:element ref="dwg:GeoreferenceVerificationStatus" minOccurs="0">
|
|
667
|
<xsd:annotation>
|
|
668
|
<xsd:documentation>A categorical description of the extent to which the georeference has been verified to represent the location where the specimen or observation was collected. This element should be vocabulary-controlled. Examples: "requires verification", "verified by collector", "verified by curator".</xsd:documentation>
|
|
669
|
</xsd:annotation>
|
|
670
|
</xsd:element>
|
|
671
|
<xsd:element ref="dwg:GeoreferenceRemarks" minOccurs="0">
|
|
672
|
<xsd:annotation>
|
|
673
|
<xsd:documentation>Comments about the spatial description determination, explaining assumptions made in addition or opposition to the those formalized in the method referred to in GeoreferenceProtocol.</xsd:documentation>
|
|
674
|
</xsd:annotation>
|
|
675
|
</xsd:element>
|
|
676
|
<xsd:element name="minimumDepthInMeters" minOccurs="0">
|
|
677
|
<xsd:annotation>
|
|
678
|
<xsd:documentation>The minimum or actual depth at which the plot observation was made. Use positive values for locations below the surface. Examples: 0 (for a depth of up to 10m). 50 (for a depth between 50m and 100m).</xsd:documentation>
|
|
679
|
<xsd:appinfo>Is Defined By
|
|
680
|
http://rs.tdwg.org/ontology/voc/TaxonOccurrence
|
|
681
|
|
|
682
|
DarwinCore Equivalent
|
|
683
|
Core:MinimumDepthInMeters</xsd:appinfo>
|
|
684
|
</xsd:annotation>
|
|
685
|
</xsd:element>
|
|
686
|
<xsd:element name="maximumDepthInMeters" minOccurs="0">
|
|
687
|
<xsd:annotation>
|
|
688
|
<xsd:documentation>The maximum or actual depth at which the plot observation was made. Use positive values for locations below the surface. Examples: 10 (for a depth of up to 10m). 100 (for a depth between 50m and 100m).</xsd:documentation>
|
|
689
|
<xsd:appinfo>Is Defined By
|
|
690
|
http://rs.tdwg.org/ontology/voc/TaxonOccurrence
|
|
691
|
|
|
692
|
DarwinCore Equivalent
|
|
693
|
Core:MaximumDepthInMeters</xsd:appinfo>
|
|
694
|
</xsd:annotation>
|
|
695
|
</xsd:element>
|
|
696
|
<xsd:element name="verbatimDepth" minOccurs="0">
|
|
697
|
<xsd:annotation>
|
|
698
|
<xsd:documentation>A text representation of the depth in its original format on the specimen or in the collection catalogue. Example: "100 to 200 ft below sea level".</xsd:documentation>
|
|
699
|
<xsd:appinfo>Is Defined By
|
|
700
|
http://rs.tdwg.org/ontology/voc/TaxonOccurrence
|
|
701
|
|
|
702
|
DarwinCore Equivalent
|
|
703
|
Curatorial:VerbatimDepth</xsd:appinfo>
|
|
704
|
</xsd:annotation>
|
|
705
|
</xsd:element>
|
|
706
|
<xsd:element name="verbatimElevation" minOccurs="0">
|
|
707
|
<xsd:annotation>
|
|
708
|
<xsd:documentation>A text representation of the altitude in its original format of an observed plot. Example: "1000+- meters".</xsd:documentation>
|
|
709
|
<xsd:appinfo>Is Defined By
|
|
710
|
http://rs.tdwg.org/ontology/voc/TaxonOccurrence
|
|
711
|
|
|
712
|
DarwinCore Equivalent
|
|
713
|
Curatorial:VerbatimElevation</xsd:appinfo>
|
|
714
|
</xsd:annotation>
|
|
715
|
</xsd:element>
|
|
716
|
<xsd:element name="minimumElevationInMeters" minOccurs="0">
|
|
717
|
<xsd:annotation>
|
|
718
|
<xsd:documentation>The minimum or actual elevation at which the observation of a plot was made. Use negative values for locations below sea level. Examples: 75 (for an elevation of 100 +- 25 meters). 100 (for an elevation between 100m and 200m).</xsd:documentation>
|
|
719
|
<xsd:appinfo>Is Defined By
|
|
720
|
http://rs.tdwg.org/ontology/voc/TaxonOccurrence
|
|
721
|
|
|
722
|
DarwinCore Equivalent
|
|
723
|
Core:MinimumElevationInMeters</xsd:appinfo>
|
|
724
|
</xsd:annotation>
|
|
725
|
</xsd:element>
|
|
726
|
<xsd:element name="maximumElevationInMeters" minOccurs="0">
|
|
727
|
<xsd:annotation>
|
|
728
|
<xsd:documentation>The maximum or actual elevation at which the observation of a plot was made. Use negative values for locations below sea level. Examples: Examples: 125 (for an elevation of 100 +- 25 meters). 200 (for an elevation between 100m and 200m).</xsd:documentation>
|
|
729
|
<xsd:appinfo>Is Defined By
|
|
730
|
http://rs.tdwg.org/ontology/voc/TaxonOccurrence
|
|
731
|
|
|
732
|
DarwinCore Equivalent
|
|
733
|
Core:MaximumElevationInMeters</xsd:appinfo>
|
|
734
|
</xsd:annotation>
|
|
735
|
</xsd:element>
|
|
736
|
<xsd:element name="gridCoordinateSystemName" type="xsd:string" minOccurs="0">
|
|
737
|
<xsd:annotation>
|
|
738
|
<xsd:documentation xml:lang="en">
|
|
739
|
Name of a projected map series or grid. For example,
|
|
740
|
</xsd:documentation>
|
|
741
|
<xsd:documentation xml:lang="de">
|
|
742
|
Kartentyp der Rasterbezeichnung (TK25, DGK5 usw.)
|
|
743
|
</xsd:documentation>
|
|
744
|
</xsd:annotation>
|
|
745
|
</xsd:element>
|
|
746
|
<xsd:element name="gridCode" type="xsd:string" minOccurs="0">
|
|
747
|
<xsd:annotation>
|
|
748
|
<xsd:documentation xml:lang="en">
|
|
749
|
Map sheet or grid cell identifier. For example, H123
|
|
750
|
</xsd:documentation>
|
|
751
|
<xsd:documentation xml:lang="de">
|
|
752
|
Nummer der Topographischen Karte
|
|
753
|
</xsd:documentation>
|
|
754
|
</xsd:annotation>
|
|
755
|
</xsd:element>
|
|
756
|
<xsd:element name="gridCellQuadrant" type="TINYINT" minOccurs="0">
|
|
757
|
<xsd:annotation>
|
|
758
|
<xsd:documentation xml:lang="en">
|
|
759
|
Quadrant of the grid cell.
|
|
760
|
</xsd:documentation>
|
|
761
|
<xsd:documentation xml:lang="de">
|
|
762
|
Quadrant innerhalb der Topographischen Karte
|
|
763
|
</xsd:documentation>
|
|
764
|
</xsd:annotation>
|
|
765
|
</xsd:element>
|
|
766
|
<xsd:element name="authorZone" type="xsd:string" minOccurs="0">
|
|
767
|
<xsd:annotation>
|
|
768
|
<xsd:documentation xml:lang="en">
|
|
769
|
Zone of geographical map projection. For example, the original UTM zone reported by the author.
|
|
770
|
</xsd:documentation>
|
|
771
|
<xsd:documentation xml:lang="de">
|
|
772
|
Bezeichnung der Projektionszone
|
|
773
|
</xsd:documentation>
|
|
774
|
</xsd:annotation>
|
|
775
|
</xsd:element>
|
|
776
|
<xsd:element name="authorEastCoordinate" type="xsd:string" minOccurs="0">
|
|
777
|
<xsd:annotation>
|
|
778
|
<xsd:documentation xml:lang="en">
|
|
779
|
East coordinate of author map projection.
|
|
780
|
</xsd:documentation>
|
|
781
|
<xsd:documentation xml:lang="de">
|
|
782
|
Ostkoordinate innerhalb der Zone (Rechtswert)
|
|
783
|
</xsd:documentation>
|
|
784
|
</xsd:annotation>
|
|
785
|
</xsd:element>
|
|
786
|
<xsd:element name="authorNorthCoordinate" type="xsd:string" minOccurs="0">
|
|
787
|
<xsd:annotation>
|
|
788
|
<xsd:documentation xml:lang="en">
|
|
789
|
North coordinate of author map projection.
|
|
790
|
</xsd:documentation>
|
|
791
|
<xsd:documentation xml:lang="de">
|
|
792
|
Nordkoordinate innerhalb der Zone (Hochwert)
|
|
793
|
</xsd:documentation>
|
|
794
|
</xsd:annotation>
|
|
795
|
</xsd:element>
|
|
796
|
</xsd:sequence>
|
|
797
|
</xsd:complexType>
|
|
798
|
<xsd:complexType name="UserdefinedType">
|
|
799
|
<xsd:annotation>
|
|
800
|
<xsd:documentation xml:lang="en">A structure allowing user defined attributes and values. </xsd:documentation>
|
|
801
|
<xsd:documentation xml:lang="de">
|
|
802
|
|
|
803
|
</xsd:documentation>
|
|
804
|
<xsd:appinfo>
|
|
805
|
<doc:moduleDocs>
|
|
806
|
<doc:moduleName>UserdefinedType</doc:moduleName>
|
|
807
|
<doc:moduleDescription>
|
|
808
|
<section xmlns="">
|
|
809
|
<title>Userdefined - A structure allowing user defined attributes and values.</title>
|
|
810
|
<para>An structure allowing user defined attributes and values</para>
|
|
811
|
</section>
|
|
812
|
</doc:moduleDescription>
|
|
813
|
<doc:recommendedUsage/>
|
|
814
|
<doc:standAlone>no</doc:standAlone>
|
|
815
|
</doc:moduleDocs>
|
|
816
|
</xsd:appinfo>
|
|
817
|
</xsd:annotation>
|
|
818
|
<xsd:sequence>
|
|
819
|
<xsd:element name="userDefinedName" type="xsd:string">
|
|
820
|
<xsd:annotation>
|
|
821
|
<xsd:documentation xml:lang="en">Unique name of the user-defined variable.
|
|
822
|
</xsd:documentation>
|
|
823
|
<xsd:documentation xml:lang="de">
|
|
824
|
Eindeutiger Name der benutzerdefinierten Variable.
|
|
825
|
</xsd:documentation>
|
|
826
|
</xsd:annotation>
|
|
827
|
</xsd:element>
|
|
828
|
<xsd:element name="userDefinedMetadata" type="xsd:string" minOccurs="0">
|
|
829
|
<xsd:annotation>
|
|
830
|
<xsd:documentation xml:lang="en">Metadata about this user-defined variable.
|
|
831
|
</xsd:documentation>
|
|
832
|
<xsd:documentation xml:lang="de">
|
|
833
|
Beliebig langer Beschreibungstext der Variablen.
|
|
834
|
</xsd:documentation>
|
|
835
|
</xsd:annotation>
|
|
836
|
</xsd:element>
|
|
837
|
<xsd:element name="userDefinedCategory" type="DEFCATEGORIE" minOccurs="0">
|
|
838
|
<xsd:annotation>
|
|
839
|
<xsd:documentation xml:lang="en">Category from closed List, also 'Undefiniert' possible.
|
|
840
|
</xsd:documentation>
|
|
841
|
<xsd:documentation xml:lang="de">
|
|
842
|
Kategorie aus einer geschlossenen Liste, auch 'Undefiniert'
|
|
843
|
m?glich.
|
|
844
|
</xsd:documentation>
|
|
845
|
</xsd:annotation>
|
|
846
|
</xsd:element>
|
|
847
|
<xsd:element name="userDefinedType" type="xsd:string">
|
|
848
|
<xsd:annotation>
|
|
849
|
<xsd:documentation xml:lang="en">Datatype in database, important for distinguish categorials or cardinals.
|
|
850
|
</xsd:documentation>
|
|
851
|
<xsd:documentation xml:lang="de">
|
|
852
|
Datentyp in der Datenbank, wichtig f?r die Unterscheidung ob
|
|
853
|
kardinal oder kategorial.
|
|
854
|
</xsd:documentation>
|
|
855
|
</xsd:annotation>
|
|
856
|
</xsd:element>
|
|
857
|
<xsd:element name="userDefinedTableName" type="xsd:string">
|
|
858
|
<xsd:annotation>
|
|
859
|
<xsd:documentation xml:lang="en">Name of the XML-entity, on which the value points.
|
|
860
|
</xsd:documentation>
|
|
861
|
<xsd:documentation xml:lang="de">
|
|
862
|
Name der XML-Entit?t, auf die sich der Wert bezieht. Hier sind nur
|
|
863
|
bestimmte Entit?ten erlaubt.
|
|
864
|
</xsd:documentation>
|
|
865
|
</xsd:annotation>
|
|
866
|
</xsd:element>
|
|
867
|
</xsd:sequence>
|
|
868
|
</xsd:complexType>
|
|
869
|
<xsd:complexType name="relativeSpatialCoordinateType">
|
|
870
|
<xsd:annotation>
|
|
871
|
<xsd:documentation>Two related items (e.g., tree or plot) may have their relative positions described in geometric space using the relative position of related items with respect to a point of origin. Normally this point of origin would be an identified plot. This Type should only be used inconjunction with elements containing an origin point defined in geographic space. </xsd:documentation>
|
|
872
|
</xsd:annotation>
|
|
873
|
<xsd:sequence>
|
|
874
|
<xsd:element name="relativeX" type="xsd:decimal">
|
|
875
|
<xsd:annotation>
|
|
876
|
<xsd:documentation source="VegBank" xml:lang="en">The X-coordinate of the related items position in meters. The user will enter the relative position of related item with respect to the plot origin (in meters) with the x-axis defined by the plot azimuth. </xsd:documentation>
|
|
877
|
</xsd:annotation>
|
|
878
|
</xsd:element>
|
|
879
|
<xsd:element name="relativeY" type="xsd:decimal">
|
|
880
|
<xsd:annotation>
|
|
881
|
<xsd:documentation source="VegBank" xml:lang="en">The Y-coordinate of the related items position in metres. The user will enter the relative position of related item with respect to the plot origin (in meters) with the y-axis defined by the plot azimuth. </xsd:documentation>
|
|
882
|
</xsd:annotation>
|
|
883
|
</xsd:element>
|
|
884
|
<xsd:element name="relativeZ" type="xsd:decimal" minOccurs="0">
|
|
885
|
<xsd:annotation>
|
|
886
|
<xsd:documentation xml:lang="en">The Z-coordinate of the related items position in metres. The user will enter the relative position of related item with respect to the plot origin (in meters) with the z-axis defined by the plot azimuth. </xsd:documentation>
|
|
887
|
</xsd:annotation>
|
|
888
|
</xsd:element>
|
|
889
|
</xsd:sequence>
|
|
890
|
</xsd:complexType>
|
|
891
|
<xsd:complexType name="percentCoverType">
|
|
892
|
<xsd:sequence>
|
|
893
|
<xsd:element name="methodID" type="xsd:string" minOccurs="0">
|
|
894
|
<xsd:annotation>
|
|
895
|
<xsd:documentation>A reference to a specific cover method commonly used to assess cover. The individual cover method is defined within the element veg:method which is a container for all methods within the dataset. </xsd:documentation>
|
|
896
|
</xsd:annotation>
|
|
897
|
</xsd:element>
|
|
898
|
<xsd:element name="cover" maxOccurs="unbounded">
|
|
899
|
<xsd:complexType>
|
|
900
|
<xsd:sequence>
|
|
901
|
<xsd:element name="coverTypeAttributeID" type="xsd:string">
|
|
902
|
<xsd:annotation>
|
|
903
|
<xsd:documentation>Type of cover, e.g. water, litter, tree, shrub etc. Recorded using Attribute type. AttributeID links to a specific categorical value stored either in the ordinal or qualitative elements of the Attributes parent element group. The individual attribute is defined within the element veg:attributes which is a container for all attributes within the dataset. </xsd:documentation>
|
|
904
|
</xsd:annotation>
|
|
905
|
</xsd:element>
|
|
906
|
<xsd:element name="coverPercent" type="MeasurementType">
|
|
907
|
<xsd:annotation>
|
|
908
|
<xsd:documentation>Estimated percent cover.</xsd:documentation>
|
|
909
|
</xsd:annotation>
|
|
910
|
</xsd:element>
|
|
911
|
</xsd:sequence>
|
|
912
|
</xsd:complexType>
|
|
913
|
</xsd:element>
|
|
914
|
</xsd:sequence>
|
|
915
|
</xsd:complexType>
|
|
916
|
<xsd:complexType name="vegetationStructureType">
|
|
917
|
<xsd:sequence>
|
|
918
|
<xsd:element name="methodID" type="xsd:string" minOccurs="0">
|
|
919
|
<xsd:annotation>
|
|
920
|
<xsd:documentation>A reference to a specific vegetation component height measurement method commonly use to measure all heights. The individual height measurement method is defined within the element veg:method which is a container for all methods within the dataset. </xsd:documentation>
|
|
921
|
</xsd:annotation>
|
|
922
|
</xsd:element>
|
|
923
|
<xsd:element name="structure" maxOccurs="unbounded">
|
|
924
|
<xsd:complexType>
|
|
925
|
<xsd:sequence>
|
|
926
|
<xsd:element name="vegetationComponentAttributeID" type="xsd:string">
|
|
927
|
<xsd:annotation>
|
|
928
|
<xsd:documentation>Vegetation component type/name, e.g. tree, shrub, field layer (Herb stratum), non-vascular layer, floating and submerged cover (wetlands) etc. Recorded using Attribute type. AttributeID links to a specific categorical value stored either in the ordinal or qualitative elements of the Attributes parent element group. The individual attribute is defined within the element veg:attributes which is a container for all attributes within the dataset. </xsd:documentation>
|
|
929
|
</xsd:annotation>
|
|
930
|
</xsd:element>
|
|
931
|
<xsd:element name="height" type="MeasurementType">
|
|
932
|
<xsd:annotation>
|
|
933
|
<xsd:documentation>Height of the vegetation component layer, e.g. tree, shrub etc. Usually recorded in meters. </xsd:documentation>
|
|
934
|
</xsd:annotation>
|
|
935
|
</xsd:element>
|
|
936
|
</xsd:sequence>
|
|
937
|
</xsd:complexType>
|
|
938
|
</xsd:element>
|
|
939
|
</xsd:sequence>
|
|
940
|
</xsd:complexType>
|
|
941
|
</xsd:schema>
|
