Changeset 912 for TI01-discovery


Ignore:
Timestamp:
10/05/06 20:36:01 (14 years ago)
Author:
lawrence
Message:

First tranch of modifications following Exeter Metadata Meeting

File:
1 edited

Legend:

Unmodified
Added
Removed
  • TI01-discovery/trunk/schema/numsim/NumSim.xsd

    r887 r912  
    44    version="00800"> 
    55    <xs:annotation> 
    6         <xs:documentation> Author: Bryan Lawrence Version date: May 4th, 2006 </xs:documentation> 
    7     </xs:annotation> 
    8     <xs:annotation> 
     6        <xs:documentation> Author: Bryan Lawrence Version date: May 10th, 2006 </xs:documentation> 
    97        <xs:documentation>The expectation is that this schema will be used initially by import into 
    10             DIF discovery records and eventually into ISO19115 based discovery records. While such 
    11             discovery records already include adequate possibilities to include free text 
    12             information and/or URI references which would allow such discrimination for a human 
    13             reader, they do not allow the construction of sensible automatic discriminants, which 
    14             would allow a software agent to identify, for example, all simulation datasets based on 
    15             the IPCC SRESA1 forcing specification by the HADCM3 model. Such a software agent is 
    16             necessary to provide meaningful discovery services on an archive holding multiple 
    17             simulation datasets, and thus, there is a requirement to build information structures to 
    18             support such software agents. The NumSim schema provides a minimum set of such metadata 
    19             structures aimed at supporting the widest possible set of simulation codes. It is 
    20             expected that more detailed discipline specific metadata schema will exist, such as the 
    21             Numerical Model Metadata Suite (hereafter the NMM). Where such schema and instances 
    22             exist, it is desirable that the NumSim instances are automatically generated from the 
    23             more detailed metadata. </xs:documentation> 
     8            discovery records (ideally ISO19115 based). While such discovery records already include 
     9            adequate possibilities to include free text information and/or URI references which 
     10            would allow such discrimination for a human reader, they do not allow the construction 
     11            of sensible automatic discriminants, which would allow a software agent to identify, for 
     12            example, all simulation datasets based on the IPCC SRESA1 forcing specification by the 
     13            HADCM3 model. Such a software agent is necessary to provide meaningful discovery 
     14            services on an archive holding multiple simulation datasets, and thus, there is a 
     15            requirement to build information structures to support such software agents. The NumSim 
     16            schema provides a minimum set of such metadata structures aimed at supporting the widest 
     17            possible set of simulation codes. It is expected that more detailed discipline specific 
     18            metadata schema will exist, such as the Numerical Model Metadata Suite (hereafter the 
     19            NMM). Where such schema and instances exist, it is desirable that the NumSim instances 
     20            are automatically generated from the more detailed metadata. </xs:documentation> 
    2421        <xs:documentation>The NumSim schema exists in a context where NumSim compliant xml metadata 
    2522            is to included in a document conforming to an (extensible) parent schema. That parent 
     
    3431            their scope and applicability is related to where they appear. By doing this it is 
    3532            possible to search for datasets created by simulations with a particular model component 
    36             which was described in a particular </xs:documentation> 
     33            which was described in a particular reference.</xs:documentation> 
    3734        <xs:documentation>The simulated element is intended to appear as part of a dataset 
    3835            description, and is used to discriminate between differing simulations of the same 
     
    8077    <xs:complexType name="NS_ReferenceList"> 
    8178        <xs:choice> 
    82             <xs:element name="NS_Reference" type="xs:string" minOccurs="1" maxOccurs="unbounded"/> 
     79            <xs:sequence> 
     80                <xs:annotation> 
     81                    <xs:documentation> An URI can be provided to allow an index of references to be 
     82                        constructed. This is included to allow strings which reference publications 
     83                        differently to, for example, share the same DOI, and be indexed on these 
     84                        strings rather than (or as well as) the reference string content itself. 
     85                    </xs:documentation> 
     86                </xs:annotation> 
     87                <xs:element name="NS_Reference" type="xs:string" minOccurs="1" maxOccurs="unbounded"/> 
     88                <xs:sequence minOccurs="0"> 
     89                    <xs:element name="NS_URI" type="xs:string" minOccurs="1" maxOccurs="1"/> 
     90                    <xs:element name="NS_URIScheme" type="xs:string" minOccurs="1" maxOccurs="1"/> 
     91                </xs:sequence> 
     92            </xs:sequence> 
    8393            <xs:element name="NS_Citation" type="gmd:CI_Citation_Type" minOccurs="1" 
    8494                maxOccurs="unbounded"/> 
     
    98108        </xs:sequence> 
    99109    </xs:complexType> 
    100     <xs:simpleType name="NS_InitialConditionTypes"> 
     110    <xs:simpleType name="NS_InitialConditionTypes" id="NumSim_InitialConditionTypes_007"> 
    101111        <xs:restriction base="xs:string"> 
    102112            <xs:enumeration value="Objective Analysis"/> 
     
    112122                which might be able to run independently but could be coupled</xs:documentation> 
    113123        </xs:annotation> 
    114         <xs:restriction base="xs:string"> 
     124        <xs:restriction base="xs:string" id="NumSIm_ModelComponents_007"> 
    115125            <xs:enumeration value="Atmosphere"/> 
    116126            <xs:enumeration value="Ocean"/> 
     
    127137                up</xs:documentation> 
    128138        </xs:annotation> 
    129         <xs:restriction base="xs:string"> 
     139        <xs:restriction base="xs:string" id="NumSim_ModelCategories_007"> 
    130140            <xs:enumeration value="GCM"/> 
    131141            <xs:enumeration value="Standalone"/> 
     
    145155            Specifications</xs:documentation> 
    146156        </xs:annotation> 
    147         <xs:restriction base="xs:string"> 
     157        <xs:restriction base="xs:string" id="NumSim_BoundaryConditionTypes_007"> 
    148158            <xs:enumeration value="IPCC SRES A1"/> 
    149159            <xs:enumeration value="IPCC SRES A2"/> 
     
    168178            types.</xs:documentation> 
    169179        </xs:annotation> 
    170         <xs:restriction base="xs:string"> 
     180        <xs:restriction base="xs:string" id="NumSim_EnsembleTypes_007"> 
    171181            <xs:enumeration value="Initial Condition"/> 
    172182            <xs:enumeration value="Perturbed Physics"/> 
Note: See TracChangeset for help on using the changeset viewer.