Project

General

Profile

Bug #602 » eml-physical.xsd

Owen Eddins, 09/24/2002 12:25 PM

 
1
<?xml version="1.0"?>
2
<xs:schema targetNamespace="eml://ecoinformatics.org/physical-2.0.0rc1" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:res="eml://ecoinformatics.org/resource-2.0.0rc1" xmlns:lit="eml://ecoinformatics.org/literature-2.0.0rc1" xmlns:doc="eml://ecoinformatics.org/documentation-2.0.0rc1" xmlns="eml://ecoinformatics.org/physical-2.0.0rc1">
3
  <xs:import namespace="eml://ecoinformatics.org/documentation-2.0.0rc1" schemaLocation="eml-documentation.xsd"/>
4
  <xs:import namespace="eml://ecoinformatics.org/literature-2.0.0rc1" schemaLocation="eml-literature.xsd"/>
5
  <xs:import namespace="eml://ecoinformatics.org/resource-2.0.0rc1" schemaLocation="eml-resource.xsd"/>
6
  <xs:annotation>
7
    <xs:documentation>
8
       '$RCSfile: eml-physical.xsd,v $'
9
       Copyright: 1997-2002 Regents of the University of California,
10
                            University of New Mexico, and
11
                            Arizona State University
12
        Sponsors: National Center for Ecological Analysis and Synthesis and
13
                  Partnership for Interdisciplinary Studies of Coastal Oceans,
14
                     University of California Santa Barbara
15
                  Long-Term Ecological Research Network Office,
16
                     University of New Mexico
17
                  Center for Environmental Studies, Arizona State University
18
   Other funding: National Science Foundation (see README for details)
19
                  The David and Lucile Packard Foundation
20

    
21
     For Details: http://knb.ecoinformatics.org/
22
        '$Author: cjones $'
23
          '$Date: 2002/09/16 23:40:58 $'
24
      '$Revision: 1.43 $'
25

    
26
    This program is free software; you can redistribute it and/or modify
27
    it under the terms of the GNU General Public License as published by
28
    the Free Software Foundation; either version 2 of the License, or
29
    (at your option) any later version.
30

    
31
    This program is distributed in the hope that it will be useful,
32
    but WITHOUT ANY WARRANTY; without even the implied warranty of
33
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
34
    GNU General Public License for more details.
35

    
36
    You should have received a copy of the GNU General Public License
37
    along with this program; if not, write to the Free Software
38
    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
39
    </xs:documentation>
40
    <xs:appinfo>
41
      <doc:moduleDocs>
42
        <doc:moduleName>eml-physical</doc:moduleName>
43
        <doc:moduleDescription>The eml-physical module describes the external 
44
	and internal physical characteristics of a data object as well as the
45
	information required for its distribution. Examples of the external 
46
	physical characteristics of a data object would be the filename, size,
47
	compression, encoding methods, and authentication of a file (or byte 
48
	stream) that resides on a filesystem or the name of a database table 
49
	if the data object resides in a relational database.  Internal 
50
	physical characteristics describe the format of the data object being 
51
	described.  Examples are Microsoft Access 2000, ASCII, or UTF-8.  It 
52
	also includes the information needed to parse the data object to 
53
	extract the entity and its attributes from the data object.  
54
	Distribution information describes how to retrieve the data object.
55
	The retrieval information can be either online with connection 
56
	information, a URL for example, or offline with the data object 
57
	residing on an archival tape.
58
	</doc:moduleDescription>
59
        <doc:recommendedUsage>Any data object that is being desribed by EML
60
	needs this information so the entities and attributes that reside with
61
	in the data object can be extracted.
62
        </doc:recommendedUsage>
63
        <doc:standAlone>yes</doc:standAlone>
64
      </doc:moduleDocs>
65
    </xs:appinfo>
66
  </xs:annotation>
67
  <xs:element name="physical" type="PhysicalType">
68
    <xs:annotation>
69
      <xs:appinfo>
70
        <doc:tooltip>Physical structure.</doc:tooltip>
71
        <doc:summary>Physical structure of an entity or entities.</doc:summary>
72
        <doc:description>The content model for physical is a CHOICE between
73
        "references" and all of the elements that let you describe the
74
        internal/external characteristics and distribution of a data object
75
	(e.g., dataObject, dataFormat, distribution.) A physical element can 
76
	contain a reference to an physical element defined elsewhere. Using 
77
	a reference means that the referenced physical is identical, not just 
78
	in name but identical in its complete description. 
79
	</doc:description>
80
        <doc:lineage>The eml-physical was introduced into EML 1.4 as
81
        eml-file.</doc:lineage>
82
      </xs:appinfo>
83
    </xs:annotation>
84
  </xs:element>
85
  <xs:complexType name="PhysicalType">
86
    <xs:choice>
87
      <xs:sequence>
88
        <xs:element name="dataObject">
89
          <xs:annotation>
90
            <xs:appinfo>
91
              <doc:tooltip>Data Object.</doc:tooltip>
92
              <doc:summary>External characteristics of a data object
93
		</doc:summary>
94
              <doc:description>The dataObject element is the parent element for
95
              several elements (e.g. objectName, size, authentication, compressionMethod,
96
	      encodingMethod, characterEncoding) which describe the external 
97
	      characteristics of the data object.
98
              </doc:description>
99
              <doc:lineage>Introduced in EML 2.0.</doc:lineage>
100
            </xs:appinfo>
101
          </xs:annotation>
102
          <xs:complexType>
103
            <xs:sequence>
104
              <xs:annotation>
105
                <xs:appinfo>
106
                  <doc:tooltip>Object name</doc:tooltip>
107
                  <doc:summary>A name for the physical object.</doc:summary>
108
                  <doc:description>The objectName is the a name (i.e.
109
                  identifier) for the object being considered. In many cases,
110
                  it may just be the file name on the file system where it is
111
                  stored. Or if the object is a table in a RDBMS it may be the
112
                  table name.</doc:description>
113
                  <doc:lineage>Introduced in EML 2.0.</doc:lineage>
114
                </xs:appinfo>
115
              </xs:annotation>
116
              <xs:element name="objectName" type="xs:string"/>
117
              <xs:element name="size" minOccurs="0">
118
                <xs:annotation>
119
                  <xs:appinfo>
120
                    <doc:tooltip>Data object size</doc:tooltip>
121
                    <doc:summary>Describes the physical size of the
122
                    data object.</doc:summary>
123
                    <doc:description>This element contains information of the
124
                    physical size of the entity, typically in
125
                    bytes.</doc:description>
126
                    <doc:example><![CDATA[<entitySize unit="bytes">13</entitySize>]]></doc:example>
127
                    <doc:lineage>The entitySize was introduced into EML
128
                    1.4.</doc:lineage>
129
                  </xs:appinfo>
130
                </xs:annotation>
131
                <xs:complexType>
132
                  <xs:simpleContent>
133
                    <xs:extension base="xs:string">
134
                      <xs:attribute name="unit" use="optional" default="bytes">
135
                        <xs:annotation>
136
                          <xs:appinfo>
137
                            <doc:tooltip>Unit of measurement</doc:tooltip>
138
                            <doc:summary>Unit of measurement for the entity
139
                            size, typically bytes</doc:summary>
140
                            <doc:description>This element gives the unit of
141
                            measurement for the size of the entity, and is
142
                            typically bytes.</doc:description>
143
                            <doc:example><![CDATA[<entitySize unit="bytes">13</entitySize>]]></doc:example>
144
                            <doc:lineage>The unit was introduced into EML
145
                            1.4.</doc:lineage>
146
                          </xs:appinfo>
147
                        </xs:annotation>
148
                      </xs:attribute>
149
                    </xs:extension>
150
                  </xs:simpleContent>
151
                </xs:complexType>
152
              </xs:element>
153
              <xs:element name="authentication" minOccurs="0" maxOccurs="unbounded">
154
                <xs:annotation>
155
                  <xs:appinfo>
156
                    <doc:tooltip>Authentication method</doc:tooltip>
157
                    <doc:summary>A value, typically a checksum, used to
158
                    authenticate that the bitstream delivered to the user is
159
                    identical to the original.</doc:summary>
160
                    <doc:description>This element describes authentication
161
                    procedures or techniques, typically by giving a checksum
162
                    method (e.g., MD5) and checksum value for the
163
                    bytestream.</doc:description>
164
                    <doc:example><![CDATA[<authentication method="MD5">
165
                    f5b2177ea03aea73de12da81f896fe40</authentication>]]></doc:example>
166
                    <doc:lineage>The authentication element was introduced into
167
                    EML 1.4.</doc:lineage>
168
                  </xs:appinfo>
169
                </xs:annotation>
170
                <xs:complexType>
171
                  <xs:simpleContent>
172
                    <xs:extension base="xs:string">
173
                      <xs:attribute name="method" type="xs:string" use="optional">
174
                        <xs:annotation>
175
                          <xs:appinfo>
176
                            <doc:tooltip>Authentication method</doc:tooltip>
177
                            <doc:summary>The method used to calculate an
178
                            authentication checksum.</doc:summary>
179
                            <doc:description>This element names the method used
180
                            to calculate and authentication checksum that can
181
                            be used to validate a bytestream. Typical checksum
182
                            methods include MD5 and CRC.</doc:description>
183
                            <doc:example><![CDATA[<authentication method="MD5">
184
                            f5b2177ea03aea73de12da81f896fe40</authentication>]]></doc:example>
185
                            <doc:lineage>The authentication element was
186
                            introduced into EML 1.4.</doc:lineage>
187
                          </xs:appinfo>
188
                        </xs:annotation>
189
                      </xs:attribute>
190
                    </xs:extension>
191
                  </xs:simpleContent>
192
                </xs:complexType>
193
              </xs:element>
194
              <xs:element name="compressionMethod" type="xs:string" minOccurs="0">
195
                <xs:annotation>
196
                  <xs:appinfo>
197
                    <doc:tooltip>Entity's compression method</doc:tooltip>
198
                    <doc:summary>Name of the entity's compression
199
                    method</doc:summary>
200
                    <doc:description>This element describes any compression
201
                    methods used to compress the entity, such as zip, compress,
202
                    etc.</doc:description>
203
                    <doc:lineage>The compressed element was introduced into EML
204
                    1.4.</doc:lineage>
205
                  </xs:appinfo>
206
                </xs:annotation>
207
              </xs:element>
208
              <xs:element name="encodingMethod" type="xs:string" minOccurs="0">
209
                <xs:annotation>
210
                  <xs:appinfo>
211
                    <doc:tooltip>Encoding Method</doc:tooltip>
212
                    <doc:summary>Method used for encoding the
213
                    entity</doc:summary>
214
                    <doc:description>This element describes the entity's
215
                    encoded method, such as MIME base64 encoding or binhex
216
                    encoding.</doc:description>
217
                    <doc:lineage>The encoded element was introduced into EML
218
                    1.4.</doc:lineage>
219
                  </xs:appinfo>
220
                </xs:annotation>
221
              </xs:element>
222
              <xs:element name="characterEncoding" type="xs:string" minOccurs="0">
223
                <xs:annotation>
224
                  <xs:appinfo>
225
                    <doc:tooltip>Character Encoding</doc:tooltip>
226
                    <doc:summary>Contains the name of the chracter encoding
227
                    used for the data.</doc:summary>
228
                    <doc:description>This element contains the name of the
229
                    character encoding. This is typically ASCII or UTF-8, or
230
                    one of the other common encodings.</doc:description>
231
                    <doc:example><![CDATA[<characterEncoding>UTF-8</characterEncoding>]]></doc:example>
232
                    <doc:lineage>Introduced in EML 2.0</doc:lineage>
233
                  </xs:appinfo>
234
                </xs:annotation>
235
              </xs:element>
236
            </xs:sequence>
237
          </xs:complexType>
238
        </xs:element>
239
        <xs:element name="dataFormat">
240
          <xs:annotation>
241
            <xs:appinfo>
242
              <doc:tooltip>Data format</doc:tooltip>
243
              <doc:summary>Describes the internal physical format
244
	      of a data object.</doc:summary>
245
              <doc:description>This element is the parent which is a CHOICE 
246
	      between four possible internal physical formats 
247
	      which describe the internal 
248
	      physical characteristics of the data object.  Using this 
249
	      information the user should be able construct the entity 
250
	      and attributes described in those modules. Note that this is 
251
	      the format of the
252
              physical file itself.</doc:description>
253
              <doc:lineage>The format element was introduced into EML
254
              1.4.</doc:lineage>
255
            </xs:appinfo>
256
          </xs:annotation>
257
          <xs:complexType>
258
            <xs:choice>
259
              <xs:annotation>
260
                <xs:appinfo>
261
                  <doc:tooltip>Generic binary format</doc:tooltip>
262
                  <doc:summary>Generic binary format</doc:summary>
263
                  <doc:description>Documentation for a generic binary
264
                  format</doc:description>
265
                  <doc:lineage>Introduced in EML 2.0.</doc:lineage>
266
                </xs:appinfo>
267
              </xs:annotation>
268
              <xs:element name="textFormat">
269
                <xs:complexType>
270
                  <xs:sequence>
271
                    <xs:element name="numHeaderLines" minOccurs="0"/>
272
                    <xs:element name="numPhysicalLines" type="xs:unsignedInt" minOccurs="0">
273
                      <xs:annotation>
274
                        <xs:appinfo>
275
                          <doc:tooltip>Number of physical lines</doc:tooltip>
276
                          <doc:summary>The number of physical lines in the file
277
                          spanned by a single logical data
278
                          record.</doc:summary>
279
                          <doc:description>A single logical data record may be
280
                          written over several physical lines in a file, with
281
                          no special marker to indicate the end of a record. In
282
                          such cases, it is necessary to know the number of
283
                          lines per record in order to correctly read
284
                          them.</doc:description>
285
                          <doc:example>3</doc:example>
286
                          <doc:lineage>Introduced into EML 2.0.</doc:lineage>
287
                        </xs:appinfo>
288
                      </xs:annotation>
289
                    </xs:element>
290
                    <xs:choice maxOccurs="unbounded">
291
                      <xs:element name="textFixed">
292
                        <xs:annotation>
293
                          <xs:appinfo>
294
                            <doc:tooltip>ASCII fixed delimited</doc:tooltip>
295
                            <doc:summary>Describes physical format of entities 
296
		  and attributes delimitedby special characters like commas
297
		  and spaces.</doc:summary>
298
                            <doc:description>Describes physical format of entities 
299
		  and attributes delimitedby special characters like commas
300
		  and spaces.</doc:description>
301
                            <doc:lineage>Introduced in EML 2.0.</doc:lineage>
302
                          </xs:appinfo>
303
                        </xs:annotation>
304
                        <xs:complexType>
305
                          <xs:sequence>
306
                            <xs:annotation>
307
                              <xs:appinfo>
308
                                <doc:tooltip>Number of header lines</doc:tooltip>
309
                                <doc:summary>The number of header lines in the file
310
                          for a single logical data record.
311
			  </doc:summary>
312
                                <doc:description>The number of header lines in the file
313
                          for a single logical data record.</doc:description>
314
                                <doc:example>1</doc:example>
315
                                <doc:lineage>Introduced into EML 2.0.</doc:lineage>
316
                              </xs:appinfo>
317
                              <xs:appinfo>
318
                                <doc:tooltip>Field Boundry</doc:tooltip>
319
                                <doc:summary>Describes the physical location of the
320
			  entity's attributes.</doc:summary>
321
                                <doc:description>Describes the physical location of the
322
			  entity's attributes. Includes the line number where the
323
			  field begins, start column, and field's width.
324
			  </doc:description>
325
                                <doc:lineage>Introduced into EML 2.0.</doc:lineage>
326
                              </xs:appinfo>
327
                            </xs:annotation>
328
                            <xs:element name="fieldBounds">
329
                              <xs:complexType>
330
                                <xs:sequence>
331
                                  <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
332
                                    <xs:annotation>
333
                                      <xs:appinfo>
334
                                        <doc:tooltip>Physical Line Number</doc:tooltip>
335
                                        <doc:summary>The line on which the data field
336
                                is found, when the data record is written over
337
                                more than one physical line in the
338
                                file.</doc:summary>
339
                                        <doc:description>A single logical data record
340
                                may be written over several physical lines in a
341
                                file, with no special marker to indicate the
342
                                end of a record. In such cases, the relative
343
                                location of a data field must be indicated by
344
                                both relative row and column
345
                                number.</doc:description>
346
                                        <doc:example>3</doc:example>
347
                                        <doc:lineage>Introduced into EML
348
                                2.0.</doc:lineage>
349
                                      </xs:appinfo>
350
                                    </xs:annotation>
351
                                  </xs:element>
352
                                  <xs:element name="fieldStartColumn" type="xs:long">
353
                                    <xs:annotation>
354
                                      <xs:appinfo>
355
                                        <doc:tooltip>Start column</doc:tooltip>
356
                                        <doc:summary>The starting column number for a
357
                                fixed format attribute.</doc:summary>
358
                                        <doc:description>FixedWidth fields have a set
359
                                length, thus the end of the field can always be
360
                                determined by adding the fieldWidth to the
361
                                starting column number.</doc:description>
362
                                        <doc:example>any positive integer, see example
363
                                in "delimiter" description</doc:example>
364
                                        <doc:lineage>Introduced into EML
365
                                2.0.</doc:lineage>
366
                                      </xs:appinfo>
367
                                    </xs:annotation>
368
                                  </xs:element>
369
                                  <xs:element name="fieldWidth" type="xs:unsignedLong">
370
                                    <xs:annotation>
371
                                      <xs:appinfo>
372
                                        <doc:tooltip>Field width</doc:tooltip>
373
                                        <doc:summary>FieldWidth specification for fixed
374
                                field length.</doc:summary>
375
                                        <doc:description>FixedWidth fields have a set
376
                                length, thus the end of the field can always be
377
                                determined by adding the fieldWidth to the
378
                                starting column number.</doc:description>
379
                                        <doc:example>any positive integer, see example
380
                                in "delimeter" description</doc:example>
381
                                        <doc:lineage>The fieldWidth element was
382
                                introduced into EML 1.4. Semantics changed to
383
                                work identically to the NBII DTD.</doc:lineage>
384
                                      </xs:appinfo>
385
                                    </xs:annotation>
386
                                  </xs:element>
387
                                </xs:sequence>
388
                              </xs:complexType>
389
                            </xs:element>
390
                          </xs:sequence>
391
                        </xs:complexType>
392
                      </xs:element>
393
                      <xs:element name="textDelimited">
394
                        <xs:annotation>
395
                          <xs:appinfo>
396
                            <doc:tooltip>ASCII field delimited</doc:tooltip>
397
                            <doc:summary>Describes physical format of entities 
398
		  and attributes delimitedby special characters like commas
399
		  and spaces.</doc:summary>
400
                            <doc:description>Describes physical format of entities 
401
		  and attributes delimitedby special characters like commas
402
		  and spaces.</doc:description>
403
                            <doc:lineage>Introduced in EML 2.0.</doc:lineage>
404
                          </xs:appinfo>
405
                        </xs:annotation>
406
                        <xs:complexType>
407
                          <xs:sequence>
408
                            <xs:element name="fieldDelimiter" type="xs:string">
409
                              <xs:annotation>
410
                                <xs:appinfo>
411
                                  <doc:tooltip>Attribute delimiter</doc:tooltip>
412
                                  <doc:summary>The end of the attribute (field) is
413
                          delimited by a special character called a field
414
                          delimiter.</doc:summary>
415
                                  <doc:description>
416
                          Variable width format fields (attributes) can vary
417
                          in their
418
                          field length, thus the end of the field is
419
                          delimited by a special character called a
420
                          field delimiter (typically a comma or a space).
421
                          Data sets are generally classified as fixedWidth
422
                          format or variableWidth format, but we have
423
                          determined that this is actually a per-field
424
                          classification because one may encounter
425
                          fixedWidth fields mixed together in the same
426
                          data file with variableWidth fields.
427
                          In our encoding scheme, the start of each field
428
                          is assumed to be the column after the last column
429
                          of the previous field, or the first column
430
                          if this is the first field in the dataset, unless
431
                          the starting column is explicity enumerated using the
432
                          "fieldStartColumn" element.
433
                          The end column for each field is classified
434
                          using either a special character delimeter indicated
435
                          using the filedDelimiter element,
436
                          or a fixed field length indicated by using the
437
                          "fieldWidth"
438
                          element.  The delimiter for the last field in the
439
                          data set can be omitted.
440
                          variableWidth fields can vary in their field length,
441
                          and the end of
442
                          the field is delimited by a special character
443
                          called a field delimiter, usually a comma or
444
                          a tab character.  fixedWidth fields have a set
445
                          length, and so the end of the field can always
446
                          be determined by adding the fieldWidth to the
447
                          starting column number.  Here is an example:
448
                          Assume we have the following data in a data set:
449
                          May,100aaaa,1.2,
450
                          April,200aaaa,3.4,
451
                          June,300bbbb,4.6,
452
                          The metadata indicating the physical layout of the
453
                          4 fields would include the
454
                          following:
455
                          <![CDATA[
456
                          <delimiter>,</delimiter>
457
                          <fieldWidth>3</fieldWidth>
458
                          <fieldWidth>3</fieldWidth>
459
                          <delimiter>,</delimiter>
460
                          ]]>
461
                          In a strictly fixed format file, the metadata would
462
                          be slightly different:
463
                          May100aaaa1.2
464
                          Apr200aaaa3.4
465
                          Jun300bbbb4.6
466
                          <![CDATA[
467
                            <fieldWidth>3</fieldWidth>
468
                            <fieldWidth>3</fieldWidth>
469
                            <fieldWidth>4</fieldWidth>
470
                            <fieldWidth>3</fieldWidth>
471
                          ]]>
472
                          or, one could explicitly describe the starting columns:
473
                          <![CDATA[
474
                            <fieldStartColumn>1</fieldStartColumn>
475
                            <fieldWidth>3</fieldWidth>
476
                            <fieldStartColumn>4</fieldStartColumn>
477
                            <fieldWidth>3</fieldWidth>
478
                            <fieldStartColumn>7</fieldStartColumn>
479
                            <fieldWidth>4</fieldWidth>
480
                            <fieldStartColumn>11</fieldStartColumn>
481
                            <fieldWidth>3</fieldWidth>
482
                          ]]></doc:description>
483
                                  <doc:example>comma, tab, white space,
484
                          etc.</doc:example>
485
                                  <doc:lineage>The delimiter element was introduced
486
                          into EML 1.4. Semantics changed to work identically
487
                          to the NBII DTD, and then modified to fit more
488
                          cases.</doc:lineage>
489
                                </xs:appinfo>
490
                              </xs:annotation>
491
                            </xs:element>
492
                            <xs:element name="maxRecordLength" type="xs:unsignedLong" minOccurs="0"/>
493
                            <xs:element name="quoteCharacter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
494
                              <xs:annotation>
495
                                <xs:appinfo>
496
                                  <doc:tooltip>Quote character</doc:tooltip>
497
                                  <doc:summary>Character used to quote values for
498
                          delimiter escaping</doc:summary>
499
                                  <doc:description>This element specifies a character
500
                          to be used in the entity for quoting values so that
501
                          field delimeters can be used within the value. This
502
                          basically allows delimeter "escaping". The
503
                          quoteChacter is typically a " or '.</doc:description>
504
                                  <doc:example><![CDATA[<quoteCharacter>"</quoteCharacter>]]></doc:example>
505
                                  <doc:lineage>The quoteCharacter element was taken
506
                          from the NBII standard.</doc:lineage>
507
                                </xs:appinfo>
508
                              </xs:annotation>
509
                            </xs:element>
510
                            <xs:element name="recordDelimiter" type="xs:string" minOccurs="0">
511
                              <xs:annotation>
512
                                <xs:appinfo>
513
                                  <doc:tooltip>Record delimiter character</doc:tooltip>
514
                                  <doc:summary>Character used to delimit
515
                          records.</doc:summary>
516
                                  <doc:description>This element specifies the record
517
                          delimiter character when the format is text. The
518
                          record delimiter is usually a newline (\n) on UNIX, a
519
                          carriage return (\r) on MacOS, or both (\r\n) on
520
                          Windows/DOS. Multiline records are usually delimited
521
                          with two line ending characters, for example on UNIX
522
                          it would be two newline characters
523
                          (\n\n).</doc:description>
524
                                  <doc:example><![CDATA[<recordDelimiter>\n\r</recordDelimiter>]]></doc:example>
525
                                  <doc:lineage>The recordDelimiter element was
526
                          introduced into EML 1.4.</doc:lineage>
527
                                </xs:appinfo>
528
                              </xs:annotation>
529
                            </xs:element>
530
                            <xs:element name="literalCharacter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
531
                              <xs:annotation>
532
                                <xs:appinfo>
533
                                  <doc:tooltip>Literal character</doc:tooltip>
534
                                  <doc:summary>Character used to escape other
535
                          characters</doc:summary>
536
                                  <doc:description>This element specifies a character
537
                          to be used for escaping character values so that the
538
                          following character is treated as its literal value.
539
                          This allows "escaping" for special characters like
540
                          quotes, commas, and spaces when they aren't intended
541
                          as a delimiter value. The literalCharacter is 
542
			  typicallya \.</doc:description>
543
                                  <doc:example><![CDATA[<literalCharacter>\</literalCharacter>]]></doc:example>
544
                                  <doc:lineage>Introduced in EML 2.0.</doc:lineage>
545
                                </xs:appinfo>
546
                              </xs:annotation>
547
                            </xs:element>
548
                          </xs:sequence>
549
                        </xs:complexType>
550
                      </xs:element>
551
                    </xs:choice>
552
                  </xs:sequence>
553
                </xs:complexType>
554
              </xs:element>
555
              <xs:element name="formatType">
556
                <xs:complexType>
557
                  <xs:sequence>
558
                    <xs:element name="formatName" type="xs:string">
559
                      <xs:annotation>
560
                        <xs:appinfo>
561
                          <doc:tooltip>Format Name</doc:tooltip>
562
                          <doc:summary>Name of the internal format of the
563
			  data object</doc:summary>
564
                          <doc:description>Name of the internal format of the
565
			  data object</doc:description>
566
                          <doc:example>
567
                           Microsoft Excel
568
                          </doc:example>
569
                          <doc:lineage>The formatName element was
570
                          introduced into EML 2.0</doc:lineage>
571
                        </xs:appinfo>
572
                      </xs:annotation>
573
                    </xs:element>
574
                    <xs:element name="formatVersion" type="xs:string" minOccurs="0">
575
                      <xs:annotation>
576
                        <xs:appinfo>
577
                          <doc:tooltip>Format Version</doc:tooltip>
578
                          <doc:summary>Version of the internal format of the
579
			  data object</doc:summary>
580
                          <doc:description>Version of the internal format of the
581
			  data object</doc:description>
582
                          <doc:example>
583
                           2000 (9.0.2720)
584
                          </doc:example>
585
                          <doc:lineage>The formatVersion element was
586
                          introduced into EML 2.0</doc:lineage>
587
                        </xs:appinfo>
588
                      </xs:annotation>
589
                    </xs:element>
590
                    <xs:element name="citation" type="lit:CitationType" minOccurs="0">
591
                      <xs:annotation>
592
                        <xs:appinfo>
593
                          <doc:tooltip>citation</doc:tooltip>
594
                          <doc:summary>Data object is an eml-literature document.
595
			  </doc:summary>
596
                          <doc:description>Data object conforms to the 
597
			  EML standard for citation as defined in the XML schema
598
			  for eml-literature.</doc:description>
599
                          <doc:example>
600
                           eml-literature.xml
601
                          </doc:example>
602
                          <doc:lineage>The citation element was
603
                          introduced into EML 2.0</doc:lineage>
604
                        </xs:appinfo>
605
                      </xs:annotation>
606
                    </xs:element>
607
                  </xs:sequence>
608
                </xs:complexType>
609
              </xs:element>
610
              <xs:element name="binaryRasterInfo">
611
                <xs:annotation>
612
                  <xs:appinfo>
613
                    <doc:tooltip>raster image parameters</doc:tooltip>
614
                    <doc:summary>contains binary raster data header
615
                    parameters</doc:summary>
616
                    <doc:description>The binaryRasterInfo element is a
617
                    container for various parameters used to described the
618
                    contents of binary raster image files. In this case, it is
619
                    based on a white paper on the ESRI site that describes the
620
                    header information used for BIP and BIL files ("Extendable
621
                    Image Formats for ArcView GIS 3.1 and
622
                    3.2").</doc:description>
623
                    <doc:lineage>Introduced in EML 2.0.</doc:lineage>
624
                  </xs:appinfo>
625
                </xs:annotation>
626
                <xs:complexType>
627
                  <xs:sequence>
628
                    <xs:element name="nrows" type="xs:int">
629
                      <xs:annotation>
630
                        <xs:appinfo>
631
                          <doc:tooltip>Number of rows</doc:tooltip>
632
                          <doc:summary>The number of rows in the image.
633
			  </doc:summary>
634
                          <doc:description>The number of rows in the image.
635
                          Rows are parallel to the x-axis of the map coordinate
636
                          system. There is no default.</doc:description>
637
                          <doc:example>400</doc:example>
638
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
639
                        </xs:appinfo>
640
                      </xs:annotation>
641
                    </xs:element>
642
                    <xs:element name="ncols" type="xs:int">
643
                      <xs:annotation>
644
                        <xs:appinfo>
645
                          <doc:tooltip>Number of columns</doc:tooltip>
646
                          <doc:summary>The number of columns in the image.
647
			  </doc:summary>
648
                          <doc:description>The number of columns in the image.
649
                          Columns are parallel to the y-axis of the map
650
                          coordinate system. There is no
651
                          default.</doc:description>
652
                          <doc:example>600</doc:example>
653
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
654
                        </xs:appinfo>
655
                      </xs:annotation>
656
                    </xs:element>
657
                    <xs:element name="orientation" nillable="true" minOccurs="0">
658
                      <xs:annotation>
659
                        <xs:appinfo>
660
                          <doc:tooltip>Entity's record
661
                          orientation</doc:tooltip>
662
                          <doc:summary>Specification of the binary raster
663
                          entity's record orientation.</doc:summary>
664
                          <doc:description>This element contains specification
665
                          of the binary raster entity's record orientation by
666
                          defining the element's attribute "columnorrow". The
667
                          binary raster will be column major if the raster is
668
                          to be displayed column by column from the byte
669
                          stream, or row major if it is to be displayed row by
670
                          row from the byte stream.</doc:description>
671
                          <doc:example>The valid attribute values are
672
                          "columnmajor" or "rowmajor". If the attribute is not
673
                          specified, "columnmajor" is used.</doc:example>
674
                          <doc:lineage>The orientation element was introduced
675
                          into EML 2.0</doc:lineage>
676
                        </xs:appinfo>
677
                      </xs:annotation>
678
                      <xs:complexType>
679
                        <xs:attribute name="columnOrRow" use="optional" default="columnMajor">
680
                          <xs:annotation>
681
                            <xs:appinfo>
682
                              <doc:tooltip>Attribute of orientation
683
                              element</doc:tooltip>
684
                              <doc:summary>Specification of the entity's record
685
                              orientation.</doc:summary>
686
                              <doc:description>This attribute specifies the
687
                              entity's record orientation.</doc:description>
688
                              <doc:example>The valid attribute values are
689
                              "columnmajor" or "rowmajor". If the attribute is
690
                              not specified, "columnmajor" is
691
                              used.</doc:example>
692
                              <doc:lineage>The columnorrow attribute was
693
                              introduced into EML 1.4.</doc:lineage>
694
                            </xs:appinfo>
695
                          </xs:annotation>
696
                          <xs:simpleType>
697
                            <xs:restriction base="xs:string">
698
                              <xs:enumeration value="columnMajor"/>
699
                              <xs:enumeration value="rowMajor"/>
700
                            </xs:restriction>
701
                          </xs:simpleType>
702
                        </xs:attribute>
703
                      </xs:complexType>
704
                    </xs:element>
705
                    <xs:element name="nbands" type="xs:int" minOccurs="0">
706
                      <xs:annotation>
707
                        <xs:appinfo>
708
                          <doc:tooltip>Number of Bands</doc:tooltip>
709
                          <doc:summary>The number of spectral bands in the
710
                          image.</doc:summary>
711
                          <doc:description>The number of spectral bands in the
712
                          image. The default is 1.</doc:description>
713
                          <doc:example>1</doc:example>
714
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
715
                        </xs:appinfo>
716
                      </xs:annotation>
717
                    </xs:element>
718
                    <xs:element name="nbits" type="xs:int" minOccurs="0">
719
                      <xs:annotation>
720
                        <xs:appinfo>
721
                          <doc:tooltip>Number of Bits</doc:tooltip>
722
                          <doc:summary>The number of bits per pixel per
723
                          band.</doc:summary>
724
                          <doc:description>The number of bits per pixel per
725
                          band. Acceptable values are 1, 4, 8, 16, and 32. The
726
                          default value is eight bits per pixel per band. For a
727
                          true color image with three bands (R, G, B) stored
728
                          using eight bits for each pixel in each band, nbits
729
                          equals eight and nbands equals three, for a total of
730
                          twenty-four bits per pixel. For an image with nbits
731
                          equal to one, nbands must also equal
732
                          one.</doc:description>
733
                          <doc:example>8</doc:example>
734
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
735
                        </xs:appinfo>
736
                      </xs:annotation>
737
                    </xs:element>
738
                    <xs:element name="byteorder" type="xs:string" minOccurs="0">
739
                      <xs:annotation>
740
                        <xs:appinfo>
741
                          <doc:tooltip>Byte Order</doc:tooltip>
742
                          <doc:summary>The byte order in which image pixel
743
                          values are stored.</doc:summary>
744
                          <doc:description>The byte order in which image pixel
745
                          values are stored. The byte order is important for
746
                          sixteen-bit images, with two bytes per pixel.
747
                          Acceptable values are I - Intel byte order (Silicon
748
                          Graphics, DEC Alpha, PC) Also known as little endian.
749
                          M - Motorola byte order (Sun, HP, etc.) Also known as
750
                          big-endian. The default byte order is the same as
751
                          that of the host machine executing the
752
                          software.</doc:description>
753
                          <doc:example>I or M</doc:example>
754
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
755
                        </xs:appinfo>
756
                      </xs:annotation>
757
                    </xs:element>
758
                    <xs:element name="layout" type="xs:string" minOccurs="0">
759
                      <xs:annotation>
760
                        <xs:appinfo>
761
                          <doc:tooltip>Layout</doc:tooltip>
762
                          <doc:summary>The organization of the bands in the
763
                          image file.</doc:summary>
764
                          <doc:description>The organization of the bands in the
765
                          image file. Acceptable values are bil - Band
766
                          interleaved by line. bip - Band interleaved by pixel.
767
                          bsq - Band sequential. The default layout is
768
                          bil.</doc:description>
769
                          <doc:example>bil, bip, bsq</doc:example>
770
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
771
                        </xs:appinfo>
772
                      </xs:annotation>
773
                    </xs:element>
774
                    <xs:element name="skipbytes" type="xs:string" minOccurs="0">
775
                      <xs:annotation>
776
                        <xs:appinfo>
777
                          <doc:tooltip>Skip Bytes</doc:tooltip>
778
                          <doc:summary>The number of bytes of data in the
779
                          image file to skip in order to reach the start of the
780
                          image data.</doc:summary>
781
                          <doc:description>The number of bytes of data in the
782
                          image file to skip in order to reach the start of the
783
                          image data. This keyword allows you to bypass any
784
                          existing image header information in the file. The
785
                          default value is zero bytes.</doc:description>
786
                          <doc:example>0</doc:example>
787
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
788
                        </xs:appinfo>
789
                      </xs:annotation>
790
                    </xs:element>
791
                    <xs:element name="ulxmap" type="xs:string" minOccurs="0">
792
                      <xs:annotation>
793
                        <xs:appinfo>
794
                          <doc:tooltip>upper left X map coordinate</doc:tooltip>
795
                          <doc:summary>The x-axis map coordinate of the
796
                          center of the upper-left pixel.</doc:summary>
797
                          <doc:description>The x-axis map coordinate of the
798
                          center of the upper-left pixel. If this parameter is
799
                          specified, ulymap must also be set, otherwise a
800
                          default value is used.</doc:description>
801
                          <doc:example>340000</doc:example>
802
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
803
                        </xs:appinfo>
804
                      </xs:annotation>
805
                    </xs:element>
806
                    <xs:element name="ulymap" type="xs:string" minOccurs="0">
807
                      <xs:annotation>
808
                        <xs:appinfo>
809
                          <doc:tooltip>upper left Y map coordinate</doc:tooltip>
810
                          <doc:summary>The y-axis map coordinate of the
811
                          center of the upper-left pixel.</doc:summary>
812
                          <doc:description>The y-axis map coordinate of the
813
                          center of the upper-left pixel. If you specify this
814
                          parameter, set ulxmap, too, otherwise a default value
815
                          is used.</doc:description>
816
                          <doc:example>6486666</doc:example>
817
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
818
                        </xs:appinfo>
819
                      </xs:annotation>
820
                    </xs:element>
821
                    <xs:element name="xdim" type="xs:string" minOccurs="0">
822
                      <xs:annotation>
823
                        <xs:appinfo>
824
                          <doc:tooltip>X dimension</doc:tooltip>
825
                          <doc:summary>The x-dimension of a pixel in map
826
                          units.</doc:summary>
827
                          <doc:description>The x-dimension of a pixel in map
828
                          units. If this parameter is specified, ydim must also
829
                          be set, otherwise a default value is
830
                          used.</doc:description>
831
                          <doc:example>16.665</doc:example>
832
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
833
                        </xs:appinfo>
834
                      </xs:annotation>
835
                    </xs:element>
836
                    <xs:element name="ydim" type="xs:string" minOccurs="0">
837
                      <xs:annotation>
838
                        <xs:appinfo>
839
                          <doc:tooltip>Y dimension</doc:tooltip>
840
                          <doc:summary>The y-dimension of a pixel in map
841
                          units.</doc:summary>
842
                          <doc:description>The y-dimension of a pixel in map
843
                          units. If this parameter is specified, xdim must also
844
                          be set, otherwise a default value is
845
                          used.</doc:description>
846
                          <doc:example>16.665</doc:example>
847
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
848
                        </xs:appinfo>
849
                      </xs:annotation>
850
                    </xs:element>
851
                    <xs:element name="bandrowbytes" type="xs:string" minOccurs="0">
852
                      <xs:annotation>
853
                        <xs:appinfo>
854
                          <doc:tooltip>Bytes per band per row</doc:tooltip>
855
                          <doc:summary>The number of bytes per band per
856
                          row.</doc:summary>
857
                          <doc:description>The number of bytes per band per
858
                          row. This must be an integer. This keyword is used
859
                          only with BIL files when there are extra bits at the
860
                          end of each band within a row that must be
861
                          skipped.</doc:description>
862
                          <doc:example>3</doc:example>
863
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
864
                        </xs:appinfo>
865
                      </xs:annotation>
866
                    </xs:element>
867
                    <xs:element name="totalrowbytes" type="xs:string" minOccurs="0">
868
                      <xs:annotation>
869
                        <xs:appinfo>
870
                          <doc:tooltip>Total bytes of data per row</doc:tooltip>
871
                          <doc:summary>The total number of bytes of data
872
                          per row.</doc:summary>
873
                          <doc:description>The total number of bytes of data
874
                          per row. Use totalrowbytes when there are extra
875
                          trailing bits at the end of each
876
                          row.</doc:description>
877
                          <doc:example>8</doc:example>
878
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
879
                        </xs:appinfo>
880
                      </xs:annotation>
881
                    </xs:element>
882
                    <xs:element name="bandgapbytes" type="xs:string" minOccurs="0">
883
                      <xs:annotation>
884
                        <xs:appinfo>
885
                          <doc:tooltip>Bytes between bands</doc:tooltip>
886
                          <doc:summary>The number of bytes between bands in
887
                          a BSQ format image.</doc:summary>
888
                          <doc:description>The number of bytes between bands in
889
                          a BSQ format image. The default is
890
                          zero.</doc:description>
891
                          <doc:example>1</doc:example>
892
                          <doc:lineage>Introduced in EML 2.0.</doc:lineage>
893
                        </xs:appinfo>
894
                      </xs:annotation>
895
                    </xs:element>
896
                  </xs:sequence>
897
                </xs:complexType>
898
              </xs:element>
899
            </xs:choice>
900
          </xs:complexType>
901
        </xs:element>
902
        <xs:element name="distribution" type="PhysicalDistributionType" minOccurs="0" maxOccurs="unbounded">
903
          <xs:annotation>
904
            <xs:appinfo>
905
              <doc:tooltip>Distribution Information</doc:tooltip>
906
              <doc:summary>Information on how the resource is distributed
907
              online and offline</doc:summary>
908
              <doc:description>This element provides information on how the
909
              resource is distributed online and offline. Connections to online
910
              systems can be described as URLs and as a list of relevant
911
              connection parameters.</doc:description>
912
              <doc:lineage>Derived from distribution elements in the FGDC
913
              standard.</doc:lineage>
914
            </xs:appinfo>
915
          </xs:annotation>
916
        </xs:element>
917
      </xs:sequence>
918
      <xs:element name="references" type="xs:string"/>
919
    </xs:choice>
920
    <xs:attribute name="id" type="xs:string" use="optional"/>
921
    <xs:attribute name="system" type="xs:string" use="optional"/>
922
    <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
923
  </xs:complexType>
924
  <xs:complexType name="PhysicalDistributionType">
925
    <xs:choice>
926
      <xs:choice>
927
        <xs:element name="online">
928
          <xs:annotation>
929
            <xs:appinfo>
930
              <doc:tooltip>Online Distribution Information</doc:tooltip>
931
              <doc:summary>Distribution information for accessing the
932
              resource online.</doc:summary>
933
              <doc:description>Distribution information for accessing the
934
              resource online, represented either as a URL or as a series of
935
              named parameters that are needed in order to
936
              connect. The URL field is provided for the simple cases where a
937
              file is available for download directly from a web server or
938
              other similar server and a complex connection protocol is not
939
              needed.  The connection field provides an alternative where a
940
              complex protocol needs to be named and described, along with
941
              the necessary parameters needed for the connection.
942
              </doc:description>
943
            </xs:appinfo>
944
          </xs:annotation>
945
          <xs:complexType>
946
            <xs:sequence>
947
              <xs:choice>
948
                <xs:element name="url">
949
                  <xs:annotation>
950
                    <xs:appinfo>
951
                      <doc:tooltip>Download site URL</doc:tooltip>
952
                      <doc:summary>A URL (Uniform Resource Locator) from which
953
                      this resource can be downloaded or information can be
954
                      obtained about downloading it.</doc:summary>
955
                      <doc:description>A URL (Uniform Resource Locator) from
956
                      which this resource can be downloaded or additional
957
                      information can be obtained. If accessing the URL would
958
                      directly return the data stream, then the "function"
959
                      attribute should be set to "download".  If the URL
960
                      provides further information about downloading the
961
                      object but does not directly return the data stream, then
962
                      the "function" attribute should be set to "information".
963
                      If the "function" attribute is omitted, then "download"
964
                      is implied for the URL function.
965
                      In more complex cases where a non-standard connection
966
                      must be established that complies with application
967
                      specific procedures beyond what can be described in the
968
                      simple URL, then the "connection" element should
969
                      be used instead of the URL element.</doc:description>
970
                      <doc:example>
971
                      http://data.org/getdata?id=98332</doc:example>
972
                      <doc:lineage>ISO CD 19115.3, Geographic information -
973
                      Metadata</doc:lineage>
974
                    </xs:appinfo>
975
                  </xs:annotation>
976
                  <xs:complexType>
977
                    <xs:simpleContent>
978
                      <xs:extension base="xs:anyURI">
979
                        <xs:attribute name="function" type="res:FunctionType" use="optional" default="download"/>
980
                      </xs:extension>
981
                    </xs:simpleContent>
982
                  </xs:complexType>
983
                </xs:element>
984
                <xs:element name="connection">
985
                  <xs:annotation>
986
                    <xs:appinfo>
987
                      <doc:tooltip>Connection</doc:tooltip>
988
                      <doc:summary>A description of the information needed
989
                      to make an application connection to a data service.
990
                      </doc:summary>
991
                      <doc:description>A description of the information needed
992
                      to make an application connection to a data service.
993
                      The connection starts with a connectionDefinition which
994
                      lists all of the parameters needed for the connection
995
                      and possible default values for each.  It then includes a
996
                      list of parameter values, one for each parameter, that
997
                      override the defaults for this particular connection.
998
                      One parameter element should exist for every
999
                      parameterDefinition that is present in the
1000
                      connectionDefinition, except that parameters that were
1001
                      defined with a defaultValue in their parameterDefinition
1002
                      can be ommitted from the connection and the default
1003
                      will be used. All information about how to use the
1004
                      parameters to establish a session and extract data is
1005
                      present in the connectionDefinition, possibly implicitly
1006
                      by naming a connection schemeName that is well-known.
1007
                      </doc:description>
1008
                    </xs:appinfo>
1009
                  </xs:annotation>
1010
                  <xs:complexType>
1011
                    <xs:choice>
1012
                      <xs:sequence>
1013
                        <xs:element name="connectionDefinition" type="res:ConnectionDefinitionType">
1014
                          <xs:annotation>
1015
                            <xs:appinfo>
1016
                              <doc:tooltip>Connection Definition</doc:tooltip>
1017
                              <doc:summary>Definition of the connection protocol
1018
                              to be used for this connection.</doc:summary>
1019
                              <doc:description>Definition of the connection
1020
                              protocol to be used for this connection.  The
1021
                              definition has a "scheme" which identifies the
1022
                              protocol by name, and a detailed description of
1023
                              the scheme and its required parameters.
1024
                              </doc:description>
1025
                            </xs:appinfo>
1026
                          </xs:annotation>
1027
                        </xs:element>
1028
                        <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
1029
                          <xs:annotation>
1030
                            <xs:appinfo>
1031
                              <doc:tooltip>Parameter</doc:tooltip>
1032
                              <doc:summary>A parameter to be used to make this
1033
                              connection.</doc:summary>
1034
                              <doc:description>A parameter to be used to make
1035
                              this connection. This value overrides any
1036
                              default value that may have been provided in the
1037
                              connection definition.
1038
                              </doc:description>
1039
                            </xs:appinfo>
1040
                          </xs:annotation>
1041
                          <xs:complexType>
1042
                            <xs:sequence>
1043
                              <xs:element name="name" type="xs:string">
1044
                                <xs:annotation>
1045
                                  <xs:appinfo>
1046
                                    <doc:tooltip>Parameter Name</doc:tooltip>
1047
                                    <doc:summary>Name of the parameter to be
1048
                                    used to make this connection.</doc:summary>
1049
                                    <doc:description>The name of the parameter
1050
                                    to be used to make this connection.
1051
                                    </doc:description>
1052
                                    <doc:example>hostname</doc:example>
1053
                                  </xs:appinfo>
1054
                                </xs:annotation>
1055
                              </xs:element>
1056
                              <xs:element name="value" type="xs:string">
1057
                                <xs:annotation>
1058
                                  <xs:appinfo>
1059
                                    <doc:tooltip>Parameter Value</doc:tooltip>
1060
                                    <doc:summary>The value of the parameter to
1061
                                    be used to make this connection.
1062
                                    </doc:summary>
1063
                                    <doc:description>The value of the parameter
1064
                                    to be used to make this connection. This
1065
                                    value overrides any default value that may
1066
                                    have been provided in the connection
1067
                                    definition.</doc:description>
1068
                                    <doc:example>nceas.ucsb.edu</doc:example>
1069
                                  </xs:appinfo>
1070
                                </xs:annotation>
1071
                              </xs:element>
1072
                            </xs:sequence>
1073
                          </xs:complexType>
1074
                        </xs:element>
1075
                      </xs:sequence>
1076
                      <xs:element name="references" type="xs:string">
1077
                        <xs:annotation>
1078
                          <xs:appinfo>
1079
                            <doc:tooltip>References</doc:tooltip>
1080
                            <doc:summary>The id of another connection in this
1081
                            EML document to be used to provide the connection
1082
                            information.
1083
                            </doc:summary>
1084
                            <doc:description>The id of another connection in
1085
                            this EML document to be used to provide the
1086
                            connection information. This is used instead of
1087
                            duplicating connection information when an identical
1088
                            connection needs to be used multiple times in an
1089
                            EML document.</doc:description>
1090
                          </xs:appinfo>
1091
                        </xs:annotation>
1092
                      </xs:element>
1093
                    </xs:choice>
1094
                    <xs:attribute name="id" type="xs:string" use="optional"/>
1095
                    <xs:attribute name="system" type="xs:string" use="optional"/>
1096
                    <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
1097
                  </xs:complexType>
1098
                </xs:element>
1099
              </xs:choice>
1100
            </xs:sequence>
1101
          </xs:complexType>
1102
        </xs:element>
1103
        <xs:element name="offline">
1104
          <xs:annotation>
1105
            <xs:appinfo>
1106
              <doc:tooltip>medium of the resource</doc:tooltip>
1107
              <doc:summary>the medium on which this resource is distributed,
1108
              either digitally or as hardcopy</doc:summary>
1109
              <doc:description>the medium on which this resource is distributed
1110
              digitally, such as 3.5" floppy disk, or various tape media types,
1111
              or 'hardcopy'</doc:description>
1112
              <doc:example>CD-ROM, 3.5 in. floppy disk, Zip disk</doc:example>
1113
              <doc:lineage>ISO CD 19115.3, Geographic information -
1114
              Metadata</doc:lineage>
1115
            </xs:appinfo>
1116
          </xs:annotation>
1117
          <xs:complexType>
1118
            <xs:sequence>
1119
              <xs:element name="mediumName" type="xs:string" minOccurs="0">
1120
                <xs:annotation>
1121
                  <xs:appinfo>
1122
                    <doc:tooltip>Medium name</doc:tooltip>
1123
                    <doc:summary>Name of the medium that for this resource
1124
                    distribution</doc:summary>
1125
                    <doc:description>Name of the medium on which this resource
1126
                    is distributed. Can be various digital media such as tapes
1127
                    and disks, or printed media which can collectively be
1128
                    termed 'hardcopy'.</doc:description>
1129
                    <doc:example>Tape, 3.5 inch Floppy Disk,
1130
                    hardcopy</doc:example>
1131
                    <doc:lineage>ISO CD 19115.3, Geographic information -
1132
                    Metadata</doc:lineage>
1133
                  </xs:appinfo>
1134
                </xs:annotation>
1135
              </xs:element>
1136
              <xs:element name="mediumDensity" type="xs:string" minOccurs="0">
1137
                <xs:annotation>
1138
                  <xs:appinfo>
1139
                    <doc:tooltip>density of the digital medium</doc:tooltip>
1140
                    <doc:summary>the density of the digital medium if this is
1141
                    relevant.</doc:summary>
1142
                    <doc:description>the density of the digital medium if this
1143
                    is relevant. Used mainly for floppy disks or
1144
                    tape.</doc:description>
1145
                    <doc:example>High Density (HD), Double Density
1146
                    (DD)</doc:example>
1147
                    <doc:lineage>ISO CD 19115.3, Geographic information -
1148
                    Metadata</doc:lineage>
1149
                  </xs:appinfo>
1150
                </xs:annotation>
1151
              </xs:element>
1152
              <xs:element name="mediumDensityUnits" type="xs:string" minOccurs="0">
1153
                <xs:annotation>
1154
                  <xs:appinfo>
1155
                    <doc:tooltip>units of a numerical density</doc:tooltip>
1156
                    <doc:summary>a numerical density's units</doc:summary>
1157
                    <doc:description>if a density is given numerically, the
1158
                    units should be given here.</doc:description>
1159
                    <doc:example>B/cm</doc:example>
1160
                    <doc:lineage>ISO CD 19115.3, Geographic information -
1161
                    Metadata</doc:lineage>
1162
                  </xs:appinfo>
1163
                </xs:annotation>
1164
              </xs:element>
1165
              <xs:element name="mediumVolume" type="xs:string" minOccurs="0">
1166
                <xs:annotation>
1167
                  <xs:appinfo>
1168
                    <doc:tooltip>storage volume</doc:tooltip>
1169
                    <doc:summary>total volume of the storage
1170
                    medium</doc:summary>
1171
                    <doc:description>the total volume of the storage medium on
1172
                    which this resource is shipped.</doc:description>
1173
                    <doc:example>650 MB</doc:example>
1174
                    <doc:lineage>ISO CD 19115.3, Geographic information -
1175
                    Metadata</doc:lineage>
1176
                  </xs:appinfo>
1177
                </xs:annotation>
1178
              </xs:element>
1179
              <xs:element name="mediumFormat" type="xs:string" minOccurs="0" maxOccurs="unbounded">
1180
                <xs:annotation>
1181
                  <xs:appinfo>
1182
                    <doc:tooltip>medium format</doc:tooltip>
1183
                    <doc:summary>format of the medium on which the resource is
1184
                    shipped.</doc:summary>
1185
                    <doc:description>the file system format of the medium on
1186
                    which the resource is shipped</doc:description>
1187
                    <doc:example>NTFS, FAT32, EXT2, QIK80</doc:example>
1188
                    <doc:lineage>ISO CD 19115.3, Geographic information -
1189
                    Metadata</doc:lineage>
1190
                  </xs:appinfo>
1191
                </xs:annotation>
1192
              </xs:element>
1193
              <xs:element name="mediumNote" type="xs:string" minOccurs="0">
1194
                <xs:annotation>
1195
                  <xs:appinfo>
1196
                    <doc:tooltip>note about the media</doc:tooltip>
1197
                    <doc:summary>note about the media</doc:summary>
1198
                    <doc:description>any additional pertinent information about
1199
                    the media</doc:description>
1200
                    <doc:lineage>ISO CD 19115.3, Geographic information -
1201
                    Metadata</doc:lineage>
1202
                  </xs:appinfo>
1203
                </xs:annotation>
1204
              </xs:element>
1205
            </xs:sequence>
1206
          </xs:complexType>
1207
        </xs:element>
1208
        <xs:element name="inline">
1209
          <xs:complexType>
1210
            <xs:sequence>
1211
              <xs:any maxOccurs="unbounded"/>
1212
            </xs:sequence>
1213
          </xs:complexType>
1214
        </xs:element>
1215
      </xs:choice>
1216
      <xs:element name="references" type="xs:string"/>
1217
    </xs:choice>
1218
    <xs:attribute name="id" type="xs:string" use="optional"/>
1219
    <xs:attribute name="system" type="xs:string" use="optional"/>
1220
    <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
1221
  </xs:complexType>
1222
</xs:schema>
(1-1/3)