|
1
|
<?xml version="1.0"?>
|
|
2
|
<xs:schema targetNamespace="eml:attribute-2.0.0beta8" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:doc="eml:documentation-2.0.0beta8" xmlns:lit="eml:literature-2.0.0beta8" xmlns:cov="eml:coverage-2.0.0beta8" xmlns:rp="eml:party-2.0.0beta8" xmlns="eml:attribute-2.0.0beta8">
|
|
3
|
<xs:import namespace="eml:documentation-2.0.0beta8" schemaLocation="eml-documentation.xsd"/>
|
|
4
|
<xs:import namespace="eml:literature-2.0.0beta8" schemaLocation="eml-literature.xsd"/>
|
|
5
|
<xs:import namespace="eml:coverage-2.0.0beta8" schemaLocation="eml-coverage.xsd"/>
|
|
6
|
<xs:import namespace="eml:party-2.0.0beta8" schemaLocation="eml-party.xsd"/>
|
|
7
|
<xs:annotation>
|
|
8
|
<xs:documentation>
|
|
9
|
'$RCSfile: eml-attribute.xsd,v $'
|
|
10
|
Copyright: 1997-2002 Regents of the University of California,
|
|
11
|
University of New Mexico, and
|
|
12
|
Arizona State University
|
|
13
|
Sponsors: National Center for Ecological Analysis and Synthesis and
|
|
14
|
Partnership for Interdisciplinary Studies of Coastal Oceans,
|
|
15
|
University of California Santa Barbara
|
|
16
|
Long-Term Ecological Research Network Office,
|
|
17
|
University of New Mexico
|
|
18
|
Center for Environmental Studies, Arizona State University
|
|
19
|
Other funding: National Science Foundation (see README for details)
|
|
20
|
The David and Lucile Packard Foundation
|
|
21
|
For Details: http://knb.ecoinformatics.org/
|
|
22
|
|
|
23
|
'$Author: berkley $'
|
|
24
|
'$Date: 2002/05/28 21:45:28 $'
|
|
25
|
'$Revision: 1.32 $'
|
|
26
|
|
|
27
|
This program is free software; you can redistribute it and/or modify
|
|
28
|
it under the terms of the GNU General Public License as published by
|
|
29
|
the Free Software Foundation; either version 2 of the License, or
|
|
30
|
(at your option) any later version.
|
|
31
|
|
|
32
|
This program is distributed in the hope that it will be useful,
|
|
33
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
34
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
35
|
GNU General Public License for more details.
|
|
36
|
|
|
37
|
You should have received a copy of the GNU General Public License
|
|
38
|
along with this program; if not, write to the Free Software
|
|
39
|
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA </xs:documentation>
|
|
40
|
<xs:appinfo>
|
|
41
|
<doc:moduleDocs>
|
|
42
|
<doc:moduleName>eml-attribute</doc:moduleName>
|
|
43
|
<doc:moduleDescription>
|
|
44
|
The EML Attribute Module describes all attributes (variables) in
|
|
45
|
a data entity (e.g., data table). The description includes the name
|
|
46
|
and definition of each attribute, its type, its allowable range
|
|
47
|
(if numeric), definitions of coded values, and other pertinent
|
|
48
|
information.
|
|
49
|
</doc:moduleDescription>
|
|
50
|
<doc:recommendedUsage>
|
|
51
|
all datasets that use tableEntities
|
|
52
|
</doc:recommendedUsage>
|
|
53
|
<doc:standAlone>
|
|
54
|
yes
|
|
55
|
</doc:standAlone>
|
|
56
|
<doc:relationship>
|
|
57
|
<doc:moduleName>
|
|
58
|
eml-tableEntity
|
|
59
|
</doc:moduleName>
|
|
60
|
<doc:relationshipType>
|
|
61
|
has attribute information for
|
|
62
|
</doc:relationshipType>
|
|
63
|
</doc:relationship>
|
|
64
|
</doc:moduleDocs>
|
|
65
|
</xs:appinfo>
|
|
66
|
</xs:annotation>
|
|
67
|
<xs:complexType name="AttributeListDefinitionType">
|
|
68
|
<xs:annotation>
|
|
69
|
<xs:appinfo>
|
|
70
|
<doc:tooltip>
|
|
71
|
AttributeType complex type
|
|
72
|
</doc:tooltip>
|
|
73
|
<doc:summary>
|
|
74
|
container for attributes, attributeLists or references
|
|
75
|
</doc:summary>
|
|
76
|
<doc:description>
|
|
77
|
This complexType is a choice between attribute, attributeList
|
|
78
|
and references. attribute is used to define a single attribute,
|
|
79
|
attributeList is used to define a discreet list of attributes
|
|
80
|
that go together in some logical way and references links
|
|
81
|
other metadat into this module.
|
|
82
|
</doc:description>
|
|
83
|
<doc:example/>
|
|
84
|
<doc:lineage>
|
|
85
|
The eml-attribute was introduced into EML 1.4 as eml-variable.
|
|
86
|
</doc:lineage>
|
|
87
|
</xs:appinfo>
|
|
88
|
</xs:annotation>
|
|
89
|
<xs:sequence>
|
|
90
|
<xs:element name="attribute" type="AttributeType" maxOccurs="unbounded"/>
|
|
91
|
</xs:sequence>
|
|
92
|
<xs:attribute name="id" type="xs:ID" use="required"/>
|
|
93
|
<xs:attribute name="system" type="xs:string" use="required"/>
|
|
94
|
<xs:attribute name="scope" use="optional" default="system">
|
|
95
|
<xs:simpleType>
|
|
96
|
<xs:restriction base="xs:string">
|
|
97
|
<xs:enumeration value="system"/>
|
|
98
|
<xs:enumeration value="document"/>
|
|
99
|
</xs:restriction>
|
|
100
|
</xs:simpleType>
|
|
101
|
</xs:attribute>
|
|
102
|
</xs:complexType>
|
|
103
|
<xs:complexType name="AttributeDefinitionType">
|
|
104
|
<xs:annotation>
|
|
105
|
<xs:appinfo>
|
|
106
|
<doc:tooltip>
|
|
107
|
Attribute descriptors
|
|
108
|
</doc:tooltip>
|
|
109
|
<doc:summary>
|
|
110
|
Container of attribute descriptors of all attributes in a dataset.
|
|
111
|
</doc:summary>
|
|
112
|
<doc:description>
|
|
113
|
Eml-attribute element represents a list of all attributes in a
|
|
114
|
dataset.
|
|
115
|
</doc:description>
|
|
116
|
<doc:example/>
|
|
117
|
<doc:lineage>
|
|
118
|
The eml-attribute was introduced into EML 1.4 as eml-variable.
|
|
119
|
</doc:lineage>
|
|
120
|
</xs:appinfo>
|
|
121
|
</xs:annotation>
|
|
122
|
<xs:sequence>
|
|
123
|
<xs:element name="attributeName" type="xs:string">
|
|
124
|
<xs:annotation>
|
|
125
|
<xs:appinfo>
|
|
126
|
<doc:tooltip>
|
|
127
|
Attribute name
|
|
128
|
</doc:tooltip>
|
|
129
|
<doc:summary>
|
|
130
|
Attribute name for identification
|
|
131
|
</doc:summary>
|
|
132
|
<doc:description>
|
|
133
|
This element specifies name of the attribute (field)
|
|
134
|
in the dataset. This information is typically used as
|
|
135
|
a column header for the field/variable in a spreadsheet.
|
|
136
|
It is usually terse, without spaces, and can be used
|
|
137
|
to "name" a column in a table definition statement.
|
|
138
|
</doc:description>
|
|
139
|
<doc:example>
|
|
140
|
spden
|
|
141
|
</doc:example>
|
|
142
|
<doc:lineage>
|
|
143
|
The attributeName was introduced into EML 1.4.
|
|
144
|
</doc:lineage>
|
|
145
|
</xs:appinfo>
|
|
146
|
</xs:annotation>
|
|
147
|
</xs:element>
|
|
148
|
<xs:element name="attributeLabel" type="xs:string" minOccurs="0" maxOccurs="unbounded">
|
|
149
|
<xs:annotation>
|
|
150
|
<xs:appinfo>
|
|
151
|
<doc:tooltip>
|
|
152
|
Attribute label
|
|
153
|
</doc:tooltip>
|
|
154
|
<doc:summary>
|
|
155
|
A label that better describes an attribute than its name
|
|
156
|
</doc:summary>
|
|
157
|
<doc:description>
|
|
158
|
A brief label used to describe the attribute. This
|
|
159
|
is often needed because attribute names are usually
|
|
160
|
very terse- often shortened to 8 characters or less to
|
|
161
|
deal with analysis systems. A label is provided as
|
|
162
|
a concise but more descriptive representation of
|
|
163
|
the attribute.
|
|
164
|
</doc:description>
|
|
165
|
<doc:example>
|
|
166
|
"Species Density" is a label for attribute with
|
|
167
|
name "spden"
|
|
168
|
</doc:example>
|
|
169
|
<doc:lineage>
|
|
170
|
Introduced in EML 2.0
|
|
171
|
</doc:lineage>
|
|
172
|
</xs:appinfo>
|
|
173
|
</xs:annotation>
|
|
174
|
</xs:element>
|
|
175
|
<xs:element name="attributeDefinition" type="xs:string">
|
|
176
|
<xs:annotation>
|
|
177
|
<xs:appinfo>
|
|
178
|
<doc:tooltip>
|
|
179
|
Attribute definition
|
|
180
|
</doc:tooltip>
|
|
181
|
<doc:summary>
|
|
182
|
Precise definition of attribute in the dataset
|
|
183
|
</doc:summary>
|
|
184
|
<doc:description>
|
|
185
|
This element gives a precise definition of attribute
|
|
186
|
in the dataset. It explains the contents of the attribute
|
|
187
|
fully and possibly provides pointers to the methods
|
|
188
|
used to generate the attribute data.
|
|
189
|
</doc:description>
|
|
190
|
<doc:example>
|
|
191
|
"spden" is the number of individuals of all
|
|
192
|
macroinvertebrate species found in the plot
|
|
193
|
</doc:example>
|
|
194
|
<doc:lineage>
|
|
195
|
The attributeDefinition was introduced into EML 1.4.
|
|
196
|
</doc:lineage>
|
|
197
|
</xs:appinfo>
|
|
198
|
</xs:annotation>
|
|
199
|
</xs:element>
|
|
200
|
<xs:element name="unit" type="xs:anyURI" default="http://ecoinformatics.org/unitDictionary?unitType=dimensionless">
|
|
201
|
<xs:annotation>
|
|
202
|
<xs:appinfo>
|
|
203
|
<doc:tooltip>
|
|
204
|
Unit of measurement
|
|
205
|
</doc:tooltip>
|
|
206
|
<doc:summary>
|
|
207
|
Unit of measurement for data in the field
|
|
208
|
</doc:summary>
|
|
209
|
<doc:description>
|
|
210
|
This element defines the unit of this attribute. This field
|
|
211
|
should be a URI that defines the unit with respect to
|
|
212
|
the eml unit dictionary (eml-unitDictionary.xml). The
|
|
213
|
URI is of the form
|
|
214
|
http://ecoinformatics.org/unitDictionary?unitType=<dictionary unitType>&<unitType dimension name>=<unit id>
|
|
215
|
This is an implementation of STMML
|
|
216
|
(see http://www.xml-cml.org/stmml) for details.
|
|
217
|
|
|
218
|
For count units, the dimensionless unitType should be
|
|
219
|
used.
|
|
220
|
http://ecoinformatics.org/unitDictionary?unitType=dimensionless
|
|
221
|
</doc:description>
|
|
222
|
<doc:example>
|
|
223
|
Length in meters
|
|
224
|
http://ecoinformatics.org/unitDictionary?unitType=length&length=meter
|
|
225
|
Acceleration in Meters per Second Squared
|
|
226
|
http://ecoinformatics.org/unitDictionary?unitType=acceleration&length=meter&time=second
|
|
227
|
</doc:example>
|
|
228
|
<doc:lineage>
|
|
229
|
The unit was introduced into EML 1.4.
|
|
230
|
</doc:lineage>
|
|
231
|
</xs:appinfo>
|
|
232
|
</xs:annotation>
|
|
233
|
</xs:element>
|
|
234
|
<xs:element name="storageType" minOccurs="0">
|
|
235
|
<xs:annotation>
|
|
236
|
<xs:appinfo>
|
|
237
|
<doc:tooltip>
|
|
238
|
Data type
|
|
239
|
</doc:tooltip>
|
|
240
|
<doc:summary>
|
|
241
|
Description of storage type for this field
|
|
242
|
</doc:summary>
|
|
243
|
<doc:description>
|
|
244
|
This element describes the storage type for data in the
|
|
245
|
field like: xs:integer, xs:double, xs:string, etc.
|
|
246
|
It is recommended that at a minimum the XML Schema type
|
|
247
|
system should be used, although this is not required.
|
|
248
|
Whatever type system is used should be noted in the
|
|
249
|
'unitSystem' attribute described below.
|
|
250
|
</doc:description>
|
|
251
|
<doc:example>
|
|
252
|
xs:string, xs:integer
|
|
253
|
</doc:example>
|
|
254
|
<doc:lineage>
|
|
255
|
From storageType, introduced in EML 1.4.
|
|
256
|
Transformed to dataType in EML 2.0 Beta 1.
|
|
257
|
Transformed to storageType in EML 2.0 Beta 9
|
|
258
|
</doc:lineage>
|
|
259
|
</xs:appinfo>
|
|
260
|
</xs:annotation>
|
|
261
|
<xs:complexType>
|
|
262
|
<xs:simpleContent>
|
|
263
|
<xs:extension base="xs:string">
|
|
264
|
<xs:attribute name="unitSystem" type="xs:string" use="optional" default="XML-SCHEMA">
|
|
265
|
<xs:annotation>
|
|
266
|
<xs:appinfo>
|
|
267
|
<doc:tooltip>
|
|
268
|
The system used to define the storage types
|
|
269
|
</doc:tooltip>
|
|
270
|
<doc:summary>
|
|
271
|
The system used to define the storage types. This should
|
|
272
|
be an identifier of a well known and published typing system.
|
|
273
|
</doc:summary>
|
|
274
|
<doc:description>
|
|
275
|
The system used to define the storage types. This should
|
|
276
|
an identifier of a well known and published typing system.
|
|
277
|
It is recommended to use the XML Schema data type
|
|
278
|
system. For details go to http://www.w3.org. If
|
|
279
|
another system is used (such as Java or C++ types)
|
|
280
|
unitSystem should be be changed to match the
|
|
281
|
system.
|
|
282
|
</doc:description>
|
|
283
|
<doc:example><![CDATA[
|
|
284
|
<storageType unitSystem="STMML">xs:integer</storageType]]></doc:example>
|
|
285
|
<doc:lineage>
|
|
286
|
New to EML 2.0.
|
|
287
|
</doc:lineage>
|
|
288
|
</xs:appinfo>
|
|
289
|
</xs:annotation>
|
|
290
|
</xs:attribute>
|
|
291
|
</xs:extension>
|
|
292
|
</xs:simpleContent>
|
|
293
|
</xs:complexType>
|
|
294
|
</xs:element>
|
|
295
|
<xs:element name="measurementScale">
|
|
296
|
<xs:annotation>
|
|
297
|
<xs:appinfo>
|
|
298
|
<doc:tooltip>
|
|
299
|
The scale of the measured attribute.
|
|
300
|
</doc:tooltip>
|
|
301
|
<doc:summary>
|
|
302
|
The scale of the measured attribute. This provides
|
|
303
|
information about the scale in which the data was
|
|
304
|
collected.
|
|
305
|
</doc:summary>
|
|
306
|
<doc:description>
|
|
307
|
The scale of the measured attribute. This provides
|
|
308
|
information about the scale in which the data was
|
|
309
|
collected. The allowed values are 'ratio', 'ordinal',
|
|
310
|
'nominal' and 'interval'
|
|
311
|
</doc:description>
|
|
312
|
<doc:example>
|
|
313
|
nominal
|
|
314
|
</doc:example>
|
|
315
|
</xs:appinfo>
|
|
316
|
</xs:annotation>
|
|
317
|
<xs:simpleType>
|
|
318
|
<xs:restriction base="xs:string">
|
|
319
|
<xs:enumeration value="ratio"/>
|
|
320
|
<xs:enumeration value="nominal"/>
|
|
321
|
<xs:enumeration value="ordinal"/>
|
|
322
|
<xs:enumeration value="interval"/>
|
|
323
|
</xs:restriction>
|
|
324
|
</xs:simpleType>
|
|
325
|
</xs:element>
|
|
326
|
<xs:element name="attributeDomain">
|
|
327
|
<xs:complexType>
|
|
328
|
<xs:choice>
|
|
329
|
<xs:element name="enumeratedDomain">
|
|
330
|
<xs:annotation>
|
|
331
|
<xs:appinfo>
|
|
332
|
<doc:tooltip>
|
|
333
|
Code definition
|
|
334
|
</doc:tooltip>
|
|
335
|
<doc:summary>
|
|
336
|
Description of any codes associated with the attribute
|
|
337
|
</doc:summary>
|
|
338
|
<doc:description>
|
|
339
|
This element describes any code associated with the
|
|
340
|
attribute.
|
|
341
|
</doc:description>
|
|
342
|
<doc:example>
|
|
343
|
The format will typically be : "code" has "definition",
|
|
344
|
e.g. "1" = "high", "2" = "medium", "3" = "low"
|
|
345
|
</doc:example>
|
|
346
|
<doc:lineage>
|
|
347
|
The codeDefinition was introduced into EML 1.4.
|
|
348
|
</doc:lineage>
|
|
349
|
</xs:appinfo>
|
|
350
|
</xs:annotation>
|
|
351
|
<xs:complexType>
|
|
352
|
<xs:sequence>
|
|
353
|
<xs:element name="code" type="xs:string">
|
|
354
|
<xs:annotation>
|
|
355
|
<xs:appinfo>
|
|
356
|
<doc:tooltip>
|
|
357
|
Code
|
|
358
|
</doc:tooltip>
|
|
359
|
<doc:summary>
|
|
360
|
Code associated with the attribute
|
|
361
|
</doc:summary>
|
|
362
|
<doc:description>
|
|
363
|
This element specifies a code associated with
|
|
364
|
the attribute.
|
|
365
|
</doc:description>
|
|
366
|
<doc:example>
|
|
367
|
"1" would be the code for "high" (where high is the description
|
|
368
|
of the code)
|
|
369
|
</doc:example>
|
|
370
|
<doc:lineage>
|
|
371
|
The code element was introduced into EML 1.4.
|
|
372
|
</doc:lineage>
|
|
373
|
</xs:appinfo>
|
|
374
|
</xs:annotation>
|
|
375
|
</xs:element>
|
|
376
|
<xs:element name="definition" type="xs:string">
|
|
377
|
<xs:annotation>
|
|
378
|
<xs:appinfo>
|
|
379
|
<doc:tooltip>
|
|
380
|
Code definition
|
|
381
|
</doc:tooltip>
|
|
382
|
<doc:summary>
|
|
383
|
Description of the code associated with
|
|
384
|
the attribute.
|
|
385
|
</doc:summary>
|
|
386
|
<doc:description>
|
|
387
|
This element describes the code associated
|
|
388
|
with the attribute.
|
|
389
|
</doc:description>
|
|
390
|
<doc:example>
|
|
391
|
"high" would be the definition for a code of "1"
|
|
392
|
</doc:example>
|
|
393
|
<doc:lineage>
|
|
394
|
The definition element is from EML 1.4.
|
|
395
|
</doc:lineage>
|
|
396
|
</xs:appinfo>
|
|
397
|
</xs:annotation>
|
|
398
|
</xs:element>
|
|
399
|
<xs:element name="source" type="xs:string" minOccurs="0">
|
|
400
|
<xs:annotation>
|
|
401
|
<xs:appinfo>
|
|
402
|
<doc:tooltip>
|
|
403
|
Source of code
|
|
404
|
</doc:tooltip>
|
|
405
|
<doc:summary>
|
|
406
|
The name of the source for this code and
|
|
407
|
its definition
|
|
408
|
</doc:summary>
|
|
409
|
<doc:description>
|
|
410
|
The name of the source from which this code
|
|
411
|
and its associated definition are drawn.
|
|
412
|
This is commonly used for identifying
|
|
413
|
standard coding systems, like the FIPS
|
|
414
|
standard for postal abbreviations for states
|
|
415
|
in the US. In other cases, the coding may be the
|
|
416
|
researcher's customized way of recording and classifying
|
|
417
|
their data, and no external "source" would exist.
|
|
418
|
</doc:description>
|
|
419
|
<doc:example>ISO country codes</doc:example>
|
|
420
|
<doc:lineage>
|
|
421
|
Introduced in EML 2.0
|
|
422
|
</doc:lineage>
|
|
423
|
</xs:appinfo>
|
|
424
|
</xs:annotation>
|
|
425
|
</xs:element>
|
|
426
|
</xs:sequence>
|
|
427
|
<xs:attribute name="enforced" default="yes">
|
|
428
|
<xs:simpleType>
|
|
429
|
<xs:restriction base="xs:string">
|
|
430
|
<xs:enumeration value="yes"/>
|
|
431
|
<xs:enumeration value="no"/>
|
|
432
|
</xs:restriction>
|
|
433
|
</xs:simpleType>
|
|
434
|
</xs:attribute>
|
|
435
|
</xs:complexType>
|
|
436
|
</xs:element>
|
|
437
|
<xs:element name="textDomain">
|
|
438
|
<xs:annotation>
|
|
439
|
<xs:appinfo>
|
|
440
|
<doc:tooltip>Text domain</doc:tooltip>
|
|
441
|
<doc:summary>
|
|
442
|
Description of a free-text domain pattern for
|
|
443
|
the attribute
|
|
444
|
</doc:summary>
|
|
445
|
<doc:description>
|
|
446
|
This element describes a free text domain for
|
|
447
|
the attribute. By default, if pattern is missing
|
|
448
|
or empty, then any text is allowed. If pattern
|
|
449
|
is present, then it is interpreted as a regular
|
|
450
|
expression constraining the allowable character
|
|
451
|
sequences for the attribute.
|
|
452
|
</doc:description>
|
|
453
|
<doc:example>
|
|
454
|
Typically, a textdomain will have an empty pattern
|
|
455
|
or one that constrains allowable values. For
|
|
456
|
example, '[0-9]{3}-[0-9]{3}-[0-9]{4}' allows
|
|
457
|
for only numeric digits in the pattern of a US
|
|
458
|
phone number.
|
|
459
|
</doc:example>
|
|
460
|
<doc:lineage>
|
|
461
|
Introduced in EML 2.0.0beta5
|
|
462
|
</doc:lineage>
|
|
463
|
</xs:appinfo>
|
|
464
|
</xs:annotation>
|
|
465
|
<xs:complexType>
|
|
466
|
<xs:sequence>
|
|
467
|
<xs:element name="definition" type="xs:string">
|
|
468
|
<xs:annotation>
|
|
469
|
<xs:appinfo>
|
|
470
|
<doc:tooltip>
|
|
471
|
Text domain definition
|
|
472
|
</doc:tooltip>
|
|
473
|
<doc:summary>
|
|
474
|
Definition of what this text domain represents
|
|
475
|
</doc:summary>
|
|
476
|
<doc:description>
|
|
477
|
The text domain definition indicates what
|
|
478
|
the purpose of the text domain is for this
|
|
479
|
attribute. For example, a particular pattern
|
|
480
|
may be meant to represent phone numbers in
|
|
481
|
the US phone system format, or it may be
|
|
482
|
used to extend an enumerated domain with
|
|
483
|
free text or pattern-constrained values.
|
|
484
|
</doc:description>
|
|
485
|
<doc:example>
|
|
486
|
US telephone numbers in the format "(999) 888-7777"
|
|
487
|
</doc:example>
|
|
488
|
<doc:lineage>
|
|
489
|
The definition element is from EML 1.4.
|
|
490
|
</doc:lineage>
|
|
491
|
</xs:appinfo>
|
|
492
|
</xs:annotation>
|
|
493
|
</xs:element>
|
|
494
|
<xs:element name="pattern" type="xs:string" minOccurs="0" maxOccurs="unbounded">
|
|
495
|
<xs:annotation>
|
|
496
|
<xs:appinfo>
|
|
497
|
<doc:tooltip>
|
|
498
|
Text pattern
|
|
499
|
</doc:tooltip>
|
|
500
|
<doc:summary>
|
|
501
|
Regular expression pattern constraining
|
|
502
|
the attribute
|
|
503
|
</doc:summary>
|
|
504
|
<doc:description>
|
|
505
|
The "pattern" element specifies a regular
|
|
506
|
expression pattern that constrains the
|
|
507
|
set of allowable values for the attribute.
|
|
508
|
This is commonly used to define template
|
|
509
|
patterns for data such as phone numbers
|
|
510
|
where the attribute is text but the
|
|
511
|
values are not drawn from an enumeration.
|
|
512
|
If the pattern field is empty or missing,
|
|
513
|
it defaults to '.*', which matches any
|
|
514
|
string, including the empty string.
|
|
515
|
Repeated pattern elements are combined
|
|
516
|
using logical OR. The regular expression
|
|
517
|
syntax is the same as that used in the
|
|
518
|
XML Schema Datatypes Recommendation from
|
|
519
|
the W3C.
|
|
520
|
</doc:description>
|
|
521
|
<doc:example>
|
|
522
|
'[0-9a-zA-Z]' matches simple alphanumeric
|
|
523
|
strings and '(\d\d\d) \d\d\d-\d\d\d\d'
|
|
524
|
represents telephone strings in the US of
|
|
525
|
the form '(704) 876-1734'
|
|
526
|
</doc:example>
|
|
527
|
<doc:lineage>
|
|
528
|
The pattern element was introduced into EML 2.0.0beta5.
|
|
529
|
</doc:lineage>
|
|
530
|
</xs:appinfo>
|
|
531
|
</xs:annotation>
|
|
532
|
</xs:element>
|
|
533
|
<xs:element name="source" type="xs:string" minOccurs="0">
|
|
534
|
<xs:annotation>
|
|
535
|
<xs:appinfo>
|
|
536
|
<doc:tooltip>
|
|
537
|
Source of text domain
|
|
538
|
</doc:tooltip>
|
|
539
|
<doc:summary>
|
|
540
|
The name of the source for this text domain.
|
|
541
|
</doc:summary>
|
|
542
|
<doc:description>
|
|
543
|
The name of the source from which this text domain
|
|
544
|
and its associated definition are drawn.
|
|
545
|
This is commonly used for identifying
|
|
546
|
standard coding systems, like the FIPS
|
|
547
|
standard for postal abbreviations for states
|
|
548
|
in the US. In other cases, the coding may be the
|
|
549
|
researcher's customized way of recording and classifying
|
|
550
|
their data, and no external "source" would exist.
|
|
551
|
</doc:description>
|
|
552
|
<doc:example>ISO country codes</doc:example>
|
|
553
|
<doc:lineage>
|
|
554
|
Introduced in EML 2.0
|
|
555
|
</doc:lineage>
|
|
556
|
</xs:appinfo>
|
|
557
|
</xs:annotation>
|
|
558
|
</xs:element>
|
|
559
|
</xs:sequence>
|
|
560
|
</xs:complexType>
|
|
561
|
</xs:element>
|
|
562
|
<xs:element name="numericDomain" maxOccurs="unbounded">
|
|
563
|
<xs:annotation>
|
|
564
|
<xs:appinfo>
|
|
565
|
<doc:tooltip>
|
|
566
|
Numeric Domain
|
|
567
|
</doc:tooltip>
|
|
568
|
<doc:summary>
|
|
569
|
Numeric domain of attribute specifying allowed value range
|
|
570
|
</doc:summary>
|
|
571
|
<doc:description>
|
|
572
|
This element specifies the minimum and maximum values
|
|
573
|
of a numeric attribute. These are theoretical or expected
|
|
574
|
values, and not necessarily the actual minimum and maximum
|
|
575
|
occurring in a given data set.
|
|
576
|
</doc:description>
|
|
577
|
<doc:example/>
|
|
578
|
<doc:lineage>
|
|
579
|
The numericDomain was introduced into EML 1.4 as rangeDomain
|
|
580
|
</doc:lineage>
|
|
581
|
</xs:appinfo>
|
|
582
|
</xs:annotation>
|
|
583
|
<xs:complexType>
|
|
584
|
<xs:sequence>
|
|
585
|
<xs:element name="minimum" type="xs:string" minOccurs="0">
|
|
586
|
<xs:annotation>
|
|
587
|
<xs:appinfo>
|
|
588
|
<doc:tooltip>
|
|
589
|
Minimum numeric range
|
|
590
|
</doc:tooltip>
|
|
591
|
<doc:summary>
|
|
592
|
Minimum numeric range of attribute
|
|
593
|
</doc:summary>
|
|
594
|
<doc:description>
|
|
595
|
This element specifies the minimum value range
|
|
596
|
of numeric attribute.
|
|
597
|
</doc:description>
|
|
598
|
<doc:example/>
|
|
599
|
<doc:lineage>
|
|
600
|
The minimum element was introduced into EML 1.4.
|
|
601
|
</doc:lineage>
|
|
602
|
</xs:appinfo>
|
|
603
|
</xs:annotation>
|
|
604
|
</xs:element>
|
|
605
|
<xs:element name="maximum" type="xs:string" minOccurs="0">
|
|
606
|
<xs:annotation>
|
|
607
|
<xs:appinfo>
|
|
608
|
<doc:tooltip>
|
|
609
|
Maximum numeric range
|
|
610
|
</doc:tooltip>
|
|
611
|
<doc:summary>
|
|
612
|
Maximum numeric range of attribute
|
|
613
|
</doc:summary>
|
|
614
|
<doc:description>
|
|
615
|
This element specifies the maximum value range
|
|
616
|
of numeric attribute.
|
|
617
|
</doc:description>
|
|
618
|
<doc:example/>
|
|
619
|
<doc:lineage>
|
|
620
|
The maximum element was introduced into EML 1.4.
|
|
621
|
</doc:lineage>
|
|
622
|
</xs:appinfo>
|
|
623
|
</xs:annotation>
|
|
624
|
</xs:element>
|
|
625
|
</xs:sequence>
|
|
626
|
</xs:complexType>
|
|
627
|
</xs:element>
|
|
628
|
</xs:choice>
|
|
629
|
</xs:complexType>
|
|
630
|
</xs:element>
|
|
631
|
<xs:element name="missingValueCode" minOccurs="0" maxOccurs="unbounded">
|
|
632
|
<xs:annotation>
|
|
633
|
<xs:appinfo>
|
|
634
|
<doc:tooltip>
|
|
635
|
Character for missing value
|
|
636
|
</doc:tooltip>
|
|
637
|
<doc:summary>
|
|
638
|
Character for missing value in the data of the field
|
|
639
|
</doc:summary>
|
|
640
|
<doc:description>
|
|
641
|
This element is to specify missing value in the data
|
|
642
|
of the field.
|
|
643
|
</doc:description>
|
|
644
|
<doc:example/>
|
|
645
|
<doc:lineage>
|
|
646
|
The missingValueCode was introduced into EML 1.4.
|
|
647
|
</doc:lineage>
|
|
648
|
</xs:appinfo>
|
|
649
|
</xs:annotation>
|
|
650
|
<xs:complexType>
|
|
651
|
<xs:sequence>
|
|
652
|
<xs:element name="code" type="xs:string">
|
|
653
|
<xs:annotation>
|
|
654
|
<xs:appinfo>
|
|
655
|
<doc:tooltip>
|
|
656
|
The missing value code itself.
|
|
657
|
</doc:tooltip>
|
|
658
|
<doc:summary>
|
|
659
|
The missing value code itself.
|
|
660
|
</doc:summary>
|
|
661
|
<doc:description>
|
|
662
|
The missing value code itself. This should describe
|
|
663
|
what is placed into a data grid if the value is
|
|
664
|
missing for some reason.
|
|
665
|
</doc:description>
|
|
666
|
<doc:example>
|
|
667
|
-9999, -1, N/A, MISSING, .
|
|
668
|
</doc:example>
|
|
669
|
<doc:lineage>
|
|
670
|
Added in EML-2.0.0beta9
|
|
671
|
</doc:lineage>
|
|
672
|
</xs:appinfo>
|
|
673
|
</xs:annotation>
|
|
674
|
</xs:element>
|
|
675
|
<xs:element name="codeExplanation" type="xs:string">
|
|
676
|
<xs:annotation>
|
|
677
|
<xs:appinfo>
|
|
678
|
<doc:tooltip>
|
|
679
|
An explanation of why the missing value code was
|
|
680
|
used.
|
|
681
|
</doc:tooltip>
|
|
682
|
<doc:summary>
|
|
683
|
An explanation of why the missing value code was
|
|
684
|
used.
|
|
685
|
</doc:summary>
|
|
686
|
<doc:description>
|
|
687
|
An explanation of why the missing value code was
|
|
688
|
used. This should also explain what different
|
|
689
|
missing value codes mean. For instance if -9999
|
|
690
|
represents a sensor error and -1 represents
|
|
691
|
a technician error this should be noted.
|
|
692
|
</doc:description>
|
|
693
|
<doc:example>
|
|
694
|
Sensor down time.
|
|
695
|
</doc:example>
|
|
696
|
<doc:lineage>
|
|
697
|
Added in eml-2.0.0beta9
|
|
698
|
</doc:lineage>
|
|
699
|
</xs:appinfo>
|
|
700
|
</xs:annotation>
|
|
701
|
</xs:element>
|
|
702
|
</xs:sequence>
|
|
703
|
</xs:complexType>
|
|
704
|
</xs:element>
|
|
705
|
<xs:element name="precision" type="xs:string" minOccurs="0">
|
|
706
|
<xs:annotation>
|
|
707
|
<xs:appinfo>
|
|
708
|
<doc:tooltip>
|
|
709
|
Precision
|
|
710
|
</doc:tooltip>
|
|
711
|
<doc:summary>
|
|
712
|
Number of significat digits after the floating point.
|
|
713
|
</doc:summary>
|
|
714
|
<doc:description>
|
|
715
|
If data of that field are of floating point storage type
|
|
716
|
this element specifies the number of significat digits
|
|
717
|
after the floating point.
|
|
718
|
</doc:description>
|
|
719
|
<doc:example>
|
|
720
|
any integer number
|
|
721
|
</doc:example>
|
|
722
|
<doc:lineage>
|
|
723
|
The precision element was introduced into EML 1.4.
|
|
724
|
</doc:lineage>
|
|
725
|
</xs:appinfo>
|
|
726
|
</xs:annotation>
|
|
727
|
</xs:element>
|
|
728
|
<xs:element name="accuracy" type="Accuracy">
|
|
729
|
<xs:annotation>
|
|
730
|
<xs:appinfo>
|
|
731
|
<doc:tooltip>
|
|
732
|
The accuracy of the measured attribute
|
|
733
|
</doc:tooltip>
|
|
734
|
<doc:summary>
|
|
735
|
The accuracy of the attribute. This information should
|
|
736
|
describe any accuracy information that is known about
|
|
737
|
the collection of this data attribute.
|
|
738
|
</doc:summary>
|
|
739
|
<doc:description>
|
|
740
|
The accuracy of the attribute. This information should
|
|
741
|
describe any accuracy information that is known about
|
|
742
|
the collection of this data attribute. The content
|
|
743
|
model of this metadata is taken directly from FGDC
|
|
744
|
FGDC-STD-001-1998 section 2 with the exception of
|
|
745
|
processContact, sourceCitation, and timePeriodInformation
|
|
746
|
which either user XMLSchema types or use predefined
|
|
747
|
EML types for these purposes.
|
|
748
|
</doc:description>
|
|
749
|
<doc:example/>
|
|
750
|
<doc:lineage>
|
|
751
|
New in EML 2.0.0beta9
|
|
752
|
</doc:lineage>
|
|
753
|
</xs:appinfo>
|
|
754
|
</xs:annotation>
|
|
755
|
</xs:element>
|
|
756
|
</xs:sequence>
|
|
757
|
<xs:attribute name="id" type="xs:ID" use="required"/>
|
|
758
|
<xs:attribute name="system" type="xs:string" use="required"/>
|
|
759
|
<xs:attribute name="scope" use="optional" default="system">
|
|
760
|
<xs:simpleType>
|
|
761
|
<xs:restriction base="xs:string">
|
|
762
|
<xs:enumeration value="system"/>
|
|
763
|
<xs:enumeration value="document"/>
|
|
764
|
</xs:restriction>
|
|
765
|
</xs:simpleType>
|
|
766
|
</xs:attribute>
|
|
767
|
</xs:complexType>
|
|
768
|
<xs:complexType name="Accuracy">
|
|
769
|
<xs:sequence>
|
|
770
|
<xs:element name="attributeAccuracyReport" type="xs:string">
|
|
771
|
<xs:annotation>
|
|
772
|
<xs:appinfo>
|
|
773
|
<doc:tooltip>
|
|
774
|
an explanation of the accuracy of the identification of the
|
|
775
|
entities and assignments of values in the data set and a
|
|
776
|
description of the tests used.
|
|
777
|
</doc:tooltip>
|
|
778
|
<doc:summary>
|
|
779
|
an explanation of the accuracy of the identification of the
|
|
780
|
entities and assignments of values in the data set and a
|
|
781
|
description of the tests used.
|
|
782
|
</doc:summary>
|
|
783
|
<doc:description>
|
|
784
|
an explanation of the accuracy of the identification of the
|
|
785
|
entities and assignments of values in the data set and a
|
|
786
|
description of the tests used.
|
|
787
|
</doc:description>
|
|
788
|
<doc:example/>
|
|
789
|
<doc:lineage>
|
|
790
|
FGDC-STD-001-1998 section 2
|
|
791
|
</doc:lineage>
|
|
792
|
</xs:appinfo>
|
|
793
|
</xs:annotation>
|
|
794
|
</xs:element>
|
|
795
|
<xs:element name="quantitativeAttributeAccuracyAssessment" minOccurs="0" maxOccurs="unbounded">
|
|
796
|
<xs:annotation>
|
|
797
|
<xs:appinfo>
|
|
798
|
<doc:tooltip>
|
|
799
|
a value assigned to summarize the accuracy of the
|
|
800
|
identification of the entities and assignments of values
|
|
801
|
in the data set and the identification of the test that
|
|
802
|
yielded the value.
|
|
803
|
</doc:tooltip>
|
|
804
|
<doc:summary>
|
|
805
|
a value assigned to summarize the accuracy of the
|
|
806
|
identification of the entities and assignments of values
|
|
807
|
in the data set and the identification of the test that
|
|
808
|
yielded the value.
|
|
809
|
</doc:summary>
|
|
810
|
<doc:description>
|
|
811
|
a value assigned to summarize the accuracy of the
|
|
812
|
identification of the entities and assignments of values
|
|
813
|
in the data set and the identification of the test that
|
|
814
|
yielded the value.
|
|
815
|
</doc:description>
|
|
816
|
<doc:example/>
|
|
817
|
<doc:lineage>
|
|
818
|
FGDC-STD-001-1998 section 2
|
|
819
|
</doc:lineage>
|
|
820
|
</xs:appinfo>
|
|
821
|
</xs:annotation>
|
|
822
|
<xs:complexType>
|
|
823
|
<xs:sequence>
|
|
824
|
<xs:element name="attributeAccuracyValue" type="xs:string">
|
|
825
|
<xs:annotation>
|
|
826
|
<xs:appinfo>
|
|
827
|
<doc:tooltip>
|
|
828
|
an estimate of the accuracy of the identification of
|
|
829
|
the entities and assignments of attribute values
|
|
830
|
in the data set.
|
|
831
|
</doc:tooltip>
|
|
832
|
<doc:summary>
|
|
833
|
an estimate of the accuracy of the identification of
|
|
834
|
the entities and assignments of attribute values
|
|
835
|
in the data set.
|
|
836
|
</doc:summary>
|
|
837
|
<doc:description>
|
|
838
|
an estimate of the accuracy of the identification of
|
|
839
|
the entities and assignments of attribute values
|
|
840
|
in the data set.
|
|
841
|
</doc:description>
|
|
842
|
<doc:example/>
|
|
843
|
<doc:lineage>
|
|
844
|
FGDC-STD-001-1998 section 2
|
|
845
|
</doc:lineage>
|
|
846
|
</xs:appinfo>
|
|
847
|
</xs:annotation>
|
|
848
|
</xs:element>
|
|
849
|
<xs:element name="attributeAccuracyExplanation" type="xs:string">
|
|
850
|
<xs:annotation>
|
|
851
|
<xs:appinfo>
|
|
852
|
<doc:tooltip>
|
|
853
|
the identification of the test that yielded the
|
|
854
|
Attribute Accuracy Value.
|
|
855
|
</doc:tooltip>
|
|
856
|
<doc:summary>
|
|
857
|
the identification of the test that yielded the
|
|
858
|
Attribute Accuracy Value.
|
|
859
|
</doc:summary>
|
|
860
|
<doc:description>
|
|
861
|
the identification of the test that yielded the
|
|
862
|
Attribute Accuracy Value.
|
|
863
|
</doc:description>
|
|
864
|
<doc:example/>
|
|
865
|
<doc:lineage>
|
|
866
|
FGDC-STD-001-1998 section 2
|
|
867
|
</doc:lineage>
|
|
868
|
</xs:appinfo>
|
|
869
|
</xs:annotation>
|
|
870
|
</xs:element>
|
|
871
|
</xs:sequence>
|
|
872
|
</xs:complexType>
|
|
873
|
</xs:element>
|
|
874
|
</xs:sequence>
|
|
875
|
</xs:complexType>
|
|
876
|
<xs:complexType name="AttributeType">
|
|
877
|
<xs:choice>
|
|
878
|
<xs:element name="attributeDefinition" type="AttributeDefinitionType"/>
|
|
879
|
<xs:element name="references"/>
|
|
880
|
</xs:choice>
|
|
881
|
</xs:complexType>
|
|
882
|
<xs:element name="AttributeListType">
|
|
883
|
<xs:complexType>
|
|
884
|
<xs:choice>
|
|
885
|
<xs:element name="attributeListDefinition" type="AttributeListDefinitionType"/>
|
|
886
|
<xs:element name="references"/>
|
|
887
|
</xs:choice>
|
|
888
|
</xs:complexType>
|
|
889
|
</xs:element>
|
|
890
|
</xs:schema>
|