|
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:proj="eml://ecoinformatics.org/project-2.0.1" xmlns:lit="eml://ecoinformatics.org/literature-2.0.1" xmlns:res="eml://ecoinformatics.org/resource-2.0.1" xmlns:party="eml://ecoinformatics.org/party-2.0.1" xmlns:tcs="http://www.tdwg.org/schemas/tcs/1.01" xmlns:plot="http://www.bfn.de/plot-1.0.1" xmlns:obs="http://www.bfn.de/plotobservation-1.0.1" xmlns:misc="http://www.bfn.de/misc-1.0.1" xmlns:org="http://www.bfn.de/organismobservation-1.0.1" xmlns:dwg="http://rs.tdwg.org/dwc/geospatial/">
|
|
4
|
<xsd:annotation>
|
|
5
|
<xsd:documentation xml:lang="en">
|
|
6
|
W3C-Schema Proposal 1.4 for an International Exchange Standard for Vegetation Data.
|
|
7
|
Author: Dr. Martin Kleikamp et al.
|
|
8
|
</xsd:documentation>
|
|
9
|
</xsd:annotation>
|
|
10
|
<xsd:import namespace="eml://ecoinformatics.org/project-2.0.1" schemaLocation="eml-project.xsd"/>
|
|
11
|
<xsd:import namespace="eml://ecoinformatics.org/literature-2.0.1" schemaLocation="eml-literature.xsd"/>
|
|
12
|
<xsd:import namespace="eml://ecoinformatics.org/party-2.0.1" schemaLocation="eml-party.xsd"/>
|
|
13
|
<xsd:import namespace="eml://ecoinformatics.org/resource-2.0.1" schemaLocation="eml-resource.xsd"/>
|
|
14
|
<xsd:import namespace="http://www.tdwg.org/schemas/tcs/1.01" schemaLocation="tcsv101.xsd"/>
|
|
15
|
<xsd:import namespace="http://www.bfn.de/plot-1.0.1" schemaLocation="veg-plot.xsd"/>
|
|
16
|
<xsd:import namespace="http://www.bfn.de/plotobservation-1.0.1" schemaLocation="veg-plotobservation.xsd"/>
|
|
17
|
<xsd:import namespace="http://www.bfn.de/organismobservation-1.0.1" schemaLocation="veg-organismobservation.xsd"/>
|
|
18
|
<xsd:import namespace="http://www.bfn.de/misc-1.0.1" schemaLocation="veg-misc.xsd"/>
|
|
19
|
<xsd:import namespace="http://rs.tdwg.org/dwc/geospatial/" schemaLocation="tdwg_dw_geospatial.xsd"/>
|
|
20
|
<xsd:include schemaLocation="veg-userdefined.xsd"/>
|
|
21
|
<xsd:element name="vegX">
|
|
22
|
<xsd:complexType>
|
|
23
|
<xsd:sequence>
|
|
24
|
<xsd:element name="literature" minOccurs="0">
|
|
25
|
<xsd:annotation>
|
|
26
|
<xsd:documentation>A container for the eml-literature module. The eml-literature module contains information that describes literature resources.</xsd:documentation>
|
|
27
|
</xsd:annotation>
|
|
28
|
<xsd:complexType>
|
|
29
|
<xsd:sequence>
|
|
30
|
<xsd:element name="literatureCitation" type="lit:CitationType" maxOccurs="unbounded">
|
|
31
|
<xsd:annotation>
|
|
32
|
<xsd:documentation source="eml" xml:lang="en">Provides overview information about the literature citation, including title, abstract, keywords, and contacts.</xsd:documentation>
|
|
33
|
</xsd:annotation>
|
|
34
|
</xsd:element>
|
|
35
|
</xsd:sequence>
|
|
36
|
</xsd:complexType>
|
|
37
|
</xsd:element>
|
|
38
|
<xsd:element name="parties" minOccurs="0">
|
|
39
|
<xsd:annotation>
|
|
40
|
<xsd:documentation>A container for eml-party types. The eml-party module describes a responsible party (person or organization). </xsd:documentation>
|
|
41
|
</xsd:annotation>
|
|
42
|
<xsd:complexType>
|
|
43
|
<xsd:sequence>
|
|
44
|
<xsd:element name="party" type="party:ResponsibleParty" maxOccurs="unbounded">
|
|
45
|
<xsd:annotation>
|
|
46
|
<xsd:documentation source="EML" xml:lang="en">The eml-party module describes a responsible party (person or organization), and is typically used to name the originator of a resource or metadata document. </xsd:documentation>
|
|
47
|
<xsd:appinfo source="EML">It contains detailed contact information for the party, be it an individual person, an organization, or a named position within an organization. The eml-party module is used throughout the other EML modules where detailed contact information is needed.</xsd:appinfo>
|
|
48
|
</xsd:annotation>
|
|
49
|
</xsd:element>
|
|
50
|
</xsd:sequence>
|
|
51
|
</xsd:complexType>
|
|
52
|
</xsd:element>
|
|
53
|
<xsd:element name="projects" minOccurs="0">
|
|
54
|
<xsd:annotation>
|
|
55
|
<xsd:documentation>A container for eml-projects. The eml-project module describes the research context in which the dataset was created. </xsd:documentation>
|
|
56
|
</xsd:annotation>
|
|
57
|
<xsd:complexType>
|
|
58
|
<xsd:sequence>
|
|
59
|
<xsd:element name="project" type="proj:ResearchProjectType" maxOccurs="unbounded">
|
|
60
|
<xsd:annotation>
|
|
61
|
<xsd:documentation source="EML" xml:lang="en">The eml-project module describes the research context in which the dataset was created, including descriptions of over-all motivations and goals, funding, personnel, description of the study area etc. Each project should have an identifier that is unique across the dataset, and preferably globally unique. </xsd:documentation>
|
|
62
|
<xsd:appinfo source="EML">This is also the module to describe the design of the project: the scientific questions being asked, the architecture of the design, etc. This module is used to place the dataset that is being documented into its larger research context.
|
|
63
|
|
|
64
|
</xsd:appinfo>
|
|
65
|
<xsd:appinfo>A GUID (globally unique identifier) would be ideal for specifying the unique identifier for the project, such as LSID (Life Science Identifier). See http://www.tdwg.org/activities/online-services/lsid-authority-ids/. </xsd:appinfo>
|
|
66
|
</xsd:annotation>
|
|
67
|
</xsd:element>
|
|
68
|
</xsd:sequence>
|
|
69
|
</xsd:complexType>
|
|
70
|
</xsd:element>
|
|
71
|
<xsd:element name="plots" minOccurs="0">
|
|
72
|
<xsd:annotation>
|
|
73
|
<xsd:documentation>A container for a sampling locations (plots). </xsd:documentation>
|
|
74
|
</xsd:annotation>
|
|
75
|
<xsd:complexType>
|
|
76
|
<xsd:sequence>
|
|
77
|
<xsd:element name="plot" type="plot:PlotType" maxOccurs="unbounded">
|
|
78
|
<xsd:annotation>
|
|
79
|
<xsd:documentation xml:lang="en">Sampling locations represented as one or more points, lines, polygons, or volumes, and is the basis for experimentation or measurement. Its properties are assumed to be constant over time. </xsd:documentation>
|
|
80
|
<xsd:appinfo>A point within the plot may be used as center for relative coordinates, which are required to be Cartesian. Plots may have no explicit bounds, and may refer to an area of inference. A plot may be related to other plots in order to express parent-child, contiguity, or other type of links. </xsd:appinfo>
|
|
81
|
</xsd:annotation>
|
|
82
|
</xsd:element>
|
|
83
|
</xsd:sequence>
|
|
84
|
</xsd:complexType>
|
|
85
|
</xsd:element>
|
|
86
|
<xsd:element name="plotObservations" minOccurs="0">
|
|
87
|
<xsd:annotation>
|
|
88
|
<xsd:documentation>A container for a specific type of ObservationGrouping that groups observations taken on a single Plot and during a single date-time period. </xsd:documentation>
|
|
89
|
</xsd:annotation>
|
|
90
|
<xsd:complexType>
|
|
91
|
<xsd:sequence>
|
|
92
|
<xsd:element name="plotObservation" type="obs:ObservationType" maxOccurs="unbounded">
|
|
93
|
<xsd:annotation>
|
|
94
|
<xsd:documentation xml:lang="en">A specific ObservationGrouping that groups observations taken on a single Plot and during a single date-time period. </xsd:documentation>
|
|
95
|
<xsd:appinfo>A Relevé or an Inventory are examples of PlotObservation. A PlotObservation may be conducted by one or more observers, and may be related to one or more Projects.</xsd:appinfo>
|
|
96
|
</xsd:annotation>
|
|
97
|
</xsd:element>
|
|
98
|
</xsd:sequence>
|
|
99
|
</xsd:complexType>
|
|
100
|
</xsd:element>
|
|
101
|
<xsd:element name="taxonNames" minOccurs="0">
|
|
102
|
<xsd:annotation>
|
|
103
|
<xsd:documentation>A container for all nomenclatural units defined for use by a dataset. This is a formal taxonomic name published under codes. Used when applying usage-published name assertions.</xsd:documentation>
|
|
104
|
</xsd:annotation>
|
|
105
|
<xsd:complexType>
|
|
106
|
<xsd:sequence>
|
|
107
|
<xsd:element name="taxonName" type="tcs:ScientificName" maxOccurs="unbounded">
|
|
108
|
<xsd:annotation>
|
|
109
|
<xsd:documentation>A published nomenclatural unit of any rank (order, family, genus, species, subspecies, etc.). This is a formal taxonomic name published under codes. Each name is of type tcs:scientificName and may be referenced in taxonDetermination allowing a name usage concept (author name) to be determined or asserted as a specific published nomenclatural name. tcs:scientificName:citation is contained in the literature container. Note this is not the same as a taxonomic name, i.e. these are not taxa, which are defined by a taxonConcept.</xsd:documentation>
|
|
110
|
<xsd:appinfo source="tcsv101">An object that represents a single scientific biological name that either is, or appears to be, governed by one of the biological codes of nomenclature. These are not taxa. Taxa, whether accepted or not, are represented by TaxonConcept objects. Vernacular names are also dealt with under taxon concepts. </xsd:appinfo>
|
|
111
|
</xsd:annotation>
|
|
112
|
</xsd:element>
|
|
113
|
</xsd:sequence>
|
|
114
|
</xsd:complexType>
|
|
115
|
</xsd:element>
|
|
116
|
<xsd:element name="taxonConcepts" minOccurs="0">
|
|
117
|
<xsd:annotation>
|
|
118
|
<xsd:documentation>A container for all taxon concepts defined for use by a dataset when applying name usage-taxonomic name assertions. Recommend to be used for published concepts.</xsd:documentation>
|
|
119
|
</xsd:annotation>
|
|
120
|
<xsd:complexType>
|
|
121
|
<xsd:sequence>
|
|
122
|
<xsd:element name="taxonConcept" type="tcs:TaxonConceptType" maxOccurs="unbounded">
|
|
123
|
<xsd:annotation>
|
|
124
|
<xsd:documentation>Representation of a Taxon Concept. Various types of concept can be represented, including a reference to the GUID of an existing Concept. Each taxon concept follows tcs:taxonConcept and may be referenced in taxonDetermination allowing a name usage concept (author name) to be determined or asserted as a specific published taxonomic name/concept. It is recommended that the relationships between concepts be a child pointing to its parent.</xsd:documentation>
|
|
125
|
</xsd:annotation>
|
|
126
|
</xsd:element>
|
|
127
|
</xsd:sequence>
|
|
128
|
</xsd:complexType>
|
|
129
|
</xsd:element>
|
|
130
|
<xsd:element name="taxonNameUsageConcepts" minOccurs="0">
|
|
131
|
<xsd:annotation>
|
|
132
|
<xsd:documentation>A container for taxon name strings occurring within the dataset. These are usage concepts defined by the dataset author which may follow, or be according, to a third party. They may be further related to a published name (taxon name, tcs:TaxonName) and or taxonomic name (taxon concept, tcs:TaxonConcept) in taxonDetermination.</xsd:documentation>
|
|
133
|
</xsd:annotation>
|
|
134
|
<xsd:complexType>
|
|
135
|
<xsd:sequence>
|
|
136
|
<xsd:element name="taxonNameUsageConcept" type="org:TaxonNameUsageType" maxOccurs="unbounded">
|
|
137
|
<xsd:annotation>
|
|
138
|
<xsd:documentation>A taxon name string occurring within the dataset. This is a usage concept defined by the dataset author which may follow, or be according to, an additional third party. It may be further related to a published name (taxon name, tcs:TaxonName) and or taxonomic name (taxon concept, tcs:TaxonConcept) in taxonDetermination.</xsd:documentation>
|
|
139
|
</xsd:annotation>
|
|
140
|
</xsd:element>
|
|
141
|
</xsd:sequence>
|
|
142
|
</xsd:complexType>
|
|
143
|
</xsd:element>
|
|
144
|
<xsd:element name="taxonDeterminations" minOccurs="0">
|
|
145
|
<xsd:annotation>
|
|
146
|
<xsd:documentation>A container for relationships or assertions between two concepts. Within vegX this typically allows for an author usage concept (datasetNameUsageConcept), i.e. a name string used by the author in this dataset, to be linked to either a published nomenclatural name (taxon name) or a specific taxa treatment (taxon concept), according to a third party. </xsd:documentation>
|
|
147
|
</xsd:annotation>
|
|
148
|
<xsd:complexType>
|
|
149
|
<xsd:sequence>
|
|
150
|
<xsd:element name="taxonDetermination" type="org:TaxonDeterminationType" maxOccurs="unbounded">
|
|
151
|
<xsd:annotation>
|
|
152
|
<xsd:documentation xml:lang="en">A specific relationship or assertion between two name concepts which are not part of the original definition of either of these concepts; possibly by a third party. Within vegX this typically allows for an author usage concept, i.e. a name string used by the author in this dataset, to be linked to either a published nomenclatural name (taxon name) or a specific taxa treatment (taxon concept), according to a third party. Similar to a tcs TaxonRelationshipAssertion. An identification applying one or more TaxonConcepts or taxon names to an IndividualOrganismObservation or AggregateTaxonObservation by a Party. </xsd:documentation>
|
|
153
|
</xsd:annotation>
|
|
154
|
</xsd:element>
|
|
155
|
</xsd:sequence>
|
|
156
|
</xsd:complexType>
|
|
157
|
</xsd:element>
|
|
158
|
<xsd:element name="communityDeterminations" minOccurs="0">
|
|
159
|
<xsd:annotation>
|
|
160
|
<xsd:documentation>A container for identifications that apply one or more CommunityConcepts to a PlotObservation by a Party.</xsd:documentation>
|
|
161
|
</xsd:annotation>
|
|
162
|
<xsd:complexType>
|
|
163
|
<xsd:sequence>
|
|
164
|
<xsd:element name="communityDetermination" type="org:CommunityDeterminationType" maxOccurs="unbounded">
|
|
165
|
<xsd:annotation>
|
|
166
|
<xsd:documentation xml:lang="en">An identification applying one or more CommunityConcepts to a PlotObservation by a Party. </xsd:documentation>
|
|
167
|
</xsd:annotation>
|
|
168
|
</xsd:element>
|
|
169
|
</xsd:sequence>
|
|
170
|
</xsd:complexType>
|
|
171
|
</xsd:element>
|
|
172
|
<xsd:element name="aggregateOrganismObservations" minOccurs="0">
|
|
173
|
<xsd:annotation>
|
|
174
|
<xsd:documentation>A container for all observation applying to all occurrences of an organism based on an aggregation factor.</xsd:documentation>
|
|
175
|
</xsd:annotation>
|
|
176
|
<xsd:complexType>
|
|
177
|
<xsd:sequence>
|
|
178
|
<xsd:element name="aggregateOrganismObservation" type="org:AggregateOrganismObservationType" maxOccurs="unbounded">
|
|
179
|
<xsd:annotation>
|
|
180
|
<xsd:documentation xml:lang="en">An observation applying to all occurrences of an organism based on an aggregation factor. It contains an AggregateValue, which is an assessment of the overall occurrence of an organism in a Plot (e.g. number of stems, percentage cover, total biomass, basal area). </xsd:documentation>
|
|
181
|
<xsd:appinfo>An AggregateOrganismObservation contains a link to a taxonOccurrence, where all the taxon identification information is contained. It also contains a reference to a single PlotObservation. Most of the remaining contextual information concerning the observation (like date-time period, observer, methods, protocol, projects _) is specified in the related PlotObservation. Optionally, the AggregateOrganismObservation may link to a StratumObservation. Additional grouping criteria may be specified through the reference to one or more ObservationGroupings. Finally, it may also have simple and/or complex user-defined elements.</xsd:appinfo>
|
|
182
|
</xsd:annotation>
|
|
183
|
</xsd:element>
|
|
184
|
</xsd:sequence>
|
|
185
|
</xsd:complexType>
|
|
186
|
</xsd:element>
|
|
187
|
<xsd:element name="strata" minOccurs="0">
|
|
188
|
<xsd:annotation>
|
|
189
|
<xsd:documentation>A container for the list of allowable stratum, following a specific definition method. Strata is a special case of a general categorical lookup list (normally recorded in the container element VegX:Attribute). Strata was separated into its own element in recognition of the large majority of end-users who primarily deal with releve type data.</xsd:documentation>
|
|
190
|
</xsd:annotation>
|
|
191
|
<xsd:complexType>
|
|
192
|
<xsd:sequence>
|
|
193
|
<xsd:element name="stratum" type="org:StratumType" maxOccurs="unbounded">
|
|
194
|
<xsd:annotation>
|
|
195
|
<xsd:documentation xml:lang="en">The specific definition of a stratum referred to by observations in the dataset. A stratum usually belongs to a ordered list that together are the set of allowable strata use in a specific dataset. It contains the stratum name (e.g. tree layer) as well as an identification code. It may also contain an indication of a position in an ordered sequence of strata. </xsd:documentation>
|
|
196
|
</xsd:annotation>
|
|
197
|
</xsd:element>
|
|
198
|
<xsd:element name="methodID" type="xsd:string" minOccurs="0">
|
|
199
|
<xsd:annotation>
|
|
200
|
<xsd:documentation xml:lang="en">A reference to a specific method applied in comon to all the strata described for a dataset. The individual method is defined within the element veg:methods 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:element>
|
|
206
|
<xsd:element name="stratumObservations" minOccurs="0">
|
|
207
|
<xsd:annotation>
|
|
208
|
<xsd:documentation>A container for observations applying to a stratum in a single plot during a single date-time period.</xsd:documentation>
|
|
209
|
</xsd:annotation>
|
|
210
|
<xsd:complexType>
|
|
211
|
<xsd:sequence>
|
|
212
|
<xsd:element name="stratumObservation" type="org:StratumObservationType" maxOccurs="unbounded">
|
|
213
|
<xsd:annotation>
|
|
214
|
<xsd:documentation xml:lang="en">A specific observation applying to a stratum in a single plot during a single date-time period. Each stratum measurement may be referenced by observations of taxa within a plot. For example, abundance estimates of a taxa on a plot within a specific stratum. </xsd:documentation>
|
|
215
|
<xsd:appinfo>Typically, it contains the lower and upper vertical bounds of the stratum and an assessment of cover. A StratumObservation always contains a reference to a PlotObservation, where contextual information lies (plot, project, parties, date-time period). It also contains a reference to a Stratum, which contains its definition.</xsd:appinfo>
|
|
216
|
</xsd:annotation>
|
|
217
|
</xsd:element>
|
|
218
|
</xsd:sequence>
|
|
219
|
</xsd:complexType>
|
|
220
|
</xsd:element>
|
|
221
|
<xsd:element name="individualOrganismObservations" minOccurs="0">
|
|
222
|
<xsd:annotation>
|
|
223
|
<xsd:documentation>A container for measurements/observations applying to one occurrence of an organism.</xsd:documentation>
|
|
224
|
</xsd:annotation>
|
|
225
|
<xsd:complexType>
|
|
226
|
<xsd:sequence>
|
|
227
|
<xsd:element name="individualOrganismObservation" type="org:IndividualOrganismObservationType" maxOccurs="unbounded">
|
|
228
|
<xsd:annotation>
|
|
229
|
<xsd:documentation xml:lang="en">An observation applying to one occurrence of an organism (or part of an organism). It is a container for measurements made on the organism (e.g. diameter, height, crown dimensions, biomass, growth form, number of stems). </xsd:documentation>
|
|
230
|
<xsd:appinfo>An IndividualOrganismObservation contains a reference to a taxonOccurrence, where all the taxon identification information is contained. It also contains a reference to a unique PlotObservation, and may include a relative location within the coordinate system of the Plot. Most of the remaining contextual information concerning the observation (like date-time period, observer, methods, protocol, projects _) is specified in the related PlotObservation. Optionally, the IndividualOrganismObservation may link to a StratumObservation. Additional grouping criteria may be specified through the reference to one or more ObservationGroupings. The IndividualOrganismObservation may contain an element to identify the organism itself. It may also specify a RelatedItem (e.g. A was found on top of B). The measured value can be a simple measurement or a multiple (tuple) measurement.</xsd:appinfo>
|
|
231
|
</xsd:annotation>
|
|
232
|
</xsd:element>
|
|
233
|
</xsd:sequence>
|
|
234
|
</xsd:complexType>
|
|
235
|
</xsd:element>
|
|
236
|
<xsd:element name="individualOrganisms" minOccurs="0">
|
|
237
|
<xsd:annotation>
|
|
238
|
<xsd:documentation>A container for all identified organisms recorded within the dataset.</xsd:documentation>
|
|
239
|
</xsd:annotation>
|
|
240
|
<xsd:complexType>
|
|
241
|
<xsd:sequence>
|
|
242
|
<xsd:element name="individualOrganism" type="org:IndividualOrganismType" maxOccurs="unbounded">
|
|
243
|
<xsd:annotation>
|
|
244
|
<xsd:documentation xml:lang="en">An identified organism recorded during 1 or more individual organism observation events. Individuals may have an identification label (e.g. tree tag number).</xsd:documentation>
|
|
245
|
</xsd:annotation>
|
|
246
|
</xsd:element>
|
|
247
|
</xsd:sequence>
|
|
248
|
</xsd:complexType>
|
|
249
|
</xsd:element>
|
|
250
|
<xsd:element name="abioticObservations" minOccurs="0">
|
|
251
|
<xsd:annotation>
|
|
252
|
<xsd:documentation>A container for all the abiotic measurements made on a single Plot during a single date-time period.</xsd:documentation>
|
|
253
|
</xsd:annotation>
|
|
254
|
<xsd:complexType>
|
|
255
|
<xsd:sequence>
|
|
256
|
<xsd:element name="abioticObservation" type="obs:AbioticObservationType" maxOccurs="unbounded">
|
|
257
|
<xsd:annotation>
|
|
258
|
<xsd:documentation xml:lang="en">A specific abiotic measurement/observation made on a plot. It always contains a reference to a single PlotObservation, where most of the contextual information concerning the observation (like date-time period, observer, methods, protocol, projects) is specified.</xsd:documentation>
|
|
259
|
</xsd:annotation>
|
|
260
|
</xsd:element>
|
|
261
|
</xsd:sequence>
|
|
262
|
</xsd:complexType>
|
|
263
|
</xsd:element>
|
|
264
|
<xsd:element name="observationGroupings" minOccurs="0">
|
|
265
|
<xsd:annotation>
|
|
266
|
<xsd:documentation>A container for a set of observation records, of any kind, that are grouped.</xsd:documentation>
|
|
267
|
</xsd:annotation>
|
|
268
|
<xsd:complexType>
|
|
269
|
<xsd:sequence>
|
|
270
|
<xsd:element name="observationGrouping" type="misc:ObservationGroupingType" maxOccurs="unbounded">
|
|
271
|
<xsd:annotation>
|
|
272
|
<xsd:documentation xml:lang="en">An specific grouping of observation records, of any kind, that are grouped in the data management system owing to some common characteristic. </xsd:documentation>
|
|
273
|
<xsd:appinfo>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).</xsd:appinfo>
|
|
274
|
</xsd:annotation>
|
|
275
|
</xsd:element>
|
|
276
|
</xsd:sequence>
|
|
277
|
</xsd:complexType>
|
|
278
|
</xsd:element>
|
|
279
|
<xsd:element name="attributes" minOccurs="0">
|
|
280
|
<xsd:annotation>
|
|
281
|
<xsd:documentation>A container for the definitions of measured properties.</xsd:documentation>
|
|
282
|
</xsd:annotation>
|
|
283
|
<xsd:complexType>
|
|
284
|
<xsd:sequence>
|
|
285
|
<xsd:element name="attribute" type="misc:AttributeType" maxOccurs="unbounded">
|
|
286
|
<xsd:annotation>
|
|
287
|
<xsd:documentation xml:lang="en">A specific definition of a measured property. An attribute has to be one of three types: qualitative (unordered categorical variable, i.e. nominal), ordinal (ordered list of values) or quantitative (a numerical variable, either discrete or continuous</xsd:documentation>
|
|
288
|
</xsd:annotation>
|
|
289
|
</xsd:element>
|
|
290
|
</xsd:sequence>
|
|
291
|
</xsd:complexType>
|
|
292
|
</xsd:element>
|
|
293
|
<xsd:element name="methods" minOccurs="0">
|
|
294
|
<xsd:annotation>
|
|
295
|
<xsd:documentation>A container for the methods followed in the creation of the datasets.</xsd:documentation>
|
|
296
|
</xsd:annotation>
|
|
297
|
<xsd:complexType>
|
|
298
|
<xsd:sequence>
|
|
299
|
<xsd:element name="method" type="misc:MethodType" maxOccurs="unbounded">
|
|
300
|
<xsd:annotation>
|
|
301
|
<xsd:documentation xml:lang="en">A specific method definition followed in the creation of the dataset. Each method links to a protocol and literature citation reference. A protocol may have many method or steps.</xsd:documentation>
|
|
302
|
</xsd:annotation>
|
|
303
|
</xsd:element>
|
|
304
|
</xsd:sequence>
|
|
305
|
</xsd:complexType>
|
|
306
|
</xsd:element>
|
|
307
|
<xsd:element name="protocols" minOccurs="0">
|
|
308
|
<xsd:annotation>
|
|
309
|
<xsd:documentation>A container for groups of methods related by common action.</xsd:documentation>
|
|
310
|
</xsd:annotation>
|
|
311
|
<xsd:complexType>
|
|
312
|
<xsd:sequence>
|
|
313
|
<xsd:element name="protocol" type="misc:ProtocolType" maxOccurs="unbounded">
|
|
314
|
<xsd:annotation>
|
|
315
|
<xsd:documentation xml:lang="en">A specific grouping of methods related by common action.</xsd:documentation>
|
|
316
|
</xsd:annotation>
|
|
317
|
</xsd:element>
|
|
318
|
</xsd:sequence>
|
|
319
|
</xsd:complexType>
|
|
320
|
</xsd:element>
|
|
321
|
<xsd:element name="userdefinedTypes" minOccurs="0">
|
|
322
|
<xsd:annotation>
|
|
323
|
<xsd:documentation>A container for user-defined types not accommodated by the schema.</xsd:documentation>
|
|
324
|
</xsd:annotation>
|
|
325
|
<xsd:complexType>
|
|
326
|
<xsd:sequence>
|
|
327
|
<xsd:element name="userdefined" type="misc:UserdefinedType" maxOccurs="unbounded">
|
|
328
|
<xsd:annotation>
|
|
329
|
<xsd:documentation>Generic element to allow for root-level user-defined information types not accommodated by the schema. </xsd:documentation>
|
|
330
|
</xsd:annotation>
|
|
331
|
</xsd:element>
|
|
332
|
</xsd:sequence>
|
|
333
|
</xsd:complexType>
|
|
334
|
</xsd:element>
|
|
335
|
</xsd:sequence>
|
|
336
|
<xsd:attribute name="id" type="res:IDType" use="optional">
|
|
337
|
<xsd:annotation>
|
|
338
|
<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., plots) or a GUID in which case it can be resolved to a location on the internet where the record is stored. This identifier is used elsewhere in a dataset instance to reference this specific element when it is referred to in a repeatable way by other part of the schema. For example, a single plot entity may be the basis for numerous measurements of different types (e.g., plot observation and aggregated organism observation). Therefore the plot entity is stored in a single location within schema and referenced by this identifier rather than repeating this information throughout the dataset instance. The identifier may have a specific system and scope.</xsd:documentation>
|
|
339
|
</xsd:annotation>
|
|
340
|
</xsd:attribute>
|
|
341
|
<xsd:attribute name="system" type="res:SystemType" use="optional"/>
|
|
342
|
<xsd:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
|
|
343
|
</xsd:complexType>
|
|
344
|
</xsd:element>
|
|
345
|
</xsd:schema>
|
