source: TI01-discovery/trunk/schema/numsim/NumSim.xsd @ 2977

Subversion URL: http://proj.badc.rl.ac.uk/svn/ndg/TI01-discovery/trunk/schema/numsim/NumSim.xsd@2977
Revision 2977, 26.3 KB checked in by lawrence, 12 years ago (diff)

Version 10-01 of NumSim - major syntax changes, minor semantic changes!

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<xs:schema xmlns:moles="http://ndg.nerc.ac.uk/moles" xmlns:xs="http://www.w3.org/2001/XMLSchema"
3    xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:numsim="http://ndg.nerc.ac.uk/numsim"
4    targetNamespace="http://ndg.nerc.ac.uk/numsim" attributeFormDefault="unqualified"
5    elementFormDefault="qualified">
6    <!-- Note the change to elementFormDefault, and consequences throughout. Should simplify validation! -->
7    <xs:annotation>
8        <xs:documentation>This is V010-01 (BNL, 2007-10-29) Substantial changes at V009 have mostly
9            been backed out. V010 changes are noted with respect to V00805.</xs:documentation>
10        <xs:documentation>Revision History: v00801, 2007-04-25, Phil Bentley, Proposed syntax
11            changes to follow GML 'in-house' style. v00802, 2007-05-31, Phil Bentley, Inserted
12            comments and prettified. v00803, 2007-07-06, Phil Bentley, Added version attribute to
13            CodeBaseType definition. v00804, 2007-07-18, Phil Bentley, Added IPCC SRES A1FI to
14            BoundaryConditionCodelist. v00805, 2007-07-30, Phil Bentley, Added mandatory name
15            element to ExperimentType.</xs:documentation>
16        <xs:documentation>Previous Version: Bryan Lawrence, Feb 20 2007, May 10th, 2006</xs:documentation>
17        <xs:documentation>The expectation is that this schema will be used initially by import into
18            discovery records (ideally ISO19115 based). While such discovery records already include
19            adequate possibilities to include free text information and/or URI references which
20            would allow such discrimination for a human reader, they do not allow the construction
21            of sensible automatic discriminants, which would allow a software agent to identify, for
22            example, all simulation datasets based on the IPCC SRESA1 forcing specification by the
23            HADCM3 model. Such a software agent is necessary to provide meaningful discovery
24            services on an archive holding multiple simulation datasets, and thus, there is a
25            requirement to build information structures to support such software agents. The NumSim
26            schema provides a minimum set of such metadata structures aimed at supporting the widest
27            possible set of simulation codes. It is expected that more detailed discipline specific
28            metadata schema will exist, such as the Numerical Model Metadata Suite (hereafter the
29            NMM). Where such schema and instances exist, it is desirable that the NumSim instances
30            are automatically generated from the more detailed metadata.</xs:documentation>
31        <xs:documentation>The NumSim schema exists in a context where NumSim compliant xml metadata
32            is to included in a document conforming to an (extensible) parent schema. That parent
33            schema is assumed to have adequate tags to fully describe the data produced by the
34            simulation, the point of the NumSim metadata is to discriminate between such datasets,
35            as a consequence all dataset description is offloaded to the parent schema, but there
36            are some tags which might appear in both the parent and the NumSim schema. In such a
37            case, the scope of the tag in the NumSim schema is simply the scope of the parent
38            element, while the scope of the tag in the parent document should be assumed to be
39            either that of the parent element, or in regard to the data, not the simulation. (For
40            example, reference lists may appear in multiple places in a discovery document, but
41            their scope and applicability is related to where they appear. By doing this it is
42            possible to search for datasets created by simulations with a particular model component
43            which was described in a particular reference.</xs:documentation>
44        <xs:documentation>The simulated element is intended to appear as part of a dataset
45            description, and is used to discriminate between differing simulations of the same
46            phenomena. There are essentially three different cases where it is expected be used, and
47            for which it has been designed: (1) Where the dataset consists of one realization of the
48            simulated phenomena (a single integration of a numerical code). (2) Where the dataset
49            consists of multiple realizations of the phenomena (an ensemble), and (3) Where the
50            dataset consists of a single realization of the simulated phenomena, but where that
51            realization has been generated from an ensemble average (an ensemble “climatology”).</xs:documentation>
52        <xs:documentation>There are a number of schema which are imported here, copies of which are
53            loaded into a directory of schema. These include xlinks.xsd and a number of draft
54            ISO19139 schema components.</xs:documentation>
55    </xs:annotation>
56    <xs:import namespace="http://www.w3.org/1999/xlink"/>
57    <xs:import namespace="http://ndg.nerc.ac.uk/moles"
58        schemaLocation="http://ndg.nerc.ac.uk/schema/ndgmetadata1.3.3.xsd"/>
59    <!-- -->
60    <!-- Definition of the xlink attribute group. -->
61    <!-- -->
62    <xs:attributeGroup name="xlink">
63        <xs:annotation>
64            <xs:documentation>The attributes are those of a hyperlink, with the addition of a role
65                which we might later want to control in a vocabulary.</xs:documentation>
66            <!--Modified in V010-01 to use xs:date-->
67        </xs:annotation>
68        <xs:attribute ref="xlink:href" use="required"/>
69        <xs:attribute ref="xlink:title" use="required"/>
70        <xs:attribute ref="xlink:role" use="optional"/>
71        <xs:attribute name="dateOfCitation" type="xs:date" use="optional"/>
72    </xs:attributeGroup>
73    <!-- -->
74    <!-- Definition of the dictionaryEntryType -->
75    <!-- New in V010-01 -->
76    <!--  -->
77    <xs:complexType name="dictionaryEntryType" mixed="true">
78        <xs:annotation>
79            <xs:documentation>Provides a comma separated list of keywords from an external
80                controlled vocabulary</xs:documentation>
81        </xs:annotation>
82        <xs:all>
83            <xs:element name="dictionary" type="xs:anyURI" minOccurs="1" maxOccurs="1"/>
84        </xs:all>
85    </xs:complexType>
86    <!-- -->
87    <!-- Definition of the RelationshipType. -->
88    <!-- -->
89    <xs:complexType name="RelationshipType">
90        <xs:annotation>
91            <xs:documentation>Used for any relationships.</xs:documentation>
92            <!-- Modified in V010-01 to provide alternative controlled vocabulary to a description type which has
93            been decremented to a simple textstring. Strongly prefer using the controlled vocabulary! -->
94        </xs:annotation>
95        <xs:choice>
96            <xs:element name="description" minOccurs="1" maxOccurs="1" type="xs:string"/>
97            <xs:element name="relationship" minOccurs="1" maxOccurs="unbounded"
98                type="numsim:RelatedToCodelist"/>
99        </xs:choice>
100        <xs:attributeGroup ref="numsim:xlink"/>
101    </xs:complexType>
102    <!-- -->
103    <!-- Definition of the RelatedToCodelist -->
104    <!-- All new in V010 -->
105    <!-- -->
106    <xs:simpleType name="RelatedToCodelist">
107        <xs:annotation>
108            <xs:documentation>This the controlled vocabulary for the various relationships encoded
109                in links. It should correspond to the content at C601 in the vocab server, where
110                full definitions exist. See http://vocab.ndg.nerc.ac.uk. .</xs:documentation>
111        </xs:annotation>
112        <xs:restriction base="xs:string">
113            <xs:enumeration value="earlierVersionOf"/>
114            <xs:enumeration value="derivedVersionOf"/>
115            <xs:enumeration value="componentOf"/>
116            <xs:enumeration value="subcomponentOf"/>
117            <xs:enumeration value="variantOf"/>
118            <xs:enumeration value="similarTo"/>
119            <xs:enumeration value="activityOf"/>
120            <xs:enumeration value="successorTo"/>
121        </xs:restriction>
122    </xs:simpleType>
123    <!-- -->
124    <!-- Definition of the ContentType -->
125    <!-- ContentType introduced at V010-01 to bundle xhtml children into one element for easier parsing to html -->
126    <!-- -->
127    <xs:complexType name="ContentType" mixed="true">
128        <xs:annotation>
129            <xs:documentation>Intended to allow mixed text and xhtml</xs:documentation>
130        </xs:annotation>
131        <xs:sequence>
132            <xs:any namespace="http://www.w3.org/1999/xhtml" minOccurs="0" maxOccurs="unbounded"
133                processContents="lax"/>
134        </xs:sequence>
135    </xs:complexType>
136    <!-- Definition of the DescriptionType. -->
137    <!-- Note the addition of optional keywords at V010-01 -->
138    <!-- -->
139    <xs:complexType name="DescriptionType" mixed="false">
140        <xs:annotation>
141            <xs:documentation>Modified in V010-01 to use the new RelationshipType, and to ensure
142                that the content was split out (to make handling the xhtml
143            easier.</xs:documentation>
144        </xs:annotation>
145        <xs:sequence>
146            <xs:element name="contents" type="numsim:ContentType" minOccurs="0" maxOccurs="1"/>
147            <xs:element name="keywords" type="numsim:dictionaryEntryType" minOccurs="0"
148                maxOccurs="1"/>
149            <xs:element name="relatedTo" type="numsim:RelationshipType" minOccurs="0"
150                maxOccurs="unbounded"/>
151        </xs:sequence>
152    </xs:complexType>
153    <!-- -->
154    <!-- Definition of the ReferenceListType. -->
155    <!-- -->
156    <xs:complexType name="ReferenceListType">
157        <!-- Modified in V010-01 to remove gmd:citation for the sake of validation etc, in doing so, we've introduced
158            a referenceType which can have an explicit URLs via an xlink and which uses mixed content -->
159        <xs:sequence>
160            <xs:element name="reference" type="numsim:ReferenceType" minOccurs="1"
161                maxOccurs="unbounded"/>
162        </xs:sequence>
163    </xs:complexType>
164    <!--- -->
165    <!-- Definition of the reference type -->
166    <!-- Basically the same as the content type, but with attributes of a link and a link type attribute -->
167    <!--  -->
168    <xs:complexType name="ReferenceType" mixed="true">
169        <xs:annotation>
170            <xs:documentation>Used for a human readable reference string. The attributes can be used
171                to provide a clickable link where appropriate (and identify the type uri/url as
172                well). Supports mixed text and xhtml</xs:documentation>
173        </xs:annotation>
174        <xs:sequence>
175            <xs:any namespace="http://www.w3.org/1999/xhtml" minOccurs="0" maxOccurs="unbounded"
176                processContents="lax"/>
177        </xs:sequence>
178        <xs:attribute name="uriScheme"/>
179        <xs:attributeGroup ref="numsim:xlink"/>
180    </xs:complexType>
181
182    <!-- -->
183    <!-- Definition of the ControlledParameterListType. -->
184    <!-- -->
185    <xs:complexType name="ControlledParameterListType">
186        <!-- Modified at V010-01 to make explicit the notion that controlled parameters can be assembled from multiple lists (it was always implicit)-->
187        <xs:sequence>
188            <xs:element name="namespaceURI" type="xs:anyURI" minOccurs="1" maxOccurs="unbounded">
189                <xs:annotation>
190                    <xs:documentation>Rather than rely on including xml namespaces, which can be
191                        done in the element values below, we've also allowed an explicitly labelled
192                        link to such namespaces, and to namespaces which are not XML
193                    namespaces.</xs:documentation>
194                </xs:annotation>
195            </xs:element>
196            <xs:element name="value" type="xs:string" minOccurs="1" maxOccurs="unbounded"/>
197        </xs:sequence>
198    </xs:complexType>
199    <!-- -->
200    <!-- Definition of the InitialConditionCodelist. -->
201    <!-- Extended at V010-01 -->
202    <!-- -->
203    <xs:simpleType name="InitialConditionCodelist">
204        <xs:restriction base="xs:string">
205            <xs:enumeration value="Objective Analysis"/>
206            <xs:enumeration value="Assimilation Analysis"/>
207            <xs:enumeration value="Unknown"/>
208            <xs:enumeration value="Climatology"/>
209            <xs:enumeration value="Random"/>
210            <!-- New in V010-01-->
211            <xs:enumeration value="PreviousIntegration"/>
212        </xs:restriction>
213    </xs:simpleType>
214    <!-- -->
215    <!-- Definition of the ModelComponentCodelist. -->
216    <!-- -->
217    <xs:simpleType name="ModelComponentCodelist">
218        <xs:annotation>
219            <xs:documentation>This the controlled vocabulary for the various model sub components
220                which might be able to run independently but could be coupled.</xs:documentation>
221        </xs:annotation>
222        <xs:restriction base="xs:string">
223            <xs:enumeration value="Atmosphere"/>
224            <xs:enumeration value="Ocean"/>
225            <xs:enumeration value="Cryosphere"/>
226            <xs:enumeration value="LandSurface"/>
227            <xs:enumeration value="Chemistry"/>
228            <xs:enumeration value="Aerosol"/>
229            <xs:enumeration value="Coupler"/>
230            <!-- New in V010-01-->
231            <xs:enumeration value="CarbonCycle"/>
232            <xs:enumeration value="RadiationScheme"/>
233            <xs:enumeration value="BoundaryLayer"/>
234            <xs:enumeration value="ConvectionScheme"/>
235            <xs:enumeration value="GravityWaves"/>
236            <xs:enumeration value="CloudScheme"/>
237            <xs:enumeration value="PrecipitationScheme"/>
238            <xs:enumeration value="AdvectionScheme"/>
239            <xs:enumeration value="DiffusionScheme"/>
240            <xs:enumeration value="AerosolScheme"/>
241            <xs:enumeration value="RiverScheme"/>
242            <xs:enumeration value="Filtering"/>
243            <xs:enumeration value="MixedLayerScheme"/>
244            <xs:enumeration value="OceanStraitScheme"/>
245        </xs:restriction>
246    </xs:simpleType>
247
248    <!-- -->
249    <!-- Definition of the ModelCategoryCodelist. -->
250    <!-- -->
251    <xs:simpleType name="ModelCategoryCodelist">
252        <xs:annotation>
253            <xs:documentation>This the controlled vocabulary that categorises how the model is set
254                up</xs:documentation>
255        </xs:annotation>
256        <xs:restriction base="xs:string" id="NumSim_ModelCategories_007">
257            <xs:enumeration value="GCM"/>
258            <xs:enumeration value="Standalone"/>
259            <xs:enumeration value="Idealised"/>
260            <xs:enumeration value="Energy Balance"/>
261            <xs:enumeration value="Assimilation"/>
262            <xs:enumeration value="Beta-plane"/>
263            <xs:enumeration value="Aqua-planet"/>
264            <xs:enumeration value="Column Mean"/>
265            <xs:enumeration value="Slab"/>
266            <xs:enumeration value="Trajectory"/>
267            <!-- New in V010-01-->
268            <xs:enumeration value="hydrostatic"/>
269            <xs:enumeration value="non-hydrostatic"/>
270        </xs:restriction>
271    </xs:simpleType>
272    <!-- -->
273    <!-- Definition of the BoundaryConditionCodelist. -->
274    <!-- -->
275    <xs:simpleType name="BoundaryConditionCodelist">
276        <xs:annotation>
277            <xs:documentation>This the controlled vocabulary for Forcing
278            Specifications</xs:documentation>
279        </xs:annotation>
280        <xs:restriction base="xs:string" id="NumSim_BoundaryConditionTypes_007">
281            <xs:enumeration value="IPCC SRES A1"/>
282            <xs:enumeration value="IPCC SRES A2"/>
283            <xs:enumeration value="IPCC SRES B1"/>
284            <xs:enumeration value="IPCC SRES B2"/>
285            <xs:enumeration value="IPCC SRES A1FI"/>
286            <xs:enumeration value="IS92A"/>
287            <xs:enumeration value="Preindustrial"/>
288            <xs:enumeration value="Present Day"/>
289            <xs:enumeration value="Double Preindustrial"/>
290            <xs:enumeration value="Double Present Day"/>
291            <xs:enumeration value="Background"/>
292            <xs:enumeration value="Historical"/>
293            <xs:enumeration value="% per annum increase"/>
294            <xs:enumeration value="Lateral Boundary Global Model"/>
295            <xs:enumeration value="User Specified"/>
296        </xs:restriction>
297    </xs:simpleType>
298    <!-- -->
299    <!-- Definition of the EnsembleTypeCodelist. -->
300    <!-- -->
301    <xs:simpleType name="EnsembleTypeCodelist">
302        <xs:annotation>
303            <xs:documentation>This the controlled vocabulary for the types of ensemble. Note that a
304                Grand ensemble is a combination of two or more other ensemble
305            types.</xs:documentation>
306        </xs:annotation>
307        <xs:restriction base="xs:string">
308            <xs:enumeration value="Initial Condition"/>
309            <xs:enumeration value="Perturbed Physics"/>
310            <xs:enumeration value="Arbitrary Collection"/>
311            <xs:enumeration value="Single Model"/>
312            <xs:enumeration value="Multiple Model"/>
313            <xs:enumeration value="Multiple Forcing"/>
314            <xs:enumeration value="Grand"/>
315        </xs:restriction>
316    </xs:simpleType>
317
318    <!-- -->
319    <!-- Definition of the InitialConditionType. -->
320    <!-- -->
321    <xs:complexType name="InitialConditionType" mixed="false">
322        <xs:annotation>
323            <xs:documentation>Multiple initial condition elements can appear to cover how different
324                parts of the model system were initialized. If present, the main requirement is that
325                the initial condition be described in the description element and those parameters
326                which are controlled by the initial condition be identified if possible. Failing a
327                description (or as well as) the type attribute can identify the sort of initial
328                condition from the InitialConditionTypes controlled vocabulary.</xs:documentation>
329            <xs:documentation>Where the initial condition is in fact a perturbed version of the
330                “real” values for the starting time (perhaps as part of an ensemble), the perturbed
331                Boolean attribute can be set true (the default is false). Where the perturbation is
332                physically meaningful (for example, using singular vectors), this can be indicated
333                in the description.</xs:documentation>
334        </xs:annotation>
335        <xs:sequence>
336            <xs:element name="description" type="numsim:DescriptionType" minOccurs="0" maxOccurs="1"/>
337            <xs:element name="controlledParameters" type="numsim:ControlledParameterListType"
338                minOccurs="0" maxOccurs="unbounded"/>
339            <xs:element name="references" type="numsim:ReferenceListType" minOccurs="0"
340                maxOccurs="1"/>
341        </xs:sequence>
342        <xs:attribute name="type" type="numsim:InitialConditionCodelist"/>
343        <xs:attribute name="perturbed" type="xs:boolean"/>
344    </xs:complexType>
345
346    <!-- -->
347    <!-- Definition of the BoundaryConditionType. -->
348    <!-- -->
349    <xs:complexType name="BoundaryConditionType">
350        <xs:sequence>
351            <xs:element name="description" type="numsim:DescriptionType" minOccurs="1"/>
352            <xs:element name="controlledParameters" type="numsim:ControlledParameterListType"
353                minOccurs="0" maxOccurs="unbounded"/>
354            <xs:element name="references" type="numsim:ReferenceListType" minOccurs="0"
355                maxOccurs="1"/>
356            <xs:element name="boundaryDataset" type="numsim:RelationshipType" minOccurs="0"
357                maxOccurs="1"/>
358        </xs:sequence>
359        <xs:attribute name="type" type="numsim:BoundaryConditionCodelist"/>
360    </xs:complexType>
361
362    <!-- -->
363    <!-- Definition of the EnsembleDetailsType. -->
364    <!-- -->
365    <xs:complexType name="EnsembleDetailsType">
366        <xs:annotation>
367            <xs:documentation>If not present, the default assumption should be that the simulation
368                is a single realization. If present, the attribute can identify that the data
369                represents an ensemble climatology by setting the Boolean EnsembleStatistics to
370                True, otherwise the default is that the data are multiple realizations. This element
371                may include multiple EnsembleType elements, which are drawn from the EnsembleTypes
372                controlled vocabulary: o Initial Condition o Perturbed Physics o Arbitrary
373                Collection o Single Mode o Multiple Model o Multiple Forcing o GrandEnsemble (any
374                combination of the others, in which case the exact combination should be recorded in
375                the EnsembleDescription element - itself including both a textural component and an
376                optional related URI for more information). If only one integration is included,
377                just one model element should be used. Whether an ensemble or a single integration
378                is described by this element, multiple boundary and initial conditions elements are
379                allowed (in the case of single integrations to support multiple components of the
380                model having different initial and/or boundary conditions, and for ensembles to
381                potentially include multiple boundary conditions associated with multiple forcings).
382                (Note that more complex ensemble statistics, such as, for example probability
383                distribution functions, are likely to be more fully described by the data
384                attributes, this attribute is simply used to aid users in finding ensemble averages
385                and avoid them being mistaken for instances and used
386            inappropriately).</xs:documentation>
387        </xs:annotation>
388        <xs:sequence>
389            <xs:element name="description" type="numsim:DescriptionType" minOccurs="0" maxOccurs="1"/>
390            <!-- Note name change from type to ensembleType at V010-01 -->
391            <xs:element name="ensembleType" type="numsim:EnsembleTypeCodelist" minOccurs="1"
392                maxOccurs="unbounded"/>
393        </xs:sequence>
394        <xs:attribute name="ensembleStatistics" type="xs:boolean" default="0"/>
395    </xs:complexType>
396
397    <!-- -->
398    <!-- Definition of the ModelType. -->
399    <!-- -->
400    <xs:complexType name="ModelType">
401        <xs:annotation>
402            <xs:documentation>The NS_Model complex type is used to both as the type of the overall
403                model description (forming a compulsory element within the NumSIm element itself),
404                and as the type of any sub component of that model.</xs:documentation>
405        </xs:annotation>
406        <xs:sequence>
407            <xs:element name="name" type="xs:string" minOccurs="1" maxOccurs="1"/>
408            <xs:element name="id" type="moles:dgMetadataIDType" minOccurs="0" maxOccurs="1"/>
409            <xs:element name="category" type="numsim:ModelCategoryCodelist" minOccurs="0"
410                maxOccurs="unbounded"/>
411            <xs:element name="componentType" type="numsim:ModelComponentCodelist" minOccurs="0"
412                maxOccurs="unbounded"/>
413            <xs:element name="description" type="numsim:DescriptionType" minOccurs="0" maxOccurs="1"/>
414            <xs:element name="resolution" type="numsim:DescriptionType" minOccurs="0" maxOccurs="1"/>
415            <xs:element name="relatedModel" type="numsim:RelationshipType" minOccurs="0"
416                maxOccurs="unbounded"/>
417            <xs:element name="references" type="numsim:ReferenceListType" minOccurs="0"
418                maxOccurs="1"/>
419            <xs:element name="component" type="numsim:ModelType" minOccurs="0" maxOccurs="unbounded"
420            />
421        </xs:sequence>
422    </xs:complexType>
423
424    <!-- -->
425    <!-- Definition of the ExperimentType. -->
426    <!-- -->
427    <xs:complexType name="ExperimentType">
428        <xs:annotation>
429            <xs:documentation>Used to define how the model has been used. Note that the
430                NS_ParentEnsemble can be used when an integration is available as in independant
431                dataset to point back to the parent ensemble dataset.</xs:documentation>
432        </xs:annotation>
433        <xs:sequence>
434            <xs:element name="name" type="xs:string"/>
435            <xs:element name="id" type="moles:dgMetadataIDType" minOccurs="1" maxOccurs="1"/>
436            <xs:element name="baseModel" type="numsim:RelationshipType">
437                <xs:annotation>
438                    <xs:documentation>It is assumed that the consumer of this document can parse
439                        this ID locate it, and populate the contents as appropriate. At some future
440                        version we might use an xlink here.</xs:documentation>
441                </xs:annotation>
442            </xs:element>
443            <xs:element name="description" type="numsim:DescriptionType"/>
444            <xs:element name="boundaryCondition" type="numsim:BoundaryConditionType" minOccurs="0"
445                maxOccurs="unbounded"/>
446            <xs:element name="initialCondition" type="numsim:InitialConditionType" minOccurs="0"
447                maxOccurs="unbounded"/>
448            <xs:element name="ensemble" type="numsim:EnsembleDetailsType" minOccurs="0"
449                maxOccurs="1"/>
450            <xs:element name="parentEnsemble" type="numsim:RelationshipType" minOccurs="0"
451                maxOccurs="unbounded"/>
452        </xs:sequence>
453    </xs:complexType>
454    <!-- -->
455    <!-- Definition of the NumSimType. -->
456    <!-- -->
457    <xs:complexType name="NumSimType">
458        <!-- Note that the CodeBase concept was removed at V010-01 in favour of the model envelop which makes things a bit
459            clearer both in producing and consuming NumSim documents.
460            The name of document element has changed to make this obvious! -->
461        <xs:annotation>
462            <xs:documentation>Anything from Dublin Core may be included here, with the intention of
463                identifying, in particular, the authorship of the NumSim document itself. However,
464                note that the existing ndg code to consume document instances will only look for the
465                dc:creator elements</xs:documentation>
466        </xs:annotation>
467        <xs:sequence>
468            <xs:choice>
469                <xs:element name="model" type="numsim:ModelType"/>
470                <xs:element name="experiment" type="numsim:ExperimentType"/>
471            </xs:choice>
472            <xs:any namespace="http://purl.org/dc/elements/1.1/dc" minOccurs="0"
473                maxOccurs="unbounded" processContents="lax"/>
474        </xs:sequence>
475        <xs:attribute name="version"/>
476    </xs:complexType>
477    <!-- -->
478    <!-- simulationMetadata is the document element. -->
479    <!-- -->
480    <xs:element name="simulationMetadata" type="numsim:NumSimType"/>
481</xs:schema>
Note: See TracBrowser for help on using the repository browser.