Project

General

Profile

Bug #2054 » eml.xsd.patch

Matt Jones, 06/30/2006 09:05 AM

View differences:

eml.xsd 30 Jun 2006 15:50:32 -0000 1.49
39 39
     For Details: http://knb.ecoinformatics.org/
40 40

  
41 41
        '$Author: jones $'
42
          '$Date: 2004/07/01 22:06:51 $'
43
      '$Revision: 1.48 $'
42
          '$Date: 2006/06/30 15:50:32 $'
43
      '$Revision: 1.49 $'
44 44

  
45 45
    This program is free software; you can redistribute it and/or modify
46 46
    it under the terms of the GNU General Public License as published by
......
268 268
                  </xs:appinfo>
269 269
                </xs:annotation>
270 270
              </xs:element>
271
              <xs:any processContents="lax">
271
              <xs:element name="metadata" type="xs:string" maxOccurs="1">
272 272
                <xs:annotation>
273 273
                  <xs:appinfo>
274
                    <doc:tooltip>Any Metadata</doc:tooltip>
275
                    <doc:summary>Any well-formed XML-formatted metadata may
276
                    be inserted at this location in the EML document.  If
277
                    an element inserted here contains a reference to its
278
                    namespace, and if there is an association between that
279
                    namespace and an XML Schema that can be located by the
280
                    processing application, then the processing application
281
                    must validate the metadata element.  If these conditions
282
                    are not met, then validation need not occur.
274
                    <doc:tooltip>Additional metadata</doc:tooltip>
275
                    <doc:summary>This element contains the additional
276
                    metadata that is to be included in the document.  The 
277
                    content of this field can be any well-formed XML fragment.
283 278
                    </doc:summary>
284
                    <doc:description>Any well-formed XML-formatted metadata may
285
                    be inserted at this location in the EML document.  If
286
                    an element inserted here contains a reference to its
287
                    namespace, and if there is an association between that
288
                    namespace and an XML Schema that can be located by the
289
                    processing application, then the processing application
290
                    must validate the metadata element.  If these conditions
291
                    are not met, then validation need not occur.
279
                    <doc:description>This element contains the additional
280
                    metadata to be included in the document.  This element
281
                    should be used for extending EML to include metadata
282
                    that is not already available in another part of the EML
283
                    specification, or to include site- or system-specific
284
                    extensions that are needed beyond the core metadata.  The
285
                    additional metadata contained in this field describes the
286
                    element referenced in the 'describes' element preceding it.
287
                    The content of this field is any well-formed XML fragment.
288
                    If that content contains namespace declarations, and if
289
                    the namespace declaration can be resolved to a schema
290
                    defniition, then the content will be validated against
291
                    that schema definition.  If no namespace is present,
292
                    or if no schema can be resolved, validation for this
293
                    fragment will be skipped (validation is "lax").
292 294
                    </doc:description>
295
                    <doc:example>
296
                      <![CDATA[
297
                      <embargoDate>2006-10-10</embargoDate>
298
                      ]]>
299
                    </doc:example>
293 300
                  </xs:appinfo>
294 301
                </xs:annotation>
295
              </xs:any>
302
                <xs:complexType>
303
                  <xs:sequence>
304
                    <xs:any processContents="lax">
305
                      <xs:annotation>
306
                        <xs:appinfo>
307
                          <doc:tooltip>Any Metadata</doc:tooltip>
308
                          <doc:summary>Any well-formed XML-formatted metadata
309
                          may be inserted at this location in the EML document.
310
                          If an element inserted here contains a reference
311
                          to its namespace, and if there is an association
312
                          between that namespace and an XML Schema that
313
                          can be located by the processing application,
314
                          then the processing application must validate the
315
                          metadata element.  If these conditions are not met,
316
                          then validation need not occur.
317
                          </doc:summary>
318
                          <doc:description>Any well-formed XML-formatted
319
                          metadata may be inserted at this location in the
320
                          EML document.  If an element inserted here contains
321
                          a reference to its namespace, and if there is an
322
                          association between that namespace and an XML Schema
323
                          that can be located by the processing application,
324
                          then the processing application must validate the
325
                          metadata element.  If these conditions are not met,
326
                          then validation need not occur.
327
                          </doc:description>
328
                        </xs:appinfo>
329
                      </xs:annotation>
330
                    </xs:any>
331
                  </xs:sequence>
332
                </xs:complexType>
333
              </xs:element> 
296 334
            </xs:sequence>
297 335
            <xs:attribute name="id" type="res:IDType" use="optional"/>
298 336
          </xs:complexType>
(1-1/2)