-
-
Notifications
You must be signed in to change notification settings - Fork 15
/
discovery-and-interpretation-modules.html
567 lines (526 loc) · 47.9 KB
/
discovery-and-interpretation-modules.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<title>7 Discovery and Interpretation Modules | Ecological Metadata Language (EML)</title>
<meta name="description" content="7 Discovery and Interpretation Modules | Ecological Metadata Language (EML)" />
<meta name="generator" content="bookdown 0.12 and GitBook 2.6.7" />
<meta property="og:title" content="7 Discovery and Interpretation Modules | Ecological Metadata Language (EML)" />
<meta property="og:type" content="book" />
<meta name="twitter:card" content="summary" />
<meta name="twitter:title" content="7 Discovery and Interpretation Modules | Ecological Metadata Language (EML)" />
<meta name="date" content="2019-08-15" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black" />
<link rel="prev" href="data-structure-modules.html">
<link rel="next" href="utility-modules.html">
<script src="libs/jquery-2.2.3/jquery.min.js"></script>
<link href="libs/gitbook-2.6.7/css/style.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-table.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-bookdown.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-highlight.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-search.css" rel="stylesheet" />
<link href="libs/gitbook-2.6.7/css/plugin-fontsettings.css" rel="stylesheet" />
<style type="text/css">
a.sourceLine { display: inline-block; line-height: 1.25; }
a.sourceLine { pointer-events: none; color: inherit; text-decoration: inherit; }
a.sourceLine:empty { height: 1.2em; position: absolute; }
.sourceCode { overflow: visible; }
code.sourceCode { white-space: pre; position: relative; }
pre.sourceCode { margin: 0; }
@media screen {
div.sourceCode { overflow: auto; }
}
@media print {
code.sourceCode { white-space: pre-wrap; }
a.sourceLine { text-indent: -1em; padding-left: 1em; }
}
pre.numberSource a.sourceLine
{ position: relative; }
pre.numberSource a.sourceLine:empty
{ position: absolute; }
pre.numberSource a.sourceLine::before
{ content: attr(data-line-number);
position: absolute; left: -5em; text-align: right; vertical-align: baseline;
border: none; pointer-events: all;
-webkit-touch-callout: none; -webkit-user-select: none;
-khtml-user-select: none; -moz-user-select: none;
-ms-user-select: none; user-select: none;
padding: 0 4px; width: 4em;
color: #aaaaaa;
}
pre.numberSource { margin-left: 3em; border-left: 1px solid #aaaaaa; padding-left: 4px; }
div.sourceCode
{ }
@media screen {
a.sourceLine::before { text-decoration: underline; }
}
code span.al { color: #ff0000; font-weight: bold; } /* Alert */
code span.an { color: #60a0b0; font-weight: bold; font-style: italic; } /* Annotation */
code span.at { color: #7d9029; } /* Attribute */
code span.bn { color: #40a070; } /* BaseN */
code span.bu { } /* BuiltIn */
code span.cf { color: #007020; font-weight: bold; } /* ControlFlow */
code span.ch { color: #4070a0; } /* Char */
code span.cn { color: #880000; } /* Constant */
code span.co { color: #60a0b0; font-style: italic; } /* Comment */
code span.cv { color: #60a0b0; font-weight: bold; font-style: italic; } /* CommentVar */
code span.do { color: #ba2121; font-style: italic; } /* Documentation */
code span.dt { color: #902000; } /* DataType */
code span.dv { color: #40a070; } /* DecVal */
code span.er { color: #ff0000; font-weight: bold; } /* Error */
code span.ex { } /* Extension */
code span.fl { color: #40a070; } /* Float */
code span.fu { color: #06287e; } /* Function */
code span.im { } /* Import */
code span.in { color: #60a0b0; font-weight: bold; font-style: italic; } /* Information */
code span.kw { color: #007020; font-weight: bold; } /* Keyword */
code span.op { color: #666666; } /* Operator */
code span.ot { color: #007020; } /* Other */
code span.pp { color: #bc7a00; } /* Preprocessor */
code span.sc { color: #4070a0; } /* SpecialChar */
code span.ss { color: #bb6688; } /* SpecialString */
code span.st { color: #4070a0; } /* String */
code span.va { color: #19177c; } /* Variable */
code span.vs { color: #4070a0; } /* VerbatimString */
code span.wa { color: #60a0b0; font-weight: bold; font-style: italic; } /* Warning */
</style>
<link rel="stylesheet" href="style.css" type="text/css" />
</head>
<body>
<div class="book without-animation with-summary font-size-2 font-family-1" data-basepath=".">
<div class="book-summary">
<nav role="navigation">
<ul class="summary">
<li><a href="./">EML Specification</a></li>
<li class="divider"></li>
<li class="chapter" data-level="1" data-path="eml-ecological-metadata-language.html"><a href="eml-ecological-metadata-language.html"><i class="fa fa-check"></i><b>1</b> EML: Ecological Metadata Language</a><ul>
<li class="chapter" data-level="1.1" data-path="eml-ecological-metadata-language.html"><a href="eml-ecological-metadata-language.html#getting-started"><i class="fa fa-check"></i><b>1.1</b> Getting Started</a></li>
<li class="chapter" data-level="1.2" data-path="eml-ecological-metadata-language.html"><a href="eml-ecological-metadata-language.html#about-the-eml-project"><i class="fa fa-check"></i><b>1.2</b> About the EML Project</a></li>
<li class="chapter" data-level="1.3" data-path="eml-ecological-metadata-language.html"><a href="eml-ecological-metadata-language.html#contributing"><i class="fa fa-check"></i><b>1.3</b> Contributing</a></li>
<li class="chapter" data-level="1.4" data-path="eml-ecological-metadata-language.html"><a href="eml-ecological-metadata-language.html#history"><i class="fa fa-check"></i><b>1.4</b> History</a></li>
<li class="chapter" data-level="1.5" data-path="eml-ecological-metadata-language.html"><a href="eml-ecological-metadata-language.html#older-versions-deprecated"><i class="fa fa-check"></i><b>1.5</b> Older versions (deprecated)</a></li>
<li class="chapter" data-level="1.6" data-path="eml-ecological-metadata-language.html"><a href="eml-ecological-metadata-language.html#copyright-and-license"><i class="fa fa-check"></i><b>1.6</b> Copyright and License</a></li>
<li class="chapter" data-level="1.7" data-path="eml-ecological-metadata-language.html"><a href="eml-ecological-metadata-language.html#funding-and-acknowledgements"><i class="fa fa-check"></i><b>1.7</b> Funding and Acknowledgements</a></li>
</ul></li>
<li class="chapter" data-level="2" data-path="features.html"><a href="features.html"><i class="fa fa-check"></i><b>2</b> Features</a></li>
<li class="chapter" data-level="3" data-path="contributors.html"><a href="contributors.html"><i class="fa fa-check"></i><b>3</b> Contributors</a><ul>
<li class="chapter" data-level="3.1" data-path="contributors.html"><a href="contributors.html#current-contributors"><i class="fa fa-check"></i><b>3.1</b> Current contributors</a></li>
<li class="chapter" data-level="3.2" data-path="contributors.html"><a href="contributors.html#past-contributors"><i class="fa fa-check"></i><b>3.2</b> Past contributors</a></li>
</ul></li>
<li class="chapter" data-level="4" data-path="whats-new-in-eml-2-2-0.html"><a href="whats-new-in-eml-2-2-0.html"><i class="fa fa-check"></i><b>4</b> What’s New in EML 2.2.0</a></li>
<li class="chapter" data-level="5" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html"><i class="fa fa-check"></i><b>5</b> The EML Module and Resources</a><ul>
<li class="chapter" data-level="5.1" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html#the-eml-module---a-metadata-container"><i class="fa fa-check"></i><b>5.1</b> The eml module - A metadata container</a></li>
<li class="chapter" data-level="5.2" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html#the-eml-resource-module---base-information-for-all-resources"><i class="fa fa-check"></i><b>5.2</b> The eml-resource module - Base information for all resources</a></li>
<li class="chapter" data-level="5.3" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html#the-eml-dataset-module---dataset-specific-information"><i class="fa fa-check"></i><b>5.3</b> The eml-dataset module - Dataset specific information</a></li>
<li class="chapter" data-level="5.4" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html#the-eml-literature-module---citation-specific-information"><i class="fa fa-check"></i><b>5.4</b> The eml-literature module - Citation-specific information</a><ul>
<li class="chapter" data-level="5.4.1" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html#eml-literature-module---literature-cited"><i class="fa fa-check"></i><b>5.4.1</b> eml-literature module - literature cited</a></li>
<li class="chapter" data-level="5.4.2" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html#eml-literature-module---usage-citation"><i class="fa fa-check"></i><b>5.4.2</b> eml-literature module - usage citation</a></li>
<li class="chapter" data-level="5.4.3" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html#eml-literature-module---reference-publication"><i class="fa fa-check"></i><b>5.4.3</b> eml-literature module - reference publication</a></li>
</ul></li>
<li class="chapter" data-level="5.5" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html#the-eml-software-module---software-specific-information"><i class="fa fa-check"></i><b>5.5</b> The eml-software module - Software specific information</a></li>
<li class="chapter" data-level="5.6" data-path="the-eml-module-and-resources.html"><a href="the-eml-module-and-resources.html#the-eml-protocol-module---research-protocol-specific-information"><i class="fa fa-check"></i><b>5.6</b> The eml-protocol module - Research protocol specific information</a></li>
</ul></li>
<li class="chapter" data-level="6" data-path="data-structure-modules.html"><a href="data-structure-modules.html"><i class="fa fa-check"></i><b>6</b> Data Structure Modules</a><ul>
<li class="chapter" data-level="6.1" data-path="data-structure-modules.html"><a href="data-structure-modules.html#the-eml-entity-module---entity-level-information-within-datasets"><i class="fa fa-check"></i><b>6.1</b> The eml-entity module - Entity level information within datasets</a></li>
<li class="chapter" data-level="6.2" data-path="data-structure-modules.html"><a href="data-structure-modules.html#the-eml-attribute-module---attribute-level-information-within-dataset-entities"><i class="fa fa-check"></i><b>6.2</b> The eml-attribute module - Attribute level information within dataset entities</a><ul>
<li class="chapter" data-level="6.2.1" data-path="data-structure-modules.html"><a href="data-structure-modules.html#philosophy-of-attribute-units"><i class="fa fa-check"></i><b>6.2.1</b> Philosophy of Attribute Units</a></li>
</ul></li>
<li class="chapter" data-level="6.3" data-path="data-structure-modules.html"><a href="data-structure-modules.html#the-eml-constraint-module---relationships-among-and-within-dataset-entities"><i class="fa fa-check"></i><b>6.3</b> The eml-constraint module - Relationships among and within dataset entities</a></li>
<li class="chapter" data-level="6.4" data-path="data-structure-modules.html"><a href="data-structure-modules.html#the-eml-datatable-module---logical-information-about-data-table-entities"><i class="fa fa-check"></i><b>6.4</b> The eml-dataTable module - Logical information about data table entities</a></li>
<li class="chapter" data-level="6.5" data-path="data-structure-modules.html"><a href="data-structure-modules.html#the-eml-spatialraster-module---logical-information-about-regularly-gridded-geospatial-image-data"><i class="fa fa-check"></i><b>6.5</b> The eml-spatialRaster module - Logical information about regularly gridded geospatial image data</a></li>
<li class="chapter" data-level="6.6" data-path="data-structure-modules.html"><a href="data-structure-modules.html#the-eml-spatialvector-module---logical-information-about-non-gridded-geospatial-image-data"><i class="fa fa-check"></i><b>6.6</b> The eml-spatialVector module - Logical information about non-gridded geospatial image data</a></li>
<li class="chapter" data-level="6.7" data-path="data-structure-modules.html"><a href="data-structure-modules.html#schema-for-validating-spatial-referencing-descriptions"><i class="fa fa-check"></i><b>6.7</b> Schema for validating spatial referencing descriptions</a></li>
<li class="chapter" data-level="6.8" data-path="data-structure-modules.html"><a href="data-structure-modules.html#the-eml-storedprocedure-module---data-tables-resulting-from-procedures-stored-in-a-database"><i class="fa fa-check"></i><b>6.8</b> The eml-storedProcedure module - Data tables resulting from procedures stored in a database</a></li>
<li class="chapter" data-level="6.9" data-path="data-structure-modules.html"><a href="data-structure-modules.html#the-eml-view-module---data-tables-resulting-from-a-database-query"><i class="fa fa-check"></i><b>6.9</b> The eml-view module - Data tables resulting from a database query</a></li>
</ul></li>
<li class="chapter" data-level="7" data-path="discovery-and-interpretation-modules.html"><a href="discovery-and-interpretation-modules.html"><i class="fa fa-check"></i><b>7</b> Discovery and Interpretation Modules</a><ul>
<li class="chapter" data-level="7.1" data-path="discovery-and-interpretation-modules.html"><a href="discovery-and-interpretation-modules.html#the-eml-access-module---access-control-rules-for-resources"><i class="fa fa-check"></i><b>7.1</b> The eml-access module - Access control rules for resources</a></li>
<li class="chapter" data-level="7.2" data-path="discovery-and-interpretation-modules.html"><a href="discovery-and-interpretation-modules.html#the-eml-physical-module---physical-file-format"><i class="fa fa-check"></i><b>7.2</b> The eml-physical module - Physical file format</a></li>
<li class="chapter" data-level="7.3" data-path="discovery-and-interpretation-modules.html"><a href="discovery-and-interpretation-modules.html#the-eml-party-module---people-and-organization-information"><i class="fa fa-check"></i><b>7.3</b> The eml-party module - People and organization information</a></li>
<li class="chapter" data-level="7.4" data-path="discovery-and-interpretation-modules.html"><a href="discovery-and-interpretation-modules.html#the-eml-coverage-module---geographic-temporal-and-taxonomic-extents-of-resources"><i class="fa fa-check"></i><b>7.4</b> The eml-coverage module - Geographic, temporal, and taxonomic extents of resources</a></li>
<li class="chapter" data-level="7.5" data-path="discovery-and-interpretation-modules.html"><a href="discovery-and-interpretation-modules.html#the-eml-project-module---research-context-information-for-resources"><i class="fa fa-check"></i><b>7.5</b> The eml-project module - Research context information for resources</a></li>
<li class="chapter" data-level="7.6" data-path="discovery-and-interpretation-modules.html"><a href="discovery-and-interpretation-modules.html#the-eml-methods-module---methodological-information-for-resources"><i class="fa fa-check"></i><b>7.6</b> The eml-methods module - Methodological information for resources</a></li>
</ul></li>
<li class="chapter" data-level="8" data-path="utility-modules.html"><a href="utility-modules.html"><i class="fa fa-check"></i><b>8</b> Utility Modules</a><ul>
<li class="chapter" data-level="8.1" data-path="utility-modules.html"><a href="utility-modules.html#the-eml-text-module---text-field-formatting"><i class="fa fa-check"></i><b>8.1</b> The eml-text module - Text field formatting</a></li>
<li class="chapter" data-level="8.2" data-path="utility-modules.html"><a href="utility-modules.html#the-eml-semantics-module---semantic-annotations-for-formalized-statements-about-eml-components"><i class="fa fa-check"></i><b>8.2</b> The eml-semantics module - Semantic annotations for formalized statements about EML components</a></li>
</ul></li>
<li class="chapter" data-level="9" data-path="eml-schema.html"><a href="eml-schema.html"><i class="fa fa-check"></i><b>9</b> EML Schema</a></li>
<li class="chapter" data-level="10" data-path="validation-and-content-references.html"><a href="validation-and-content-references.html"><i class="fa fa-check"></i><b>10</b> Validation and Content references</a><ul>
<li class="chapter" data-level="10.1" data-path="validation-and-content-references.html"><a href="validation-and-content-references.html#validation-rules"><i class="fa fa-check"></i><b>10.1</b> Validation rules</a></li>
<li class="chapter" data-level="10.2" data-path="validation-and-content-references.html"><a href="validation-and-content-references.html#validation-algorithm"><i class="fa fa-check"></i><b>10.2</b> Validation algorithm</a></li>
<li class="chapter" data-level="10.3" data-path="validation-and-content-references.html"><a href="validation-and-content-references.html#content-references"><i class="fa fa-check"></i><b>10.3</b> Content references</a></li>
<li class="chapter" data-level="10.4" data-path="validation-and-content-references.html"><a href="validation-and-content-references.html#eml-validity-parser"><i class="fa fa-check"></i><b>10.4</b> EML Validity Parser</a></li>
<li class="chapter" data-level="10.5" data-path="validation-and-content-references.html"><a href="validation-and-content-references.html#id-and-scope-examples"><i class="fa fa-check"></i><b>10.5</b> id and Scope Examples</a></li>
</ul></li>
<li class="chapter" data-level="11" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html"><i class="fa fa-check"></i><b>11</b> Semantic Annotation Primer</a><ul>
<li class="chapter" data-level="11.1" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#introduction"><i class="fa fa-check"></i><b>11.1</b> Introduction</a><ul>
<li class="chapter" data-level="11.1.1" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#take-home-messages"><i class="fa fa-check"></i><b>11.1.1</b> Take-home messages</a></li>
<li class="chapter" data-level="11.1.2" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#organization-of-this-document"><i class="fa fa-check"></i><b>11.1.2</b> Organization of this document</a></li>
<li class="chapter" data-level="11.1.3" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#other-conventions-and-terminology"><i class="fa fa-check"></i><b>11.1.3</b> Other Conventions and Terminology</a></li>
</ul></li>
<li class="chapter" data-level="11.2" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#semantic-annotations-in-eml-2.2.0"><i class="fa fa-check"></i><b>11.2</b> Semantic Annotations in EML 2.2.0</a><ul>
<li class="chapter" data-level="11.2.1" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#annotation-element-structure"><i class="fa fa-check"></i><b>11.2.1</b> Annotation element structure</a></li>
<li class="chapter" data-level="11.2.2" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#top-level-resource-entity-level-and-attribute-annotations"><i class="fa fa-check"></i><b>11.2.2</b> Top-level resource, entity-level, and attribute annotations</a></li>
<li class="chapter" data-level="11.2.3" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#annotations-grouped-under-the-eml-annotations-element"><i class="fa fa-check"></i><b>11.2.3</b> Annotations grouped under the EML <code><annotations></code> element</a></li>
<li class="chapter" data-level="11.2.4" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#annotations-grouped-under-additionalmetadata"><i class="fa fa-check"></i><b>11.2.4</b> Annotations grouped under <code><additionalMetadata></code></a></li>
</ul></li>
<li class="chapter" data-level="11.3" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#appendix"><i class="fa fa-check"></i><b>11.3</b> Appendix</a><ul>
<li class="chapter" data-level="11.3.1" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#semantic-triples"><i class="fa fa-check"></i><b>11.3.1</b> Semantic triples</a></li>
<li class="chapter" data-level="11.3.2" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#uris"><i class="fa fa-check"></i><b>11.3.2</b> URIs</a></li>
<li class="chapter" data-level="11.3.3" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#rdf-graphs"><i class="fa fa-check"></i><b>11.3.3</b> RDF Graphs</a></li>
<li class="chapter" data-level="11.3.4" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#check-for-logical-consistency"><i class="fa fa-check"></i><b>11.3.4</b> Check for Logical Consistency</a></li>
<li class="chapter" data-level="11.3.5" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#glossary"><i class="fa fa-check"></i><b>11.3.5</b> Glossary</a></li>
<li class="chapter" data-level="11.3.6" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#vocabularies-and-repositories-used-in-examples"><i class="fa fa-check"></i><b>11.3.6</b> Vocabularies and repositories used in examples</a></li>
<li class="chapter" data-level="11.3.7" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#additional-background-information"><i class="fa fa-check"></i><b>11.3.7</b> Additional background information</a></li>
</ul></li>
<li class="chapter" data-level="11.4" data-path="semantic-annotation-primer.html"><a href="semantic-annotation-primer.html#frequently-asked-questions"><i class="fa fa-check"></i><b>11.4</b> Frequently asked questions</a></li>
</ul></li>
<li class="chapter" data-level="12" data-path="internationalization-metadata-in-multiple-languages.html"><a href="internationalization-metadata-in-multiple-languages.html"><i class="fa fa-check"></i><b>12</b> Internationalization - Metadata in multiple languages</a></li>
<li class="chapter" data-level="13" data-path="release-notes.html"><a href="release-notes.html"><i class="fa fa-check"></i><b>13</b> Release Notes</a><ul>
<li class="chapter" data-level="13.0.1" data-path="release-notes.html"><a href="release-notes.html#section"><i class="fa fa-check"></i><b>13.0.1</b> 2.2.0</a></li>
<li class="chapter" data-level="13.0.2" data-path="release-notes.html"><a href="release-notes.html#section-1"><i class="fa fa-check"></i><b>13.0.2</b> 2.1.1</a></li>
<li class="chapter" data-level="13.0.3" data-path="release-notes.html"><a href="release-notes.html#numbers-refer-to-the-corresponding-bugzilla-bug-id-not-the-github"><i class="fa fa-check"></i><b>13.0.3</b> 2.1.0 (numbers refer to the corresponding Bugzilla bug id, not the GitHub #)</a></li>
<li class="chapter" data-level="13.0.4" data-path="release-notes.html"><a href="release-notes.html#numbers-refer-to-the-corresponding-bugzilla-bug-id-not-the-github-1"><i class="fa fa-check"></i><b>13.0.4</b> 2.0.1 (numbers refer to the corresponding Bugzilla bug id, not the GitHub #)</a></li>
<li class="chapter" data-level="13.0.5" data-path="release-notes.html"><a href="release-notes.html#numbers-refer-to-the-corresponding-bugzilla-bug-id-not-the-github-2"><i class="fa fa-check"></i><b>13.0.5</b> 2.0.0 - (numbers refer to the corresponding Bugzilla bug id, not the GitHub #)</a></li>
<li class="chapter" data-level="13.0.6" data-path="release-notes.html"><a href="release-notes.html#rc3-numbers-refer-to-the-corresponding-bugzilla-bug-id-not-the-github"><i class="fa fa-check"></i><b>13.0.6</b> 2.0.0rc3 (numbers refer to the corresponding Bugzilla bug id, not the GitHub #)</a></li>
<li class="chapter" data-level="13.0.7" data-path="release-notes.html"><a href="release-notes.html#rc2-numbers-refer-to-the-corresponding-bugzilla-bug-id-not-the-github"><i class="fa fa-check"></i><b>13.0.7</b> RC2 (numbers refer to the corresponding Bugzilla bug id, not the GitHub #)</a></li>
<li class="chapter" data-level="13.0.8" data-path="release-notes.html"><a href="release-notes.html#rc1-numbers-refer-to-the-corresponding-bugzilla-bug-id-not-the-github"><i class="fa fa-check"></i><b>13.0.8</b> RC1 (numbers refer to the corresponding Bugzilla bug id, not the GitHub #)</a></li>
<li class="chapter" data-level="13.0.9" data-path="release-notes.html"><a href="release-notes.html#beta9-fixes-"><i class="fa fa-check"></i><b>13.0.9</b> Beta9 Fixes-</a></li>
<li class="chapter" data-level="13.0.10" data-path="release-notes.html"><a href="release-notes.html#beta-8-fixes-"><i class="fa fa-check"></i><b>13.0.10</b> Beta 8 Fixes-</a></li>
<li class="chapter" data-level="13.0.11" data-path="release-notes.html"><a href="release-notes.html#beta-7-fixes-"><i class="fa fa-check"></i><b>13.0.11</b> Beta 7 Fixes-</a></li>
</ul></li>
<li class="chapter" data-level="14" data-path="about-this-site.html"><a href="about-this-site.html"><i class="fa fa-check"></i><b>14</b> About this site</a><ul>
<li class="chapter" data-level="14.1" data-path="about-this-site.html"><a href="about-this-site.html#building-the-site"><i class="fa fa-check"></i><b>14.1</b> Building the site</a></li>
<li class="chapter" data-level="14.2" data-path="about-this-site.html"><a href="about-this-site.html#deploying-the-site"><i class="fa fa-check"></i><b>14.2</b> Deploying the site</a></li>
</ul></li>
<li class="chapter" data-level="15" data-path="references.html"><a href="references.html"><i class="fa fa-check"></i><b>15</b> References</a></li>
<li class="divider"></li>
<li><a href="../">← Back to main website</a></li>
</ul>
</nav>
</div>
<div class="book-body">
<div class="body-inner">
<div class="book-header" role="navigation">
<h1>
<i class="fa fa-circle-o-notch fa-spin"></i><a href="./">Ecological Metadata Language (EML)</a>
</h1>
</div>
<div class="page-wrapper" tabindex="-1" role="main">
<div class="page-inner">
<section class="normal" id="section-">
<div id="discovery-and-interpretation-modules" class="section level1">
<h1><span class="header-section-number">7</span> Discovery and Interpretation Modules</h1>
<p>The following six modules are used to qualify the resources being
described in more detail. They are used to describe access control
rules, distribution of the metadata and data themselves, parties
associated with the resource, the geographic, temporal, and taxonomic
extents of the resource, the overall research context of the resource,
and detailed methodology used for creating the resource. Some of these
modules are imported directly into the top-level resource modules, often
in many locations in order to limit the scope of the description. For
instance, the eml-coverage module may be used for a particular column of
a dataset, rather than the entire dataset as a whole.</p>
<div id="the-eml-access-module---access-control-rules-for-resources" class="section level2">
<h2><span class="header-section-number">7.1</span> The eml-access module - Access control rules for resources</h2>
<p>The eml-access module describes the level of access that is to be
allowed or denied to a resource for a particular user or group of users,
and can be described independently for metadata and data. The eml-access
module uses a reference to a particular authentication system to
determine the set of principals (users or groups) that can be specified
in the access rules. The special principal 'public' can be used to
indicate that any user or group has access permission, thereby making it
easier to specify that anonymous access is allowed.</p>
<p>There are two mechanisms for including access control via the eml-access
module:</p>
<ol style="list-style-type: decimal">
<li><p>The top-level "eml" element may have an optional <access>
element that is used to establish the default access control for the
entire EML package. If this access element is omitted from the
document, then the package submitter should be given full access to
the package but all other users should be denied all access. To
allow the package to be publicly viewable, the EML author must
explicitly include a rule stating so. Barring the existence of a
distribution-level <access> element (see below), access to data
entities will be controlled by the package-level <access> element
in the <eml> element.</p></li>
<li><p>Exceptions for particular entity-level components of the package can
be controlled at a finer grain by using an access description in
that entity's physical/distribution tree. When access control rules
are specified at this level, they apply only to the data in the
parent distribution element, and not to the metadata. Thus, it will
control access to the content of the <inline> element, as well as
resources that are referenced by the <online/url> and
<online/connection> paths. These exceptions to access for
particular data resources are applied after the default access rules
at the package-level have been applied, so they effectively override
the default rules when they overlap.</p></li>
</ol>
<p>In previous versions of EML access rules for entity-level distribution
were contained in <additionalMetadata> sections and referenced via the
<describes> tag. Although in theory these could have referenced any
node, in application such node-level access control is problematic.
Since the most common uses of access control rules were to limit access
to specific data entities, the access tree has been placed there
explicitly in EML 2.1.0.</p>
<p>Access is specified with a choice of child elements, either <allow> or
<deny>. Within these rules, values can be assigned for each
<principal> using the <permission> element. Users given "read"
permission can view the resource; "write" allows changes to the
resource excluding changes to the access rules; "changePermission"
includes "write" plus the changing of access rules. Users allowed
"all" permissions; may do all of the above. Access to data and
metadata is affected by the order attribute of the <access> element.
It is possible for a deny rule to override an allow rule, and vice
versa. In the case where the order attribute is set to "allowFirst",
and there are rules similar to the following (with non-critical sections
deleted):</p>
<div class="sourceCode" id="cb16"><pre class="sourceCode xml"><code class="sourceCode xml"><a class="sourceLine" id="cb16-1" data-line-number="1"> <span class="kw"><deny></span></a>
<a class="sourceLine" id="cb16-2" data-line-number="2"> <span class="kw"><principal></span>public<span class="kw"></principal></span></a>
<a class="sourceLine" id="cb16-3" data-line-number="3"> <span class="kw"><permission></span>read<span class="kw"></permission></span></a>
<a class="sourceLine" id="cb16-4" data-line-number="4"> <span class="kw"></deny></span></a>
<a class="sourceLine" id="cb16-5" data-line-number="5"> <span class="kw"><allow></span></a>
<a class="sourceLine" id="cb16-6" data-line-number="6"> <span class="kw"><principal></span>uid=alice,o=NASA,dc=ecoinformatics,dc=org<span class="kw"></principal></span></a>
<a class="sourceLine" id="cb16-7" data-line-number="7"> <span class="kw"><permission></span>read<span class="kw"></permission></span></a>
<a class="sourceLine" id="cb16-8" data-line-number="8"> <span class="kw"></allow></span></a></code></pre></div>
<p>the principal "uid=alice ..." will be denied access, because it is a
member of the special "public" principal, and the deny rule is
processed second. For this allow rule to truly allow access to that
principal, the order attribute should be set to "denyFirst", and the
allow rule will override the deny rule when it is processed second.</p>
<p>An example is given below, with non-critical sections deleted:</p>
<div class="sourceCode" id="cb17"><pre class="sourceCode xml"><code class="sourceCode xml"><a class="sourceLine" id="cb17-1" data-line-number="1"> <span class="kw"><eml></span></a>
<a class="sourceLine" id="cb17-2" data-line-number="2"> <span class="kw"><access</span></a>
<a class="sourceLine" id="cb17-3" data-line-number="3"><span class="ot"> authSystem=</span><span class="st">"ldap://ldap.ecoinformatics.org:389/dc=ecoinformatics,dc=org"</span></a>
<a class="sourceLine" id="cb17-4" data-line-number="4"><span class="ot"> order=</span><span class="st">"allowFirst"</span><span class="kw">></span></a>
<a class="sourceLine" id="cb17-5" data-line-number="5"> <span class="kw"><allow></span></a>
<a class="sourceLine" id="cb17-6" data-line-number="6"> <span class="kw"><principal></span>uid=alice,o=NASA,dc=ecoinformatics,dc=org<span class="kw"></principal></span></a>
<a class="sourceLine" id="cb17-7" data-line-number="7"> <span class="kw"><permission></span>read<span class="kw"></permission></span></a>
<a class="sourceLine" id="cb17-8" data-line-number="8"> <span class="kw"><permission></span>write<span class="kw"></permission></span></a>
<a class="sourceLine" id="cb17-9" data-line-number="9"> <span class="kw"><allow></span></a>
<a class="sourceLine" id="cb17-10" data-line-number="10"> <span class="kw"></access></span></a>
<a class="sourceLine" id="cb17-11" data-line-number="11"> <span class="kw"><dataset></span></a>
<a class="sourceLine" id="cb17-12" data-line-number="12"> ...</a>
<a class="sourceLine" id="cb17-13" data-line-number="13"> ...</a>
<a class="sourceLine" id="cb17-14" data-line-number="14"> <span class="kw"><dataTable</span><span class="ot"> id=</span><span class="st">"entity123"</span><span class="kw">></span></a>
<a class="sourceLine" id="cb17-15" data-line-number="15"> ...</a>
<a class="sourceLine" id="cb17-16" data-line-number="16"> <span class="kw"><physical></span></a>
<a class="sourceLine" id="cb17-17" data-line-number="17"> ...</a>
<a class="sourceLine" id="cb17-18" data-line-number="18"> <span class="kw"><distribution></span></a>
<a class="sourceLine" id="cb17-19" data-line-number="19"> ...</a>
<a class="sourceLine" id="cb17-20" data-line-number="20"> <span class="kw"><access</span><span class="ot"> id=</span><span class="st">"access123"</span></a>
<a class="sourceLine" id="cb17-21" data-line-number="21"><span class="ot"> authSystem=</span><span class="st">"ldap://ldap.ecoinformatics.org:389/dc=ecoinformatics,dc=org"</span></a>
<a class="sourceLine" id="cb17-22" data-line-number="22"><span class="ot"> order=</span><span class="st">"allowFirst"</span><span class="kw">></span></a>
<a class="sourceLine" id="cb17-23" data-line-number="23"> <span class="kw"><deny></span></a>
<a class="sourceLine" id="cb17-24" data-line-number="24"> <span class="kw"><principal></span>uid=alice,o=NASA,dc=ecoinformatics,dc=org<span class="kw"></principal></span></a>
<a class="sourceLine" id="cb17-25" data-line-number="25"> <span class="kw"><permission></span>write<span class="kw"></permission></span></a>
<a class="sourceLine" id="cb17-26" data-line-number="26"> <span class="kw"></deny></span></a>
<a class="sourceLine" id="cb17-27" data-line-number="27"> <span class="kw"></access></span></a>
<a class="sourceLine" id="cb17-28" data-line-number="28"> <span class="kw"></distribution></span></a>
<a class="sourceLine" id="cb17-29" data-line-number="29"> <span class="kw"></physical></span></a>
<a class="sourceLine" id="cb17-30" data-line-number="30"> <span class="kw"></dataTable></span></a>
<a class="sourceLine" id="cb17-31" data-line-number="31"> <span class="kw"><dataTable</span><span class="ot"> id=</span><span class="st">"entity234"</span><span class="kw">></span></a>
<a class="sourceLine" id="cb17-32" data-line-number="32"> ...</a>
<a class="sourceLine" id="cb17-33" data-line-number="33"> <span class="kw"><physical></span></a>
<a class="sourceLine" id="cb17-34" data-line-number="34"> ...</a>
<a class="sourceLine" id="cb17-35" data-line-number="35"> <span class="kw"><distribution></span></a>
<a class="sourceLine" id="cb17-36" data-line-number="36"> ...</a>
<a class="sourceLine" id="cb17-37" data-line-number="37"> <span class="kw"><access></span></a>
<a class="sourceLine" id="cb17-38" data-line-number="38"> <span class="kw"><references></span>access123<span class="kw"></references></span></a>
<a class="sourceLine" id="cb17-39" data-line-number="39"> <span class="kw"></access></span></a>
<a class="sourceLine" id="cb17-40" data-line-number="40"> <span class="kw"></distribution></span></a>
<a class="sourceLine" id="cb17-41" data-line-number="41"> <span class="kw"></physical></span></a>
<a class="sourceLine" id="cb17-42" data-line-number="42"> <span class="kw"></dataTable></span></a>
<a class="sourceLine" id="cb17-43" data-line-number="43"> ... </a>
<a class="sourceLine" id="cb17-44" data-line-number="44"> <span class="kw"></dataset></span></a>
<a class="sourceLine" id="cb17-45" data-line-number="45"> <span class="kw"><eml></span></a></code></pre></div>
<p>In this example, the overall default access is to allow the user=alice
(but no one else) to read and write all metadata and data. However,
under "entity123" and "entity234", there is an additional rule
saying that user=alice does not have write permission. The net effect is
that Alice can read and make changes to the metadata, but cannot make
changes to the two data entities. In addition, Alice cannot change these
access rules; although the submitter can.</p>
<p>This example also shows how the eml-access module, like other modules,
may be "referenced" via the <references> tag. This allows an access
control document to be described once, and then used as a reference in
other locations within the EML document via its ID.</p>
<p>In summary, access rules can be applied in two places in an eml
document. Default access rules are established in the top <access>
element for the main eml document (e.g., "/eml/access"). These default
rules can be overridden for particular data entities by adding
additional <access> elements in the physical/distribution trees of
those entities.</p>
</div>
<div id="the-eml-physical-module---physical-file-format" class="section level2">
<h2><span class="header-section-number">7.2</span> The eml-physical module - Physical file format</h2>
<p>The eml-physical module describes the external and internal physical
characteristics of a data object as well as the information required for
its distribution. Examples of the external physical characteristics of a
data object would be the filename, size, compression, encoding methods,
and authentication of a file or byte stream. Internal physical
characteristics describe the format of the data object being described.
Both named binary or otherwise proprietary formats can be cited (e.g.,
Microsoft Access 2000), or text formats can be precisely described
(e.g., ASCII text delimited with commas). For these text formats, it
also includes the information needed to parse the data object to extract
the entity and its attributes from the data object. Distribution
information describes how to retrieve the data object. The retrieval
information can be either online (e.g., a URL or other connection
information) or offline (e.g., a data object residing on an archival
tape).</p>
<p>The eml-physical module, like other modules, may be "referenced" via
the <references> tag. This allows a physical document to be described
once, and then used as a reference in other locations within the EML
document via its ID.</p>
</div>
<div id="the-eml-party-module---people-and-organization-information" class="section level2">
<h2><span class="header-section-number">7.3</span> The eml-party module - People and organization information</h2>
<p>The eml-party module describes a responsible party and is typically used
to name the creator of a resource or metadata document. A responsible
party may be an individual person, an organization or a named position
within an organization. The eml-party module contains detailed contact
information. It is used throughout the other EML modules where detailed
contact information is needed.</p>
<p>The eml-party module, like other modules, may be "referenced" via the
<references> tag. This allows a party to be described once, and then
used as a reference in other locations within the EML document via its
ID.</p>
</div>
<div id="the-eml-coverage-module---geographic-temporal-and-taxonomic-extents-of-resources" class="section level2">
<h2><span class="header-section-number">7.4</span> The eml-coverage module - Geographic, temporal, and taxonomic extents of resources</h2>
<p>The eml-coverage module contains fields for describing the coverage of a
resource in terms of time, space, and taxonomy. These coverages
(temporal, spatial, and taxonomic) represent the extent of applicability
of the resource in those domains. The Geographic coverage section allows
for 2 means of expressing coverage on the surface of the earth: 1) via a
set of bounding coordinates that define the North, South, East and West
points in a rectangular area, optionally including a bounding altitude,
and 2) using a G-Ring polygon definition, where an irregularly shaped
area may be defined using a ordered list of latitude/longitude
coordinates. A G-Ring may also include an "inner G-Ring" that defines
one or more "cut-outs" in the area, i.e. the donut hole concept.</p>
<p>The temporal coverage section allows for the definition of either a
single date or time, or a range of dates or times. These may be
expressed as a calendar date according to the ISO 8601 Date and Time
Specification, or by using an alternate time scale, such as the geologic
time scale. Currently, EML does not have specific fields to indicate
that a data resource may be "ongoing." Two examples are data tables
that are planned to be appended in the future, or resources with complex
connection definitions (such as to a database) which may return data in
real time. It is important that EML be able to handle data from both the
"producer" and "consumer" points of view, although currently the
temporal coverage modules are designed for the latter. There is no
universally acceptable recommendation for describing "ongoing" data
within EML. Some groups have chosen to use the <alternateTimeScale>
node for the end date, with a value of "ongoing," although this
practice is not endorsed by the EML authors. A better solution could be
to use very general content for the endDate (such as only the current
year) so that the data are accurately described, and searches return
datasets as expected. A future version of EML will accommodate such data
types with coverage elements specific to their needs.</p>
<p>The taxonomic coverage section allows for detailed description of the
taxonomic extent of the dataset or resource. The taxonomic
classification consists of a recursive set of taxon rank names, their
values, and their common names. This construct allows for a taxonomic
hierarchy to be built to show the level of identification (e.g. Rank
Name = Kingdom, Rank Value = Animalia, Common Name = Animals, and so on
down the hierarchy.) The taxonomic coverage module also allows for the
definition of the classification system in cases where alternative
systems are used.</p>
<p>The eml-coverage module, like other modules, may be "referenced" via
the <references> tag. This allows the coverage extent to be described
once, and then used as a reference in other locations within the EML
document via its ID.</p>
</div>
<div id="the-eml-project-module---research-context-information-for-resources" class="section level2">
<h2><span class="header-section-number">7.5</span> The eml-project module - Research context information for resources</h2>
<p>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. 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.</p>
<p>The eml-project module, like other modules, may be "referenced" via
the <references> tag. This allows a research project to be described
once, and then used as a reference in other locations within the EML
document via its ID.</p>
</div>
<div id="the-eml-methods-module---methodological-information-for-resources" class="section level2">
<h2><span class="header-section-number">7.6</span> The eml-methods module - Methodological information for resources</h2>
<p>The eml-methods module describes the methods followed in the creation of
the dataset, including description of field, laboratory and processing
steps, sampling methods and units, quality control procedures. The
eml-methods module is used to describe the <span class="emphasis"><em>actual</em></span>
procedures that are used in the creation or the subsequent processing of
a dataset. Likewise, eml-methods is used to describe processes that have
been used to define / improve the quality of a data file, or to identify
potential problems with the data file. Note that the eml-protocol module
is intended to be used to document a <span class="emphasis"><em>prescribed</em></span>
procedure, whereas the eml-method module is used to describe procedures
that <span class="emphasis"><em>were actually performed</em></span>. The distinction is that the
use of the term "protocol" is used in the "prescriptive" sense, and
the term "method" is used in the "descriptive" sense. This
distinction allows managers to build a protocol library of well-known,
established protocols (procedures), but also document what procedure was
truly performed in relation to the established protocol. The method may
have diverged from the protocol purposefully, or perhaps incidentally,
but the procedural lineage is still preserved and understandable.</p>
</div>
</div>
</section>
</div>
</div>
</div>
<a href="data-structure-modules.html" class="navigation navigation-prev " aria-label="Previous page"><i class="fa fa-angle-left"></i></a>
<a href="utility-modules.html" class="navigation navigation-next " aria-label="Next page"><i class="fa fa-angle-right"></i></a>
</div>
</div>
<script src="libs/gitbook-2.6.7/js/app.min.js"></script>
<script src="libs/gitbook-2.6.7/js/lunr.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-search.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-sharing.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-fontsettings.js"></script>
<script src="libs/gitbook-2.6.7/js/plugin-bookdown.js"></script>
<script src="libs/gitbook-2.6.7/js/jquery.highlight.js"></script>
<script>
gitbook.require(["gitbook"], function(gitbook) {
gitbook.start({
"sharing": {
"github": false,
"facebook": true,
"twitter": true,
"google": false,
"linkedin": false,
"weibo": false,
"instapaper": false,
"vk": false,
"all": ["facebook", "google", "twitter", "linkedin", "weibo", "instapaper"]
},
"fontsettings": {
"theme": "white",
"family": "sans",
"size": 2
},
"edit": {
"link": null,
"text": null
},
"history": {
"link": null,
"text": null
},
"download": null,
"toc": {
"collapse": "section"
}
});
});
</script>
</body>
</html>