Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Model
Properties
Source
Used by
Element eml / access
Namespace No namespace
Annotations
tooltip: Access

summary: Access control rules for the entire resource, which can be overridden by access rules in distribution trees

description: An optional access tree at this location controls access to the entire metadata document. If this access element is omitted from the document, then the package submitter should be given full access to the package but all other users should be denied all access.
Diagram
Diagram NO_NAMESPACE.tmp#AccessType_id NO_NAMESPACE.tmp#AccessType_system NO_NAMESPACE.tmp#AccessType_scope NO_NAMESPACE.tmp#AccessType_order NO_NAMESPACE.tmp#AccessType_authSystem NO_NAMESPACE.tmp#AccessType_allow NO_NAMESPACE.tmp#AccessType_deny NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup access-2_2_0.tmp#AccessType
Type AccessType
Properties
content complex
minOccurs 0
Model
Children allow, deny, references
Instance
<access authSystem="" id="" order="allowFirst" scope="document" system="">
  <allow>{1,1}</allow>
  <deny>{1,1}</deny>
  <references system="">{1,1}</references>
</access>
Attributes
QName Type Default Use Annotation
authSystem xs:string required
tooltip: Authentication system

summary: The authentication system is used to verify the user or
          group to whom access is allowed or denied.

description: The authentication system determines the set of
          principals (users + groups) that can be used in the access control
          list, and the membership of users in groups. This element is intended
          to provide a reference to the authentication system that is used to
          verify the user or group. This reference is typically in the form
          of a URI, which includes the connection protocol, Internet host, and
          path to the authentication mechanism.
id IDType optional
order restriction of xs:string allowFirst optional
tooltip: Rule order

summary: The order in which the allow and deny rules should be
          applied.

description: To obtain the desired access control, use the order
          attribute to define which rules should be applied first. The acceptable
          values are 'allowFirst' and 'denyFirst'. If 'allowFirst' is
          specified, then all 'allow' rules are processed, and then overridden
          by all 'deny' rules.  If 'denyFirst' is specified, then all 'deny'
          rules are processed, and then overridden by all 'allow' rules.
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="access" type="acc:AccessType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Access summary: Access control rules for the entire resource, which can be overridden by access rules in distribution trees description: An optional access tree at this location controls access to the entire metadata document. If this access element is omitted from the document, then the package submitter should be given full access to the package but all other users should be denied all access.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element AccessType / allow
Namespace No namespace
Annotations
tooltip: Allow rule

summary: A rule that grants a permission
              type.

description: The allow element indicates that a particular
              user or group is granted the defined permission.
Diagram
Diagram NO_NAMESPACE.tmp#AccessRule_principal NO_NAMESPACE.tmp#AccessRule_permission access-2_2_0.tmp#AccessRule
Type AccessRule
Properties
content complex
Model
Children permission, principal
Instance
<allow>
  <principal>{1,unbounded}</principal>
  <permission>{1,unbounded}</permission>
</allow>
Source
<xs:element name="allow" type="AccessRule">
  <xs:annotation>
    <xs:documentation>tooltip: Allow rule summary: A rule that grants a permission type. description: The allow element indicates that a particular user or group is granted the defined permission.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-access.xsd
Element AccessRule / principal
Namespace No namespace
Annotations
tooltip: User or group

summary: The user or group (principal) for which the access
            control applies.

description: The principal element defines the user or group to
            which the access control rule applies. The users and groups must be
            defined in the authentication system described in the authSystem
            element.  The special principal 'public' can be used to indicate
            that any user or group has a particular access permission, thereby
            making it easier to specify that anonymous access is allowed.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="principal" type="res:NonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: User or group summary: The user or group (principal) for which the access control applies. description: The principal element defines the user or group to which the access control rule applies. The users and groups must be defined in the authentication system described in the authSystem element. The special principal 'public' can be used to indicate that any user or group has a particular access permission, thereby making it easier to specify that anonymous access is allowed.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-access.xsd
Element AccessRule / permission
Namespace No namespace
Annotations
tooltip: Type of permission

summary: The type of permission being granted or denied.
            

description: 
              
                
            The permission that is being granted or denied
            to a particular user or group for a given resource. The list of
            permissions come from a predetermined list:
            
                'read' - allow or deny viewing of the resource, 
                'write' - allow or deny modification of the resource (except for access rules),  
                'changePermission' - modifications including access rules, and  
                'all' - all of the above. 
                

                This element also allows other permission values that may be applicable to some other authentication systems but are not defined in this specification (if these other values are used, access rule enforcement is indeterminate outside of the originating system).
Diagram
Diagram
Type union of(restriction of xs:string, xs:string)
Properties
content simple
maxOccurs unbounded
Source
<xs:element name="permission" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Type of permission summary: The type of permission being granted or denied. description: The permission that is being granted or denied to a particular user or group for a given resource. The list of permissions come from a predetermined list: 'read' - allow or deny viewing of the resource, 'write' - allow or deny modification of the resource (except for access rules), 'changePermission' - modifications including access rules, and 'all' - all of the above. This element also allows other permission values that may be applicable to some other authentication systems but are not defined in this specification (if these other values are used, access rule enforcement is indeterminate outside of the originating system).</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:union>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="read"/>
          <xs:enumeration value="write"/>
          <xs:enumeration value="changePermission"/>
          <xs:enumeration value="all"/>
        </xs:restriction>
      </xs:simpleType>
      <xs:simpleType>
        <xs:restriction base="xs:string"/>
      </xs:simpleType>
    </xs:union>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-access.xsd
Element AccessType / deny
Namespace No namespace
Annotations
tooltip: Deny rule

summary: A rule that revokes a permission
              type.

description: The deny element indicates that a particular
              user or group is not granted the defined
              permission.
Diagram
Diagram NO_NAMESPACE.tmp#AccessRule_principal NO_NAMESPACE.tmp#AccessRule_permission access-2_2_0.tmp#AccessRule
Type AccessRule
Properties
content complex
Model
Children permission, principal
Instance
<deny>
  <principal>{1,unbounded}</principal>
  <permission>{1,unbounded}</permission>
</deny>
Source
<xs:element name="deny" type="AccessRule">
  <xs:annotation>
    <xs:documentation>tooltip: Deny rule summary: A rule that revokes a permission type. description: The deny element indicates that a particular user or group is not granted the defined permission.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-access.xsd
Element ReferencesGroup / references
Namespace No namespace
Annotations
tooltip: References

summary: The id of another element in this
            EML document to be used to here in this context.
            

description: The id of another element in
            this EML document to be used to here in this context.
            This is used instead of duplicating information when an identical
            piece of information needs to be used multiple times in an
            EML document. For example, if the same person is the creator,
            metadataProvider, and contact for a dataset, their name and address
            can be provided once as part of the "creator" element, and then
            their "id" can be used in the "references" element of
            metadataProvider and contact.  This reduces the likelihood of
            error by reducing redundancy, and allows one to specify that
            two pieces of information are identical.  To be a valid EML
            document, the content of every "references" element MUST be
            defined in the document as the value of an "id" attribute on
            some element within the document.  Other critical rules
            about the use of IDs and references in EML are provided in the
            text of the EML specification.
Diagram
Diagram NO_NAMESPACE.tmp#ReferencesGroup_ReferencesGroup_references_system
Type extension of xs:string
Properties
content complex
Attributes
QName Type Use
system SystemType optional
Source
<xs:element name="references">
  <xs:annotation>
    <xs:documentation>tooltip: References summary: The id of another element in this EML document to be used to here in this context. description: The id of another element in this EML document to be used to here in this context. This is used instead of duplicating information when an identical piece of information needs to be used multiple times in an EML document. For example, if the same person is the creator, metadataProvider, and contact for a dataset, their name and address can be provided once as part of the "creator" element, and then their "id" can be used in the "references" element of metadataProvider and contact. This reduces the likelihood of error by reducing redundancy, and allows one to specify that two pieces of information are identical. To be a valid EML document, the content of every "references" element MUST be defined in the document as the value of an "id" attribute on some element within the document. Other critical rules about the use of IDs and references in EML are provided in the text of the EML specification.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="system" type="SystemType" use="optional"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element eml / dataset
Namespace No namespace
Annotations
tooltip: Dataset Resource

summary: A resource that describes a data set, which can include one or more
                  data entities such as data tables. 

description: A resource that describes a data set, which can include one or more
                  data entities such as data tables and spatial images (raster and vector). If
                  included, this represents the primary resource that is described in this eml
                  document.
Diagram
Diagram NO_NAMESPACE.tmp#DatasetType_id NO_NAMESPACE.tmp#DatasetType_system NO_NAMESPACE.tmp#DatasetType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#DatasetType_purpose NO_NAMESPACE.tmp#DatasetType_introduction NO_NAMESPACE.tmp#DatasetType_gettingStarted NO_NAMESPACE.tmp#DatasetType_acknowledgements NO_NAMESPACE.tmp#DatasetType_maintenance NO_NAMESPACE.tmp#DatasetType_contact NO_NAMESPACE.tmp#DatasetType_publisher NO_NAMESPACE.tmp#DatasetType_pubPlace NO_NAMESPACE.tmp#DatasetType_methods NO_NAMESPACE.tmp#DatasetType_project NO_NAMESPACE.tmp#DatasetType_dataTable NO_NAMESPACE.tmp#DatasetType_spatialRaster NO_NAMESPACE.tmp#DatasetType_spatialVector NO_NAMESPACE.tmp#DatasetType_storedProcedure NO_NAMESPACE.tmp#DatasetType_view NO_NAMESPACE.tmp#DatasetType_otherEntity NO_NAMESPACE.tmp#DatasetType_referencePublication NO_NAMESPACE.tmp#DatasetType_usageCitation NO_NAMESPACE.tmp#DatasetType_literatureCited NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup dataset-2_2_0.tmp#DatasetType
Type DatasetType
Properties
content complex
Model
Children abstract, acknowledgements, additionalInfo, alternateIdentifier, annotation, associatedParty, contact, coverage, creator, dataTable, distribution, gettingStarted, intellectualRights, introduction, keywordSet, language, licensed, literatureCited, maintenance, metadataProvider, methods, otherEntity, project, pubDate, pubPlace, publisher, purpose, referencePublication, references, series, shortName, spatialRaster, spatialVector, storedProcedure, title, usageCitation, view
Instance
<dataset id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <purpose xml:lang="">{0,1}</purpose>
  <introduction xml:lang="">{0,1}</introduction>
  <gettingStarted xml:lang="">{0,1}</gettingStarted>
  <acknowledgements xml:lang="">{0,1}</acknowledgements>
  <maintenance>{0,1}</maintenance>
  <contact id="" scope="document" system="">{1,unbounded}</contact>
  <publisher id="" scope="document" system="">{0,1}</publisher>
  <pubPlace>{0,1}</pubPlace>
  <methods>{0,1}</methods>
  <project id="" scope="document" system="">{0,1}</project>
  <dataTable id="" scope="document" system="">{1,1}</dataTable>
  <spatialRaster id="" scope="document" system="">{1,1}</spatialRaster>
  <spatialVector id="" scope="document" system="">{1,1}</spatialVector>
  <storedProcedure id="" scope="document" system="">{1,1}</storedProcedure>
  <view id="" scope="document" system="">{1,1}</view>
  <otherEntity id="" scope="document" system="">{1,1}</otherEntity>
  <referencePublication id="" scope="document" system="">{0,1}</referencePublication>
  <usageCitation id="" scope="document" system="">{0,unbounded}</usageCitation>
  <literatureCited>{0,unbounded}</literatureCited>
  <references system="">{1,1}</references>
</dataset>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="dataset" type="ds:DatasetType">
  <xs:annotation>
    <xs:documentation>tooltip: Dataset Resource summary: A resource that describes a data set, which can include one or more data entities such as data tables. description: A resource that describes a data set, which can include one or more data entities such as data tables and spatial images (raster and vector). If included, this represents the primary resource that is described in this eml document.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element ResourceGroup / alternateIdentifier
Namespace No namespace
Annotations
tooltip: Alternate Identifier

summary: A secondary identifier for this entity

description: An additional, secondary identifier for this
            entity. The primary identifier belongs in the "id" attribute, but
            additional identifiers that are used to label this entity, possibly
            from different data management systems, can be listed
            here.
Diagram
Diagram NO_NAMESPACE.tmp#ResourceGroup_ResourceGroup_alternateIdentifier_system
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
system SystemType optional
Source
<xs:element name="alternateIdentifier" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Alternate Identifier summary: A secondary identifier for this entity description: An additional, secondary identifier for this entity. The primary identifier belongs in the "id" attribute, but additional identifiers that are used to label this entity, possibly from different data management systems, can be listed here.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="system" type="SystemType" use="optional"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / shortName
Namespace No namespace
Annotations
tooltip: Short Name

summary: A short name that describes the resource, sometimes a
            filename.

description: The 'shortName' field provides a concise name that
            describes the resource that is being documented. It is the
            appropriate place to store a filename associated with other storage
            systems.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="shortName" type="NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Short Name summary: A short name that describes the resource, sometimes a filename. description: The 'shortName' field provides a concise name that describes the resource that is being documented. It is the appropriate place to store a filename associated with other storage systems.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / title
Namespace No namespace
Annotations
tooltip: Title

summary: A brief description of the resource, providing enough
            detail to differentiate it from other similar
            resources.

description: The 'title' field provides a description of the
            resource that is being documented that is long enough to
            differentiate it from other similar resources. Multiple titles may
            be provided, particularly when trying to express the title in more
            than one language (use the "xml:lang" attribute to indicate the
            language if not English/en).
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
maxOccurs unbounded
mixed true
Model
Children value
Instance
<title xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</title>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="title" type="i18nNonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Title summary: A brief description of the resource, providing enough detail to differentiate it from other similar resources. description: The 'title' field provides a description of the resource that is being documented that is long enough to differentiate it from other similar resources. Multiple titles may be provided, particularly when trying to express the title in more than one language (use the "xml:lang" attribute to indicate the language if not English/en).</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element i18nNonEmptyStringType / value
Namespace No namespace
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType namespace.tmp#lang
Type extension of NonEmptyStringType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="value" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>tooltip: i18n Value summary: i18n Value description: Allows multiple language translations to appear as children of a mixed-content parent element. The xml:lang attribute is optional and will override any xml:lang attribute that has been specified in the ancestor elements. The content is subject to the same rules defined by NonEmptyStringType.</xs:documentation>
    </xs:annotation>
    <xs:simpleContent>
      <xs:extension base="NonEmptyStringType">
        <xs:attribute ref="xml:lang" use="optional"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / creator
Namespace No namespace
Annotations
tooltip: Creator

summary: The people or organizations who created this
            resource.

description: The 'creator' element provides the full name of
            the person, organization, or position who created the resource. The
            list of creators for a resource represent the people and
            organizations who should be cited for the
            resource.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<creator id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</creator>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="creator" type="rp:ResponsibleParty" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Creator summary: The people or organizations who created this resource. description: The 'creator' element provides the full name of the person, organization, or position who created the resource. The list of creators for a resource represent the people and organizations who should be cited for the resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResponsibleParty / individualName
Namespace No namespace
Annotations
tooltip: Individual Name

summary: The full name of the person being
                described

description: 
                  
                    The individualName
                field contains subfields so that  a person's name can be broken
                down into               parts.
                    Note that the the content model for the containing type
        allows a sequence of choices for the first
        element(s): <individualName>, <organizationName> and/or <positionName>.
        This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements
        to make up a single logical party. For example, a creator with only
                the individualName of 'Joe Smith' is NOT the same as a
                creator with the individualName of 'Joe Smith' and the
                organizationName of 'NSF'. To include both a positionName and
                 an organizationName as children of a <contact> implies that anyone
                currently occupying that positionName at that organizationName
                is an appropriate contact.
                The positionName should not be
                used in conjunction with individualName unless only that specific
                individual at that position would be considered appropriate for that
                designation.
Diagram
Diagram NO_NAMESPACE.tmp#Person_salutation NO_NAMESPACE.tmp#Person_givenName NO_NAMESPACE.tmp#Person_surName party-2_2_0.tmp#Person
Type Person
Properties
content complex
Model
Children givenName, salutation, surName
Instance
<individualName>
  <salutation xml:lang="">{0,unbounded}</salutation>
  <givenName xml:lang="">{0,unbounded}</givenName>
  <surName xml:lang="">{1,1}</surName>
</individualName>
Source
<xs:element name="individualName" type="Person">
  <xs:annotation>
    <xs:documentation>tooltip: Individual Name summary: The full name of the person being described description: The individualName field contains subfields so that a person's name can be broken down into parts. Note that the the content model for the containing type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element Person / salutation
Namespace No namespace
Annotations
tooltip: Salutation

summary: The salutation used to address an
            individual

description: The salutation field is used in addressing an
            individual with a particular title, such as Dr., Ms., Mrs., Mr.,
            etc.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
maxOccurs unbounded
mixed true
Model
Children value
Instance
<salutation xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</salutation>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="salutation" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Salutation summary: The salutation used to address an individual description: The salutation field is used in addressing an individual with a particular title, such as Dr., Ms., Mrs., Mr., etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element Person / givenName
Namespace No namespace
Annotations
tooltip: Given name

summary: The given name of the individual.

description: The given name field can be used for first name of
            the individual associated with the resource, or for any other names
            that are not intended to be alphabetized, (as appropriate). Note that
            while it is possible  to include all given names in one field (as in the
            example below), it may be not be good practice to do so. For example, if an
            XSL transformation stylesheet were to abbreviate the content of a
            givenName to just the first initial, a givenName element that contained
            more than one name would not be transformed correctly.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
maxOccurs unbounded
mixed true
Model
Children value
Instance
<givenName xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</givenName>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="givenName" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Given name summary: The given name of the individual. description: The given name field can be used for first name of the individual associated with the resource, or for any other names that are not intended to be alphabetized, (as appropriate). Note that while it is possible to include all given names in one field (as in the example below), it may be not be good practice to do so. For example, if an XSL transformation stylesheet were to abbreviate the content of a givenName to just the first initial, a givenName element that contained more than one name would not be transformed correctly.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element Person / surName
Namespace No namespace
Annotations
tooltip: Last name

summary: The last name of the individual.

description: The surname field is used for the last name of the
            individual associated with the resource. This is typically the family name
            of an individual, for example, the name by which s/he is referred to in citations.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
mixed true
Model
Children value
Instance
<surName xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</surName>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="surName" type="res:i18nNonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Last name summary: The last name of the individual. description: The surname field is used for the last name of the individual associated with the resource. This is typically the family name of an individual, for example, the name by which s/he is referred to in citations.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element ResponsibleParty / organizationName
Namespace No namespace
Annotations
tooltip: Organization name

summary: The full name of the organization being
                described

description: 
                  
                    The responsible party field contains the full
                name of the organization that is associated with the resource.
                This field is intended to describe which institution or overall
                organization is associated with the resource being described.
               
                    Note that the the content model for the containing type
        allows a sequence of choices for the first
        element(s): <individualName>, <organizationName> and/or <positionName>.
        This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements
        to make up a single logical party. For example, a creator with only
                the individualName of 'Joe Smith' is NOT the same as a
                creator with the individualName of 'Joe Smith' and the
                organizationName of 'NSF'. To include both a positionName and
                 an organizationName as children of a <contact> implies that anyone
                currently occupying that positionName at that organizationName
                is an appropriate contact.
                The positionName should not be
                used in conjunction with individualName unless only that specific
                individual at that position would be considered appropriate for that
                designation.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
mixed true
Model
Children value
Instance
<organizationName xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</organizationName>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="organizationName" type="res:i18nNonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Organization name summary: The full name of the organization being described description: The responsible party field contains the full name of the organization that is associated with the resource. This field is intended to describe which institution or overall organization is associated with the resource being described. Note that the the content model for the containing type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element ResponsibleParty / positionName
Namespace No namespace
Annotations
tooltip: Position Name

summary: The name of the title or position associated with
                the resource.

description: 
                  
                    This field is intended to be used instead of a
                particular person or full organization name. If the associated
                person who holds the role changes frequently, then Position
                Name would be used for consistency. 
                    Note that the the content model for the containing type
        allows a sequence of choices for the first
        element(s): <individualName>, <organizationName> and/or <positionName>.
        This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements
        to make up a single logical party. For example, a creator with only
                the individualName of 'Joe Smith' is NOT the same as a
                creator with the individualName of 'Joe Smith' and the
                organizationName of 'NSF'. To include both a positionName and
                 an organizationName as children of a <contact> implies that anyone
                currently occupying that positionName at that organizationName
                is an appropriate contact.
                The positionName should not be
                used in conjunction with individualName unless only that specific
                individual at that position would be considered appropriate for that
                designation.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
mixed true
Model
Children value
Instance
<positionName xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</positionName>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="positionName" type="res:i18nNonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Position Name summary: The name of the title or position associated with the resource. description: This field is intended to be used instead of a particular person or full organization name. If the associated person who holds the role changes frequently, then Position Name would be used for consistency. Note that the the content model for the containing type allows a sequence of choices for the first element(s): <individualName>, <organizationName> and/or <positionName>. This means that a parent element (e.g., creator) may use combinations of the 3 sub-elements to make up a single logical party. For example, a creator with only the individualName of 'Joe Smith' is NOT the same as a creator with the individualName of 'Joe Smith' and the organizationName of 'NSF'. To include both a positionName and an organizationName as children of a <contact> implies that anyone currently occupying that positionName at that organizationName is an appropriate contact. The positionName should not be used in conjunction with individualName unless only that specific individual at that position would be considered appropriate for that designation.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element ResponsibleParty / address
Namespace No namespace
Annotations
tooltip: Contact address

summary: The full address information for a given responsible
              party entry.

description: The address field is a container for multiple
              subfields that describe the physical or electronic address of the
              responsible party for a resource.
Diagram
Diagram NO_NAMESPACE.tmp#Address_id NO_NAMESPACE.tmp#Address_system NO_NAMESPACE.tmp#Address_scope NO_NAMESPACE.tmp#Address_deliveryPoint NO_NAMESPACE.tmp#Address_city NO_NAMESPACE.tmp#Address_administrativeArea NO_NAMESPACE.tmp#Address_postalCode NO_NAMESPACE.tmp#Address_country NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#Address
Type Address
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children administrativeArea, city, country, deliveryPoint, postalCode, references
Instance
<address id="" scope="document" system="">
  <deliveryPoint xml:lang="">{0,unbounded}</deliveryPoint>
  <city xml:lang="">{0,1}</city>
  <administrativeArea xml:lang="">{0,1}</administrativeArea>
  <postalCode xml:lang="">{0,1}</postalCode>
  <country xml:lang="">{0,1}</country>
  <references system="">{1,1}</references>
</address>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="address" type="Address" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Contact address summary: The full address information for a given responsible party entry. description: The address field is a container for multiple subfields that describe the physical or electronic address of the responsible party for a resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element Address / deliveryPoint
Namespace No namespace
Annotations
tooltip: Delivery point

summary: The location for postal deliveries.

description: The delivery point field is used for the
              physical address for postal communication. This field is used to
              accommodate the many different international conventions that are
              the equivalent to a U.S. 'street address'.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
maxOccurs unbounded
mixed true
Model
Children value
Instance
<deliveryPoint xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</deliveryPoint>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="deliveryPoint" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Delivery point summary: The location for postal deliveries. description: The delivery point field is used for the physical address for postal communication. This field is used to accommodate the many different international conventions that are the equivalent to a U.S. 'street address'.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element Address / city
Namespace No namespace
Annotations
tooltip: City

summary: The name of the city for the contact.

description: The city field is used for the city name of the
              contact associated with a particular resource.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
mixed true
Model
Children value
Instance
<city xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</city>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="city" type="res:i18nNonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: City summary: The name of the city for the contact. description: The city field is used for the city name of the contact associated with a particular resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element Address / administrativeArea
Namespace No namespace
Annotations
tooltip: Administrative area

summary: The political area of a country.

description: The administrative area field is the equivalent
              of a 'state' in the U.S., or Province in Canada. This field is
              intended to accommodate the many types of international
              administrative areas.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
mixed true
Model
Children value
Instance
<administrativeArea xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</administrativeArea>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="administrativeArea" type="res:i18nNonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Administrative area summary: The political area of a country. description: The administrative area field is the equivalent of a 'state' in the U.S., or Province in Canada. This field is intended to accommodate the many types of international administrative areas.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element Address / postalCode
Namespace No namespace
Annotations
tooltip: Postal code

summary: The postal code used for routing to an
              address.

description: The postal code is equivalent to a U.S. zip
              code, or the number used for routing to an international address.
              The U.S. postal code should include the 5 digit code plus the 4
              digit extension.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
mixed true
Model
Children value
Instance
<postalCode xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</postalCode>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="postalCode" type="res:i18nNonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Postal code summary: The postal code used for routing to an address. description: The postal code is equivalent to a U.S. zip code, or the number used for routing to an international address. The U.S. postal code should include the 5 digit code plus the 4 digit extension.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element Address / country
Namespace No namespace
Annotations
tooltip: Country

summary: The name of the country for the contact's
              address.

description: The country field is used for the name of the
              contact's country.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
mixed true
Model
Children value
Instance
<country xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</country>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="country" type="res:i18nNonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Country summary: The name of the country for the contact's address. description: The country field is used for the name of the contact's country.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element ResponsibleParty / phone
Namespace No namespace
Annotations
tooltip: Phone

summary: Information about the contact's
              telephone

description: The phone field describes information about the
              responsible party's telephone, be it a voice phone, fax, or
              TTD/TTY type telephone. This field contains an attribute used to
              identify the type.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_ResponsibleParty_phone_phonetype
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Default Use Annotation
phonetype xs:string voice optional
tooltip: Phone type

summary: The type of the phone to which this number
                      applies

description: This attribute gives the type of phone
                      to which this number applies. By default, this is assumed
                      to be of type "voice", but other possibilities include
                      "facsimile" and "tdd".
Source
<xs:element name="phone" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Phone summary: Information about the contact's telephone description: The phone field describes information about the responsible party's telephone, be it a voice phone, fax, or TTD/TTY type telephone. This field contains an attribute used to identify the type.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="phonetype" type="xs:string" use="optional" default="voice">
          <xs:annotation>
            <xs:documentation>tooltip: Phone type summary: The type of the phone to which this number applies description: This attribute gives the type of phone to which this number applies. By default, this is assumed to be of type "voice", but other possibilities include "facsimile" and "tdd".</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element ResponsibleParty / electronicMailAddress
Namespace No namespace
Annotations
tooltip: Email address

summary: The email address of the contact.

description: The electronic mail address is the email address
              for the party. It is intended to be an Internet SMTP email
              address, which should consist of a username followed by the @
              symbol, followed by the email server domain name address. Other
              address types are allowable.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
maxOccurs unbounded
mixed true
Model
Children value
Instance
<electronicMailAddress xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</electronicMailAddress>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="electronicMailAddress" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Email address summary: The email address of the contact. description: The electronic mail address is the email address for the party. It is intended to be an Internet SMTP email address, which should consist of a username followed by the @ symbol, followed by the email server domain name address. Other address types are allowable.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element ResponsibleParty / onlineUrl
Namespace No namespace
Annotations
tooltip: Online Link

summary: A link to associated online information, usually a
              web site.

description: A link to associated online information, usually
              a web site. When the party represents an organization, this is
              the URL to a website or other online information about the
              organization. If the party is an individual, it might be their
              personal web site or other related online information about the
              party.
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
<xs:element name="onlineUrl" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Online Link summary: A link to associated online information, usually a web site. description: A link to associated online information, usually a web site. When the party represents an organization, this is the URL to a website or other online information about the organization. If the party is an individual, it might be their personal web site or other related online information about the party.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element ResponsibleParty / userId
Namespace No namespace
Annotations
tooltip: User Identifier

summary: An identifier that links this party to a
              directory of individuals

description: An identifier that links this party to a
              directory of individuals.  Although specific contact information
              for a party might change, the underlying correspondence to a
              real individual does not.  This identifier provides a pointer
              within a directory of individuals that may contain further, and
              possibly more current, information about the party.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_ResponsibleParty_userId_directory
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
directory xs:string required
tooltip: Directory

summary: The directory system within which the
                      directoryId can be retrieved.

description: This attribute names the directory system
                      to which this userId applies. This will generally
                      be a URL that shows how to look up information, for
                      example an LDAP URL. However, it could also be a
                      non-parsable description of the directory system if
                      that is all that is available.
Source
<xs:element name="userId" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: User Identifier summary: An identifier that links this party to a directory of individuals description: An identifier that links this party to a directory of individuals. Although specific contact information for a party might change, the underlying correspondence to a real individual does not. This identifier provides a pointer within a directory of individuals that may contain further, and possibly more current, information about the party.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="directory" type="xs:string" use="required">
          <xs:annotation>
            <xs:documentation>tooltip: Directory summary: The directory system within which the directoryId can be retrieved. description: This attribute names the directory system to which this userId applies. This will generally be a URL that shows how to look up information, for example an LDAP URL. However, it could also be a non-parsable description of the directory system if that is all that is available.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Element ResourceGroup / metadataProvider
Namespace No namespace
Annotations
tooltip: Metadata Provider

summary: The people or organizations who created provided
            documentation and other metadata for this resource.

description: The 'metadataProvider' element provides the full
            name of the person, organization, or position who created
            documentation for the resource.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<metadataProvider id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</metadataProvider>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="metadataProvider" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Metadata Provider summary: The people or organizations who created provided documentation and other metadata for this resource. description: The 'metadataProvider' element provides the full name of the person, organization, or position who created documentation for the resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / associatedParty
Namespace No namespace
Annotations
tooltip: Associated Party

summary: Other people or organizations who should be associated
            with this resource.

description: The 'associatedParty' element provides the full
            name of other people, organizations, or positions who should be
            associated with the resource. These parties might play various
            roles in the creation or maintenance of the resource, and these
            roles should be indicated in the "role" element.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty NO_NAMESPACE.tmp#ResourceGroup_ResourceGroup_associatedParty_role
Type extension of ResponsibleParty
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, role, userId
Instance
<associatedParty id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
  <role>{1,1}</role>
</associatedParty>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="associatedParty" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Associated Party summary: Other people or organizations who should be associated with this resource. description: The 'associatedParty' element provides the full name of other people, organizations, or positions who should be associated with the resource. These parties might play various roles in the creation or maintenance of the resource, and these roles should be indicated in the "role" element.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="rp:ResponsibleParty">
        <xs:sequence>
          <xs:element name="role" type="rp:RoleType">
            <xs:annotation>
              <xs:documentation>tooltip: Role summary: The role the party played with respect to the resource. description: Use this field to describe the role the party played with respect to the resource. Some potential roles include technician, reviewer, principal investigator, and many others.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / associatedParty / role
Namespace No namespace
Annotations
tooltip: Role

summary: The role the party played with respect to
                      the resource.

description: Use this field to describe the role the
                      party played with respect to the resource. Some potential
                      roles include technician, reviewer, principal
                      investigator, and many others.
Diagram
Diagram party-2_2_0.tmp#RoleType
Type RoleType
Properties
content simple
Source
<xs:element name="role" type="rp:RoleType">
  <xs:annotation>
    <xs:documentation>tooltip: Role summary: The role the party played with respect to the resource. description: Use this field to describe the role the party played with respect to the resource. Some potential roles include technician, reviewer, principal investigator, and many others.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / pubDate
Namespace No namespace
Annotations
tooltip: Publication date

summary: The publication date of the resource.

description: The 'pubDate' field represents the date that the
            resource was published. The format should be represented as: CCYY,
            which represents a 4 digit year, or as CCYY-MM-DD, which denotes
            the full year, month, and day. Note that month and day are optional
            components. Formats must conform to ISO 8601.
Diagram
Diagram resource-2_2_0.tmp#yearDate
Type yearDate
Properties
content simple
minOccurs 0
Source
<xs:element name="pubDate" type="yearDate" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publication date summary: The publication date of the resource. description: The 'pubDate' field represents the date that the resource was published. The format should be represented as: CCYY, which represents a 4 digit year, or as CCYY-MM-DD, which denotes the full year, month, and day. Note that month and day are optional components. Formats must conform to ISO 8601.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / language
Namespace No namespace
Annotations
tooltip: Language

summary: The language in which the resource is
            written.

description: The language in which the resource is written.
            This can be a well-known language name, or one of the ISO language
            codes to be more precise.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
mixed true
Model
Children value
Instance
<language xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</language>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="language" type="i18nNonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Language summary: The language in which the resource is written. description: The language in which the resource is written. This can be a well-known language name, or one of the ISO language codes to be more precise.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / series
Namespace No namespace
Annotations
tooltip: Series

summary: The series from which the resource came.

description: This field describes the series of resources that
            include the resource being described. For example, a volume of a
            journal may be part of a series of the journal for a particular
            year.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="series" type="NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Series summary: The series from which the resource came. description: This field describes the series of resources that include the resource being described. For example, a volume of a journal may be part of a series of the journal for a particular year.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / abstract
Namespace No namespace
Annotations
tooltip: Abstract

summary: A brief overview of the resource.

description: A brief overview of the resource that is being
            documented. The abstract should include basic information that
            summarizes the resource.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
mixed true
Model
Children markdown, para, section
Instance
<abstract xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</abstract>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="abstract" type="txt:TextType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Abstract summary: A brief overview of the resource. description: A brief overview of the resource that is being documented. The abstract should include basic information that summarizes the resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element TextType / section
Namespace No namespace
Annotations
tooltip: Section

summary: A section of related text.

description: The "section" element allows for grouping related paragraphs of text together, with an optional title. This markup is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#SectionType_title NO_NAMESPACE.tmp#SectionType_para NO_NAMESPACE.tmp#SectionType_section text-2_2_0.tmp#SectionType
Type SectionType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children para, section, title
Instance
<section xml:lang="">
  <title xml:lang="">{0,1}</title>
  <para xml:lang="">{1,1}</para>
  <section xml:lang="">{1,1}</section>
</section>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="section" type="SectionType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Section summary: A section of related text. description: The "section" element allows for grouping related paragraphs of text together, with an optional title. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element SectionType / title
Namespace No namespace
Annotations
tooltip: Title

summary: The optional title of the section.

description: The optional title for a section. This markup is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang text-2_2_0.tmp#i18nString
Type i18nString
Properties
content complex
minOccurs 0
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="title" type="i18nString" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Title summary: The optional title of the section. description: The optional title for a section. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element SectionType / para
Namespace No namespace
Annotations
tooltip: Paragraph

summary: A simple paragraph of text.

description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup
                                is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#ParagraphType_value NO_NAMESPACE.tmp#ParagraphType_itemizedlist NO_NAMESPACE.tmp#ParagraphType_orderedlist NO_NAMESPACE.tmp#ParagraphType_emphasis NO_NAMESPACE.tmp#ParagraphType_subscript NO_NAMESPACE.tmp#ParagraphType_superscript NO_NAMESPACE.tmp#ParagraphType_literalLayout NO_NAMESPACE.tmp#ParagraphType_ulink text-2_2_0.tmp#ParagraphType
Type ParagraphType
Properties
content complex
mixed true
Model
Children emphasis, itemizedlist, literalLayout, orderedlist, subscript, superscript, ulink, value
Instance
<para xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
  <itemizedlist>{1,1}</itemizedlist>
  <orderedlist>{1,1}</orderedlist>
  <emphasis xml:lang="">{1,1}</emphasis>
  <subscript xml:lang="">{1,1}</subscript>
  <superscript xml:lang="">{1,1}</superscript>
  <literalLayout>{1,1}</literalLayout>
  <ulink url="">{0,1}</ulink>
</para>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="para" type="ParagraphType">
  <xs:annotation>
    <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / value
Namespace No namespace
Annotations
tooltip: Localized string for the paragraph

summary: Language translation for the paragraph

description: Language translation as specified by the xml:lang attribute
Diagram
Diagram namespace.tmp#lang text-2_2_0.tmp#i18nString
Type i18nString
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Localized string for the paragraph summary: Language translation for the paragraph description: Language translation as specified by the xml:lang attribute</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / itemizedlist
Namespace No namespace
Annotations
tooltip: Itemized List

summary: A list of items in a text paragraph.
                        

description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.
Diagram
Diagram NO_NAMESPACE.tmp#ListType_listitem text-2_2_0.tmp#ListType
Type ListType
Properties
content complex
Model
Children listitem
Instance
<itemizedlist>
  <listitem>{1,unbounded}</listitem>
</itemizedlist>
Source
<xs:element name="itemizedlist" type="ListType">
  <xs:annotation>
    <xs:documentation>tooltip: Itemized List summary: A list of items in a text paragraph. description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ListType / listitem
Namespace No namespace
Annotations
tooltip: List Item

summary: An item in a list of items.

description: An item in a list of items. Each list item is formatted as a bulleted or numbered item depending on the list type in which it resides. List items contain paragraphs which in turn can be plain text or text with a limited set of markup
                            tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.
Diagram
Diagram NO_NAMESPACE.tmp#ListType_ListType_listitem_para NO_NAMESPACE.tmp#ListType_ListType_listitem_itemizedlist NO_NAMESPACE.tmp#ListType_ListType_listitem_orderedlist
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children itemizedlist, orderedlist, para
Instance
<listitem>
  <para xml:lang="">{1,1}</para>
  <itemizedlist>{1,1}</itemizedlist>
  <orderedlist>{1,1}</orderedlist>
</listitem>
Source
<xs:element name="listitem" minOccurs="1" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: List Item summary: An item in a list of items. description: An item in a list of items. Each list item is formatted as a bulleted or numbered item depending on the list type in which it resides. List items contain paragraphs which in turn can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice minOccurs="1" maxOccurs="unbounded">
      <xs:element name="para" type="ParagraphType">
        <xs:annotation>
          <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="itemizedlist" type="ListType">
        <xs:annotation>
          <xs:documentation>tooltip: Itemized List summary: A list of items in a text paragraph. description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="orderedlist" type="ListType">
        <xs:annotation>
          <xs:documentation>tooltip: Ordered List summary: An ordered list of items in a text paragraph. description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ListType / listitem / para
Namespace No namespace
Annotations
tooltip: Paragraph

summary: A simple paragraph of text.

description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup
                                        is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#ParagraphType_value NO_NAMESPACE.tmp#ParagraphType_itemizedlist NO_NAMESPACE.tmp#ParagraphType_orderedlist NO_NAMESPACE.tmp#ParagraphType_emphasis NO_NAMESPACE.tmp#ParagraphType_subscript NO_NAMESPACE.tmp#ParagraphType_superscript NO_NAMESPACE.tmp#ParagraphType_literalLayout NO_NAMESPACE.tmp#ParagraphType_ulink text-2_2_0.tmp#ParagraphType
Type ParagraphType
Properties
content complex
mixed true
Model
Children emphasis, itemizedlist, literalLayout, orderedlist, subscript, superscript, ulink, value
Instance
<para xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
  <itemizedlist>{1,1}</itemizedlist>
  <orderedlist>{1,1}</orderedlist>
  <emphasis xml:lang="">{1,1}</emphasis>
  <subscript xml:lang="">{1,1}</subscript>
  <superscript xml:lang="">{1,1}</superscript>
  <literalLayout>{1,1}</literalLayout>
  <ulink url="">{0,1}</ulink>
</para>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="para" type="ParagraphType">
  <xs:annotation>
    <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / orderedlist
Namespace No namespace
Annotations
tooltip: Ordered List

summary: An ordered list of items in a text paragraph.
                        

description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.
Diagram
Diagram NO_NAMESPACE.tmp#ListType_listitem text-2_2_0.tmp#ListType
Type ListType
Properties
content complex
Model
Children listitem
Instance
<orderedlist>
  <listitem>{1,unbounded}</listitem>
</orderedlist>
Source
<xs:element name="orderedlist" type="ListType">
  <xs:annotation>
    <xs:documentation>tooltip: Ordered List summary: An ordered list of items in a text paragraph. description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / emphasis
Namespace No namespace
Annotations
tooltip: Emphasis

summary: A span of emphasized text in a paragraph.

description: A span of emphasized text in a paragraph. Emphasized text is generally rendered as boldfaced or otherwise distinct from the surrounding text. This markup is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#ParagraphType_ParagraphType_emphasis_value
Properties
content complex
mixed true
Model
Children value
Instance
<emphasis xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</emphasis>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="emphasis">
  <xs:annotation>
    <xs:documentation>tooltip: Emphasis summary: A span of emphasized text in a paragraph. description: A span of emphasized text in a paragraph. Emphasized text is generally rendered as boldfaced or otherwise distinct from the surrounding text. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="true">
    <xs:sequence>
      <xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
    <xs:attribute ref="xml:lang"/>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / emphasis / value
Namespace No namespace
Diagram
Diagram namespace.tmp#lang text-2_2_0.tmp#i18nString
Type i18nString
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / subscript
Namespace No namespace
Annotations
tooltip: Subscript

summary: A subscript in a text paragraph.

description: A subscript in a text paragraph. This markup is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#SubSuperScriptType_value NO_NAMESPACE.tmp#SubSuperScriptType_subscript NO_NAMESPACE.tmp#SubSuperScriptType_superscript text-2_2_0.tmp#SubSuperScriptType
Type SubSuperScriptType
Properties
content complex
mixed true
Model
Children subscript, superscript, value
Instance
<subscript xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
  <subscript xml:lang="">{1,1}</subscript>
  <superscript xml:lang="">{1,1}</superscript>
</subscript>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="subscript" type="SubSuperScriptType">
  <xs:annotation>
    <xs:documentation>tooltip: Subscript summary: A subscript in a text paragraph. description: A subscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element SubSuperScriptType / value
Namespace No namespace
Annotations
tooltip: Localized string for the sub/superscript

summary: Language translation for the sub/superscript

description: Language translation as specified by the xml:lang attribute
Diagram
Diagram namespace.tmp#lang text-2_2_0.tmp#i18nString
Type i18nString
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Localized string for the sub/superscript summary: Language translation for the sub/superscript description: Language translation as specified by the xml:lang attribute</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element SubSuperScriptType / subscript
Namespace No namespace
Annotations
tooltip: Subscript

summary: A subscript in a text paragraph.

description: A subscript in a text paragraph. This markup is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#SubSuperScriptType_value NO_NAMESPACE.tmp#SubSuperScriptType_subscript NO_NAMESPACE.tmp#SubSuperScriptType_superscript text-2_2_0.tmp#SubSuperScriptType
Type SubSuperScriptType
Properties
content complex
mixed true
Model
Children subscript, superscript, value
Instance
<subscript xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
  <subscript xml:lang="">{1,1}</subscript>
  <superscript xml:lang="">{1,1}</superscript>
</subscript>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="subscript" type="SubSuperScriptType">
  <xs:annotation>
    <xs:documentation>tooltip: Subscript summary: A subscript in a text paragraph. description: A subscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element SubSuperScriptType / superscript
Namespace No namespace
Annotations
tooltip: Superscript

summary: A superscript in a text paragraph.

description: A superscript in a text paragraph. This markup is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#SubSuperScriptType_value NO_NAMESPACE.tmp#SubSuperScriptType_subscript NO_NAMESPACE.tmp#SubSuperScriptType_superscript text-2_2_0.tmp#SubSuperScriptType
Type SubSuperScriptType
Properties
content complex
mixed true
Model
Children subscript, superscript, value
Instance
<superscript xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
  <subscript xml:lang="">{1,1}</subscript>
  <superscript xml:lang="">{1,1}</superscript>
</superscript>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="superscript" type="SubSuperScriptType">
  <xs:annotation>
    <xs:documentation>tooltip: Superscript summary: A superscript in a text paragraph. description: A superscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / superscript
Namespace No namespace
Annotations
tooltip: Superscript

summary: A superscript in a text paragraph.

description: A superscript in a text paragraph. This markup is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#SubSuperScriptType_value NO_NAMESPACE.tmp#SubSuperScriptType_subscript NO_NAMESPACE.tmp#SubSuperScriptType_superscript text-2_2_0.tmp#SubSuperScriptType
Type SubSuperScriptType
Properties
content complex
mixed true
Model
Children subscript, superscript, value
Instance
<superscript xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
  <subscript xml:lang="">{1,1}</subscript>
  <superscript xml:lang="">{1,1}</superscript>
</superscript>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="superscript" type="SubSuperScriptType">
  <xs:annotation>
    <xs:documentation>tooltip: Superscript summary: A superscript in a text paragraph. description: A superscript in a text paragraph. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / literalLayout
Namespace No namespace
Annotations
tooltip: literalLayout

summary: The equivalent to <pre> in html.

description: This element specifies that the structure of the text within the tag, specifically the whitespace, should not be altered.
Diagram
Diagram NO_NAMESPACE.tmp#ParagraphType_ParagraphType_literalLayout_value
Properties
content complex
mixed true
Model
Children value
Instance
<literalLayout>
  <value xml:lang="">{0,unbounded}</value>
</literalLayout>
Source
<xs:element name="literalLayout">
  <xs:annotation>
    <xs:documentation>tooltip: literalLayout summary: The equivalent to <pre> in html. description: This element specifies that the structure of the text within the tag, specifically the whitespace, should not be altered.</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="true">
    <xs:sequence>
      <xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / literalLayout / value
Namespace No namespace
Diagram
Diagram namespace.tmp#lang text-2_2_0.tmp#i18nString
Type i18nString
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="value" type="i18nString" minOccurs="0" maxOccurs="unbounded"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / ulink
Namespace No namespace
Annotations
Diagram
Properties
Model
Children citetitle
Instance
Attributes
Source
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ParagraphType / ulink / citetitle
Namespace No namespace
Annotations
Diagram
Type i18nString
Properties
Attributes
Source
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ListType / listitem / itemizedlist
Namespace No namespace
Annotations
tooltip: Itemized List

summary: A list of items in a text paragraph.
                                    

description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.
Diagram
Diagram NO_NAMESPACE.tmp#ListType_listitem text-2_2_0.tmp#ListType
Type ListType
Properties
content complex
Model
Children listitem
Instance
<itemizedlist>
  <listitem>{1,unbounded}</listitem>
</itemizedlist>
Source
<xs:element name="itemizedlist" type="ListType">
  <xs:annotation>
    <xs:documentation>tooltip: Itemized List summary: A list of items in a text paragraph. description: A list of items in a text paragraph. The list is generally displayed as a bulleted list. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ListType / listitem / orderedlist
Namespace No namespace
Annotations
tooltip: Ordered List

summary: An ordered list of items in a text paragraph.
                                    

description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.
Diagram
Diagram NO_NAMESPACE.tmp#ListType_listitem text-2_2_0.tmp#ListType
Type ListType
Properties
content complex
Model
Children listitem
Instance
<orderedlist>
  <listitem>{1,unbounded}</listitem>
</orderedlist>
Source
<xs:element name="orderedlist" type="ListType">
  <xs:annotation>
    <xs:documentation>tooltip: Ordered List summary: An ordered list of items in a text paragraph. description: An ordered list of items in a text paragraph. The list is generally displayed as a numbered list. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element SectionType / section
Namespace No namespace
Annotations
tooltip: Section

summary: A section of related text.

description: The "section" element allows for grouping related paragraphs of text together, with an optional title. This markup is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#SectionType_title NO_NAMESPACE.tmp#SectionType_para NO_NAMESPACE.tmp#SectionType_section text-2_2_0.tmp#SectionType
Type SectionType
Properties
content complex
Model
Children para, section, title
Instance
<section xml:lang="">
  <title xml:lang="">{0,1}</title>
  <para xml:lang="">{1,1}</para>
  <section xml:lang="">{1,1}</section>
</section>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="section" type="SectionType">
  <xs:annotation>
    <xs:documentation>tooltip: Section summary: A section of related text. description: The "section" element allows for grouping related paragraphs of text together, with an optional title. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element TextType / para
Namespace No namespace
Annotations
tooltip: Paragraph

summary: A simple paragraph of text.

description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#ParagraphType_value NO_NAMESPACE.tmp#ParagraphType_itemizedlist NO_NAMESPACE.tmp#ParagraphType_orderedlist NO_NAMESPACE.tmp#ParagraphType_emphasis NO_NAMESPACE.tmp#ParagraphType_subscript NO_NAMESPACE.tmp#ParagraphType_superscript NO_NAMESPACE.tmp#ParagraphType_literalLayout NO_NAMESPACE.tmp#ParagraphType_ulink text-2_2_0.tmp#ParagraphType
Type ParagraphType
Properties
content complex
minOccurs 0
maxOccurs unbounded
mixed true
Model
Children emphasis, itemizedlist, literalLayout, orderedlist, subscript, superscript, ulink, value
Instance
<para xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
  <itemizedlist>{1,1}</itemizedlist>
  <orderedlist>{1,1}</orderedlist>
  <emphasis xml:lang="">{1,1}</emphasis>
  <subscript xml:lang="">{1,1}</subscript>
  <superscript xml:lang="">{1,1}</superscript>
  <literalLayout>{1,1}</literalLayout>
  <ulink url="">{0,1}</ulink>
</para>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="para" type="ParagraphType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Paragraph summary: A simple paragraph of text. description: The "paragraph" element allows for both formatted and unformatted text blocks to be included in EML. It can be plain text or text with a limited set of markup tags, including emphasis, subscript, superscript, and lists. This markup is a subset of DocBook.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element TextType / markdown
Namespace No namespace
Annotations
tooltip: Markdown

summary: A block of text formatted with Markdown directives.

description: 
                            
                                Markdown is a family of text-based formatting directives that can be used to
                                structure and format a block of text.  A single markdown element in EML can contain multiple
                                formatting directives that support creation of sections and subsections with headings, a
                                wide variety of text formatting directives, the ability to include inline links to external
                                content, and the ability to embed inline citations, figures, and tables. EML's markdown element
                                follows the GitHub Flavored Markdown (GFM) extensions to the CommonMark specification.  Clients that
                                display EML should use a markdown preprocessor to convert the Markdown formatting into an
                                appropriate display format such as HTML or PDF as appropriate.  When a Markdown block is interleaved
                                with other blocks of text such as section and paragraph elements from Docbook, the Markdown section
                                should be interleaved as a block-level element in the flow of the document.  This allows authors to
                                specify, for example, an initial section in DocBook, followed by a Markdown section, and then possibly
                                other sections in DocBook.  This will likely be uncommon because Markdown and Docbook have similar
                                formatting capabilities, but it may be helpful when converting legacy documents that use DocBook.
                            
                            
                                Because markdown uses special characters that might be reserved by XML processors, one
                                must be careful to escape such characters, which is typically done by embedding the
                                text in a CDATA block, or other XML escaping measures.  These escape sequences must be
                                unescaped before parsing the text with a Markdown processor.
                            
                            
                                Within a Markdown block, one can use embedded images to specify the location where an inline image
                                should be displayed within the document.  For example, the syntax for an embedded image uses the
                                markdown reference syntax, for example ![Figure 1][fig.1.ab567w], where "fig.1.ab567w"
                                is the unique id attribute for the entity containing the reference to the image.  When
                                client tools process such image links, they should inline the image data from that entity at the
                                location specified, which may involve, for example, resolving the image url from an
                                otherEntity section.  This means that there is an implied link in all Markdown
                                documents of the form [id]: url/to/image  "Optional title attribute", which is derived
                                from the metadata for each entity within a document.  Users do not need to insert these links in
                                order to use them, but client software that might be generating HTML from the markdown will likely
                                need to generate them from the entity metadata if they are using an external Markdown pre-processor
                                to handle conversion to HTML and other languages.
                            
                            
                                Inline citations can also be used to cite scholarly works in the text of an EML
                                document.  This follows the Pandoc syntax for citation keys, in which the citation keys
                                are in inside square brackets and separated by semicolons. Each citation is identified
                                by a key, which consists of an ‘@’ symbol and the citation identifier from the entry for
                                that citation. Citation keys may optionally have a prefix, a locator, and a suffix to
                                further qualify what is being cited.  For example, a simple citation would be
                                constructed as '[@fegraus_2005]', and a list would be '[@jones_2001; @fegraus_2005]'.
                                The keys must be present in either the 'id' field of a
                                citation element in the EML document, or as the BibTex key in a 'bibtex' entry in the
                                EML document.  It is a validation error to cite an entry for which the corresponding
                                citation key is not present in the EML document, and it is a validation error for the
                                same citation key to be reused across citation and bibtex elements in the document (each
                                citation identifier must be unique within the document).  Clients that parse and display
                                EML documents should first gather up all citation and bibtex elements in the document to
                                create a citation database in bibtext format, and then pass that database along with the
                                text in markdown sections to pandoc or an equivalent tool to convert the citations into
                                properly formatted, human readable citations.  Pandoc supports the use of Citation Style
                                Language (CSL) files to specify the formatting of citations upon conversion.  See
                                http://citationstyles.org/ for more details.
                            
                            
                                Because bulleted lists and other structures within Markdown are dependent on indenting the raw
                                markdown text, authors and processors should pay close attention to formatting within the
                                markdown block.  In particular, if the XML document within which the markdown block is embedded
                                is in an indented hierarchy, then the first non-whitespace character of the markdown block defines
                                the column for the leftmost column of the markdown, and all subsequent markdown should be indented
                                relative to that column.  For example, if the first character of the markdown is in column 16
                                of the document, then all subsequent markdown lines in that block should also start on column 16.
                                A bulleted list would start on column 16, and its sublist would be indented four space to column 20.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type extension of NonEmptyStringType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Source
<xs:element name="markdown" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Markdown summary: A block of text formatted with Markdown directives. description: Markdown is a family of text-based formatting directives that can be used to structure and format a block of text. A single markdown element in EML can contain multiple formatting directives that support creation of sections and subsections with headings, a wide variety of text formatting directives, the ability to include inline links to external content, and the ability to embed inline citations, figures, and tables. EML's markdown element follows the GitHub Flavored Markdown (GFM) extensions to the CommonMark specification. Clients that display EML should use a markdown preprocessor to convert the Markdown formatting into an appropriate display format such as HTML or PDF as appropriate. When a Markdown block is interleaved with other blocks of text such as section and paragraph elements from Docbook, the Markdown section should be interleaved as a block-level element in the flow of the document. This allows authors to specify, for example, an initial section in DocBook, followed by a Markdown section, and then possibly other sections in DocBook. This will likely be uncommon because Markdown and Docbook have similar formatting capabilities, but it may be helpful when converting legacy documents that use DocBook. Because markdown uses special characters that might be reserved by XML processors, one must be careful to escape such characters, which is typically done by embedding the text in a CDATA block, or other XML escaping measures. These escape sequences must be unescaped before parsing the text with a Markdown processor. Within a Markdown block, one can use embedded images to specify the location where an inline image should be displayed within the document. For example, the syntax for an embedded image uses the markdown reference syntax, for example ![Figure 1][fig.1.ab567w], where "fig.1.ab567w" is the unique id attribute for the entity containing the reference to the image. When client tools process such image links, they should inline the image data from that entity at the location specified, which may involve, for example, resolving the image url from an otherEntity section. This means that there is an implied link in all Markdown documents of the form [id]: url/to/image "Optional title attribute", which is derived from the metadata for each entity within a document. Users do not need to insert these links in order to use them, but client software that might be generating HTML from the markdown will likely need to generate them from the entity metadata if they are using an external Markdown pre-processor to handle conversion to HTML and other languages. Inline citations can also be used to cite scholarly works in the text of an EML document. This follows the Pandoc syntax for citation keys, in which the citation keys are in inside square brackets and separated by semicolons. Each citation is identified by a key, which consists of an ‘@’ symbol and the citation identifier from the entry for that citation. Citation keys may optionally have a prefix, a locator, and a suffix to further qualify what is being cited. For example, a simple citation would be constructed as '[@fegraus_2005]', and a list would be '[@jones_2001; @fegraus_2005]'. The keys must be present in either the 'id' field of a citation element in the EML document, or as the BibTex key in a 'bibtex' entry in the EML document. It is a validation error to cite an entry for which the corresponding citation key is not present in the EML document, and it is a validation error for the same citation key to be reused across citation and bibtex elements in the document (each citation identifier must be unique within the document). Clients that parse and display EML documents should first gather up all citation and bibtex elements in the document to create a citation database in bibtext format, and then pass that database along with the text in markdown sections to pandoc or an equivalent tool to convert the citations into properly formatted, human readable citations. Pandoc supports the use of Citation Style Language (CSL) files to specify the formatting of citations upon conversion. See http://citationstyles.org/ for more details. Because bulleted lists and other structures within Markdown are dependent on indenting the raw markdown text, authors and processors should pay close attention to formatting within the markdown block. In particular, if the XML document within which the markdown block is embedded is in an indented hierarchy, then the first non-whitespace character of the markdown block defines the column for the leftmost column of the markdown, and all subsequent markdown should be indented relative to that column. For example, if the first character of the markdown is in column 16 of the document, then all subsequent markdown lines in that block should also start on column 16. A bulleted list would start on column 16, and its sublist would be indented four space to column 20.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="res:NonEmptyStringType">
        <!--
                            <xs:attribute name="syntax" type="i18nNonEmptyStringType" use="optional">
                                <xs:annotation>
                                    <xs:appinfo>
                                        <doc:tooltip>url</doc:tooltip>
                                        <doc:summary>the Uniform Resource Locator for the cited work</doc:summary>
                                        <doc:description>the url attribute contains the location of the work for a link. This markup is a subset of DocBook.</doc:description>
                                        <doc:example>url="http://dublincore.org/documents/usageguide/"</doc:example>
                                    </xs:appinfo>
                                </xs:annotation>
                            </xs:attribute>
                            -->
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Element ResourceGroup / keywordSet
Namespace No namespace
Annotations
tooltip: Keyword information

summary: Keyword information that describes the
            resource.

description: The 'keywordSet' element is a container for the
            'keyword' and 'keywordThesaurus' fields. Each keywordSet field can
            contain one or more keywords and a name of a thesaurus for the set
            of keywords. Each keyword field should contain one and only one
            keyword (i.e., keywords should not be separated by commas or other
            delimiters).
Diagram
Diagram NO_NAMESPACE.tmp#ResourceGroup_ResourceGroup_keywordSet_keyword NO_NAMESPACE.tmp#ResourceGroup_ResourceGroup_keywordSet_keywordThesaurus
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children keyword, keywordThesaurus
Instance
<keywordSet>
  <keyword keywordType="" xml:lang="">{1,unbounded}</keyword>
  <keywordThesaurus>{0,1}</keywordThesaurus>
</keywordSet>
Source
<xs:element name="keywordSet" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Keyword information summary: Keyword information that describes the resource. description: The 'keywordSet' element is a container for the 'keyword' and 'keywordThesaurus' fields. Each keywordSet field can contain one or more keywords and a name of a thesaurus for the set of keywords. Each keyword field should contain one and only one keyword (i.e., keywords should not be separated by commas or other delimiters).</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="keyword" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Keyword summary: A single keyword that describes the resource. description: This field names a keyword or key phrase that concisely describes the resource or is related to the resource. Each keyword field should contain one and only one keyword (i.e., keywords should not be separated by commas or other delimiters).</xs:documentation>
        </xs:annotation>
        <xs:complexType mixed="true">
          <xs:complexContent>
            <xs:extension base="i18nNonEmptyStringType">
              <xs:attribute name="keywordType" type="KeyTypeCode" use="optional">
                <xs:annotation>
                  <xs:documentation>tooltip: Keyword type summary: The type of each keyword. description: This field classifies the keyword that has been provided from a list of pre-determined categories. The possible types are listed in the example.</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:extension>
          </xs:complexContent>
        </xs:complexType>
      </xs:element>
      <xs:element name="keywordThesaurus" type="NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Keyword thesaurus summary: The name of a thesaurus from which the keyword is derived. description: This field provides the name of the official keyword thesaurus from which keyword was derived. The keyword thesauri are usually discipline specific.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / keywordSet / keyword
Namespace No namespace
Annotations
tooltip: Keyword

summary: A single keyword that describes the
                  resource.

description: This field names a keyword or key phrase that
                  concisely describes the resource or is related to the
                  resource. Each keyword field should contain one and only one
                  keyword (i.e., keywords should not be separated by commas or
                  other delimiters).
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType NO_NAMESPACE.tmp#ResourceGroup_ResourceGroup_keywordSet_ResourceGroup_ResourceGroup_keywordSet_keyword_keywordType
Type extension of i18nNonEmptyStringType
Type hierarchy
Properties
content complex
maxOccurs unbounded
mixed true
Model
Children value
Instance
<keyword keywordType="" xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</keyword>
Attributes
QName Type Use Annotation
keywordType KeyTypeCode optional
tooltip: Keyword type

summary: The type of each keyword.

description: This field classifies the keyword
                          that has been provided from a list of pre-determined
                          categories. The possible types are listed in the
                          example.
xml:lang optional
Source
<xs:element name="keyword" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Keyword summary: A single keyword that describes the resource. description: This field names a keyword or key phrase that concisely describes the resource or is related to the resource. Each keyword field should contain one and only one keyword (i.e., keywords should not be separated by commas or other delimiters).</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="true">
    <xs:complexContent>
      <xs:extension base="i18nNonEmptyStringType">
        <xs:attribute name="keywordType" type="KeyTypeCode" use="optional">
          <xs:annotation>
            <xs:documentation>tooltip: Keyword type summary: The type of each keyword. description: This field classifies the keyword that has been provided from a list of pre-determined categories. The possible types are listed in the example.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / keywordSet / keywordThesaurus
Namespace No namespace
Annotations
tooltip: Keyword thesaurus

summary: The name of a thesaurus from which the keyword
                  is derived.

description: This field provides the name of the official
                  keyword thesaurus from which keyword was derived. The keyword
                  thesauri are usually discipline specific.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="keywordThesaurus" type="NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Keyword thesaurus summary: The name of a thesaurus from which the keyword is derived. description: This field provides the name of the official keyword thesaurus from which keyword was derived. The keyword thesauri are usually discipline specific.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / additionalInfo
Namespace No namespace
Annotations
tooltip: Additional Information

summary: Any extra information pertitent to the
            resource.

description: This field provides any information that is not
            characterized by the other resource metadata
            fields.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
maxOccurs unbounded
mixed true
Model
Children markdown, para, section
Instance
<additionalInfo xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</additionalInfo>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="additionalInfo" type="txt:TextType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Additional Information summary: Any extra information pertitent to the resource. description: This field provides any information that is not characterized by the other resource metadata fields.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / intellectualRights
Namespace No namespace
Annotations
tooltip: Intellectual Property Rights

summary: Intellectual property rights regarding usage and
            licensing of this resource.

description: Typically, an intellectual Rights element will
            contain a rights management statement for the resource, or
            reference a service providing such information. Rights information
            encompasses Intellectual Property Rights (IPR), Copyright, and
            various Property Rights. In the case of a data set, rights might
            include requirements for use, requirements for attribution, or other
            requirements the owner would like to impose.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
mixed true
Model
Children markdown, para, section
Instance
<intellectualRights xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</intellectualRights>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="intellectualRights" type="txt:TextType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Intellectual Property Rights summary: Intellectual property rights regarding usage and licensing of this resource. description: Typically, an intellectual Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. In the case of a data set, rights might include requirements for use, requirements for attribution, or other requirements the owner would like to impose.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / licensed
Namespace No namespace
Annotations
tooltip: License

summary: Information identifying a well-known license for the metadata and data
            

description: This element provides information on how the resource is licensed
                and what rights may be available to users.   While data are often not
                copyrightable in the US and other jurisdictions, it is still useful
                to clarify rights by declaring a CC0, CC-BY, or similar license for both the
                metadata and data.  Whatever license is declared here is intended to apply to
                all metadata and data described in the metadata record, including attached data
                resources such as external files and databases.  If multiple license elements
                are provided, this indicates that the resource can be used under the terms of
                any of the listed licenses. The field is meant to be highly structured
                to allow machine-interpretable licenses to be asserted for the resource.  This
                is done by identifying a well-defined license or contract and providing
                the SPDX license key or the license URL, and the name of the license.
                Where posisble, the name, URL, and SPDX key should match the values found in
                the official SPDX license vocabulary (https://spdx.org/licenses/).  If
                the license is not found in SPDX, then other well-established URIs for
                licenses can be used, but avoid using arbitrary URIs that
                are not maintained for persistence.
Diagram
Diagram NO_NAMESPACE.tmp#LicenseType_licenseName NO_NAMESPACE.tmp#LicenseType_url NO_NAMESPACE.tmp#LicenseType_identifier resource-2_2_0.tmp#LicenseType
Type LicenseType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children identifier, licenseName, url
Instance
<licensed>
  <licenseName>{1,1}</licenseName>
  <url>{0,1}</url>
  <identifier>{0,1}</identifier>
</licensed>
Source
<xs:element name="licensed" type="LicenseType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: License summary: Information identifying a well-known license for the metadata and data description: This element provides information on how the resource is licensed and what rights may be available to users. While data are often not copyrightable in the US and other jurisdictions, it is still useful to clarify rights by declaring a CC0, CC-BY, or similar license for both the metadata and data. Whatever license is declared here is intended to apply to all metadata and data described in the metadata record, including attached data resources such as external files and databases. If multiple license elements are provided, this indicates that the resource can be used under the terms of any of the listed licenses. The field is meant to be highly structured to allow machine-interpretable licenses to be asserted for the resource. This is done by identifying a well-defined license or contract and providing the SPDX license key or the license URL, and the name of the license. Where posisble, the name, URL, and SPDX key should match the values found in the official SPDX license vocabulary (https://spdx.org/licenses/). If the license is not found in SPDX, then other well-established URIs for licenses can be used, but avoid using arbitrary URIs that are not maintained for persistence.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element LicenseType / licenseName
Namespace No namespace
Annotations
tooltip: License Name

summary: The official name of the license

description: The official name of a license that applies to the
                        data and metadata described in this metadata record.
                        The name should match the name of a well-known license from
                        the SPDX license vocabulary or a similar persistent vocabulary.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 1
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="licenseName" type="NonEmptyStringType" minOccurs="1">
  <xs:annotation>
    <xs:documentation>tooltip: License Name summary: The official name of the license description: The official name of a license that applies to the data and metadata described in this metadata record. The name should match the name of a well-known license from the SPDX license vocabulary or a similar persistent vocabulary.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element LicenseType / url
Namespace No namespace
Annotations
tooltip: License URL

summary: The persistent URL for the license

description: The persistent URL for the license, typically
                        a SPDX URL, or an official URL from another well-known
                        license vocabulary.  Users should avoid using arbitrary
                        URLs that are not the official URL for a license.
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 0
Source
<xs:element name="url" type="xs:anyURI" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: License URL summary: The persistent URL for the license description: The persistent URL for the license, typically a SPDX URL, or an official URL from another well-known license vocabulary. Users should avoid using arbitrary URLs that are not the official URL for a license.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element LicenseType / identifier
Namespace No namespace
Annotations
tooltip: License Identifier

summary: License Identifier

description: The official identifier for the license, which
                        should be drawn from the SPDX license vocabulary, or a similar
                        well-known license vocabulary.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="identifier" type="NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: License Identifier summary: License Identifier description: The official identifier for the license, which should be drawn from the SPDX license vocabulary, or a similar well-known license vocabulary.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / distribution
Namespace No namespace
Annotations
tooltip: Distribution Information

summary: Information on how the resource is distributed online
            and offline

description: This element provides information on how the
            resource is distributed. When used at the resource level, this element can provide
            only general information, but elements for describing connections to online
            systems are provided. See the Type for specific recommendations and examples.
Diagram
Diagram NO_NAMESPACE.tmp#DistributionType_id NO_NAMESPACE.tmp#DistributionType_system NO_NAMESPACE.tmp#DistributionType_scope NO_NAMESPACE.tmp#DistributionType_online NO_NAMESPACE.tmp#DistributionType_offline NO_NAMESPACE.tmp#DistributionType_inline NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup resource-2_2_0.tmp#DistributionType
Type DistributionType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children inline, offline, online, references
Instance
<distribution id="" scope="document" system="">
  <online>{1,1}</online>
  <offline>{1,1}</offline>
  <inline>{1,1}</inline>
  <references system="">{1,1}</references>
</distribution>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="distribution" type="DistributionType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Distribution Information summary: Information on how the resource is distributed online and offline description: This element provides information on how the resource is distributed. When used at the resource level, this element can provide only general information, but elements for describing connections to online systems are provided. See the Type for specific recommendations and examples.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element DistributionType / online
Namespace No namespace
Annotations
tooltip: distribution/online

summary: Online distribution information

description: This element contains information for accessing the
              resource online, represented either as a URL a connection, or
              a connectionDefinition which may be referenced in other parts of
              the EML document. See the Type definition for more information.
Diagram
Diagram NO_NAMESPACE.tmp#OnlineType_onlineDescription NO_NAMESPACE.tmp#OnlineType_url NO_NAMESPACE.tmp#OnlineType_connection NO_NAMESPACE.tmp#OnlineType_connectionDefinition resource-2_2_0.tmp#OnlineType
Type OnlineType
Properties
content complex
Model
Children connection, connectionDefinition, onlineDescription, url
Instance
<online>
  <onlineDescription xml:lang="">{0,1}</onlineDescription>
  <url function="download">{1,1}</url>
  <connection id="" scope="document" system="">{1,1}</connection>
  <connectionDefinition id="" scope="document" system="">{1,1}</connectionDefinition>
</online>
Source
<xs:element name="online" type="OnlineType">
  <xs:annotation>
    <xs:documentation>tooltip: distribution/online summary: Online distribution information description: This element contains information for accessing the resource online, represented either as a URL a connection, or a connectionDefinition which may be referenced in other parts of the EML document. See the Type definition for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OnlineType / onlineDescription
Namespace No namespace
Annotations
tooltip: Description of online information

summary: Brief description of the the content of online

description: This element can hold a brief description of the content
            of the online element's online|offline|inline child. This description element could
            supply content for an html anchor tag.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
mixed true
Model
Children value
Instance
<onlineDescription xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</onlineDescription>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="onlineDescription" type="i18nNonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Description of online information summary: Brief description of the the content of online description: This element can hold a brief description of the content of the online element's online|offline|inline child. This description element could supply content for an html anchor tag.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OnlineType / url
Namespace No namespace
Annotations
tooltip: URL

summary: A URL or this resource.

description: A URL (Uniform Resource Locator) from which this additional
              information can be obtained, or from which the resource can be downloaded
              directly. In the resource module, the distribution URL is generally meant for
              informational purposes, and the "function" attribute should be set to "information".
              However, if the URL returns the data stream itself, then the "function" attribute
              should be set to "download".  See the Type Definition for more information.
Diagram
Diagram NO_NAMESPACE.tmp#UrlType_function resource-2_2_0.tmp#UrlType
Type UrlType
Properties
content complex
Attributes
QName Type Default Use
function FunctionType download optional
Source
<xs:element name="url" type="UrlType">
  <xs:annotation>
    <xs:documentation>tooltip: URL summary: A URL or this resource. description: A URL (Uniform Resource Locator) from which this additional information can be obtained, or from which the resource can be downloaded directly. In the resource module, the distribution URL is generally meant for informational purposes, and the "function" attribute should be set to "information". However, if the URL returns the data stream itself, then the "function" attribute should be set to "download". See the Type Definition for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OnlineType / connection
Namespace No namespace
Annotations
tooltip: Connection

summary: A connection to a data service

description: A description of the information needed to make an application
              connection to a data service. The connection contains a connectionDefinition
              and optional parameters for overriding defaults. See the Type Definition for
              more information.
Diagram
Diagram NO_NAMESPACE.tmp#ConnectionType_id NO_NAMESPACE.tmp#ConnectionType_system NO_NAMESPACE.tmp#ConnectionType_scope NO_NAMESPACE.tmp#ConnectionType_connectionDefinition NO_NAMESPACE.tmp#ConnectionType_parameter NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup resource-2_2_0.tmp#ConnectionType
Type ConnectionType
Properties
content complex
Model
Children connectionDefinition, parameter, references
Instance
<connection id="" scope="document" system="">
  <connectionDefinition id="" scope="document" system="">{1,1}</connectionDefinition>
  <parameter>{0,unbounded}</parameter>
  <references system="">{1,1}</references>
</connection>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="connection" type="ConnectionType">
  <xs:annotation>
    <xs:documentation>tooltip: Connection summary: A connection to a data service description: A description of the information needed to make an application connection to a data service. The connection contains a connectionDefinition and optional parameters for overriding defaults. See the Type Definition for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionType / connectionDefinition
Namespace No namespace
Annotations
tooltip: Connection Definition

summary: Connection Definition

description: In a ConnectionType, the connectionDefinition element provides the definition of the protocol and its parameters. The definition has a "scheme" which identifies the protocol by name, with a detailed description and its required parameters. A connectionDefinition lists all of the parameters needed for the connection and possible default values for each.
Diagram
Diagram NO_NAMESPACE.tmp#ConnectionDefinitionType_id NO_NAMESPACE.tmp#ConnectionDefinitionType_system NO_NAMESPACE.tmp#ConnectionDefinitionType_scope NO_NAMESPACE.tmp#ConnectionDefinitionType_schemeName NO_NAMESPACE.tmp#ConnectionDefinitionType_description NO_NAMESPACE.tmp#ConnectionDefinitionType_parameterDefinition NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup resource-2_2_0.tmp#ConnectionDefinitionType
Type ConnectionDefinitionType
Properties
content complex
Model
Children description, parameterDefinition, references, schemeName
Instance
<connectionDefinition id="" scope="document" system="">
  <schemeName system="">{1,1}</schemeName>
  <description xml:lang="">{1,1}</description>
  <parameterDefinition>{1,unbounded}</parameterDefinition>
  <references system="">{1,1}</references>
</connectionDefinition>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="connectionDefinition" type="ConnectionDefinitionType">
  <xs:annotation>
    <xs:documentation>tooltip: Connection Definition summary: Connection Definition description: In a ConnectionType, the connectionDefinition element provides the definition of the protocol and its parameters. The definition has a "scheme" which identifies the protocol by name, with a detailed description and its required parameters. A connectionDefinition lists all of the parameters needed for the connection and possible default values for each.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionDefinitionType / schemeName
Namespace No namespace
Annotations
tooltip: Scheme Name

summary: The name of the scheme used to identify this
              connection.

description: The name of the scheme used to identify this
              connection.  The scheme name is qualified by its system attribute.
              The scheme name implies a particular protocol for
              accessing information from the connection.  Applications must
              have a knowledge of the scheme or be able to deduce the protocol
              from the scheme description in order to effectively access data
              over the connection.  Many schemes will be unknown to client
              applications.  At some later point in time a registry for
              connection schemes may be established in order to promote
              application interoperability, and we may expand this portion of
              EML to adopt a more comprehensive standard such as WSDL, but for
              now this simpler description is provided.
Diagram
Diagram NO_NAMESPACE.tmp#ConnectionDefinitionType_ConnectionDefinitionType_schemeName_system
Type extension of xs:string
Properties
content complex
Attributes
QName Type Use Annotation
system SystemType optional
tooltip: Scheme System

summary: The system in which this scheme name is
                      relevant

description: The computing system within which this
                      scheme name has relevance. This attribute qualifies the
                      scheme name in order to decrease the likelihood of scheme
                      name collisions when more that one EML user defines a
                      scheme name with the same name but different semantics.
Source
<xs:element name="schemeName">
  <xs:annotation>
    <xs:documentation>tooltip: Scheme Name summary: The name of the scheme used to identify this connection. description: The name of the scheme used to identify this connection. The scheme name is qualified by its system attribute. The scheme name implies a particular protocol for accessing information from the connection. Applications must have a knowledge of the scheme or be able to deduce the protocol from the scheme description in order to effectively access data over the connection. Many schemes will be unknown to client applications. At some later point in time a registry for connection schemes may be established in order to promote application interoperability, and we may expand this portion of EML to adopt a more comprehensive standard such as WSDL, but for now this simpler description is provided.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="system" type="SystemType" use="optional">
          <xs:annotation>
            <xs:documentation>tooltip: Scheme System summary: The system in which this scheme name is relevant description: The computing system within which this scheme name has relevance. This attribute qualifies the scheme name in order to decrease the likelihood of scheme name collisions when more that one EML user defines a scheme name with the same name but different semantics.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionDefinitionType / description
Namespace No namespace
Annotations
tooltip: Scheme Description

summary: The description of the scheme used to identify this
              connection.

description: The description of the scheme used to identify
              this connection. The scheme name implies a particular protocol for
              accessing information from the connection.  Applications must
              have a knowledge of the scheme or be able to deduce the protocol
              from the scheme description in order to effectively access data
              over the connection.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
mixed true
Model
Children markdown, para, section
Instance
<description xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</description>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="description" type="txt:TextType">
  <xs:annotation>
    <xs:documentation>tooltip: Scheme Description summary: The description of the scheme used to identify this connection. description: The description of the scheme used to identify this connection. The scheme name implies a particular protocol for accessing information from the connection. Applications must have a knowledge of the scheme or be able to deduce the protocol from the scheme description in order to effectively access data over the connection.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionDefinitionType / parameterDefinition
Namespace No namespace
Annotations
tooltip: Parameter Definition

summary: The definition of a parameter that is needed to
              properly use this connection scheme.

description: The definition of a parameter that is needed to
              properly use this connection scheme.  Each parameter has a name
              and a definition that are used by applications to assess the type
              of information needed for the request.  Parameters may also set
              default values that are used if a connection does not provide a
              value for a parameter.
Diagram
Diagram NO_NAMESPACE.tmp#ConnectionDefinitionType_ConnectionDefinitionType_parameterDefinition_name NO_NAMESPACE.tmp#ConnectionDefinitionType_ConnectionDefinitionType_parameterDefinition_definition NO_NAMESPACE.tmp#ConnectionDefinitionType_ConnectionDefinitionType_parameterDefinition_defaultValue
Properties
content complex
maxOccurs unbounded
Model
Children defaultValue, definition, name
Instance
<parameterDefinition>
  <name>{1,1}</name>
  <definition>{1,1}</definition>
  <defaultValue>{0,1}</defaultValue>
</parameterDefinition>
Source
<xs:element name="parameterDefinition" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter Definition summary: The definition of a parameter that is needed to properly use this connection scheme. description: The definition of a parameter that is needed to properly use this connection scheme. Each parameter has a name and a definition that are used by applications to assess the type of information needed for the request. Parameters may also set default values that are used if a connection does not provide a value for a parameter.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="name" type="NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Parameter Name summary: The Name of a parameter that is needed to properly use this connection scheme. description: The name of a parameter that is needed to properly use this connection scheme.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="definition" type="NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Parameter Definition summary: The definition of a parameter that is needed to properly use this connection scheme. description: The definition of a parameter that is needed to properly use this connection scheme. The definition is used by applications to assess the type of information needed for the request.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="defaultValue" type="NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Default Parameter Value summary: The default value for a parameter that is needed to properly use this connection scheme. description: The default value for a parameter that is needed to properly use this connection scheme. If a default value is set, then it should be used for connections that do not override the default with a connection-specific value. This allows a definition to be established that declares common information that might be shared by several connections as default values. Parameter values provided in the connection always override any default values provided in the connection definition.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionDefinitionType / parameterDefinition / name
Namespace No namespace
Annotations
tooltip: Parameter Name

summary: The Name of a parameter that is needed to
                    properly use this connection scheme.

description: The name of a parameter that is needed to
                    properly use this connection scheme.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="name" type="NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter Name summary: The Name of a parameter that is needed to properly use this connection scheme. description: The name of a parameter that is needed to properly use this connection scheme.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionDefinitionType / parameterDefinition / definition
Namespace No namespace
Annotations
tooltip: Parameter Definition

summary: The definition of a parameter that is needed
                    to properly use this connection scheme.

description: The definition of a parameter that is
                    needed to properly use this connection scheme.  The
                    definition is used by applications to assess the type
                    of information needed for the request.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="definition" type="NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter Definition summary: The definition of a parameter that is needed to properly use this connection scheme. description: The definition of a parameter that is needed to properly use this connection scheme. The definition is used by applications to assess the type of information needed for the request.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionDefinitionType / parameterDefinition / defaultValue
Namespace No namespace
Annotations
tooltip: Default Parameter Value

summary: The default value for a parameter that is
                    needed to properly use this connection scheme.

description: The default value for a parameter that is
                    needed to properly use this connection scheme.  If a default
                    value is set, then it should be used for connections that
                    do not override the default with a connection-specific
                    value. This allows a definition to be established that
                    declares common information that might be shared by several
                    connections as default values.  Parameter values provided
                    in the connection always override any default values
                    provided in the connection definition.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="defaultValue" type="NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Default Parameter Value summary: The default value for a parameter that is needed to properly use this connection scheme. description: The default value for a parameter that is needed to properly use this connection scheme. If a default value is set, then it should be used for connections that do not override the default with a connection-specific value. This allows a definition to be established that declares common information that might be shared by several connections as default values. Parameter values provided in the connection always override any default values provided in the connection definition.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionType / parameter
Namespace No namespace
Annotations
tooltip: Parameter

summary: A parameter to be used to make this
                            connection.

description: A parameter to be used to make
                            this connection. This value overrides any
                            default value that may have been provided in the
                            connection definition.
Diagram
Diagram NO_NAMESPACE.tmp#ConnectionType_ConnectionType_parameter_name NO_NAMESPACE.tmp#ConnectionType_ConnectionType_parameter_value
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children name, value
Instance
<parameter>
  <name>{1,1}</name>
  <value>{1,1}</value>
</parameter>
Source
<xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter summary: A parameter to be used to make this connection. description: A parameter to be used to make this connection. This value overrides any default value that may have been provided in the connection definition.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="name" type="NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Parameter Name summary: Name of the parameter to be used to make this connection. description: The name of the parameter to be used to make this connection.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="value" type="NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Parameter Value summary: The value of the parameter to be used to make this connection. description: The value of the parameter to be used to make this connection. This value overrides any default value that may have been provided in the connection definition.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionType / parameter / name
Namespace No namespace
Annotations
tooltip: Parameter Name

summary: Name of the parameter to be
                                  used to make this connection.

description: The name of the parameter
                                  to be used to make this connection.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="name" type="NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter Name summary: Name of the parameter to be used to make this connection. description: The name of the parameter to be used to make this connection.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ConnectionType / parameter / value
Namespace No namespace
Annotations
tooltip: Parameter Value

summary: The value of the parameter to
                                  be used to make this connection.
                                  

description: The value of the parameter
                                  to be used to make this connection. This
                                  value overrides any default value that may
                                  have been provided in the connection
                                  definition.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="value" type="NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter Value summary: The value of the parameter to be used to make this connection. description: The value of the parameter to be used to make this connection. This value overrides any default value that may have been provided in the connection definition.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OnlineType / connectionDefinition
Namespace No namespace
Annotations
tooltip: Connection Definition

summary: The definition of a connection
        that will be used in another location in the EML
        document
                            

description: 
The definition of a type of connection
        that will be used in another location in the EML
        document. The connectionDefinition element only provides the definition of the
        protocol and its parameters, but not the actual values
        to be used to make the connection (instead, see the
        connection element).  This connectionDefinition may be
        used by multiple connections (e.g., to download different files
        from the same database), but each connection must provide or
        reference a valid connection definition.

     The definition has a "scheme" which identifies the
                            protocol by name, with a detailed description
                            and its required parameters. A connectionDefinition
                    lists all of the parameters needed for the connection
                    and possible default values for each.
Diagram
Diagram NO_NAMESPACE.tmp#ConnectionDefinitionType_id NO_NAMESPACE.tmp#ConnectionDefinitionType_system NO_NAMESPACE.tmp#ConnectionDefinitionType_scope NO_NAMESPACE.tmp#ConnectionDefinitionType_schemeName NO_NAMESPACE.tmp#ConnectionDefinitionType_description NO_NAMESPACE.tmp#ConnectionDefinitionType_parameterDefinition NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup resource-2_2_0.tmp#ConnectionDefinitionType
Type ConnectionDefinitionType
Properties
content complex
Model
Children description, parameterDefinition, references, schemeName
Instance
<connectionDefinition id="" scope="document" system="">
  <schemeName system="">{1,1}</schemeName>
  <description xml:lang="">{1,1}</description>
  <parameterDefinition>{1,unbounded}</parameterDefinition>
  <references system="">{1,1}</references>
</connectionDefinition>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="connectionDefinition" type="ConnectionDefinitionType">
  <xs:annotation>
    <xs:documentation>tooltip: Connection Definition summary: The definition of a connection that will be used in another location in the EML document description: The definition of a type of connection that will be used in another location in the EML document. The connectionDefinition element only provides the definition of the protocol and its parameters, but not the actual values to be used to make the connection (instead, see the connection element). This connectionDefinition may be used by multiple connections (e.g., to download different files from the same database), but each connection must provide or reference a valid connection definition. The definition has a "scheme" which identifies the protocol by name, with a detailed description and its required parameters. A connectionDefinition lists all of the parameters needed for the connection and possible default values for each.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element DistributionType / offline
Namespace No namespace
Annotations
tooltip: Offline distribution

summary: data are available offline

description: This element is for data which are distributed offline,
         generally by request. See the Type
        definition for more information.
Diagram
Diagram NO_NAMESPACE.tmp#OfflineType_mediumName NO_NAMESPACE.tmp#OfflineType_mediumDensity NO_NAMESPACE.tmp#OfflineType_mediumDensityUnits NO_NAMESPACE.tmp#OfflineType_mediumVolume NO_NAMESPACE.tmp#OfflineType_mediumFormat NO_NAMESPACE.tmp#OfflineType_mediumNote resource-2_2_0.tmp#OfflineType
Type OfflineType
Properties
content complex
Model
Children mediumDensity, mediumDensityUnits, mediumFormat, mediumName, mediumNote, mediumVolume
Instance
<offline>
  <mediumName>{1,1}</mediumName>
  <mediumDensity>{0,1}</mediumDensity>
  <mediumDensityUnits>{0,1}</mediumDensityUnits>
  <mediumVolume>{0,1}</mediumVolume>
  <mediumFormat>{0,unbounded}</mediumFormat>
  <mediumNote>{0,1}</mediumNote>
</offline>
Source
<xs:element name="offline" type="OfflineType">
  <xs:annotation>
    <xs:documentation>tooltip: Offline distribution summary: data are available offline description: This element is for data which are distributed offline, generally by request. See the Type definition for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OfflineType / mediumName
Namespace No namespace
Annotations
tooltip: Medium name

summary: Name of the medium that for this resource
                    distribution

description: Name of the medium on which this resource
                    is distributed. Can be various digital media such as tapes
                    and disks, or printed media which can collectively be
                    termed 'hardcopy'.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="mediumName" type="NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Medium name summary: Name of the medium that for this resource distribution description: Name of the medium on which this resource is distributed. Can be various digital media such as tapes and disks, or printed media which can collectively be termed 'hardcopy'.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OfflineType / mediumDensity
Namespace No namespace
Annotations
tooltip: density of the digital medium

summary: the density of the digital medium if this is
                    relevant.

description: the density of the digital medium if this
                    is relevant. Used mainly for floppy disks or
                    tape.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="mediumDensity" type="NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: density of the digital medium summary: the density of the digital medium if this is relevant. description: the density of the digital medium if this is relevant. Used mainly for floppy disks or tape.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OfflineType / mediumDensityUnits
Namespace No namespace
Annotations
tooltip: units of a numerical density

summary: a numerical density's units

description: if a density is given numerically, the
                    units should be given here.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="mediumDensityUnits" type="NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: units of a numerical density summary: a numerical density's units description: if a density is given numerically, the units should be given here.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OfflineType / mediumVolume
Namespace No namespace
Annotations
tooltip: storage volume

summary: total volume of the storage
                    medium

description: the total volume of the storage medium on
                    which this resource is shipped.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="mediumVolume" type="NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: storage volume summary: total volume of the storage medium description: the total volume of the storage medium on which this resource is shipped.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OfflineType / mediumFormat
Namespace No namespace
Annotations
tooltip: medium format

summary: format of the medium on which the resource is
                    shipped.

description: the file system format of the medium on
                    which the resource is shipped
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="mediumFormat" type="NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: medium format summary: format of the medium on which the resource is shipped. description: the file system format of the medium on which the resource is shipped</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element OfflineType / mediumNote
Namespace No namespace
Annotations
tooltip: note about the media

summary: note about the media

description: any additional pertinent information about
                    the media
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="mediumNote" type="NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: note about the media summary: note about the media description: any additional pertinent information about the media</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element DistributionType / inline
Namespace No namespace
Annotations
tooltip: Inline distribution

summary: data distributed inline in the metadata.

description: The data are distributed inline, with the metadata. See the Type
        definition for more information.
Diagram
Diagram resource-2_2_0.tmp#InlineType
Type InlineType
Properties
content complex
mixed true
Model
ANY element from ANY namespace
Source
<xs:element name="inline" type="InlineType">
  <xs:annotation>
    <xs:documentation>tooltip: Inline distribution summary: data distributed inline in the metadata. description: The data are distributed inline, with the metadata. See the Type definition for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element ResourceGroup / coverage
Namespace No namespace
Annotations
tooltip: Resource coverage

summary: Extent of the coverage of the resource.

description: This element describes the extent of the coverage
            of the resource in terms of its spatial extent, temporal extent,
            and taxonomic extent. For data sets, this is useful to specify the
            entire extent to which all of the data might
            apply.
Diagram
Diagram NO_NAMESPACE.tmp#Coverage_id NO_NAMESPACE.tmp#Coverage_system NO_NAMESPACE.tmp#Coverage_scope NO_NAMESPACE.tmp#Coverage_geographicCoverage NO_NAMESPACE.tmp#Coverage_temporalCoverage NO_NAMESPACE.tmp#Coverage_taxonomicCoverage NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#Coverage
Type Coverage
Properties
content complex
minOccurs 0
Model
Children geographicCoverage, references, taxonomicCoverage, temporalCoverage
Instance
<coverage id="" scope="document" system="">
  <geographicCoverage id="" scope="document" system="">{1,1}</geographicCoverage>
  <temporalCoverage id="" scope="document" system="">{1,1}</temporalCoverage>
  <taxonomicCoverage id="" scope="document" system="">{1,1}</taxonomicCoverage>
  <references system="">{1,1}</references>
</coverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="coverage" type="cov:Coverage" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Resource coverage summary: Extent of the coverage of the resource. description: This element describes the extent of the coverage of the resource in terms of its spatial extent, temporal extent, and taxonomic extent. For data sets, this is useful to specify the entire extent to which all of the data might apply.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element Coverage / geographicCoverage
Namespace No namespace
Annotations
tooltip: Geographic coverage

summary: Geographic coverage information.

description: Geographic Coverage is a container for spatial
              information about a project, a resource, or an entity within a
              resource. It allows a bounding box for the overall coverage (in
              lat long), and also allows description of arbitrary polygons with
              exclusions.
Diagram
Diagram NO_NAMESPACE.tmp#GeographicCoverage_id NO_NAMESPACE.tmp#GeographicCoverage_system NO_NAMESPACE.tmp#GeographicCoverage_scope NO_NAMESPACE.tmp#GeographicCoverage_geographicDescription NO_NAMESPACE.tmp#GeographicCoverage_boundingCoordinates NO_NAMESPACE.tmp#GeographicCoverage_datasetGPolygon NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#GeographicCoverage
Type GeographicCoverage
Properties
content complex
Model
Children boundingCoordinates, datasetGPolygon, geographicDescription, references
Instance
<geographicCoverage id="" scope="document" system="">
  <geographicDescription>{1,1}</geographicDescription>
  <boundingCoordinates>{1,1}</boundingCoordinates>
  <datasetGPolygon>{0,unbounded}</datasetGPolygon>
  <references system="">{1,1}</references>
</geographicCoverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="geographicCoverage" type="GeographicCoverage">
  <xs:annotation>
    <xs:documentation>tooltip: Geographic coverage summary: Geographic coverage information. description: Geographic Coverage is a container for spatial information about a project, a resource, or an entity within a resource. It allows a bounding box for the overall coverage (in lat long), and also allows description of arbitrary polygons with exclusions.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / geographicDescription
Namespace No namespace
Annotations
tooltip: Description of geographic extent

summary: Short text description of the geographic areal domain of
              the data set.

description: 
                
                  geographicDescription is a short text description of a dataset's
              geographic areal domain. A text description is especially important to
              provide a geographic                           setting
               when the extent of the data set cannot be well described
              by the "boundingCoordinates", or in the case of data
              which are not specifically geospatial. Assuming the
              "boundingCoordinates" do not adequately describe the
              extent of the data set, the discrepancy can be identified and
              described here. The coordinates may define a rectangle around a
              country, with this geographicDescription element
              containing a disclaimer
               and/or further details concerning the border.
             A study of the diseases of salmon may not have a
              specific geographic extent associated with it, but the salmon
               were collected in the states of Washington and Oregon.
              The "boundingCoordinates" might form a
              general rectangle around the states of Washington and Oregon, but
              the "geographicDescription" might describe the fact
              that the study took place only along
              certain rivers within those states. 
                  
              This data element differs
              from the standard data element "Place_Keyword" in that it allows
              a free text description of the geographic extent, rather than
              just a list of words or phrases useful as an index of location
              names associated with the data set.  
                  This element can also contain information
              about the collection of the boundingCoordinates, e.g., an altitude value that is referenced
              to Mean Lower Low Water, or the projection system that the latitude and
              longitude coordinates were taken from.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="geographicDescription" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Description of geographic extent summary: Short text description of the geographic areal domain of the data set. description: geographicDescription is a short text description of a dataset's geographic areal domain. A text description is especially important to provide a geographic setting when the extent of the data set cannot be well described by the "boundingCoordinates", or in the case of data which are not specifically geospatial. Assuming the "boundingCoordinates" do not adequately describe the extent of the data set, the discrepancy can be identified and described here. The coordinates may define a rectangle around a country, with this geographicDescription element containing a disclaimer and/or further details concerning the border. A study of the diseases of salmon may not have a specific geographic extent associated with it, but the salmon were collected in the states of Washington and Oregon. The "boundingCoordinates" might form a general rectangle around the states of Washington and Oregon, but the "geographicDescription" might describe the fact that the study took place only along certain rivers within those states. This data element differs from the standard data element "Place_Keyword" in that it allows a free text description of the geographic extent, rather than just a list of words or phrases useful as an index of location names associated with the data set. This element can also contain information about the collection of the boundingCoordinates, e.g., an altitude value that is referenced to Mean Lower Low Water, or the projection system that the latitude and longitude coordinates were taken from.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / boundingCoordinates
Namespace No namespace
Annotations
tooltip: Bounding coordinates

summary: The four margins (N, S, E, W) of a bounding box on the earth's surface,
              or when considered in lat-lon pairs, the corners of the box. To define a single
              point, use the same value in each lat or lon pair.  These elements are meant to convey general
              information and are not for accurate mapping.  More specific information may be
              included by using the elements in the spatialReference schema.

description: 
                
                  Bounding Coordinates are the four margins (N, S, E, W) of a bounding box,
              or when considered in lat-lon pairs, the corners of the box. These elements are meant to convey general
              information and are not for accurate mapping.  More specific information may be
              included by using the elements in the spatialReference schema.
                  The limits of coverage of a data set should be expressed
              as decimal latitudes and longitudes, and in the order western-most,
              eastern-most, northern-most, and southern-most. By convention,
              latitudes and longitudes are referenced to the  Equator and to the Prime Meridian
              (the datums), respectively.
              By definition, the 0 and 180 meridians themselves do not belong in either hemisphere,
              but local conventions may place them in either. All coordinates are typed as decimals.
              Since all four elements are required, a bounding area that is a
              single point should use the same values for
              northBoundingCoordinate and southBoundingCoordinate, and likewise
             for westBoundingCoordinate and eastBoundingCoordinate. 
                  In the case of a data set that comprises
                    all longitudes (e.g., a horizontal band between 2 parallels that fully
                    encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an
                    eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically
                    appropriate to specify both values as "180" (or any other meridian), but this could
                    also be interpreted as only the  meridian itself, so this is not recommended
Diagram
Diagram NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_boundingCoordinates_westBoundingCoordinate NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_boundingCoordinates_eastBoundingCoordinate NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_boundingCoordinates_northBoundingCoordinate NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_boundingCoordinates_southBoundingCoordinate NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_boundingCoordinates_boundingAltitudes
Properties
content complex
Model
Children boundingAltitudes, eastBoundingCoordinate, northBoundingCoordinate, southBoundingCoordinate, westBoundingCoordinate
Instance
<boundingCoordinates>
  <westBoundingCoordinate>{1,1}</westBoundingCoordinate>
  <eastBoundingCoordinate>{1,1}</eastBoundingCoordinate>
  <northBoundingCoordinate>{1,1}</northBoundingCoordinate>
  <southBoundingCoordinate>{1,1}</southBoundingCoordinate>
  <boundingAltitudes>{0,1}</boundingAltitudes>
</boundingCoordinates>
Source
<xs:element name="boundingCoordinates">
  <xs:annotation>
    <xs:documentation>tooltip: Bounding coordinates summary: The four margins (N, S, E, W) of a bounding box on the earth's surface, or when considered in lat-lon pairs, the corners of the box. To define a single point, use the same value in each lat or lon pair. These elements are meant to convey general information and are not for accurate mapping. More specific information may be included by using the elements in the spatialReference schema. description: Bounding Coordinates are the four margins (N, S, E, W) of a bounding box, or when considered in lat-lon pairs, the corners of the box. These elements are meant to convey general information and are not for accurate mapping. More specific information may be included by using the elements in the spatialReference schema. The limits of coverage of a data set should be expressed as decimal latitudes and longitudes, and in the order western-most, eastern-most, northern-most, and southern-most. By convention, latitudes and longitudes are referenced to the Equator and to the Prime Meridian (the datums), respectively. By definition, the 0 and 180 meridians themselves do not belong in either hemisphere, but local conventions may place them in either. All coordinates are typed as decimals. Since all four elements are required, a bounding area that is a single point should use the same values for northBoundingCoordinate and southBoundingCoordinate, and likewise for westBoundingCoordinate and eastBoundingCoordinate. In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="westBoundingCoordinate">
        <xs:annotation>
          <xs:documentation>tooltip: West bounding coordinate, in decimal degrees summary: Western-most limit of a bounding box, expressed in degrees of longitude. description: The westBoundingCoordinate field defines the longitude of the western-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:decimal">
            <xs:minInclusive value="-180.0"/>
            <xs:maxInclusive value="180.0"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="eastBoundingCoordinate">
        <xs:annotation>
          <xs:documentation>tooltip: East bounding coordinate summary: Eastern-most limit of a bounding box, expressed in degrees of longitude. description: The eastBoundingCoordinate field defines the longitude of the eastern-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:decimal">
            <xs:minInclusive value="-180.0"/>
            <xs:maxInclusive value="180.0"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="northBoundingCoordinate">
        <xs:annotation>
          <xs:documentation>tooltip: North bounding coordinate summary: Northern-most lilmit of a bounding box expressed in latitude. description: The northBoundingCoordinate field defines the latitude of the northern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:decimal">
            <xs:minInclusive value="-90.0"/>
            <xs:maxInclusive value="90.0"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="southBoundingCoordinate">
        <xs:annotation>
          <xs:documentation>tooltip: South bounding coordinate summary: Southern-most limit of the bounding box expressed in latitude. description: The southBoundingCoordinate field defines the latitude of the southern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:decimal">
            <xs:minInclusive value="-90.0"/>
            <xs:maxInclusive value="90.0"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="boundingAltitudes" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Bounding altitudes summary: The vertical limits of a data set expressed by altitude. description: The bounding altitude field is intended to contain altitudinal (elevation) measurements for the bounding box being described. It allows for minimum and maximum altitude fields, as well as a field for the units of measure. The combination of these fields provide the vertical extent information for the bounding box.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="altitudeMinimum" type="xs:decimal">
              <xs:annotation>
                <xs:documentation>tooltip: Minimum altitude summary: The minimum altitude extent of coverage. description: The minimum altitude extent of coverage for the bounding box that is being described. The minimum altitude should be in reference to a known datum (e.g., Mean Sea Level), which should be part of the geographicDescription.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="altitudeMaximum" type="xs:decimal">
              <xs:annotation>
                <xs:documentation>tooltip: Maximum altitude summary: The maximum altitude extent of coverage. description: The maximum altitude extent of coverage for the bounding box that is being described. The maximum altitude should be in reference to a known datum, which should be part of the geographicDescription.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="altitudeUnits" type="unit:LengthUnitType">
              <xs:annotation>
                <xs:documentation>tooltip: Altitude Units summary: The unit of altitude description: The unit that the altitude is expressed in. See the description under the Type definition</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / boundingCoordinates / westBoundingCoordinate
Namespace No namespace
Annotations
tooltip: West bounding coordinate, in decimal degrees

summary: Western-most limit of a bounding box, expressed in degrees of
                    longitude.

description: The westBoundingCoordinate field defines
                    the longitude of the western-most point of the bounding box that is being
                    described. A longitude coordinate is typed as a decimal, i.e.,
                    decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to
                    any precision desired. Fractions of a degree in minutes and seconds should be
                    converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are
                    not allowed. Longitudes east of the prime meridian must be specified by
                    a plus sign (+), or by the absence of a minus sign (-), and longitudes west of
                    the meridian shall be  prefixed with minus sign (-). In the case of a data set that comprises
                    all longitudes (e.g., a horizontal band between 2 parallels that fully
                    encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an
                    eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically
                    appropriate to specify both values as "180" (or any other meridian), but this could
                    also be interpreted as only the  meridian itself, so this is not recommended.
Diagram
Diagram
Type restriction of xs:decimal
Properties
content simple
Facets
maxInclusive 180.0
minInclusive -180.0
Source
<xs:element name="westBoundingCoordinate">
  <xs:annotation>
    <xs:documentation>tooltip: West bounding coordinate, in decimal degrees summary: Western-most limit of a bounding box, expressed in degrees of longitude. description: The westBoundingCoordinate field defines the longitude of the western-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:decimal">
      <xs:minInclusive value="-180.0"/>
      <xs:maxInclusive value="180.0"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / boundingCoordinates / eastBoundingCoordinate
Namespace No namespace
Annotations
tooltip: East bounding coordinate

summary: Eastern-most limit of a bounding box, expressed in degrees of
                    longitude.

description: The eastBoundingCoordinate field defines
                    the longitude of the eastern-most point of the bounding box that is being
                    described. A longitude coordinate is typed as a decimal, i.e.,
                    decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to
                    any precision desired. Fractions of a degree in minutes and seconds should be
                    converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are
                    not allowed. Longitudes east of the prime meridian must be specified by
                    a plus sign (+), or by the absence of a minus sign (-), and longitudes west of
                    the meridian shall be  prefixed with minus sign (-). In the case of a data set that comprises
                    all longitudes (e.g., a horizontal band between 2 parallels that fully
                    encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an
                    eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically
                    appropriate to specify both values as "180" (or any other meridian), but this could
                    also be interpreted as only the  meridian itself, so this is not recommended.
Diagram
Diagram
Type restriction of xs:decimal
Properties
content simple
Facets
maxInclusive 180.0
minInclusive -180.0
Source
<xs:element name="eastBoundingCoordinate">
  <xs:annotation>
    <xs:documentation>tooltip: East bounding coordinate summary: Eastern-most limit of a bounding box, expressed in degrees of longitude. description: The eastBoundingCoordinate field defines the longitude of the eastern-most point of the bounding box that is being described. A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-). In the case of a data set that comprises all longitudes (e.g., a horizontal band between 2 parallels that fully encompasses the earth ), please use a westBoundingCoordinate of -180.0, and an eastBoundingCoordinate of 180.0 (or +180.0). In this case, it could be considered geographically appropriate to specify both values as "180" (or any other meridian), but this could also be interpreted as only the meridian itself, so this is not recommended.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:decimal">
      <xs:minInclusive value="-180.0"/>
      <xs:maxInclusive value="180.0"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / boundingCoordinates / northBoundingCoordinate
Namespace No namespace
Annotations
tooltip: North bounding coordinate

summary: Northern-most lilmit of a bounding box expressed in latitude.

description: The northBoundingCoordinate field defines
                    the latitude of the northern-most point of the bounding box that is being
                    described. A latitude coordinate is typed as a decimal, i.e.,
                    decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to
                    any precision desired. Fractions of a degree in minutes and seconds should be
                    converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are
                    not allowed. Latitudes north of the equator must be denoted by
                    a plus sign (+), or by the absence of a minus sign (-), and latitudes south of
                    the equator shall be  prefixed with minus sign (-).  A location with latitude of +90 (90)
                     or -90 degrees will specify the position at the North or South Pole,
                    respectively.
Diagram
Diagram
Type restriction of xs:decimal
Properties
content simple
Facets
maxInclusive 90.0
minInclusive -90.0
Source
<xs:element name="northBoundingCoordinate">
  <xs:annotation>
    <xs:documentation>tooltip: North bounding coordinate summary: Northern-most lilmit of a bounding box expressed in latitude. description: The northBoundingCoordinate field defines the latitude of the northern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:decimal">
      <xs:minInclusive value="-90.0"/>
      <xs:maxInclusive value="90.0"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / boundingCoordinates / southBoundingCoordinate
Namespace No namespace
Annotations
tooltip: South bounding coordinate

summary: Southern-most limit of the bounding box expressed in latitude.

description: The southBoundingCoordinate field defines
                    the latitude of the southern-most point of the bounding box that is being
                    described. A latitude coordinate is typed as a decimal, i.e.,
                    decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to
                    any precision desired. Fractions of a degree in minutes and seconds should be
                    converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are
                    not allowed. Latitudes north of the equator must be denoted by
                    a plus sign (+), or by the absence of a minus sign (-), and latitudes south of
                    the equator shall be  prefixed with minus sign (-).  A location with latitude of +90 (90)
                     or -90 degrees will specify the position at the North or South Pole,
                    respectively.
Diagram
Diagram
Type restriction of xs:decimal
Properties
content simple
Facets
maxInclusive 90.0
minInclusive -90.0
Source
<xs:element name="southBoundingCoordinate">
  <xs:annotation>
    <xs:documentation>tooltip: South bounding coordinate summary: Southern-most limit of the bounding box expressed in latitude. description: The southBoundingCoordinate field defines the latitude of the southern-most point of the bounding box that is being described. A latitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'N' or north') are not allowed. Latitudes north of the equator must be denoted by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-). A location with latitude of +90 (90) or -90 degrees will specify the position at the North or South Pole, respectively.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:decimal">
      <xs:minInclusive value="-90.0"/>
      <xs:maxInclusive value="90.0"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / boundingCoordinates / boundingAltitudes
Namespace No namespace
Annotations
tooltip: Bounding altitudes

summary: The vertical limits of a data set expressed
                    by altitude.

description: The bounding altitude field is intended to
                    contain altitudinal (elevation) measurements for
                    the bounding box being described. It allows for minimum and
                    maximum altitude fields, as well as a field for the units
                    of measure. The combination of these fields provide the
                    vertical extent information for the bounding box.
Diagram
Diagram NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_boundingCoordinates_GeographicCoverage_GeographicCoverage_boundingCoordinates_boundingAltitudes_altitudeMinimum NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_boundingCoordinates_GeographicCoverage_GeographicCoverage_boundingCoordinates_boundingAltitudes_altitudeMaximum NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_boundingCoordinates_GeographicCoverage_GeographicCoverage_boundingCoordinates_boundingAltitudes_altitudeUnits
Properties
content complex
minOccurs 0
Model
Children altitudeMaximum, altitudeMinimum, altitudeUnits
Instance
<boundingAltitudes>
  <altitudeMinimum>{1,1}</altitudeMinimum>
  <altitudeMaximum>{1,1}</altitudeMaximum>
  <altitudeUnits>{1,1}</altitudeUnits>
</boundingAltitudes>
Source
<xs:element name="boundingAltitudes" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Bounding altitudes summary: The vertical limits of a data set expressed by altitude. description: The bounding altitude field is intended to contain altitudinal (elevation) measurements for the bounding box being described. It allows for minimum and maximum altitude fields, as well as a field for the units of measure. The combination of these fields provide the vertical extent information for the bounding box.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="altitudeMinimum" type="xs:decimal">
        <xs:annotation>
          <xs:documentation>tooltip: Minimum altitude summary: The minimum altitude extent of coverage. description: The minimum altitude extent of coverage for the bounding box that is being described. The minimum altitude should be in reference to a known datum (e.g., Mean Sea Level), which should be part of the geographicDescription.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="altitudeMaximum" type="xs:decimal">
        <xs:annotation>
          <xs:documentation>tooltip: Maximum altitude summary: The maximum altitude extent of coverage. description: The maximum altitude extent of coverage for the bounding box that is being described. The maximum altitude should be in reference to a known datum, which should be part of the geographicDescription.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="altitudeUnits" type="unit:LengthUnitType">
        <xs:annotation>
          <xs:documentation>tooltip: Altitude Units summary: The unit of altitude description: The unit that the altitude is expressed in. See the description under the Type definition</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / boundingCoordinates / boundingAltitudes / altitudeMinimum
Namespace No namespace
Annotations
tooltip: Minimum altitude

summary: The minimum altitude extent of
                          coverage.

description: The minimum altitude extent of
                          coverage for the bounding box that is being
                          described. The minimum altitude should be in
                          reference to a known datum (e.g., Mean Sea Level), which should be part of the geographicDescription.
Diagram
Diagram
Type xs:decimal
Properties
content simple
Source
<xs:element name="altitudeMinimum" type="xs:decimal">
  <xs:annotation>
    <xs:documentation>tooltip: Minimum altitude summary: The minimum altitude extent of coverage. description: The minimum altitude extent of coverage for the bounding box that is being described. The minimum altitude should be in reference to a known datum (e.g., Mean Sea Level), which should be part of the geographicDescription.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / boundingCoordinates / boundingAltitudes / altitudeMaximum
Namespace No namespace
Annotations
tooltip: Maximum altitude

summary: The maximum altitude extent of
                          coverage.

description: The maximum altitude extent of
                          coverage for the bounding box that is being
                          described. The maximum altitude should be in
                          reference to a known datum, which should be part of the geographicDescription.
Diagram
Diagram
Type xs:decimal
Properties
content simple
Source
<xs:element name="altitudeMaximum" type="xs:decimal">
  <xs:annotation>
    <xs:documentation>tooltip: Maximum altitude summary: The maximum altitude extent of coverage. description: The maximum altitude extent of coverage for the bounding box that is being described. The maximum altitude should be in reference to a known datum, which should be part of the geographicDescription.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / boundingCoordinates / boundingAltitudes / altitudeUnits
Namespace No namespace
Annotations
tooltip: Altitude Units

summary: The unit of altitude 

description: The unit that the altitude is expressed in. See the description under the Type definition
Diagram
Diagram units-2_2_0.tmp#LengthUnitType
Type unit:LengthUnitType
Properties
content simple
Facets
enumeration meter
enumeration nanometer
enumeration micrometer
enumeration micron
enumeration millimeter
enumeration centimeter
enumeration decimeter
enumeration dekameter
enumeration hectometer
enumeration kilometer
enumeration megameter
enumeration angstrom
enumeration inch
enumeration Foot_US
enumeration foot
enumeration Foot_Gold_Coast
enumeration fathom
enumeration nauticalMile
enumeration yard
enumeration Yard_Indian
enumeration Link_Clarke
enumeration Yard_Sears
enumeration mile
Source
<xs:element name="altitudeUnits" type="unit:LengthUnitType">
  <xs:annotation>
    <xs:documentation>tooltip: Altitude Units summary: The unit of altitude description: The unit that the altitude is expressed in. See the description under the Type definition</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / datasetGPolygon
Namespace No namespace
Annotations
tooltip: Polygon data set

summary: This construct creates a spatial ring with a
              hollow center.

description: This construct creates a spatial ring with a
              hollow center.  This doughnut shape is specified by the outer
              ring (datasetGPolygonOuterRing) and the inner exclusion zone
              (datasetGPolygonExclusionGRing) which can be thought of as the
              hole in the center of a doughnut.  This is useful for defining
              areas such as the shores of a pond where you only want to specify
              the shore excluding the pond itself.
Diagram
Diagram NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_datasetGPolygon_datasetGPolygonOuterGRing NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_datasetGPolygon_datasetGPolygonExclusionGRing
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children datasetGPolygonExclusionGRing, datasetGPolygonOuterGRing
Instance
<datasetGPolygon>
  <datasetGPolygonOuterGRing>{1,1}</datasetGPolygonOuterGRing>
  <datasetGPolygonExclusionGRing>{0,unbounded}</datasetGPolygonExclusionGRing>
</datasetGPolygon>
Source
<xs:element name="datasetGPolygon" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Polygon data set summary: This construct creates a spatial ring with a hollow center. description: This construct creates a spatial ring with a hollow center. This doughnut shape is specified by the outer ring (datasetGPolygonOuterRing) and the inner exclusion zone (datasetGPolygonExclusionGRing) which can be thought of as the hole in the center of a doughnut. This is useful for defining areas such as the shores of a pond where you only want to specify the shore excluding the pond itself.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="datasetGPolygonOuterGRing">
        <xs:annotation>
          <xs:documentation>tooltip: Outer polygon summary: The outer containment loop of a datasetGPolygon. description: The outer containment loop of a datasetGPolygon. This is the outer part of the doughnut shape that encompasses the broadest area of coverage. It can be created either by a gRing (list of points) or 3 or more gRingPoints. See the sub-elements and their Type definitions for more specific information. This element is generally analogous to the FGDC outer ring although somewhat differently specified. Documentation for an FGDC G-Ring states that 4 points are required to define a polygon, and the first and last should be identical. However this is not enforceable in XML Schema, and so in EML a minimum of 3 <gRingPoint>s is required to define a polygon, and it can be assumed that a polygon is closed by joining the last point to the first. XSL stylesheets that transform EML instances to the FGDC specification should repeat the first gRingPoint node as the last when creating a list of points.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:choice>
            <xs:sequence>
              <xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded">
                <xs:annotation>
                  <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. As a child of <datasetGPolygonOuterGRing> a minimum of 3 are required to define a polygon. The polygon is presumed to be closed. Please see the sub elements and the Type description for more information about creating a point location.</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:sequence>
            <xs:element name="gRing" type="GRingType">
              <xs:annotation>
                <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, The number of points in the string is not enforced by EML. However, authors should note that in order for this field is to be directly translated to FGDC, 4 points should be included in the string. See the Type for more information on constructing the string.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:choice>
        </xs:complexType>
      </xs:element>
      <xs:element name="datasetGPolygonExclusionGRing" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Exclusion polygon summary: Data Set G-Polygon Exclusion G-Ring, the closed nonintersecting boundary of a void area (or hole in an interior area). description: the closed nonintersecting boundary of a void area (or hole in an interior area). This is the center of the doughnut shape created by the datasetGPolygon. It can be created either by a gRing (list of points) or one or more gRingPoints. See the sub-elements and their Type definitions for more information. This element is generally analogous to an FGDC exclusion ring "Data Set G-Polygon Exclusion G-Ring", although it's children are somewhat differently described. Documentation for the FGDC component states that 4 points are required to define a polygon, and the first and last should be identical. However this EML element requires only one point so that a single point can be excluded, presumably, a single station. If multiple single stations are to be excluded, then authors should include multiple <datasetGPolygonExclusionGRing>s.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:choice>
            <xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. This is useful if you register your datasets by a single geospatial point, such as the lat/long of your research station. Please see the sub elements and the Type description for more information on constructing a gRingPoint</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="gRing" type="GRingType">
              <xs:annotation>
                <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, See the Type for more information</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:choice>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / datasetGPolygon / datasetGPolygonOuterGRing
Namespace No namespace
Annotations
tooltip: Outer polygon

summary: 
                      The outer containment loop of a datasetGPolygon.
                    

description: 
                      
                        The outer containment loop of a
                    datasetGPolygon.  This is the outer part of the doughnut
                    shape that encompasses the broadest area of coverage.
                    It can be created either by a gRing (list of points) or 3 or more gRingPoints.
                    See the sub-elements and their Type definitions for more specific
                    information.
                        
                    This element is generally analogous to the FGDC outer ring although
                    somewhat differently specified.  Documentation for an FGDC G-Ring
                    states that 4 points are required
                    to define a polygon, and the first and last should be identical.
                    However this is not enforceable in XML Schema, and so in EML
                    a minimum of 3 <gRingPoint>s is required to define a polygon, and
                    it can be assumed that a polygon is closed by joining the last point to the
                    first.
                    XSL stylesheets that transform EML instances to the FGDC specification
                    should repeat the first gRingPoint node as the last when creating a list of points.
Diagram
Diagram NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_datasetGPolygon_GeographicCoverage_GeographicCoverage_datasetGPolygon_datasetGPolygonOuterGRing_gRingPoint NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_datasetGPolygon_GeographicCoverage_GeographicCoverage_datasetGPolygon_datasetGPolygonOuterGRing_gRing
Properties
content complex
Model
Children gRing, gRingPoint
Instance
<datasetGPolygonOuterGRing>
  <gRingPoint>{3,unbounded}</gRingPoint>
  <gRing>{1,1}</gRing>
</datasetGPolygonOuterGRing>
Source
<xs:element name="datasetGPolygonOuterGRing">
  <xs:annotation>
    <xs:documentation>tooltip: Outer polygon summary: The outer containment loop of a datasetGPolygon. description: The outer containment loop of a datasetGPolygon. This is the outer part of the doughnut shape that encompasses the broadest area of coverage. It can be created either by a gRing (list of points) or 3 or more gRingPoints. See the sub-elements and their Type definitions for more specific information. This element is generally analogous to the FGDC outer ring although somewhat differently specified. Documentation for an FGDC G-Ring states that 4 points are required to define a polygon, and the first and last should be identical. However this is not enforceable in XML Schema, and so in EML a minimum of 3 <gRingPoint>s is required to define a polygon, and it can be assumed that a polygon is closed by joining the last point to the first. XSL stylesheets that transform EML instances to the FGDC specification should repeat the first gRingPoint node as the last when creating a list of points.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:sequence>
        <xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. As a child of <datasetGPolygonOuterGRing> a minimum of 3 are required to define a polygon. The polygon is presumed to be closed. Please see the sub elements and the Type description for more information about creating a point location.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:element name="gRing" type="GRingType">
        <xs:annotation>
          <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, The number of points in the string is not enforced by EML. However, authors should note that in order for this field is to be directly translated to FGDC, 4 points should be included in the string. See the Type for more information on constructing the string.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / datasetGPolygon / datasetGPolygonOuterGRing / gRingPoint
Namespace No namespace
Annotations
tooltip: G Ring Point

summary: A single geographic location

description: A single geographic location.  As a child of <datasetGPolygonOuterGRing>
                            a minimum of 3 are required to define a polygon. The polygon is presumed to be closed. Please see the sub elements and the Type description for more information about creating a point location.
Diagram
Diagram NO_NAMESPACE.tmp#GRingPointType_gRingLatitude NO_NAMESPACE.tmp#GRingPointType_gRingLongitude coverage-2_2_0.tmp#GRingPointType
Type GRingPointType
Properties
content complex
minOccurs 3
maxOccurs unbounded
Model
Children gRingLatitude, gRingLongitude
Instance
<gRingPoint>
  <gRingLatitude>{1,1}</gRingLatitude>
  <gRingLongitude>{1,1}</gRingLongitude>
</gRingPoint>
Source
<xs:element name="gRingPoint" type="GRingPointType" minOccurs="3" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. As a child of <datasetGPolygonOuterGRing> a minimum of 3 are required to define a polygon. The polygon is presumed to be closed. Please see the sub elements and the Type description for more information about creating a point location.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GRingPointType / gRingLatitude
Namespace No namespace
Annotations
tooltip: G-Ring Latitude

summary: 
            The latitude of a point of the
            g-ring.

description:  A latitude coordinate is typed as a decimal, i.e.,
                    decimal degrees from -90 to 90, inclusive. Decimal degrees may be expressed to
                    any precision desired. Fractions of a degree in minutes and seconds should be
                    converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'S' or 'south') are
                    not allowed. Latitudes north of the equator must be specified by
                    a plus sign (+), or by the absence of a minus sign (-), and latitudes south of
                    the equator shall be  prefixed with minus sign (-).
Diagram
Diagram
Type restriction of xs:decimal
Properties
content simple
Facets
maxInclusive 90.0
minInclusive -90.0
Source
<xs:element name="gRingLatitude">
  <xs:annotation>
    <xs:documentation>tooltip: G-Ring Latitude summary: The latitude of a point of the g-ring. description: A latitude coordinate is typed as a decimal, i.e., decimal degrees from -90 to 90, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'S' or 'south') are not allowed. Latitudes north of the equator must be specified by a plus sign (+), or by the absence of a minus sign (-), and latitudes south of the equator shall be prefixed with minus sign (-).</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:decimal">
      <xs:minInclusive value="-90.0"/>
      <xs:maxInclusive value="90.0"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GRingPointType / gRingLongitude
Namespace No namespace
Annotations
tooltip: G-Ring Longitude

summary: 

description: The longitude of a point of the
            g-ring A longitude coordinate is typed as a decimal, i.e.,
                    decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to
                    any precision desired. Fractions of a degree in minutes and seconds should be
                    converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are
                    not allowed. Longitudes east of the prime meridian must be specified by
                    a plus sign (+), or by the absence of a minus sign (-), and longitudes west of
                    the meridian shall be  prefixed with minus sign (-).
Diagram
Diagram
Type restriction of xs:decimal
Properties
content simple
Facets
maxInclusive 180.0
minInclusive -180.0
Source
<xs:element name="gRingLongitude">
  <xs:annotation>
    <xs:documentation>tooltip: G-Ring Longitude summary: description: The longitude of a point of the g-ring A longitude coordinate is typed as a decimal, i.e., decimal degrees from -180 to 180, inclusive. Decimal degrees may be expressed to any precision desired. Fractions of a degree in minutes and seconds should be converted to degree fractions. Strings denoting direction or hemisphere (e.g., 'W' or 'west') are not allowed. Longitudes east of the prime meridian must be specified by a plus sign (+), or by the absence of a minus sign (-), and longitudes west of the meridian shall be prefixed with minus sign (-).</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:decimal">
      <xs:minInclusive value="-180.0"/>
      <xs:maxInclusive value="180.0"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / datasetGPolygon / datasetGPolygonOuterGRing / gRing
Namespace No namespace
Annotations
tooltip: G-Ring

description: A set of ordered pairs of floating-point numbers,
        The number of points in the string is not enforced by EML.
        However, authors should note that in order for this field is to be directly translated to FGDC, 4 points should
        be included in the string. See the Type for more information on constructing the string.
Diagram
Diagram coverage-2_2_0.tmp#GRingType
Type GRingType
Properties
content simple
Source
<xs:element name="gRing" type="GRingType">
  <xs:annotation>
    <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, The number of points in the string is not enforced by EML. However, authors should note that in order for this field is to be directly translated to FGDC, 4 points should be included in the string. See the Type for more information on constructing the string.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / datasetGPolygon / datasetGPolygonExclusionGRing
Namespace No namespace
Annotations
tooltip: Exclusion polygon

summary: 
                    Data Set G-Polygon Exclusion G-Ring, the
                    closed nonintersecting boundary of a void area (or hole in
                    an interior area).
                    

description: 
                      
                         the
                    closed nonintersecting boundary of a void area (or hole in
                    an interior area).  This is the center of the doughnut
                    shape created by the datasetGPolygon. It can be created either by
                    a gRing (list of points) or one or more gRingPoints. See the sub-elements and their
                    Type definitions for more information.
                        
                        This element is generally analogous to an FGDC exclusion ring "Data Set G-Polygon
                        Exclusion G-Ring", although it's children are
                    somewhat differently described.  Documentation for the FGDC component states that
                    4 points are required to define a polygon, and the first and last should be identical.
                    However this EML element requires only one point so that a single point can be
                    excluded,  presumably, a single station.  If multiple single stations are to be
                    excluded, then authors should include multiple <datasetGPolygonExclusionGRing>s.
Diagram
Diagram NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_datasetGPolygon_GeographicCoverage_GeographicCoverage_datasetGPolygon_datasetGPolygonExclusionGRing_gRingPoint NO_NAMESPACE.tmp#GeographicCoverage_GeographicCoverage_datasetGPolygon_GeographicCoverage_GeographicCoverage_datasetGPolygon_datasetGPolygonExclusionGRing_gRing
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children gRing, gRingPoint
Instance
<datasetGPolygonExclusionGRing>
  <gRingPoint>{1,unbounded}</gRingPoint>
  <gRing>{1,1}</gRing>
</datasetGPolygonExclusionGRing>
Source
<xs:element name="datasetGPolygonExclusionGRing" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Exclusion polygon summary: Data Set G-Polygon Exclusion G-Ring, the closed nonintersecting boundary of a void area (or hole in an interior area). description: the closed nonintersecting boundary of a void area (or hole in an interior area). This is the center of the doughnut shape created by the datasetGPolygon. It can be created either by a gRing (list of points) or one or more gRingPoints. See the sub-elements and their Type definitions for more information. This element is generally analogous to an FGDC exclusion ring "Data Set G-Polygon Exclusion G-Ring", although it's children are somewhat differently described. Documentation for the FGDC component states that 4 points are required to define a polygon, and the first and last should be identical. However this EML element requires only one point so that a single point can be excluded, presumably, a single station. If multiple single stations are to be excluded, then authors should include multiple <datasetGPolygonExclusionGRing>s.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. This is useful if you register your datasets by a single geospatial point, such as the lat/long of your research station. Please see the sub elements and the Type description for more information on constructing a gRingPoint</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="gRing" type="GRingType">
        <xs:annotation>
          <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, See the Type for more information</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / datasetGPolygon / datasetGPolygonExclusionGRing / gRingPoint
Namespace No namespace
Annotations
tooltip: G Ring Point

summary: A single geographic location

description: A single geographic location.  This is useful if you
        register your datasets by a single geospatial point, such as the
        lat/long of your research station. Please see the sub elements and the Type description
		for more information on constructing a gRingPoint
Diagram
Diagram NO_NAMESPACE.tmp#GRingPointType_gRingLatitude NO_NAMESPACE.tmp#GRingPointType_gRingLongitude coverage-2_2_0.tmp#GRingPointType
Type GRingPointType
Properties
content complex
maxOccurs unbounded
Model
Children gRingLatitude, gRingLongitude
Instance
<gRingPoint>
  <gRingLatitude>{1,1}</gRingLatitude>
  <gRingLongitude>{1,1}</gRingLongitude>
</gRingPoint>
Source
<xs:element name="gRingPoint" type="GRingPointType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: G Ring Point summary: A single geographic location description: A single geographic location. This is useful if you register your datasets by a single geospatial point, such as the lat/long of your research station. Please see the sub elements and the Type description for more information on constructing a gRingPoint</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element GeographicCoverage / datasetGPolygon / datasetGPolygonExclusionGRing / gRing
Namespace No namespace
Annotations
tooltip: G-Ring

description: A set of ordered pairs of floating-point numbers,
        See the Type for more information
Diagram
Diagram coverage-2_2_0.tmp#GRingType
Type GRingType
Properties
content simple
Source
<xs:element name="gRing" type="GRingType">
  <xs:annotation>
    <xs:documentation>tooltip: G-Ring description: A set of ordered pairs of floating-point numbers, See the Type for more information</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element Coverage / temporalCoverage
Namespace No namespace
Annotations
tooltip: Temporal coverage

summary: Temporal coverage information.

description: This field specifies temporal coverage, and
              allows coverages to be a single point in time, multiple points in
              time, or a range of dates. Dates can be expressed in terms of both
              calendar dates and geologic dating systems.
Diagram
Diagram NO_NAMESPACE.tmp#TemporalCoverage_id NO_NAMESPACE.tmp#TemporalCoverage_singleDateTime NO_NAMESPACE.tmp#TemporalCoverage_rangeOfDates NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#TemporalCoverage NO_NAMESPACE.tmp#Coverage_Coverage_temporalCoverage_system NO_NAMESPACE.tmp#Coverage_Coverage_temporalCoverage_scope
Type extension of TemporalCoverage
Type hierarchy
Properties
content complex
Model
Children rangeOfDates, references, singleDateTime
Instance
<temporalCoverage id="" scope="document" system="">
  <singleDateTime>{1,unbounded}</singleDateTime>
  <rangeOfDates>{1,1}</rangeOfDates>
  <references system="">{1,1}</references>
</temporalCoverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="temporalCoverage">
  <xs:annotation>
    <xs:documentation>tooltip: Temporal coverage summary: Temporal coverage information. description: This field specifies temporal coverage, and allows coverages to be a single point in time, multiple points in time, or a range of dates. Dates can be expressed in terms of both calendar dates and geologic dating systems.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="TemporalCoverage">
        <xs:attribute name="system" type="res:SystemType" use="optional"/>
        <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TemporalCoverage / singleDateTime
Namespace No namespace
Annotations
tooltip: Single Date/Time

summary: Means of encoding a single date and
              time

description: The singleDateTime field is intended to
              describe a
              single date and time for an event. There is a choice between two
              options: a calendar date with a time, or a geologic
              age.
Diagram
Diagram NO_NAMESPACE.tmp#SingleDateTimeType_calendarDate NO_NAMESPACE.tmp#SingleDateTimeType_time NO_NAMESPACE.tmp#SingleDateTimeType_alternativeTimeScale coverage-2_2_0.tmp#SingleDateTimeType
Type SingleDateTimeType
Properties
content complex
maxOccurs unbounded
Model
Children alternativeTimeScale, calendarDate, time
Instance
<singleDateTime>
  <calendarDate>{1,1}</calendarDate>
  <time>{0,1}</time>
  <alternativeTimeScale>{1,1}</alternativeTimeScale>
</singleDateTime>
Source
<xs:element name="singleDateTime" type="SingleDateTimeType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Single Date/Time summary: Means of encoding a single date and time description: The singleDateTime field is intended to describe a single date and time for an event. There is a choice between two options: a calendar date with a time, or a geologic age.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element SingleDateTimeType / calendarDate
Namespace No namespace
Annotations
tooltip: Calendar date

summary: The calendar date for an event.

description: The calendar date field is used to express a
              date, giving the year, month, and day. The format should be one
              that complies with the International Standards Organization's
              standard 8601. The recommended format for EML is YYYY-MM-DD,
              where Y is the four digit year, M is the two digit month code
              (01 - 12, where January = 01), and D is the two digit day of
              the month (01 - 31). This field can also be used to enter just
	      the year portion of a date.
Diagram
Diagram resource-2_2_0.tmp#yearDate
Type yearDate
Properties
content simple
Source
<xs:element name="calendarDate" type="res:yearDate">
  <xs:annotation>
    <xs:documentation>tooltip: Calendar date summary: The calendar date for an event. description: The calendar date field is used to express a date, giving the year, month, and day. The format should be one that complies with the International Standards Organization's standard 8601. The recommended format for EML is YYYY-MM-DD, where Y is the four digit year, M is the two digit month code (01 - 12, where January = 01), and D is the two digit day of the month (01 - 31). This field can also be used to enter just the year portion of a date.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element SingleDateTimeType / time
Namespace No namespace
Annotations
tooltip: Time of day

summary: The time of day for an event.

description: The time field is used to express the hour
              (and optionally minute, or minute and second) of the day for an
              event, and should comply with the International Standards
              Organization's standard 8601. The recommended format for EML is
              hh:mm:ssTZD, where hh is the two digit hour of the day, mm is
              the two digit minute of the hour, and ss is the two digit
              second of the minute. TZD stands for Time Zone Designator which
              is used to handle time zone offsets. Times may be expressed in
              two ways: 1) UTC (Coordinated Universal Time, also known as
              Greenwich Mean Time, or GMT), with a special UTC designator
              ("Z"), 2) local time, together with a time zone offset in hours
              and minutes. A time zone offset of "+hh:mm" indicates that the
              date or time uses a local time zone which is "hh" hours and "mm"
              minutes ahead of UTC. A time zone offset of "-hh:mm" indicates
              a local time zone which is "hh" hours
              and "mm" minutes behind UTC.
Diagram
Diagram
Type xs:time
Properties
content simple
minOccurs 0
Source
<xs:element name="time" type="xs:time" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Time of day summary: The time of day for an event. description: The time field is used to express the hour (and optionally minute, or minute and second) of the day for an event, and should comply with the International Standards Organization's standard 8601. The recommended format for EML is hh:mm:ssTZD, where hh is the two digit hour of the day, mm is the two digit minute of the hour, and ss is the two digit second of the minute. TZD stands for Time Zone Designator which is used to handle time zone offsets. Times may be expressed in two ways: 1) UTC (Coordinated Universal Time, also known as Greenwich Mean Time, or GMT), with a special UTC designator ("Z"), 2) local time, together with a time zone offset in hours and minutes. A time zone offset of "+hh:mm" indicates that the date or time uses a local time zone which is "hh" hours and "mm" minutes ahead of UTC. A time zone offset of "-hh:mm" indicates a local time zone which is "hh" hours and "mm" minutes behind UTC.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element SingleDateTimeType / alternativeTimeScale
Namespace No namespace
Annotations
tooltip: Alternative Time Scale

summary: A name, code, or date describing an event or period
            in an alternative time scale, such as one of the geologic time
            scales.

description: A name, code, or date describing an event or
            period in an alternative time scale, for instance as an absolute
            date calculated using a named dating method, or as a relative
            date that is drawn from stratigraphy or biostratigraphy.
            Calendar dates as provided in the ISO
            8601 dating system used in the standard CSDGM are not adequate to
            describe geologic time periods. Absolute geologic time is usually
            measured in millions of years before present, but may use different
            units and relative base times. Relative geologic time is measured by
            subdivisions of the earth's geology. in an order based upon relative
            age, most commonly, vertical or stratigraphic position. The actual
            dating systems used in geologic studies often tie relative times
            measured through stratigraphy or biostratigraphy to a particular
            absolute time using radioisotope dating techniques, among others. As
            these methods for absolute dating have improved, the estimates of
            the dates for strata have changed, consequently, it would be
            inaccurate to record absolute dates in situations where relative
            dates were measured.  This structure is provided as an optional
            alternative to the standard calendar dates provided by ISO 8601.
Diagram
Diagram NO_NAMESPACE.tmp#SingleDateTimeType_SingleDateTimeType_alternativeTimeScale_timeScaleName NO_NAMESPACE.tmp#SingleDateTimeType_SingleDateTimeType_alternativeTimeScale_timeScaleAgeEstimate NO_NAMESPACE.tmp#SingleDateTimeType_SingleDateTimeType_alternativeTimeScale_timeScaleAgeUncertainty NO_NAMESPACE.tmp#SingleDateTimeType_SingleDateTimeType_alternativeTimeScale_timeScaleAgeExplanation NO_NAMESPACE.tmp#SingleDateTimeType_SingleDateTimeType_alternativeTimeScale_timeScaleCitation
Properties
content complex
Model
Children timeScaleAgeEstimate, timeScaleAgeExplanation, timeScaleAgeUncertainty, timeScaleCitation, timeScaleName
Instance
<alternativeTimeScale>
  <timeScaleName>{1,1}</timeScaleName>
  <timeScaleAgeEstimate>{1,1}</timeScaleAgeEstimate>
  <timeScaleAgeUncertainty>{0,1}</timeScaleAgeUncertainty>
  <timeScaleAgeExplanation>{0,1}</timeScaleAgeExplanation>
  <timeScaleCitation id="" scope="document" system="">{0,unbounded}</timeScaleCitation>
</alternativeTimeScale>
Source
<xs:element name="alternativeTimeScale">
  <xs:annotation>
    <xs:documentation>tooltip: Alternative Time Scale summary: A name, code, or date describing an event or period in an alternative time scale, such as one of the geologic time scales. description: A name, code, or date describing an event or period in an alternative time scale, for instance as an absolute date calculated using a named dating method, or as a relative date that is drawn from stratigraphy or biostratigraphy. Calendar dates as provided in the ISO 8601 dating system used in the standard CSDGM are not adequate to describe geologic time periods. Absolute geologic time is usually measured in millions of years before present, but may use different units and relative base times. Relative geologic time is measured by subdivisions of the earth's geology. in an order based upon relative age, most commonly, vertical or stratigraphic position. The actual dating systems used in geologic studies often tie relative times measured through stratigraphy or biostratigraphy to a particular absolute time using radioisotope dating techniques, among others. As these methods for absolute dating have improved, the estimates of the dates for strata have changed, consequently, it would be inaccurate to record absolute dates in situations where relative dates were measured. This structure is provided as an optional alternative to the standard calendar dates provided by ISO 8601.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="timeScaleName" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: alternative time scale summary: Name of a recognized alternative time scale. description: Name of a recognized alternative time scale. This includes 'Absolute' as the name of the time scale for measuring geologic dates before the present and names of geologic dating systems that are arrangements of symbols or names in order of relative geologic time.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="timeScaleAgeEstimate" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Time scale age estimate summary: description: Either an absolute date or a relative age name describing an event or period in an alternative time scale such as the Geologic Time Scale.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="timeScaleAgeUncertainty" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Time scale age uncertainty summary: The error estimate for the alternative time scale. description: The error estimate for the alternative time. This should include the units of measure, a description of what the error estimate represents and how it was calculated.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="timeScaleAgeExplanation" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Time scale age explanation summary: The name and/or description of the method used to calculate the time scale age estimate. description: The name and/or description of the method used to calculate the age estimate. Detailed information about the method may be provided through references contained in the Time Scale Citation field.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="timeScaleCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Time Scale citation summary: Citation for works providing detailed information about any element of the time scale age. description: Citation for works providing detailed information about any element of the time scale age.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element SingleDateTimeType / alternativeTimeScale / timeScaleName
Namespace No namespace
Annotations
tooltip: alternative time scale

summary: Name of a recognized alternative time
                  scale.

description: Name of a recognized alternative time scale.
                  This includes 'Absolute' as the name of the time scale for
                  measuring geologic dates before the present and names of
                  geologic dating systems that are arrangements of symbols or
                  names in order of relative geologic time.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="timeScaleName" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: alternative time scale summary: Name of a recognized alternative time scale. description: Name of a recognized alternative time scale. This includes 'Absolute' as the name of the time scale for measuring geologic dates before the present and names of geologic dating systems that are arrangements of symbols or names in order of relative geologic time.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element SingleDateTimeType / alternativeTimeScale / timeScaleAgeEstimate
Namespace No namespace
Annotations
tooltip: Time scale age estimate

summary: 

description: Either an absolute date or a relative age
                  name describing an event or period in an alternative time
                  scale such as the Geologic Time Scale.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="timeScaleAgeEstimate" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Time scale age estimate summary: description: Either an absolute date or a relative age name describing an event or period in an alternative time scale such as the Geologic Time Scale.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element SingleDateTimeType / alternativeTimeScale / timeScaleAgeUncertainty
Namespace No namespace
Annotations
tooltip: Time scale age uncertainty

summary: The error estimate for the alternative time
                  scale.

description: The error estimate for the alternative time.
                  This should include the units of measure, a description of
                  what the error estimate represents and how it was
                  calculated.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="timeScaleAgeUncertainty" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Time scale age uncertainty summary: The error estimate for the alternative time scale. description: The error estimate for the alternative time. This should include the units of measure, a description of what the error estimate represents and how it was calculated.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element SingleDateTimeType / alternativeTimeScale / timeScaleAgeExplanation
Namespace No namespace
Annotations
tooltip: Time scale age explanation

summary: The name and/or description of the method used to
                  calculate the time scale age estimate.

description: The name and/or description of the method
                  used to calculate the age estimate. Detailed information
                  about the method may be provided through references
                  contained in the Time Scale Citation field.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="timeScaleAgeExplanation" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Time scale age explanation summary: The name and/or description of the method used to calculate the time scale age estimate. description: The name and/or description of the method used to calculate the age estimate. Detailed information about the method may be provided through references contained in the Time Scale Citation field.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element SingleDateTimeType / alternativeTimeScale / timeScaleCitation
Namespace No namespace
Annotations
tooltip: Time Scale citation

summary: Citation for works providing detailed information
                  about any element of the time scale age.

description: Citation for works providing detailed
                  information about any element of the time scale
                  age.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<timeScaleCitation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</timeScaleCitation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="timeScaleCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Time Scale citation summary: Citation for works providing detailed information about any element of the time scale age. description: Citation for works providing detailed information about any element of the time scale age.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element CitationType / contact
Namespace No namespace
Annotations
tooltip: Contact

summary: An optional contact individual for this citation

description: The contact field contains information about an alternate person to be contacted
              about this citation. Usually, the first author serves as the contact for a citation resource, e.g., a reprint request. In some cases, an alternate individual(s) may serve that function, and can be indicated here. Since contact is of the type rp:ResponsibleParty, a reference may be used.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<contact id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</contact>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="contact" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Contact summary: An optional contact individual for this citation description: The contact field contains information about an alternate person to be contacted about this citation. Usually, the first author serves as the contact for a citation resource, e.g., a reprint request. In some cases, an alternate individual(s) may serve that function, and can be indicated here. Since contact is of the type rp:ResponsibleParty, a reference may be used.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / article
Namespace No namespace
Annotations
tooltip: article

summary: Information for full citation of a journal article
                or other periodical article.

description: The article field provides sub-fields for a
                full citation of an article in a journal or other
                periodical.
Diagram
Diagram NO_NAMESPACE.tmp#Article_journal NO_NAMESPACE.tmp#Article_volume NO_NAMESPACE.tmp#Article_issue NO_NAMESPACE.tmp#Article_pageRange NO_NAMESPACE.tmp#Article_publisher NO_NAMESPACE.tmp#Article_publicationPlace NO_NAMESPACE.tmp#Article_ISSN literature-2_2_0.tmp#Article
Type Article
Properties
content complex
Model
journal , volume{0,1} , issue{0,1} , pageRange{0,1} , publisher{0,1} , publicationPlace{0,1} , ISSN{0,1}
Children ISSN, issue, journal, pageRange, publicationPlace, publisher, volume
Instance
<article>
  <journal>{1,1}</journal>
  <volume>{0,1}</volume>
  <issue>{0,1}</issue>
  <pageRange>{0,1}</pageRange>
  <publisher id="" scope="document" system="">{0,1}</publisher>
  <publicationPlace>{0,1}</publicationPlace>
  <ISSN>{0,1}</ISSN>
</article>
Source
<xs:element name="article" type="Article">
  <xs:annotation>
    <xs:documentation>tooltip: article summary: Information for full citation of a journal article or other periodical article. description: The article field provides sub-fields for a full citation of an article in a journal or other periodical.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Article / journal
Namespace No namespace
Annotations
tooltip: Journal Name

summary: The name of the journal, magazine, newspaper, zine,
            etc... in which the article was published.

description: The name of the journal, magazine, newspaper,
            zine, etc... in which the article was published.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="journal" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Journal Name summary: The name of the journal, magazine, newspaper, zine, etc... in which the article was published. description: The name of the journal, magazine, newspaper, zine, etc... in which the article was published.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Article / volume
Namespace No namespace
Annotations
tooltip: Journal Volume

summary: The volume of the journal in which the article
            appears

description: The volume field is used to describe the volume of
            the journal in which the article appears.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="volume" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Journal Volume summary: The volume of the journal in which the article appears description: The volume field is used to describe the volume of the journal in which the article appears.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Article / issue
Namespace No namespace
Annotations
tooltip: Journal issue

summary: The issue of the journal in which the article
            appears

description: The issue field is used to describe the issue of
            the journal in which the article appears.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="issue" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Journal issue summary: The issue of the journal in which the article appears description: The issue field is used to describe the issue of the journal in which the article appears.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Article / pageRange
Namespace No namespace
Annotations
tooltip: Journal Pages

summary: The beginning and end page numbers of the journal
            article

description: The page range field is used for the beginning and
            ending pages of the journal article that is being
            documented.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="pageRange" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Journal Pages summary: The beginning and end page numbers of the journal article description: The page range field is used for the beginning and ending pages of the journal article that is being documented.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Article / publisher
Namespace No namespace
Annotations
tooltip: Publisher

summary: Organization that actually publishes the
            article

description: The organization that physically puts together the
            article and publishes it.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
minOccurs 0
Model
((individualName | organizationName | positionName) , address* , phone* , electronicMailAddress* , onlineUrl* , userId*) | (references)
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<publisher id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</publisher>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the article description: The organization that physically puts together the article and publishes it.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Article / publicationPlace
Namespace No namespace
Annotations
tooltip: Publication Place

summary: The location at which the work was
            published.

description: The location at which the work was published. This
            is usually the name of the city in which the publishing house
            produced the work.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Article / ISSN
Namespace No namespace
Annotations
tooltip: International Standard Serial Number

summary: The unique Internation Standard Serial
            Number

description: The ISSN, or International Standard Serial Number
            that has been assigned to this literature
            resource.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="ISSN" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: International Standard Serial Number summary: The unique Internation Standard Serial Number description: The ISSN, or International Standard Serial Number that has been assigned to this literature resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / book
Namespace No namespace
Annotations
tooltip: Book

summary: Information for full citation of a
                book

description: The book field provides sub-fields for a full
                citation of a book.
Diagram
Diagram NO_NAMESPACE.tmp#Book_publisher NO_NAMESPACE.tmp#Book_publicationPlace NO_NAMESPACE.tmp#Book_edition NO_NAMESPACE.tmp#Book_volume NO_NAMESPACE.tmp#Book_numberOfVolumes NO_NAMESPACE.tmp#Book_totalPages NO_NAMESPACE.tmp#Book_totalFigures NO_NAMESPACE.tmp#Book_totalTables NO_NAMESPACE.tmp#Book_ISBN literature-2_2_0.tmp#Book
Type Book
Properties
content complex
Model
Children ISBN, edition, numberOfVolumes, publicationPlace, publisher, totalFigures, totalPages, totalTables, volume
Instance
<book>
  <publisher id="" scope="document" system="">{1,1}</publisher>
  <publicationPlace>{0,1}</publicationPlace>
  <edition>{0,1}</edition>
  <volume>{0,1}</volume>
  <numberOfVolumes>{0,1}</numberOfVolumes>
  <totalPages>{0,1}</totalPages>
  <totalFigures>{0,1}</totalFigures>
  <totalTables>{0,1}</totalTables>
  <ISBN>{0,1}</ISBN>
</book>
Source
<xs:element name="book" type="Book">
  <xs:annotation>
    <xs:documentation>tooltip: Book summary: Information for full citation of a book description: The book field provides sub-fields for a full citation of a book.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Book / publisher
Namespace No namespace
Annotations
tooltip: Publisher

summary: Organization that actually publishes the
            book

description: The organization that physically puts together the
            book and publishes it.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<publisher id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</publisher>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="publisher" type="rp:ResponsibleParty">
  <xs:annotation>
    <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the book description: The organization that physically puts together the book and publishes it.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Book / publicationPlace
Namespace No namespace
Annotations
tooltip: Publication Place

summary: The location at which the work was
            published.

description: The location at which the work was published. This
            is usually the name of the city in which the publishing house
            produced the work.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Book / edition
Namespace No namespace
Annotations
tooltip: Book edition

summary: The edition of the book being described.

description: The edition field is to document the edition of
            the book that is being described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="edition" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Book edition summary: The edition of the book being described. description: The edition field is to document the edition of the book that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Book / volume
Namespace No namespace
Annotations
tooltip: Book volume

summary: The volume of the book that is part of a
            series.

description: The volume field is used to describe the volume
            number of a book that is part of a multi-volume series of
            books.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="volume" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Book volume summary: The volume of the book that is part of a series. description: The volume field is used to describe the volume number of a book that is part of a multi-volume series of books.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Book / numberOfVolumes
Namespace No namespace
Annotations
tooltip: Number of Volumes

summary: Number of volumes in a collection

description: Number of volumes in a
            collection
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="numberOfVolumes" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Number of Volumes summary: Number of volumes in a collection description: Number of volumes in a collection</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Book / totalPages
Namespace No namespace
Annotations
tooltip: Total book pages

summary: The total number of pages in the book.

description: The total pages field is used to describe the
            total number of pages in the book that is being
            described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Total book pages summary: The total number of pages in the book. description: The total pages field is used to describe the total number of pages in the book that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Book / totalFigures
Namespace No namespace
Annotations
tooltip: Number of figures in book

summary: The total number of figures in the book.

description: the total figures field is used to describe the
            total number of figures, diagrams, and plates in the book that is
            being documented.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalFigures" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Number of figures in book summary: The total number of figures in the book. description: the total figures field is used to describe the total number of figures, diagrams, and plates in the book that is being documented.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Book / totalTables
Namespace No namespace
Annotations
tooltip: Number of tables in book

summary: The total number of tables in a book.

description: The total tables field is used to describe the
            total number of tables that are present in the book that is being
            documented.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalTables" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Number of tables in book summary: The total number of tables in a book. description: The total tables field is used to describe the total number of tables that are present in the book that is being documented.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Book / ISBN
Namespace No namespace
Annotations
tooltip: International Standard Book Number

summary: The unique Internation Standard Book
            Number

description: The ISBN, or International Standard Book Number
            that has been assigned to this literature
            resource.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="ISBN" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: International Standard Book Number summary: The unique Internation Standard Book Number description: The ISBN, or International Standard Book Number that has been assigned to this literature resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / chapter
Namespace No namespace
Annotations
tooltip: Book Chapter

summary: Information for citation of a chapter in a
                book

description: The book chapter allows citation of a single
                chapter or section of a book. The "creator" for a book chapter
                are the chapter's authors, while the "editor" is the book
                editors. Likewise, "title" is the chapter title, while
                "bookTitle" is the title of the whole book.
Diagram
Diagram NO_NAMESPACE.tmp#Book_publisher NO_NAMESPACE.tmp#Book_publicationPlace NO_NAMESPACE.tmp#Book_edition NO_NAMESPACE.tmp#Book_volume NO_NAMESPACE.tmp#Book_numberOfVolumes NO_NAMESPACE.tmp#Book_totalPages NO_NAMESPACE.tmp#Book_totalFigures NO_NAMESPACE.tmp#Book_totalTables NO_NAMESPACE.tmp#Book_ISBN literature-2_2_0.tmp#Book NO_NAMESPACE.tmp#Chapter_chapterNumber NO_NAMESPACE.tmp#Chapter_editor NO_NAMESPACE.tmp#Chapter_bookTitle NO_NAMESPACE.tmp#Chapter_pageRange literature-2_2_0.tmp#Chapter
Type Chapter
Type hierarchy
Properties
content complex
Model
Children ISBN, bookTitle, chapterNumber, edition, editor, numberOfVolumes, pageRange, publicationPlace, publisher, totalFigures, totalPages, totalTables, volume
Instance
<chapter>
  <publisher id="" scope="document" system="">{1,1}</publisher>
  <publicationPlace>{0,1}</publicationPlace>
  <edition>{0,1}</edition>
  <volume>{0,1}</volume>
  <numberOfVolumes>{0,1}</numberOfVolumes>
  <totalPages>{0,1}</totalPages>
  <totalFigures>{0,1}</totalFigures>
  <totalTables>{0,1}</totalTables>
  <ISBN>{0,1}</ISBN>
  <chapterNumber>{0,1}</chapterNumber>
  <editor id="" scope="document" system="">{1,unbounded}</editor>
  <bookTitle>{1,1}</bookTitle>
  <pageRange>{0,1}</pageRange>
</chapter>
Source
<xs:element name="chapter" type="Chapter">
  <xs:annotation>
    <xs:documentation>tooltip: Book Chapter summary: Information for citation of a chapter in a book description: The book chapter allows citation of a single chapter or section of a book. The "creator" for a book chapter are the chapter's authors, while the "editor" is the book editors. Likewise, "title" is the chapter title, while "bookTitle" is the title of the whole book.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Chapter / chapterNumber
Namespace No namespace
Annotations
tooltip: Chapter number

summary: The chapter number of interest within a
                book

description: The chapter number of the chapter of a book
                that is being described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="chapterNumber" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Chapter number summary: The chapter number of interest within a book description: The chapter number of the chapter of a book that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Chapter / editor
Namespace No namespace
Annotations
tooltip: Book editor

summary: The name of the editor of the book.

description: The book editor field is used to document the
                name of the editor of the book that is being described. The
                editor may be a person, organization, or a role within an
                organization.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<editor id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</editor>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="editor" type="rp:ResponsibleParty" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Book editor summary: The name of the editor of the book. description: The book editor field is used to document the name of the editor of the book that is being described. The editor may be a person, organization, or a role within an organization.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Chapter / bookTitle
Namespace No namespace
Annotations
tooltip: Book title

summary: The title of the book.

description: The book title field is used to document the
                title of the book that is being described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="bookTitle" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Book title summary: The title of the book. description: The book title field is used to document the title of the book that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Chapter / pageRange
Namespace No namespace
Annotations
tooltip: Chapter page range

summary: The beginning and ending page numbers of a
                chapter.

description: The page range field is used to document the
                beginning and ending pages of a chapter in a
                book.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="pageRange" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Chapter page range summary: The beginning and ending page numbers of a chapter. description: The page range field is used to document the beginning and ending pages of a chapter in a book.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / editedBook
Namespace No namespace
Annotations
tooltip: Book

summary: Information for full citation of an edited
                book

description: The edited book represents a book which was
                edited by one or more editors, but whose chapters were possibly
                authored by others. The editors of an edited book should be
                listed in the "creator" field.
Diagram
Diagram NO_NAMESPACE.tmp#Book_publisher NO_NAMESPACE.tmp#Book_publicationPlace NO_NAMESPACE.tmp#Book_edition NO_NAMESPACE.tmp#Book_volume NO_NAMESPACE.tmp#Book_numberOfVolumes NO_NAMESPACE.tmp#Book_totalPages NO_NAMESPACE.tmp#Book_totalFigures NO_NAMESPACE.tmp#Book_totalTables NO_NAMESPACE.tmp#Book_ISBN literature-2_2_0.tmp#Book
Type Book
Properties
content complex
Model
Children ISBN, edition, numberOfVolumes, publicationPlace, publisher, totalFigures, totalPages, totalTables, volume
Instance
<editedBook>
  <publisher id="" scope="document" system="">{1,1}</publisher>
  <publicationPlace>{0,1}</publicationPlace>
  <edition>{0,1}</edition>
  <volume>{0,1}</volume>
  <numberOfVolumes>{0,1}</numberOfVolumes>
  <totalPages>{0,1}</totalPages>
  <totalFigures>{0,1}</totalFigures>
  <totalTables>{0,1}</totalTables>
  <ISBN>{0,1}</ISBN>
</editedBook>
Source
<xs:element name="editedBook" type="Book">
  <xs:annotation>
    <xs:documentation>tooltip: Book summary: Information for full citation of an edited book description: The edited book represents a book which was edited by one or more editors, but whose chapters were possibly authored by others. The editors of an edited book should be listed in the "creator" field.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / manuscript
Namespace No namespace
Annotations
tooltip: unpublished manuscipt

summary: Information about an unpublished
                manuscript

description: The manuscript field provides sub-fields for a
                full citation of an unpublished manuscript.
Diagram
Diagram NO_NAMESPACE.tmp#Manuscript_institution NO_NAMESPACE.tmp#Manuscript_totalPages literature-2_2_0.tmp#Manuscript
Type Manuscript
Properties
content complex
Model
Children institution, totalPages
Instance
<manuscript>
  <institution id="" scope="document" system="">{1,unbounded}</institution>
  <totalPages>{0,1}</totalPages>
</manuscript>
Source
<xs:element name="manuscript" type="Manuscript">
  <xs:annotation>
    <xs:documentation>tooltip: unpublished manuscipt summary: Information about an unpublished manuscript description: The manuscript field provides sub-fields for a full citation of an unpublished manuscript.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Manuscript / institution
Namespace No namespace
Annotations
tooltip: Manuscript publication information

summary: The address and contact information needed to request
            a manuscript.

description: The institution information field is used to
            provide contact and address information that would be needed to
            request an unpublished manuscript
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<institution id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</institution>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="institution" type="rp:ResponsibleParty" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Manuscript publication information summary: The address and contact information needed to request a manuscript. description: The institution information field is used to provide contact and address information that would be needed to request an unpublished manuscript</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Manuscript / totalPages
Namespace No namespace
Annotations
tooltip: Total manuscript pages

summary: The total number of pages in the
            manuscript.

description: The total pages field is used to describe the
            total number of pages in the manuscript that is being
            described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Total manuscript pages summary: The total number of pages in the manuscript. description: The total pages field is used to describe the total number of pages in the manuscript that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / report
Namespace No namespace
Annotations
tooltip: Report

summary: Information about a report published by an
                institution.

description: The report may be self published by the
                institution or through a publisher. They usually are available
                by request to the institution or can be purchased from the
                publisher.
Diagram
Diagram NO_NAMESPACE.tmp#Report_reportNumber NO_NAMESPACE.tmp#Report_publisher NO_NAMESPACE.tmp#Report_publicationPlace NO_NAMESPACE.tmp#Report_totalPages literature-2_2_0.tmp#Report
Type Report
Properties
content complex
Model
Children publicationPlace, publisher, reportNumber, totalPages
Instance
<report>
  <reportNumber>{0,1}</reportNumber>
  <publisher id="" scope="document" system="">{0,1}</publisher>
  <publicationPlace>{0,1}</publicationPlace>
  <totalPages>{0,1}</totalPages>
</report>
Source
<xs:element name="report" type="Report">
  <xs:annotation>
    <xs:documentation>tooltip: Report summary: Information about a report published by an institution. description: The report may be self published by the institution or through a publisher. They usually are available by request to the institution or can be purchased from the publisher.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Report / reportNumber
Namespace No namespace
Annotations
tooltip: Report Number

summary: The unique identification number assigned to the
            report.

description: The report number field is used to describe the
            unique identification number that has been issued by the report
            institution for the report being described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="reportNumber" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Report Number summary: The unique identification number assigned to the report. description: The report number field is used to describe the unique identification number that has been issued by the report institution for the report being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Report / publisher
Namespace No namespace
Annotations
tooltip: Publisher

summary: Organization that actually publishes the
            report

description: The organization that physically put together the
            report and publishes it.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
minOccurs 0
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<publisher id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</publisher>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the report description: The organization that physically put together the report and publishes it.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Report / publicationPlace
Namespace No namespace
Annotations
tooltip: Publication Place

summary: The location at which the work was
            published.

description: The location at which the work was published. This
            is usually the name of the city in which the publishing house
            produced the work.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Report / totalPages
Namespace No namespace
Annotations
tooltip: Total report pages

summary: The total number of pages in the report.

description: The total pages field is used to describe the
            total number of pages in the report that is being
            described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Total report pages summary: The total number of pages in the report. description: The total pages field is used to describe the total number of pages in the report that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / thesis
Namespace No namespace
Annotations
tooltip: Thesis as part of a degree

summary: Information about a thesis that has been written
                as part of a degree requirement and is frequently published in
                small numbers by the degree awarding institution.

description: Information about a thesis that has been
                written as part of a degree requirement and is frequently
                published in small numbers by the degree awarding
                institution.
Diagram
Diagram NO_NAMESPACE.tmp#Thesis_degree NO_NAMESPACE.tmp#Thesis_institution NO_NAMESPACE.tmp#Thesis_totalPages literature-2_2_0.tmp#Thesis
Type Thesis
Properties
content complex
Model
Children degree, institution, totalPages
Instance
<thesis>
  <degree>{1,1}</degree>
  <institution id="" scope="document" system="">{1,1}</institution>
  <totalPages>{0,1}</totalPages>
</thesis>
Source
<xs:element name="thesis" type="Thesis">
  <xs:annotation>
    <xs:documentation>tooltip: Thesis as part of a degree summary: Information about a thesis that has been written as part of a degree requirement and is frequently published in small numbers by the degree awarding institution. description: Information about a thesis that has been written as part of a degree requirement and is frequently published in small numbers by the degree awarding institution.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Thesis / degree
Namespace No namespace
Annotations
tooltip: Degee name

summary: The name or degree level for which the thesis was
            completed.

description: The degree field is used to describe the name or
            degree level for which the thesis was completed.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="degree" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Degee name summary: The name or degree level for which the thesis was completed. description: The degree field is used to describe the name or degree level for which the thesis was completed.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Thesis / institution
Namespace No namespace
Annotations
tooltip: Degree awarding institution

summary: The name of the degree-awarding
            institution

description: The degree institution field is used to name the
            institution from which the degree was awarded for the thesis being
            described.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<institution id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</institution>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="institution" type="rp:ResponsibleParty">
  <xs:annotation>
    <xs:documentation>tooltip: Degree awarding institution summary: The name of the degree-awarding institution description: The degree institution field is used to name the institution from which the degree was awarded for the thesis being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Thesis / totalPages
Namespace No namespace
Annotations
tooltip: Thesis Pages

summary: The total number of pages in the thesis.

description: The total pages field is used to document the
            number of pages that are present in the thesis that is being
            described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Thesis Pages summary: The total number of pages in the thesis. description: The total pages field is used to document the number of pages that are present in the thesis that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / conferenceProceedings
Namespace No namespace
Annotations
tooltip: conference proceedings

summary: The published notes, papers, presentations etc...
                of a conference.

description: The published notes, papers, presentations,
                etc..., of a conference.
Diagram
Diagram NO_NAMESPACE.tmp#Book_publisher NO_NAMESPACE.tmp#Book_publicationPlace NO_NAMESPACE.tmp#Book_edition NO_NAMESPACE.tmp#Book_volume NO_NAMESPACE.tmp#Book_numberOfVolumes NO_NAMESPACE.tmp#Book_totalPages NO_NAMESPACE.tmp#Book_totalFigures NO_NAMESPACE.tmp#Book_totalTables NO_NAMESPACE.tmp#Book_ISBN literature-2_2_0.tmp#Book NO_NAMESPACE.tmp#Chapter_chapterNumber NO_NAMESPACE.tmp#Chapter_editor NO_NAMESPACE.tmp#Chapter_bookTitle NO_NAMESPACE.tmp#Chapter_pageRange literature-2_2_0.tmp#Chapter NO_NAMESPACE.tmp#ConferenceProceedings_conferenceName NO_NAMESPACE.tmp#ConferenceProceedings_conferenceDate NO_NAMESPACE.tmp#ConferenceProceedings_conferenceLocation literature-2_2_0.tmp#ConferenceProceedings
Type ConferenceProceedings
Type hierarchy
Properties
content complex
Model
Children ISBN, bookTitle, chapterNumber, conferenceDate, conferenceLocation, conferenceName, edition, editor, numberOfVolumes, pageRange, publicationPlace, publisher, totalFigures, totalPages, totalTables, volume
Instance
<conferenceProceedings>
  <publisher id="" scope="document" system="">{1,1}</publisher>
  <publicationPlace>{0,1}</publicationPlace>
  <edition>{0,1}</edition>
  <volume>{0,1}</volume>
  <numberOfVolumes>{0,1}</numberOfVolumes>
  <totalPages>{0,1}</totalPages>
  <totalFigures>{0,1}</totalFigures>
  <totalTables>{0,1}</totalTables>
  <ISBN>{0,1}</ISBN>
  <chapterNumber>{0,1}</chapterNumber>
  <editor id="" scope="document" system="">{1,unbounded}</editor>
  <bookTitle>{1,1}</bookTitle>
  <pageRange>{0,1}</pageRange>
  <conferenceName>{0,1}</conferenceName>
  <conferenceDate>{0,1}</conferenceDate>
  <conferenceLocation id="" scope="document" system="">{0,1}</conferenceLocation>
</conferenceProceedings>
Source
<xs:element name="conferenceProceedings" type="ConferenceProceedings">
  <xs:annotation>
    <xs:documentation>tooltip: conference proceedings summary: The published notes, papers, presentations etc... of a conference. description: The published notes, papers, presentations, etc..., of a conference.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element ConferenceProceedings / conferenceName
Namespace No namespace
Annotations
tooltip: Conference Name

summary: The name of the conference whose proceedings have
                been published.

description: The name of the conference whose proceedings
                have been published.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="conferenceName" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Conference Name summary: The name of the conference whose proceedings have been published. description: The name of the conference whose proceedings have been published.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element ConferenceProceedings / conferenceDate
Namespace No namespace
Annotations
tooltip: Conference Date

summary: The date the conference was held.

description: The date the conference was
                held.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="conferenceDate" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Conference Date summary: The date the conference was held. description: The date the conference was held.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element ConferenceProceedings / conferenceLocation
Namespace No namespace
Annotations
tooltip: Conference Location

summary: The location where the conference was
                held.

description: The location where the conference was
                held.
Diagram
Diagram NO_NAMESPACE.tmp#Address_id NO_NAMESPACE.tmp#Address_system NO_NAMESPACE.tmp#Address_scope NO_NAMESPACE.tmp#Address_deliveryPoint NO_NAMESPACE.tmp#Address_city NO_NAMESPACE.tmp#Address_administrativeArea NO_NAMESPACE.tmp#Address_postalCode NO_NAMESPACE.tmp#Address_country NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#Address
Type Address
Properties
content complex
minOccurs 0
Model
Children administrativeArea, city, country, deliveryPoint, postalCode, references
Instance
<conferenceLocation id="" scope="document" system="">
  <deliveryPoint xml:lang="">{0,unbounded}</deliveryPoint>
  <city xml:lang="">{0,1}</city>
  <administrativeArea xml:lang="">{0,1}</administrativeArea>
  <postalCode xml:lang="">{0,1}</postalCode>
  <country xml:lang="">{0,1}</country>
  <references system="">{1,1}</references>
</conferenceLocation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="conferenceLocation" type="rp:Address" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Conference Location summary: The location where the conference was held. description: The location where the conference was held.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / personalCommunication
Namespace No namespace
Annotations
tooltip: Personal communication

summary: A personal communication that has been saved
                online or as hard-copy.

description: This could be a widely distributed memo, an
                e-mail, a transcript from a conversation or interview,
                etc...
Diagram
Diagram NO_NAMESPACE.tmp#PersonalCommunication_publisher NO_NAMESPACE.tmp#PersonalCommunication_publicationPlace NO_NAMESPACE.tmp#PersonalCommunication_communicationType NO_NAMESPACE.tmp#PersonalCommunication_recipient literature-2_2_0.tmp#PersonalCommunication
Type PersonalCommunication
Properties
content complex
Model
Children communicationType, publicationPlace, publisher, recipient
Instance
<personalCommunication>
  <publisher id="" scope="document" system="">{0,1}</publisher>
  <publicationPlace>{0,1}</publicationPlace>
  <communicationType>{0,1}</communicationType>
  <recipient id="" scope="document" system="">{0,unbounded}</recipient>
</personalCommunication>
Source
<xs:element name="personalCommunication" type="PersonalCommunication">
  <xs:annotation>
    <xs:documentation>tooltip: Personal communication summary: A personal communication that has been saved online or as hard-copy. description: This could be a widely distributed memo, an e-mail, a transcript from a conversation or interview, etc...</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element PersonalCommunication / publisher
Namespace No namespace
Annotations
tooltip: Publisher

summary: Organization that actually publishes the
            communication

description: The organization that physically puts together the
            communication and publishes it.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
minOccurs 0
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<publisher id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</publisher>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the communication description: The organization that physically puts together the communication and publishes it.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element PersonalCommunication / publicationPlace
Namespace No namespace
Annotations
tooltip: Publication Place

summary: The location at which the work was
            published.

description: The location at which the work was published. This
            is usually the name of the city in which the publishing house
            produced the work.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element PersonalCommunication / communicationType
Namespace No namespace
Annotations
tooltip: Type of communication

summary: The type of personal communication.

description: The type of personal communication. Could be an
            email, letter, memo, transcript of conversation either hardcopy or
            online.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="communicationType" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Type of communication summary: The type of personal communication. description: The type of personal communication. Could be an email, letter, memo, transcript of conversation either hardcopy or online.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element PersonalCommunication / recipient
Namespace No namespace
Annotations
tooltip: Recipient

summary: Recipient of the communication

description: The person, place or thing the personal
            communication was sent to.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<recipient id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</recipient>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="recipient" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Recipient summary: Recipient of the communication description: The person, place or thing the personal communication was sent to.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / map
Namespace No namespace
Annotations
tooltip: map

summary: This element describes the map that is being cited
                or cataloged.

description: This element describes the map that is being
                cited or cataloged, including its geographic coverage and
                scale.
Diagram
Diagram NO_NAMESPACE.tmp#Map_publisher NO_NAMESPACE.tmp#Map_edition NO_NAMESPACE.tmp#Map_geographicCoverage NO_NAMESPACE.tmp#Map_scale literature-2_2_0.tmp#Map
Type Map
Properties
content complex
Model
Children edition, geographicCoverage, publisher, scale
Instance
<map>
  <publisher id="" scope="document" system="">{0,1}</publisher>
  <edition>{0,1}</edition>
  <geographicCoverage id="" scope="document" system="">{0,unbounded}</geographicCoverage>
  <scale>{0,1}</scale>
</map>
Source
<xs:element name="map" type="Map">
  <xs:annotation>
    <xs:documentation>tooltip: map summary: This element describes the map that is being cited or cataloged. description: This element describes the map that is being cited or cataloged, including its geographic coverage and scale.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Map / publisher
Namespace No namespace
Annotations
tooltip: Publisher

summary: Organization that actually publishes the
            map

description: The organization that physically puts together the
            map and publishes it.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
minOccurs 0
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<publisher id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</publisher>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publisher summary: Organization that actually publishes the map description: The organization that physically puts together the map and publishes it.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Map / edition
Namespace No namespace
Annotations
tooltip: Map edition

summary: The edition of the map being described.

description: The edition field is to document the edition of
            the map that is being described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="edition" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Map edition summary: The edition of the map being described. description: The edition field is to document the edition of the map that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Map / geographicCoverage
Namespace No namespace
Annotations
tooltip: Geographic coverage

summary: Description of the geographic area which the map
            covers

description: This element describes the geographic area which
            the map covers. Could be descriptive text or Cartesian coordinates
            of the area.
Diagram
Diagram NO_NAMESPACE.tmp#GeographicCoverage_id NO_NAMESPACE.tmp#GeographicCoverage_system NO_NAMESPACE.tmp#GeographicCoverage_scope NO_NAMESPACE.tmp#GeographicCoverage_geographicDescription NO_NAMESPACE.tmp#GeographicCoverage_boundingCoordinates NO_NAMESPACE.tmp#GeographicCoverage_datasetGPolygon NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#GeographicCoverage
Type GeographicCoverage
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children boundingCoordinates, datasetGPolygon, geographicDescription, references
Instance
<geographicCoverage id="" scope="document" system="">
  <geographicDescription>{1,1}</geographicDescription>
  <boundingCoordinates>{1,1}</boundingCoordinates>
  <datasetGPolygon>{0,unbounded}</datasetGPolygon>
  <references system="">{1,1}</references>
</geographicCoverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="geographicCoverage" type="cov:GeographicCoverage" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Geographic coverage summary: Description of the geographic area which the map covers description: This element describes the geographic area which the map covers. Could be descriptive text or Cartesian coordinates of the area.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Map / scale
Namespace No namespace
Annotations
tooltip: Scale

summary: The Map's scale

description: The Map's scale
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="scale" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Scale summary: The Map's scale description: The Map's scale</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / generic
Namespace No namespace
Annotations
tooltip: Generic Citation

summary: This reference type was created for references
                that do not fit in to the other existing reference
                types

description: This reference type was created for references
                that do not fit in to the other existing reference
                types.
Diagram
Diagram NO_NAMESPACE.tmp#Generic_publisher NO_NAMESPACE.tmp#Generic_publicationPlace NO_NAMESPACE.tmp#Generic_referenceType NO_NAMESPACE.tmp#Generic_volume NO_NAMESPACE.tmp#Generic_numberOfVolumes NO_NAMESPACE.tmp#Generic_totalPages NO_NAMESPACE.tmp#Generic_totalFigures NO_NAMESPACE.tmp#Generic_totalTables NO_NAMESPACE.tmp#Generic_edition NO_NAMESPACE.tmp#Generic_originalPublication NO_NAMESPACE.tmp#Generic_reprintEdition NO_NAMESPACE.tmp#Generic_reviewedItem NO_NAMESPACE.tmp#Generic_ISBN NO_NAMESPACE.tmp#Generic_ISSN literature-2_2_0.tmp#Generic
Type Generic
Properties
content complex
Model
Children ISBN, ISSN, edition, numberOfVolumes, originalPublication, publicationPlace, publisher, referenceType, reprintEdition, reviewedItem, totalFigures, totalPages, totalTables, volume
Instance
<generic>
  <publisher id="" scope="document" system="">{1,1}</publisher>
  <publicationPlace>{0,1}</publicationPlace>
  <referenceType>{0,1}</referenceType>
  <volume>{0,1}</volume>
  <numberOfVolumes>{0,1}</numberOfVolumes>
  <totalPages>{0,1}</totalPages>
  <totalFigures>{0,1}</totalFigures>
  <totalTables>{0,1}</totalTables>
  <edition>{0,1}</edition>
  <originalPublication>{0,1}</originalPublication>
  <reprintEdition>{0,1}</reprintEdition>
  <reviewedItem>{0,1}</reviewedItem>
  <ISBN>{1,1}</ISBN>
  <ISSN>{1,1}</ISSN>
</generic>
Source
<xs:element name="generic" type="Generic">
  <xs:annotation>
    <xs:documentation>tooltip: Generic Citation summary: This reference type was created for references that do not fit in to the other existing reference types description: This reference type was created for references that do not fit in to the other existing reference types.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / publisher
Namespace No namespace
Annotations
tooltip: Publisher

summary: Organization which actually publishes the
            reference

description: The organization which physically puts together
            the reference and publishes it.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<publisher id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</publisher>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="publisher" type="rp:ResponsibleParty">
  <xs:annotation>
    <xs:documentation>tooltip: Publisher summary: Organization which actually publishes the reference description: The organization which physically puts together the reference and publishes it.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / publicationPlace
Namespace No namespace
Annotations
tooltip: Publication Place

summary: The location at which the work was
            published.

description: The location at which the work was published. This
            is usually the name of the city in which the publishing house
            produced the work.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / referenceType
Namespace No namespace
Annotations
tooltip: Reference Type

summary: The type of reference.

description: The reference type describes the type of reference
            this generic type is being used to represent.
Diagram
Diagram
Properties
minOccurs 0
Source
<xs:element name="referenceType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Reference Type summary: The type of reference. description: The reference type describes the type of reference this generic type is being used to represent.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / volume
Namespace No namespace
Annotations
tooltip: Reference volume

summary: The volume of the reference that is part of a
            series.

description: The volume field is used to describe the volume
            number of a reference that is part of a multi-volume series of
            references.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="volume" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Reference volume summary: The volume of the reference that is part of a series. description: The volume field is used to describe the volume number of a reference that is part of a multi-volume series of references.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / numberOfVolumes
Namespace No namespace
Annotations
tooltip: Number of Volumes

summary: Number of volumes in a collection

description: Number of volumes in a
            collection
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="numberOfVolumes" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Number of Volumes summary: Number of volumes in a collection description: Number of volumes in a collection</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / totalPages
Namespace No namespace
Annotations
tooltip: Total reference pages

summary: The total number of pages in the
            references.

description: The total pages field is used to describe the
            total number of pages in the references that is being
            described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalPages" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Total reference pages summary: The total number of pages in the references. description: The total pages field is used to describe the total number of pages in the references that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / totalFigures
Namespace No namespace
Annotations
tooltip: Number of figures in reference

summary: The total number of figures in the
            reference.

description: The total figures field is used to describe the
            total number of figures, diagrams, and plates in the reference that
            is being documented.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalFigures" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Number of figures in reference summary: The total number of figures in the reference. description: The total figures field is used to describe the total number of figures, diagrams, and plates in the reference that is being documented.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / totalTables
Namespace No namespace
Annotations
tooltip: Number of tables in reference

summary: The total number of tables in a
            reference.

description: The total tables field is used to describe the
            total number of tables that are present in the reference that is
            being documented.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalTables" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Number of tables in reference summary: The total number of tables in a reference. description: The total tables field is used to describe the total number of tables that are present in the reference that is being documented.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / edition
Namespace No namespace
Annotations
tooltip: edition

summary: The edition of the generic reference being
            described.

description: The edition field is to document the edition of
            the generic reference type that is being
            described.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="edition" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: edition summary: The edition of the generic reference being described. description: The edition field is to document the edition of the generic reference type that is being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / originalPublication
Namespace No namespace
Annotations
tooltip: Original Publication

summary: References current publication to its
            original.

description: Supplemental information about the original
            publication of the current reference.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="originalPublication" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Original Publication summary: References current publication to its original. description: Supplemental information about the original publication of the current reference.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / reprintEdition
Namespace No namespace
Annotations
tooltip: Reprint Edition

summary: Reference for current edition that was originally
            published under a different title.

description: Reference for current edition that was originally
            published under a different title.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="reprintEdition" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Reprint Edition summary: Reference for current edition that was originally published under a different title. description: Reference for current edition that was originally published under a different title.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / reviewedItem
Namespace No namespace
Annotations
tooltip: Reviewed Item

summary: Reference types that are reviews of other
            references.

description: Use for articles, chapters, audio visual, etc.
            that are critical review of books, cinema, art, or other
            works.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="reviewedItem" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Reviewed Item summary: Reference types that are reviews of other references. description: Use for articles, chapters, audio visual, etc. that are critical review of books, cinema, art, or other works.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / ISBN
Namespace No namespace
Annotations
tooltip: International Standard Book Number

summary: The unique Internation Standard Book
              Number

description: The ISBN, or International Standard Book Number
              that has been assigned to this literature
              resource.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="ISBN" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: International Standard Book Number summary: The unique Internation Standard Book Number description: The ISBN, or International Standard Book Number that has been assigned to this literature resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Generic / ISSN
Namespace No namespace
Annotations
tooltip: International Standard Serial Number

summary: The unique Internation Standard Serial
              Number

description: The ISSN, or International Standard Serial
              Number that has been assigned to this literature
              resource.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="ISSN" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: International Standard Serial Number summary: The unique Internation Standard Serial Number description: The ISSN, or International Standard Serial Number that has been assigned to this literature resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / audioVisual
Namespace No namespace
Annotations
tooltip: audio visual

summary: This reference type is meant to cover all forms of
                audio and visual media.

description: This reference type is meant to cover all
                forms of audio and visual media, including film, video,
                broadcast, other electronic media.
Diagram
Diagram NO_NAMESPACE.tmp#AudioVisual_publisher NO_NAMESPACE.tmp#AudioVisual_publicationPlace NO_NAMESPACE.tmp#AudioVisual_performer NO_NAMESPACE.tmp#AudioVisual_ISBN literature-2_2_0.tmp#AudioVisual
Type AudioVisual
Properties
content complex
Model
Children ISBN, performer, publicationPlace, publisher
Instance
<audioVisual>
  <publisher id="" scope="document" system="">{1,1}</publisher>
  <publicationPlace>{0,unbounded}</publicationPlace>
  <performer id="" scope="document" system="">{0,unbounded}</performer>
  <ISBN>{0,1}</ISBN>
</audioVisual>
Source
<xs:element name="audioVisual" type="AudioVisual">
  <xs:annotation>
    <xs:documentation>tooltip: audio visual summary: This reference type is meant to cover all forms of audio and visual media. description: This reference type is meant to cover all forms of audio and visual media, including film, video, broadcast, other electronic media.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element AudioVisual / publisher
Namespace No namespace
Annotations
tooltip: Publisher

summary: Organization which actually distributes the video,
            film, the broadcaster etc...

description: Organization which actually distributes the video,
            film, the broadcaster etc...
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<publisher id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</publisher>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="publisher" type="rp:ResponsibleParty">
  <xs:annotation>
    <xs:documentation>tooltip: Publisher summary: Organization which actually distributes the video, film, the broadcaster etc... description: Organization which actually distributes the video, film, the broadcaster etc...</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element AudioVisual / publicationPlace
Namespace No namespace
Annotations
tooltip: Publication Place

summary: The location at which the work was
            published.

description: The location at which the work was published. This
            is usually the name of the city in which the publishing house
            produced the work.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="publicationPlace" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Publication Place summary: The location at which the work was published. description: The location at which the work was published. This is usually the name of the city in which the publishing house produced the work.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element AudioVisual / performer
Namespace No namespace
Annotations
tooltip: Performer

summary: The performers in the audio visual
            production

description: The performers involved in acting, narrating, or
            shown in the audio visual production.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<performer id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</performer>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="performer" type="rp:ResponsibleParty" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Performer summary: The performers in the audio visual production description: The performers involved in acting, narrating, or shown in the audio visual production.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element AudioVisual / ISBN
Namespace No namespace
Annotations
tooltip: International Standard Book Number

summary: The unique Internation Standard Book
            Number

description: The ISBN, or International Standard Book Number
            that has been assigned to this literature
            resource.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="ISBN" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: International Standard Book Number summary: The unique Internation Standard Book Number description: The ISBN, or International Standard Book Number that has been assigned to this literature resource.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / presentation
Namespace No namespace
Annotations
tooltip: Unpublished Presentation

summary: An unpublished presentation from a conference,
                workshop, workgroup, symposium etc.

description: An unpublished presentation from a conference,
                workshop, workgroup, symposium, etc. It will be provided upon
                request in either in paper and/or electronic form. If the
                presentation was actually published in a proceedings, use the
                conferenceProceedings type instead.
Diagram
Diagram NO_NAMESPACE.tmp#Presentation_conferenceName NO_NAMESPACE.tmp#Presentation_conferenceDate NO_NAMESPACE.tmp#Presentation_conferenceLocation literature-2_2_0.tmp#Presentation
Type Presentation
Properties
content complex
Model
Children conferenceDate, conferenceLocation, conferenceName
Instance
<presentation>
  <conferenceName>{0,1}</conferenceName>
  <conferenceDate>{0,1}</conferenceDate>
  <conferenceLocation id="" scope="document" system="">{0,1}</conferenceLocation>
</presentation>
Source
<xs:element name="presentation" type="Presentation">
  <xs:annotation>
    <xs:documentation>tooltip: Unpublished Presentation summary: An unpublished presentation from a conference, workshop, workgroup, symposium etc. description: An unpublished presentation from a conference, workshop, workgroup, symposium, etc. It will be provided upon request in either in paper and/or electronic form. If the presentation was actually published in a proceedings, use the conferenceProceedings type instead.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Presentation / conferenceName
Namespace No namespace
Annotations
tooltip: Conference Name

summary: The name of the conference at which this presentation
            was given.

description: The name of the conference at which this
            presentation was given.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="conferenceName" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Conference Name summary: The name of the conference at which this presentation was given. description: The name of the conference at which this presentation was given.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Presentation / conferenceDate
Namespace No namespace
Annotations
tooltip: Conference Date

summary: The date the conference was held.

description: The date the conference was
            held.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="conferenceDate" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Conference Date summary: The date the conference was held. description: The date the conference was held.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element Presentation / conferenceLocation
Namespace No namespace
Annotations
tooltip: Conference Location

summary: The location where the conference was
            held.

description: The location where the conference was
            held.
Diagram
Diagram NO_NAMESPACE.tmp#Address_id NO_NAMESPACE.tmp#Address_system NO_NAMESPACE.tmp#Address_scope NO_NAMESPACE.tmp#Address_deliveryPoint NO_NAMESPACE.tmp#Address_city NO_NAMESPACE.tmp#Address_administrativeArea NO_NAMESPACE.tmp#Address_postalCode NO_NAMESPACE.tmp#Address_country NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#Address
Type Address
Properties
content complex
minOccurs 0
Model
Children administrativeArea, city, country, deliveryPoint, postalCode, references
Instance
<conferenceLocation id="" scope="document" system="">
  <deliveryPoint xml:lang="">{0,unbounded}</deliveryPoint>
  <city xml:lang="">{0,1}</city>
  <administrativeArea xml:lang="">{0,1}</administrativeArea>
  <postalCode xml:lang="">{0,1}</postalCode>
  <country xml:lang="">{0,1}</country>
  <references system="">{1,1}</references>
</conferenceLocation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="conferenceLocation" type="rp:Address" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Conference Location summary: The location where the conference was held. description: The location where the conference was held.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationType / bibtex
Namespace No namespace
Annotations
tooltip: Bibtex Citation

summary: Citation in Bibtex format.

description: The bibtex field provides a parseable citation formatted according to
                      the Bibtex formatting conventions. The citation entry is assigned a unique key that must be unique across all bibtex fields in the EML document. The citation key can be used in markdown sections of the text to refer to this citation using the pandoc-style of inline citation keys.  See the markdown element for more details.  The record is delimited using curly braces. Most reference software can both import and export citations in Bibtex format, so this is a simpler representation to produce and consume than native EML citation representations.
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="bibtex" type="xs:string">
  <xs:annotation>
    <xs:documentation>tooltip: Bibtex Citation summary: Citation in Bibtex format. description: The bibtex field provides a parseable citation formatted according to the Bibtex formatting conventions. The citation entry is assigned a unique key that must be unique across all bibtex fields in the EML document. The citation key can be used in markdown sections of the text to refer to this citation using the pandoc-style of inline citation keys. See the markdown element for more details. The record is delimited using curly braces. Most reference software can both import and export citations in Bibtex format, so this is a simpler representation to produce and consume than native EML citation representations.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element TemporalCoverage / rangeOfDates
Namespace No namespace
Annotations
tooltip: Range of dates/times

summary: Means of encoding a range of dates and
        times.

description: The 'RangeOfDatesType' field is intended to be used for
        describing a range of dates and/or times. It may be used multiple times
        to document multiple date ranges. It allows for two 'singleDateTime'
        fields, the first to be used as the beginning dateTime, and the second
        to be used as the ending dateTime of the range.
Diagram
Diagram NO_NAMESPACE.tmp#TemporalCoverage_TemporalCoverage_rangeOfDates_beginDate NO_NAMESPACE.tmp#TemporalCoverage_TemporalCoverage_rangeOfDates_endDate
Properties
content complex
Model
Children beginDate, endDate
Instance
<rangeOfDates>
  <beginDate>{1,1}</beginDate>
  <endDate>{1,1}</endDate>
</rangeOfDates>
Source
<xs:element name="rangeOfDates">
  <xs:annotation>
    <xs:documentation>tooltip: Range of dates/times summary: Means of encoding a range of dates and times. description: The 'RangeOfDatesType' field is intended to be used for describing a range of dates and/or times. It may be used multiple times to document multiple date ranges. It allows for two 'singleDateTime' fields, the first to be used as the beginning dateTime, and the second to be used as the ending dateTime of the range.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="beginDate" type="SingleDateTimeType">
        <xs:annotation>
          <xs:documentation>tooltip: Begin Date summary: A single time stamp signifying the beginning of some time period description: A single time stamp signifying the beginning of some time period. There is a choice between two options: a calendar date with a time, or a geologic age.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="endDate" type="SingleDateTimeType">
        <xs:annotation>
          <xs:documentation>tooltip: End Date summary: A single time stamp signifying the end of some time period description: A single time stamp signifying the end of some time period. There is a choice between two options: a calendar date with a time, or a geologic age.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TemporalCoverage / rangeOfDates / beginDate
Namespace No namespace
Annotations
tooltip: Begin Date

summary: A single time stamp signifying the beginning of
              some time period

description: A single time stamp signifying the beginning of
              some time period.  There is a choice between two
              options: a calendar date with a time, or a geologic
              age.
Diagram
Diagram NO_NAMESPACE.tmp#SingleDateTimeType_calendarDate NO_NAMESPACE.tmp#SingleDateTimeType_time NO_NAMESPACE.tmp#SingleDateTimeType_alternativeTimeScale coverage-2_2_0.tmp#SingleDateTimeType
Type SingleDateTimeType
Properties
content complex
Model
Children alternativeTimeScale, calendarDate, time
Instance
<beginDate>
  <calendarDate>{1,1}</calendarDate>
  <time>{0,1}</time>
  <alternativeTimeScale>{1,1}</alternativeTimeScale>
</beginDate>
Source
<xs:element name="beginDate" type="SingleDateTimeType">
  <xs:annotation>
    <xs:documentation>tooltip: Begin Date summary: A single time stamp signifying the beginning of some time period description: A single time stamp signifying the beginning of some time period. There is a choice between two options: a calendar date with a time, or a geologic age.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TemporalCoverage / rangeOfDates / endDate
Namespace No namespace
Annotations
tooltip: End Date

summary: A single time stamp signifying the end of
              some time period

description: A single time stamp signifying the end of
              some time period.  There is a choice between two
              options: a calendar date with a time, or a geologic
              age.
Diagram
Diagram NO_NAMESPACE.tmp#SingleDateTimeType_calendarDate NO_NAMESPACE.tmp#SingleDateTimeType_time NO_NAMESPACE.tmp#SingleDateTimeType_alternativeTimeScale coverage-2_2_0.tmp#SingleDateTimeType
Type SingleDateTimeType
Properties
content complex
Model
Children alternativeTimeScale, calendarDate, time
Instance
<endDate>
  <calendarDate>{1,1}</calendarDate>
  <time>{0,1}</time>
  <alternativeTimeScale>{1,1}</alternativeTimeScale>
</endDate>
Source
<xs:element name="endDate" type="SingleDateTimeType">
  <xs:annotation>
    <xs:documentation>tooltip: End Date summary: A single time stamp signifying the end of some time period description: A single time stamp signifying the end of some time period. There is a choice between two options: a calendar date with a time, or a geologic age.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element Coverage / taxonomicCoverage
Namespace No namespace
Annotations
tooltip: Taxonomic coverage

summary: Taxonomic coverage information.

description: Taxonomic Coverage is a container for Taxonomic
              information about a project, a resource, or an entity within a
              resource. It includes a list of species names (or higher level
              ranks) from one or more classification systems.
Diagram
Diagram NO_NAMESPACE.tmp#TaxonomicCoverage_id NO_NAMESPACE.tmp#TaxonomicCoverage_taxonomicSystem NO_NAMESPACE.tmp#TaxonomicCoverage_generalTaxonomicCoverage NO_NAMESPACE.tmp#TaxonomicCoverage_taxonomicClassification NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#TaxonomicCoverage NO_NAMESPACE.tmp#Coverage_Coverage_taxonomicCoverage_system NO_NAMESPACE.tmp#Coverage_Coverage_taxonomicCoverage_scope
Type extension of TaxonomicCoverage
Type hierarchy
Properties
content complex
Model
Children generalTaxonomicCoverage, references, taxonomicClassification, taxonomicSystem
Instance
<taxonomicCoverage id="" scope="document" system="">
  <taxonomicSystem>{0,1}</taxonomicSystem>
  <generalTaxonomicCoverage>{0,1}</generalTaxonomicCoverage>
  <taxonomicClassification id="">{1,unbounded}</taxonomicClassification>
  <references system="">{1,1}</references>
</taxonomicCoverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="taxonomicCoverage">
  <xs:annotation>
    <xs:documentation>tooltip: Taxonomic coverage summary: Taxonomic coverage information. description: Taxonomic Coverage is a container for Taxonomic information about a project, a resource, or an entity within a resource. It includes a list of species names (or higher level ranks) from one or more classification systems.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="TaxonomicCoverage">
        <xs:attribute name="system" type="res:SystemType" use="optional"/>
        <xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem
Namespace No namespace
Annotations
tooltip: Taxonomic system

summary: Documentation of taxonomic sources, procedures, and
              treatments.

description: Documentation of taxonomic sources, procedures,
              and treatments.
Diagram
Diagram NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_classificationSystem NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_identificationReference NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_identifierName NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_taxonomicProcedures NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_taxonomicCompleteness NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_vouchers
Properties
content complex
minOccurs 0
Model
Children classificationSystem, identificationReference, identifierName, taxonomicCompleteness, taxonomicProcedures, vouchers
Instance
<taxonomicSystem>
  <classificationSystem>{1,unbounded}</classificationSystem>
  <identificationReference id="" scope="document" system="">{0,unbounded}</identificationReference>
  <identifierName id="" scope="document" system="">{1,unbounded}</identifierName>
  <taxonomicProcedures>{1,1}</taxonomicProcedures>
  <taxonomicCompleteness>{0,1}</taxonomicCompleteness>
  <vouchers>{0,unbounded}</vouchers>
</taxonomicSystem>
Source
<xs:element name="taxonomicSystem" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Taxonomic system summary: Documentation of taxonomic sources, procedures, and treatments. description: Documentation of taxonomic sources, procedures, and treatments.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="classificationSystem" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Classification system/authority summary: Information about the classification system or authority used. description: Information about the classification system or authority used.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="classificationSystemCitation" type="cit:CitationType">
              <xs:annotation>
                <xs:documentation>tooltip: Taxonomic citation summary: description: Relevant literature for documenting the used classification system.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="classificationSystemModifications" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Classification system modification summary: description: A description of any modifications or exceptions made to the classification system or authority used.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="identificationReference" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Non-authoritative citation summary: description: Information on any non-authoritative materials (e.g. field guides) useful for reconstructing the actual identification process.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="identifierName" type="rp:ResponsibleParty" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Identifier's Name summary: description: Information about the individual(s) responsible for the identification(s) of the specimens or sightings, etc.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="taxonomicProcedures" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Taxonomic procedures summary: description: Description of the methods used for the taxonomic identification.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="taxonomicCompleteness" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Taxonomic completeness summary: description: Information concerning the proportions and treatment of unidentified materials, estimates of the importance and possible identities of uncertain determinations, synonyms or other incorrect usages, taxa not well treated or requiring further work, and expertise of field workers.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="vouchers" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Specimen information summary: description: Information on the types of specimen, the repository, and the individuals who identified the vouchers.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="specimen" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Specimen type summary: description: A word or phrase describing the type of specimen collected.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="repository">
              <xs:annotation>
                <xs:documentation>tooltip: Storage location of specimen summary: description: Information about the curator or contact person and/or agency responsible for the specimens.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
                    <xs:annotation>
                      <xs:documentation>tooltip: Originator summary: A person or organization asociated with this resource. description: The 'originator' element provides the full name of the person, organization, or position associated with the resource. Typically, the originator role is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / classificationSystem
Namespace No namespace
Annotations
tooltip: Classification system/authority

summary: Information about the classification system or
                    authority used.

description: Information about the classification
                    system or authority used.
Diagram
Diagram NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_classificationSystem_classificationSystemCitation NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_classificationSystem_classificationSystemModifications
Properties
content complex
maxOccurs unbounded
Model
Children classificationSystemCitation, classificationSystemModifications
Instance
<classificationSystem>
  <classificationSystemCitation id="" scope="document" system="">{1,1}</classificationSystemCitation>
  <classificationSystemModifications>{0,1}</classificationSystemModifications>
</classificationSystem>
Source
<xs:element name="classificationSystem" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Classification system/authority summary: Information about the classification system or authority used. description: Information about the classification system or authority used.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="classificationSystemCitation" type="cit:CitationType">
        <xs:annotation>
          <xs:documentation>tooltip: Taxonomic citation summary: description: Relevant literature for documenting the used classification system.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="classificationSystemModifications" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Classification system modification summary: description: A description of any modifications or exceptions made to the classification system or authority used.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / classificationSystem / classificationSystemCitation
Namespace No namespace
Annotations
tooltip: Taxonomic citation

summary: 

description: Relevant literature for documenting
                          the used classification system.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<classificationSystemCitation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</classificationSystemCitation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="classificationSystemCitation" type="cit:CitationType">
  <xs:annotation>
    <xs:documentation>tooltip: Taxonomic citation summary: description: Relevant literature for documenting the used classification system.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / classificationSystem / classificationSystemModifications
Namespace No namespace
Annotations
tooltip: Classification system
                          modification

summary: 

description: A description of any modifications
                          or exceptions made to the classification system or
                          authority used.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="classificationSystemModifications" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Classification system modification summary: description: A description of any modifications or exceptions made to the classification system or authority used.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / identificationReference
Namespace No namespace
Annotations
tooltip: Non-authoritative citation

summary: 

description: Information on any non-authoritative
                    materials (e.g. field guides) useful for reconstructing the
                    actual identification process.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<identificationReference id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</identificationReference>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="identificationReference" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Non-authoritative citation summary: description: Information on any non-authoritative materials (e.g. field guides) useful for reconstructing the actual identification process.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / identifierName
Namespace No namespace
Annotations
tooltip: Identifier's Name

summary: 

description: Information about the individual(s)
                    responsible for the identification(s) of the specimens or
                    sightings, etc.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<identifierName id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</identifierName>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="identifierName" type="rp:ResponsibleParty" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Identifier's Name summary: description: Information about the individual(s) responsible for the identification(s) of the specimens or sightings, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / taxonomicProcedures
Namespace No namespace
Annotations
tooltip: Taxonomic procedures

summary: 

description: Description of the methods used for the
                    taxonomic identification.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="taxonomicProcedures" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Taxonomic procedures summary: description: Description of the methods used for the taxonomic identification.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / taxonomicCompleteness
Namespace No namespace
Annotations
tooltip: Taxonomic completeness

summary: 

description: Information concerning the proportions and
                    treatment of unidentified materials, estimates of the
                    importance and possible identities of uncertain
                    determinations, synonyms or other incorrect usages, taxa
                    not well treated or requiring further work, and expertise
                    of field workers.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="taxonomicCompleteness" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Taxonomic completeness summary: description: Information concerning the proportions and treatment of unidentified materials, estimates of the importance and possible identities of uncertain determinations, synonyms or other incorrect usages, taxa not well treated or requiring further work, and expertise of field workers.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / vouchers
Namespace No namespace
Annotations
tooltip: Specimen information

summary: 

description: Information on the types of specimen, the
                    repository, and the individuals who identified the
                    vouchers.
Diagram
Diagram NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_vouchers_specimen NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_vouchers_repository
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children repository, specimen
Instance
<vouchers>
  <specimen>{1,1}</specimen>
  <repository>{1,1}</repository>
</vouchers>
Source
<xs:element name="vouchers" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Specimen information summary: description: Information on the types of specimen, the repository, and the individuals who identified the vouchers.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="specimen" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Specimen type summary: description: A word or phrase describing the type of specimen collected.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="repository">
        <xs:annotation>
          <xs:documentation>tooltip: Storage location of specimen summary: description: Information about the curator or contact person and/or agency responsible for the specimens.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Originator summary: A person or organization asociated with this resource. description: The 'originator' element provides the full name of the person, organization, or position associated with the resource. Typically, the originator role is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / vouchers / specimen
Namespace No namespace
Annotations
tooltip: Specimen type

summary: 

description: A word or phrase describing the type
                          of specimen collected.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="specimen" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Specimen type summary: description: A word or phrase describing the type of specimen collected.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / vouchers / repository
Namespace No namespace
Annotations
tooltip: Storage location of
                          specimen

summary: 

description: Information about the curator or
                          contact person and/or agency responsible for the
                          specimens.
Diagram
Diagram NO_NAMESPACE.tmp#TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_vouchers_TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_TaxonomicCoverage_TaxonomicCoverage_taxonomicSystem_vouchers_repository_originator
Properties
content complex
Model
Children originator
Instance
<repository>
  <originator id="" scope="document" system="">{1,unbounded}</originator>
</repository>
Source
<xs:element name="repository">
  <xs:annotation>
    <xs:documentation>tooltip: Storage location of specimen summary: description: Information about the curator or contact person and/or agency responsible for the specimens.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Originator summary: A person or organization asociated with this resource. description: The 'originator' element provides the full name of the person, organization, or position associated with the resource. Typically, the originator role is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicSystem / vouchers / repository / originator
Namespace No namespace
Annotations
tooltip: Originator

summary: A person or organization asociated
                                with this resource.

description: The 'originator' element
                                provides the full name of the person,
                                organization, or position associated with the
                                resource. Typically, the originator role is set
                                to "owner" to indicate the list of parties who
                                "own" the resource, but other roles such as
                                "principal investigator", "author", and
                                "editor" are provided.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<originator id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</originator>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="originator" type="rp:ResponsibleParty" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Originator summary: A person or organization asociated with this resource. description: The 'originator' element provides the full name of the person, organization, or position associated with the resource. Typically, the originator role is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / generalTaxonomicCoverage
Namespace No namespace
Annotations
tooltip: General taxonomic coverage

summary: A description of the range of taxa addressed in the
              data set or collection.

description: A description of the range of taxa addressed in
              the data set or collection.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="generalTaxonomicCoverage" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: General taxonomic coverage summary: A description of the range of taxa addressed in the data set or collection. description: A description of the range of taxa addressed in the data set or collection.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicCoverage / taxonomicClassification
Namespace No namespace
Annotations
tooltip: Taxonomic classification

summary: Information about the range of taxa addressed in the data
        set or collection.

description: Information about the range of taxa addressed in the
        data set or collection. See the Type definition for more information.
Diagram
Diagram NO_NAMESPACE.tmp#TaxonomicClassificationType_id NO_NAMESPACE.tmp#TaxonomicClassificationType_taxonRankName NO_NAMESPACE.tmp#TaxonomicClassificationType_taxonRankValue NO_NAMESPACE.tmp#TaxonomicClassificationType_commonName NO_NAMESPACE.tmp#TaxonomicClassificationType_taxonId NO_NAMESPACE.tmp#TaxonomicClassificationType_taxonomicClassification coverage-2_2_0.tmp#TaxonomicClassificationType
Type TaxonomicClassificationType
Properties
content complex
maxOccurs unbounded
Model
Children commonName, taxonId, taxonRankName, taxonRankValue, taxonomicClassification
Instance
<taxonomicClassification id="">
  <taxonRankName>{0,1}</taxonRankName>
  <taxonRankValue>{0,1}</taxonRankValue>
  <commonName>{0,unbounded}</commonName>
  <taxonId provider="">{0,unbounded}</taxonId>
  <taxonomicClassification id="">{0,unbounded}</taxonomicClassification>
</taxonomicClassification>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="taxonomicClassification" type="TaxonomicClassificationType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Taxonomic classification summary: Information about the range of taxa addressed in the data set or collection. description: Information about the range of taxa addressed in the data set or collection. See the Type definition for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicClassificationType / taxonRankName
Namespace No namespace
Annotations
tooltip: Taxon rank name

summary: The name of the taxonomic rank for which the Taxon
            rank value is provided.

description: The name of the taxonomic rank for which the
            Taxon rank value is provided. This field allows for the name one
            of the accepted levels of Taxa.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="taxonRankName" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Taxon rank name summary: The name of the taxonomic rank for which the Taxon rank value is provided. description: The name of the taxonomic rank for which the Taxon rank value is provided. This field allows for the name one of the accepted levels of Taxa.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicClassificationType / taxonRankValue
Namespace No namespace
Annotations
tooltip: Taxon rank value

summary: The taxonomic rank name being described.

description: The name for the taxonomic rank being described.
              Typically the values are from authoritative sources
              such as the Integrated Taxonomic
            Information System (ITIS) in the U.S. (http://www/itis.usda.gov)
            and in Canada (http://sis.agr.gc.ca/pls/itisca/taxaget).
            Species2000 is another source of taxonomic information, found at
            (http://www.sp2000.org). Note that for the taxonomic rank "species", the
            accepted practice is to use binomial nomenclaure, i.e., a combination of
            the genus name plus species epithet is required to denote the species. Therefore
            the "species" is not the species epithet alone.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="taxonRankValue" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Taxon rank value summary: The taxonomic rank name being described. description: The name for the taxonomic rank being described. Typically the values are from authoritative sources such as the Integrated Taxonomic Information System (ITIS) in the U.S. (http://www/itis.usda.gov) and in Canada (http://sis.agr.gc.ca/pls/itisca/taxaget). Species2000 is another source of taxonomic information, found at (http://www.sp2000.org). Note that for the taxonomic rank "species", the accepted practice is to use binomial nomenclaure, i.e., a combination of the genus name plus species epithet is required to denote the species. Therefore the "species" is not the species epithet alone.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicClassificationType / commonName
Namespace No namespace
Annotations
tooltip: Common name

summary: Specification of applicable common
            names.

description: Specification of applicable common names. These
            common names may be general descriptions of a group of organisms
            if appropriate.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="commonName" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Common name summary: Specification of applicable common names. description: Specification of applicable common names. These common names may be general descriptions of a group of organisms if appropriate.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicClassificationType / taxonId
Namespace No namespace
Annotations
tooltip: Taxonomic Identifier

summary: Element holds an ID and ID-provider for this taxon. 

description: The identifier for this
              taxon from an authority, such as ITIS or USDA Plant Database. Using an external
            system identifer allows referencing of additional information about a taxon, e.g.,
            authoritative names, historical synonyms, published descriptions or rank
            hierarchies.
Diagram
Diagram NO_NAMESPACE.tmp#TaxonomicClassificationType_TaxonomicClassificationType_taxonId_provider
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
provider xs:anyURI required
tooltip: Taxon ID Provider

summary: The taxonomic authority or catalog from which the
                      taxonId can be retrieved, defined
                      as the namespace URI for the provider.

description: This attribute holds the namespace URI
                      for the taxonomic authority or catalog to which this taxonId applies.
                      taxonId providers should be chosen for their stability and longevity,
                      and with discernable website URIs or APIs.
Source
<xs:element name="taxonId" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Taxonomic Identifier summary: Element holds an ID and ID-provider for this taxon. description: The identifier for this taxon from an authority, such as ITIS or USDA Plant Database. Using an external system identifer allows referencing of additional information about a taxon, e.g., authoritative names, historical synonyms, published descriptions or rank hierarchies.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="provider" type="xs:anyURI" use="required">
          <xs:annotation>
            <xs:documentation>tooltip: Taxon ID Provider summary: The taxonomic authority or catalog from which the taxonId can be retrieved, defined as the namespace URI for the provider. description: This attribute holds the namespace URI for the taxonomic authority or catalog to which this taxonId applies. taxonId providers should be chosen for their stability and longevity, and with discernable website URIs or APIs.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element TaxonomicClassificationType / taxonomicClassification
Namespace No namespace
Annotations
tooltip: Taxonomic classification

summary: Information about the range of taxa addressed in the data
        set or collection.

description: Information about the range of taxa addressed in the
        data set or collection. See the Type definition for more information.
Diagram
Diagram NO_NAMESPACE.tmp#TaxonomicClassificationType_id NO_NAMESPACE.tmp#TaxonomicClassificationType_taxonRankName NO_NAMESPACE.tmp#TaxonomicClassificationType_taxonRankValue NO_NAMESPACE.tmp#TaxonomicClassificationType_commonName NO_NAMESPACE.tmp#TaxonomicClassificationType_taxonId NO_NAMESPACE.tmp#TaxonomicClassificationType_taxonomicClassification coverage-2_2_0.tmp#TaxonomicClassificationType
Type TaxonomicClassificationType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children commonName, taxonId, taxonRankName, taxonRankValue, taxonomicClassification
Instance
<taxonomicClassification id="">
  <taxonRankName>{0,1}</taxonRankName>
  <taxonRankValue>{0,1}</taxonRankValue>
  <commonName>{0,unbounded}</commonName>
  <taxonId provider="">{0,unbounded}</taxonId>
  <taxonomicClassification id="">{0,unbounded}</taxonomicClassification>
</taxonomicClassification>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="taxonomicClassification" type="TaxonomicClassificationType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Taxonomic classification summary: Information about the range of taxa addressed in the data set or collection. description: Information about the range of taxa addressed in the data set or collection. See the Type definition for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Element ResourceGroup / annotation
Namespace No namespace
Annotations
tooltip: Semantic Annotation

summary: A precisely-defined semantic statement about this resource.
            

description: An annotation represents a precisely-defined semantic
                  statement that applies to this resource.  This semantic
                  statement is used to associate precise semantics with the
                  resource.  Each annotation consists of a propertyURI and
                  valueURI that define a property and value that apply to the
                  resource. The subject of the statement is implicitly the
                  eml:resource that contains the annotation.  The associated
                  labels can be used to display the statement to users.
                  Each URI is resolvable to a controlled vocabulary
                  that provides a definition, relationships to other terms, and
                  multiple labels for displaying the statement.
Diagram
Diagram NO_NAMESPACE.tmp#SemanticAnnotation_propertyURI NO_NAMESPACE.tmp#SemanticAnnotation_valueURI semantics-2_2_0.tmp#SemanticAnnotation
Type SemanticAnnotation
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children propertyURI, valueURI
Instance
<annotation>
  <propertyURI label="">{1,1}</propertyURI>
  <valueURI label="">{1,1}</valueURI>
</annotation>
Source
<xs:element name="annotation" type="sem:SemanticAnnotation" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about this resource. description: An annotation represents a precisely-defined semantic statement that applies to this resource. This semantic statement is used to associate precise semantics with the resource. Each annotation consists of a propertyURI and valueURI that define a property and value that apply to the resource. The subject of the statement is implicitly the eml:resource that contains the annotation. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Element SemanticAnnotation / propertyURI
Namespace No namespace
Annotations
tooltip: Property URI

summary: The persistent URI used to identify a property from a vocabulary.
                    

description: The URI for a property that is drawn from a controlled
                        vocabulary, and that links the subject of this annotation
                        (which is implied by its parent element) to the annotation value.
                        The propertyURI represents a semantically well-defined concept
                        that one wants to apply to an element within EML.
                        These properties should be precisely defined,
                        including defining various relationships to related concepts.
                        Property URIs are typically drawn from formal ontologies that
                        provide well-defined logical semantics and provide for various
                        types of reasoning about equivalence and overlap.
                        Property URIs should be persistent and unique over decades,
                        and the meaning of the URI should
                        be stable over time as well. These URIs are usually constructed
                        using an additional abstraction layer via link resolvers,
                        rather than directly resolving to the term definition itself.
                        Thus, when resolving the propertyURI, software user agents should
                        be prepared to follow multiple redirects before finally
                        resolving the current location of the definition.
                        However, there is no requirement that propertyURIs need to be
                        resolvable, and metadata parsers should expect to find
                        propertyURIs that do not resolve and are only used as unique
                        URIs for the property (i.e., a name).
Diagram
Diagram NO_NAMESPACE.tmp#SemanticAnnotation_SemanticAnnotation_propertyURI_label
Type extension of xs:anyURI
Properties
content complex
minOccurs 1
maxOccurs 1
Attributes
QName Type Use Annotation
label xs:string required
tooltip: Property Label

summary: 
                                    A human readable representation of the controlled property.
                                

description: 
                                    A label that provides a human readable representation of
                                    the controlled property. The label is often used to represent
                                    the controlled property when displaying annotations in
                                    software. The label is often redundant with one or more labels
                                    that are defined in the controlled vocabulary itself,
                                    but is repreated here within the EML document to make it easy
                                    for consumers to display the annotation to users.  Other
                                    labels, including labels in multiple languages, may often be
                                    accessible from within the ontology or controlled
                                    vocabularly accessible at the propertyURI.  Property definitions
                                    and relationships to other properties are also typically
                                    provided within the vocabularly accessible at the propertyURI.
                                    Software and people may be able to resolve the URI to find out
                                    the definition and retrieve additional labels and other metadata
                                    for presentation to users.
Source
<xs:element name="propertyURI" minOccurs="1" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>tooltip: Property URI summary: The persistent URI used to identify a property from a vocabulary. description: The URI for a property that is drawn from a controlled vocabulary, and that links the subject of this annotation (which is implied by its parent element) to the annotation value. The propertyURI represents a semantically well-defined concept that one wants to apply to an element within EML. These properties should be precisely defined, including defining various relationships to related concepts. Property URIs are typically drawn from formal ontologies that provide well-defined logical semantics and provide for various types of reasoning about equivalence and overlap. Property URIs should be persistent and unique over decades, and the meaning of the URI should be stable over time as well. These URIs are usually constructed using an additional abstraction layer via link resolvers, rather than directly resolving to the term definition itself. Thus, when resolving the propertyURI, software user agents should be prepared to follow multiple redirects before finally resolving the current location of the definition. However, there is no requirement that propertyURIs need to be resolvable, and metadata parsers should expect to find propertyURIs that do not resolve and are only used as unique URIs for the property (i.e., a name).</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:anyURI">
        <xs:attribute name="label" type="xs:string" use="required">
          <xs:annotation>
            <xs:documentation>tooltip: Property Label summary: A human readable representation of the controlled property. description: A label that provides a human readable representation of the controlled property. The label is often used to represent the controlled property when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the propertyURI. Property definitions and relationships to other properties are also typically provided within the vocabularly accessible at the propertyURI. Software and people may be able to resolve the URI to find out the definition and retrieve additional labels and other metadata for presentation to users.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-semantics.xsd
Element SemanticAnnotation / valueURI
Namespace No namespace
Annotations
tooltip: Value URI

summary: The persistent URI used to identify a value from a vocabulary.
              

description: The URI for a value that is drawn from a controlled
                  vocabulary such as a published ontology or controlled term list. The
                  value represents the object of a semantic statement in which the
                  subject is the containing element, the property is defined by
                  the sibling propertyURI, and this valueURI element represents
                  the object.  These values should be precisely defined,
                  including defining various relationships to related concepts.
                  Value URIs are typically drawn from formal ontologies that
                  provide well-defined logical semantics and provide for various
                  types of reasoning about value equivalence and overlap.
                  Value URIs should be persistent and unique over decades,
                  and the meaning of the values associated with the URI should
                  be stable over time as well. These URIs are usually constructed
                  using an additional abstraction layer via link resolvers,
                  rather than directly resolving to the term definition itself.
                  Thus, when resolving the valueURI, software user agents should
                  be prepared to follow multiple redirects before finally
                  resolving the current location of the value definition.
                  However, there is no requirement that valueURIs need to be
                  resolvable, and metadata parsers should expect to find
                  valueURIs that do not resolve and are only used as unique
                  URIs for the value (i.e., a name)
Diagram
Diagram NO_NAMESPACE.tmp#SemanticAnnotation_SemanticAnnotation_valueURI_label
Type extension of xs:anyURI
Properties
content complex
minOccurs 1
maxOccurs 1
Attributes
QName Type Use Annotation
label xs:string required
tooltip: Value Label

summary: 
                                  A human readable representation of the controlled value.
                              

description: 
                                  A label that provides a human readable representation of
                                  the controlled value. The label is often used to represent the
                                  controlled value when displaying annotations in software. The
                                  label is often redundant with one or more labels that are
                                  defined in the controlled vocabulary itself, but is repreated
                                  here within the EML document to make it easy for consumers to
                                  display the annotation to users.  Other labels, including
                                  labels in multiple languages, may often be accessible from
                                  within the ontology or controlled vocabularly accessible at
                                  the valueURI.  Value definitions and relationships to
                                  other terms are also typically provided within the vocabularly
                                  accessible at the valueURI.  Software and people can resolve
                                  the value URI to find out the definition of the value and
                                  retrieve additional labels and other metadata about the value
                                  for presentation to users.
Source
<xs:element name="valueURI" minOccurs="1" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>tooltip: Value URI summary: The persistent URI used to identify a value from a vocabulary. description: The URI for a value that is drawn from a controlled vocabulary such as a published ontology or controlled term list. The value represents the object of a semantic statement in which the subject is the containing element, the property is defined by the sibling propertyURI, and this valueURI element represents the object. These values should be precisely defined, including defining various relationships to related concepts. Value URIs are typically drawn from formal ontologies that provide well-defined logical semantics and provide for various types of reasoning about value equivalence and overlap. Value URIs should be persistent and unique over decades, and the meaning of the values associated with the URI should be stable over time as well. These URIs are usually constructed using an additional abstraction layer via link resolvers, rather than directly resolving to the term definition itself. Thus, when resolving the valueURI, software user agents should be prepared to follow multiple redirects before finally resolving the current location of the value definition. However, there is no requirement that valueURIs need to be resolvable, and metadata parsers should expect to find valueURIs that do not resolve and are only used as unique URIs for the value (i.e., a name)</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:anyURI">
        <xs:attribute name="label" type="xs:string" use="required">
          <xs:annotation>
            <xs:documentation>tooltip: Value Label summary: A human readable representation of the controlled value. description: A label that provides a human readable representation of the controlled value. The label is often used to represent the controlled value when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the valueURI. Value definitions and relationships to other terms are also typically provided within the vocabularly accessible at the valueURI. Software and people can resolve the value URI to find out the definition of the value and retrieve additional labels and other metadata about the value for presentation to users.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-semantics.xsd
Element DatasetType / purpose
Namespace No namespace
Annotations
tooltip: Purpose

summary: A synopsis of the purpose of this
              dataset.

description: A synopsis of the purpose of this
              dataset.  It may include one or more paragraphs as well as
              inline links to table(s) and figure(s) that summarize the
              data included in the data paper, including a summary of key
              findings if appropriate. Note that this element requires DocBook style
              formatting.  See eml-text for more information.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
mixed true
Model
Children markdown, para, section
Instance
<purpose xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</purpose>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="purpose" type="txt:TextType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Purpose summary: A synopsis of the purpose of this dataset. description: A synopsis of the purpose of this dataset. It may include one or more paragraphs as well as inline links to table(s) and figure(s) that summarize the data included in the data paper, including a summary of key findings if appropriate. Note that this element requires DocBook style formatting. See eml-text for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / introduction
Namespace No namespace
Annotations
tooltip: Introduction

summary: An overview of the background and context for the dataset.

description: One to many paragraphs that provide background
                  and context for the dataset with appropriate figures and
                  references.  This is similar to the introduction for a journal
                  article, and would include, for example, project objectives,
                  hypotheses being addressed, what is known about the pattern or
                  process under study, how the data have been used to date
                  (including references), and how they could be used in the future.
                  The introduction may include figure(s) and table(s) by first
                  attaching those entities to the dataset (e.g., dataTable,
                  otherEntity), providing an id attribute for that entity, and
                  then referencing that entity id in the text of the introduction
                  using Markdown's syntax for inline images. See eml-text for
                  more information on formatting within this section.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
mixed true
Model
Children markdown, para, section
Instance
<introduction xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</introduction>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="introduction" type="txt:TextType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Introduction summary: An overview of the background and context for the dataset. description: One to many paragraphs that provide background and context for the dataset with appropriate figures and references. This is similar to the introduction for a journal article, and would include, for example, project objectives, hypotheses being addressed, what is known about the pattern or process under study, how the data have been used to date (including references), and how they could be used in the future. The introduction may include figure(s) and table(s) by first attaching those entities to the dataset (e.g., dataTable, otherEntity), providing an id attribute for that entity, and then referencing that entity id in the text of the introduction using Markdown's syntax for inline images. See eml-text for more information on formatting within this section.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / gettingStarted
Namespace No namespace
Annotations
tooltip: Getting Started

summary: A high level overview of interpretation, structure,
                  and content of the dataset.

description: One or more paragraphs that describe the overall
                  interpretation, content and structure of the dataset.  For
                  example, the number and names of data files, they types of
                  measurements that they contain, how those data files fit
                  together in an overall design, and how they relate to the
                  data collections methods, experimental design, and sampling
                  design that are described in other EML sections.  One might
                  describe any specialized software that is available and/or may
                  be necessary for analyzing or interpreting the data, and
                  possibly include a high level description of data formats if
                  they are unusual, keeping in mind that detailed desriptions
                  of data structure and format are contained in the entity
                  sections of EML. Citations, inline figures, and inline
                  images can be included via inline references in Markdown
                  sections. See eml-text for more information on formatting
                  within this section.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
mixed true
Model
Children markdown, para, section
Instance
<gettingStarted xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</gettingStarted>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="gettingStarted" type="txt:TextType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Getting Started summary: A high level overview of interpretation, structure, and content of the dataset. description: One or more paragraphs that describe the overall interpretation, content and structure of the dataset. For example, the number and names of data files, they types of measurements that they contain, how those data files fit together in an overall design, and how they relate to the data collections methods, experimental design, and sampling design that are described in other EML sections. One might describe any specialized software that is available and/or may be necessary for analyzing or interpreting the data, and possibly include a high level description of data formats if they are unusual, keeping in mind that detailed desriptions of data structure and format are contained in the entity sections of EML. Citations, inline figures, and inline images can be included via inline references in Markdown sections. See eml-text for more information on formatting within this section.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / acknowledgements
Namespace No namespace
Annotations
tooltip: Acknowledgements

summary: Text that acknowledges funders and other key
                  contributors.
              

description: One or more sentences that acknowledge funders
                  and other key contributors to the study (excluding the
                  dataset authors listed in the creator field). Note that
                  funding awards are also listed by award number in the
                  eml-project award element, which provides a structured
                  list of funders, award numbers, and award URIs for the dataset.
                  When displaying acknowledgements, client software should
                  provide both the information in this acknowledgements element
                  as well as links from the award element. See eml-text for
                  more information on formatting within this section.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
mixed true
Model
Children markdown, para, section
Instance
<acknowledgements xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</acknowledgements>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="acknowledgements" type="txt:TextType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Acknowledgements summary: Text that acknowledges funders and other key contributors. description: One or more sentences that acknowledge funders and other key contributors to the study (excluding the dataset authors listed in the creator field). Note that funding awards are also listed by award number in the eml-project award element, which provides a structured list of funders, award numbers, and award URIs for the dataset. When displaying acknowledgements, client software should provide both the information in this acknowledgements element as well as links from the award element. See eml-text for more information on formatting within this section.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / maintenance
Namespace No namespace
Annotations
tooltip: Maintenance

summary: A description of the maintenance of this data
              resource.

description: A description of the maintenance of this data
              resource. This includes information about the frequency of
              update, and whether there is ongoing data
              collection.
Diagram
Diagram NO_NAMESPACE.tmp#MaintenanceType_description NO_NAMESPACE.tmp#MaintenanceType_maintenanceUpdateFrequency NO_NAMESPACE.tmp#MaintenanceType_changeHistory dataset-2_2_0.tmp#MaintenanceType
Type MaintenanceType
Properties
content complex
minOccurs 0
Model
Children changeHistory, description, maintenanceUpdateFrequency
Instance
<maintenance>
  <description xml:lang="">{1,1}</description>
  <maintenanceUpdateFrequency>{0,1}</maintenanceUpdateFrequency>
  <changeHistory>{0,unbounded}</changeHistory>
</maintenance>
Source
<xs:element name="maintenance" type="MaintenanceType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Maintenance summary: A description of the maintenance of this data resource. description: A description of the maintenance of this data resource. This includes information about the frequency of update, and whether there is ongoing data collection.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element MaintenanceType / description
Namespace No namespace
Annotations
tooltip: Maintenance Description

summary: A text description of the maintenance of this data
              resource.

description: A text description of the maintenance of this data
              resource.  Note that this field must be marked up using DocBook
              like tagging.  See eml-text for more information.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
mixed true
Model
Children markdown, para, section
Instance
<description xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</description>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="description" type="txt:TextType">
  <xs:annotation>
    <xs:documentation>tooltip: Maintenance Description summary: A text description of the maintenance of this data resource. description: A text description of the maintenance of this data resource. Note that this field must be marked up using DocBook like tagging. See eml-text for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element MaintenanceType / maintenanceUpdateFrequency
Namespace No namespace
Annotations
tooltip: Maintenance Update Frequency

summary: Frequency with which changes and additions are made
            to the dataset
            after the initial dataset is completed.

description: Frequency with which changes and additions are made
            to the dataset
            after the initial dataset is completed.  The values for this
            field must come from the enumeration MaintUpFreqType.
Diagram
Diagram dataset-2_2_0.tmp#MaintUpFreqType
Type MaintUpFreqType
Properties
content simple
minOccurs 0
Facets
enumeration annually
enumeration asNeeded
enumeration biannually
enumeration continually
enumeration daily
enumeration irregular
enumeration monthly
enumeration notPlanned
enumeration weekly
enumeration unknown
enumeration unkown
enumeration otherMaintenancePeriod
Source
<xs:element name="maintenanceUpdateFrequency" type="MaintUpFreqType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Maintenance Update Frequency summary: Frequency with which changes and additions are made to the dataset after the initial dataset is completed. description: Frequency with which changes and additions are made to the dataset after the initial dataset is completed. The values for this field must come from the enumeration MaintUpFreqType.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element MaintenanceType / changeHistory
Namespace No namespace
Annotations
tooltip: Change History

summary: A description of changes made to the data since its
            release.

description: A description of changes made to the data since
            its release.
Diagram
Diagram NO_NAMESPACE.tmp#MaintenanceType_MaintenanceType_changeHistory_changeScope NO_NAMESPACE.tmp#MaintenanceType_MaintenanceType_changeHistory_oldValue NO_NAMESPACE.tmp#MaintenanceType_MaintenanceType_changeHistory_changeDate NO_NAMESPACE.tmp#MaintenanceType_MaintenanceType_changeHistory_comment
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children changeDate, changeScope, comment, oldValue
Instance
<changeHistory>
  <changeScope>{1,1}</changeScope>
  <oldValue>{1,1}</oldValue>
  <changeDate>{1,1}</changeDate>
  <comment>{0,1}</comment>
</changeHistory>
Source
<xs:element name="changeHistory" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Change History summary: A description of changes made to the data since its release. description: A description of changes made to the data since its release.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="changeScope" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Change Scope summary: An expression describing the scope to which the documented change was applied. description: The expression should unambiguously identify the entity(s) and attribute(s) that were changed.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="oldValue" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Old Value summary: The previous value of the data prior to the change. description: The previous value or an expression that describes the previous value of the data.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="changeDate" type="xs:date">
        <xs:annotation>
          <xs:documentation>tooltip: Change Date summary: The date the changes were applied. description: The date the changes were applied.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="comment" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Comment summary: Explanation or justification for the change made to the data. description: Explanation or justification for the change made to the data.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element MaintenanceType / changeHistory / changeScope
Namespace No namespace
Annotations
tooltip: Change Scope

summary: An expression describing the scope to which the
                  documented change was
                  applied.

description: The expression should unambiguously identify
                  the entity(s) and attribute(s) that were
                  changed.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="changeScope" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Change Scope summary: An expression describing the scope to which the documented change was applied. description: The expression should unambiguously identify the entity(s) and attribute(s) that were changed.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element MaintenanceType / changeHistory / oldValue
Namespace No namespace
Annotations
tooltip: Old Value

summary: The previous value of the data prior to the
                  change.

description: The previous value or an expression that
                  describes the previous value of the
                  data.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="oldValue" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Old Value summary: The previous value of the data prior to the change. description: The previous value or an expression that describes the previous value of the data.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element MaintenanceType / changeHistory / changeDate
Namespace No namespace
Annotations
tooltip: Change Date

summary: The date the changes were applied.

description: The date the changes were
                  applied.
Diagram
Diagram
Type xs:date
Properties
content simple
Source
<xs:element name="changeDate" type="xs:date">
  <xs:annotation>
    <xs:documentation>tooltip: Change Date summary: The date the changes were applied. description: The date the changes were applied.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element MaintenanceType / changeHistory / comment
Namespace No namespace
Annotations
tooltip: Comment

summary: Explanation or justification for the change
                  made to the data.

description: Explanation or justification for the change
                  made to the data.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="comment" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Comment summary: Explanation or justification for the change made to the data. description: Explanation or justification for the change made to the data.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / contact
Namespace No namespace
Annotations
tooltip: Contact

summary: The contact for this dataset

description: The contact field contains contact information
              for this dataset. This is the
              person or institution to contact with questions about the use,
              interpretation of a data set.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<contact id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</contact>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="contact" type="rp:ResponsibleParty" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Contact summary: The contact for this dataset description: The contact field contains contact information for this dataset. This is the person or institution to contact with questions about the use, interpretation of a data set.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / publisher
Namespace No namespace
Annotations
tooltip: Data Set Publisher

summary: The publisher of this data set

description: The publisher of this data set. At times this is
              a traditional publishing house, but it may also simply be an
              institution that is making the data available in a published (ie,
              citable) format.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty
Type ResponsibleParty
Properties
content complex
minOccurs 0
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, userId
Instance
<publisher id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
</publisher>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="publisher" type="rp:ResponsibleParty" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Data Set Publisher summary: The publisher of this data set description: The publisher of this data set. At times this is a traditional publishing house, but it may also simply be an institution that is making the data available in a published (ie, citable) format.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / pubPlace
Namespace No namespace
Annotations
tooltip: Publication place

summary: The location that the resource was
              published.

description: The pubPlace field is the location where the
              resource was published, which may be different from where the
              resource was created.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="pubPlace" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Publication place summary: The location that the resource was published. description: The pubPlace field is the location where the resource was published, which may be different from where the resource was created.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / methods
Namespace No namespace
Annotations
tooltip: methods

summary: The methods field documents scientific methods
              used in the collection of this dataset.

description: The methods field documents scientific methods
              used in the collection of this dataset.  It includes information
              on items such as tools, instrument calibration and
              software.
Diagram
Diagram NO_NAMESPACE.tmp#MethodsType_methodStep NO_NAMESPACE.tmp#MethodsType_sampling NO_NAMESPACE.tmp#MethodsType_qualityControl methods-2_2_0.tmp#MethodsType
Type MethodsType
Properties
content complex
minOccurs 0
Model
Children methodStep, qualityControl, sampling
Instance
<methods>
  <methodStep>{1,unbounded}</methodStep>
  <sampling>{0,1}</sampling>
  <qualityControl>{0,unbounded}</qualityControl>
</methods>
Source
<xs:element name="methods" type="md:MethodsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: methods summary: The methods field documents scientific methods used in the collection of this dataset. description: The methods field documents scientific methods used in the collection of this dataset. It includes information on items such as tools, instrument calibration and software.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element MethodsType / methodStep
Namespace No namespace
Annotations
tooltip: method information

summary: Information about the methods employed in collecting
            or generating a data set or other resource.

description: The methodStep field allows for repeated sets of
            elements that document a series of procedures followed to produce a
            data object. These include text descriptions of the procedures,
            relevant literature, software, instrumentation, source data and any
            quality control measures taken.
Diagram
Diagram NO_NAMESPACE.tmp#ProcedureStepType_description NO_NAMESPACE.tmp#ProcedureStepType_citation NO_NAMESPACE.tmp#ProcedureStepType_protocol NO_NAMESPACE.tmp#ProcedureStepType_instrumentation NO_NAMESPACE.tmp#ProcedureStepType_software NO_NAMESPACE.tmp#ProcedureStepType_subStep methods-2_2_0.tmp#ProcedureStepType NO_NAMESPACE.tmp#MethodsType_MethodsType_methodStep_dataSource
Type extension of ProcedureStepType
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
Children citation, dataSource, description, instrumentation, protocol, software, subStep
Instance
<methodStep>
  <description xml:lang="">{1,1}</description>
  <citation id="" scope="document" system="">{1,1}</citation>
  <protocol id="" scope="document" system="">{1,1}</protocol>
  <instrumentation>{0,unbounded}</instrumentation>
  <software id="" scope="document" system="">{0,unbounded}</software>
  <subStep>{0,unbounded}</subStep>
  <dataSource id="" scope="document" system="">{0,unbounded}</dataSource>
</methodStep>
Source
<xs:element name="methodStep" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: method information summary: Information about the methods employed in collecting or generating a data set or other resource. description: The methodStep field allows for repeated sets of elements that document a series of procedures followed to produce a data object. These include text descriptions of the procedures, relevant literature, software, instrumentation, source data and any quality control measures taken.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="ProcedureStepType">
        <xs:sequence>
          <xs:element name="dataSource" type="ds:DatasetType" minOccurs="0" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>tooltip: data source summary: A source of data used by this methodStep. description: A source of data used by this methodStep.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element ProcedureStepType / description
Namespace No namespace
Annotations
tooltip: Methods description

summary: Description of the methods employed in collecting or
              generating a data set or other resource or in quality control and
              assurance.

description: The description field allows for repeated text
              that describes the methodology for a project, experiment, or
              particular data table or to describe the steps taken to control
              or assure the quality of the data. Likewise, a literature
              citation may be provided that describes the methodology that was
              employed. Or the information my be provided by either referencing
              a protocol resource or entering the structured protocol
              information
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
mixed true
Model
Children markdown, para, section
Instance
<description xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</description>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="description" type="txt:TextType">
  <xs:annotation>
    <xs:documentation>tooltip: Methods description summary: Description of the methods employed in collecting or generating a data set or other resource or in quality control and assurance. description: The description field allows for repeated text that describes the methodology for a project, experiment, or particular data table or to describe the steps taken to control or assure the quality of the data. Likewise, a literature citation may be provided that describes the methodology that was employed. Or the information my be provided by either referencing a protocol resource or entering the structured protocol information</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element ProcedureStepType / citation
Namespace No namespace
Annotations
tooltip: citation

summary: Literature citation relating to the methods
              used.

description: The citation field allows to either reference a
              literature resource or enter structured literature
              information
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<citation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</citation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="citation" type="cit:CitationType">
  <xs:annotation>
    <xs:documentation>tooltip: citation summary: Literature citation relating to the methods used. description: The citation field allows to either reference a literature resource or enter structured literature information</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element ProcedureStepType / protocol
Namespace No namespace
Annotations
tooltip: Protocol

summary: Protocol description relating to the methods
              used.

description: The protocol field is used to either reference a
              protocol resource or describe methods and identify the processes
              that have been used to define / improve the quality of a data
              file, also used to identify potential problems with the data
              file.
Diagram
Diagram NO_NAMESPACE.tmp#ProtocolType_id NO_NAMESPACE.tmp#ProtocolType_system NO_NAMESPACE.tmp#ProtocolType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#ProtocolType_proceduralStep NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup protocol-2_2_0.tmp#ProtocolType
Type ProtocolType
Properties
content complex
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, associatedParty, coverage, creator, distribution, intellectualRights, keywordSet, language, licensed, metadataProvider, proceduralStep, pubDate, references, series, shortName, title
Instance
<protocol id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <proceduralStep>{0,unbounded}</proceduralStep>
  <references system="">{1,1}</references>
</protocol>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="protocol" type="pro:ProtocolType">
  <xs:annotation>
    <xs:documentation>tooltip: Protocol summary: Protocol description relating to the methods used. description: The protocol field is used to either reference a protocol resource or describe methods and identify the processes that have been used to define / improve the quality of a data file, also used to identify potential problems with the data file.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element ProtocolType / proceduralStep
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#ProcedureStepType_description NO_NAMESPACE.tmp#ProcedureStepType_citation NO_NAMESPACE.tmp#ProcedureStepType_protocol NO_NAMESPACE.tmp#ProcedureStepType_instrumentation NO_NAMESPACE.tmp#ProcedureStepType_software NO_NAMESPACE.tmp#ProcedureStepType_subStep methods-2_2_0.tmp#ProcedureStepType
Type ProcedureStepType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children citation, description, instrumentation, protocol, software, subStep
Instance
<proceduralStep>
  <description xml:lang="">{1,1}</description>
  <citation id="" scope="document" system="">{1,1}</citation>
  <protocol id="" scope="document" system="">{1,1}</protocol>
  <instrumentation>{0,unbounded}</instrumentation>
  <software id="" scope="document" system="">{0,unbounded}</software>
  <subStep>{0,unbounded}</subStep>
</proceduralStep>
Source
<xs:element name="proceduralStep" type="md:ProcedureStepType" minOccurs="0" maxOccurs="unbounded"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-protocol.xsd
Element ProcedureStepType / instrumentation
Namespace No namespace
Annotations
tooltip: Instrumentation

summary: Instruments used for measurement and recording
            data.

description: The Instrumentation field allows the description
            of any instruments used in the data collection or quality control
            and quality assurance. The description should include vendor, model
            number, optional equipment, etc.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="instrumentation" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Instrumentation summary: Instruments used for measurement and recording data. description: The Instrumentation field allows the description of any instruments used in the data collection or quality control and quality assurance. The description should include vendor, model number, optional equipment, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element ProcedureStepType / software
Namespace No namespace
Annotations
tooltip: Software

summary: Software used in the processing of data.

description: The software element allows reference to any
            software used to process data.
Diagram
Diagram NO_NAMESPACE.tmp#SoftwareType_id NO_NAMESPACE.tmp#SoftwareType_system NO_NAMESPACE.tmp#SoftwareType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#SoftwareType_implementation NO_NAMESPACE.tmp#SoftwareType_dependency NO_NAMESPACE.tmp#SoftwareType_licenseURL NO_NAMESPACE.tmp#SoftwareType_license NO_NAMESPACE.tmp#SoftwareType_version NO_NAMESPACE.tmp#SoftwareType_project NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup software-2_2_0.tmp#SoftwareType
Type SoftwareType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, associatedParty, coverage, creator, dependency, distribution, implementation, intellectualRights, keywordSet, language, license, licenseURL, licensed, metadataProvider, project, pubDate, references, series, shortName, title, version
Instance
<software id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <implementation>{1,unbounded}</implementation>
  <dependency>{0,unbounded}</dependency>
  <licenseURL>{1,1}</licenseURL>
  <license>{1,1}</license>
  <version>{1,1}</version>
  <project id="" scope="document" system="">{0,1}</project>
  <references system="">{1,1}</references>
</software>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="software" type="sw:SoftwareType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Software summary: Software used in the processing of data. description: The software element allows reference to any software used to process data.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element SoftwareType / implementation
Namespace No namespace
Annotations
tooltip: Implementation

summary: Describes the hardware and/or operating system
              requirements for one implementation of a package.

description: Implementation describes the hardware, operating
              system resources a package runs on. Note, a package can have
              multiple implementations. So for example, a package may be
              written in java and the package may run on numerous hardware
              and/or operating systems like Pentium/Linux, Pentium/NT and so
              on. Hardware and Software descriptions that have different
              requirements can be placed here.
Diagram
Diagram NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_distribution NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_size NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_language NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_operatingSystem NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_machineProcessor NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_virtualMachine NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_diskUsage NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_runtimeMemoryUsage NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_programmingLanguage NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_checksum NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_dependency
Properties
content complex
maxOccurs unbounded
Model
Children checksum, dependency, diskUsage, distribution, language, machineProcessor, operatingSystem, programmingLanguage, runtimeMemoryUsage, size, virtualMachine
Instance
<implementation>
  <distribution id="" scope="document" system="">{1,unbounded}</distribution>
  <size>{0,1}</size>
  <language>{0,unbounded}</language>
  <operatingSystem>{0,unbounded}</operatingSystem>
  <machineProcessor>{0,unbounded}</machineProcessor>
  <virtualMachine>{0,1}</virtualMachine>
  <diskUsage>{0,1}</diskUsage>
  <runtimeMemoryUsage>{0,1}</runtimeMemoryUsage>
  <programmingLanguage>{0,unbounded}</programmingLanguage>
  <checksum>{0,1}</checksum>
  <dependency>{0,unbounded}</dependency>
</implementation>
Source
<xs:element name="implementation" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Implementation summary: Describes the hardware and/or operating system requirements for one implementation of a package. description: Implementation describes the hardware, operating system resources a package runs on. Note, a package can have multiple implementations. So for example, a package may be written in java and the package may run on numerous hardware and/or operating systems like Pentium/Linux, Pentium/NT and so on. Hardware and Software descriptions that have different requirements can be placed here.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="distribution" type="phys:PhysicalDistributionType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Distribution summary: Information on how the resource is distributed online and offline description: This field provides information on how the resource is distributed online and offline. Connections to online systems can be described as URLs and as a list of relevant connection parameters.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="size" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Physical Size summary: Physical size of an implementation. description: The physical size of an implementation on disk.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="language" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: International Language summary: The International Language of the software implementation. description: The International Language of the software implementation.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="LanguageValue" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Language Value summary: The actual value for the language or a code for the language. description: The actual value for the language or a code for the language.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="LanguageCodeStandard" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Language Code Standard summary: The International Language Code being used in the field languageValue. description: The International Language Code being used in the field languageValue. See http://www.loc.gov/standards/iso639-2/</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="operatingSystem" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Operating System summary: The operating system(s) an implementation runs on. description: The operating system(s) an implementation runs on.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="machineProcessor" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Machine Processor summary: The machine processor(s) required for executing the implementation. description: The Machine Processor required for executing the implementation.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="virtualMachine" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Virtual Machine summary: The virtual machine that the implementation requires. description: The virtual machine that the implementation requires.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="diskUsage" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Disk Usage summary: The minimum amount of Disk Space required to install this implementation. description: The minimum amount of Disk Space required to install this implementation.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="runtimeMemoryUsage" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Runtime Memory Usage summary: The minimum amount of memory required to run an implementation. description: The minimum amount of memory required to run an implementation.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="programmingLanguage" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Programming Language summary: The computer programming language the software package was programmed in. description: The computer programming language the software package was programmed in.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="checksum" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Checksum summary: The generated checksum value of a software package that is a self-contained module. description: The generated checksum value of a software package that is a self-contained module.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="dependency" type="DependencyType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: dependency summary: This fields documents any dependencies that this implementation might have. description: This fields documents any dependencies that this implementation might have.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / distribution
Namespace No namespace
Annotations
tooltip: Distribution

summary: Information on how the resource is distributed
                   online and offline

description: This field provides information on how the
                   resource is distributed online and offline. Connections to
                   online systems can be described as URLs and as a list of
                   relevant connection parameters.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalDistributionType_id NO_NAMESPACE.tmp#PhysicalDistributionType_system NO_NAMESPACE.tmp#PhysicalDistributionType_scope NO_NAMESPACE.tmp#PhysicalDistributionType_online NO_NAMESPACE.tmp#PhysicalDistributionType_offline NO_NAMESPACE.tmp#PhysicalDistributionType_inline NO_NAMESPACE.tmp#PhysicalDistributionType_access NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup physical-2_2_0.tmp#PhysicalDistributionType
Type PhysicalDistributionType
Properties
content complex
maxOccurs unbounded
Model
Children access, inline, offline, online, references
Instance
<distribution id="" scope="document" system="">
  <online>{1,1}</online>
  <offline>{1,1}</offline>
  <inline>{1,1}</inline>
  <access authSystem="" id="" order="allowFirst" scope="document" system="">{0,1}</access>
  <references system="">{1,1}</references>
</distribution>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="distribution" type="phys:PhysicalDistributionType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Distribution summary: Information on how the resource is distributed online and offline description: This field provides information on how the resource is distributed online and offline. Connections to online systems can be described as URLs and as a list of relevant connection parameters.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element PhysicalDistributionType / online
Namespace No namespace
Annotations
tooltip: online

summary: online

description: Information for a resource that is distributed online.
              Please see the Type definition for complete information.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalOnlineType_onlineDescription NO_NAMESPACE.tmp#PhysicalOnlineType_url NO_NAMESPACE.tmp#PhysicalOnlineType_connection physical-2_2_0.tmp#PhysicalOnlineType
Type PhysicalOnlineType
Properties
content complex
Model
Children connection, onlineDescription, url
Instance
<online>
  <onlineDescription>{0,1}</onlineDescription>
  <url function="download">{1,1}</url>
  <connection id="" scope="document" system="">{1,1}</connection>
</online>
Source
<xs:element name="online" type="PhysicalOnlineType">
  <xs:annotation>
    <xs:documentation>tooltip: online summary: online description: Information for a resource that is distributed online. Please see the Type definition for complete information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalOnlineType / onlineDescription
Namespace No namespace
Annotations
tooltip: onlineDescription

summary: onlineDescription

description: The onlineDescription element can hold a brief description of the content of the online element's online|offline|inline child. This description element could supply content for an html anchor tag.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="onlineDescription" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: onlineDescription summary: onlineDescription description: The onlineDescription element can hold a brief description of the content of the online element's online|offline|inline child. This description element could supply content for an html anchor tag.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalOnlineType / url
Namespace No namespace
Annotations
tooltip: url

summary: url

description: The URL of the resource that is available online.
              Please see the Type definition for complete information.
Diagram
Diagram NO_NAMESPACE.tmp#UrlType_function resource-2_2_0.tmp#UrlType
Type UrlType
Properties
content complex
Attributes
QName Type Default Use
function FunctionType download optional
Source
<xs:element name="url" type="res:UrlType">
  <xs:annotation>
    <xs:documentation>tooltip: url summary: url description: The URL of the resource that is available online. Please see the Type definition for complete information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalOnlineType / connection
Namespace No namespace
Annotations
tooltip: connection

summary: connection

description: A connection to a resource that is available online.
              Please see the Type definition for complete information.
Diagram
Diagram NO_NAMESPACE.tmp#ConnectionType_id NO_NAMESPACE.tmp#ConnectionType_system NO_NAMESPACE.tmp#ConnectionType_scope NO_NAMESPACE.tmp#ConnectionType_connectionDefinition NO_NAMESPACE.tmp#ConnectionType_parameter NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup resource-2_2_0.tmp#ConnectionType
Type ConnectionType
Properties
content complex
Model
Children connectionDefinition, parameter, references
Instance
<connection id="" scope="document" system="">
  <connectionDefinition id="" scope="document" system="">{1,1}</connectionDefinition>
  <parameter>{0,unbounded}</parameter>
  <references system="">{1,1}</references>
</connection>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="connection" type="res:ConnectionType">
  <xs:annotation>
    <xs:documentation>tooltip: connection summary: connection description: A connection to a resource that is available online. Please see the Type definition for complete information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalDistributionType / offline
Namespace No namespace
Annotations
tooltip: offline

summary: offline

description: Information for a resource that is distributed offline.
              Please see the Type definition for complete information.
Diagram
Diagram NO_NAMESPACE.tmp#OfflineType_mediumName NO_NAMESPACE.tmp#OfflineType_mediumDensity NO_NAMESPACE.tmp#OfflineType_mediumDensityUnits NO_NAMESPACE.tmp#OfflineType_mediumVolume NO_NAMESPACE.tmp#OfflineType_mediumFormat NO_NAMESPACE.tmp#OfflineType_mediumNote resource-2_2_0.tmp#OfflineType
Type OfflineType
Properties
content complex
Model
Children mediumDensity, mediumDensityUnits, mediumFormat, mediumName, mediumNote, mediumVolume
Instance
<offline>
  <mediumName>{1,1}</mediumName>
  <mediumDensity>{0,1}</mediumDensity>
  <mediumDensityUnits>{0,1}</mediumDensityUnits>
  <mediumVolume>{0,1}</mediumVolume>
  <mediumFormat>{0,unbounded}</mediumFormat>
  <mediumNote>{0,1}</mediumNote>
</offline>
Source
<xs:element name="offline" type="res:OfflineType">
  <xs:annotation>
    <xs:documentation>tooltip: offline summary: offline description: Information for a resource that is distributed offline. Please see the Type definition for complete information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalDistributionType / inline
Namespace No namespace
Annotations
tooltip: inline

summary: inline

description: Information for a resource that is distributed inline, i.e., along
              with the metadata.
              Please see the Type definition for complete information.
Diagram
Diagram resource-2_2_0.tmp#InlineType
Type InlineType
Properties
content complex
mixed true
Model
ANY element from ANY namespace
Source
<xs:element name="inline" type="res:InlineType">
  <xs:annotation>
    <xs:documentation>tooltip: inline summary: inline description: Information for a resource that is distributed inline, i.e., along with the metadata. Please see the Type definition for complete information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalDistributionType / access
Namespace No namespace
Annotations
tooltip: access

summary: access

description: When this element occurs in a distribution module,
              it controls access only to the resource being described by the same
              distribution parent.
              Please see the Type definition for complete information on constructing
              an access tree.
Diagram
Diagram NO_NAMESPACE.tmp#AccessType_id NO_NAMESPACE.tmp#AccessType_system NO_NAMESPACE.tmp#AccessType_scope NO_NAMESPACE.tmp#AccessType_order NO_NAMESPACE.tmp#AccessType_authSystem NO_NAMESPACE.tmp#AccessType_allow NO_NAMESPACE.tmp#AccessType_deny NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup access-2_2_0.tmp#AccessType
Type AccessType
Properties
content complex
minOccurs 0
Model
Children allow, deny, references
Instance
<access authSystem="" id="" order="allowFirst" scope="document" system="">
  <allow>{1,1}</allow>
  <deny>{1,1}</deny>
  <references system="">{1,1}</references>
</access>
Attributes
QName Type Default Use Annotation
authSystem xs:string required
tooltip: Authentication system

summary: The authentication system is used to verify the user or
          group to whom access is allowed or denied.

description: The authentication system determines the set of
          principals (users + groups) that can be used in the access control
          list, and the membership of users in groups. This element is intended
          to provide a reference to the authentication system that is used to
          verify the user or group. This reference is typically in the form
          of a URI, which includes the connection protocol, Internet host, and
          path to the authentication mechanism.
id IDType optional
order restriction of xs:string allowFirst optional
tooltip: Rule order

summary: The order in which the allow and deny rules should be
          applied.

description: To obtain the desired access control, use the order
          attribute to define which rules should be applied first. The acceptable
          values are 'allowFirst' and 'denyFirst'. If 'allowFirst' is
          specified, then all 'allow' rules are processed, and then overridden
          by all 'deny' rules.  If 'denyFirst' is specified, then all 'deny'
          rules are processed, and then overridden by all 'allow' rules.
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="access" type="acc:AccessType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: access summary: access description: When this element occurs in a distribution module, it controls access only to the resource being described by the same distribution parent. Please see the Type definition for complete information on constructing an access tree.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element SoftwareType / implementation / size
Namespace No namespace
Annotations
tooltip: Physical Size

summary: Physical size of an implementation.
                    

description: The physical size of an implementation on
                    disk.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="size" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Physical Size summary: Physical size of an implementation. description: The physical size of an implementation on disk.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / language
Namespace No namespace
Annotations
tooltip: International Language

summary: The International Language of the software
                    implementation.

description: The International Language of the software
                    implementation.
Diagram
Diagram NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_SoftwareType_SoftwareType_implementation_language_LanguageValue NO_NAMESPACE.tmp#SoftwareType_SoftwareType_implementation_SoftwareType_SoftwareType_implementation_language_LanguageCodeStandard
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children LanguageCodeStandard, LanguageValue
Instance
<language>
  <LanguageValue>{1,1}</LanguageValue>
  <LanguageCodeStandard>{0,1}</LanguageCodeStandard>
</language>
Source
<xs:element name="language" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: International Language summary: The International Language of the software implementation. description: The International Language of the software implementation.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="LanguageValue" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Language Value summary: The actual value for the language or a code for the language. description: The actual value for the language or a code for the language.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="LanguageCodeStandard" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Language Code Standard summary: The International Language Code being used in the field languageValue. description: The International Language Code being used in the field languageValue. See http://www.loc.gov/standards/iso639-2/</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / language / LanguageValue
Namespace No namespace
Annotations
tooltip: Language Value

summary: The actual value for the language or
                          a code for the language.

description: The actual value for the language or
                          a code for the language.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="LanguageValue" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Language Value summary: The actual value for the language or a code for the language. description: The actual value for the language or a code for the language.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / language / LanguageCodeStandard
Namespace No namespace
Annotations
tooltip: Language Code Standard

summary: The International Language Code being
                          used in the field languageValue.

description: The International Language Code being
                          used in the field languageValue. See
                          http://www.loc.gov/standards/iso639-2/
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="LanguageCodeStandard" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Language Code Standard summary: The International Language Code being used in the field languageValue. description: The International Language Code being used in the field languageValue. See http://www.loc.gov/standards/iso639-2/</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / operatingSystem
Namespace No namespace
Annotations
tooltip: Operating System

summary: The operating system(s) an implementation runs
                    on.

description: The operating system(s) an implementation runs
                    on.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="operatingSystem" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Operating System summary: The operating system(s) an implementation runs on. description: The operating system(s) an implementation runs on.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / machineProcessor
Namespace No namespace
Annotations
tooltip: Machine Processor

summary: The machine processor(s) required for
                    executing the implementation.

description: The Machine Processor required for
                    executing the implementation.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="machineProcessor" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Machine Processor summary: The machine processor(s) required for executing the implementation. description: The Machine Processor required for executing the implementation.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / virtualMachine
Namespace No namespace
Annotations
tooltip: Virtual Machine

summary: The virtual machine that the implementation
                    requires.

description: The virtual machine that the implementation
                    requires.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="virtualMachine" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Virtual Machine summary: The virtual machine that the implementation requires. description: The virtual machine that the implementation requires.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / diskUsage
Namespace No namespace
Annotations
tooltip: Disk Usage

summary: The minimum amount of Disk Space required to
                    install this implementation.

description: The minimum amount of Disk Space required to
                    install this implementation.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="diskUsage" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Disk Usage summary: The minimum amount of Disk Space required to install this implementation. description: The minimum amount of Disk Space required to install this implementation.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / runtimeMemoryUsage
Namespace No namespace
Annotations
tooltip: Runtime Memory Usage

summary: The minimum amount of memory required to run
                    an implementation.

description: The minimum amount of memory required to run
                    an implementation.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="runtimeMemoryUsage" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Runtime Memory Usage summary: The minimum amount of memory required to run an implementation. description: The minimum amount of memory required to run an implementation.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / programmingLanguage
Namespace No namespace
Annotations
tooltip: Programming Language

summary: The computer programming language the software
                    package was programmed in.

description: The computer programming language the software
                    package was programmed in.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="programmingLanguage" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Programming Language summary: The computer programming language the software package was programmed in. description: The computer programming language the software package was programmed in.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / checksum
Namespace No namespace
Annotations
tooltip: Checksum

summary: The generated checksum value of a software
                    package that is a self-contained module.

description: The generated checksum value of a software
                    package that is a self-contained module.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="checksum" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Checksum summary: The generated checksum value of a software package that is a self-contained module. description: The generated checksum value of a software package that is a self-contained module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / implementation / dependency
Namespace No namespace
Annotations
tooltip: dependency

summary: This fields documents any dependencies
                    that this implementation might have.

description: This fields documents any dependencies
                    that this implementation might have.
Diagram
Diagram NO_NAMESPACE.tmp#DependencyType_action NO_NAMESPACE.tmp#DependencyType_software software-2_2_0.tmp#DependencyType
Type DependencyType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children action, software
Instance
<dependency>
  <action>{1,1}</action>
  <software id="" scope="document" system="">{1,1}</software>
</dependency>
Source
<xs:element name="dependency" type="DependencyType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: dependency summary: This fields documents any dependencies that this implementation might have. description: This fields documents any dependencies that this implementation might have.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element DependencyType / action
Namespace No namespace
Annotations
tooltip: Action

summary: Describes what action needs to be undertaken (if any)
           for a software dependency at either the software package or
           implementation level.

description: This element and its enumerations of assert and
           install can be used as commands by a software application to carry
           out these actions on software package dependencies. This is a change
           from how we have used all previous elements within eml. Up until now
           all other elements have been simply metadata designed to describe
           data, literature citations, etc... with the Action element we can
           use this module as a command to carry out the action.
Diagram
Diagram software-2_2_0.tmp#Action
Type Action
Properties
content simple
Facets
enumeration install
enumeration assert
Source
<xs:element name="action" type="Action">
  <xs:annotation>
    <xs:documentation>tooltip: Action summary: Describes what action needs to be undertaken (if any) for a software dependency at either the software package or implementation level. description: This element and its enumerations of assert and install can be used as commands by a software application to carry out these actions on software package dependencies. This is a change from how we have used all previous elements within eml. Up until now all other elements have been simply metadata designed to describe data, literature citations, etc... with the Action element we can use this module as a command to carry out the action.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element DependencyType / software
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#SoftwareType_id NO_NAMESPACE.tmp#SoftwareType_system NO_NAMESPACE.tmp#SoftwareType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#SoftwareType_implementation NO_NAMESPACE.tmp#SoftwareType_dependency NO_NAMESPACE.tmp#SoftwareType_licenseURL NO_NAMESPACE.tmp#SoftwareType_license NO_NAMESPACE.tmp#SoftwareType_version NO_NAMESPACE.tmp#SoftwareType_project NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup software-2_2_0.tmp#SoftwareType
Type SoftwareType
Properties
content complex
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, associatedParty, coverage, creator, dependency, distribution, implementation, intellectualRights, keywordSet, language, license, licenseURL, licensed, metadataProvider, project, pubDate, references, series, shortName, title, version
Instance
<software id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <implementation>{1,unbounded}</implementation>
  <dependency>{0,unbounded}</dependency>
  <licenseURL>{1,1}</licenseURL>
  <license>{1,1}</license>
  <version>{1,1}</version>
  <project id="" scope="document" system="">{0,1}</project>
  <references system="">{1,1}</references>
</software>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="software" type="SoftwareType"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / dependency
Namespace No namespace
Annotations
tooltip: dependency

summary: This fields documents any dependencies
              that this software package in general might have.

description: This fields documents any dependencies
              that this software package in general might have.
Diagram
Diagram NO_NAMESPACE.tmp#DependencyType_action NO_NAMESPACE.tmp#DependencyType_software software-2_2_0.tmp#DependencyType
Type DependencyType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children action, software
Instance
<dependency>
  <action>{1,1}</action>
  <software id="" scope="document" system="">{1,1}</software>
</dependency>
Source
<xs:element name="dependency" type="DependencyType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: dependency summary: This fields documents any dependencies that this software package in general might have. description: This fields documents any dependencies that this software package in general might have.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / licenseURL
Namespace No namespace
Annotations
tooltip: URL for License

summary: URL where the license can be found

description: URL where the license can be found
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="licenseURL" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: URL for License summary: URL where the license can be found description: URL where the license can be found</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / license
Namespace No namespace
Annotations
tooltip: License

summary: Text of the license

description: Text of the license
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="license" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: License summary: Text of the license description: Text of the license</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / version
Namespace No namespace
Annotations
tooltip: Version

summary: Version of the software being
              packaged.

description: String value corresponding to the major, minor,
              custom, and build version.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="version" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Version summary: Version of the software being packaged. description: String value corresponding to the major, minor, custom, and build version.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element SoftwareType / project
Namespace No namespace
Annotations
tooltip: project descriptor

summary: 

description: This field is a description of the project with
           which this software product is related.  Please see the eml-project
           module for more information.
Diagram
Diagram NO_NAMESPACE.tmp#ResearchProjectType_id NO_NAMESPACE.tmp#ResearchProjectType_system NO_NAMESPACE.tmp#ResearchProjectType_scope NO_NAMESPACE.tmp#ResearchProjectType_title NO_NAMESPACE.tmp#ResearchProjectType_personnel NO_NAMESPACE.tmp#ResearchProjectType_abstract NO_NAMESPACE.tmp#ResearchProjectType_funding NO_NAMESPACE.tmp#ResearchProjectType_award NO_NAMESPACE.tmp#ResearchProjectType_studyAreaDescription NO_NAMESPACE.tmp#ResearchProjectType_designDescription NO_NAMESPACE.tmp#ResearchProjectType_relatedProject NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup project-2_2_0.tmp#ResearchProjectType
Type ResearchProjectType
Properties
content complex
minOccurs 0
Model
Children abstract, award, designDescription, funding, personnel, references, relatedProject, studyAreaDescription, title
Instance
<project id="" scope="document" system="">
  <title>{1,unbounded}</title>
  <personnel id="" scope="document" system="">{1,unbounded}</personnel>
  <abstract xml:lang="">{0,1}</abstract>
  <funding xml:lang="">{0,1}</funding>
  <award>{0,unbounded}</award>
  <studyAreaDescription>{0,1}</studyAreaDescription>
  <designDescription>{0,1}</designDescription>
  <relatedProject id="" scope="document" system="">{0,unbounded}</relatedProject>
  <references system="">{1,1}</references>
</project>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="project" type="proj:ResearchProjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: project descriptor summary: description: This field is a description of the project with which this software product is related. Please see the eml-project module for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Element ResearchProjectType / title
Namespace No namespace
Annotations
tooltip: Project Title

summary: Title of the project.

description: A descriptive title for the research
              project.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="title" type="res:NonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Project Title summary: Title of the project. description: A descriptive title for the research project.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / personnel
Namespace No namespace
Annotations
tooltip: Personnel

summary: Contact and role information for people involved in
              the research project.

description: The Personnel field extends ResponsibleParty
              with role information and is used to document people involved in
              a research project by providing contact information and their
              role in the project.
Diagram
Diagram NO_NAMESPACE.tmp#ResponsibleParty_id NO_NAMESPACE.tmp#ResponsibleParty_system NO_NAMESPACE.tmp#ResponsibleParty_scope NO_NAMESPACE.tmp#ResponsibleParty_individualName NO_NAMESPACE.tmp#ResponsibleParty_organizationName NO_NAMESPACE.tmp#ResponsibleParty_positionName NO_NAMESPACE.tmp#ResponsibleParty_address NO_NAMESPACE.tmp#ResponsibleParty_phone NO_NAMESPACE.tmp#ResponsibleParty_electronicMailAddress NO_NAMESPACE.tmp#ResponsibleParty_onlineUrl NO_NAMESPACE.tmp#ResponsibleParty_userId NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup party-2_2_0.tmp#ResponsibleParty NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_personnel_role
Type extension of ResponsibleParty
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
Children address, electronicMailAddress, individualName, onlineUrl, organizationName, phone, positionName, references, role, userId
Instance
<personnel id="" scope="document" system="">
  <individualName>{1,1}</individualName>
  <organizationName xml:lang="">{1,1}</organizationName>
  <positionName xml:lang="">{1,1}</positionName>
  <address id="" scope="document" system="">{0,unbounded}</address>
  <phone phonetype="voice">{0,unbounded}</phone>
  <electronicMailAddress xml:lang="">{0,unbounded}</electronicMailAddress>
  <onlineUrl>{0,unbounded}</onlineUrl>
  <userId directory="">{0,unbounded}</userId>
  <references system="">{1,1}</references>
  <role>{1,1}</role>
</personnel>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="personnel" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Personnel summary: Contact and role information for people involved in the research project. description: The Personnel field extends ResponsibleParty with role information and is used to document people involved in a research project by providing contact information and their role in the project.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="rp:ResponsibleParty">
        <xs:sequence maxOccurs="unbounded">
          <xs:element name="role" type="rp:RoleType">
            <xs:annotation>
              <xs:documentation>tooltip: Role summary: Role information for people involved in the research project. description: The role field contains information about role a person plays in a research project. There are a number of suggested roles, however, it is possible to add a role if the suggested roles are not adequate.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / personnel / role
Namespace No namespace
Annotations
tooltip: Role

summary: Role information for people involved in
                        the research project.

description: The role field contains information
                        about role a person plays in a research project. There
                        are a number of suggested roles, however, it is
                        possible to add a role if the suggested roles are not
                        adequate.
Diagram
Diagram party-2_2_0.tmp#RoleType
Type RoleType
Properties
content simple
Source
<xs:element name="role" type="rp:RoleType">
  <xs:annotation>
    <xs:documentation>tooltip: Role summary: Role information for people involved in the research project. description: The role field contains information about role a person plays in a research project. There are a number of suggested roles, however, it is possible to add a role if the suggested roles are not adequate.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / abstract
Namespace No namespace
Annotations
tooltip: Abstract

summary: Project Abstract.

description: Descriptive abstract that summarizes information
              about the research project.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
mixed true
Model
Children markdown, para, section
Instance
<abstract xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</abstract>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="abstract" type="txt:TextType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Abstract summary: Project Abstract. description: Descriptive abstract that summarizes information about the research project.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / funding
Namespace No namespace
Annotations
tooltip: Funding

summary: Funding information.

description: The funding field is used to provide general information
              about the funding for a project, generally in prose form. This field is
              included for historical compatibility, and has been augmented by the
              award field that provides structured information about funding
              included.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
mixed true
Model
Children markdown, para, section
Instance
<funding xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</funding>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="funding" type="txt:TextType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Funding summary: Funding information. description: The funding field is used to provide general information about the funding for a project, generally in prose form. This field is included for historical compatibility, and has been augmented by the award field that provides structured information about funding included.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / award
Namespace No namespace
Annotations
tooltip: Award information

summary: Award information.

description: The award field is used to provide specific information
              about the funding awards for a project in a structured format.  Sub-fields
              are provided for the name of the funding agency, the Open Funder Registry
              identifiers for the agency and program that made the award, the award
              number assigned, the title of the award, and the URL to the award page
              describing the award. The award field replaces the earlier funding field
              from prior EML version releases.  In general, the funding agency should be
              listed with a cross-reference to the appropriate identifier from the
              Open Funder Registry (included in the EML distribution, but which is
              also update periodically from the Open Funder Registry).
Diagram
Diagram NO_NAMESPACE.tmp#AwardType_funderName NO_NAMESPACE.tmp#AwardType_funderIdentifier NO_NAMESPACE.tmp#AwardType_awardNumber NO_NAMESPACE.tmp#AwardType_title NO_NAMESPACE.tmp#AwardType_awardUrl project-2_2_0.tmp#AwardType
Type AwardType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children awardNumber, awardUrl, funderIdentifier, funderName, title
Instance
<award>
  <funderName xml:lang="">{1,1}</funderName>
  <funderIdentifier xml:lang="">{0,unbounded}</funderIdentifier>
  <awardNumber xml:lang="">{0,1}</awardNumber>
  <title xml:lang="">{1,1}</title>
  <awardUrl xml:lang="">{0,1}</awardUrl>
</award>
Source
<xs:element name="award" type="AwardType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Award information summary: Award information. description: The award field is used to provide specific information about the funding awards for a project in a structured format. Sub-fields are provided for the name of the funding agency, the Open Funder Registry identifiers for the agency and program that made the award, the award number assigned, the title of the award, and the URL to the award page describing the award. The award field replaces the earlier funding field from prior EML version releases. In general, the funding agency should be listed with a cross-reference to the appropriate identifier from the Open Funder Registry (included in the EML distribution, but which is also update periodically from the Open Funder Registry).</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element AwardType / funderName
Namespace No namespace
Annotations
tooltip: Funder Name

summary: The name of the funding institution that made this award

description: The name of the funding institution, with fully expanded acronyms
            to show the full, official name of the funding agency. In general, this should match
            the official name of the funder as listed in an Authority such as the Open
            Funder Registry.  The Open Funder Registry and other organizational authorities may
            provide a list of other alternative names for the funding agency.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 1
maxOccurs 1
mixed true
Model
Children value
Instance
<funderName xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</funderName>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="funderName" type="res:i18nNonEmptyStringType" minOccurs="1" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>tooltip: Funder Name summary: The name of the funding institution that made this award description: The name of the funding institution, with fully expanded acronyms to show the full, official name of the funding agency. In general, this should match the official name of the funder as listed in an Authority such as the Open Funder Registry. The Open Funder Registry and other organizational authorities may provide a list of other alternative names for the funding agency.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element AwardType / funderIdentifier
Namespace No namespace
Annotations
tooltip: Funder identifier

summary: The identifier of the funding agency.

description: The funder identifier is used to provide one or more
            canonical identifiers that reference the funder.  These identifiers
            should be globally unique.  The most common form of a funder identifier
            is a DOI identifier of an institution or program drawn from the CrossRef
            Open Funder Registry (https://github.com/Crossref/open-funder-registry),
            which assigns DOIs to each funding agency and to their programs, and
            links these together in a navigable hierarchy.  A copy of the current
            Funder Registry is included as an RDF file with EML for reference, but
            as the list is constantly growing, users can retrieve new copies of the
            RDF file to get updates and current metadata about funders.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
maxOccurs unbounded
mixed true
Model
Children value
Instance
<funderIdentifier xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</funderIdentifier>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="funderIdentifier" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Funder identifier summary: The identifier of the funding agency. description: The funder identifier is used to provide one or more canonical identifiers that reference the funder. These identifiers should be globally unique. The most common form of a funder identifier is a DOI identifier of an institution or program drawn from the CrossRef Open Funder Registry (https://github.com/Crossref/open-funder-registry), which assigns DOIs to each funding agency and to their programs, and links these together in a navigable hierarchy. A copy of the current Funder Registry is included as an RDF file with EML for reference, but as the list is constantly growing, users can retrieve new copies of the RDF file to get updates and current metadata about funders.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element AwardType / awardNumber
Namespace No namespace
Annotations
tooltip: Award Number

summary: The assigned award number.

description: The awardNumber field provides the unique identifier used by
            the funder to uniquely identify an award.  These are typically alphanumeric values
            that are unique within the system used by a given funder.  The number should be listed
            using the canonical form that each funder uses to express its award numbers, and not
            be prefixed or postfixed with extra text such as the acronym of the funder or the name
            of the funder, which is available instead in the funderName field.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
maxOccurs 1
mixed true
Model
Children value
Instance
<awardNumber xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</awardNumber>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="awardNumber" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>tooltip: Award Number summary: The assigned award number. description: The awardNumber field provides the unique identifier used by the funder to uniquely identify an award. These are typically alphanumeric values that are unique within the system used by a given funder. The number should be listed using the canonical form that each funder uses to express its award numbers, and not be prefixed or postfixed with extra text such as the acronym of the funder or the name of the funder, which is available instead in the funderName field.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element AwardType / title
Namespace No namespace
Annotations
tooltip: Title

summary: The title of the award.

description: The title field is used for the title of the award or grant
            being described.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 1
maxOccurs 1
mixed true
Model
Children value
Instance
<title xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</title>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="title" type="res:i18nNonEmptyStringType" minOccurs="1" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>tooltip: Title summary: The title of the award. description: The title field is used for the title of the award or grant being described.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element AwardType / awardUrl
Namespace No namespace
Annotations
tooltip: Award URL

summary: The URL associated with award.

description: Typically, the awardUrl is use to find and locate the award, and
            generally addresses the internet location to find out more information about the
            award.  This should point to a funder site for the award, rather than a project site.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#i18nNonEmptyStringType_value resource-2_2_0.tmp#i18nNonEmptyStringType
Type i18nNonEmptyStringType
Properties
content complex
minOccurs 0
maxOccurs 1
mixed true
Model
Children value
Instance
<awardUrl xml:lang="">
  <value xml:lang="">{0,unbounded}</value>
</awardUrl>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="awardUrl" type="res:i18nNonEmptyStringType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>tooltip: Award URL summary: The URL associated with award. description: Typically, the awardUrl is use to find and locate the award, and generally addresses the internet location to find out more information about the award. This should point to a funder site for the award, rather than a project site.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / studyAreaDescription
Namespace No namespace
Annotations
tooltip: Description of the study area.

summary: Description of the physical area associated with the
              research project, potentially including coverage, climate,
              geology, disturbances, etc.

description: The studyAreaDescription field documents the
              physical area associated with the research project. It can
              include descriptions of the geographic, temporal, and taxonomic
              coverage of the research location and descriptions of domains
              (themes) of interest such as climate, geology, soils or
              disturbances or reference to citable biological or geophysical
              classification systems such as the Bailey Ecoregions or the
              Holdridge Life Zones.
Diagram
Diagram NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_studyAreaDescription_descriptor NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_studyAreaDescription_citation NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_studyAreaDescription_coverage
Properties
content complex
minOccurs 0
Model
Children citation, coverage, descriptor
Instance
<studyAreaDescription>
  <descriptor citableClassificationSystem="" name="">{1,1}</descriptor>
  <citation id="" scope="document" system="">{0,1}</citation>
  <coverage id="" scope="document" system="">{0,1}</coverage>
</studyAreaDescription>
Source
<xs:element name="studyAreaDescription" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Description of the study area. summary: Description of the physical area associated with the research project, potentially including coverage, climate, geology, disturbances, etc. description: The studyAreaDescription field documents the physical area associated with the research project. It can include descriptions of the geographic, temporal, and taxonomic coverage of the research location and descriptions of domains (themes) of interest such as climate, geology, soils or disturbances or reference to citable biological or geophysical classification systems such as the Bailey Ecoregions or the Holdridge Life Zones.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice maxOccurs="unbounded">
      <xs:element name="descriptor">
        <xs:annotation>
          <xs:documentation>tooltip: Non-coverage characteristics of the study area summary: Description of non-coverage characteristics of the study area such as climate, geology, disturbances description: The descriptor field is used to document domains (themes) of interest such as climate, geology, soils or disturbances or references to citable biological or geophysical classification systems such as the Bailey Ecoregions or the Holdridge Life Zones.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence maxOccurs="unbounded">
            <xs:element name="descriptorValue" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Description of some aspect of the study area. summary: Description of some aspect of the study area. description: The descriptorValue field contains the value of a descriptor, describing some aspect of the study area. This may either be a general description in textual form or the value part of a "name/value" pair where the name is entered in the attribute "name_or_id". For example, if the value of the "name" attribute" of the element "descriptor" is "climate", and the value of the attribute "name_or_id" of the element "descriptorValue" is "Annual Precipitation" then the value of this element could be "12.5 inches".</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:simpleContent>
                  <xs:extension base="xs:string">
                    <xs:attribute name="name_or_id" type="xs:string" use="optional">
                      <xs:annotation>
                        <xs:documentation>tooltip: The name or ID of a descriptor value. summary: The name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. description: The name_or_id field is the name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. The values of biogeophysical classification systems, e.g. Bailey-Ecoregions, often take the form of an ID or Code along with a text representation. For example, the ID/Code M131 refers to the phrase "Open Woodland -Tundra". M131 is an unambiguous reference to a more detailed description. If one is using a published classification system then there should be a corresponding citation to the source, e.g., Bailey,R.G., 1996 "Ecosystem Geography".</xs:documentation>
                      </xs:annotation>
                    </xs:attribute>
                  </xs:extension>
                </xs:simpleContent>
              </xs:complexType>
            </xs:element>
            <xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: citation summary: A citation for this descriptor. description: A citation for this descriptor.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="name" type="DescriptorType" use="required">
            <xs:annotation>
              <xs:documentation>tooltip: name summary: The name of the descriptor system. description: The name of the descriptor system. The name can be either a theme such as climate or hydrology, or the name of a citable classification system.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="citableClassificationSystem" type="xs:boolean" use="required">
            <xs:annotation>
              <xs:documentation>tooltip: citation classification system summary: This boolean attribute defines whether this descriptor comes from a citable classification system or not. description: This boolean attribute defines whether this descriptor comes from a citable classification system or not.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
      <xs:element name="citation" type="cit:CitationType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: citation summary: The citation for this descriptor. description: The citation for this descriptor.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="coverage" type="cov:Coverage" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: coverage summary: The coverage of this descriptor. description: The coverage of this descriptor.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / studyAreaDescription / descriptor
Namespace No namespace
Annotations
tooltip: Non-coverage characteristics of the study
                    area

summary: Description of non-coverage characteristics of
                    the study area such as climate, geology,
                    disturbances

description: The descriptor field is used to document
                    domains (themes) of interest such as climate, geology,
                    soils or disturbances or references to citable biological
                    or geophysical classification systems such as the Bailey
                    Ecoregions or the Holdridge Life Zones.
Diagram
Diagram NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_studyAreaDescription_ResearchProjectType_ResearchProjectType_studyAreaDescription_descriptor_name NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_studyAreaDescription_ResearchProjectType_ResearchProjectType_studyAreaDescription_descriptor_citableClassificationSystem NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_studyAreaDescription_ResearchProjectType_ResearchProjectType_studyAreaDescription_descriptor_descriptorValue NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_studyAreaDescription_ResearchProjectType_ResearchProjectType_studyAreaDescription_descriptor_citation
Properties
content complex
Model
Children citation, descriptorValue
Instance
<descriptor citableClassificationSystem="" name="">
  <descriptorValue name_or_id="">{1,unbounded}</descriptorValue>
  <citation id="" scope="document" system="">{0,unbounded}</citation>
</descriptor>
Attributes
QName Type Use Annotation
citableClassificationSystem xs:boolean required
tooltip: citation classification
                        system

summary: This boolean attribute defines whether
                        this descriptor comes from a citable classification
                        system or not.

description: This boolean attribute defines whether
                        this descriptor comes from a citable classification
                        system or not.
name DescriptorType required
tooltip: name

summary: The name of the descriptor
                        system.

description: The name of the descriptor system. The
                        name can be either a theme such as climate or
                        hydrology, or the name of a citable classification
                        system.
Source
<xs:element name="descriptor">
  <xs:annotation>
    <xs:documentation>tooltip: Non-coverage characteristics of the study area summary: Description of non-coverage characteristics of the study area such as climate, geology, disturbances description: The descriptor field is used to document domains (themes) of interest such as climate, geology, soils or disturbances or references to citable biological or geophysical classification systems such as the Bailey Ecoregions or the Holdridge Life Zones.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence maxOccurs="unbounded">
      <xs:element name="descriptorValue" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Description of some aspect of the study area. summary: Description of some aspect of the study area. description: The descriptorValue field contains the value of a descriptor, describing some aspect of the study area. This may either be a general description in textual form or the value part of a "name/value" pair where the name is entered in the attribute "name_or_id". For example, if the value of the "name" attribute" of the element "descriptor" is "climate", and the value of the attribute "name_or_id" of the element "descriptorValue" is "Annual Precipitation" then the value of this element could be "12.5 inches".</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:string">
              <xs:attribute name="name_or_id" type="xs:string" use="optional">
                <xs:annotation>
                  <xs:documentation>tooltip: The name or ID of a descriptor value. summary: The name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. description: The name_or_id field is the name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. The values of biogeophysical classification systems, e.g. Bailey-Ecoregions, often take the form of an ID or Code along with a text representation. For example, the ID/Code M131 refers to the phrase "Open Woodland -Tundra". M131 is an unambiguous reference to a more detailed description. If one is using a published classification system then there should be a corresponding citation to the source, e.g., Bailey,R.G., 1996 "Ecosystem Geography".</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
      <xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: citation summary: A citation for this descriptor. description: A citation for this descriptor.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="name" type="DescriptorType" use="required">
      <xs:annotation>
        <xs:documentation>tooltip: name summary: The name of the descriptor system. description: The name of the descriptor system. The name can be either a theme such as climate or hydrology, or the name of a citable classification system.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="citableClassificationSystem" type="xs:boolean" use="required">
      <xs:annotation>
        <xs:documentation>tooltip: citation classification system summary: This boolean attribute defines whether this descriptor comes from a citable classification system or not. description: This boolean attribute defines whether this descriptor comes from a citable classification system or not.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / studyAreaDescription / descriptor / descriptorValue
Namespace No namespace
Annotations
tooltip: Description of some aspect of the study
                          area.

summary: Description of some aspect of the study
                          area.

description: The descriptorValue field contains
                          the value of a descriptor, describing some aspect of
                          the study area. This may either be a general
                          description in textual form or the value part of a
                          "name/value" pair where the name is entered in the
                          attribute "name_or_id". For example, if the value of
                          the "name" attribute" of the element "descriptor" is
                          "climate", and the value of the attribute
                          "name_or_id" of the element "descriptorValue" is
                          "Annual Precipitation" then the value of this element
                          could be "12.5 inches".
Diagram
Diagram NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_studyAreaDescription_ResearchProjectType_ResearchProjectType_studyAreaDescription_descriptor_ResearchProjectType_ResearchProjectType_studyAreaDescription_ResearchProjectType_ResearchProjectType_studyAreaDescription_descriptor_descriptorValue_name_or_id
Type extension of xs:string
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use Annotation
name_or_id xs:string optional
tooltip: The name or ID of a descriptor
                                  value.

summary: The name part of a name/value
                                  pair of a descriptor; or ID portion of a
                                  classification, if applicable.

description: The name_or_id field is the
                                  name part of a name/value pair of a
                                  descriptor; or ID portion of a
                                  classification, if applicable. The values of
                                  biogeophysical classification systems, e.g.
                                  Bailey-Ecoregions, often take the form of an
                                  ID or Code along with a text representation.
                                  For example, the ID/Code M131 refers to the
                                  phrase "Open Woodland -Tundra". M131 is an
                                  unambiguous reference to a more detailed
                                  description. If one is using a published
                                  classification system then there should be a
                                  corresponding citation to the source, e.g.,
                                  Bailey,R.G., 1996 "Ecosystem
                                  Geography".
Source
<xs:element name="descriptorValue" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Description of some aspect of the study area. summary: Description of some aspect of the study area. description: The descriptorValue field contains the value of a descriptor, describing some aspect of the study area. This may either be a general description in textual form or the value part of a "name/value" pair where the name is entered in the attribute "name_or_id". For example, if the value of the "name" attribute" of the element "descriptor" is "climate", and the value of the attribute "name_or_id" of the element "descriptorValue" is "Annual Precipitation" then the value of this element could be "12.5 inches".</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="name_or_id" type="xs:string" use="optional">
          <xs:annotation>
            <xs:documentation>tooltip: The name or ID of a descriptor value. summary: The name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. description: The name_or_id field is the name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. The values of biogeophysical classification systems, e.g. Bailey-Ecoregions, often take the form of an ID or Code along with a text representation. For example, the ID/Code M131 refers to the phrase "Open Woodland -Tundra". M131 is an unambiguous reference to a more detailed description. If one is using a published classification system then there should be a corresponding citation to the source, e.g., Bailey,R.G., 1996 "Ecosystem Geography".</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / studyAreaDescription / descriptor / citation
Namespace No namespace
Annotations
tooltip: citation

summary: A citation for this
                          descriptor.

description: A citation for this
                          descriptor.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<citation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</citation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: citation summary: A citation for this descriptor. description: A citation for this descriptor.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / studyAreaDescription / citation
Namespace No namespace
Annotations
tooltip: citation

summary: The citation for this
                    descriptor.

description: The citation for this
                    descriptor.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
minOccurs 0
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<citation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</citation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="citation" type="cit:CitationType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: citation summary: The citation for this descriptor. description: The citation for this descriptor.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / studyAreaDescription / coverage
Namespace No namespace
Annotations
tooltip: coverage

summary: The coverage of this descriptor.

description: The coverage of this
                    descriptor.
Diagram
Diagram NO_NAMESPACE.tmp#Coverage_id NO_NAMESPACE.tmp#Coverage_system NO_NAMESPACE.tmp#Coverage_scope NO_NAMESPACE.tmp#Coverage_geographicCoverage NO_NAMESPACE.tmp#Coverage_temporalCoverage NO_NAMESPACE.tmp#Coverage_taxonomicCoverage NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#Coverage
Type Coverage
Properties
content complex
minOccurs 0
Model
Children geographicCoverage, references, taxonomicCoverage, temporalCoverage
Instance
<coverage id="" scope="document" system="">
  <geographicCoverage id="" scope="document" system="">{1,1}</geographicCoverage>
  <temporalCoverage id="" scope="document" system="">{1,1}</temporalCoverage>
  <taxonomicCoverage id="" scope="document" system="">{1,1}</taxonomicCoverage>
  <references system="">{1,1}</references>
</coverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="coverage" type="cov:Coverage" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: coverage summary: The coverage of this descriptor. description: The coverage of this descriptor.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / designDescription
Namespace No namespace
Annotations
tooltip: Description of research design

summary: Description of the design of the research
              project

description: The field designDescription contains general
              textual descriptions of research design. It can include detailed
              accounts of goals, motivations, theory, hypotheses, strategy,
              statistical design, and actual work. Literature citations may
              also be used to describe the research design.
Diagram
Diagram NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_designDescription_description NO_NAMESPACE.tmp#ResearchProjectType_ResearchProjectType_designDescription_citation
Properties
content complex
minOccurs 0
Model
Children citation, description
Instance
<designDescription>
  <description xml:lang="">{1,1}</description>
  <citation id="" scope="document" system="">{0,1}</citation>
</designDescription>
Source
<xs:element name="designDescription" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Description of research design summary: Description of the design of the research project description: The field designDescription contains general textual descriptions of research design. It can include detailed accounts of goals, motivations, theory, hypotheses, strategy, statistical design, and actual work. Literature citations may also be used to describe the research design.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice maxOccurs="unbounded">
      <xs:element name="description" type="txt:TextType">
        <xs:annotation>
          <xs:documentation>tooltip: Description of research design summary: Textual description of research design. description: The field designDescription contains general textual descriptions of research design. It can include detailed accounts of goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="citation" type="cit:CitationType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Citation for research design summary: Citation that describes the research design. description: The citation field is a citation to literature that describes elements of the research design, such as goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / designDescription / description
Namespace No namespace
Annotations
tooltip: Description of research design

summary: Textual description of research
                    design.

description: The field designDescription contains
                    general textual descriptions of research design. It can
                    include detailed accounts of goals, motivations, theory,
                    hypotheses, strategy, statistical design, and actual
                    work.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
mixed true
Model
Children markdown, para, section
Instance
<description xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</description>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="description" type="txt:TextType">
  <xs:annotation>
    <xs:documentation>tooltip: Description of research design summary: Textual description of research design. description: The field designDescription contains general textual descriptions of research design. It can include detailed accounts of goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / designDescription / citation
Namespace No namespace
Annotations
tooltip: Citation for research design

summary: Citation that describes the research
                    design.

description: The citation field is a citation to
                    literature that describes elements of the research design,
                    such as goals, motivations, theory, hypotheses, strategy,
                    statistical design, and actual work.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
minOccurs 0
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<citation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</citation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="citation" type="cit:CitationType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Citation for research design summary: Citation that describes the research design. description: The citation field is a citation to literature that describes elements of the research design, such as goals, motivations, theory, hypotheses, strategy, statistical design, and actual work.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ResearchProjectType / relatedProject
Namespace No namespace
Annotations
tooltip: related project

summary: This field is a recursive link to another
              project.

description: This field is a recursive link to another
              project. This allows projects to be nested under one another for
              the case where one project spawns another.
Diagram
Diagram NO_NAMESPACE.tmp#ResearchProjectType_id NO_NAMESPACE.tmp#ResearchProjectType_system NO_NAMESPACE.tmp#ResearchProjectType_scope NO_NAMESPACE.tmp#ResearchProjectType_title NO_NAMESPACE.tmp#ResearchProjectType_personnel NO_NAMESPACE.tmp#ResearchProjectType_abstract NO_NAMESPACE.tmp#ResearchProjectType_funding NO_NAMESPACE.tmp#ResearchProjectType_award NO_NAMESPACE.tmp#ResearchProjectType_studyAreaDescription NO_NAMESPACE.tmp#ResearchProjectType_designDescription NO_NAMESPACE.tmp#ResearchProjectType_relatedProject NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup project-2_2_0.tmp#ResearchProjectType
Type ResearchProjectType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children abstract, award, designDescription, funding, personnel, references, relatedProject, studyAreaDescription, title
Instance
<relatedProject id="" scope="document" system="">
  <title>{1,unbounded}</title>
  <personnel id="" scope="document" system="">{1,unbounded}</personnel>
  <abstract xml:lang="">{0,1}</abstract>
  <funding xml:lang="">{0,1}</funding>
  <award>{0,unbounded}</award>
  <studyAreaDescription>{0,1}</studyAreaDescription>
  <designDescription>{0,1}</designDescription>
  <relatedProject id="" scope="document" system="">{0,unbounded}</relatedProject>
  <references system="">{1,1}</references>
</relatedProject>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="relatedProject" type="ResearchProjectType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: related project summary: This field is a recursive link to another project. description: This field is a recursive link to another project. This allows projects to be nested under one another for the case where one project spawns another.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Element ProcedureStepType / subStep
Namespace No namespace
Annotations
tooltip: substep

summary: 

description: This fields allows the nesting of additional method
            steps within this step.  This is useful for hierarchical method
            descriptions.
Diagram
Diagram NO_NAMESPACE.tmp#ProcedureStepType_description NO_NAMESPACE.tmp#ProcedureStepType_citation NO_NAMESPACE.tmp#ProcedureStepType_protocol NO_NAMESPACE.tmp#ProcedureStepType_instrumentation NO_NAMESPACE.tmp#ProcedureStepType_software NO_NAMESPACE.tmp#ProcedureStepType_subStep methods-2_2_0.tmp#ProcedureStepType
Type ProcedureStepType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children citation, description, instrumentation, protocol, software, subStep
Instance
<subStep>
  <description xml:lang="">{1,1}</description>
  <citation id="" scope="document" system="">{1,1}</citation>
  <protocol id="" scope="document" system="">{1,1}</protocol>
  <instrumentation>{0,unbounded}</instrumentation>
  <software id="" scope="document" system="">{0,unbounded}</software>
  <subStep>{0,unbounded}</subStep>
</subStep>
Source
<xs:element name="subStep" type="ProcedureStepType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: substep summary: description: This fields allows the nesting of additional method steps within this step. This is useful for hierarchical method descriptions.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / methodStep / dataSource
Namespace No namespace
Annotations
tooltip: data source

summary: A source of data used by this
                      methodStep.

description: A source of data used by this methodStep.
Diagram
Diagram NO_NAMESPACE.tmp#DatasetType_id NO_NAMESPACE.tmp#DatasetType_system NO_NAMESPACE.tmp#DatasetType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#DatasetType_purpose NO_NAMESPACE.tmp#DatasetType_introduction NO_NAMESPACE.tmp#DatasetType_gettingStarted NO_NAMESPACE.tmp#DatasetType_acknowledgements NO_NAMESPACE.tmp#DatasetType_maintenance NO_NAMESPACE.tmp#DatasetType_contact NO_NAMESPACE.tmp#DatasetType_publisher NO_NAMESPACE.tmp#DatasetType_pubPlace NO_NAMESPACE.tmp#DatasetType_methods NO_NAMESPACE.tmp#DatasetType_project NO_NAMESPACE.tmp#DatasetType_dataTable NO_NAMESPACE.tmp#DatasetType_spatialRaster NO_NAMESPACE.tmp#DatasetType_spatialVector NO_NAMESPACE.tmp#DatasetType_storedProcedure NO_NAMESPACE.tmp#DatasetType_view NO_NAMESPACE.tmp#DatasetType_otherEntity NO_NAMESPACE.tmp#DatasetType_referencePublication NO_NAMESPACE.tmp#DatasetType_usageCitation NO_NAMESPACE.tmp#DatasetType_literatureCited NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup dataset-2_2_0.tmp#DatasetType
Type DatasetType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children abstract, acknowledgements, additionalInfo, alternateIdentifier, annotation, associatedParty, contact, coverage, creator, dataTable, distribution, gettingStarted, intellectualRights, introduction, keywordSet, language, licensed, literatureCited, maintenance, metadataProvider, methods, otherEntity, project, pubDate, pubPlace, publisher, purpose, referencePublication, references, series, shortName, spatialRaster, spatialVector, storedProcedure, title, usageCitation, view
Instance
<dataSource id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <purpose xml:lang="">{0,1}</purpose>
  <introduction xml:lang="">{0,1}</introduction>
  <gettingStarted xml:lang="">{0,1}</gettingStarted>
  <acknowledgements xml:lang="">{0,1}</acknowledgements>
  <maintenance>{0,1}</maintenance>
  <contact id="" scope="document" system="">{1,unbounded}</contact>
  <publisher id="" scope="document" system="">{0,1}</publisher>
  <pubPlace>{0,1}</pubPlace>
  <methods>{0,1}</methods>
  <project id="" scope="document" system="">{0,1}</project>
  <dataTable id="" scope="document" system="">{1,1}</dataTable>
  <spatialRaster id="" scope="document" system="">{1,1}</spatialRaster>
  <spatialVector id="" scope="document" system="">{1,1}</spatialVector>
  <storedProcedure id="" scope="document" system="">{1,1}</storedProcedure>
  <view id="" scope="document" system="">{1,1}</view>
  <otherEntity id="" scope="document" system="">{1,1}</otherEntity>
  <referencePublication id="" scope="document" system="">{0,1}</referencePublication>
  <usageCitation id="" scope="document" system="">{0,unbounded}</usageCitation>
  <literatureCited>{0,unbounded}</literatureCited>
  <references system="">{1,1}</references>
</dataSource>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="dataSource" type="ds:DatasetType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: data source summary: A source of data used by this methodStep. description: A source of data used by this methodStep.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element DatasetType / project
Namespace No namespace
Annotations
tooltip: project

summary: The project field contains information on
              the project in which this dataset was collected.

description: The project field contains information on
              the project in which this dataset was collected.  It includes
              information such as project personnel, funding, study area,
              project design and related projects.  The project description
              can also contain documentation on subprojects.
Diagram
Diagram NO_NAMESPACE.tmp#ResearchProjectType_id NO_NAMESPACE.tmp#ResearchProjectType_system NO_NAMESPACE.tmp#ResearchProjectType_scope NO_NAMESPACE.tmp#ResearchProjectType_title NO_NAMESPACE.tmp#ResearchProjectType_personnel NO_NAMESPACE.tmp#ResearchProjectType_abstract NO_NAMESPACE.tmp#ResearchProjectType_funding NO_NAMESPACE.tmp#ResearchProjectType_award NO_NAMESPACE.tmp#ResearchProjectType_studyAreaDescription NO_NAMESPACE.tmp#ResearchProjectType_designDescription NO_NAMESPACE.tmp#ResearchProjectType_relatedProject NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup project-2_2_0.tmp#ResearchProjectType
Type ResearchProjectType
Properties
content complex
minOccurs 0
Model
Children abstract, award, designDescription, funding, personnel, references, relatedProject, studyAreaDescription, title
Instance
<project id="" scope="document" system="">
  <title>{1,unbounded}</title>
  <personnel id="" scope="document" system="">{1,unbounded}</personnel>
  <abstract xml:lang="">{0,1}</abstract>
  <funding xml:lang="">{0,1}</funding>
  <award>{0,unbounded}</award>
  <studyAreaDescription>{0,1}</studyAreaDescription>
  <designDescription>{0,1}</designDescription>
  <relatedProject id="" scope="document" system="">{0,unbounded}</relatedProject>
  <references system="">{1,1}</references>
</project>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="project" type="proj:ResearchProjectType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: project summary: The project field contains information on the project in which this dataset was collected. description: The project field contains information on the project in which this dataset was collected. It includes information such as project personnel, funding, study area, project design and related projects. The project description can also contain documentation on subprojects.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / dataTable
Namespace No namespace
Annotations
tooltip: data table

summary: The dataTable field documents the dataTable(s)
                that make up this dataset.

description: The dataTable field documents the dataTable(s)
                that make up this dataset.  A dataTable could be anything from
                a Comma Separated Value (CSV) file to a spreadsheet to a table
                in an RDBMS.
Diagram
Diagram NO_NAMESPACE.tmp#DataTableType_id NO_NAMESPACE.tmp#DataTableType_system NO_NAMESPACE.tmp#DataTableType_scope NO_NAMESPACE.tmp#EntityGroup_alternateIdentifier NO_NAMESPACE.tmp#EntityGroup_entityName NO_NAMESPACE.tmp#EntityGroup_entityDescription NO_NAMESPACE.tmp#EntityGroup_physical NO_NAMESPACE.tmp#EntityGroup_coverage NO_NAMESPACE.tmp#EntityGroup_methods NO_NAMESPACE.tmp#EntityGroup_additionalInfo NO_NAMESPACE.tmp#EntityGroup_annotation entity-2_2_0.tmp#EntityGroup NO_NAMESPACE.tmp#DataTableType_attributeList NO_NAMESPACE.tmp#DataTableType_constraint NO_NAMESPACE.tmp#DataTableType_caseSensitive NO_NAMESPACE.tmp#DataTableType_numberOfRecords NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup dataTable-2_2_0.tmp#DataTableType
Type DataTableType
Properties
content complex
Model
Children additionalInfo, alternateIdentifier, annotation, attributeList, caseSensitive, constraint, coverage, entityDescription, entityName, methods, numberOfRecords, physical, references
Instance
<dataTable id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <entityName>{1,1}</entityName>
  <entityDescription>{0,1}</entityDescription>
  <physical id="" scope="document" system="">{0,unbounded}</physical>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <methods>{0,1}</methods>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <annotation>{0,unbounded}</annotation>
  <attributeList id="">{1,1}</attributeList>
  <constraint id="" scope="document" system="">{0,unbounded}</constraint>
  <caseSensitive>{0,1}</caseSensitive>
  <numberOfRecords>{0,1}</numberOfRecords>
  <references system="">{1,1}</references>
</dataTable>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="dataTable" type="dat:DataTableType">
  <xs:annotation>
    <xs:documentation>tooltip: data table summary: The dataTable field documents the dataTable(s) that make up this dataset. description: The dataTable field documents the dataTable(s) that make up this dataset. A dataTable could be anything from a Comma Separated Value (CSV) file to a spreadsheet to a table in an RDBMS.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element EntityGroup / alternateIdentifier
Namespace No namespace
Annotations
tooltip: Alternate Identifier

summary: A secondary identifier for this entity

description: An additional, secondary identifier for this
            entity. The primary identifier belongs in the "id" attribute, but
            additional identifiers that are used to label this entity, possibly
            from different data management systems, can be listed
            here.
Diagram
Diagram NO_NAMESPACE.tmp#EntityGroup_EntityGroup_alternateIdentifier_system
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
system SystemType optional
tooltip: Identifier System

summary: The system in which this id is
                    relevant

description: The information management system within
                    which this identifier has relevance. Generally, the
                    identifier would be unique within the "system" and would be
                    sufficient to retrieve the entity from the system. The
                    system is often a URL or URI that identifies the main entry
                    point for the information management
                    system.
Source
<xs:element name="alternateIdentifier" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Alternate Identifier summary: A secondary identifier for this entity description: An additional, secondary identifier for this entity. The primary identifier belongs in the "id" attribute, but additional identifiers that are used to label this entity, possibly from different data management systems, can be listed here.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="system" type="res:SystemType" use="optional">
          <xs:annotation>
            <xs:documentation>tooltip: Identifier System summary: The system in which this id is relevant description: The information management system within which this identifier has relevance. Generally, the identifier would be unique within the "system" and would be sufficient to retrieve the entity from the system. The system is often a URL or URI that identifies the main entry point for the information management system.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element EntityGroup / entityName
Namespace No namespace
Annotations
tooltip: Entity name

summary: The name of the entity name

description: The name identifies the entity in the dataset:
            file name, name of database table, etc.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="entityName" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Entity name summary: The name of the entity name description: The name identifies the entity in the dataset: file name, name of database table, etc.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element EntityGroup / entityDescription
Namespace No namespace
Annotations
tooltip: Entity description

summary: General description of the entity and its
            contents

description: Text generally describing the entity, its type,
            and relevant information about the data in the
            entity.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="entityDescription" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Entity description summary: General description of the entity and its contents description: Text generally describing the entity, its type, and relevant information about the data in the entity.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element EntityGroup / physical
Namespace No namespace
Annotations
tooltip: physical descriptors

summary: Description of the physical format of the entity
            

description: Information on the physical format of this entity.
            Each logical entity can be serialized in one or more physical
            formats, which can be described here.  For each physical format,
            provide a "physical" element that describes the format and how
            to obtain that version.  Two physical elements MUST describe
            the same entity precisely (i.e., after obtaining and parsing
            the physical data stream described under each physical element,
            one MUST end with an identical logical entity).
            For more information see the eml-physical module.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_id NO_NAMESPACE.tmp#PhysicalType_system NO_NAMESPACE.tmp#PhysicalType_scope NO_NAMESPACE.tmp#PhysicalType_objectName NO_NAMESPACE.tmp#PhysicalType_size NO_NAMESPACE.tmp#PhysicalType_authentication NO_NAMESPACE.tmp#PhysicalType_compressionMethod NO_NAMESPACE.tmp#PhysicalType_encodingMethod NO_NAMESPACE.tmp#PhysicalType_characterEncoding NO_NAMESPACE.tmp#PhysicalType_dataFormat NO_NAMESPACE.tmp#PhysicalType_distribution NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup physical-2_2_0.tmp#PhysicalType
Type PhysicalType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children authentication, characterEncoding, compressionMethod, dataFormat, distribution, encodingMethod, objectName, references, size
Instance
<physical id="" scope="document" system="">
  <objectName>{1,1}</objectName>
  <size unit="byte">{0,1}</size>
  <authentication method="">{0,unbounded}</authentication>
  <compressionMethod>{1,1}</compressionMethod>
  <encodingMethod>{1,1}</encodingMethod>
  <characterEncoding>{0,1}</characterEncoding>
  <dataFormat>{1,1}</dataFormat>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <references system="">{1,1}</references>
</physical>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="physical" type="phys:PhysicalType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: physical descriptors summary: Description of the physical format of the entity description: Information on the physical format of this entity. Each logical entity can be serialized in one or more physical formats, which can be described here. For each physical format, provide a "physical" element that describes the format and how to obtain that version. Two physical elements MUST describe the same entity precisely (i.e., after obtaining and parsing the physical data stream described under each physical element, one MUST end with an identical logical entity). For more information see the eml-physical module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element PhysicalType / objectName
Namespace No namespace
Annotations
tooltip: Data object name

summary: The name of the data object.
              

description: The name of the data object.  This is
              possibly distinct from the entity name in that one physical
              object can contain multiple entities, even though that is not
              a recommended practice.  The objectName often is the filename
              of a file in a file system or that is accessible on the network.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="objectName" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Data object name summary: The name of the data object. description: The name of the data object. This is possibly distinct from the entity name in that one physical object can contain multiple entities, even though that is not a recommended practice. The objectName often is the filename of a file in a file system or that is accessible on the network.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / size
Namespace No namespace
Annotations
tooltip: Data object size

summary: Describes the physical size of the
                    data object.

description: This element contains information of the
                    physical size of the entity, by default represented in
                    bytes unless the unit attribute is provided to change
                    the units.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_size_unit
Type extension of xs:string
Properties
content complex
minOccurs 0
Attributes
QName Type Default Use Annotation
unit byte optional
tooltip: Unit of measurement

summary: Unit of measurement for the entity
                            size, by default byte

description: This element gives the unit of
                            measurement for the size of the entity, and is
                            by default a byte.
Source
<xs:element name="size" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Data object size summary: Describes the physical size of the data object. description: This element contains information of the physical size of the entity, by default represented in bytes unless the unit attribute is provided to change the units.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="unit" use="optional" default="byte">
          <xs:annotation>
            <xs:documentation>tooltip: Unit of measurement summary: Unit of measurement for the entity size, by default byte description: This element gives the unit of measurement for the size of the entity, and is by default a byte.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / authentication
Namespace No namespace
Annotations
tooltip: Authentication value

summary: A value, typically a checksum, used to
                    authenticate that the bitstream delivered to the user is
                    identical to the original.

description: This element describes authentication
                    procedures or techniques, typically by giving a checksum
                    value for the object. The method used to compute the
                    authentication value (e.g., MD5) is listed in the method
                    attribute.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_authentication_method
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
method xs:string optional
tooltip: Authentication method

summary: The method used to calculate an
                            authentication checksum.

description: This element names the method used
                            to calculate and authentication checksum that can
                            be used to validate a bytestream. Typical checksum
                            methods include MD5 and CRC.
Source
<xs:element name="authentication" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Authentication value summary: A value, typically a checksum, used to authenticate that the bitstream delivered to the user is identical to the original. description: This element describes authentication procedures or techniques, typically by giving a checksum value for the object. The method used to compute the authentication value (e.g., MD5) is listed in the method attribute.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="method" type="xs:string" use="optional">
          <xs:annotation>
            <xs:documentation>tooltip: Authentication method summary: The method used to calculate an authentication checksum. description: This element names the method used to calculate and authentication checksum that can be used to validate a bytestream. Typical checksum methods include MD5 and CRC.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / compressionMethod
Namespace No namespace
Annotations
tooltip: Compression Method

summary: Name of a compression method applied
                

description: This element lists a compression method used
                to compress the object, such as zip, compress, etc. Compression
                and encoding methods must be listed in the order in which they
                were applied, so that decompression and decoding should
                occur in the reverse order of the listing. For example,
                if a file is compressed using zip and then encoded using
                MIME base64, the compression method would be listed first
                and the encoding method second.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="compressionMethod" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Compression Method summary: Name of a compression method applied description: This element lists a compression method used to compress the object, such as zip, compress, etc. Compression and encoding methods must be listed in the order in which they were applied, so that decompression and decoding should occur in the reverse order of the listing. For example, if a file is compressed using zip and then encoded using MIME base64, the compression method would be listed first and the encoding method second.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / encodingMethod
Namespace No namespace
Annotations
tooltip: Encoding Method

summary: Name of a encoding method applied
                

description: This element lists a encoding method used
                to encode the object, such as base64, BinHex, etc. Compression
                and encoding methods must be listed in the order in which they
                were applied, so that decompression and decoding should
                occur in the reverse order of the listing. For example,
                if a file is compressed using zip and then encoded using
                MIME base64, the compression method would be listed first
                and the encoding method second.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="encodingMethod" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Encoding Method summary: Name of a encoding method applied description: This element lists a encoding method used to encode the object, such as base64, BinHex, etc. Compression and encoding methods must be listed in the order in which they were applied, so that decompression and decoding should occur in the reverse order of the listing. For example, if a file is compressed using zip and then encoded using MIME base64, the compression method would be listed first and the encoding method second.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / characterEncoding
Namespace No namespace
Annotations
tooltip: Character Encoding

summary: Contains the name of the character encoding
                    used for the data.

description: This element contains the name of the
                    character encoding. This is typically ASCII or UTF-8, or
                    one of the other common encodings.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="characterEncoding" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Character Encoding summary: Contains the name of the character encoding used for the data. description: This element contains the name of the character encoding. This is typically ASCII or UTF-8, or one of the other common encodings.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat
Namespace No namespace
Annotations
tooltip: Data format

summary: Describes the internal physical format
            of a data object.

description: This element is the parent which is a CHOICE
            between four possible internal physical formats
            which describe the internal
            physical characteristics of the data object.  Using this
            information the user should be able parse physical object to
              extract the entity and its attributes. Note that this is
            the format of the physical object itself.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_textFormat NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_externallyDefinedFormat NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_binaryRasterFormat
Properties
content complex
Model
Children binaryRasterFormat, externallyDefinedFormat, textFormat
Instance
<dataFormat>
  <textFormat>{1,1}</textFormat>
  <externallyDefinedFormat>{1,1}</externallyDefinedFormat>
  <binaryRasterFormat>{1,1}</binaryRasterFormat>
</dataFormat>
Source
<xs:element name="dataFormat">
  <xs:annotation>
    <xs:documentation>tooltip: Data format summary: Describes the internal physical format of a data object. description: This element is the parent which is a CHOICE between four possible internal physical formats which describe the internal physical characteristics of the data object. Using this information the user should be able parse physical object to extract the entity and its attributes. Note that this is the format of the physical object itself.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="textFormat">
        <xs:annotation>
          <xs:documentation>tooltip: Text Format summary: Description of a text formatted object description: Description of a text formatted object. The description includes detailed parsing instructions for extracting attributes from the bytestream for simple delimited file formats (e.g., CSV), fixed format files that use fixed columns for attribute locations, and mixtures of the two. It also supports records that span multiple lines.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="numHeaderLines" type="xs:int" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Number of header lines summary: Number of header lines preceding data. description: Number of header lines preceding data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of header lines that should be skipped before starting to parse the data.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="numFooterLines" type="xs:int" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Number of footer lines summary: Number of footer lines following data. description: Number of footer lines following data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of footer lines that should be skipped after parsing the data. If this value is omitted, parsers should assume the data continues to the end of the data stream.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="recordDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Record delimiter character summary: Character used to delimit records. description: This element specifies the record delimiter character when the format is text. The record delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As record delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a).</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="physicalLineDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Physical line delimiter character summary: Character used to delimit physical lines. description: This element specifies the physical line delimiter character when the format is text. The line delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As line delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). If this value is not provided, processors should assume that the physical line delimiter is the same as the record delimiter.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="numPhysicalLinesPerRecord" type="xs:unsignedInt" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Physical lines per record summary: The number of physical lines in the file spanned by a single logical data record. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, it is necessary to know the number of lines per record in order to correctly read them. If this value is not provided, processors should assume that records are wholly contained on one physical line. If the value is greater than 1, then processors should examine the lineNumber field for each attribute to determine which line of the record contains the information.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="maxRecordLength" type="xs:unsignedLong" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Maximum record length summary: The maximum number of characters in any record in the physical file. description: The maximum number of characters in any record in the physical file. For delimited files, the record length varies and this is not particularly useful. However, for fixed format files that do not contain record delimiters, this field is critical to tell processors when one record stops and another begins.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="attributeOrientation">
              <xs:annotation>
                <xs:documentation>tooltip: Orientation of attributes summary: Orientation of attributes. description: Specifies whether the attributes described in the physical stream are found in columns or rows. The valid values are column or row. If set to 'column', then the attributes are in columns. If set to 'row', then the attributes are in rows. Row orientation is rare, but some systems such as SPlus and R utilize it. For example, some data with column orientation: DATE PLOT SPECIES 2002-01-15 hfr5 acer rubrum 2002-01-15 hfr5 acer xxxx The same data in a rowMajor table: DATE 2002-01-15 PLOT hfr5 SPECIES acer rubrum acer xxxx</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="column"/>
                  <xs:enumeration value="row"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:choice>
              <xs:element name="simpleDelimited">
                <xs:annotation>
                  <xs:documentation>tooltip: Simple delimited format summary: A simple delimited format. description: A simple delimited format that uses one of a series of delimiters to indicate the ends of fields in the data stream. More complex formats such as fixed format or mixed delimited and fixed formats can be described using the "complex" element.</xs:documentation>
                </xs:annotation>
                <xs:complexType>
                  <xs:sequence>
                    <xs:element name="fieldDelimiter" type="xs:string" maxOccurs="unbounded">
                      <xs:annotation>
                        <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of an attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                    <xs:element name="collapseDelimiters" minOccurs="0">
                      <xs:annotation>
                        <xs:documentation>tooltip: Treat consecutive delimiters as one summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default.</xs:documentation>
                      </xs:annotation>
                      <xs:simpleType>
                        <xs:restriction base="xs:string">
                          <xs:enumeration value="yes"/>
                          <xs:enumeration value="no"/>
                        </xs:restriction>
                      </xs:simpleType>
                    </xs:element>
                    <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
                      <xs:annotation>
                        <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                    <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
                      <xs:annotation>
                        <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                  </xs:sequence>
                </xs:complexType>
              </xs:element>
              <xs:element name="complex">
                <xs:annotation>
                  <xs:documentation>tooltip: Complex text format summary: A complex text format. description: A complex text format that can describe delimited fields, fixed width fields, and mixtures of the two. This supports multiline records (where one record is distributed across multiple physical lines). When using the complex format, the number of textFixed and textDelimited elements should exactly equal the number of attributes that have been described for the entity, and the order of the textFixed and textDelimited elements should correspond to the order of the attributes as described in the entity. Thus, for a delimited file with fourteen attributes, one should provide exactly fourteen textDelimited elements.</xs:documentation>
                </xs:annotation>
                <xs:complexType>
                  <xs:choice maxOccurs="unbounded">
                    <xs:element name="textFixed">
                      <xs:annotation>
                        <xs:documentation>tooltip: Fixed format text summary: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. description: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. This method is common in sensor-derived data and in legacy database systems. To parse it, one must know the number of characters for each attribute and the starting column and line to begin reading the value.</xs:documentation>
                      </xs:annotation>
                      <xs:complexType>
                        <xs:sequence>
                          <xs:element name="fieldWidth" type="xs:unsignedLong">
                            <xs:annotation>
                              <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number.</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                          <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
                            <xs:annotation>
                              <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record.</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                          <xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
                            <xs:annotation>
                              <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                        </xs:sequence>
                      </xs:complexType>
                    </xs:element>
                    <xs:element name="textDelimited">
                      <xs:annotation>
                        <xs:documentation>tooltip: Delimited format text summary: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. description: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. This method is common in data exported from spreadsheets and database systems, To parse it, one must know the character that indicates the end of each attribute and the line to begin reading the value.</xs:documentation>
                      </xs:annotation>
                      <xs:complexType>
                        <xs:sequence>
                          <xs:element name="fieldDelimiter" type="xs:string">
                            <xs:annotation>
                              <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                          <xs:element name="collapseDelimiters" minOccurs="0">
                            <xs:annotation>
                              <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default.</xs:documentation>
                            </xs:annotation>
                            <xs:simpleType>
                              <xs:restriction base="xs:string">
                                <xs:enumeration value="yes"/>
                                <xs:enumeration value="no"/>
                              </xs:restriction>
                            </xs:simpleType>
                          </xs:element>
                          <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
                            <xs:annotation>
                              <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter.</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                          <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
                            <xs:annotation>
                              <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values.</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                          <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
                            <xs:annotation>
                              <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \.</xs:documentation>
                            </xs:annotation>
                          </xs:element>
                        </xs:sequence>
                      </xs:complexType>
                    </xs:element>
                  </xs:choice>
                </xs:complexType>
              </xs:element>
            </xs:choice>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="externallyDefinedFormat">
        <xs:annotation>
          <xs:documentation>tooltip: Externally Defined Format summary: Information about a non-text or proprietary formatted object. description: Information about a non-text or proprietary formatted object. The description names the format explicitly, but assumes a processor implicitly knows how to parse that format to extract the data. A format version can be included. This is mainly used for proprietary formats, including binary files like Microsoft Excel and text formats like ESRI's ArcInfo export format. This is not a recommended way to permanently archive data because the software to parse the format is unlikely to be available over extended periods, but is included to allow for commonly used physical formats.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="formatName" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Format Name summary: Name of the format of the data object description: Name of the format of the data object</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="formatVersion" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Format Version summary: Version of the format of the data object description: Version of the format of the data object</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="citation" type="cit:CitationType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Format citation summary: Citation providing more details about the physical format. description: Citation providing more detail about the physical format, including parsing information or information about the software required for reading the object.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="binaryRasterFormat">
        <xs:annotation>
          <xs:documentation>tooltip: Raster image format summary: Contains binary raster data header parameters description: The binaryRasterInfo element is a container for various parameters used to described the contents of binary raster image files. In this case, it is based on a white paper on the ESRI site that describes the header information used for BIP and BIL files ("Extendable Image Formats for ArcView GIS 3.1 and 3.2").</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="rowColumnOrientation">
              <xs:annotation>
                <xs:documentation>tooltip: Orientation for reading rows and columns summary: Orientation for reading rows and columns. description: Specifies whether the data should be read across rows or down columns. The valid values are column or row. If set to 'column', then the data are read down columns. If set to 'row', then the data are read across rows.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="column"/>
                  <xs:enumeration value="row"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="multiBand" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Multiple band image summary: Multiple band image information. description: Information needed to properly interpret a multiband image.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="nbands" type="xs:int">
                    <xs:annotation>
                      <xs:documentation>tooltip: Number of Bands summary: The number of spectral bands in the image. description: The number of spectral bands in the image. Must be greater than 1.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                  <xs:element name="layout" type="res:NonEmptyStringType">
                    <xs:annotation>
                      <xs:documentation>tooltip: Layout summary: The organization of the bands in the image file. description: The organization of the bands in the image file. Acceptable values are bil - Band interleaved by line. bip - Band interleaved by pixel. bsq - Band sequential.</xs:documentation>
                    </xs:annotation>
                  </xs:element>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
            <xs:element name="nbits" type="xs:int">
              <xs:annotation>
                <xs:documentation>tooltip: Number of Bits summary: The number of bits per pixel per band. description: The number of bits per pixel per band. Acceptable values are typically 1, 4, 8, 16, and 32. The default value is eight bits per pixel per band. For a true color image with three bands (R, G, B) stored using eight bits for each pixel in each band, nbits equals eight and nbands equals three, for a total of twenty-four bits per pixel.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="byteorder" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Byte Order summary: The byte order in which values are stored. description: The byte order in which values are stored. The byte order is important for sixteen-bit and higher images, that have two or more bytes per pixel. Acceptable values are little-endian (common on Intel systems like PCs) and big-endian (common on Motorola platforms).</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="skipbytes" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Skip Bytes summary: The number of bytes of data in the image file to skip in order to reach the start of the image data. description: The number of bytes of data in the image file to skip in order to reach the start of the image data. This keyword allows you to bypass any existing image header information in the file. The default value is zero bytes.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="bandrowbytes" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Bytes per band per row summary: The number of bytes per band per row. description: The number of bytes per band per row. This must be an integer. This keyword is used only with BIL files when there are extra bits at the end of each band within a row that must be skipped.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="totalrowbytes" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Total bytes of data per row summary: The total number of bytes of data per row. description: The total number of bytes of data per row. Use totalrowbytes when there are extra trailing bits at the end of each row.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="bandgapbytes" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Bytes between bands summary: The number of bytes between bands in a BSQ format image. description: The number of bytes between bands in a BSQ format image. The default is zero.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat
Namespace No namespace
Annotations
tooltip: Text Format

summary: Description of a text formatted object
                    

description: Description of a text formatted object.
                    The description includes detailed parsing instructions for
                    extracting attributes from the bytestream for simple
                    delimited file formats (e.g., CSV), fixed format files
                    that use fixed columns for attribute locations, and
                    mixtures of the two.  It also supports records that
                    span multiple lines.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_numHeaderLines NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_numFooterLines NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_recordDelimiter NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_physicalLineDelimiter NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_numPhysicalLinesPerRecord NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_maxRecordLength NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_attributeOrientation NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_simpleDelimited NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex
Properties
content complex
Model
Children attributeOrientation, complex, maxRecordLength, numFooterLines, numHeaderLines, numPhysicalLinesPerRecord, physicalLineDelimiter, recordDelimiter, simpleDelimited
Instance
<textFormat>
  <numHeaderLines>{0,1}</numHeaderLines>
  <numFooterLines>{0,1}</numFooterLines>
  <recordDelimiter>{0,unbounded}</recordDelimiter>
  <physicalLineDelimiter>{0,unbounded}</physicalLineDelimiter>
  <numPhysicalLinesPerRecord>{0,1}</numPhysicalLinesPerRecord>
  <maxRecordLength>{0,1}</maxRecordLength>
  <attributeOrientation>{1,1}</attributeOrientation>
  <simpleDelimited>{1,1}</simpleDelimited>
  <complex>{1,1}</complex>
</textFormat>
Source
<xs:element name="textFormat">
  <xs:annotation>
    <xs:documentation>tooltip: Text Format summary: Description of a text formatted object description: Description of a text formatted object. The description includes detailed parsing instructions for extracting attributes from the bytestream for simple delimited file formats (e.g., CSV), fixed format files that use fixed columns for attribute locations, and mixtures of the two. It also supports records that span multiple lines.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="numHeaderLines" type="xs:int" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Number of header lines summary: Number of header lines preceding data. description: Number of header lines preceding data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of header lines that should be skipped before starting to parse the data.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="numFooterLines" type="xs:int" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Number of footer lines summary: Number of footer lines following data. description: Number of footer lines following data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of footer lines that should be skipped after parsing the data. If this value is omitted, parsers should assume the data continues to the end of the data stream.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="recordDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Record delimiter character summary: Character used to delimit records. description: This element specifies the record delimiter character when the format is text. The record delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As record delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="physicalLineDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Physical line delimiter character summary: Character used to delimit physical lines. description: This element specifies the physical line delimiter character when the format is text. The line delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As line delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). If this value is not provided, processors should assume that the physical line delimiter is the same as the record delimiter.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="numPhysicalLinesPerRecord" type="xs:unsignedInt" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Physical lines per record summary: The number of physical lines in the file spanned by a single logical data record. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, it is necessary to know the number of lines per record in order to correctly read them. If this value is not provided, processors should assume that records are wholly contained on one physical line. If the value is greater than 1, then processors should examine the lineNumber field for each attribute to determine which line of the record contains the information.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="maxRecordLength" type="xs:unsignedLong" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Maximum record length summary: The maximum number of characters in any record in the physical file. description: The maximum number of characters in any record in the physical file. For delimited files, the record length varies and this is not particularly useful. However, for fixed format files that do not contain record delimiters, this field is critical to tell processors when one record stops and another begins.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="attributeOrientation">
        <xs:annotation>
          <xs:documentation>tooltip: Orientation of attributes summary: Orientation of attributes. description: Specifies whether the attributes described in the physical stream are found in columns or rows. The valid values are column or row. If set to 'column', then the attributes are in columns. If set to 'row', then the attributes are in rows. Row orientation is rare, but some systems such as SPlus and R utilize it. For example, some data with column orientation: DATE PLOT SPECIES 2002-01-15 hfr5 acer rubrum 2002-01-15 hfr5 acer xxxx The same data in a rowMajor table: DATE 2002-01-15 PLOT hfr5 SPECIES acer rubrum acer xxxx</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="column"/>
            <xs:enumeration value="row"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:choice>
        <xs:element name="simpleDelimited">
          <xs:annotation>
            <xs:documentation>tooltip: Simple delimited format summary: A simple delimited format. description: A simple delimited format that uses one of a series of delimiters to indicate the ends of fields in the data stream. More complex formats such as fixed format or mixed delimited and fixed formats can be described using the "complex" element.</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:sequence>
              <xs:element name="fieldDelimiter" type="xs:string" maxOccurs="unbounded">
                <xs:annotation>
                  <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of an attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="collapseDelimiters" minOccurs="0">
                <xs:annotation>
                  <xs:documentation>tooltip: Treat consecutive delimiters as one summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default.</xs:documentation>
                </xs:annotation>
                <xs:simpleType>
                  <xs:restriction base="xs:string">
                    <xs:enumeration value="yes"/>
                    <xs:enumeration value="no"/>
                  </xs:restriction>
                </xs:simpleType>
              </xs:element>
              <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
                <xs:annotation>
                  <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values.</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
                <xs:annotation>
                  <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \.</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:sequence>
          </xs:complexType>
        </xs:element>
        <xs:element name="complex">
          <xs:annotation>
            <xs:documentation>tooltip: Complex text format summary: A complex text format. description: A complex text format that can describe delimited fields, fixed width fields, and mixtures of the two. This supports multiline records (where one record is distributed across multiple physical lines). When using the complex format, the number of textFixed and textDelimited elements should exactly equal the number of attributes that have been described for the entity, and the order of the textFixed and textDelimited elements should correspond to the order of the attributes as described in the entity. Thus, for a delimited file with fourteen attributes, one should provide exactly fourteen textDelimited elements.</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:choice maxOccurs="unbounded">
              <xs:element name="textFixed">
                <xs:annotation>
                  <xs:documentation>tooltip: Fixed format text summary: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. description: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. This method is common in sensor-derived data and in legacy database systems. To parse it, one must know the number of characters for each attribute and the starting column and line to begin reading the value.</xs:documentation>
                </xs:annotation>
                <xs:complexType>
                  <xs:sequence>
                    <xs:element name="fieldWidth" type="xs:unsignedLong">
                      <xs:annotation>
                        <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                    <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
                      <xs:annotation>
                        <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                    <xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
                      <xs:annotation>
                        <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                  </xs:sequence>
                </xs:complexType>
              </xs:element>
              <xs:element name="textDelimited">
                <xs:annotation>
                  <xs:documentation>tooltip: Delimited format text summary: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. description: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. This method is common in data exported from spreadsheets and database systems, To parse it, one must know the character that indicates the end of each attribute and the line to begin reading the value.</xs:documentation>
                </xs:annotation>
                <xs:complexType>
                  <xs:sequence>
                    <xs:element name="fieldDelimiter" type="xs:string">
                      <xs:annotation>
                        <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                    <xs:element name="collapseDelimiters" minOccurs="0">
                      <xs:annotation>
                        <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default.</xs:documentation>
                      </xs:annotation>
                      <xs:simpleType>
                        <xs:restriction base="xs:string">
                          <xs:enumeration value="yes"/>
                          <xs:enumeration value="no"/>
                        </xs:restriction>
                      </xs:simpleType>
                    </xs:element>
                    <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
                      <xs:annotation>
                        <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                    <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
                      <xs:annotation>
                        <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                    <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
                      <xs:annotation>
                        <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \.</xs:documentation>
                      </xs:annotation>
                    </xs:element>
                  </xs:sequence>
                </xs:complexType>
              </xs:element>
            </xs:choice>
          </xs:complexType>
        </xs:element>
      </xs:choice>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / numHeaderLines
Namespace No namespace
Annotations
tooltip: Number of header lines

summary: Number of header lines preceding
                          data.

description: Number of header lines preceding
                          data.  Lines are determined by the
                          physicalLineDelimiter, or if it is absent, by the
                          recordDelimiter.  This value indicated the
                          number of header lines that should be skipped
                          before starting to parse the data.
Diagram
Diagram
Type xs:int
Properties
content simple
minOccurs 0
Source
<xs:element name="numHeaderLines" type="xs:int" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Number of header lines summary: Number of header lines preceding data. description: Number of header lines preceding data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of header lines that should be skipped before starting to parse the data.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / numFooterLines
Namespace No namespace
Annotations
tooltip: Number of footer lines

summary: Number of footer lines following
                          data.

description: Number of footer lines following
                          data.  Lines are determined by the
                          physicalLineDelimiter, or if it is absent, by the
                          recordDelimiter.  This value indicated the
                          number of footer lines that should be skipped
                          after parsing the data. If this value is omitted,
                          parsers should assume the data continues to the end
                          of the data stream.
Diagram
Diagram
Type xs:int
Properties
content simple
minOccurs 0
Source
<xs:element name="numFooterLines" type="xs:int" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Number of footer lines summary: Number of footer lines following data. description: Number of footer lines following data. Lines are determined by the physicalLineDelimiter, or if it is absent, by the recordDelimiter. This value indicated the number of footer lines that should be skipped after parsing the data. If this value is omitted, parsers should assume the data continues to the end of the data stream.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / recordDelimiter
Namespace No namespace
Annotations
tooltip: Record delimiter character

summary: Character used to delimit
                          records.

description: This element specifies the record
                          delimiter character when the format is text. The
                          record delimiter is usually a linefeed (\n) on UNIX, a
                          carriage return (\r) on MacOS, or both (\r\n) on
                          Windows/DOS. Multiline records are usually delimited
                          with two line ending characters, for example on UNIX
                          it would be two linefeed characters (\n\n). As record
                          delimiters are often non-printing characters, one can
                          use either the special value "\n" to represent a
                          linefeed (ASCII 0x0a) and "\r" to represent a carriage
                          return (ASCII 0x0d).  Alternatively, one can use the
                          hex value to represent character values (e.g., 0x0a).
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
<xs:element name="recordDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Record delimiter character summary: Character used to delimit records. description: This element specifies the record delimiter character when the format is text. The record delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As record delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a).</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / physicalLineDelimiter
Namespace No namespace
Annotations
tooltip: Physical line delimiter character
                          

summary: Character used to delimit
                          physical lines.

description: This element specifies the physical
                          line delimiter character when the format is text. The
                          line delimiter is usually a linefeed (\n) on UNIX, a
                          carriage return (\r) on MacOS, or both (\r\n) on
                          Windows/DOS. Multiline records are usually delimited
                          with two line ending characters, for example on UNIX
                          it would be two linefeed characters (\n\n). As line
                          delimiters are often non-printing characters, one can
                          use either the special value "\n" to represent a
                          linefeed (ASCII 0x0a) and "\r" to represent a carriage
                          return (ASCII 0x0d).  Alternatively, one can use the
                          hex value to represent character values (e.g., 0x0a).
                          If this value is not provided, processors should
                          assume that the physical line delimiter is the same
                          as the record delimiter.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
<xs:element name="physicalLineDelimiter" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Physical line delimiter character summary: Character used to delimit physical lines. description: This element specifies the physical line delimiter character when the format is text. The line delimiter is usually a linefeed (\n) on UNIX, a carriage return (\r) on MacOS, or both (\r\n) on Windows/DOS. Multiline records are usually delimited with two line ending characters, for example on UNIX it would be two linefeed characters (\n\n). As line delimiters are often non-printing characters, one can use either the special value "\n" to represent a linefeed (ASCII 0x0a) and "\r" to represent a carriage return (ASCII 0x0d). Alternatively, one can use the hex value to represent character values (e.g., 0x0a). If this value is not provided, processors should assume that the physical line delimiter is the same as the record delimiter.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / numPhysicalLinesPerRecord
Namespace No namespace
Annotations
tooltip: Physical lines per record

summary: The number of physical lines in the file
                          spanned by a single logical data record.

description: A single logical data record may be
                          written over several physical lines in a file, with
                          no special marker to indicate the end of a record. In
                          such cases, it is necessary to know the number of
                          lines per record in order to correctly read
                          them. If this value is not provided, processors should
                          assume that records are wholly contained on one
                          physical line.  If the value is greater than 1, then
                          processors should examine the lineNumber field for
                          each attribute to determine which line of the
                          record contains the information.
Diagram
Diagram
Type xs:unsignedInt
Properties
content simple
minOccurs 0
Source
<xs:element name="numPhysicalLinesPerRecord" type="xs:unsignedInt" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Physical lines per record summary: The number of physical lines in the file spanned by a single logical data record. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, it is necessary to know the number of lines per record in order to correctly read them. If this value is not provided, processors should assume that records are wholly contained on one physical line. If the value is greater than 1, then processors should examine the lineNumber field for each attribute to determine which line of the record contains the information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / maxRecordLength
Namespace No namespace
Annotations
tooltip: Maximum record length

summary: The maximum number of characters in any
                          record in the physical file.
                          

description: The maximum number of characters
                          in any record in the physical file.  For delimited
                          files, the record length varies and this is not
                          particularly useful.  However, for fixed format files
                          that do not contain record delimiters, this field is
                          critical to tell processors when one record stops
                          and another begins.
Diagram
Diagram
Type xs:unsignedLong
Properties
content simple
minOccurs 0
Source
<xs:element name="maxRecordLength" type="xs:unsignedLong" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Maximum record length summary: The maximum number of characters in any record in the physical file. description: The maximum number of characters in any record in the physical file. For delimited files, the record length varies and this is not particularly useful. However, for fixed format files that do not contain record delimiters, this field is critical to tell processors when one record stops and another begins.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / attributeOrientation
Namespace No namespace
Annotations
tooltip: Orientation of attributes

summary: Orientation of attributes.

description:  Specifies whether the attributes
                          described in the physical stream are found in
                          columns or rows. The valid values are column or row.
                          If set to 'column', then the attributes are in
                          columns. If set to 'row', then the attributes
                          are in rows.  Row orientation is rare,  but some
                          systems such as SPlus and R utilize it.

                          For example, some data with column orientation:
                          DATE          PLOT           SPECIES
                          2002-01-15    hfr5           acer rubrum
                          2002-01-15    hfr5           acer xxxx

                          The same data in a rowMajor table:
                          DATE   2002-01-15
                          PLOT   hfr5
                          SPECIES acer rubrum  acer xxxx
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration column
enumeration row
Source
<xs:element name="attributeOrientation">
  <xs:annotation>
    <xs:documentation>tooltip: Orientation of attributes summary: Orientation of attributes. description: Specifies whether the attributes described in the physical stream are found in columns or rows. The valid values are column or row. If set to 'column', then the attributes are in columns. If set to 'row', then the attributes are in rows. Row orientation is rare, but some systems such as SPlus and R utilize it. For example, some data with column orientation: DATE PLOT SPECIES 2002-01-15 hfr5 acer rubrum 2002-01-15 hfr5 acer xxxx The same data in a rowMajor table: DATE 2002-01-15 PLOT hfr5 SPECIES acer rubrum acer xxxx</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="column"/>
      <xs:enumeration value="row"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / simpleDelimited
Namespace No namespace
Annotations
tooltip: Simple delimited format
                            

summary: A simple delimited format.
                            

description: A simple delimited format that
                            uses one of a series of delimiters to indicate
                            the ends of fields in the data stream. More
                            complex formats such as fixed format or mixed
                            delimited and fixed formats can be described using
                            the "complex" element.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_simpleDelimited_fieldDelimiter NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_simpleDelimited_collapseDelimiters NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_simpleDelimited_quoteCharacter NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_simpleDelimited_literalCharacter
Properties
content complex
Model
Children collapseDelimiters, fieldDelimiter, literalCharacter, quoteCharacter
Instance
<simpleDelimited>
  <fieldDelimiter>{1,unbounded}</fieldDelimiter>
  <collapseDelimiters>{0,1}</collapseDelimiters>
  <quoteCharacter>{0,unbounded}</quoteCharacter>
  <literalCharacter>{0,unbounded}</literalCharacter>
</simpleDelimited>
Source
<xs:element name="simpleDelimited">
  <xs:annotation>
    <xs:documentation>tooltip: Simple delimited format summary: A simple delimited format. description: A simple delimited format that uses one of a series of delimiters to indicate the ends of fields in the data stream. More complex formats such as fixed format or mixed delimited and fixed formats can be described using the "complex" element.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="fieldDelimiter" type="xs:string" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of an attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="collapseDelimiters" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Treat consecutive delimiters as one summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="yes"/>
            <xs:enumeration value="no"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / simpleDelimited / fieldDelimiter
Namespace No namespace
Annotations
tooltip: Field Delimiter character
                                  

summary: Character used to delimit the
                                  end of an attribute

description: This element specifies
                                  a character to be used in the object for
                                  indicating the ending column for an attribute.
                                  The delimiter character itself is not part
                                  of the attribute value, but rather is present
                                  in the column following the last character
                                  of the value. Typical delimiter characters
                                  include commas, tabs, spaces, and semicolons.
                                  The only time the fieldDelimiter character is
                                  not interpreted as a delimiter is if it
                                  is contained in a quoted string
                                  (see quoteCharacter) or is immediately
                                  preceded by a literalCharacter.
                                  Non-printable quote characters can be
                                  provided as their hex values, and for tab
                                  characters by its ASCII string "\t".
                                  Processors should assume that the field
                                  starts in the column following the previous
                                  field if the previous field was fixed,
                                  or in the column following the delimiter
                                  from the previous field if the previous
                                  field was delimited.
Diagram
Diagram
Type xs:string
Properties
content simple
maxOccurs unbounded
Source
<xs:element name="fieldDelimiter" type="xs:string" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of an attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / simpleDelimited / collapseDelimiters
Namespace No namespace
Annotations
tooltip: Treat consecutive delimiters
                                  as one

summary: Specification of how to
                                  handle consecutive delimiters while
                                  parsing

description: 
                                  The collapseDelimiters element
                                  specifies whether sequential delimiters
                                  should be treated as a single delimiter or
                                  multiple delimiters.    An example is when
                                  a space delimiter is used; often there may
                                  be several repeated spaces that should be
                                  treated as a single delimiter, but not
                                  always. The valid values are yes or no.
                                  If it is set to yes, then consecutive
                                  delimiters will be collapsed to one.  If set
                                  to no or absent, then consecutive delimiters
                                  will be treated as separate delimiters.
                                  Default behaviour is no; hence, consecutive
                                  delimiters will be treated as separate
                                  delimiters, by default.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
Facets
enumeration yes
enumeration no
Source
<xs:element name="collapseDelimiters" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Treat consecutive delimiters as one summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="yes"/>
      <xs:enumeration value="no"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / simpleDelimited / quoteCharacter
Namespace No namespace
Annotations
tooltip: Quote character

summary: Character used to quote values
                                  for delimiter escaping

description: This element specifies
                                  a character to be used in the object for
                                  quoting values so that field delimiters can
                                  be used within the value. This basically
                                  allows delimiter "escaping". The quoteChacter
                                  is typically a " or '. When a processor
                                  encounters a quote character, it should
                                  not interpret any following characters as
                                  a delimiter until a matching quote character
                                  has been encountered (i.e., quotes come in
                                  pairs). It is an error to not provide a
                                  closing quote before the record ends.
                                  Non-printable quote characters can be
                                  provided as their hex values.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / simpleDelimited / literalCharacter
Namespace No namespace
Annotations
tooltip: Literal character

summary: Character used to escape other
                                  special characters

description: This element specifies
                                  a character to be used for escaping
                                  special character values so that they
                                  are treated as literal values.
                                  This allows "escaping" for special
                                  characters like quotes, commas, and spaces
                                  when they are intended to be used in an
                                  attribute value rather than being intended
                                  as a delimiter.  The literalCharacter is
                                  typically a \.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex
Namespace No namespace
Annotations
tooltip: Complex text format
                            

summary: A complex text format.
                            

description: A complex text format that
                            can describe delimited fields, fixed width
                            fields, and mixtures of the two. This supports
                            multiline records (where one record is distributed
                            across multiple physical lines).  When using the
                            complex format, the number of textFixed and
                            textDelimited elements should exactly equal the
                            number of attributes that have been described
                            for the entity, and the order of the textFixed
                            and textDelimited elements should correspond to
                            the order of the attributes as described in the
                            entity. Thus, for a delimited file with fourteen
                            attributes, one should provide exactly fourteen
                            textDelimited elements.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textFixed NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textDelimited
Properties
content complex
Model
Children textDelimited, textFixed
Instance
<complex>
  <textFixed>{1,1}</textFixed>
  <textDelimited>{1,1}</textDelimited>
</complex>
Source
<xs:element name="complex">
  <xs:annotation>
    <xs:documentation>tooltip: Complex text format summary: A complex text format. description: A complex text format that can describe delimited fields, fixed width fields, and mixtures of the two. This supports multiline records (where one record is distributed across multiple physical lines). When using the complex format, the number of textFixed and textDelimited elements should exactly equal the number of attributes that have been described for the entity, and the order of the textFixed and textDelimited elements should correspond to the order of the attributes as described in the entity. Thus, for a delimited file with fourteen attributes, one should provide exactly fourteen textDelimited elements.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice maxOccurs="unbounded">
      <xs:element name="textFixed">
        <xs:annotation>
          <xs:documentation>tooltip: Fixed format text summary: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. description: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. This method is common in sensor-derived data and in legacy database systems. To parse it, one must know the number of characters for each attribute and the starting column and line to begin reading the value.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="fieldWidth" type="xs:unsignedLong">
              <xs:annotation>
                <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="textDelimited">
        <xs:annotation>
          <xs:documentation>tooltip: Delimited format text summary: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. description: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. This method is common in data exported from spreadsheets and database systems, To parse it, one must know the character that indicates the end of each attribute and the line to begin reading the value.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="fieldDelimiter" type="xs:string">
              <xs:annotation>
                <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="collapseDelimiters" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="yes"/>
                  <xs:enumeration value="no"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textFixed
Namespace No namespace
Annotations
tooltip: Fixed format text
                                  

summary: Describes the physical format
                                  of data sequences that use a fixed
                                  number of characters in a specified position
                                  in the stream to locate attribute values.
                                  

description: Describes the physical
                                  format of data sequences that use a fixed
                                  number of characters in a specified position
                                  in the stream to locate attribute values.
                                  This method is common in sensor-derived
                                  data and in legacy database systems.  To
                                  parse it, one must know the number
                                  of characters for each attribute and the
                                  starting column and line to begin reading
                                  the value.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textFixed_fieldWidth NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textFixed_lineNumber NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textFixed_fieldStartColumn
Properties
content complex
Model
Children fieldStartColumn, fieldWidth, lineNumber
Instance
<textFixed>
  <fieldWidth>{1,1}</fieldWidth>
  <lineNumber>{0,1}</lineNumber>
  <fieldStartColumn>{0,1}</fieldStartColumn>
</textFixed>
Source
<xs:element name="textFixed">
  <xs:annotation>
    <xs:documentation>tooltip: Fixed format text summary: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. description: Describes the physical format of data sequences that use a fixed number of characters in a specified position in the stream to locate attribute values. This method is common in sensor-derived data and in legacy database systems. To parse it, one must know the number of characters for each attribute and the starting column and line to begin reading the value.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="fieldWidth" type="xs:unsignedLong">
        <xs:annotation>
          <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textFixed / fieldWidth
Namespace No namespace
Annotations
tooltip: Field width

summary: Field width in
                                        characters for fixed field
                                        length.

description: Fixed width fields
                                        have a set length, thus the end of
                                        the field can always be determined by
                                        adding the fieldWidth to the starting
                                        column number.
Diagram
Diagram
Type xs:unsignedLong
Properties
content simple
Source
<xs:element name="fieldWidth" type="xs:unsignedLong">
  <xs:annotation>
    <xs:documentation>tooltip: Field width summary: Field width in characters for fixed field length. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textFixed / lineNumber
Namespace No namespace
Annotations
tooltip: Physical Line Number
                                        

summary: The line on which
                                        the data field is found, when
                                        the data record is written over
                                        more than one physical line in
                                        the file.

description: A single logical
                                        data record may be written over
                                        several physical lines in a file,
                                        with no special marker to indicate
                                        the end of a record. In such
                                        cases, the relative location of
                                        a data field must be indicated
                                        by both relative row and column
                                        number.  The lineNumber should never
                                        greater that the number of physical
                                        lines per record.
Diagram
Diagram
Type xs:unsignedLong
Properties
content simple
minOccurs 0
Source
<xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never greater that the number of physical lines per record.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textFixed / fieldStartColumn
Namespace No namespace
Annotations
tooltip: Start column
                                        

summary: The starting
                                        column number for a fixed format
                                        attribute.

description: Fixed width fields
                                        have a set length, thus the end of
                                        the field can always be determined by
                                        adding the fieldWidth to the starting
                                        column number. If the starting
                                        column is not provided, processors
                                        should assume that the field starts
                                        in the column following the previous
                                        field if the previous field was fixed,
                                        or in the column following the
                                        delimiter from the previous field if
                                        the previous field was delimited.
Diagram
Diagram
Type xs:long
Properties
content simple
minOccurs 0
Source
<xs:element name="fieldStartColumn" type="xs:long" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Start column summary: The starting column number for a fixed format attribute. description: Fixed width fields have a set length, thus the end of the field can always be determined by adding the fieldWidth to the starting column number. If the starting column is not provided, processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textDelimited
Namespace No namespace
Annotations
tooltip: Delimited format text
                                  

summary: Describes the physical format
                                  of data sequences that use delimiters
                                  in the stream to locate attribute values.
                                  

description: Describes the physical
                                  format of data sequences that use delimiters
                                  in the stream to locate attribute values.
                                  This method is common in data exported from
                                  spreadsheets and database systems,
                                  To parse it, one must know the character
                                  that indicates the end of each attribute
                                  and the line to begin reading the value.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textDelimited_fieldDelimiter NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textDelimited_collapseDelimiters NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textDelimited_lineNumber NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textDelimited_quoteCharacter NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_textFormat_complex_textDelimited_literalCharacter
Properties
content complex
Model
Children collapseDelimiters, fieldDelimiter, lineNumber, literalCharacter, quoteCharacter
Instance
<textDelimited>
  <fieldDelimiter>{1,1}</fieldDelimiter>
  <collapseDelimiters>{0,1}</collapseDelimiters>
  <lineNumber>{0,1}</lineNumber>
  <quoteCharacter>{0,unbounded}</quoteCharacter>
  <literalCharacter>{0,unbounded}</literalCharacter>
</textDelimited>
Source
<xs:element name="textDelimited">
  <xs:annotation>
    <xs:documentation>tooltip: Delimited format text summary: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. description: Describes the physical format of data sequences that use delimiters in the stream to locate attribute values. This method is common in data exported from spreadsheets and database systems, To parse it, one must know the character that indicates the end of each attribute and the line to begin reading the value.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="fieldDelimiter" type="xs:string">
        <xs:annotation>
          <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="collapseDelimiters" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="yes"/>
            <xs:enumeration value="no"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textDelimited / fieldDelimiter
Namespace No namespace
Annotations
tooltip: Field Delimiter character
                                        

summary: Character used
                                        to delimit the end of a particular
                                        attribute

description: This element
                                        specifies a character to be used
                                        in the object for indicating the
                                        ending column for an attribute.
                                        The delimiter character itself is
                                        not part of the attribute value,
                                        but rather is present in the column
                                        following the last character of the
                                        value. Typical delimiter characters
                                        include commas, tabs, spaces,
                                        and semicolons.  The only time the
                                        fieldDelimiter character is not
                                        interpreted as a delimiter is if it
                                        is contained in a quoted string (see
                                        quoteCharacter) or is immediately
                                        preceded by a literalCharacter.
                                        Non-printable quote characters can
                                        be provided as their hex values,
                                        and for tab characters by its ASCII
                                        string "\t".  Processors should
                                        assume that the field starts in the
                                        column following the previous field
                                        if the previous field was fixed,
                                        or in the column following the
                                        delimiter from the previous field
                                        if the previous field was delimited.
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="fieldDelimiter" type="xs:string">
  <xs:annotation>
    <xs:documentation>tooltip: Field Delimiter character summary: Character used to delimit the end of a particular attribute description: This element specifies a character to be used in the object for indicating the ending column for an attribute. The delimiter character itself is not part of the attribute value, but rather is present in the column following the last character of the value. Typical delimiter characters include commas, tabs, spaces, and semicolons. The only time the fieldDelimiter character is not interpreted as a delimiter is if it is contained in a quoted string (see quoteCharacter) or is immediately preceded by a literalCharacter. Non-printable quote characters can be provided as their hex values, and for tab characters by its ASCII string "\t". Processors should assume that the field starts in the column following the previous field if the previous field was fixed, or in the column following the delimiter from the previous field if the previous field was delimited.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textDelimited / collapseDelimiters
Namespace No namespace
Annotations
tooltip: Treat consecutive
                                        delimiters as single

summary: Specification of how
                                        to handle consecutive delimiters
                                        while parsing 

description: 
                                        The collapseDelimiters element
                                        specifies whether sequential delimiters
                                        should be treated as a single delimiter
                                        or multiple delimiters.    An example
                                        is when a space delimiter is used;
                                        often there may be several repeated
                                        spaces that should be treated as a
                                        single delimiter, but not always. The
                                        valid values are yes or no.  If it
                                        is set to yes, then consecutive
                                        delimiters will be collapsed
                                        to one.  If set to no or absent,
                                        then consecutive delimiters will
                                        be treated as separate delimiters.
                                        Default behaviour is no; hence,
                                        consecutive delimiters will be treated
                                        as separate delimiters, by default.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
Facets
enumeration yes
enumeration no
Source
<xs:element name="collapseDelimiters" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Treat consecutive delimiters as single summary: Specification of how to handle consecutive delimiters while parsing description: The collapseDelimiters element specifies whether sequential delimiters should be treated as a single delimiter or multiple delimiters. An example is when a space delimiter is used; often there may be several repeated spaces that should be treated as a single delimiter, but not always. The valid values are yes or no. If it is set to yes, then consecutive delimiters will be collapsed to one. If set to no or absent, then consecutive delimiters will be treated as separate delimiters. Default behaviour is no; hence, consecutive delimiters will be treated as separate delimiters, by default.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="yes"/>
      <xs:enumeration value="no"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textDelimited / lineNumber
Namespace No namespace
Annotations
tooltip: Physical Line Number
                                        

summary: The line on which
                                        the data field is found, when
                                        the data record is written over
                                        more than one physical line in
                                        the file.

description: A single logical
                                        data record may be written over
                                        several physical lines in a file,
                                        with no special marker to indicate
                                        the end of a record. In such
                                        cases, the relative location of
                                        a data field must be indicated
                                        by both relative row and column
                                        number.
                                        The lineNumber should never be
                                        greater that the number of physical
                                        lines per record.  When parsing the
                                        first field on a physical line as
                                        a delimited field, they should assume
                                        that the field data starts in the
                                        first column.  Otherwise, follow the
                                        rules indicated under fieldDelimiter.
Diagram
Diagram
Type xs:unsignedLong
Properties
content simple
minOccurs 0
Source
<xs:element name="lineNumber" type="xs:unsignedLong" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Physical Line Number summary: The line on which the data field is found, when the data record is written over more than one physical line in the file. description: A single logical data record may be written over several physical lines in a file, with no special marker to indicate the end of a record. In such cases, the relative location of a data field must be indicated by both relative row and column number. The lineNumber should never be greater that the number of physical lines per record. When parsing the first field on a physical line as a delimited field, they should assume that the field data starts in the first column. Otherwise, follow the rules indicated under fieldDelimiter.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textDelimited / quoteCharacter
Namespace No namespace
Annotations
tooltip: Quote character
                                        

summary: Character used
                                        to quote values for delimiter
                                        escaping

description: This element
                                        specifies a character to be used in
                                        the object for quoting values so
                                        that field delimiters can be used
                                        within the value. This basically
                                        allows delimiter "escaping". The
                                        quoteChacter is typically a " or
                                        '. When a processor encounters
                                        a quote character, it should not
                                        interpret any following characters
                                        as a delimiter until a matching
                                        quote character has been encountered
                                        (i.e., quotes come in pairs). It is
                                        an error to not provide a closing
                                        quote before the record ends.
                                        Non-printable quote characters
                                        can be provided as their hex
                                        values.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="quoteCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Quote character summary: Character used to quote values for delimiter escaping description: This element specifies a character to be used in the object for quoting values so that field delimiters can be used within the value. This basically allows delimiter "escaping". The quoteChacter is typically a " or '. When a processor encounters a quote character, it should not interpret any following characters as a delimiter until a matching quote character has been encountered (i.e., quotes come in pairs). It is an error to not provide a closing quote before the record ends. Non-printable quote characters can be provided as their hex values.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / textFormat / complex / textDelimited / literalCharacter
Namespace No namespace
Annotations
tooltip: Literal character
                                        

summary: Character used
                                        to escape other special
                                        characters

description: This element
                                        specifies a character to be used
                                        for escaping special character
                                        values so that they are treated
                                        as literal values.  This allows
                                        "escaping" for special characters
                                        like quotes, commas, and spaces
                                        when they are intended to be used
                                        in an attribute value rather than
                                        being intended as a delimiter.
                                        The literalCharacter is typically
                                        a \.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="literalCharacter" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Literal character summary: Character used to escape other special characters description: This element specifies a character to be used for escaping special character values so that they are treated as literal values. This allows "escaping" for special characters like quotes, commas, and spaces when they are intended to be used in an attribute value rather than being intended as a delimiter. The literalCharacter is typically a \.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / externallyDefinedFormat
Namespace No namespace
Annotations
tooltip: Externally Defined Format

summary: Information about a non-text or proprietary
                    formatted object.
                    

description: Information about a non-text or
                    proprietary formatted object.
                    The description names the format explicitly, but assumes
                    a processor implicitly knows how to parse that format
                    to extract the data.  A format version can be included.
                    This is mainly used for proprietary formats, including
                    binary files like Microsoft Excel and text formats like
                    ESRI's ArcInfo export format.  This is not a recommended
                    way to permanently archive data because the software to
                    parse the format is unlikely to be available over extended
                    periods, but is included to allow for commonly used
                    physical formats.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_externallyDefinedFormat_formatName NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_externallyDefinedFormat_formatVersion NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_externallyDefinedFormat_citation
Properties
content complex
Model
Children citation, formatName, formatVersion
Instance
<externallyDefinedFormat>
  <formatName>{1,1}</formatName>
  <formatVersion>{0,1}</formatVersion>
  <citation id="" scope="document" system="">{0,1}</citation>
</externallyDefinedFormat>
Source
<xs:element name="externallyDefinedFormat">
  <xs:annotation>
    <xs:documentation>tooltip: Externally Defined Format summary: Information about a non-text or proprietary formatted object. description: Information about a non-text or proprietary formatted object. The description names the format explicitly, but assumes a processor implicitly knows how to parse that format to extract the data. A format version can be included. This is mainly used for proprietary formats, including binary files like Microsoft Excel and text formats like ESRI's ArcInfo export format. This is not a recommended way to permanently archive data because the software to parse the format is unlikely to be available over extended periods, but is included to allow for commonly used physical formats.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="formatName" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Format Name summary: Name of the format of the data object description: Name of the format of the data object</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="formatVersion" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Format Version summary: Version of the format of the data object description: Version of the format of the data object</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="citation" type="cit:CitationType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Format citation summary: Citation providing more details about the physical format. description: Citation providing more detail about the physical format, including parsing information or information about the software required for reading the object.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / externallyDefinedFormat / formatName
Namespace No namespace
Annotations
tooltip: Format Name

summary: Name of the format of the data
                          object

description: Name of the format of
                          the data object
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="formatName" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Format Name summary: Name of the format of the data object description: Name of the format of the data object</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / externallyDefinedFormat / formatVersion
Namespace No namespace
Annotations
tooltip: Format Version

summary: Version of the format of the
                    data object

description: Version of the format of
                          the data object
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="formatVersion" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Format Version summary: Version of the format of the data object description: Version of the format of the data object</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / externallyDefinedFormat / citation
Namespace No namespace
Annotations
tooltip: Format citation

summary: Citation providing more details about
                          the physical format.
                          

description: Citation providing more detail about
                          the physical format, including parsing information
                          or information about the software required for
                          reading the object.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
minOccurs 0
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<citation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</citation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="citation" type="cit:CitationType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Format citation summary: Citation providing more details about the physical format. description: Citation providing more detail about the physical format, including parsing information or information about the software required for reading the object.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat
Namespace No namespace
Annotations
tooltip: Raster image format

summary: Contains binary raster data header
                    parameters

description: The binaryRasterInfo element is a
                    container for various parameters used to described the
                    contents of binary raster image files. In this case, it is
                    based on a white paper on the ESRI site that describes the
                    header information used for BIP and BIL files ("Extendable
                    Image Formats for ArcView GIS 3.1 and
                    3.2").
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_rowColumnOrientation NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_multiBand NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_nbits NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_byteorder NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_skipbytes NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_bandrowbytes NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_totalrowbytes NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_bandgapbytes
Properties
content complex
Model
Children bandgapbytes, bandrowbytes, byteorder, multiBand, nbits, rowColumnOrientation, skipbytes, totalrowbytes
Instance
<binaryRasterFormat>
  <rowColumnOrientation>{1,1}</rowColumnOrientation>
  <multiBand>{0,1}</multiBand>
  <nbits>{1,1}</nbits>
  <byteorder>{1,1}</byteorder>
  <skipbytes>{0,1}</skipbytes>
  <bandrowbytes>{0,1}</bandrowbytes>
  <totalrowbytes>{0,1}</totalrowbytes>
  <bandgapbytes>{0,1}</bandgapbytes>
</binaryRasterFormat>
Source
<xs:element name="binaryRasterFormat">
  <xs:annotation>
    <xs:documentation>tooltip: Raster image format summary: Contains binary raster data header parameters description: The binaryRasterInfo element is a container for various parameters used to described the contents of binary raster image files. In this case, it is based on a white paper on the ESRI site that describes the header information used for BIP and BIL files ("Extendable Image Formats for ArcView GIS 3.1 and 3.2").</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="rowColumnOrientation">
        <xs:annotation>
          <xs:documentation>tooltip: Orientation for reading rows and columns summary: Orientation for reading rows and columns. description: Specifies whether the data should be read across rows or down columns. The valid values are column or row. If set to 'column', then the data are read down columns. If set to 'row', then the data are read across rows.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="column"/>
            <xs:enumeration value="row"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="multiBand" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Multiple band image summary: Multiple band image information. description: Information needed to properly interpret a multiband image.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="nbands" type="xs:int">
              <xs:annotation>
                <xs:documentation>tooltip: Number of Bands summary: The number of spectral bands in the image. description: The number of spectral bands in the image. Must be greater than 1.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="layout" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Layout summary: The organization of the bands in the image file. description: The organization of the bands in the image file. Acceptable values are bil - Band interleaved by line. bip - Band interleaved by pixel. bsq - Band sequential.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="nbits" type="xs:int">
        <xs:annotation>
          <xs:documentation>tooltip: Number of Bits summary: The number of bits per pixel per band. description: The number of bits per pixel per band. Acceptable values are typically 1, 4, 8, 16, and 32. The default value is eight bits per pixel per band. For a true color image with three bands (R, G, B) stored using eight bits for each pixel in each band, nbits equals eight and nbands equals three, for a total of twenty-four bits per pixel.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="byteorder" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Byte Order summary: The byte order in which values are stored. description: The byte order in which values are stored. The byte order is important for sixteen-bit and higher images, that have two or more bytes per pixel. Acceptable values are little-endian (common on Intel systems like PCs) and big-endian (common on Motorola platforms).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="skipbytes" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Skip Bytes summary: The number of bytes of data in the image file to skip in order to reach the start of the image data. description: The number of bytes of data in the image file to skip in order to reach the start of the image data. This keyword allows you to bypass any existing image header information in the file. The default value is zero bytes.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="bandrowbytes" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Bytes per band per row summary: The number of bytes per band per row. description: The number of bytes per band per row. This must be an integer. This keyword is used only with BIL files when there are extra bits at the end of each band within a row that must be skipped.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="totalrowbytes" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Total bytes of data per row summary: The total number of bytes of data per row. description: The total number of bytes of data per row. Use totalrowbytes when there are extra trailing bits at the end of each row.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="bandgapbytes" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Bytes between bands summary: The number of bytes between bands in a BSQ format image. description: The number of bytes between bands in a BSQ format image. The default is zero.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / rowColumnOrientation
Namespace No namespace
Annotations
tooltip: Orientation for reading rows and columns
                          

summary: Orientation for reading rows and columns.
                          

description:  Specifies whether the data should
                          be read across rows or down columns.  The valid
                          values are column or row.  If set to 'column', then
                          the data are read down columns. If set to 'row',
                          then the data are read across rows.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration column
enumeration row
Source
<xs:element name="rowColumnOrientation">
  <xs:annotation>
    <xs:documentation>tooltip: Orientation for reading rows and columns summary: Orientation for reading rows and columns. description: Specifies whether the data should be read across rows or down columns. The valid values are column or row. If set to 'column', then the data are read down columns. If set to 'row', then the data are read across rows.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="column"/>
      <xs:enumeration value="row"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / multiBand
Namespace No namespace
Annotations
tooltip: Multiple band image

summary: Multiple band image information.
                          

description: Information needed to properly
                          interpret a multiband image.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_multiBand_nbands NO_NAMESPACE.tmp#PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_PhysicalType_PhysicalType_dataFormat_PhysicalType_PhysicalType_dataFormat_binaryRasterFormat_multiBand_layout
Properties
content complex
minOccurs 0
Model
Children layout, nbands
Instance
<multiBand>
  <nbands>{1,1}</nbands>
  <layout>{1,1}</layout>
</multiBand>
Source
<xs:element name="multiBand" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Multiple band image summary: Multiple band image information. description: Information needed to properly interpret a multiband image.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="nbands" type="xs:int">
        <xs:annotation>
          <xs:documentation>tooltip: Number of Bands summary: The number of spectral bands in the image. description: The number of spectral bands in the image. Must be greater than 1.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="layout" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Layout summary: The organization of the bands in the image file. description: The organization of the bands in the image file. Acceptable values are bil - Band interleaved by line. bip - Band interleaved by pixel. bsq - Band sequential.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / multiBand / nbands
Namespace No namespace
Annotations
tooltip: Number of Bands

summary: The number of spectral bands in the
                                image.

description: The number of spectral
                                bands in the image. Must be greater than 1.
Diagram
Diagram
Type xs:int
Properties
content simple
Source
<xs:element name="nbands" type="xs:int">
  <xs:annotation>
    <xs:documentation>tooltip: Number of Bands summary: The number of spectral bands in the image. description: The number of spectral bands in the image. Must be greater than 1.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / multiBand / layout
Namespace No namespace
Annotations
tooltip: Layout

summary: The organization of the bands
                                in the image file.

description: The organization of
                                the bands in the image file. Acceptable
                                values are bil - Band interleaved by
                                line. bip - Band interleaved by pixel.
                                bsq - Band sequential.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="layout" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Layout summary: The organization of the bands in the image file. description: The organization of the bands in the image file. Acceptable values are bil - Band interleaved by line. bip - Band interleaved by pixel. bsq - Band sequential.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / nbits
Namespace No namespace
Annotations
tooltip: Number of Bits

summary: The number of bits per pixel per
                          band.

description: The number of bits per pixel per
                          band. Acceptable values are typically 1, 4, 8, 16,
                          and 32. The default value is eight bits per pixel per
                          band. For a true color image with three bands (R, G,
                          B) stored using eight bits for each pixel in each
                          band, nbits equals eight and nbands equals three,
                          for a total of twenty-four bits per pixel.
Diagram
Diagram
Type xs:int
Properties
content simple
Source
<xs:element name="nbits" type="xs:int">
  <xs:annotation>
    <xs:documentation>tooltip: Number of Bits summary: The number of bits per pixel per band. description: The number of bits per pixel per band. Acceptable values are typically 1, 4, 8, 16, and 32. The default value is eight bits per pixel per band. For a true color image with three bands (R, G, B) stored using eight bits for each pixel in each band, nbits equals eight and nbands equals three, for a total of twenty-four bits per pixel.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / byteorder
Namespace No namespace
Annotations
tooltip: Byte Order

summary: The byte order in which values are
                          stored.

description: The byte order in which
                          values are stored. The byte order is important for
                          sixteen-bit and higher images, that have two or more
                          bytes per pixel.
                          Acceptable values are little-endian (common on Intel
                          systems like PCs) and big-endian (common on
                          Motorola platforms).
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="byteorder" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Byte Order summary: The byte order in which values are stored. description: The byte order in which values are stored. The byte order is important for sixteen-bit and higher images, that have two or more bytes per pixel. Acceptable values are little-endian (common on Intel systems like PCs) and big-endian (common on Motorola platforms).</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / skipbytes
Namespace No namespace
Annotations
tooltip: Skip Bytes

summary: The number of bytes of data in the
                          image file to skip in order to reach the start of the
                          image data.

description: The number of bytes of data in the
                          image file to skip in order to reach the start of the
                          image data. This keyword allows you to bypass any
                          existing image header information in the file. The
                          default value is zero bytes.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="skipbytes" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Skip Bytes summary: The number of bytes of data in the image file to skip in order to reach the start of the image data. description: The number of bytes of data in the image file to skip in order to reach the start of the image data. This keyword allows you to bypass any existing image header information in the file. The default value is zero bytes.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / bandrowbytes
Namespace No namespace
Annotations
tooltip: Bytes per band per row

summary: The number of bytes per band per
                          row.

description: The number of bytes per band per
                          row. This must be an integer. This keyword is used
                          only with BIL files when there are extra bits at the
                          end of each band within a row that must be
                          skipped.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="bandrowbytes" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Bytes per band per row summary: The number of bytes per band per row. description: The number of bytes per band per row. This must be an integer. This keyword is used only with BIL files when there are extra bits at the end of each band within a row that must be skipped.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / totalrowbytes
Namespace No namespace
Annotations
tooltip: Total bytes of data per row

summary: The total number of bytes of data
                          per row.

description: The total number of bytes of data
                          per row. Use totalrowbytes when there are extra
                          trailing bits at the end of each
                          row.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="totalrowbytes" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Total bytes of data per row summary: The total number of bytes of data per row. description: The total number of bytes of data per row. Use totalrowbytes when there are extra trailing bits at the end of each row.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / dataFormat / binaryRasterFormat / bandgapbytes
Namespace No namespace
Annotations
tooltip: Bytes between bands

summary: The number of bytes between bands in
                          a BSQ format image.

description: The number of bytes between bands in
                          a BSQ format image. The default is
                          zero.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="bandgapbytes" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Bytes between bands summary: The number of bytes between bands in a BSQ format image. description: The number of bytes between bands in a BSQ format image. The default is zero.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element PhysicalType / distribution
Namespace No namespace
Annotations
tooltip: Distribution Information

summary: Information on how the resource is distributed
              online and offline

description: This element provides information on how the
              resource is distributed. Connections to online
              systems can be described as URLs or as a list of connection parameters.
               Please see the Type definition for complete information.
Diagram
Diagram NO_NAMESPACE.tmp#PhysicalDistributionType_id NO_NAMESPACE.tmp#PhysicalDistributionType_system NO_NAMESPACE.tmp#PhysicalDistributionType_scope NO_NAMESPACE.tmp#PhysicalDistributionType_online NO_NAMESPACE.tmp#PhysicalDistributionType_offline NO_NAMESPACE.tmp#PhysicalDistributionType_inline NO_NAMESPACE.tmp#PhysicalDistributionType_access NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup physical-2_2_0.tmp#PhysicalDistributionType
Type PhysicalDistributionType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children access, inline, offline, online, references
Instance
<distribution id="" scope="document" system="">
  <online>{1,1}</online>
  <offline>{1,1}</offline>
  <inline>{1,1}</inline>
  <access authSystem="" id="" order="allowFirst" scope="document" system="">{0,1}</access>
  <references system="">{1,1}</references>
</distribution>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="distribution" type="PhysicalDistributionType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Distribution Information summary: Information on how the resource is distributed online and offline description: This element provides information on how the resource is distributed. Connections to online systems can be described as URLs or as a list of connection parameters. Please see the Type definition for complete information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Element EntityGroup / coverage
Namespace No namespace
Annotations
tooltip: coverage descriptors

summary: Information on the geographic, spatial and temporal
            coverages used in this entity.

description: Information on the geographic, spatial and temporal
            coverages used in this entity.  Please see the eml-coverage module
            for more information.
Diagram
Diagram NO_NAMESPACE.tmp#Coverage_id NO_NAMESPACE.tmp#Coverage_system NO_NAMESPACE.tmp#Coverage_scope NO_NAMESPACE.tmp#Coverage_geographicCoverage NO_NAMESPACE.tmp#Coverage_temporalCoverage NO_NAMESPACE.tmp#Coverage_taxonomicCoverage NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#Coverage
Type Coverage
Properties
content complex
minOccurs 0
Model
Children geographicCoverage, references, taxonomicCoverage, temporalCoverage
Instance
<coverage id="" scope="document" system="">
  <geographicCoverage id="" scope="document" system="">{1,1}</geographicCoverage>
  <temporalCoverage id="" scope="document" system="">{1,1}</temporalCoverage>
  <taxonomicCoverage id="" scope="document" system="">{1,1}</taxonomicCoverage>
  <references system="">{1,1}</references>
</coverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="coverage" type="cov:Coverage" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: coverage descriptors summary: Information on the geographic, spatial and temporal coverages used in this entity. description: Information on the geographic, spatial and temporal coverages used in this entity. Please see the eml-coverage module for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element EntityGroup / methods
Namespace No namespace
Annotations
tooltip: method descriptions

summary: 

description: Information on the specific methods used to collect
            information in this entity.  Please see the eml-methods module for
            more information.
Diagram
Diagram NO_NAMESPACE.tmp#MethodsType_methodStep NO_NAMESPACE.tmp#MethodsType_sampling NO_NAMESPACE.tmp#MethodsType_qualityControl methods-2_2_0.tmp#MethodsType
Type MethodsType
Properties
content complex
minOccurs 0
Model
Children methodStep, qualityControl, sampling
Instance
<methods>
  <methodStep>{1,unbounded}</methodStep>
  <sampling>{0,1}</sampling>
  <qualityControl>{0,unbounded}</qualityControl>
</methods>
Source
<xs:element name="methods" type="md:MethodsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: method descriptions summary: description: Information on the specific methods used to collect information in this entity. Please see the eml-methods module for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element MethodsType / sampling
Namespace No namespace
Annotations
tooltip: sampling methods

summary: Description of sampling procedures including the
            geographic, temporal and taxonomic coverage of the
            study.

description: Description of sampling procedures including the
            geographic, temporal and taxonomic coverage of the
            study.  See individual elements for more detailed
            descriptions.
Diagram
Diagram NO_NAMESPACE.tmp#MethodsType_MethodsType_sampling_studyExtent NO_NAMESPACE.tmp#MethodsType_MethodsType_sampling_samplingDescription NO_NAMESPACE.tmp#MethodsType_MethodsType_sampling_spatialSamplingUnits NO_NAMESPACE.tmp#MethodsType_MethodsType_sampling_citation
Properties
content complex
minOccurs 0
Model
Children citation, samplingDescription, spatialSamplingUnits, studyExtent
Instance
<sampling>
  <studyExtent>{1,1}</studyExtent>
  <samplingDescription xml:lang="">{1,1}</samplingDescription>
  <spatialSamplingUnits>{0,1}</spatialSamplingUnits>
  <citation id="" scope="document" system="">{0,unbounded}</citation>
</sampling>
Source
<xs:element name="sampling" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: sampling methods summary: Description of sampling procedures including the geographic, temporal and taxonomic coverage of the study. description: Description of sampling procedures including the geographic, temporal and taxonomic coverage of the study. See individual elements for more detailed descriptions.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="studyExtent">
        <xs:annotation>
          <xs:documentation>tooltip: Geographic, temporal, taxonomic coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:choice maxOccurs="unbounded">
            <xs:element name="coverage" type="cov:Coverage">
              <xs:annotation>
                <xs:documentation>tooltip: coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element. See eml-coverage for more information.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="description" type="txt:TextType">
              <xs:annotation>
                <xs:documentation>tooltip: Text description of the coverage summary: A textual description of the specific areas sampled (geographic coverage), the sampling frequency (temporal coverage), and groups of living organisms sampled (taxonomic coverage). description: The coverage field allows for a textual description of the specific sampling area, the sampling frequency (temporal boundaries, frequency of occurrence), and groups of living organisms sampled (taxonomic coverage).</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:choice>
        </xs:complexType>
      </xs:element>
      <xs:element name="samplingDescription" type="txt:TextType">
        <xs:annotation>
          <xs:documentation>tooltip: Sampling methods and procedures summary: A description of sampling methods and procedures description: The samplingDescription field allows for a text-based/human readable description of the sampling procedures used in the research project. The content of this element would be similar to a description of sampling procedures found in the methods section of a journal article.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="spatialSamplingUnits" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Spatial sampling units summary: Spatial sampling units represent the plots sampled. description: A spatial sampling unit describes the specific geographic areas sampled. In the case of a study in which the measurements from several disbursed point collection devices are aggregated, then the sampling unit would be the area of that aggregation. Spatial sampling units can either be described by filling out the structured coverage element or by reference to the values in a data table (usually a GIS layer)</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:choice maxOccurs="unbounded">
            <xs:element name="referencedEntityId">
              <xs:annotation>
                <xs:documentation>tooltip: The identifier of a spatial sampling entity. summary: The identifier of an entity described in the entity module. This is usually a GIS layer. description: A value of a referencedEntityId element is a reference to the identifier of the entity module that provides the metadata for a data table (RDBMS, GIS or ascii text) that has the actual spatial sampling unit values. The referencedEntityId field is an indirect pointer to the actual values. The referencedEntityId can be thought of as a foreign key in a relational database.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="coverage" type="cov:GeographicCoverage">
              <xs:annotation>
                <xs:documentation>tooltip: sampling unit location summary: Structured description of each sampling unit location description: Structured description of each sampling unit location</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:choice>
        </xs:complexType>
      </xs:element>
      <xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: citation summary: Literature citation relating to the sampling procedures used. description: The citation field allows to either reference a literature resource or enter structured literature information</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / sampling / studyExtent
Namespace No namespace
Annotations
tooltip: Geographic, temporal, taxonomic
                  coverage

summary: A description of the geographic area sampled
                  (geographic coverage), the sampling frequency (temporal
                  coverage), and living organisms sampled (taxonomic
                  coverage.

description: The field studyExtent represents both a
                  specific sampling area and the sampling frequency (temporal
                  boundaries, frequency of occurrence). The geographic
                  studyExtent is usually a surrogate (representative area of)
                  for the larger area documented in the "studyAreaDescription".
                  The studyExtent can be entered either in non-structured
                  textual form or using the structure of the coverage
                  element.
Diagram
Diagram NO_NAMESPACE.tmp#MethodsType_MethodsType_sampling_MethodsType_MethodsType_sampling_studyExtent_coverage NO_NAMESPACE.tmp#MethodsType_MethodsType_sampling_MethodsType_MethodsType_sampling_studyExtent_description
Properties
content complex
Model
Children coverage, description
Instance
<studyExtent>
  <coverage id="" scope="document" system="">{1,1}</coverage>
  <description xml:lang="">{1,1}</description>
</studyExtent>
Source
<xs:element name="studyExtent">
  <xs:annotation>
    <xs:documentation>tooltip: Geographic, temporal, taxonomic coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice maxOccurs="unbounded">
      <xs:element name="coverage" type="cov:Coverage">
        <xs:annotation>
          <xs:documentation>tooltip: coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element. See eml-coverage for more information.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="description" type="txt:TextType">
        <xs:annotation>
          <xs:documentation>tooltip: Text description of the coverage summary: A textual description of the specific areas sampled (geographic coverage), the sampling frequency (temporal coverage), and groups of living organisms sampled (taxonomic coverage). description: The coverage field allows for a textual description of the specific sampling area, the sampling frequency (temporal boundaries, frequency of occurrence), and groups of living organisms sampled (taxonomic coverage).</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / sampling / studyExtent / coverage
Namespace No namespace
Annotations
tooltip: coverage

summary: A description of the geographic area sampled
                        (geographic coverage), the sampling frequency (temporal
                        coverage), and living organisms sampled (taxonomic
                        coverage.

description: The field studyExtent represents both a
                        specific sampling area and the sampling frequency (temporal
                        boundaries, frequency of occurrence). The geographic
                        studyExtent is usually a surrogate (representative area of)
                        for the larger area documented in the "studyAreaDescription".
                        The studyExtent can be entered either in non-structured
                        textual form or using the structure of the coverage
                        element.  See eml-coverage for more
                        information.
Diagram
Diagram NO_NAMESPACE.tmp#Coverage_id NO_NAMESPACE.tmp#Coverage_system NO_NAMESPACE.tmp#Coverage_scope NO_NAMESPACE.tmp#Coverage_geographicCoverage NO_NAMESPACE.tmp#Coverage_temporalCoverage NO_NAMESPACE.tmp#Coverage_taxonomicCoverage NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#Coverage
Type Coverage
Properties
content complex
Model
Children geographicCoverage, references, taxonomicCoverage, temporalCoverage
Instance
<coverage id="" scope="document" system="">
  <geographicCoverage id="" scope="document" system="">{1,1}</geographicCoverage>
  <temporalCoverage id="" scope="document" system="">{1,1}</temporalCoverage>
  <taxonomicCoverage id="" scope="document" system="">{1,1}</taxonomicCoverage>
  <references system="">{1,1}</references>
</coverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="coverage" type="cov:Coverage">
  <xs:annotation>
    <xs:documentation>tooltip: coverage summary: A description of the geographic area sampled (geographic coverage), the sampling frequency (temporal coverage), and living organisms sampled (taxonomic coverage. description: The field studyExtent represents both a specific sampling area and the sampling frequency (temporal boundaries, frequency of occurrence). The geographic studyExtent is usually a surrogate (representative area of) for the larger area documented in the "studyAreaDescription". The studyExtent can be entered either in non-structured textual form or using the structure of the coverage element. See eml-coverage for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / sampling / studyExtent / description
Namespace No namespace
Annotations
tooltip: Text description of the
                        coverage

summary: A textual description of the specific
                        areas sampled (geographic coverage), the sampling
                        frequency (temporal coverage), and groups of living
                        organisms sampled (taxonomic coverage).

description: The coverage field allows for a
                        textual description of the specific sampling area, the
                        sampling frequency (temporal boundaries, frequency of
                        occurrence), and groups of living organisms sampled
                        (taxonomic coverage).
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
mixed true
Model
Children markdown, para, section
Instance
<description xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</description>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="description" type="txt:TextType">
  <xs:annotation>
    <xs:documentation>tooltip: Text description of the coverage summary: A textual description of the specific areas sampled (geographic coverage), the sampling frequency (temporal coverage), and groups of living organisms sampled (taxonomic coverage). description: The coverage field allows for a textual description of the specific sampling area, the sampling frequency (temporal boundaries, frequency of occurrence), and groups of living organisms sampled (taxonomic coverage).</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / sampling / samplingDescription
Namespace No namespace
Annotations
tooltip: Sampling methods and procedures

summary: A description of sampling methods and
                  procedures

description: The samplingDescription field allows for a
                  text-based/human readable description of the sampling
                  procedures used in the research project. The content of this
                  element would be similar to a description of sampling
                  procedures found in the methods section of a journal
                  article.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
mixed true
Model
Children markdown, para, section
Instance
<samplingDescription xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</samplingDescription>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="samplingDescription" type="txt:TextType">
  <xs:annotation>
    <xs:documentation>tooltip: Sampling methods and procedures summary: A description of sampling methods and procedures description: The samplingDescription field allows for a text-based/human readable description of the sampling procedures used in the research project. The content of this element would be similar to a description of sampling procedures found in the methods section of a journal article.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / sampling / spatialSamplingUnits
Namespace No namespace
Annotations
tooltip: Spatial sampling units

summary: Spatial sampling units represent the plots
                  sampled.

description: A spatial sampling unit describes the
                  specific geographic areas sampled. In the case of a study in
                  which the measurements from several disbursed point
                  collection devices are aggregated, then the sampling unit
                  would be the area of that aggregation. Spatial sampling units
                  can either be described by filling out the structured
                  coverage element or by reference to the values in a data
                  table (usually a GIS layer)
Diagram
Diagram NO_NAMESPACE.tmp#MethodsType_MethodsType_sampling_MethodsType_MethodsType_sampling_spatialSamplingUnits_referencedEntityId NO_NAMESPACE.tmp#MethodsType_MethodsType_sampling_MethodsType_MethodsType_sampling_spatialSamplingUnits_coverage
Properties
content complex
minOccurs 0
Model
Children coverage, referencedEntityId
Instance
<spatialSamplingUnits>
  <referencedEntityId>{1,1}</referencedEntityId>
  <coverage id="" scope="document" system="">{1,1}</coverage>
</spatialSamplingUnits>
Source
<xs:element name="spatialSamplingUnits" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Spatial sampling units summary: Spatial sampling units represent the plots sampled. description: A spatial sampling unit describes the specific geographic areas sampled. In the case of a study in which the measurements from several disbursed point collection devices are aggregated, then the sampling unit would be the area of that aggregation. Spatial sampling units can either be described by filling out the structured coverage element or by reference to the values in a data table (usually a GIS layer)</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice maxOccurs="unbounded">
      <xs:element name="referencedEntityId">
        <xs:annotation>
          <xs:documentation>tooltip: The identifier of a spatial sampling entity. summary: The identifier of an entity described in the entity module. This is usually a GIS layer. description: A value of a referencedEntityId element is a reference to the identifier of the entity module that provides the metadata for a data table (RDBMS, GIS or ascii text) that has the actual spatial sampling unit values. The referencedEntityId field is an indirect pointer to the actual values. The referencedEntityId can be thought of as a foreign key in a relational database.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="coverage" type="cov:GeographicCoverage">
        <xs:annotation>
          <xs:documentation>tooltip: sampling unit location summary: Structured description of each sampling unit location description: Structured description of each sampling unit location</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / sampling / spatialSamplingUnits / referencedEntityId
Namespace No namespace
Annotations
tooltip: The identifier of a spatial sampling
                        entity.

summary: The identifier of an entity described in
                        the entity module. This is usually a GIS
                        layer.

description: A value of a referencedEntityId
                        element is a reference to the identifier of the entity
                        module that provides the metadata for a data table
                        (RDBMS, GIS or ascii text) that has the actual spatial
                        sampling unit values. The referencedEntityId field is
                        an indirect pointer to the actual values. The
                        referencedEntityId can be thought of as a foreign key
                        in a relational database.
Diagram
Diagram
Source
<xs:element name="referencedEntityId">
  <xs:annotation>
    <xs:documentation>tooltip: The identifier of a spatial sampling entity. summary: The identifier of an entity described in the entity module. This is usually a GIS layer. description: A value of a referencedEntityId element is a reference to the identifier of the entity module that provides the metadata for a data table (RDBMS, GIS or ascii text) that has the actual spatial sampling unit values. The referencedEntityId field is an indirect pointer to the actual values. The referencedEntityId can be thought of as a foreign key in a relational database.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / sampling / spatialSamplingUnits / coverage
Namespace No namespace
Annotations
tooltip: sampling unit location

summary: Structured description of each sampling unit
                      location

description: Structured description of each sampling
                      unit location
Diagram
Diagram NO_NAMESPACE.tmp#GeographicCoverage_id NO_NAMESPACE.tmp#GeographicCoverage_system NO_NAMESPACE.tmp#GeographicCoverage_scope NO_NAMESPACE.tmp#GeographicCoverage_geographicDescription NO_NAMESPACE.tmp#GeographicCoverage_boundingCoordinates NO_NAMESPACE.tmp#GeographicCoverage_datasetGPolygon NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#GeographicCoverage
Type GeographicCoverage
Properties
content complex
Model
Children boundingCoordinates, datasetGPolygon, geographicDescription, references
Instance
<coverage id="" scope="document" system="">
  <geographicDescription>{1,1}</geographicDescription>
  <boundingCoordinates>{1,1}</boundingCoordinates>
  <datasetGPolygon>{0,unbounded}</datasetGPolygon>
  <references system="">{1,1}</references>
</coverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="coverage" type="cov:GeographicCoverage">
  <xs:annotation>
    <xs:documentation>tooltip: sampling unit location summary: Structured description of each sampling unit location description: Structured description of each sampling unit location</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / sampling / citation
Namespace No namespace
Annotations
tooltip: citation

summary: Literature citation relating to the sampling
               procedures used.

description: The citation field allows to either reference
               a literature resource or enter structured literature
               information
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<citation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</citation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="citation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: citation summary: Literature citation relating to the sampling procedures used. description: The citation field allows to either reference a literature resource or enter structured literature information</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element MethodsType / qualityControl
Namespace No namespace
Annotations
tooltip: Quality Control

summary: Information on possible errors or on the quality of a
            data set.

description: The qualityControl field provides a location for
            the description of actions taken to either control or assess the
            quality of data resulting from the associated method step. A
            quality control description should identify a quality goal and
            describe prescriptive steps taken to ensure that the data meet
            those standards and/or postscriptive steps taken to assess the
            extent to which they are met. A quality control statement is
            associated with the methodStep that could have affected the
            targeted quality goal.
Diagram
Diagram NO_NAMESPACE.tmp#ProcedureStepType_description NO_NAMESPACE.tmp#ProcedureStepType_citation NO_NAMESPACE.tmp#ProcedureStepType_protocol NO_NAMESPACE.tmp#ProcedureStepType_instrumentation NO_NAMESPACE.tmp#ProcedureStepType_software NO_NAMESPACE.tmp#ProcedureStepType_subStep methods-2_2_0.tmp#ProcedureStepType
Type ProcedureStepType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children citation, description, instrumentation, protocol, software, subStep
Instance
<qualityControl>
  <description xml:lang="">{1,1}</description>
  <citation id="" scope="document" system="">{1,1}</citation>
  <protocol id="" scope="document" system="">{1,1}</protocol>
  <instrumentation>{0,unbounded}</instrumentation>
  <software id="" scope="document" system="">{0,unbounded}</software>
  <subStep>{0,unbounded}</subStep>
</qualityControl>
Source
<xs:element name="qualityControl" type="ProcedureStepType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Quality Control summary: Information on possible errors or on the quality of a data set. description: The qualityControl field provides a location for the description of actions taken to either control or assess the quality of data resulting from the associated method step. A quality control description should identify a quality goal and describe prescriptive steps taken to ensure that the data meet those standards and/or postscriptive steps taken to assess the extent to which they are met. A quality control statement is associated with the methodStep that could have affected the targeted quality goal.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-methods.xsd
Element EntityGroup / additionalInfo
Namespace No namespace
Annotations
tooltip: Additional Information

summary: Any extra information pertitent to the
            entity.

description: This field provides any information that is not
            characterized by the other entity metadata
            fields.
Diagram
Diagram namespace.tmp#lang NO_NAMESPACE.tmp#TextType_section NO_NAMESPACE.tmp#TextType_para NO_NAMESPACE.tmp#TextType_markdown text-2_2_0.tmp#TextType
Type TextType
Properties
content complex
minOccurs 0
maxOccurs unbounded
mixed true
Model
Children markdown, para, section
Instance
<additionalInfo xml:lang="">
  <section xml:lang="">{0,unbounded}</section>
  <para xml:lang="">{0,unbounded}</para>
  <markdown>{0,unbounded}</markdown>
</additionalInfo>
Attributes
QName Type Use
xml:lang optional
Source
<xs:element name="additionalInfo" type="txt:TextType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Additional Information summary: Any extra information pertitent to the entity. description: This field provides any information that is not characterized by the other entity metadata fields.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element EntityGroup / annotation
Namespace No namespace
Annotations
tooltip: Semantic Annotation

summary: A precisely-defined semantic statement about this entity.
            

description: An annotation represents a precisely-defined semantic
                  statement that applies to this entity.  This semantic statement
                  is used to associate precise measurement semantics with the
                  entity.  Each annotation consists of a propertyURI and valueURI,
                  which define a property and a value that apply to the entity.
                  The associated labels can be used to display the property and
                  value to users.  Each URI is resolvable to a
                  controlled vocabulary that provides a definition, relationships
                  to other terms, and multiple labels for displaying the statement.
Diagram
Diagram NO_NAMESPACE.tmp#SemanticAnnotation_propertyURI NO_NAMESPACE.tmp#SemanticAnnotation_valueURI semantics-2_2_0.tmp#SemanticAnnotation
Type SemanticAnnotation
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children propertyURI, valueURI
Instance
<annotation>
  <propertyURI label="">{1,1}</propertyURI>
  <valueURI label="">{1,1}</valueURI>
</annotation>
Source
<xs:element name="annotation" type="sem:SemanticAnnotation" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about this entity. description: An annotation represents a precisely-defined semantic statement that applies to this entity. This semantic statement is used to associate precise measurement semantics with the entity. Each annotation consists of a propertyURI and valueURI, which define a property and a value that apply to the entity. The associated labels can be used to display the property and value to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element DataTableType / attributeList
Namespace No namespace
Annotations
tooltip: Attribute List

summary: The list of attributes associated with this
              entity.

description: The list of attributes associated with this
              entity.  For more information see the eml-attribute
              module.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeListType_id NO_NAMESPACE.tmp#AttributeListType_attribute NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#AttributeListType
Type AttributeListType
Properties
content complex
Model
Children attribute, references
Instance
<attributeList id="">
  <attribute id="" scope="document" system="">{1,unbounded}</attribute>
  <references system="">{1,1}</references>
</attributeList>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="attributeList" type="att:AttributeListType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataTable.xsd
Element AttributeListType / attribute
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#AttributeType_id NO_NAMESPACE.tmp#AttributeType_system NO_NAMESPACE.tmp#AttributeType_scope NO_NAMESPACE.tmp#AttributeType_attributeName NO_NAMESPACE.tmp#AttributeType_attributeLabel NO_NAMESPACE.tmp#AttributeType_attributeDefinition NO_NAMESPACE.tmp#AttributeType_storageType NO_NAMESPACE.tmp#AttributeType_measurementScale NO_NAMESPACE.tmp#AttributeType_missingValueCode NO_NAMESPACE.tmp#AttributeType_accuracy NO_NAMESPACE.tmp#AttributeType_coverage NO_NAMESPACE.tmp#AttributeType_methods NO_NAMESPACE.tmp#AttributeType_annotation NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#AttributeType
Type AttributeType
Properties
content complex
maxOccurs unbounded
Model
Children accuracy, annotation, attributeDefinition, attributeLabel, attributeName, coverage, measurementScale, methods, missingValueCode, references, storageType
Instance
<attribute id="" scope="document" system="">
  <attributeName>{1,1}</attributeName>
  <attributeLabel>{0,unbounded}</attributeLabel>
  <attributeDefinition>{1,1}</attributeDefinition>
  <storageType typeSystem="http://www.w3.org/2001/XMLSchema-datatypes">{0,unbounded}</storageType>
  <measurementScale>{1,1}</measurementScale>
  <missingValueCode>{0,unbounded}</missingValueCode>
  <accuracy>{0,1}</accuracy>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <methods>{0,1}</methods>
  <annotation>{0,unbounded}</annotation>
  <references system="">{1,1}</references>
</attribute>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="attribute" type="AttributeType" maxOccurs="unbounded"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / attributeName
Namespace No namespace
Annotations
tooltip: Attribute name

summary: The name of the attribute
              

description: Attribute name is official name of the
              attribute.  This is usually a short, sometimes cryptic name
              that is used to refer to the attribute.  Many systems have
              restrictions on the length of attribute names, and on the
              use of special characters like spaces in the name, so the
              attribute name is often not particularly useful for display
              (use attributeLabel for display).  The attributeName is
              usually the name of the variable that is found in the header
              of a data file.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeName" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute name summary: The name of the attribute description: Attribute name is official name of the attribute. This is usually a short, sometimes cryptic name that is used to refer to the attribute. Many systems have restrictions on the length of attribute names, and on the use of special characters like spaces in the name, so the attribute name is often not particularly useful for display (use attributeLabel for display). The attributeName is usually the name of the variable that is found in the header of a data file.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / attributeLabel
Namespace No namespace
Annotations
tooltip: Attribute label

summary: A label for displaying an attribute name.
              

description: A descriptive label that can be used to display
              the name of an attribute.  This is often a longer, possibly
              multiple word name for the attribute than the attributeName. It
              is not constrained by system limitations on length or special
              characters.  For example, an attribute with a name of 'spcode'
              might have an attributeLabel of 'Species Code'.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeLabel" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute label summary: A label for displaying an attribute name. description: A descriptive label that can be used to display the name of an attribute. This is often a longer, possibly multiple word name for the attribute than the attributeName. It is not constrained by system limitations on length or special characters. For example, an attribute with a name of 'spcode' might have an attributeLabel of 'Species Code'.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / attributeDefinition
Namespace No namespace
Annotations
tooltip: Attribute definition

summary: Precise definition of the attribute
              

description: This element gives a precise definition of
              attribute in the data entity (dataTable, spatialRaster,
              spatialVector, storedProcedure, view or otherEntity) being
              documented. It explains the contents of the attribute fully so
              that a data user could interpret the attribute accurately.
              Some additional information may also be found in the
              methods element as well.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeDefinition" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute definition summary: Precise definition of the attribute description: This element gives a precise definition of attribute in the data entity (dataTable, spatialRaster, spatialVector, storedProcedure, view or otherEntity) being documented. It explains the contents of the attribute fully so that a data user could interpret the attribute accurately. Some additional information may also be found in the methods element as well.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / storageType
Namespace No namespace
Annotations
tooltip: Storage Type

summary: Storage type hint for this field

description: This element describes the storage type,
              for data in a RDBMS (or other data management system) field.
              As many systems do not
              provide for fine-grained restrictions on types, this type will
              often be a superset of the allowed domain defined in
              attributeDomain. Values for this field are by default drawn from
              the XML Schema Datatypes standard values, such as: integer,
              double, string, etc. If the XML Schema Datatypes are not used,
              the type system from which the values are derived should be
              listed in the 'typeSystem' attribute described below. This field
              represents a 'hint' to processing systems as to how the attribute
              might be represented in a system or language, but is distinct
              from the actual expression of the domain of the attribute. The
              field is repeatable so that the storageType can be indicated for
              multiple type systems (e.g., Oracle data types and Java data
              types).
Diagram
Diagram NO_NAMESPACE.tmp#AttributeType_AttributeType_storageType_typeSystem
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Default Use Annotation
typeSystem xs:string http://www.w3.org/2001/XMLSchema-datatypes optional
tooltip: Storage Type System

summary: The system used to define the storage types.
                      This should be an identifier of a well known and
                      published typing system.

description: The typeSystem attribute is the system
                      used to define the storage types. This should be an
                      identifier of a well known and published typing system.
                      The default and recommended system is the XML Schema data
                      type system. For details go to http://www.w3.org. If
                      another system is used (such as Java or C++ types),
                      typeSystem should be changed to match the
                      system.
Source
<xs:element name="storageType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Storage Type summary: Storage type hint for this field description: This element describes the storage type, for data in a RDBMS (or other data management system) field. As many systems do not provide for fine-grained restrictions on types, this type will often be a superset of the allowed domain defined in attributeDomain. Values for this field are by default drawn from the XML Schema Datatypes standard values, such as: integer, double, string, etc. If the XML Schema Datatypes are not used, the type system from which the values are derived should be listed in the 'typeSystem' attribute described below. This field represents a 'hint' to processing systems as to how the attribute might be represented in a system or language, but is distinct from the actual expression of the domain of the attribute. The field is repeatable so that the storageType can be indicated for multiple type systems (e.g., Oracle data types and Java data types).</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="typeSystem" type="xs:string" use="optional" default="http://www.w3.org/2001/XMLSchema-datatypes">
          <xs:annotation>
            <xs:documentation>tooltip: Storage Type System summary: The system used to define the storage types. This should be an identifier of a well known and published typing system. description: The typeSystem attribute is the system used to define the storage types. This should be an identifier of a well known and published typing system. The default and recommended system is the XML Schema data type system. For details go to http://www.w3.org. If another system is used (such as Java or C++ types), typeSystem should be changed to match the system.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale
Namespace No namespace
Annotations
tooltip: Measurement Scale

summary: The measurement scale for the attribute.
              

description: The measurementScale element indicates the
              type of scale from which values are drawn for the
              attribute. This provides information about the scale in
              which the data was collected.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_nominal NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_ordinal NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_interval NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_ratio NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_dateTime
Properties
content complex
Model
Children dateTime, interval, nominal, ordinal, ratio
Instance
<measurementScale>
  <nominal>{1,1}</nominal>
  <ordinal>{1,1}</ordinal>
  <interval>{1,1}</interval>
  <ratio>{1,1}</ratio>
  <dateTime>{1,1}</dateTime>
</measurementScale>
Source
<xs:element name="measurementScale">
  <xs:annotation>
    <xs:documentation>tooltip: Measurement Scale summary: The measurement scale for the attribute. description: The measurementScale element indicates the type of scale from which values are drawn for the attribute. This provides information about the scale in which the data was collected.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="nominal">
        <xs:annotation>
          <xs:documentation>tooltip: Nominal scale summary: Characteristics used to define nominal (categorical) scale attributes description: This field is used for defining the characteristics of this variable if it is a nominal scale variable, which are variables that are categorical in nature. Nominal is used when numbers have only been assigned to a variable for the purpose of categorizing the variable. An example of a nominal scale is assigning the number 1 for male and 2 for female.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="ordinal">
        <xs:annotation>
          <xs:documentation>tooltip: Ordinal scale summary: Characteristics used to define ordinal (ordered) scale attributes description: This field is used for defining the characteristics of this variable if it is an ordinal scale variable, which specify ordered values without specifying the magnitude of the difference between values. Ordinal is used when the categories have a logical or ordered relationship to each other. These types of scale allow one to distinguish the order of values, but not the magnitude of the difference between values. An example of an ordinal scale is a categorical survey where you rank a variable 1=good, 2=fair, 3=poor.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="interval">
        <xs:annotation>
          <xs:documentation>tooltip: Interval scale summary: Characteristics used to define interval scale attributes description: This field is used for defining the characteristics of this variable if it is an interval scale variable, which specifies both the order and magnitude of values, but has no natural zero point. Interval is used for data which consist of equidistant points on a scale. The Celsius scale is an interval scale, since each degree is equal but there is no natural zero point (so, 20 C is not twice as hot as 10 C). zero point (so, 20 C is not twice as hot as 10 C).</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="unit" type="UnitType"/>
            <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
            <xs:element name="numericDomain" type="NumericDomainType"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="ratio">
        <xs:annotation>
          <xs:documentation>tooltip: Ratio scale summary: Characteristics used to define ratio scale attributes description: This field is used for defining the characteristics of this variable if it is a ratio scale variable, which specifies the order and magnitude of values and has a natural zero point, allowing for ratio comparisons to be valid. Ratio is used for data which consists not only of equidistant points but also has a meaningful zero point, which allows ratios to have meaning. An example of a ratio scale would be the Kelvin temperature scale (200K is half as hot as 400K), and length in meters (e.g., 10 meters is twice as long as 5 meters).</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="unit" type="UnitType"/>
            <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
            <xs:element name="numericDomain" type="NumericDomainType"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="dateTime">
        <xs:annotation>
          <xs:documentation>tooltip: Date/Time scale summary: Characteristics used to define date and time attributes description: The dateTime field is used for defining the characteristics of the attribute if it contains date and time values. DateTime is used when the values fall on the Gregorian calendar system. DateTime values are special because they have properties of interval values (most of the time it is legitimate to treat them as interval values by converting them to a duration from a fixed point) but they sometimes only behave as ordinals (because the calendar is not predetermined, for some dateTime values one can only find out the order of the points and not the magnitude of the duration between those points). Thus, the dateTime scale provides the information necessary to properly understand and parse date and time values without improperly labeling them under one of the more traditional scales. Date and time values are unlike any other measured values. Note that the dateTime field would not be used if one is recording time durations. In that case, one should use a standard unit such as seconds, nominalMinute or nominalDay, or a customUnit that defines the unit in terms of its relationship to SI second.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="formatString" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Date/Time Format summary: A format string that describes the format for a date-time value from the Gregorian calendar. description: A format string that describes the format for a dateTime value from the Gregorian calendar. DateTime values should be expressed in a format that conforms to the ISO 8601 standard. This field allows one to specify the format string that should be used to decode the date or time value. To describe the format of an attribute containing dateTime values, construct a string representation of the format using the following symbols: Y year M month W month abbreviation (e.g., JAN) D day h hour m minute s second T time designator (demarcates date and time parts of date-time) Z UTC designator, indicating value is in UTC time . indicates a decimal fraction of a unit +/- indicates a positive or negative number, or a positive or negative time zone adjustment relative to UTC - indicates a separator between date components A/P am or pm designator Any other character in the format string is interpreted as a separator character. Here are some examples of the format strings that can be constructed. Format string Example value ------------------- ------------------ ISO Date YYYY-MM-DD 2002-10-14 ISO Datetime YYYY-MM-DDThh:mm:ss 2002-10-14T09:13:45 ISO Time hh:mm:ss 17:13:45 ISO Time hh:mm:ss.sss 09:13:45.432 ISO Time hh:mm.mm 09:13.42 Non-standard DD/MM/YYYY 14/10/2002 Non-standard MM/DD/YYYY 10/14/2002 Non-standard MM/DD/YY 10/14/02 Non-standard YYYY-MMM-DD 2002-OCT-14 Non-standard YYYYMMMDD 2002OCT14 Non-standard YYYY-MM-DD hh:mm:ss 2002-10-14 09:13:45 Some notes about these examples. First, the ISO 8601 standard is strict about the date components, their order, and the separators; e.g., date parts are upper case, and time parts are lower case. If no UTC relation information is given, the time is assumed to be in local time. Assuming local time is ambiguous even when communicating within a single time zone, given variations in Daylight Saving Time. Best practice is to follow the ISO 8601 format precisely and accurately. In particular, please note that these are all non-standard according to ISO: use of a slash (/) to separate date components, a space to separate date and time components, using a twelve-hour time with am/pm designator, placing any of the components out of descending order However, we recognize that existing data contain non-standard dates, and existing equipment (e.g., sensors) may still be producing non-standard dates. Further, data parsers often apply individual interpretations. E.g., Java interprets HH on a 24-hr clock and hh on a 12-hr clock, and MM as a padded integer for month but MMM as a 3-letter abbreviation. Consequently, the formatting string can contain characters as needed to accommodate existing data. Decimal dateTime values can be extended by indicating in the format that additional decimals can be used. Only the final unit (e.g., seconds in a time value) can use the extended digits according to the ISO 8601 standard. For example, to show indicate that seconds are represented to the nearest 1/1000 of a second, the format string would be "hh:mm:ss.sss". Note that this only indicates the number of decimals used to record the value, and not the precision of the measurement (see dateTimePrecision for that). Date and time values are from an interval scale, but it is extremely complex because of the vagaries of the calendar (e.g., leap years, and leap seconds). The duration between date and time values in the future is not even deterministic because leap seconds are based on current measurements of the earth's orbit. Consequently, date and time values are unlike any other measured values. The format string for dateTime values allows one to accurately calculate the duration in SI second units between two measured dateTime values, assuming that the conversion software has a detailed knowledge of the Gregorian calendar.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="dateTimePrecision" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: DateTime Precision summary: An indication of the precision of a date or time value description: A quantitative indication of the precision of a date or time measurement. The precision should be interpreted in the smallest units represented by the dateTime format. For example, if a dateTime value has a format of "hh:mm:ss.sss", then "seconds" are the smallest unit and the precision should be expressed in seconds. Thus, a precision value of "0.01" would mean that measurements were precise to the nearest hundredth of a second, even though the format string might indicate that values were written down with 3 decimal places.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="dateTimeDomain" type="DateTimeDomainType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: DateTime Domain summary: See the summary for the type: DateTimeDomainType description: See the description for the type: DateTimeDomainType</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / nominal
Namespace No namespace
Annotations
tooltip: Nominal scale

summary: Characteristics used to define nominal
                    (categorical) scale attributes

description: This field is used for defining the
                    characteristics of this variable if it is a
                    nominal scale variable, which are variables that are
                    categorical in nature.
                    Nominal is used when numbers have only been
                    assigned to a variable for the purpose of categorizing the
                    variable.  An example of a nominal scale is assigning the
                    number 1 for male and 2 for female.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_nominal_nonNumericDomain
Properties
content complex
Model
Children nonNumericDomain
Instance
<nominal>
  <nonNumericDomain id="">{1,1}</nonNumericDomain>
</nominal>
Source
<xs:element name="nominal">
  <xs:annotation>
    <xs:documentation>tooltip: Nominal scale summary: Characteristics used to define nominal (categorical) scale attributes description: This field is used for defining the characteristics of this variable if it is a nominal scale variable, which are variables that are categorical in nature. Nominal is used when numbers have only been assigned to a variable for the purpose of categorizing the variable. An example of a nominal scale is assigning the number 1 for male and 2 for female.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / nominal / nonNumericDomain
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#NonNumericDomainType_id NO_NAMESPACE.tmp#NonNumericDomainType_enumeratedDomain NO_NAMESPACE.tmp#NonNumericDomainType_textDomain NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#NonNumericDomainType
Type NonNumericDomainType
Properties
content complex
Model
Children enumeratedDomain, references, textDomain
Instance
<nonNumericDomain id="">
  <enumeratedDomain enforced="yes">{1,1}</enumeratedDomain>
  <textDomain>{1,1}</textDomain>
  <references system="">{1,1}</references>
</nonNumericDomain>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain
Namespace No namespace
Annotations
tooltip: Enumerated domain

summary: Description of any coded values associated
              with the attribute.

description: The enumeratedDomain element describes
              any code that is used as a value of an attribute. These
              codes can be defined here in the metadata as a list with
              definitions (preferred), can be referenced by pointing to
              an external citation or URL where the codes are defined,
              or can be referenced by pointing at an entity that contains
              the code value and code definition as two attributes. For
              example, data might have a variable named 'site' with
              values 'A', 'B', and 'C', and the enumeratedDomain would
              explain how to interpret those codes.
Diagram
Diagram NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_enforced NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_codeDefinition NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_externalCodeSet NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_entityCodeList
Properties
content complex
Model
Children codeDefinition, entityCodeList, externalCodeSet
Instance
<enumeratedDomain enforced="yes">
  <codeDefinition order="">{1,unbounded}</codeDefinition>
  <externalCodeSet>{1,1}</externalCodeSet>
  <entityCodeList>{1,1}</entityCodeList>
</enumeratedDomain>
Attributes
QName Type Default Use Annotation
enforced restriction of xs:string yes optional
tooltip: Enforced Domain

summary: Indicates whether the enumerated
                  domain values enforced.

description: Indicates whether the enumerated
                  domain values are the only allowable values for
                  the domain.  In some exceedingly rare cases, users may
                  wish to present a list of value codes in
                  enumeratedDomain but not formally restrict the value
                  space for the attribute to those values.  If so, they
                  can indicate this by setting the enforced attribute
                  to the value no.  Acceptable values are yes and no, and
                  the default value is yes.
Source
<xs:element name="enumeratedDomain">
  <xs:annotation>
    <xs:documentation>tooltip: Enumerated domain summary: Description of any coded values associated with the attribute. description: The enumeratedDomain element describes any code that is used as a value of an attribute. These codes can be defined here in the metadata as a list with definitions (preferred), can be referenced by pointing to an external citation or URL where the codes are defined, or can be referenced by pointing at an entity that contains the code value and code definition as two attributes. For example, data might have a variable named 'site' with values 'A', 'B', and 'C', and the enumeratedDomain would explain how to interpret those codes.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="codeDefinition" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Code Definition summary: A codes and its definition description: This element gives the value of a particular code and its definition. It is repeatable to allow for a list of codes to be provided.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="code" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Code summary: Code value allowed in the domain description: The code element specifies a code value that can be used in the domain</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="definition" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Code definition summary: Definition of the associated code description: The definition describes the code with which it is associated in enough detail for scientists to interpret the meaning of the coded values.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Source of code summary: The name of the source for this code and its definition description: The source element is the name of the source from which this code and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be the researcher's customized way of recording and classifying their data, and no external "source" would exist.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="order" type="xs:long" use="optional">
            <xs:annotation>
              <xs:documentation>tooltip: Order summary: Mechanism for specifying what the order of the code-definitions included should be description: Ordinal scale measurements have a discrete list of values with a specific ordering of those values. This attributes specifies that order from low to high. For example, for LOW, MEDIUM, HIGH, the order attribute might be "LOW=1, MEDIUM=2 and HIGH=3".</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
      <xs:element name="externalCodeSet">
        <xs:annotation>
          <xs:documentation>tooltip: External code set summary: A reference to an externally defined set of codes used in this attribute description: The externalCodeSet element is a reference to an externally defined set of codes used in this attribute. This can either be a citation (using the eml-citation module) or a URL. Using an externally defined codeset (rather than a codeDefinition) means that interpretation of the data is dependent upon future users being able to obtain the code definitions, so care should be taken to only use highly standardized external code sets that will be available for many years. If at all possible, it is preferable to define the codes inline using the codeDefinition element.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="codesetName" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Code Set Name summary: The name of an externally defined code set description: The codesetName element is the name of an externally defined code set.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:choice maxOccurs="unbounded">
              <xs:element name="citation" type="cit:CitationType">
                <xs:annotation>
                  <xs:documentation>tooltip: Citation summary: A citation for the code set reference description: The citation element is a citation for the code set reference</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="codesetURL" type="xs:anyURI">
                <xs:annotation>
                  <xs:documentation>tooltip: Code set URL summary: A URL for the code set reference description: The codesetURL element is a URL for the code set reference.</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:choice>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="entityCodeList">
        <xs:annotation>
          <xs:documentation>tooltip: Entity Code List summary: A code list that is defined in a data table description: The entityCodeList is a list of codes and their definitions in a data entity that is present in this dataset. The fields specify exactly which entity it is, and which attributes of that entity contain the codes, their definitions, and the order of the values.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="entityReference" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Entity Reference summary: A reference to the id of the entity in which the code list has been defined description: The entityReference element is a reference to the id of the entity in which the code list has been defined. This entity must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="valueAttributeReference" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Value Attribute Reference summary: A reference to the id of the attribute that contains the list of codes description: The valueAttributeReference element is a reference to the id of the attribute that contains the list of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="definitionAttributeReference" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Definition Attribute Reference summary: A reference to the id of the attribute that contains the definition of codes description: The definitionAttributeReference element is a reference to the id of the attribute that contains the definition of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="orderAttributeReference" type="res:NonEmptyStringType" minOccurs="0">
              <xs:annotation>
                <xs:documentation>tooltip: Order Attribute Reference summary: A reference to the id of the attribute that contains the order of codes description: The orderAttributeReference element is a reference to the id of the attribute that contains the order of codes. The values in this attribute are integers indicating increasing values of the categories. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:choice>
    <xs:attribute name="enforced" use="optional" default="yes">
      <xs:annotation>
        <xs:documentation>tooltip: Enforced Domain summary: Indicates whether the enumerated domain values enforced. description: Indicates whether the enumerated domain values are the only allowable values for the domain. In some exceedingly rare cases, users may wish to present a list of value codes in enumeratedDomain but not formally restrict the value space for the attribute to those values. If so, they can indicate this by setting the enforced attribute to the value no. Acceptable values are yes and no, and the default value is yes.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="yes"/>
          <xs:enumeration value="no"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / codeDefinition
Namespace No namespace
Annotations
tooltip: Code Definition

summary: A codes and its definition

description: This element gives the value of a
                    particular code and its definition.  It is repeatable
                    to allow for a list of codes to be provided.
Diagram
Diagram NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_codeDefinition_order NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_codeDefinition_code NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_codeDefinition_definition NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_codeDefinition_source
Properties
content complex
maxOccurs unbounded
Model
Children code, definition, source
Instance
<codeDefinition order="">
  <code>{1,1}</code>
  <definition>{1,1}</definition>
  <source>{0,1}</source>
</codeDefinition>
Attributes
QName Type Use Annotation
order xs:long optional
tooltip: Order

summary: Mechanism for specifying what the
			order of the code-definitions included should
			be

description: Ordinal scale measurements have a discrete list
			of values with a specific ordering of those values. This attributes
			specifies that order from low to high. For example, for LOW,
            MEDIUM, HIGH, the order attribute might be "LOW=1, MEDIUM=2 and
            HIGH=3".
Source
<xs:element name="codeDefinition" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Code Definition summary: A codes and its definition description: This element gives the value of a particular code and its definition. It is repeatable to allow for a list of codes to be provided.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="code" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Code summary: Code value allowed in the domain description: The code element specifies a code value that can be used in the domain</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="definition" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Code definition summary: Definition of the associated code description: The definition describes the code with which it is associated in enough detail for scientists to interpret the meaning of the coded values.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Source of code summary: The name of the source for this code and its definition description: The source element is the name of the source from which this code and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be the researcher's customized way of recording and classifying their data, and no external "source" would exist.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="order" type="xs:long" use="optional">
      <xs:annotation>
        <xs:documentation>tooltip: Order summary: Mechanism for specifying what the order of the code-definitions included should be description: Ordinal scale measurements have a discrete list of values with a specific ordering of those values. This attributes specifies that order from low to high. For example, for LOW, MEDIUM, HIGH, the order attribute might be "LOW=1, MEDIUM=2 and HIGH=3".</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / codeDefinition / code
Namespace No namespace
Annotations
tooltip: Code

summary: Code value allowed in the
                          domain

description: The code element specifies a
                          code value that can be used in the domain
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="code" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Code summary: Code value allowed in the domain description: The code element specifies a code value that can be used in the domain</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / codeDefinition / definition
Namespace No namespace
Annotations
tooltip: Code definition

summary: Definition of the associated code
                          

description: The definition describes the
                          code with which it is associated in enough
                          detail for scientists to interpret the meaning
                          of the coded values.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="definition" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Code definition summary: Definition of the associated code description: The definition describes the code with which it is associated in enough detail for scientists to interpret the meaning of the coded values.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / codeDefinition / source
Namespace No namespace
Annotations
tooltip: Source of code

summary: The name of the source for this
                          code and its definition

description: The source element is the name
                          of the source from which this code and its
                          associated definition are drawn. This is
                          commonly used for identifying standard coding
                          systems, like the FIPS standard for postal
                          abbreviations for states in the US. In other
                          cases, the coding may be the researcher's
                          customized way of recording and classifying
                          their data, and no external "source" would
                          exist.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Source of code summary: The name of the source for this code and its definition description: The source element is the name of the source from which this code and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be the researcher's customized way of recording and classifying their data, and no external "source" would exist.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / externalCodeSet
Namespace No namespace
Annotations
tooltip: External code set

summary: A reference to an externally defined set
                    of codes used in this attribute

description: The externalCodeSet element is a
                    reference to an externally defined set of codes used
                    in this attribute. This can either be a citation
                    (using the eml-citation module) or a
                    URL. Using an externally defined codeset (rather
                    than a codeDefinition) means that interpretation of the
                    data is dependent upon future users being able to
                    obtain the code definitions, so care should be taken
                    to only use highly standardized external code sets that
                    will be available for many years.  If at all possible,
                    it is preferable to define the codes inline using the
                    codeDefinition element.
Diagram
Diagram NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_externalCodeSet_codesetName NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_externalCodeSet_citation NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_externalCodeSet_codesetURL
Properties
content complex
Model
Children citation, codesetName, codesetURL
Instance
<externalCodeSet>
  <codesetName>{1,1}</codesetName>
  <citation id="" scope="document" system="">{1,1}</citation>
  <codesetURL>{1,1}</codesetURL>
</externalCodeSet>
Source
<xs:element name="externalCodeSet">
  <xs:annotation>
    <xs:documentation>tooltip: External code set summary: A reference to an externally defined set of codes used in this attribute description: The externalCodeSet element is a reference to an externally defined set of codes used in this attribute. This can either be a citation (using the eml-citation module) or a URL. Using an externally defined codeset (rather than a codeDefinition) means that interpretation of the data is dependent upon future users being able to obtain the code definitions, so care should be taken to only use highly standardized external code sets that will be available for many years. If at all possible, it is preferable to define the codes inline using the codeDefinition element.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="codesetName" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Code Set Name summary: The name of an externally defined code set description: The codesetName element is the name of an externally defined code set.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:choice maxOccurs="unbounded">
        <xs:element name="citation" type="cit:CitationType">
          <xs:annotation>
            <xs:documentation>tooltip: Citation summary: A citation for the code set reference description: The citation element is a citation for the code set reference</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="codesetURL" type="xs:anyURI">
          <xs:annotation>
            <xs:documentation>tooltip: Code set URL summary: A URL for the code set reference description: The codesetURL element is a URL for the code set reference.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:choice>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / externalCodeSet / codesetName
Namespace No namespace
Annotations
tooltip: Code Set Name

summary: The name of an externally defined
                          code set

description: The codesetName element is the
                          name of an externally defined code
                          set.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="codesetName" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Code Set Name summary: The name of an externally defined code set description: The codesetName element is the name of an externally defined code set.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / externalCodeSet / citation
Namespace No namespace
Annotations
tooltip: Citation

summary: A citation for the code set
                            reference

description: The citation element is a
                            citation for the code set
                            reference
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<citation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</citation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="citation" type="cit:CitationType">
  <xs:annotation>
    <xs:documentation>tooltip: Citation summary: A citation for the code set reference description: The citation element is a citation for the code set reference</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / externalCodeSet / codesetURL
Namespace No namespace
Annotations
tooltip: Code set URL

summary: A URL for the code set
                            reference

description: The codesetURL element is a
                            URL for the code set
                            reference.
Diagram
Diagram
Type xs:anyURI
Properties
content simple
Source
<xs:element name="codesetURL" type="xs:anyURI">
  <xs:annotation>
    <xs:documentation>tooltip: Code set URL summary: A URL for the code set reference description: The codesetURL element is a URL for the code set reference.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / entityCodeList
Namespace No namespace
Annotations
tooltip: Entity Code List

summary: A code list that is defined in a data
                    table

description: The entityCodeList is a list of
                    codes and their definitions in a data
                    entity that is present in this dataset. The fields
                    specify exactly which entity it is, and which
                    attributes of that entity contain the codes, their
                    definitions, and the order of the values.
Diagram
Diagram NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_entityCodeList_entityReference NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_entityCodeList_valueAttributeReference NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_entityCodeList_definitionAttributeReference NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_enumeratedDomain_NonNumericDomainType_NonNumericDomainType_enumeratedDomain_entityCodeList_orderAttributeReference
Properties
content complex
Model
Children definitionAttributeReference, entityReference, orderAttributeReference, valueAttributeReference
Instance
<entityCodeList>
  <entityReference>{1,1}</entityReference>
  <valueAttributeReference>{1,1}</valueAttributeReference>
  <definitionAttributeReference>{1,1}</definitionAttributeReference>
  <orderAttributeReference>{0,1}</orderAttributeReference>
</entityCodeList>
Source
<xs:element name="entityCodeList">
  <xs:annotation>
    <xs:documentation>tooltip: Entity Code List summary: A code list that is defined in a data table description: The entityCodeList is a list of codes and their definitions in a data entity that is present in this dataset. The fields specify exactly which entity it is, and which attributes of that entity contain the codes, their definitions, and the order of the values.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="entityReference" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Entity Reference summary: A reference to the id of the entity in which the code list has been defined description: The entityReference element is a reference to the id of the entity in which the code list has been defined. This entity must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="valueAttributeReference" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Value Attribute Reference summary: A reference to the id of the attribute that contains the list of codes description: The valueAttributeReference element is a reference to the id of the attribute that contains the list of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="definitionAttributeReference" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Definition Attribute Reference summary: A reference to the id of the attribute that contains the definition of codes description: The definitionAttributeReference element is a reference to the id of the attribute that contains the definition of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="orderAttributeReference" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Order Attribute Reference summary: A reference to the id of the attribute that contains the order of codes description: The orderAttributeReference element is a reference to the id of the attribute that contains the order of codes. The values in this attribute are integers indicating increasing values of the categories. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / entityCodeList / entityReference
Namespace No namespace
Annotations
tooltip: Entity Reference

summary: A reference to the id of the
                          entity in which the code list has been
                          defined

description: The entityReference element is
                          a reference to the id of the entity in which
                          the code list has been defined. This entity
                          must have been defined elsewhere in the
                          metadata and have an id that matches the value
                          of this element.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="entityReference" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Entity Reference summary: A reference to the id of the entity in which the code list has been defined description: The entityReference element is a reference to the id of the entity in which the code list has been defined. This entity must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / entityCodeList / valueAttributeReference
Namespace No namespace
Annotations
tooltip: Value Attribute
                          Reference

summary: A reference to the id of the
                          attribute that contains the list of
                          codes

description: The valueAttributeReference
                          element is a reference to the id of the
                          attribute that contains the list of codes. This
                          attribute must have been defined elsewhere in
                          the metadata and have an id that matches the
                          value of this element.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="valueAttributeReference" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Value Attribute Reference summary: A reference to the id of the attribute that contains the list of codes description: The valueAttributeReference element is a reference to the id of the attribute that contains the list of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / entityCodeList / definitionAttributeReference
Namespace No namespace
Annotations
tooltip: Definition Attribute
                          Reference

summary: A reference to the id of the
                          attribute that contains the definition of
                          codes

description: The
                          definitionAttributeReference element is a
                          reference to the id of the attribute that
                          contains the definition of codes. This
                          attribute must have been defined elsewhere in
                          the metadata and have an id that matches the
                          value of this element.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="definitionAttributeReference" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Definition Attribute Reference summary: A reference to the id of the attribute that contains the definition of codes description: The definitionAttributeReference element is a reference to the id of the attribute that contains the definition of codes. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / enumeratedDomain / entityCodeList / orderAttributeReference
Namespace No namespace
Annotations
tooltip: Order Attribute
                          Reference

summary: A reference to the id of the
                          attribute that contains the order of
                          codes

description: The orderAttributeReference element
                          is a reference to the id of the attribute that
                          contains the order of codes. The values in this
                          attribute are integers indicating increasing values
                          of the categories.  This attribute must have been
                          defined elsewhere in the metadata and have an id that
                          matches the value of this element.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="orderAttributeReference" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Order Attribute Reference summary: A reference to the id of the attribute that contains the order of codes description: The orderAttributeReference element is a reference to the id of the attribute that contains the order of codes. The values in this attribute are integers indicating increasing values of the categories. This attribute must have been defined elsewhere in the metadata and have an id that matches the value of this element.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / textDomain
Namespace No namespace
Annotations
tooltip: Text domain

summary: Description of a free-text domain pattern for
              the attribute

description: The textDomain element describes a free
              text domain for the attribute. By default, if a pattern is
              missing or empty, then any text is allowed. If a pattern is
              present, then it is interpreted as a regular expression
              constraining the allowable character sequences for the
              attribute. This domain type is most useful for describing
              extensive text domains that match a pattern but do not
              have a finite set of values.  Another use is for
              describing the domain of textual fields like comments
              that allow any legal string value.
Diagram
Diagram NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_textDomain_definition NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_textDomain_pattern NO_NAMESPACE.tmp#NonNumericDomainType_NonNumericDomainType_textDomain_source
Properties
content complex
Model
Children definition, pattern, source
Instance
<textDomain>
  <definition>{1,1}</definition>
  <pattern>{0,unbounded}</pattern>
  <source>{0,1}</source>
</textDomain>
Source
<xs:element name="textDomain">
  <xs:annotation>
    <xs:documentation>tooltip: Text domain summary: Description of a free-text domain pattern for the attribute description: The textDomain element describes a free text domain for the attribute. By default, if a pattern is missing or empty, then any text is allowed. If a pattern is present, then it is interpreted as a regular expression constraining the allowable character sequences for the attribute. This domain type is most useful for describing extensive text domains that match a pattern but do not have a finite set of values. Another use is for describing the domain of textual fields like comments that allow any legal string value.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="definition" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Text domain definition summary: Definition of what this text domain represents description: The element definition provides the text domain definition, that is, what kinds of text expressions are allowed for this attribute. If there is a pattern supplied, the definition element expresses the meaning of the pattern, For example, a particular pattern may be meant to represent phone numbers in the US phone system format. A definition element may also be used to extend an enumerated domain.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="pattern" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Text pattern summary: Regular expression pattern constraining the attribute description: The pattern element specifies a regular expression pattern that constrains the set of allowable values for the attribute. This is commonly used to define template patterns for data such as phone numbers where the attribute is text but the values are not drawn from an enumeration. If the pattern field is empty or missing, it defaults to '.*', which matches any string, including the empty string. Repeated pattern elements are combined using logical OR. The regular expression syntax is the same as that used in the XML Schema Datatypes Recommendation from the W3C.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Source of text domain summary: The name of the source for this text domain. description: The source element is the name of the source from which this text domain and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be a researcher's custom way of recording and classifying their data, and no external "source" would exist.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / textDomain / definition
Namespace No namespace
Annotations
tooltip: Text domain definition

summary: Definition of what this text domain
                    represents

description: The element definition provides the
                    text domain definition, that is, what kinds of text
                    expressions are allowed for this attribute. If there
                    is a pattern supplied, the definition element
                    expresses the meaning of the pattern, For example, a
                    particular pattern may be meant to represent phone
                    numbers in the US phone system format. A definition
                    element may also be used to extend an enumerated
                    domain.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="definition" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Text domain definition summary: Definition of what this text domain represents description: The element definition provides the text domain definition, that is, what kinds of text expressions are allowed for this attribute. If there is a pattern supplied, the definition element expresses the meaning of the pattern, For example, a particular pattern may be meant to represent phone numbers in the US phone system format. A definition element may also be used to extend an enumerated domain.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / textDomain / pattern
Namespace No namespace
Annotations
tooltip: Text pattern

summary: Regular expression pattern constraining
                    the attribute

description: The pattern element specifies a
                    regular expression pattern that constrains the set of
                    allowable values for the attribute. This is commonly
                    used to define template patterns for data such as
                    phone numbers where the attribute is text but the
                    values are not drawn from an enumeration. If the
                    pattern field is empty or missing, it defaults to
                    '.*', which matches any string, including the empty
                    string. Repeated pattern elements are combined using
                    logical OR. The regular expression syntax is the same
                    as that used in the XML Schema Datatypes
                    Recommendation from the W3C.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="pattern" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Text pattern summary: Regular expression pattern constraining the attribute description: The pattern element specifies a regular expression pattern that constrains the set of allowable values for the attribute. This is commonly used to define template patterns for data such as phone numbers where the attribute is text but the values are not drawn from an enumeration. If the pattern field is empty or missing, it defaults to '.*', which matches any string, including the empty string. Repeated pattern elements are combined using logical OR. The regular expression syntax is the same as that used in the XML Schema Datatypes Recommendation from the W3C.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NonNumericDomainType / textDomain / source
Namespace No namespace
Annotations
tooltip: Source of text domain

summary: The name of the source for this text
                    domain.

description: The source element is the name of
                    the source from which this text domain and its
                    associated definition are drawn. This is commonly
                    used for identifying standard coding systems, like
                    the FIPS standard for postal abbreviations for states
                    in the US. In other cases, the coding may be a
                    researcher's custom way of recording and classifying
                    their data, and no external "source" would
                    exist.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="source" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Source of text domain summary: The name of the source for this text domain. description: The source element is the name of the source from which this text domain and its associated definition are drawn. This is commonly used for identifying standard coding systems, like the FIPS standard for postal abbreviations for states in the US. In other cases, the coding may be a researcher's custom way of recording and classifying their data, and no external "source" would exist.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / ordinal
Namespace No namespace
Annotations
tooltip: Ordinal scale

summary: Characteristics used to define ordinal
                    (ordered) scale attributes

description: This field is used for defining the
                    characteristics of this variable if it is an
                    ordinal scale variable, which specify ordered values
                    without specifying the magnitude of the difference between
                    values. Ordinal is used when the categories have
                    a logical or ordered relationship to each other. These
                    types of scale allow one to distinguish the order
                    of values, but not the magnitude of the difference
                    between values. An example of an ordinal scale is a
                    categorical survey where you rank a variable 1=good,
                    2=fair, 3=poor.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_ordinal_nonNumericDomain
Properties
content complex
Model
Children nonNumericDomain
Instance
<ordinal>
  <nonNumericDomain id="">{1,1}</nonNumericDomain>
</ordinal>
Source
<xs:element name="ordinal">
  <xs:annotation>
    <xs:documentation>tooltip: Ordinal scale summary: Characteristics used to define ordinal (ordered) scale attributes description: This field is used for defining the characteristics of this variable if it is an ordinal scale variable, which specify ordered values without specifying the magnitude of the difference between values. Ordinal is used when the categories have a logical or ordered relationship to each other. These types of scale allow one to distinguish the order of values, but not the magnitude of the difference between values. An example of an ordinal scale is a categorical survey where you rank a variable 1=good, 2=fair, 3=poor.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / ordinal / nonNumericDomain
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#NonNumericDomainType_id NO_NAMESPACE.tmp#NonNumericDomainType_enumeratedDomain NO_NAMESPACE.tmp#NonNumericDomainType_textDomain NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#NonNumericDomainType
Type NonNumericDomainType
Properties
content complex
Model
Children enumeratedDomain, references, textDomain
Instance
<nonNumericDomain id="">
  <enumeratedDomain enforced="yes">{1,1}</enumeratedDomain>
  <textDomain>{1,1}</textDomain>
  <references system="">{1,1}</references>
</nonNumericDomain>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="nonNumericDomain" type="NonNumericDomainType"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / interval
Namespace No namespace
Annotations
tooltip: Interval scale

summary: Characteristics used to define interval
                    scale attributes

description: This field is used for defining the
                    characteristics of this variable if it is an
                    interval scale variable, which specifies both the order
                    and magnitude of values, but has no natural zero point.
                    Interval is used for data which consist of
                    equidistant points on a scale. The Celsius scale is an
                    interval scale, since each degree is equal but there is
                    no natural zero point (so, 20 C is not twice as hot as
                    10 C).  zero point (so, 20 C is not twice as hot as 10
                    C).
Diagram
Diagram NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_interval_unit NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_interval_precision NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_interval_numericDomain
Properties
content complex
Model
Children numericDomain, precision, unit
Instance
<interval>
  <unit>{1,1}</unit>
  <precision>{0,1}</precision>
  <numericDomain id="">{1,1}</numericDomain>
</interval>
Source
<xs:element name="interval">
  <xs:annotation>
    <xs:documentation>tooltip: Interval scale summary: Characteristics used to define interval scale attributes description: This field is used for defining the characteristics of this variable if it is an interval scale variable, which specifies both the order and magnitude of values, but has no natural zero point. Interval is used for data which consist of equidistant points on a scale. The Celsius scale is an interval scale, since each degree is equal but there is no natural zero point (so, 20 C is not twice as hot as 10 C). zero point (so, 20 C is not twice as hot as 10 C).</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="unit" type="UnitType"/>
      <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
      <xs:element name="numericDomain" type="NumericDomainType"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / interval / unit
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#UnitType_standardUnit NO_NAMESPACE.tmp#UnitType_customUnit attribute-2_2_0.tmp#UnitType
Type UnitType
Properties
content complex
Model
Children customUnit, standardUnit
Instance
<unit>
  <standardUnit>{1,1}</standardUnit>
  <customUnit>{1,1}</customUnit>
</unit>
Source
<xs:element name="unit" type="UnitType"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element UnitType / standardUnit
Namespace No namespace
Annotations
tooltip: Standard Unit

summary: The name of a standard unit used to make this
            measurement

description: Use the standardUnit element if the unit for this attribute has
            been defined in the Standard Unit Dictionary.
            The list of "standard" units includes the SI base units and many compound units based
            on SI, plus and some commonly used units which are not SI. The list is by no means
            exhaustive. If the unit you need is not part of this list, then the customUnit field should be used
            instead. Standard units have been described using STMML. See the documentation
            for the Type for more information.
Diagram
Diagram units-2_2_0.tmp#StandardUnitDictionary
Type unit:StandardUnitDictionary
Properties
content simple
Source
<xs:element name="standardUnit" type="unit:StandardUnitDictionary">
  <xs:annotation>
    <xs:documentation>tooltip: Standard Unit summary: The name of a standard unit used to make this measurement description: Use the standardUnit element if the unit for this attribute has been defined in the Standard Unit Dictionary. The list of "standard" units includes the SI base units and many compound units based on SI, plus and some commonly used units which are not SI. The list is by no means exhaustive. If the unit you need is not part of this list, then the customUnit field should be used instead. Standard units have been described using STMML. See the documentation for the Type for more information.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element UnitType / customUnit
Namespace No namespace
Annotations
tooltip: Custom Unit

summary: The name of a custom unit used to make this
            measurement.

description: The customUnit element is for units that are
             not part of the standard list provided with EML. The customUnit
             must correspond to an id in the
            document where its definition is provided using the STMML
            syntax. The customUnit definition will most likely be in
            the additionalMetadata section.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="customUnit" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Custom Unit summary: The name of a custom unit used to make this measurement. description: The customUnit element is for units that are not part of the standard list provided with EML. The customUnit must correspond to an id in the document where its definition is provided using the STMML syntax. The customUnit definition will most likely be in the additionalMetadata section.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / interval / precision
Namespace No namespace
Diagram
Diagram attribute-2_2_0.tmp#PrecisionType
Type PrecisionType
Properties
content complex
minOccurs 0
Source
<xs:element name="precision" type="PrecisionType" minOccurs="0"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / interval / numericDomain
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#NumericDomainType_id NO_NAMESPACE.tmp#NumericDomainType_numberType NO_NAMESPACE.tmp#BoundsGroup_bounds attribute-2_2_0.tmp#BoundsGroup NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#NumericDomainType
Type NumericDomainType
Properties
content complex
Model
Children bounds, numberType, references
Instance
<numericDomain id="">
  <numberType>{1,1}</numberType>
  <bounds>{0,unbounded}</bounds>
  <references system="">{1,1}</references>
</numericDomain>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="numericDomain" type="NumericDomainType"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element NumericDomainType / numberType
Namespace No namespace
Annotations
tooltip: number type
Diagram
Diagram attribute-2_2_0.tmp#NumberType
Type NumberType
Properties
content simple
Facets
enumeration natural
tooltip: Natural numbers

summary: Natural numbers
            

description: The number type for this attribute consists
            of the 'natural' numbers, otherwise known as the counting numbers:
            1, 2, 3, 4, ...
enumeration whole
tooltip: Whole numbers

summary: Whole numbers
            

description: The number type for this attribute consists
            of the 'whole' numbers, which are the natural numbers plus the
            zero value: 0, 1, 2, 3, 4, ...
enumeration integer
tooltip: Integer numbers

summary: Integer numbers
            

description: The number type for this attribute consists
            of the 'integer' numbers, which are the natural numbers, plus the
            zero value, plus the negatives of the natural numbers: ..., -4, -3,
            -2, -1, 0, 1, 2, 3, 4, ...
enumeration real
tooltip: Real numbers

summary: Real numbers
            

description: The number type for this attribute consists
            of the 'real' numbers, which contains both the rational numbers
            that can be expressed as fractions and the irrational numbers
            that can not be expressed as fractions (such as the square root of 2).
Source
<xs:element name="numberType" type="NumberType">
  <xs:annotation>
    <xs:documentation>tooltip: number type</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element BoundsGroup / bounds
Namespace No namespace
Annotations
tooltip: Bounds

summary: Elements for specifying allowed
        values range.

description: The bounds element in the BoundsGroup contains the
        minimum and maximum values of a numeric attribute. These
        are theoretical or permitted values (ie. prescriptive), and
        not necessarily the actual minimum and maximum observed in
        a given data set (descriptive). Either or both a minimum and maximum may
        be set, and each has an attribute "exclusive" to define how the value should
        be interpreted.
Diagram
Diagram NO_NAMESPACE.tmp#BoundsGroup_BoundsGroup_bounds_minimum NO_NAMESPACE.tmp#BoundsGroup_BoundsGroup_bounds_maximum
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children maximum, minimum
Instance
<bounds>
  <minimum exclusive="">{0,1}</minimum>
  <maximum exclusive="">{0,1}</maximum>
</bounds>
Source
<xs:element name="bounds" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Bounds summary: Elements for specifying allowed values range. description: The bounds element in the BoundsGroup contains the minimum and maximum values of a numeric attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive). Either or both a minimum and maximum may be set, and each has an attribute "exclusive" to define how the value should be interpreted.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="minimum" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Minimum numeric bound summary: Minimum numeric bound of attribute description: The minimum element specifies the minimum permitted value of a numeric attribute.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:float">
              <xs:attribute name="exclusive" type="xs:boolean" use="required">
                <xs:annotation>
                  <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
      <xs:element name="maximum" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Maximum numeric bound summary: Maximum numeric bound of attribute description: The maximum element specifies the maximum permitted value of a numeric attribute.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:float">
              <xs:attribute name="exclusive" type="xs:boolean" use="required">
                <xs:annotation>
                  <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element BoundsGroup / bounds / minimum
Namespace No namespace
Annotations
tooltip: Minimum numeric bound

summary: Minimum numeric bound of
                attribute

description: The minimum element specifies the
                minimum permitted value of a numeric
                attribute.
Diagram
Diagram NO_NAMESPACE.tmp#BoundsGroup_BoundsGroup_bounds_BoundsGroup_BoundsGroup_bounds_minimum_exclusive
Type extension of xs:float
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
exclusive xs:boolean required
tooltip: Exclusive
                        

summary: Exclusive bounds flag
                        

description: If exclusive is set to true, then
                        the value specifies a lower bound not including
                        the value itself.  Setting exclusive to true is
                        the equivalent of using a less-than or greater-than
                        operator, while setting it to false is the same as
                        using a less-than-or-equals or greater-than-or-equals
                        operator. For example, if the minimum is "5" and
                        exclusive is false, then all values must be greater
                        than or equal to 5, but if exclusive is true than
                        all values must be greater than 5 (not including
                        5.0 itself).
Source
<xs:element name="minimum" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Minimum numeric bound summary: Minimum numeric bound of attribute description: The minimum element specifies the minimum permitted value of a numeric attribute.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:float">
        <xs:attribute name="exclusive" type="xs:boolean" use="required">
          <xs:annotation>
            <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element BoundsGroup / bounds / maximum
Namespace No namespace
Annotations
tooltip: Maximum numeric bound

summary: Maximum numeric bound of
                attribute

description: The maximum element specifies the
                maximum permitted value of a numeric
                attribute.
Diagram
Diagram NO_NAMESPACE.tmp#BoundsGroup_BoundsGroup_bounds_BoundsGroup_BoundsGroup_bounds_maximum_exclusive
Type extension of xs:float
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
exclusive xs:boolean required
tooltip: Exclusive
                        

summary: Exclusive bounds flag
                        

description: If exclusive is set to true, then
                        the value specifies a lower bound not including
                        the value itself.  Setting exclusive to true is
                        the equivalent of using a less-than or greater-than
                        operator, while setting it to false is the same as
                        using a less-than-or-equals or greater-than-or-equals
                        operator. For example, if the minimum is "5" and
                        exclusive is false, then all values must be greater
                        than or equal to 5, but if exclusive is true than
                        all values must be greater than 5 (not including
                        5.0 itself).
Source
<xs:element name="maximum" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Maximum numeric bound summary: Maximum numeric bound of attribute description: The maximum element specifies the maximum permitted value of a numeric attribute.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:float">
        <xs:attribute name="exclusive" type="xs:boolean" use="required">
          <xs:annotation>
            <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / ratio
Namespace No namespace
Annotations
tooltip: Ratio scale

summary: Characteristics used to define ratio
                    scale attributes

description: This field is used for defining the
                    characteristics of this variable if it is a
                    ratio scale variable, which specifies the order and
                    magnitude of values and has a natural zero point, allowing
                    for ratio comparisons to be valid.
                    Ratio is used for data which consists not
                    only of equidistant points but also has a meaningful zero
                    point, which allows ratios to have meaning. An example
                    of a ratio scale would be the Kelvin temperature scale
                    (200K is half as hot as 400K), and length in meters (e.g.,
                    10 meters is twice as long as 5 meters).
Diagram
Diagram NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_ratio_unit NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_ratio_precision NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_ratio_numericDomain
Properties
content complex
Model
Children numericDomain, precision, unit
Instance
<ratio>
  <unit>{1,1}</unit>
  <precision>{0,1}</precision>
  <numericDomain id="">{1,1}</numericDomain>
</ratio>
Source
<xs:element name="ratio">
  <xs:annotation>
    <xs:documentation>tooltip: Ratio scale summary: Characteristics used to define ratio scale attributes description: This field is used for defining the characteristics of this variable if it is a ratio scale variable, which specifies the order and magnitude of values and has a natural zero point, allowing for ratio comparisons to be valid. Ratio is used for data which consists not only of equidistant points but also has a meaningful zero point, which allows ratios to have meaning. An example of a ratio scale would be the Kelvin temperature scale (200K is half as hot as 400K), and length in meters (e.g., 10 meters is twice as long as 5 meters).</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="unit" type="UnitType"/>
      <xs:element name="precision" type="PrecisionType" minOccurs="0"/>
      <xs:element name="numericDomain" type="NumericDomainType"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / ratio / unit
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#UnitType_standardUnit NO_NAMESPACE.tmp#UnitType_customUnit attribute-2_2_0.tmp#UnitType
Type UnitType
Properties
content complex
Model
Children customUnit, standardUnit
Instance
<unit>
  <standardUnit>{1,1}</standardUnit>
  <customUnit>{1,1}</customUnit>
</unit>
Source
<xs:element name="unit" type="UnitType"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / ratio / precision
Namespace No namespace
Diagram
Diagram attribute-2_2_0.tmp#PrecisionType
Type PrecisionType
Properties
content complex
minOccurs 0
Source
<xs:element name="precision" type="PrecisionType" minOccurs="0"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / ratio / numericDomain
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#NumericDomainType_id NO_NAMESPACE.tmp#NumericDomainType_numberType NO_NAMESPACE.tmp#BoundsGroup_bounds attribute-2_2_0.tmp#BoundsGroup NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#NumericDomainType
Type NumericDomainType
Properties
content complex
Model
Children bounds, numberType, references
Instance
<numericDomain id="">
  <numberType>{1,1}</numberType>
  <bounds>{0,unbounded}</bounds>
  <references system="">{1,1}</references>
</numericDomain>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="numericDomain" type="NumericDomainType"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / dateTime
Namespace No namespace
Annotations
tooltip: Date/Time scale

summary: Characteristics used to define date and
                    time attributes

description: 
                      The dateTime field is used for defining the
                    characteristics of the attribute if it contains
                    date and time values. DateTime is used when the values
                    fall on the Gregorian calendar system.  DateTime values
                    are special because they have properties of interval
                    values (most of the time it is legitimate to treat them
                    as interval values by converting them to a duration from
                    a fixed point) but they sometimes only behave as ordinals
                    (because the calendar is not predetermined, for some
                    dateTime values one can only find out the order of
                    the points and not the magnitude of the duration
                    between those points).  Thus, the dateTime scale provides
                    the information necessary to properly understand and
                    parse date and time values without improperly
                    labeling them under one of the more traditional scales.
                      Date and time values are unlike any other measured values.
                      Note that the dateTime field would not be used if
              one is recording time durations.  In that case, one should use a
              standard unit such as seconds, nominalMinute or nominalDay, or a
              customUnit that defines the unit in terms of its relationship to
              SI second.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_dateTime_formatString NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_dateTime_dateTimePrecision NO_NAMESPACE.tmp#AttributeType_AttributeType_measurementScale_AttributeType_AttributeType_measurementScale_dateTime_dateTimeDomain
Properties
content complex
Model
Children dateTimeDomain, dateTimePrecision, formatString
Instance
<dateTime>
  <formatString>{1,1}</formatString>
  <dateTimePrecision>{0,1}</dateTimePrecision>
  <dateTimeDomain id="">{0,1}</dateTimeDomain>
</dateTime>
Source
<xs:element name="dateTime">
  <xs:annotation>
    <xs:documentation>tooltip: Date/Time scale summary: Characteristics used to define date and time attributes description: The dateTime field is used for defining the characteristics of the attribute if it contains date and time values. DateTime is used when the values fall on the Gregorian calendar system. DateTime values are special because they have properties of interval values (most of the time it is legitimate to treat them as interval values by converting them to a duration from a fixed point) but they sometimes only behave as ordinals (because the calendar is not predetermined, for some dateTime values one can only find out the order of the points and not the magnitude of the duration between those points). Thus, the dateTime scale provides the information necessary to properly understand and parse date and time values without improperly labeling them under one of the more traditional scales. Date and time values are unlike any other measured values. Note that the dateTime field would not be used if one is recording time durations. In that case, one should use a standard unit such as seconds, nominalMinute or nominalDay, or a customUnit that defines the unit in terms of its relationship to SI second.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="formatString" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Date/Time Format summary: A format string that describes the format for a date-time value from the Gregorian calendar. description: A format string that describes the format for a dateTime value from the Gregorian calendar. DateTime values should be expressed in a format that conforms to the ISO 8601 standard. This field allows one to specify the format string that should be used to decode the date or time value. To describe the format of an attribute containing dateTime values, construct a string representation of the format using the following symbols: Y year M month W month abbreviation (e.g., JAN) D day h hour m minute s second T time designator (demarcates date and time parts of date-time) Z UTC designator, indicating value is in UTC time . indicates a decimal fraction of a unit +/- indicates a positive or negative number, or a positive or negative time zone adjustment relative to UTC - indicates a separator between date components A/P am or pm designator Any other character in the format string is interpreted as a separator character. Here are some examples of the format strings that can be constructed. Format string Example value ------------------- ------------------ ISO Date YYYY-MM-DD 2002-10-14 ISO Datetime YYYY-MM-DDThh:mm:ss 2002-10-14T09:13:45 ISO Time hh:mm:ss 17:13:45 ISO Time hh:mm:ss.sss 09:13:45.432 ISO Time hh:mm.mm 09:13.42 Non-standard DD/MM/YYYY 14/10/2002 Non-standard MM/DD/YYYY 10/14/2002 Non-standard MM/DD/YY 10/14/02 Non-standard YYYY-MMM-DD 2002-OCT-14 Non-standard YYYYMMMDD 2002OCT14 Non-standard YYYY-MM-DD hh:mm:ss 2002-10-14 09:13:45 Some notes about these examples. First, the ISO 8601 standard is strict about the date components, their order, and the separators; e.g., date parts are upper case, and time parts are lower case. If no UTC relation information is given, the time is assumed to be in local time. Assuming local time is ambiguous even when communicating within a single time zone, given variations in Daylight Saving Time. Best practice is to follow the ISO 8601 format precisely and accurately. In particular, please note that these are all non-standard according to ISO: use of a slash (/) to separate date components, a space to separate date and time components, using a twelve-hour time with am/pm designator, placing any of the components out of descending order However, we recognize that existing data contain non-standard dates, and existing equipment (e.g., sensors) may still be producing non-standard dates. Further, data parsers often apply individual interpretations. E.g., Java interprets HH on a 24-hr clock and hh on a 12-hr clock, and MM as a padded integer for month but MMM as a 3-letter abbreviation. Consequently, the formatting string can contain characters as needed to accommodate existing data. Decimal dateTime values can be extended by indicating in the format that additional decimals can be used. Only the final unit (e.g., seconds in a time value) can use the extended digits according to the ISO 8601 standard. For example, to show indicate that seconds are represented to the nearest 1/1000 of a second, the format string would be "hh:mm:ss.sss". Note that this only indicates the number of decimals used to record the value, and not the precision of the measurement (see dateTimePrecision for that). Date and time values are from an interval scale, but it is extremely complex because of the vagaries of the calendar (e.g., leap years, and leap seconds). The duration between date and time values in the future is not even deterministic because leap seconds are based on current measurements of the earth's orbit. Consequently, date and time values are unlike any other measured values. The format string for dateTime values allows one to accurately calculate the duration in SI second units between two measured dateTime values, assuming that the conversion software has a detailed knowledge of the Gregorian calendar.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="dateTimePrecision" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: DateTime Precision summary: An indication of the precision of a date or time value description: A quantitative indication of the precision of a date or time measurement. The precision should be interpreted in the smallest units represented by the dateTime format. For example, if a dateTime value has a format of "hh:mm:ss.sss", then "seconds" are the smallest unit and the precision should be expressed in seconds. Thus, a precision value of "0.01" would mean that measurements were precise to the nearest hundredth of a second, even though the format string might indicate that values were written down with 3 decimal places.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="dateTimeDomain" type="DateTimeDomainType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: DateTime Domain summary: See the summary for the type: DateTimeDomainType description: See the description for the type: DateTimeDomainType</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / dateTime / formatString
Namespace No namespace
Annotations
tooltip: Date/Time Format

summary: A format string that describes the
                          format for a date-time value from the Gregorian
                          calendar.

description: 
                            A format string that describes
                            the format for a dateTime value from the
                            Gregorian calendar.  DateTime values should be
                            expressed in a format that conforms to the ISO
                            8601 standard.  This field allows one to specify
                            the format string that should be used to decode
                            the date or time value.  To describe the format
                            of an attribute containing dateTime values,
                            construct a string representation of the format
                            using the following symbols:
                            
                            
                              
              Y   year
              M   month
              W   month abbreviation (e.g., JAN)
              D   day
              h   hour
              m   minute
              s   second
              T   time designator (demarcates date and time parts of date-time)
              Z   UTC designator, indicating value is in UTC time
              .   indicates a decimal fraction of a unit
              +/- indicates a positive or negative number,
                  or a positive or negative time zone adjustment relative to UTC
              -   indicates a separator between date components
              A/P am or pm designator
              
                            
                            
              Any other character in the format string is interpreted as a
              separator character.  Here are some examples of the format
              strings that can be constructed.
              
                            
                              
                                 Format string          Example value
                                 -------------------    ------------------
                  ISO Date       YYYY-MM-DD             2002-10-14
                  ISO Datetime   YYYY-MM-DDThh:mm:ss    2002-10-14T09:13:45
                  ISO Time       hh:mm:ss               17:13:45
                  ISO Time       hh:mm:ss.sss           09:13:45.432
                  ISO Time       hh:mm.mm               09:13.42
                  Non-standard   DD/MM/YYYY             14/10/2002
                  Non-standard   MM/DD/YYYY             10/14/2002
                  Non-standard   MM/DD/YY               10/14/02
                  Non-standard   YYYY-MMM-DD            2002-OCT-14
                  Non-standard   YYYYMMMDD              2002OCT14
                  Non-standard   YYYY-MM-DD hh:mm:ss    2002-10-14 09:13:45
              
                            
                            
              Some notes about these examples.  First, the ISO 8601 standard is
              strict about the date components, their order, and the separators;
              e.g., date parts are upper case, and time parts are lower case.
              If no UTC relation information is given, the time is assumed to be in local
              time. Assuming local time is ambiguous even when communicating within a
              single time zone, given variations in Daylight Saving Time.
              Best practice is to follow the ISO 8601 format precisely and accurately.
                            
                            
              In particular, please note that these are all non-standard
                according to ISO:
              
                use of a slash (/) to separate date components,
                a space to separate date and time components,
                using a twelve-hour time with am/pm designator,
                placing any of the components out of descending order
              
                            
                            

              However, we recognize that existing data contain
              non-standard dates, and existing equipment (e.g., sensors) may
              still be producing non-standard dates.
              Further, data parsers often apply individual interpretations. E.g., Java
              interprets HH on a 24-hr clock and hh on a 12-hr clock, and MM as a
              padded integer for month but MMM as a 3-letter abbreviation.
              Consequently, the formatting string can contain characters as needed
               to accommodate existing data.
              
                            
              Decimal dateTime values can be extended by indicating in
              the format that additional decimals can be used.  Only the final
              unit (e.g., seconds in a time value) can use the extended digits
              according to the ISO 8601 standard.  For example, to show
              indicate that seconds are represented to the nearest 1/1000
              of a second, the format string would be "hh:mm:ss.sss".
              Note that this only indicates the number of decimals used to
              record the value, and not the precision of the measurement
              (see dateTimePrecision for that).
              
                            
              Date and time values are from an interval scale, but it is extremely
              complex because of the vagaries of the calendar (e.g., leap
              years, and leap seconds).  The duration between date and time values
              in the future is not even deterministic because leap seconds are
              based on current measurements of the earth's orbit. Consequently,
              date and time values are unlike any other measured values.  The format
              string for dateTime values allows one to accurately calculate the
              duration in SI second units between two measured dateTime values,
              assuming that the conversion software has a detailed knowledge of
              the Gregorian calendar.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="formatString" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Date/Time Format summary: A format string that describes the format for a date-time value from the Gregorian calendar. description: A format string that describes the format for a dateTime value from the Gregorian calendar. DateTime values should be expressed in a format that conforms to the ISO 8601 standard. This field allows one to specify the format string that should be used to decode the date or time value. To describe the format of an attribute containing dateTime values, construct a string representation of the format using the following symbols: Y year M month W month abbreviation (e.g., JAN) D day h hour m minute s second T time designator (demarcates date and time parts of date-time) Z UTC designator, indicating value is in UTC time . indicates a decimal fraction of a unit +/- indicates a positive or negative number, or a positive or negative time zone adjustment relative to UTC - indicates a separator between date components A/P am or pm designator Any other character in the format string is interpreted as a separator character. Here are some examples of the format strings that can be constructed. Format string Example value ------------------- ------------------ ISO Date YYYY-MM-DD 2002-10-14 ISO Datetime YYYY-MM-DDThh:mm:ss 2002-10-14T09:13:45 ISO Time hh:mm:ss 17:13:45 ISO Time hh:mm:ss.sss 09:13:45.432 ISO Time hh:mm.mm 09:13.42 Non-standard DD/MM/YYYY 14/10/2002 Non-standard MM/DD/YYYY 10/14/2002 Non-standard MM/DD/YY 10/14/02 Non-standard YYYY-MMM-DD 2002-OCT-14 Non-standard YYYYMMMDD 2002OCT14 Non-standard YYYY-MM-DD hh:mm:ss 2002-10-14 09:13:45 Some notes about these examples. First, the ISO 8601 standard is strict about the date components, their order, and the separators; e.g., date parts are upper case, and time parts are lower case. If no UTC relation information is given, the time is assumed to be in local time. Assuming local time is ambiguous even when communicating within a single time zone, given variations in Daylight Saving Time. Best practice is to follow the ISO 8601 format precisely and accurately. In particular, please note that these are all non-standard according to ISO: use of a slash (/) to separate date components, a space to separate date and time components, using a twelve-hour time with am/pm designator, placing any of the components out of descending order However, we recognize that existing data contain non-standard dates, and existing equipment (e.g., sensors) may still be producing non-standard dates. Further, data parsers often apply individual interpretations. E.g., Java interprets HH on a 24-hr clock and hh on a 12-hr clock, and MM as a padded integer for month but MMM as a 3-letter abbreviation. Consequently, the formatting string can contain characters as needed to accommodate existing data. Decimal dateTime values can be extended by indicating in the format that additional decimals can be used. Only the final unit (e.g., seconds in a time value) can use the extended digits according to the ISO 8601 standard. For example, to show indicate that seconds are represented to the nearest 1/1000 of a second, the format string would be "hh:mm:ss.sss". Note that this only indicates the number of decimals used to record the value, and not the precision of the measurement (see dateTimePrecision for that). Date and time values are from an interval scale, but it is extremely complex because of the vagaries of the calendar (e.g., leap years, and leap seconds). The duration between date and time values in the future is not even deterministic because leap seconds are based on current measurements of the earth's orbit. Consequently, date and time values are unlike any other measured values. The format string for dateTime values allows one to accurately calculate the duration in SI second units between two measured dateTime values, assuming that the conversion software has a detailed knowledge of the Gregorian calendar.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / dateTime / dateTimePrecision
Namespace No namespace
Annotations
tooltip: DateTime Precision

summary: An indication of the precision of a
                          date or time value

description: A quantitative indication of
                          the precision of a date or time measurement.
                          The precision should be interpreted in the
                          smallest units represented by the dateTime format.
                          For example, if a dateTime value has a format of
                          "hh:mm:ss.sss", then "seconds" are the smallest unit
                          and the precision should be expressed in seconds.
                          Thus, a precision value of "0.01" would mean that
                          measurements were precise to the nearest hundredth
                          of a second, even though the format string might
                          indicate that values were written down with 3
                          decimal places.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="dateTimePrecision" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: DateTime Precision summary: An indication of the precision of a date or time value description: A quantitative indication of the precision of a date or time measurement. The precision should be interpreted in the smallest units represented by the dateTime format. For example, if a dateTime value has a format of "hh:mm:ss.sss", then "seconds" are the smallest unit and the precision should be expressed in seconds. Thus, a precision value of "0.01" would mean that measurements were precise to the nearest hundredth of a second, even though the format string might indicate that values were written down with 3 decimal places.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / measurementScale / dateTime / dateTimeDomain
Namespace No namespace
Annotations
tooltip: DateTime Domain

summary: See the summary for the type: DateTimeDomainType

description: See the description for the type: DateTimeDomainType
Diagram
Diagram NO_NAMESPACE.tmp#DateTimeDomainType_id NO_NAMESPACE.tmp#BoundsDateGroup_bounds attribute-2_2_0.tmp#BoundsDateGroup NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#DateTimeDomainType
Type DateTimeDomainType
Properties
content complex
minOccurs 0
Model
Children bounds, references
Instance
<dateTimeDomain id="">
  <bounds>{0,unbounded}</bounds>
  <references system="">{1,1}</references>
</dateTimeDomain>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="dateTimeDomain" type="DateTimeDomainType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: DateTime Domain summary: See the summary for the type: DateTimeDomainType description: See the description for the type: DateTimeDomainType</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element BoundsDateGroup / bounds
Namespace No namespace
Annotations
tooltip: Bounds

summary: Elements for specifying allowed
        date range.

description: The bounds element in the BoundsDateGroup contains the
        minimum and maximum dates of a dateTime attribute. These
        are theoretical or permitted values (ie. prescriptive), and
        not necessarily the actual minimum and maximum observed in
        a given data set (descriptive). Either or both a minimum and maximum may
        be set, and each has an attribute "exclusive" to define how the value should
        be interpreted.
Diagram
Diagram NO_NAMESPACE.tmp#BoundsDateGroup_BoundsDateGroup_bounds_minimum NO_NAMESPACE.tmp#BoundsDateGroup_BoundsDateGroup_bounds_maximum
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children maximum, minimum
Instance
<bounds>
  <minimum exclusive="">{0,1}</minimum>
  <maximum exclusive="">{0,1}</maximum>
</bounds>
Source
<xs:element name="bounds" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Bounds summary: Elements for specifying allowed date range. description: The bounds element in the BoundsDateGroup contains the minimum and maximum dates of a dateTime attribute. These are theoretical or permitted values (ie. prescriptive), and not necessarily the actual minimum and maximum observed in a given data set (descriptive). Either or both a minimum and maximum may be set, and each has an attribute "exclusive" to define how the value should be interpreted.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="minimum" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Minimum date bound summary: Minimum date bound of attribute description: The minimum element specifies the minimum permitted value of a date attribute.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:string">
              <xs:attribute name="exclusive" type="xs:boolean" use="required">
                <xs:annotation>
                  <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
      <xs:element name="maximum" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Maximum date bound summary: Maximum date bound of attribute description: The maximum element specifies the maximum permitted value of a date attribute.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:string">
              <xs:attribute name="exclusive" type="xs:boolean" use="required">
                <xs:annotation>
                  <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
                </xs:annotation>
              </xs:attribute>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element BoundsDateGroup / bounds / minimum
Namespace No namespace
Annotations
tooltip: Minimum date bound

summary: Minimum date bound of
                attribute

description: The minimum element specifies the
                minimum permitted value of a date
                attribute.
Diagram
Diagram NO_NAMESPACE.tmp#BoundsDateGroup_BoundsDateGroup_bounds_BoundsDateGroup_BoundsDateGroup_bounds_minimum_exclusive
Type extension of xs:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
exclusive xs:boolean required
tooltip: Exclusive
                        

summary: Exclusive bounds flag
                        

description: If exclusive is set to true, then
                        the value specifies a lower bound not including
                        the value itself.  Setting exclusive to true is
                        the equivalent of using a less-than or greater-than
                        operator, while setting it to false is the same as
                        using a less-than-or-equals or greater-than-or-equals
                        operator. For example, if the minimum is "5" and
                        exclusive is false, then all values must be greater
                        than or equal to 5, but if exclusive is true than
                        all values must be greater than 5 (not including
                        5.0 itself).
Source
<xs:element name="minimum" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Minimum date bound summary: Minimum date bound of attribute description: The minimum element specifies the minimum permitted value of a date attribute.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="exclusive" type="xs:boolean" use="required">
          <xs:annotation>
            <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element BoundsDateGroup / bounds / maximum
Namespace No namespace
Annotations
tooltip: Maximum date bound

summary: Maximum date bound of
                attribute

description: The maximum element specifies the
                maximum permitted value of a date
                attribute.
Diagram
Diagram NO_NAMESPACE.tmp#BoundsDateGroup_BoundsDateGroup_bounds_BoundsDateGroup_BoundsDateGroup_bounds_maximum_exclusive
Type extension of xs:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
exclusive xs:boolean required
tooltip: Exclusive
                        

summary: Exclusive bounds flag
                        

description: If exclusive is set to true, then
                        the value specifies a lower bound not including
                        the value itself.  Setting exclusive to true is
                        the equivalent of using a less-than or greater-than
                        operator, while setting it to false is the same as
                        using a less-than-or-equals or greater-than-or-equals
                        operator. For example, if the minimum is "5" and
                        exclusive is false, then all values must be greater
                        than or equal to 5, but if exclusive is true than
                        all values must be greater than 5 (not including
                        5.0 itself).
Source
<xs:element name="maximum" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Maximum date bound summary: Maximum date bound of attribute description: The maximum element specifies the maximum permitted value of a date attribute.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="exclusive" type="xs:boolean" use="required">
          <xs:annotation>
            <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / missingValueCode
Namespace No namespace
Annotations
tooltip: Character for missing value

summary: Character for missing value in the data of the
              field

description: This element is to specify missing value in the
              data of the field. It is repeatable to allow for multiple
              different codes to be present in the attribute. Note that missing
              value codes should not be considered when determining if the
              observed values of an attribute all fall within the domain
              of the attribute (i.e., missing value codes should be parsed out
              of the data stream before examining the data for domain
              violations.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeType_AttributeType_missingValueCode_code NO_NAMESPACE.tmp#AttributeType_AttributeType_missingValueCode_codeExplanation
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children code, codeExplanation
Instance
<missingValueCode>
  <code>{1,1}</code>
  <codeExplanation>{1,1}</codeExplanation>
</missingValueCode>
Source
<xs:element name="missingValueCode" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Character for missing value summary: Character for missing value in the data of the field description: This element is to specify missing value in the data of the field. It is repeatable to allow for multiple different codes to be present in the attribute. Note that missing value codes should not be considered when determining if the observed values of an attribute all fall within the domain of the attribute (i.e., missing value codes should be parsed out of the data stream before examining the data for domain violations.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="code" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: The missing value code itself. summary: The missing value code itself. description: The code element is the missing value code itself. Each missing value code should be entered in a separate element instance. The value entered is what is placed into a data grid if the value is missing for some reason.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="codeExplanation" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Explanation of Missing value Code summary: An explanation of what the missing value code means. description: The codeExplanation element is an explanation of the meaning of the missing value code that was used, that is, the reason that there is a missing value. For example, an attribute might have a missing value code of '-99' to indicate that the data observation was not actually taken, and a code of '-88' to indicate that the data value was removed because of calibration errors.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / missingValueCode / code
Namespace No namespace
Annotations
tooltip: The missing value code itself.

summary: The missing value code itself.

description: The code element is the missing value code
                    itself. Each missing value code should be entered in a
                    separate element instance. The value entered is what is
                    placed into a data grid if the value is missing for some
                    reason.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="code" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: The missing value code itself. summary: The missing value code itself. description: The code element is the missing value code itself. Each missing value code should be entered in a separate element instance. The value entered is what is placed into a data grid if the value is missing for some reason.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / missingValueCode / codeExplanation
Namespace No namespace
Annotations
tooltip: Explanation of Missing value Code

summary: An explanation of what the missing value code
                    means.

description: The codeExplanation element is an
                    explanation of the meaning of the missing value code that
                    was used, that is, the reason that there is a missing
                    value. For example, an attribute might have a missing
                    value code of '-99' to indicate that the data observation
                    was not actually taken, and a code of '-88' to indicate
                    that the data value was removed because of
                    calibration errors.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="codeExplanation" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Explanation of Missing value Code summary: An explanation of what the missing value code means. description: The codeExplanation element is an explanation of the meaning of the missing value code that was used, that is, the reason that there is a missing value. For example, an attribute might have a missing value code of '-99' to indicate that the data observation was not actually taken, and a code of '-88' to indicate that the data value was removed because of calibration errors.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / accuracy
Namespace No namespace
Annotations
tooltip: The accuracy of the measured attribute

summary: The accuracy of the attribute. This information
              should describe any accuracy information that is known about the
              collection of this data attribute.

description: The accuracy element represents the accuracy of
              the attribute. This information should describe any accuracy
              information that is known about the collection of this data
              attribute. The content model of this metadata is taken directly
              from FGDC FGDC-STD-001-1998 section 2 with the exception of
              processContact, sourceCitation, and timePeriodInformation which
              either user XMLSchema types or use predefined EML types for these
              purposes.
Diagram
Diagram NO_NAMESPACE.tmp#Accuracy_attributeAccuracyReport NO_NAMESPACE.tmp#Accuracy_quantitativeAttributeAccuracyAssessment attribute-2_2_0.tmp#Accuracy
Type Accuracy
Properties
content complex
minOccurs 0
Model
Children attributeAccuracyReport, quantitativeAttributeAccuracyAssessment
Instance
<accuracy>
  <attributeAccuracyReport>{1,1}</attributeAccuracyReport>
  <quantitativeAttributeAccuracyAssessment>{0,unbounded}</quantitativeAttributeAccuracyAssessment>
</accuracy>
Source
<xs:element name="accuracy" type="Accuracy" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: The accuracy of the measured attribute summary: The accuracy of the attribute. This information should describe any accuracy information that is known about the collection of this data attribute. description: The accuracy element represents the accuracy of the attribute. This information should describe any accuracy information that is known about the collection of this data attribute. The content model of this metadata is taken directly from FGDC FGDC-STD-001-1998 section 2 with the exception of processContact, sourceCitation, and timePeriodInformation which either user XMLSchema types or use predefined EML types for these purposes.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element Accuracy / attributeAccuracyReport
Namespace No namespace
Annotations
tooltip: Attribute Accuracy Report

summary: An explanatory report of the accuracy of the
            attribute.

description: The attributeAccuracyReport element is an
            explanation of the accuracy of the observation recorded in this
            attribute. It will often include a description of the tests used to
            determine the accuracy of the observation. These reports are
            generally prepared for remote sensing or other measurement
            devices.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeAccuracyReport" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute Accuracy Report summary: An explanatory report of the accuracy of the attribute. description: The attributeAccuracyReport element is an explanation of the accuracy of the observation recorded in this attribute. It will often include a description of the tests used to determine the accuracy of the observation. These reports are generally prepared for remote sensing or other measurement devices.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element Accuracy / quantitativeAttributeAccuracyAssessment
Namespace No namespace
Annotations
tooltip: Quantitative Attribute Accuracy
            Assessment

summary: A value assigned to summarize the accuracy of the
            attribute.

description: The quantitativeAttributeAccuracyAssessment
            element is composed of two parts, a value that represents the
            accuracy of the recorded observation an explanation of the tests
            used to determine the accuracy.
Diagram
Diagram NO_NAMESPACE.tmp#Accuracy_Accuracy_quantitativeAttributeAccuracyAssessment_attributeAccuracyValue NO_NAMESPACE.tmp#Accuracy_Accuracy_quantitativeAttributeAccuracyAssessment_attributeAccuracyExplanation
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children attributeAccuracyExplanation, attributeAccuracyValue
Instance
<quantitativeAttributeAccuracyAssessment>
  <attributeAccuracyValue>{1,1}</attributeAccuracyValue>
  <attributeAccuracyExplanation>{1,1}</attributeAccuracyExplanation>
</quantitativeAttributeAccuracyAssessment>
Source
<xs:element name="quantitativeAttributeAccuracyAssessment" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Quantitative Attribute Accuracy Assessment summary: A value assigned to summarize the accuracy of the attribute. description: The quantitativeAttributeAccuracyAssessment element is composed of two parts, a value that represents the accuracy of the recorded observation an explanation of the tests used to determine the accuracy.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="attributeAccuracyValue" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Attribute Accuracy Value summary: A value assigned to estimate the accuracy of the attribute. description: The attributeAccuracyValue element is an estimate of the accuracy of the identification of the entities and assignments of attribute values in the data set.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="attributeAccuracyExplanation" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Attribute Accuracy Explanation summary: The test which yields the Attribute Accuracy Value. description: The attributeAccuracyExplanation element is the identification of the test that yielded the Attribute Accuracy Value.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element Accuracy / quantitativeAttributeAccuracyAssessment / attributeAccuracyValue
Namespace No namespace
Annotations
tooltip: Attribute Accuracy Value

summary: A value assigned to estimate the accuracy of the
                  attribute.

description: The attributeAccuracyValue element is an
                  estimate of the accuracy of the identification of the
                  entities and assignments of attribute values in the data set.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeAccuracyValue" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute Accuracy Value summary: A value assigned to estimate the accuracy of the attribute. description: The attributeAccuracyValue element is an estimate of the accuracy of the identification of the entities and assignments of attribute values in the data set.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element Accuracy / quantitativeAttributeAccuracyAssessment / attributeAccuracyExplanation
Namespace No namespace
Annotations
tooltip: Attribute Accuracy Explanation

summary: The test which yields the Attribute Accuracy
                  Value.

description: The attributeAccuracyExplanation element is
                  the identification of the test that yielded the Attribute
                  Accuracy Value.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeAccuracyExplanation" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute Accuracy Explanation summary: The test which yields the Attribute Accuracy Value. description: The attributeAccuracyExplanation element is the identification of the test that yielded the Attribute Accuracy Value.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / coverage
Namespace No namespace
Annotations
tooltip: Attribute coverage

summary: An explanation of the coverage of the attribute.
              

description: An explanation of the coverage of the attribute.
              This specifically indicates the spatial, temporal, and taxonomic
              coverage of the attribute in question when that coverage deviates
              from coverages expressed at a higher level (e.g., entity or
              dataset).  Please see the eml-coverage module for complete
              documentation.
Diagram
Diagram NO_NAMESPACE.tmp#Coverage_id NO_NAMESPACE.tmp#Coverage_system NO_NAMESPACE.tmp#Coverage_scope NO_NAMESPACE.tmp#Coverage_geographicCoverage NO_NAMESPACE.tmp#Coverage_temporalCoverage NO_NAMESPACE.tmp#Coverage_taxonomicCoverage NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup coverage-2_2_0.tmp#Coverage
Type Coverage
Properties
content complex
minOccurs 0
Model
Children geographicCoverage, references, taxonomicCoverage, temporalCoverage
Instance
<coverage id="" scope="document" system="">
  <geographicCoverage id="" scope="document" system="">{1,1}</geographicCoverage>
  <temporalCoverage id="" scope="document" system="">{1,1}</temporalCoverage>
  <taxonomicCoverage id="" scope="document" system="">{1,1}</taxonomicCoverage>
  <references system="">{1,1}</references>
</coverage>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="coverage" type="cov:Coverage" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute coverage summary: An explanation of the coverage of the attribute. description: An explanation of the coverage of the attribute. This specifically indicates the spatial, temporal, and taxonomic coverage of the attribute in question when that coverage deviates from coverages expressed at a higher level (e.g., entity or dataset). Please see the eml-coverage module for complete documentation.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / methods
Namespace No namespace
Annotations
tooltip: Attribute methods

summary: An explanation of the methods involved in the
              collection of this attribute.

description: An explanation of the methods involved in the
              collection of this attribute. These specifically supplement or
              possibly override methods provided at a higher level such as
              entity or dataset.
              Please see the eml-methods module for complete documentation.
Diagram
Diagram NO_NAMESPACE.tmp#MethodsType_methodStep NO_NAMESPACE.tmp#MethodsType_sampling NO_NAMESPACE.tmp#MethodsType_qualityControl methods-2_2_0.tmp#MethodsType
Type MethodsType
Properties
content complex
minOccurs 0
Model
Children methodStep, qualityControl, sampling
Instance
<methods>
  <methodStep>{1,unbounded}</methodStep>
  <sampling>{0,1}</sampling>
  <qualityControl>{0,unbounded}</qualityControl>
</methods>
Source
<xs:element name="methods" type="md:MethodsType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute methods summary: An explanation of the methods involved in the collection of this attribute. description: An explanation of the methods involved in the collection of this attribute. These specifically supplement or possibly override methods provided at a higher level such as entity or dataset. Please see the eml-methods module for complete documentation.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element AttributeType / annotation
Namespace No namespace
Annotations
tooltip: Semantic Annotation

summary: A precisely-defined semantic statement for this attribute.
              

description: An annotation represents a precisely-defined semantic
                  statement that applies to this attribute.  This semantic
                  statement is used to associate precise measurement semantics
                  with the attribute, such as the property that is being measured
                  (e.g., oboe:Characteristic), the entity that is being measured
                  (e.g., oboe:Entity), and the measurement standard for
                  interpreting values for this attribute (e.g., oboe:Standard).
                  Each annotation consists of a propertyURI and valueURI that
                  define the property and value of the statement.  The subject
                  of the statement is the eml:attribute that contains the
                  annotation. The associated labels can be used
                  to display the statement to users.  Each URI is
                  resolvable to a controlled vocabulary that provides
                  a definition, relationships to other terms, and multiple
                  labels for displaying the statement.
Diagram
Diagram NO_NAMESPACE.tmp#SemanticAnnotation_propertyURI NO_NAMESPACE.tmp#SemanticAnnotation_valueURI semantics-2_2_0.tmp#SemanticAnnotation
Type SemanticAnnotation
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children propertyURI, valueURI
Instance
<annotation>
  <propertyURI label="">{1,1}</propertyURI>
  <valueURI label="">{1,1}</valueURI>
</annotation>
Source
<xs:element name="annotation" type="sem:SemanticAnnotation" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement for this attribute. description: An annotation represents a precisely-defined semantic statement that applies to this attribute. This semantic statement is used to associate precise measurement semantics with the attribute, such as the property that is being measured (e.g., oboe:Characteristic), the entity that is being measured (e.g., oboe:Entity), and the measurement standard for interpreting values for this attribute (e.g., oboe:Standard). Each annotation consists of a propertyURI and valueURI that define the property and value of the statement. The subject of the statement is the eml:attribute that contains the annotation. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Element DataTableType / constraint
Namespace No namespace
Annotations
tooltip: Constraint

summary: 

description: Description of any relational constraints on '
              this entity.  For more information see the eml-constraint
              module.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_id NO_NAMESPACE.tmp#ConstraintType_system NO_NAMESPACE.tmp#ConstraintType_scope NO_NAMESPACE.tmp#ConstraintType_primaryKey NO_NAMESPACE.tmp#ConstraintType_uniqueKey NO_NAMESPACE.tmp#ConstraintType_checkConstraint NO_NAMESPACE.tmp#ConstraintType_foreignKey NO_NAMESPACE.tmp#ConstraintType_joinCondition NO_NAMESPACE.tmp#ConstraintType_notNullConstraint constraint-2_2_0.tmp#ConstraintType
Type ConstraintType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children checkConstraint, foreignKey, joinCondition, notNullConstraint, primaryKey, uniqueKey
Instance
<constraint id="" scope="document" system="">
  <primaryKey>{1,1}</primaryKey>
  <uniqueKey>{1,1}</uniqueKey>
  <checkConstraint language="">{1,1}</checkConstraint>
  <foreignKey>{1,1}</foreignKey>
  <joinCondition>{1,1}</joinCondition>
  <notNullConstraint>{1,1}</notNullConstraint>
</constraint>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataTable.xsd
Element ConstraintType / primaryKey
Namespace No namespace
Annotations
tooltip: Primary Key

summary: The primary key in the entity

description: The primaryKey element declares the primary key in
            the entity to which the defined constraint
            pertains.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintName NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintDescription constraint-2_2_0.tmp#ConstraintBaseGroup NO_NAMESPACE.tmp#ConstraintType_ConstraintType_primaryKey_key
Properties
content complex
Model
Children constraintDescription, constraintName, key
Instance
<primaryKey>
  <constraintName>{1,1}</constraintName>
  <constraintDescription>{0,1}</constraintDescription>
  <key>{1,1}</key>
</primaryKey>
Source
<xs:element name="primaryKey">
  <xs:annotation>
    <xs:documentation>tooltip: Primary Key summary: The primary key in the entity description: The primaryKey element declares the primary key in the entity to which the defined constraint pertains.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:group ref="ConstraintBaseGroup"/>
      <xs:element name="key">
        <xs:annotation>
          <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintBaseGroup / constraintName
Namespace No namespace
Annotations
tooltip: Name of the constraint

summary: A meaningfull name of the constraint.

description: The constraintName element is a name which
            represents a human readable and meaningful name for the
            constraint.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="constraintName" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Name of the constraint summary: A meaningfull name of the constraint. description: The constraintName element is a name which represents a human readable and meaningful name for the constraint.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintBaseGroup / constraintDescription
Namespace No namespace
Annotations
tooltip: Description of the constraint

summary: Descibes the purpose of the constraint.

description: The constraintDescription element describes the
            nature of the constraint. It might be a description of a check
            condition, or a statement about the composition of a primary key or
            the nature of the relationship between two database tables or two
            ascii files.
Diagram
Diagram
Properties
minOccurs 0
Source
<xs:element name="constraintDescription" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Description of the constraint summary: Descibes the purpose of the constraint. description: The constraintDescription element describes the nature of the constraint. It might be a description of a check condition, or a statement about the composition of a primary key or the nature of the relationship between two database tables or two ascii files.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / primaryKey / key
Namespace No namespace
Annotations
tooltip: Key

summary: The set of attributes to which this constraint
                  applies.

description: The key element defines the set of attributes
                  to which this constraint applies. For a primary key or a
                  unique key, the set of attributes must be identifying. For a
                  foreign key, the set of attributes must match an identifying
                  key in the referenced entity. For a 'not null' constraint, the
                  key indicates the attribute which should not be
                  null.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_ConstraintType_primaryKey_ConstraintType_ConstraintType_primaryKey_key_attributeReference
Properties
content complex
Model
Children attributeReference
Instance
<key>
  <attributeReference>{1,unbounded}</attributeReference>
</key>
Source
<xs:element name="key">
  <xs:annotation>
    <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / primaryKey / key / attributeReference
Namespace No namespace
Annotations
tooltip: Attribute Reference

summary: The identifier of an attribute found
                        in the identified entity

description: The attributeReference element is the
                        identifier of an attribute that can be found in the
                        identified entity. This id will be unique within an
                        entity and specifies that the attribute participates
                        in the key that is being defined.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / uniqueKey
Namespace No namespace
Annotations
tooltip: Unique Key

summary: A unique key in the entity

description: The uniqueKey element represents a unique key
            within the referenced entity. This is different from a primary key
            in that it does not form any implicit foreign key relationships to
            other entities, however it is required to be unique within the
            entity.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintName NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintDescription constraint-2_2_0.tmp#ConstraintBaseGroup NO_NAMESPACE.tmp#ConstraintType_ConstraintType_uniqueKey_key
Properties
content complex
Model
Children constraintDescription, constraintName, key
Instance
<uniqueKey>
  <constraintName>{1,1}</constraintName>
  <constraintDescription>{0,1}</constraintDescription>
  <key>{1,1}</key>
</uniqueKey>
Source
<xs:element name="uniqueKey">
  <xs:annotation>
    <xs:documentation>tooltip: Unique Key summary: A unique key in the entity description: The uniqueKey element represents a unique key within the referenced entity. This is different from a primary key in that it does not form any implicit foreign key relationships to other entities, however it is required to be unique within the entity.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:group ref="ConstraintBaseGroup"/>
      <xs:element name="key">
        <xs:annotation>
          <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / uniqueKey / key
Namespace No namespace
Annotations
tooltip: Key

summary: The set of attributes to which this constraint
                  applies.

description: The key element defines the set of attributes
                  to which this constraint applies. For a primary key or a
                  unique key, the set of attributes must be identifying. For a
                  foreign key, the set of attributes must match an identifying
                  key in the referenced entity. For a 'not null' constraint, the
                  key indicates the attribute which should not be
                  null.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_ConstraintType_uniqueKey_ConstraintType_ConstraintType_uniqueKey_key_attributeReference
Properties
content complex
Model
Children attributeReference
Instance
<key>
  <attributeReference>{1,unbounded}</attributeReference>
</key>
Source
<xs:element name="key">
  <xs:annotation>
    <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / uniqueKey / key / attributeReference
Namespace No namespace
Annotations
tooltip: Attribute Reference

summary: The identifier of an attribute found
                        in the identified entity

description: The attributeReference element is the
                        identifier of an attribute that can be found in the
                        identified entity. This id will be unique within an
                        entity and specifies that the attribute participates
                        in the key that is being defined.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / checkConstraint
Namespace No namespace
Annotations
tooltip: Check Constraint

summary: A constraint which checks a conditional clause
            within an entity.

description: The checkConstraint element defines a constraint
            which checks a conditional clause within an
            entity.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_ConstraintType_checkConstraint_language NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintName NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintDescription constraint-2_2_0.tmp#ConstraintBaseGroup NO_NAMESPACE.tmp#ConstraintType_ConstraintType_checkConstraint_checkCondition
Properties
content complex
Model
Children checkCondition, constraintDescription, constraintName
Instance
<checkConstraint language="">
  <constraintName>{1,1}</constraintName>
  <constraintDescription>{0,1}</constraintDescription>
  <checkCondition>{1,1}</checkCondition>
</checkConstraint>
Attributes
QName Type Use Annotation
language xs:string optional
tooltip: Language

summary: The language that the is used to express or
                implement the check constraint.

description: The language element declares the language
                that is used to implement the check constraint.  This is
                typically the name and version of a programming language such as
                Java, C, Perl, Basic, or other.  Sometime it is the name and
                version of a scriptable analysis system such as SAS, Matlab, R,
                or SPlus.
Source
<xs:element name="checkConstraint">
  <xs:annotation>
    <xs:documentation>tooltip: Check Constraint summary: A constraint which checks a conditional clause within an entity. description: The checkConstraint element defines a constraint which checks a conditional clause within an entity.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:group ref="ConstraintBaseGroup"/>
      <xs:element name="checkCondition" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Check Condition summary: An SQL statement or other language implementation of the condition for a check constraint. description: The checkCondition element defines an SQL statement or other language implementation of the condition for a check constraint. Generally this provides a means for constraining the values within and among entities.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="language" type="xs:string" use="optional">
      <xs:annotation>
        <xs:documentation>tooltip: Language summary: The language that the is used to express or implement the check constraint. description: The language element declares the language that is used to implement the check constraint. This is typically the name and version of a programming language such as Java, C, Perl, Basic, or other. Sometime it is the name and version of a scriptable analysis system such as SAS, Matlab, R, or SPlus.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / checkConstraint / checkCondition
Namespace No namespace
Annotations
tooltip: Check Condition

summary: An SQL statement or other language
                  implementation of the condition for a check
                  constraint.

description: The checkCondition element defines an SQL
                  statement or other language implementation of the condition
                  for a check constraint.  Generally this provides a means for
                  constraining the values within and among
                  entities.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="checkCondition" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Check Condition summary: An SQL statement or other language implementation of the condition for a check constraint. description: The checkCondition element defines an SQL statement or other language implementation of the condition for a check constraint. Generally this provides a means for constraining the values within and among entities.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / foreignKey
Namespace No namespace
Annotations
tooltip: Foreign Key

summary: A foreign key relationship among entities

description: The foreignKey element defines a foreign key
            relationship among entities which relates this entity to another's
            primary key.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintName NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintDescription constraint-2_2_0.tmp#ConstraintBaseGroup NO_NAMESPACE.tmp#ForeignKeyGroup_key NO_NAMESPACE.tmp#ForeignKeyGroup_entityReference NO_NAMESPACE.tmp#ForeignKeyGroup_relationshipType NO_NAMESPACE.tmp#ForeignKeyGroup_cardinality constraint-2_2_0.tmp#ForeignKeyGroup
Properties
content complex
Model
Children cardinality, constraintDescription, constraintName, entityReference, key, relationshipType
Instance
<foreignKey>
  <constraintName>{1,1}</constraintName>
  <constraintDescription>{0,1}</constraintDescription>
  <key>{1,1}</key>
  <entityReference>{1,1}</entityReference>
  <relationshipType>{0,1}</relationshipType>
  <cardinality>{0,1}</cardinality>
</foreignKey>
Source
<xs:element name="foreignKey">
  <xs:annotation>
    <xs:documentation>tooltip: Foreign Key summary: A foreign key relationship among entities description: The foreignKey element defines a foreign key relationship among entities which relates this entity to another's primary key.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:group ref="ForeignKeyGroup"/>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ForeignKeyGroup / key
Namespace No namespace
Annotations
tooltip: Key

summary: The set of attributes to which this constraint
            applies.

description: The key element defines the set of attributes to
            which this constraint applies. For a primary key or a unique key,
            the set of attributes must be identifying. For a foreign key, the
            set of attributes must match an identifying key in the referenced
            entity. For a 'not null' constraint, the key indicates the attribute
            which should not be null.
Diagram
Diagram NO_NAMESPACE.tmp#ForeignKeyGroup_ForeignKeyGroup_key_attributeReference
Properties
content complex
Model
Children attributeReference
Instance
<key>
  <attributeReference>{1,unbounded}</attributeReference>
</key>
Source
<xs:element name="key">
  <xs:annotation>
    <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ForeignKeyGroup / key / attributeReference
Namespace No namespace
Annotations
tooltip: Attribute Reference

summary: The identifier of an attribute found
                  in the identified entity

description: The attributeReference element is the
                  identifier of an attribute that can be found in the
                  identified entity. This id will be unique within an
                  entity and specifies that the attribute participates
                  in the key that is being defined.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ForeignKeyGroup / entityReference
Namespace No namespace
Annotations
tooltip: Referenced Entity ID

summary: The id of the parent-entity in a foreign key
            constraint.

description: The entityReference element contains the id of the
            entity to which a foreign key refers, otherwise known as the
            parent-entity or parent-table. This should be an identifier that
            matches one of the "identifier" elements for an
            entity.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="entityReference" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Referenced Entity ID summary: The id of the parent-entity in a foreign key constraint. description: The entityReference element contains the id of the entity to which a foreign key refers, otherwise known as the parent-entity or parent-table. This should be an identifier that matches one of the "identifier" elements for an entity.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ForeignKeyGroup / relationshipType
Namespace No namespace
Annotations
tooltip: Relationship type: Identifying or
            non-identifying

summary: Relationship type: Identifying or
            non-identifying

description: The relationshipType element defines identifying
            relationships that propagate from the parent entity's primary key to
            the child's primary key. Non-identifying relationships propagate the
            parent's primary key as a non-key attribute of the child
            entity.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
Facets
enumeration identifying
enumeration non-identifying
Source
<xs:element name="relationshipType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Relationship type: Identifying or non-identifying summary: Relationship type: Identifying or non-identifying description: The relationshipType element defines identifying relationships that propagate from the parent entity's primary key to the child's primary key. Non-identifying relationships propagate the parent's primary key as a non-key attribute of the child entity.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="identifying"/>
      <xs:enumeration value="non-identifying"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ForeignKeyGroup / cardinality
Namespace No namespace
Annotations
tooltip: Cardinality of the relationship between two
            entities.

summary: Cardinality of the relationship between a parent
            entity and a child entity.

description: The cardinality element represents a statement of
            the relationship between parent and child entities. Cardinality is
            expressed as the ratio of related parent and child
            entities. Cardinality 1 to N is a specific form of cardinality in
            which zero or one parent records are related to a specified number
            of child records. The cardinality ratio for the parent entity
            depends on whether the "existence" is mandatory (one or more) or
            optional (zero to ...).
Diagram
Diagram NO_NAMESPACE.tmp#ForeignKeyGroup_ForeignKeyGroup_cardinality_parentOccurences NO_NAMESPACE.tmp#ForeignKeyGroup_ForeignKeyGroup_cardinality_childOccurences
Properties
content complex
minOccurs 0
Model
Children childOccurences, parentOccurences
Instance
<cardinality>
  <parentOccurences>{1,1}</parentOccurences>
  <childOccurences>{1,1}</childOccurences>
</cardinality>
Source
<xs:element name="cardinality" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Cardinality of the relationship between two entities. summary: Cardinality of the relationship between a parent entity and a child entity. description: The cardinality element represents a statement of the relationship between parent and child entities. Cardinality is expressed as the ratio of related parent and child entities. Cardinality 1 to N is a specific form of cardinality in which zero or one parent records are related to a specified number of child records. The cardinality ratio for the parent entity depends on whether the "existence" is mandatory (one or more) or optional (zero to ...).</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="parentOccurences">
        <xs:annotation>
          <xs:documentation>tooltip: Parent portion of a 1 to exactly N cardinality summary: Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. description: The parentOccurences element describes the Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. Value of 0 implies that the "existence" of a child record is optional. Value of 1 implies that the "existence" of a child record is mandatory.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:integer">
            <xs:enumeration value="0"/>
            <xs:enumeration value="1"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="childOccurences" type="CardinalityChildOccurancesType">
        <xs:annotation>
          <xs:documentation>tooltip: Child portion of the cardinality expression summary: Child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many". description: The childOccurences element describes the child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many"</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ForeignKeyGroup / cardinality / parentOccurences
Namespace No namespace
Annotations
tooltip: Parent portion of a 1 to exactly N
                  cardinality

summary: Parent portion of a 1 to exactly N cardinality.
                  May have a value of either 0 or 1.

description: The parentOccurences element describes the
                  Parent portion of a 1 to exactly N cardinality. May have a
                  value of either 0 or 1. Value of 0 implies that the
                  "existence" of a child record is optional.  Value of 1 implies
                  that the "existence" of a child record is
                  mandatory.
Diagram
Diagram
Type restriction of xs:integer
Properties
content simple
Facets
enumeration 0
enumeration 1
Source
<xs:element name="parentOccurences">
  <xs:annotation>
    <xs:documentation>tooltip: Parent portion of a 1 to exactly N cardinality summary: Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. description: The parentOccurences element describes the Parent portion of a 1 to exactly N cardinality. May have a value of either 0 or 1. Value of 0 implies that the "existence" of a child record is optional. Value of 1 implies that the "existence" of a child record is mandatory.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:integer">
      <xs:enumeration value="0"/>
      <xs:enumeration value="1"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ForeignKeyGroup / cardinality / childOccurences
Namespace No namespace
Annotations
tooltip: Child portion of the cardinality
                  expression

summary: Child portion of a cardinality expression
                  Allowed values are positive integers including zero or the
                  string value "many".

description: The childOccurences element describes the
                  child portion of a cardinality expression Allowed values are
                  positive integers including zero or the string value
                  "many"
Diagram
Diagram constraint-2_2_0.tmp#CardinalityChildOccurancesType
Type CardinalityChildOccurancesType
Properties
content simple
Source
<xs:element name="childOccurences" type="CardinalityChildOccurancesType">
  <xs:annotation>
    <xs:documentation>tooltip: Child portion of the cardinality expression summary: Child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many". description: The childOccurences element describes the child portion of a cardinality expression Allowed values are positive integers including zero or the string value "many"</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / joinCondition
Namespace No namespace
Annotations
tooltip: Join Condition

summary: A non primary/foreign key join

description: The joinCondition element describes any join of two
            tables that is not done with a primary/foreign key
            relationship.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintName NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintDescription constraint-2_2_0.tmp#ConstraintBaseGroup NO_NAMESPACE.tmp#ForeignKeyGroup_key NO_NAMESPACE.tmp#ForeignKeyGroup_entityReference NO_NAMESPACE.tmp#ForeignKeyGroup_relationshipType NO_NAMESPACE.tmp#ForeignKeyGroup_cardinality constraint-2_2_0.tmp#ForeignKeyGroup NO_NAMESPACE.tmp#ConstraintType_ConstraintType_joinCondition_referencedKey
Properties
content complex
Model
Children cardinality, constraintDescription, constraintName, entityReference, key, referencedKey, relationshipType
Instance
<joinCondition>
  <constraintName>{1,1}</constraintName>
  <constraintDescription>{0,1}</constraintDescription>
  <key>{1,1}</key>
  <entityReference>{1,1}</entityReference>
  <relationshipType>{0,1}</relationshipType>
  <cardinality>{0,1}</cardinality>
  <referencedKey>{1,1}</referencedKey>
</joinCondition>
Source
<xs:element name="joinCondition">
  <xs:annotation>
    <xs:documentation>tooltip: Join Condition summary: A non primary/foreign key join description: The joinCondition element describes any join of two tables that is not done with a primary/foreign key relationship.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:group ref="ForeignKeyGroup"/>
      <xs:element name="referencedKey">
        <xs:annotation>
          <xs:documentation>tooltip: Key summary: The set of attributes to which a foreign key constraint refers. description: The referencedKey element defines set of attributes to which a foreign key constraint refers. If the key refers to the primary key in the referenced entity, then the "referencedKey" is optional. For a foreign key, the set of attributes must match an identifying key in the referenced entity.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / joinCondition / referencedKey
Namespace No namespace
Annotations
tooltip: Key

summary: The set of attributes to which a foreign key
                  constraint refers.

description: The referencedKey element defines set of
                  attributes to which a foreign key constraint refers. If the
                  key refers to the primary key in the referenced entity, then
                  the "referencedKey" is optional.  For a foreign key, the set
                  of attributes must match an identifying key in the referenced
                  entity.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_ConstraintType_joinCondition_ConstraintType_ConstraintType_joinCondition_referencedKey_attributeReference
Properties
content complex
Model
Children attributeReference
Instance
<referencedKey>
  <attributeReference>{1,unbounded}</attributeReference>
</referencedKey>
Source
<xs:element name="referencedKey">
  <xs:annotation>
    <xs:documentation>tooltip: Key summary: The set of attributes to which a foreign key constraint refers. description: The referencedKey element defines set of attributes to which a foreign key constraint refers. If the key refers to the primary key in the referenced entity, then the "referencedKey" is optional. For a foreign key, the set of attributes must match an identifying key in the referenced entity.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / joinCondition / referencedKey / attributeReference
Namespace No namespace
Annotations
tooltip: Attribute Reference

summary: The identifier of an attribute found
                        in the identified entity

description: The attributeReference element is the
                        identifier of an attribute that can be found in the
                        identified entity. This id will be unique within an
                        entity and specifies that the attribute participates
                        in the key that is being defined.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / notNullConstraint
Namespace No namespace
Annotations
tooltip: Not Null Constraint

summary: A constraint that indicates that no null values
            should be present for an attribute.

description: The notNullConstraint element defines a constraint
            that indicates that no null values should be present for an
            attribute in this entity.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintName NO_NAMESPACE.tmp#ConstraintBaseGroup_constraintDescription constraint-2_2_0.tmp#ConstraintBaseGroup NO_NAMESPACE.tmp#ConstraintType_ConstraintType_notNullConstraint_key
Properties
content complex
Model
Children constraintDescription, constraintName, key
Instance
<notNullConstraint>
  <constraintName>{1,1}</constraintName>
  <constraintDescription>{0,1}</constraintDescription>
  <key>{1,1}</key>
</notNullConstraint>
Source
<xs:element name="notNullConstraint">
  <xs:annotation>
    <xs:documentation>tooltip: Not Null Constraint summary: A constraint that indicates that no null values should be present for an attribute. description: The notNullConstraint element defines a constraint that indicates that no null values should be present for an attribute in this entity.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:group ref="ConstraintBaseGroup"/>
      <xs:element name="key">
        <xs:annotation>
          <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / notNullConstraint / key
Namespace No namespace
Annotations
tooltip: Key

summary: The set of attributes to which this constraint
                  applies.

description: The key element defines the set of attributes
                  to which this constraint applies. For a primary key or a
                  unique key, the set of attributes must be identifying. For a
                  foreign key, the set of attributes must match an identifying
                  key in the referenced entity. For a 'not null' constraint, the
                  key indicates the attribute which should not be
                  null.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_ConstraintType_notNullConstraint_ConstraintType_ConstraintType_notNullConstraint_key_attributeReference
Properties
content complex
Model
Children attributeReference
Instance
<key>
  <attributeReference>{1,unbounded}</attributeReference>
</key>
Source
<xs:element name="key">
  <xs:annotation>
    <xs:documentation>tooltip: Key summary: The set of attributes to which this constraint applies. description: The key element defines the set of attributes to which this constraint applies. For a primary key or a unique key, the set of attributes must be identifying. For a foreign key, the set of attributes must match an identifying key in the referenced entity. For a 'not null' constraint, the key indicates the attribute which should not be null.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element ConstraintType / notNullConstraint / key / attributeReference
Namespace No namespace
Annotations
tooltip: Attribute Reference

summary: The identifier of an attribute found
                        in the identified entity

description: The attributeReference element is the
                        identifier of an attribute that can be found in the
                        identified entity. This id will be unique within an
                        entity and specifies that the attribute participates
                        in the key that is being defined.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="attributeReference" type="res:NonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute Reference summary: The identifier of an attribute found in the identified entity description: The attributeReference element is the identifier of an attribute that can be found in the identified entity. This id will be unique within an entity and specifies that the attribute participates in the key that is being defined.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Element DataTableType / caseSensitive
Namespace No namespace
Annotations
tooltip: Case sensitivity

summary: Specification of text case sensitivity in the
              dataTable.

description: The caseSensitive element
              specifies text case sensitivity of the data in the
              dataTable. The valid values are yes or no. If it is set to
              yes, then values of attributes that differ only in case (e.g.,
              LOW, low) represent distinct values.  If set to no, then values
              of attributes that differ only in case represent the same value.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
Facets
enumeration yes
enumeration no
Source
<xs:element name="caseSensitive" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Case sensitivity summary: Specification of text case sensitivity in the dataTable. description: The caseSensitive element specifies text case sensitivity of the data in the dataTable. The valid values are yes or no. If it is set to yes, then values of attributes that differ only in case (e.g., LOW, low) represent distinct values. If set to no, then values of attributes that differ only in case represent the same value.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="yes"/>
      <xs:enumeration value="no"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataTable.xsd
Element DataTableType / numberOfRecords
Namespace No namespace
Annotations
tooltip: Number of records

summary: The integer count of the number of records in the
              dataTable.

description: The numberOfRecords element contains a count
              of the number of records in the dataTable. This is typically an
              integer value, and only includes records that represent
              observations. It would not include any details of physical
              formatting such as the number of header lines (see eml-physical
              for that information).
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="numberOfRecords" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Number of records summary: The integer count of the number of records in the dataTable. description: The numberOfRecords element contains a count of the number of records in the dataTable. This is typically an integer value, and only includes records that represent observations. It would not include any details of physical formatting such as the number of header lines (see eml-physical for that information).</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataTable.xsd
Element DatasetType / spatialRaster
Namespace No namespace
Annotations
tooltip: spatial raster

summary: The spatialRaster field describes any
                spatial raster images included in this dataset.

description: The spatialRaster field describes any
                spatial raster images included in this dataset.
Diagram
Diagram NO_NAMESPACE.tmp#SpatialRasterType_id NO_NAMESPACE.tmp#SpatialRasterType_system NO_NAMESPACE.tmp#SpatialRasterType_scope NO_NAMESPACE.tmp#EntityGroup_alternateIdentifier NO_NAMESPACE.tmp#EntityGroup_entityName NO_NAMESPACE.tmp#EntityGroup_entityDescription NO_NAMESPACE.tmp#EntityGroup_physical NO_NAMESPACE.tmp#EntityGroup_coverage NO_NAMESPACE.tmp#EntityGroup_methods NO_NAMESPACE.tmp#EntityGroup_additionalInfo NO_NAMESPACE.tmp#EntityGroup_annotation entity-2_2_0.tmp#EntityGroup NO_NAMESPACE.tmp#SpatialRasterType_attributeList NO_NAMESPACE.tmp#SpatialRasterType_constraint NO_NAMESPACE.tmp#SpatialRasterType_spatialReference NO_NAMESPACE.tmp#SpatialRasterType_georeferenceInfo NO_NAMESPACE.tmp#SpatialRasterType_horizontalAccuracy NO_NAMESPACE.tmp#SpatialRasterType_verticalAccuracy NO_NAMESPACE.tmp#SpatialRasterType_cellSizeXDirection NO_NAMESPACE.tmp#SpatialRasterType_cellSizeYDirection NO_NAMESPACE.tmp#SpatialRasterType_numberOfBands NO_NAMESPACE.tmp#SpatialRasterType_rasterOrigin NO_NAMESPACE.tmp#SpatialRasterType_rows NO_NAMESPACE.tmp#SpatialRasterType_columns NO_NAMESPACE.tmp#SpatialRasterType_verticals NO_NAMESPACE.tmp#SpatialRasterType_cellGeometry NO_NAMESPACE.tmp#SpatialRasterType_toneGradation NO_NAMESPACE.tmp#SpatialRasterType_scaleFactor NO_NAMESPACE.tmp#SpatialRasterType_offset NO_NAMESPACE.tmp#SpatialRasterType_imageDescription NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup spatialRaster-2_2_0.tmp#SpatialRasterType
Type SpatialRasterType
Properties
content complex
Model
Children additionalInfo, alternateIdentifier, annotation, attributeList, cellGeometry, cellSizeXDirection, cellSizeYDirection, columns, constraint, coverage, entityDescription, entityName, georeferenceInfo, horizontalAccuracy, imageDescription, methods, numberOfBands, offset, physical, rasterOrigin, references, rows, scaleFactor, spatialReference, toneGradation, verticalAccuracy, verticals
Instance
<spatialRaster id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <entityName>{1,1}</entityName>
  <entityDescription>{0,1}</entityDescription>
  <physical id="" scope="document" system="">{0,unbounded}</physical>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <methods>{0,1}</methods>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <annotation>{0,unbounded}</annotation>
  <attributeList id="">{1,1}</attributeList>
  <constraint id="" scope="document" system="">{0,unbounded}</constraint>
  <spatialReference id="" scope="document" system="">{1,1}</spatialReference>
  <georeferenceInfo>{0,1}</georeferenceInfo>
  <horizontalAccuracy>{1,1}</horizontalAccuracy>
  <verticalAccuracy>{1,1}</verticalAccuracy>
  <cellSizeXDirection>{1,1}</cellSizeXDirection>
  <cellSizeYDirection>{1,1}</cellSizeYDirection>
  <numberOfBands>{1,1}</numberOfBands>
  <rasterOrigin>{1,1}</rasterOrigin>
  <rows>{1,1}</rows>
  <columns>{1,1}</columns>
  <verticals>{1,1}</verticals>
  <cellGeometry>{1,1}</cellGeometry>
  <toneGradation>{0,1}</toneGradation>
  <scaleFactor>{0,1}</scaleFactor>
  <offset>{0,1}</offset>
  <imageDescription>{0,1}</imageDescription>
  <references system="">{1,1}</references>
</spatialRaster>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="spatialRaster" type="sr:SpatialRasterType">
  <xs:annotation>
    <xs:documentation>tooltip: spatial raster summary: The spatialRaster field describes any spatial raster images included in this dataset. description: The spatialRaster field describes any spatial raster images included in this dataset.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element SpatialRasterType / attributeList
Namespace No namespace
Annotations
tooltip: Attribute List

summary: The list of attributes associated with this
              entity.

description: The list of attributes associated with this
              entity.  For more information see the eml-attribute
              module.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeListType_id NO_NAMESPACE.tmp#AttributeListType_attribute NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#AttributeListType
Type AttributeListType
Properties
content complex
Model
Children attribute, references
Instance
<attributeList id="">
  <attribute id="" scope="document" system="">{1,unbounded}</attribute>
  <references system="">{1,1}</references>
</attributeList>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="attributeList" type="att:AttributeListType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / constraint
Namespace No namespace
Annotations
tooltip: Constraint

summary: Description of any relational constraints on
              this entity.

description: Description of any relational constraints on
              this entity.  For more information see the eml-constraint
              module.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_id NO_NAMESPACE.tmp#ConstraintType_system NO_NAMESPACE.tmp#ConstraintType_scope NO_NAMESPACE.tmp#ConstraintType_primaryKey NO_NAMESPACE.tmp#ConstraintType_uniqueKey NO_NAMESPACE.tmp#ConstraintType_checkConstraint NO_NAMESPACE.tmp#ConstraintType_foreignKey NO_NAMESPACE.tmp#ConstraintType_joinCondition NO_NAMESPACE.tmp#ConstraintType_notNullConstraint constraint-2_2_0.tmp#ConstraintType
Type ConstraintType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children checkConstraint, foreignKey, joinCondition, notNullConstraint, primaryKey, uniqueKey
Instance
<constraint id="" scope="document" system="">
  <primaryKey>{1,1}</primaryKey>
  <uniqueKey>{1,1}</uniqueKey>
  <checkConstraint language="">{1,1}</checkConstraint>
  <foreignKey>{1,1}</foreignKey>
  <joinCondition>{1,1}</joinCondition>
  <notNullConstraint>{1,1}</notNullConstraint>
</constraint>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Constraint summary: Description of any relational constraints on this entity. description: Description of any relational constraints on this entity. For more information see the eml-constraint module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / spatialReference
Namespace No namespace
Annotations
tooltip: Spatial Reference

summary: The means by which positional information in this entity is
              related to points on the earth's surface.

description: Spatial Referencing systems define the coordinates used to
              describe horizontal and vertical locations. These are typically either geographic, projected
              planar, or arbitrary planar.
Diagram
Diagram NO_NAMESPACE.tmp#SpatialReferenceType_id NO_NAMESPACE.tmp#SpatialReferenceType_system NO_NAMESPACE.tmp#SpatialReferenceType_scope NO_NAMESPACE.tmp#SpatialReferenceType_horizCoordSysName NO_NAMESPACE.tmp#SpatialReferenceType_horizCoordSysDef NO_NAMESPACE.tmp#SpatialReferenceType_vertCoordSys NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup spatialReference-2_2_0.tmp#SpatialReferenceType
Type SpatialReferenceType
Properties
content complex
Model
Children horizCoordSysDef, horizCoordSysName, references, vertCoordSys
Instance
<spatialReference id="" scope="document" system="">
  <horizCoordSysName>{1,1}</horizCoordSysName>
  <horizCoordSysDef name="">{1,1}</horizCoordSysDef>
  <vertCoordSys>{0,1}</vertCoordSys>
  <references system="">{1,1}</references>
</spatialReference>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="spatialReference" type="spref:SpatialReferenceType">
  <xs:annotation>
    <xs:documentation>tooltip: Spatial Reference summary: The means by which positional information in this entity is related to points on the earth's surface. description: Spatial Referencing systems define the coordinates used to describe horizontal and vertical locations. These are typically either geographic, projected planar, or arbitrary planar.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialReferenceType / horizCoordSysName
Namespace No namespace
Annotations
tooltip: Horizonal Coordinate System Name

summary: The name of a predefined coordinate system

description: The name of a coordinate system for which a definition has been
                provided in the eml-spatialReferenceDictionary.xml file.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration GCS_Abidjan_1987
enumeration GCS_Accra
enumeration GCS_Adindan
enumeration GCS_Afgooye
enumeration GCS_Agadez
enumeration GCS_Ain_el_Abd_1970
enumeration GCS_Arc_1950
enumeration GCS_Arc_1960
enumeration GCS_Ayabelle
enumeration GCS_Beduaram
enumeration GCS_Bissau
enumeration GCS_Camacupa
enumeration GCS_Cape
enumeration GCS_Carthage_Degree
enumeration GCS_Carthage_Paris
enumeration GCS_Carthage
enumeration GCS_Conakry_1905
enumeration GCS_Cote_d_Ivoire
enumeration GCS_Dabola
enumeration GCS_Douala
enumeration GCS_Egypt_1907
enumeration GCS_European_1950
enumeration GCS_European_Libyan_Datum_1979
enumeration GCS_Garoua
enumeration GCS_Hartebeesthoek_1994
enumeration GCS_Kuwait_Oil_Company
enumeration GCS_KUDAMS
enumeration GCS_Leigon
enumeration GCS_Liberia_1964
enumeration GCS_Locodjo_1965
enumeration GCS_Lome
enumeration GCS_Mporaloko
enumeration GCS_Madzansua
enumeration GCS_Mahe_1971
enumeration GCS_Malongo_1987
enumeration GCS_Manoca
enumeration GCS_Massawa
enumeration GCS_Merchich_Degree
enumeration GCS_Merchich
enumeration GCS_Mhast
enumeration GCS_Minna
enumeration GCS_Moznet
enumeration GCS_Nahrwan_1967
enumeration GCS_NGN
enumeration GCS_Nord_Sahara_1959
enumeration GCS_Observatario
enumeration GCS_Oman
enumeration GCS_Palestine_1923
enumeration GCS_PDO_1993
enumeration GCS_Point_58
enumeration GCS_Pointe_Noire
enumeration GCS_Qatar_1948
enumeration GCS_Qatar
enumeration GCS_Schwarzeck
enumeration GCS_Sierra_Leone_1924
enumeration GCS_Sierra_Leone_1960
enumeration GCS_Sierra_Leone_1968
enumeration GCS_South_Yemen
enumeration GCS_Sudan
enumeration GCS_Tananarive_1925_Paris
enumeration GCS_Tananarive_1925
enumeration GCS_Tete
enumeration GCS_Trucial_Coast_1948
enumeration GCS_Voirol_1875_Degree
enumeration GCS_Voirol_1875_Paris
enumeration GCS_Voirol_1875
enumeration GCS_Voirol_Unifie_1960_Degree
enumeration GCS_Voirol_Unifie_1960_Paris
enumeration GCS_Voirol_Unifie_1960
enumeration GCS_Yemen_NGN_1996
enumeration GCS_Yoff
enumeration GCS_Camp_Area
enumeration GCS_Deception_Island
enumeration GCS_Ain_el_Abd_1970
enumeration GCS_Batavia_Jakarta
enumeration GCS_Batavia
enumeration GCS_Beijing_1954
enumeration GCS_Bukit_Rimpah
enumeration GCS_Deir_ez_Zor
enumeration GCS_European_1950_ED77
enumeration GCS_European_1950
enumeration GCS_Everest_def_1962
enumeration GCS_Everest_def_1967
enumeration GCS_Everest_def_1975
enumeration GCS_Everest_Bangladesh
enumeration GCS_Everest_India_Nepal
enumeration GCS_Everest_1830
enumeration GCS_Everest_Modified
enumeration GCS_Fahud
enumeration GCS_FD_1958
enumeration GCS_Gandajika_1970
enumeration GCS_Gunung_Segara
enumeration GCS_Hanoi_1972
enumeration GCS_Herat_North
enumeration GCS_Hong_Kong_1963
enumeration GCS_Hong_Kong_1980
enumeration GCS_Hu_Tzu_Shan
enumeration GCS_Indian_1954
enumeration GCS_Indian_1960
enumeration GCS_Indian_1975
enumeration GCS_Indonesian_1974
enumeration GCS_Israel
enumeration GCS_JGD_2000
enumeration GCS_Kalianpur_1880
enumeration GCS_Kalianpur_1937
enumeration GCS_Kalianpur_1962
enumeration GCS_Kalianpur_1975
enumeration GCS_Kandawala
enumeration GCS_Kertau
enumeration GCS_Korean_Datum_1985
enumeration GCS_Korean_Datum_1995
enumeration GCS_Kuwait_Oil_Company
enumeration GCS_KUDAMS
enumeration GCS_Luzon_1911
enumeration GCS_Makassar_Jakarta
enumeration GCS_Makassar
enumeration GCS_Nahrwan_1967
enumeration GCS_NGN
enumeration GCS_Oman
enumeration GCS_Padang_1884_Jakarta
enumeration GCS_Padang_1884
enumeration GCS_Palestine_1923
enumeration GCS_Pulkovo_1942
enumeration GCS_Pulkovo_1995
enumeration GCS_Qatar_1948
enumeration GCS_Qatar
enumeration GCS_Rassadiran
enumeration GCS_Samboja
enumeration GCS_Segora
enumeration GCS_Serindung
enumeration GCS_South_Asia_Singapore
enumeration GCS_Timbalai_1948
enumeration GCS_Tokyo
enumeration GCS_Trucial_Coast_1948
enumeration GCS_Australian_1966
enumeration GCS_Australian_1984
enumeration GCS_GDA_1994
enumeration GCS_New_Zealand_1949
enumeration GCS_NZGD_2000
enumeration GCS_Amersfoort
enumeration GCS_ATF_Paris
enumeration GCS_Belge_1950_Brussels
enumeration GCS_Belge_1972
enumeration GCS_Bern_1898_Bern
enumeration GCS_Bern_1898
enumeration GCS_Bern_1938
enumeration GCS_CH1903+
enumeration GCS_CH1903
enumeration GCS_Datum_73
enumeration GCS_Datum_Lisboa_Bessel
enumeration GCS_Datum_Lisboa_Bessel
enumeration GCS_Dealul_Piscului_1933
enumeration GCS_Dealul_Piscului_1970
enumeration GCS_Deutsche_Hauptdreiecksnetz
enumeration GCS_Estonia_1937
enumeration GCS_Estonia_1992
enumeration GCS_ETRF_1989
enumeration GCS_European_1979
enumeration GCS_European_1950
enumeration GCS_European_1987
enumeration GCS_Greek_Athens
enumeration GCS_Greek
enumeration GCS_Hermannskogel
enumeration GCS_Hjorsey_1955
enumeration GCS_Hungarian_1972
enumeration GCS_IRENET95
enumeration GCS_KKJ
enumeration GCS_Lisbon_Lisbon
enumeration GCS_Lisbon
enumeration GCS_LKS_1994
enumeration GCS_Madrid_1870_Madrid
enumeration GCS_MGI_Ferro
enumeration GCS_MGI
enumeration GCS_Monte_Mario_Rome
enumeration GCS_Monte_Mario
enumeration GCS_NGO_1948_Oslo
enumeration GCS_NGO_1948
enumeration GCS_Nord_de_Guerre_Paris
enumeration GCS_NTF
enumeration GCS_NTF_Paris
enumeration GCS_OS_SN_1980
enumeration GCS_OSGB_1936
enumeration GCS_OSGB_1970_SN
enumeration GCS_Pulkovo_1942
enumeration GCS_Pulkovo_1995
enumeration GCS_Qornoq
enumeration GCS_Belge_1950
enumeration GCS_Belge_1972
enumeration GCS_RGF_1993
enumeration GCS_RT_1990
enumeration GCS_RT38_Stockholm
enumeration GCS_RT38
enumeration GCS_S42_Hungary
enumeration GCS_S_JTSK
enumeration GCS_Swiss_TRF_1995
enumeration GCS_TM65
enumeration GCS_TM75
enumeration GCS_Alaskan_Islands
enumeration GCS_American_Samoa_1962
enumeration GCS_ATS_1977
enumeration GCS_Barbados
enumeration GCS_Bermuda_1957
enumeration GCS_Cape_Canaveral
enumeration GCS_Guam_1963
enumeration GCS_Jamaica_1875
enumeration GCS_Jamaica_1969
enumeration GCS_NAD_1927_CGQ77
enumeration GCS_NAD_1927_Definition_1976
enumeration GCS_North_American_Michigan
enumeration GCS_North_American_1983_CSRS98
enumeration GCS_North_American_1983_HARN
enumeration GCS_North_American_1927
enumeration GCS_North_American_1983
enumeration GCS_Old_Hawaiian
enumeration GCS_Puerto_Rico
enumeration GCS_Qornoq
enumeration GCS_St_George_Island
enumeration GCS_St_Lawrence_Island
enumeration GCS_St_Paul_Island
enumeration GCS_Alaskan_Islands
enumeration GCS_American_Samoa_1962
enumeration GCS_Anguilla_1957
enumeration GCS_Anna_1_1965
enumeration GCS_Antigua_1943
enumeration GCS_Ascension_Island_1958
enumeration GCS_Beacon_E_1945
enumeration GCS_DOS_71_4
enumeration GCS_Astro_1952
enumeration GCS_Bab_South
enumeration GCS_Barbados_1938
enumeration GCS_Barbados
enumeration GCS_Bellevue_IGN
enumeration GCS_Bermuda_1957
enumeration GCS_Canton_1966
enumeration GCS_Chatham_Island_1971
enumeration GCS_Dominica_1945
enumeration GCS_DOS_1968
enumeration GCS_Easter_Island_1967
enumeration GCS_Fort_Thomas_1955
enumeration GCS_Gan_1970
enumeration GCS_Graciosa_Base_SW_1948
enumeration GCS_Grenada_1953
enumeration GCS_Guam_1963
enumeration GCS_GUX_1
enumeration GCS_Hjorsey_1955
enumeration GCS_ISTS_061_1968
enumeration GCS_ISTS_073_1969
enumeration GCS_Jamaica_1875
enumeration GCS_Jamaica_1969
enumeration GCS_Johnston_Island_1961
enumeration GCS_Kerguelen_Island_1949
enumeration GCS_Kusaie_1951
enumeration GCS_LC5_1961
enumeration GCS_Mahe_1971
enumeration GCS_Majuro
enumeration GCS_Midway_1961
enumeration GCS_Montserrat_1958
enumeration GCS_Observ_Meteorologico_1939
enumeration GCS_Old_Hawaiian
enumeration GCS_Pico_de_Las_Nieves
enumeration GCS_Pitcairn_1967
enumeration GCS_Pohnpei
enumeration GCS_Porto_Santo_1936
enumeration GCS_Puerto_Rico
enumeration GCS_Reunion
enumeration GCS_Santo_DOS_1965
enumeration GCS_Sao_Braz
enumeration GCS_Sapper_Hill_1943
enumeration GCS_Selvagem_Grande_1938
enumeration GCS_St_Kitts_1955
enumeration GCS_St_Lucia_1955
enumeration GCS_St_Vincent_1945
enumeration GCS_Tern_Island_1961
enumeration GCS_Tristan_1968
enumeration GCS_Viti_Levu_1916
enumeration GCS_Wake_Island_1952
enumeration GCS_Wake_Eniwetok_1960
enumeration GCS_Aratu
enumeration GCS_Bogota_Bogota
enumeration GCS_Bogota
enumeration GCS_Campo_Inchauspe
enumeration GCS_Chos_Malal_1914
enumeration GCS_Chua
enumeration GCS_Corrego_Alegre
enumeration GCS_Guyane_Francaise
enumeration GCS_Hito_XVIII_1963
enumeration GCS_La_Canoa
enumeration GCS_Lake
enumeration GCS_Loma_Quintana
enumeration GCS_Mount_Dillon
enumeration GCS_Naparima_1955
enumeration GCS_Naparima_1972
enumeration GCS_Pampa_del_Castillo
enumeration GCS_POSGAR
enumeration GCS_REGVEN
enumeration GCS_Sapper_Hill_1943
enumeration GCS_SIRGAS
enumeration GCS_South_American_1969
enumeration GCS_Trinidad_1903
enumeration GCS_Yacare
enumeration GCS_Zanderij
enumeration GCS_Airy_1830
enumeration GCS_Airy_Modified
enumeration GCS_Australian
enumeration GCS_Sphere_ARC_INFO
enumeration GCS_Sphere
enumeration GCS_ATS_1977
enumeration GCS_Bessel_1841
enumeration GCS_Bessel_Modified
enumeration GCS_Bessel_Namibia
enumeration GCS_Clarke_1858
enumeration GCS_Clarke_1866_Michigan
enumeration GCS_Clarke_1866
enumeration GCS_Clarke_1880_Arc
enumeration GCS_Clarke_1880_Benoit
enumeration GCS_Clarke_1880_IGN
enumeration GCS_Clarke_1880_RGS
enumeration GCS_Clarke_1880_SGA
enumeration GCS_Clarke_1880
enumeration GCS_Everest_def_1967
enumeration GCS_Everest_def_1975
enumeration GCS_Everest_1830
enumeration GCS_Everest_Modified_1969
enumeration GCS_Everest_Modified
enumeration GCS_Fischer_1960
enumeration GCS_Fischer_1968
enumeration GCS_Fischer_Modified
enumeration GCS_GEM_10C
enumeration GCS_GRS_1967
enumeration GCS_GRS_1980
enumeration GCS_Helmert_1906
enumeration GCS_Hough_1960
enumeration GCS_Indonesian
enumeration GCS_International_1924
enumeration GCS_International_1967
enumeration GCS_Krasovsky_1940
enumeration GCS_OSU_86F
enumeration GCS_OSU_91A
enumeration GCS_Plessis_1817
enumeration GCS_Struve_1860
enumeration GCS_NWL_9D
enumeration GCS_Walbeck
enumeration GCS_War_Office
enumeration GCS_WGS_1966
enumeration GCS_NSWC_9Z_2
enumeration GCS_WGS_1966
enumeration GCS_WGS_1972_BE
enumeration GCS_WGS_1972
enumeration GCS_WGS_1984
enumeration Africa_Albers_Equal_Area_Conic
enumeration Africa_Equidistant_Conic
enumeration Africa_Lambert_Conformal_Conic
enumeration Africa_Sinusoidal
enumeration Asia_Lambert_Conformal_Conic
enumeration Asia_North_Albers_Equal_Area_Conic
enumeration Asia_North_Equidistant_Conic
enumeration Asia_North_Lambert_Conformal_Conic
enumeration Asia_South_Albers_Equal_Area_Conic
enumeration Asia_South_Equidistant_Conic
enumeration Asia_South_Lambert_Conformal_Conic
enumeration Europe_Albers_Equal_Area_Conic
enumeration Europe_Equidistant_Conic
enumeration Europe_Lambert_Conformal_Conic
enumeration Alaska_Albers_Equal_Area_Conic
enumeration Canada_Albers_Equal_Area_Conic
enumeration Canada_Lambert_Conformal_Conic
enumeration Hawaii_Albers_Equal_Area_Conic
enumeration North_America_Albers_Equal_Area_Conic
enumeration North_America_Equidistant_Conic
enumeration North_America_Lambert_Conformal_Conic
enumeration USA_Contiguous_Albers_Equal_Area_Conic_USGS_version
enumeration USA_Contiguous_Albers_Equal_Area_Conic
enumeration USA_Contiguous_Equidistant_Conic
enumeration USA_Contiguous_Lambert_Conformal_Conic
enumeration South_America_Albers_Equal_Area_Conic
enumeration South_America_Equidistant_Conic
enumeration South_America_Lambert_Conformal_Conic
enumeration Beijing_1954_GK_Zone_13
enumeration Beijing_1954_GK_Zone_13N
enumeration Beijing_1954_GK_Zone_14
enumeration Beijing_1954_GK_Zone_14N
enumeration Beijing_1954_GK_Zone_15
enumeration Beijing_1954_GK_Zone_15N
enumeration Beijing_1954_GK_Zone_16
enumeration Beijing_1954_GK_Zone_16N
enumeration Beijing_1954_GK_Zone_17
enumeration Beijing_1954_GK_Zone_17N
enumeration Beijing_1954_GK_Zone_18
enumeration Beijing_1954_GK_Zone_18N
enumeration Beijing_1954_GK_Zone_19
enumeration Beijing_1954_GK_Zone_19N
enumeration Beijing_1954_GK_Zone_20
enumeration Beijing_1954_GK_Zone_20N
enumeration Beijing_1954_GK_Zone_21
enumeration Beijing_1954_GK_Zone_21N
enumeration Beijing_1954_GK_Zone_22
enumeration Beijing_1954_GK_Zone_22N
enumeration Beijing_1954_GK_Zone_23
enumeration Beijing_1954_GK_Zone_23N
enumeration Hanoi_1972_GK_Zone_18
enumeration Hanoi_1972_GK_Zone_19
enumeration South_Yemen_GK_Zone_8
enumeration South_Yemen_GK_Zone_9
enumeration Pulkovo_1942_GK_Zone_10
enumeration Pulkovo_1942_GK_Zone_10N
enumeration Pulkovo_1942_GK_Zone_11
enumeration Pulkovo_1942_GK_Zone_11N
enumeration Pulkovo_1942_GK_Zone_12
enumeration Pulkovo_1942_GK_Zone_12N
enumeration Pulkovo_1942_GK_Zone_13
enumeration Pulkovo_1942_GK_Zone_13N
enumeration Pulkovo_1942_GK_Zone_14
enumeration Pulkovo_1942_GK_Zone_14N
enumeration Pulkovo_1942_GK_Zone_15
enumeration Pulkovo_1942_GK_Zone_15N
enumeration Pulkovo_1942_GK_Zone_16
enumeration Pulkovo_1942_GK_Zone_16N
enumeration Pulkovo_1942_GK_Zone_17
enumeration Pulkovo_1942_GK_Zone_17N
enumeration Pulkovo_1942_GK_Zone_18
enumeration Pulkovo_1942_GK_Zone_18N
enumeration Pulkovo_1942_GK_Zone_19
enumeration Pulkovo_1942_GK_Zone_19N
enumeration Pulkovo_1942_GK_Zone_2
enumeration Pulkovo_1942_GK_Zone_20
enumeration Pulkovo_1942_GK_Zone_20N
enumeration Pulkovo_1942_GK_Zone_21
enumeration Pulkovo_1942_GK_Zone_21N
enumeration Pulkovo_1942_GK_Zone_22
enumeration Pulkovo_1942_GK_Zone_22N
enumeration Pulkovo_1942_GK_Zone_23
enumeration Pulkovo_1942_GK_Zone_23N
enumeration Pulkovo_1942_GK_Zone_24
enumeration Pulkovo_1942_GK_Zone_24N
enumeration Pulkovo_1942_GK_Zone_25
enumeration Pulkovo_1942_GK_Zone_25N
enumeration Pulkovo_1942_GK_Zone_26
enumeration Pulkovo_1942_GK_Zone_26N
enumeration Pulkovo_1942_GK_Zone_27
enumeration Pulkovo_1942_GK_Zone_27N
enumeration Pulkovo_1942_GK_Zone_28
enumeration Pulkovo_1942_GK_Zone_28N
enumeration Pulkovo_1942_GK_Zone_29
enumeration Pulkovo_1942_GK_Zone_29N
enumeration Pulkovo_1942_GK_Zone_2N
enumeration Pulkovo_1942_GK_Zone_3
enumeration Pulkovo_1942_GK_Zone_30
enumeration Pulkovo_1942_GK_Zone_30N
enumeration Pulkovo_1942_GK_Zone_31
enumeration Pulkovo_1942_GK_Zone_31N
enumeration Pulkovo_1942_GK_Zone_32
enumeration Pulkovo_1942_GK_Zone_32N
enumeration Pulkovo_1942_GK_Zone_3N
enumeration Pulkovo_1942_GK_Zone_4
enumeration Pulkovo_1942_GK_Zone_4N
enumeration Pulkovo_1942_GK_Zone_5
enumeration Pulkovo_1942_GK_Zone_5N
enumeration Pulkovo_1942_GK_Zone_6
enumeration Pulkovo_1942_GK_Zone_6N
enumeration Pulkovo_1942_GK_Zone_7
enumeration Pulkovo_1942_GK_Zone_7N
enumeration Pulkovo_1942_GK_Zone_8
enumeration Pulkovo_1942_GK_Zone_8N
enumeration Pulkovo_1942_GK_Zone_9
enumeration Pulkovo_1942_GK_Zone_9N
enumeration Pulkovo_1995_GK_Zone_10
enumeration Pulkovo_1995_GK_Zone_10N
enumeration Pulkovo_1995_GK_Zone_11
enumeration Pulkovo_1995_GK_Zone_11N
enumeration Pulkovo_1995_GK_Zone_12
enumeration Pulkovo_1995_GK_Zone_12N
enumeration Pulkovo_1995_GK_Zone_13
enumeration Pulkovo_1995_GK_Zone_13N
enumeration Pulkovo_1995_GK_Zone_14
enumeration Pulkovo_1995_GK_Zone_14N
enumeration Pulkovo_1995_GK_Zone_15
enumeration Pulkovo_1995_GK_Zone_15N
enumeration Pulkovo_1995_GK_Zone_16
enumeration Pulkovo_1995_GK_Zone_16N
enumeration Pulkovo_1995_GK_Zone_17
enumeration Pulkovo_1995_GK_Zone_17N
enumeration Pulkovo_1995_GK_Zone_18
enumeration Pulkovo_1995_GK_Zone_18N
enumeration Pulkovo_1995_GK_Zone_19
enumeration Pulkovo_1995_GK_Zone_19N
enumeration Pulkovo_1995_GK_Zone_2
enumeration Pulkovo_1995_GK_Zone_20
enumeration Pulkovo_1995_GK_Zone_20N
enumeration Pulkovo_1995_GK_Zone_21
enumeration Pulkovo_1995_GK_Zone_21N
enumeration Pulkovo_1995_GK_Zone_22
enumeration Pulkovo_1995_GK_Zone_22N
enumeration Pulkovo_1995_GK_Zone_23
enumeration Pulkovo_1995_GK_Zone_23N
enumeration Pulkovo_1995_GK_Zone_24
enumeration Pulkovo_1995_GK_Zone_24N
enumeration Pulkovo_1995_GK_Zone_25
enumeration Pulkovo_1995_GK_Zone_25N
enumeration Pulkovo_1995_GK_Zone_26
enumeration Pulkovo_1995_GK_Zone_26N
enumeration Pulkovo_1995_GK_Zone_27
enumeration Pulkovo_1995_GK_Zone_27N
enumeration Pulkovo_1995_GK_Zone_28
enumeration Pulkovo_1995_GK_Zone_28N
enumeration Pulkovo_1995_GK_Zone_29
enumeration Pulkovo_1995_GK_Zone_29N
enumeration Pulkovo_1995_GK_Zone_2N
enumeration Pulkovo_1995_GK_Zone_3
enumeration Pulkovo_1995_GK_Zone_30
enumeration Pulkovo_1995_GK_Zone_30N
enumeration Pulkovo_1995_GK_Zone_31
enumeration Pulkovo_1995_GK_Zone_31N
enumeration Pulkovo_1995_GK_Zone_32
enumeration Pulkovo_1995_GK_Zone_32N
enumeration Pulkovo_1995_GK_Zone_3N
enumeration Pulkovo_1995_GK_Zone_4
enumeration Pulkovo_1995_GK_Zone_4N
enumeration Pulkovo_1995_GK_Zone_5
enumeration Pulkovo_1995_GK_Zone_5N
enumeration Pulkovo_1995_GK_Zone_6
enumeration Pulkovo_1995_GK_Zone_6N
enumeration Pulkovo_1995_GK_Zone_7
enumeration Pulkovo_1995_GK_Zone_7N
enumeration Pulkovo_1995_GK_Zone_8
enumeration Pulkovo_1995_GK_Zone_8N
enumeration Pulkovo_1995_GK_Zone_9
enumeration Pulkovo_1995_GK_Zone_9N
enumeration Abidjan_1987_TM_5_NW
enumeration Accra_Ghana_Grid
enumeration Accra_TM_1_NW
enumeration Samoa_1962_Samoa_Lambert
enumeration Anguilla_1957_British_West_Indies_Grid
enumeration Antigua_1943_British_West_Indies_Grid
enumeration Argentina_Zone_1
enumeration Argentina_Zone_2
enumeration Argentina_Zone_3
enumeration Argentina_Zone_4
enumeration Argentina_Zone_5
enumeration Argentina_Zone_6
enumeration Argentina_Zone_7
enumeration AGD_1966_AMG_Zone_48
enumeration AGD_1966_AMG_Zone_49
enumeration AGD_1966_AMG_Zone_50
enumeration AGD_1966_AMG_Zone_51
enumeration AGD_1966_AMG_Zone_52
enumeration AGD_1966_AMG_Zone_53
enumeration AGD_1966_AMG_Zone_54
enumeration AGD_1966_AMG_Zone_55
enumeration AGD_1966_AMG_Zone_56
enumeration AGD_1966_AMG_Zone_57
enumeration AGD_1966_AMG_Zone_58
enumeration AGD_1966_VICGRID
enumeration AGD_1984_AMG_Zone_48
enumeration AGD_1984_AMG_Zone_49
enumeration AGD_1984_AMG_Zone_50
enumeration AGD_1984_AMG_Zone_51
enumeration AGD_1984_AMG_Zone_52
enumeration AGD_1984_AMG_Zone_53
enumeration AGD_1984_AMG_Zone_54
enumeration AGD_1984_AMG_Zone_55
enumeration AGD_1984_AMG_Zone_56
enumeration AGD_1984_AMG_Zone_57
enumeration AGD_1984_AMG_Zone_58
enumeration GDA_1994_MGA_Zone_48
enumeration GDA_1994_MGA_Zone_49
enumeration GDA_1994_MGA_Zone_50
enumeration GDA_1994_MGA_Zone_51
enumeration GDA_1994_MGA_Zone_52
enumeration GDA_1994_MGA_Zone_53
enumeration GDA_1994_MGA_Zone_54
enumeration GDA_1994_MGA_Zone_55
enumeration GDA_1994_MGA_Zone_56
enumeration GDA_1994_MGA_Zone_57
enumeration GDA_1994_MGA_Zone_58
enumeration GDA_1994_South_Australia_Lambert
enumeration GDA_1994_VICGRID94
enumeration Austria_Central_Zone
enumeration Austria_East_Zone
enumeration Austria_West_Zone
enumeration Bahrain_State_Grid
enumeration Barbados_1938_Barbados_Grid
enumeration Barbados_1938_British_West_Indies_Grid
enumeration Belge_Lambert_1950
enumeration Belge_Lambert_1972
enumeration Bern_1898_Bern_LV03C
enumeration British_National_Grid
enumeration Camacupa_TM_11_30_SE
enumeration Camacupa_TM_12_SE
enumeration ATS_1977_MTM_4_Nova_Scotia
enumeration ATS_1977_MTM_5_Nova_Scotia
enumeration ATS_1977_New_Brunswick_Stereographic
enumeration NAD_1927_10TM_AEP_Forest
enumeration NAD_1927_10TM_AEP_Resource
enumeration NAD_1927_3TM_111
enumeration NAD_1927_3TM_114
enumeration NAD_1927_3TM_117
enumeration NAD_1927_3TM_120
enumeration NAD_1927_CGQ77_MTM_10_SCoPQ
enumeration NAD_1927_CGQ77_MTM_2_SCoPQ
enumeration NAD_1927_CGQ77_MTM_3_SCoPQ
enumeration NAD_1927_CGQ77_MTM_4_SCoPQ
enumeration NAD_1927_CGQ77_MTM_5_SCoPQ
enumeration NAD_1927_CGQ77_MTM_6_SCoPQ
enumeration NAD_1927_CGQ77_MTM_7_SCoPQ
enumeration NAD_1927_CGQ77_MTM_8_SCoPQ
enumeration NAD_1927_CGQ77_MTM_9_SCoPQ
enumeration NAD_1927_CGQ77_Quebec_Lambert
enumeration NAD_1927_CGQ77_UTM_Zone_17N
enumeration NAD_1927_CGQ77_UTM_Zone_18N
enumeration NAD_1927_CGQ77_UTM_Zone_19N
enumeration NAD_1927_CGQ77_UTM_Zone_20N
enumeration NAD_1927_CGQ77_UTM_Zone_21N
enumeration NAD_1927_DEF_1976_MTM_10
enumeration NAD_1927_DEF_1976_MTM_11
enumeration NAD_1927_DEF_1976_MTM_12
enumeration NAD_1927_DEF_1976_MTM_13
enumeration NAD_1927_DEF_1976_MTM_14
enumeration NAD_1927_DEF_1976_MTM_15
enumeration NAD_1927_DEF_1976_MTM_16
enumeration NAD_1927_DEF_1976_MTM_17
enumeration NAD_1927_DEF_1976_MTM_8
enumeration NAD_1927_DEF_1976_MTM_9
enumeration NAD_1927_DEF_1976_UTM_Zone_15N
enumeration NAD_1927_DEF_1976_UTM_Zone_16N
enumeration NAD_1927_DEF_1976_UTM_Zone_17N
enumeration NAD_1927_DEF_1976_UTM_Zone_18N
enumeration NAD_1927_MTM_1
enumeration NAD_1927_MTM_2
enumeration NAD_1927_MTM_3
enumeration NAD_1927_MTM_4
enumeration NAD_1927_MTM_5
enumeration NAD_1927_MTM_6
enumeration NAD_1927_Quebec_Lambert
enumeration NAD_1983_10TM_AEP_Forest
enumeration NAD_1983_10TM_AEP_Resource
enumeration NAD_1983_3TM_111
enumeration NAD_1983_3TM_114
enumeration NAD_1983_3TM_117
enumeration NAD_1983_3TM_120
enumeration NAD_1983_BC_Environment_Albers
enumeration NAD_1983_CRS98_MTM_10
enumeration NAD_1983_CSRS98_MTM_2_SCoPQ
enumeration NAD_1983_CRS98_MTM_3
enumeration NAD_1983_CRS98_MTM_4
enumeration NAD_1983_CRS98_MTM_5
enumeration NAD_1983_CRS98_MTM_6
enumeration NAD_1983_CRS98_MTM_7
enumeration NAD_1983_CRS98_MTM_8
enumeration NAD_1983_CRS98_MTM_9
enumeration NAD_1983_CSRS98_New_Brunswick_Stereographic
enumeration NAD_1983_CSRS98_Prince_Edward_Island
enumeration NAD_1983_CSRS98_UTM_Zone_21N
enumeration NAD_1983_CSRS98_UTM_Zone_11N
enumeration NAD_1983_CSRS98_UTM_Zone_12N
enumeration NAD_1983_CSRS98_UTM_Zone_13N
enumeration NAD_1983_CSRS98_UTM_Zone_17N
enumeration NAD_1983_CSRS98_UTM_Zone_18N
enumeration NAD_1983_CSRS98_UTM_Zone_19N
enumeration NAD_1983_CSRS98_UTM_Zone_20N
enumeration NAD_1983_MTM_1
enumeration NAD_1983_MTM_10
enumeration NAD_1983_MTM_11
enumeration NAD_1983_MTM_12
enumeration NAD_1983_MTM_13
enumeration NAD_1983_MTM_14
enumeration NAD_1983_MTM_15
enumeration NAD_1983_MTM_16
enumeration NAD_1983_MTM_17
enumeration NAD_1983_MTM_2_SCoPQ
enumeration NAD_1983_MTM_2
enumeration NAD_1983_MTM_3
enumeration NAD_1983_MTM_4
enumeration NAD_1983_MTM_5
enumeration NAD_1983_MTM_6
enumeration NAD_1983_MTM_7
enumeration NAD_1983_MTM_8
enumeration NAD_1983_MTM_9
enumeration NAD_1983_Quebec_Lambert
enumeration Prince_Edward_Island_Stereographic
enumeration Carthage_TM_11_NE
enumeration Centre_France
enumeration CH1903_LV03
enumeration CH1903+_LV95
enumeration Chos_Malal_1914_Argentina_2
enumeration Colombia_Bogota_Zone
enumeration Colombia_East_Central_Zone
enumeration Colombia_East_Zone
enumeration Colombia_West_Zone
enumeration Corse
enumeration Datum_73_Hayford_Gauss_IGeoE
enumeration Datum_73_Hayford_Gauss_IPCC
enumeration Deir_ez_Zor_Levant_Stereographic
enumeration Deir_ez_Zor_Levant_Zone
enumeration Deir_ez_Zor_Syria_Lambert
enumeration DHDN_3_Degree_Gauss_Zone_1
enumeration DHDN_3_Degree_Gauss_Zone_2
enumeration DHDN_3_Degree_Gauss_Zone_3
enumeration DHDN_3_Degree_Gauss_Zone_4
enumeration DHDN_3_Degree_Gauss_Zone_5
enumeration Dominica_1945_British_West_Indies_Grid
enumeration ED_1950_TM_0_N
enumeration ED_1950_TM_5_NE
enumeration Egypt_Blue_Belt
enumeration Egypt_Extended_Purple_Belt
enumeration Egypt_Purple_Belt
enumeration Egypt_Red_Belt
enumeration ELD_1979_Libya_10
enumeration ELD_1979_Libya_11
enumeration ELD_1979_Libya_12
enumeration ELD_1979_Libya_13
enumeration ELD_1979_Libya_5
enumeration ELD_1979_Libya_6
enumeration ELD_1979_Libya_7
enumeration ELD_1979_Libya_8
enumeration ELD_1979_Libya_9
enumeration ELD_1979_TM_12_NE
enumeration Estonian_Coordinate_System_of_1992
enumeration ETRF_1989_TM_Baltic_1993
enumeration FD_1958_Iraq
enumeration Finland_Zone_1
enumeration Finland_Zone_2
enumeration Finland_Zone_3
enumeration Finland_Zone_4
enumeration France_I
enumeration France_II
enumeration France_III
enumeration France_IV
enumeration Germany_Zone_1
enumeration Germany_Zone_2
enumeration Germany_Zone_3
enumeration Germany_Zone_4
enumeration Germany_Zone_5
enumeration Ghana_Metre_Grid
enumeration Greek_Grid
enumeration Grenada_1953_British_West_Indies_Grid
enumeration Hanoi_1972_GK_106_NE
enumeration HD_1972_Egyseges_Orszagos_Vetuleti
enumeration Hito_XVIII_1963_Argentina_2
enumeration Hong_Kong_1980_Grid
enumeration Indian_1960_TM_106NE
enumeration Kalianpur_1880_India_Zone_0
enumeration Kalianpur_1880_India_Zone_I
enumeration Kalianpur_1880_India_Zone_IIa
enumeration Kalianpur_1880_India_Zone_IIb
enumeration Kalianpur_1880_India_Zone_III
enumeration Kalianpur_1880_India_Zone_IV
enumeration Kalianpur_1937_India_Zone_IIb
enumeration Kalianpur_1937_UTM_Zone_45N
enumeration Kalianpur_1937_UTM_Zone_46N
enumeration Kalianpur_1962_India_Zone_I
enumeration Kalianpur_1962_India_Zone_IIa
enumeration Kalianpur_1962_UTM_Zone_41N
enumeration Kalianpur_1962_UTM_Zone_42N
enumeration Kalianpur_1962_UTM_Zone_43N
enumeration Kalianpur_1975_India_Zone_I
enumeration Kalianpur_1975_India_Zone_IIa
enumeration Kalianpur_1975_India_Zone_IIb
enumeration Kalianpur_1975_India_Zone_III
enumeration Kalianpur_1975_India_Zone_IV
enumeration Kalianpur_1975_UTM_Zone_42N
enumeration Kalianpur_1975_UTM_Zone_43N
enumeration Kalianpur_1975_UTM_Zone_44N
enumeration Kalianpur_1975_UTM_Zone_45N
enumeration Kalianpur_1975_UTM_Zone_46N
enumeration Kalianpur_1975_UTM_Zone_47N
enumeration IRENET95_IRISH_Transverse_Mercator
enumeration Irish_National_Grid
enumeration Israel_TM_Grid
enumeration Jamaica_1875_Old_Grid
enumeration Jamaica_Grid
enumeration Japan_Zone_1
enumeration Japan_Zone_10
enumeration Japan_Zone_11
enumeration Japan_Zone_12
enumeration Japan_Zone_13
enumeration Japan_Zone_14
enumeration Japan_Zone_15
enumeration Japan_Zone_16
enumeration Japan_Zone_17
enumeration Japan_Zone_18
enumeration Japan_Zone_19
enumeration Japan_Zone_2
enumeration Japan_Zone_3
enumeration Japan_Zone_4
enumeration Japan_Zone_5
enumeration Japan_Zone_6
enumeration Japan_Zone_7
enumeration Japan_Zone_8
enumeration Japan_Zone_9
enumeration Kertau_Singapore_Grid
enumeration KOC_Lambert
enumeration Korean_1985_Korea_Central_Belt
enumeration Korean_1985_Korea_East_Belt
enumeration Korean_1985_Korea_West_Belt
enumeration KUDAMS_KTM
enumeration KOC_Lambert
enumeration KUDAMS_KTM
enumeration Lake_Maracaibo_Grid_M1
enumeration Lake_Maracaibo_Grid_M3
enumeration Lake_Maracaibo_Grid
enumeration Lake_Maracaibo_La_Rosa_Grid
enumeration Lietuvos_Koordinaciu_Sistema
enumeration Lisboa_Bessel_Bonne
enumeration Lisboa_Hayford_Gauss_IGeoE
enumeration Lisboa_Hayford_Gauss_IPCC
enumeration Locodjo_1965_TM_5_NW
enumeration Madrid_1870_Madrid_Spain
enumeration MGI_3_Degree_Gauss_Zone_5
enumeration MGI_3_Degree_Gauss_Zone_6
enumeration MGI_3_Degree_Gauss_Zone_7
enumeration MGI_3_Degree_Gauss_Zone_8
enumeration MGI_Austria_Lambert
enumeration MGI_Balkans_5
enumeration MGI_Balkans_6
enumeration MGI_Balkans_8
enumeration MGI_Balkans_8
enumeration MGI_M28
enumeration MGI_M31
enumeration MGI_M34
enumeration Monte_Mario_Rome_Italy_1
enumeration Monte_Mario_Rome_Italy_2
enumeration Monte_Mario_Italy_1
enumeration Monte_Mario_Italy_2
enumeration Montserrat_1958_British_West_Indies_Grid
enumeration Mount_Dillon_Tobago_Grid
enumeration NAD_1927_Cuba_Norte
enumeration NAD_1927_Cuba_Sur
enumeration NAD_1927_Guatemala_Norte
enumeration NAD_1927_Guatemala_Sur
enumeration NAD_1927_Michigan_GeoRef_Meters
enumeration NAD_1927_Michigan_GeoRef_Feet_US
enumeration NAD_1983_HARN_Guam_Map_Grid
enumeration NAD_1983_Michigan_GeoRef_Meters
enumeration NAD_1983_Michigan_GeoRef_Feet_US
enumeration GD_1949_New_Zealand_Map_Grid
enumeration New_Zealand_North_Island
enumeration New_Zealand_South_Island
enumeration NZGD_1949_Amuri_Circuit
enumeration NZGD_1949_Bay_of_Plenty_Circuit
enumeration NZGD_1949_Bluff_Circuit
enumeration NZGD_1949_Buller_Circuit
enumeration NZGD_1949_Collingwood_Circuit
enumeration NZGD_1949_Gawler_Circuit
enumeration NZGD_1949_Grey_Circuit
enumeration NZGD_1949_Hawkes_Bay_Circuit
enumeration NZGD_1949_Hokitika_Circuit
enumeration NZGD_1949_Jacksons_Bay_Circuit
enumeration NZGD_1949_Karamea_Circuit
enumeration NZGD_1949_Lindis_Peak_Circuit
enumeration NZGD_1949_Marlborough_Circuit
enumeration NZGD_1949_Mount_Eden_Circuit
enumeration NZGD_1949_Mount_Nicholas_Circuit
enumeration NZGD_1949_Mount_Pleasant_Circuit
enumeration NZGD_1949_Mount_York_Circuit
enumeration NZGD_1949_Nelson_Circuit
enumeration NZGD_1949_North_Taieri_Circuit
enumeration NZGD_1949_Observation_Point_Circuit
enumeration NZGD_1949_Okarito_Circuit
enumeration NZGD_1949_Poverty_Bay_Circuit
enumeration NZGD_1949_Taranaki_Circuit
enumeration NZGD_1949_Timaru_Circuit
enumeration NZGD_1949_Tuhirangi_Circuit
enumeration NZGD_1949_UTM_Zone_58S
enumeration NZGD_1949_UTM_Zone_59S
enumeration NZGD_1949_UTM_Zone_60S
enumeration NZGD_1949_Wairarapa_Circuit
enumeration NZGD_1949_Wanganui_Circuit
enumeration NZGD_1949_Wellington_Circuit
enumeration NZGD_2000_Amuri_Circuit
enumeration NZGD_2000_Bay_of_Plenty_Circuit
enumeration NZGD_2000_Bluff_Circuit
enumeration NZGD_2000_Buller_Circuit
enumeration NZGD_2000_Collingwood_Circuit
enumeration NZGD_2000_Gawler_Circuit
enumeration NZGD_2000_Grey_Circuit
enumeration NZGD_2000_Hawkes_Bay_Circuit
enumeration NZGD_2000_Hokitika_Circuit
enumeration NZGD_2000_Jacksons_Bay_Circuit
enumeration NZGD_2000_Karamea_Circuit
enumeration NZGD_2000_Lindis_Peak_Circuit
enumeration NZGD_2000_Marlborough_Circuit
enumeration NZGD_2000_Mount_Eden_Circuit
enumeration NZGD_2000_Mount_Nicholas_Circuit
enumeration NZGD_2000_Mount_Pleasant_Circuit
enumeration NZGD_2000_Mount_York_Circuit
enumeration NZGD_2000_Nelson_Circuit
enumeration NZGD_2000_North_Taieri_Circuit
enumeration NZGD_2000_Observation_Point_Circuit
enumeration NZGD_2000_Okarito_Circuit
enumeration NZGD_2000_Poverty_Bay_Circuit
enumeration NZGD_2000_Taranaki_Circuit
enumeration NZGD_2000_Timaru_Circuit
enumeration NZGD_2000_Tuhirangi_Circuit
enumeration NZGD_2000_UTM_Zone_58S
enumeration NZGD_2000_UTM_Zone_59S
enumeration NZGD_2000_UTM_Zone_60S
enumeration NZGD_2000_Wairarapa_Circuit
enumeration NZGD_2000_Wanganui_Circuit
enumeration NZGD_2000_Wellington_Circuit
enumeration GD_1949_New_Zealand_Map_Grid
enumeration New_Zealand_North_Island
enumeration New_Zealand_South_Island
enumeration Nigeria_East_Belt
enumeration Nigeria_Mid_Belt
enumeration Nigeria_West_Belt
enumeration Nord_Algerie_Degree
enumeration Nord_Algerie_Ancienne_Degree
enumeration Sud_Algerie_Ancienne
enumeration Nord_Algerie
enumeration Nord_de_Guerre
enumeration Nord_France
enumeration Nord_Maroc_Degree
enumeration Nord_Maroc
enumeration Nord_Tunisie
enumeration NGO_1948_Baerum_Kommune
enumeration NGO_1948_Bergenhalvoen
enumeration NGO_1948_Norway_Zone_1
enumeration NGO_1948_Norway_Zone_2
enumeration NGO_1948_Norway_Zone_3
enumeration NGO_1948_Norway_Zone_4
enumeration NGO_1948_Norway_Zone_5
enumeration NGO_1948_Norway_Zone_6
enumeration NGO_1948_Norway_Zone_7
enumeration NGO_1948_Norway_Zone_8
enumeration NGO_1948_Oslo_Kommune
enumeration NGO_1948_Oslo_Norway_Zone_1
enumeration NGO_1948_Oslo_Norway_Zone_2
enumeration NGO_1948_Oslo_Norway_Zone_3
enumeration NGO_1948_Oslo_Norway_Zone_4
enumeration NGO_1948_Oslo_Norway_Zone_5
enumeration NGO_1948_Oslo_Norway_Zone_6
enumeration NGO_1948_Oslo_Norway_Zone_7
enumeration NGO_1948_Oslo_Norway_Zone_8
enumeration NTF_France_I_degrees
enumeration NTF_France_II_degrees
enumeration NTF_France_III_degrees
enumeration NTF_France_IV_degrees
enumeration Palestine_1923_Israel_CS_Grid
enumeration Palestine_1923_Palestine_Belt
enumeration Palestine_1923_Palestine_Grid
enumeration Pampa_del_Castillo_Argentina_2
enumeration Peru_Central_Zone
enumeration Peru_East_Zone
enumeration Peru_West_Zone
enumeration Philippines_Zone_I
enumeration Philippines_Zone_II
enumeration Philippines_Zone_III
enumeration Philippines_Zone_IV
enumeration Philippines_Zone_V
enumeration Portuguese_National_Grid
enumeration Qatar_1948_Qatar_Grid
enumeration Qatar_National_Grid
enumeration RD_Old
enumeration RGF_1993_Lambert_93
enumeration Rijksdriehoekstelsel_New
enumeration RT90_25_gon_W
enumeration S-JTSK_Ferro_Krovak_East_North
enumeration S-JTSK_Ferro_Krovak
enumeration S-JTSK_Krovak_East_North
enumeration S-JTSK_Krovak
enumeration SAD_1969_Brazil_Polyconic
enumeration Sahara_Degree
enumeration Sahara
enumeration Sierra_Leone_1924_New_Colony_Grid
enumeration Sierra_Leone_1924_New_War_Office_Grid
enumeration St_Kitts_1955_British_West_Indies_Grid
enumeration St_Lucia_1955_British_West_Indies_Grid
enumeration St_Vincent_1945_British_West_Indies_Grid
enumeration Stereo_33
enumeration Stereo_70
enumeration Sud_Algerie_Degree
enumeration Sud_Algerie_Ancienne_Degree
enumeration Sud_Algerie
enumeration Sud_France
enumeration Sud_Maroc_Degree
enumeration Sud_Maroc
enumeration Sud_Tunisie
enumeration Swedish_National_Grid
enumeration Trinidad_1903_Trinidad_Grid
enumeration UWPP_1992
enumeration UWPP_2000_pas_5
enumeration UWPP_2000_pas_6
enumeration UWPP_2000_pas_7
enumeration UWPP_2000_pas_8
enumeration WGS_1972_BE_TM_106_NE
enumeration WGS_1984_TM_36_SE
enumeration Zanderij_Suriname_Old_TM
enumeration Zanderij_Suriname_TM
enumeration Zanderij_TM_54_NW
enumeration North_Pole_Azimuthal_Equidistant
enumeration North_Pole_Gnomonic
enumeration North_Pole_Lambert_Azimuthal_Equal_Area
enumeration North_Pole_Orthographic
enumeration North_Pole_Stereographic
enumeration South_Pole_Azimuthal_Equidistant
enumeration South_Pole_Gnomonic
enumeration South_Pole_Lambert_Azimuthal_Equal_Area
enumeration South_Pole_Orthographic
enumeration South_Pole_Stereographic
enumeration UPS_North
enumeration UPS_South
enumeration NAD_1927_StatePlane_Alabama_East_FIPS_0101
enumeration NAD_1927_StatePlane_Alabama_West_FIPS_0102
enumeration NAD_1927_StatePlane_Alaska_1_FIPS_5001
enumeration NAD_1927_StatePlane_Alaska_10_FIPS_5010
enumeration NAD_1927_StatePlane_Alaska_2_FIPS_5002
enumeration NAD_1927_StatePlane_Alaska_3_FIPS_5003
enumeration NAD_1927_StatePlane_Alaska_4_FIPS_5004
enumeration NAD_1927_StatePlane_Alaska_5_FIPS_5005
enumeration NAD_1927_StatePlane_Alaska_6_FIPS_5006
enumeration NAD_1927_StatePlane_Alaska_7_FIPS_5007
enumeration NAD_1927_StatePlane_Alaska_8_FIPS_5008
enumeration NAD_1927_StatePlane_Alaska_9_FIPS_5009
enumeration NAD_1927_StatePlane_Arizona_Central_FIPS_0202
enumeration NAD_1927_StatePlane_Arizona_East_FIPS_0201
enumeration NAD_1927_StatePlane_Arizona_West_FIPS_0203
enumeration NAD_1927_StatePlane_Arkansas_North_FIPS_0301
enumeration NAD_1927_StatePlane_Arkansas_South_FIPS_0302
enumeration NAD_1927_StatePlane_California_I_FIPS_0401
enumeration NAD_1927_StatePlane_California_II_FIPS_0402
enumeration NAD_1927_StatePlane_California_III_FIPS_0403
enumeration NAD_1927_StatePlane_California_IV_FIPS_0404
enumeration NAD_1927_StatePlane_California_V_FIPS_0405
enumeration NAD_1927_StatePlane_California_VI_FIPS_0406
enumeration NAD_1927_StatePlane_California_VII_FIPS_0407
enumeration NAD_1927_StatePlane_Colorado_Central_FIPS_0502
enumeration NAD_1927_StatePlane_Colorado_North_FIPS_0501
enumeration NAD_1927_StatePlane_Colorado_South_FIPS_0503
enumeration NAD_1927_StatePlane_Connecticut_FIPS_0600
enumeration NAD_1927_StatePlane_Delaware_FIPS_0700
enumeration NAD_1927_StatePlane_Florida_East_FIPS_0901
enumeration NAD_1927_StatePlane_Florida_North_FIPS_0903
enumeration NAD_1927_StatePlane_Florida_West_FIPS_0902
enumeration NAD_1927_StatePlane_Georgia_East_FIPS_1001
enumeration NAD_1927_StatePlane_Georgia_West_FIPS_1002
enumeration NAD_1927_StatePlane_Guam_FIPS_5400
enumeration NAD_1927_StatePlane_Idaho_Central_FIPS_1102
enumeration NAD_1927_StatePlane_Idaho_East_FIPS_1101
enumeration NAD_1927_StatePlane_Idaho_West_FIPS_1103
enumeration NAD_1927_StatePlane_Illinois_East_FIPS_1201
enumeration NAD_1927_StatePlane_Illinois_West_FIPS_1202
enumeration NAD_1927_StatePlane_Indiana_East_FIPS_1301
enumeration NAD_1927_StatePlane_Indiana_West_FIPS_1302
enumeration NAD_1927_StatePlane_Iowa_North_FIPS_1401
enumeration NAD_1927_StatePlane_Iowa_South_FIPS_1402
enumeration NAD_1927_StatePlane_Kansas_North_FIPS_1501
enumeration NAD_1927_StatePlane_Kansas_South_FIPS_1502
enumeration NAD_1927_StatePlane_Kentucky_North_FIPS_1601
enumeration NAD_1927_StatePlane_Kentucky_South_FIPS_1602
enumeration NAD_1927_StatePlane_Louisiana_North_FIPS_1701
enumeration NAD_1927_StatePlane_Louisiana_South_FIPS_1702
enumeration NAD_1927_StatePlane_Maine_East_FIPS_1801
enumeration NAD_1927_StatePlane_Maine_West_FIPS_1802
enumeration NAD_1927_StatePlane_Maryland_FIPS_1900
enumeration NAD_1927_StatePlane_Massachusetts_Island_FIPS_2002
enumeration NAD_1927_StatePlane_Massachusetts_Mainland_FIPS_2001
enumeration NAD_1927_StatePlane_Michigan_Central_FIPS_2112
enumeration NAD_1927_StatePlane_Michigan_North_FIPS_2111
enumeration NAD_1927_StatePlane_Michigan_South_FIPS_2113
enumeration NAD_1927_StatePlane_Minnesota_Central_FIPS_2202
enumeration NAD_1927_StatePlane_Minnesota_North_FIPS_2201
enumeration NAD_1927_StatePlane_Minnesota_South_FIPS_2203
enumeration NAD_1927_StatePlane_Mississippi_East_FIPS_2301
enumeration NAD_1927_StatePlane_Mississippi_West_FIPS_2302
enumeration NAD_1927_StatePlane_Missouri_Central_FIPS_2402
enumeration NAD_1927_StatePlane_Missouri_East_FIPS_2401
enumeration NAD_1927_StatePlane_Missouri_West_FIPS_2403
enumeration NAD_1927_StatePlane_Montana_Central_FIPS_2502
enumeration NAD_1927_StatePlane_Montana_North_FIPS_2501
enumeration NAD_1927_StatePlane_Montana_South_FIPS_2503
enumeration NAD_1927_StatePlane_Nebraska_North_FIPS_2601
enumeration NAD_1927_StatePlane_Nebraska_South_FIPS_2602
enumeration NAD_1927_StatePlane_Nevada_Central_FIPS_2702
enumeration NAD_1927_StatePlane_Nevada_East_FIPS_2701
enumeration NAD_1927_StatePlane_Nevada_West_FIPS_2703
enumeration NAD_1927_StatePlane_New_Hampshire_FIPS_2800
enumeration NAD_1927_StatePlane_New_Jersey_FIPS_2900
enumeration NAD_1927_StatePlane_New_Mexico_Central_FIPS_3002
enumeration NAD_1927_StatePlane_New_Mexico_East_FIPS_3001
enumeration NAD_1927_StatePlane_New_Mexico_West_FIPS_3003
enumeration NAD_1927_StatePlane_New_York_Central_FIPS_3102
enumeration NAD_1927_StatePlane_New_York_East_FIPS_3101
enumeration NAD_1927_StatePlane_New_York_Long_Island_FIPS_3104
enumeration NAD_1927_StatePlane_New_York_West_FIPS_3103
enumeration NAD_1927_StatePlane_North_Carolina_FIPS_3200
enumeration NAD_1927_StatePlane_North_Dakota_North_FIPS_3301
enumeration NAD_1927_StatePlane_North_Dakota_South_FIPS_3302
enumeration NAD_1927_StatePlane_Ohio_North_FIPS_3401
enumeration NAD_1927_StatePlane_Ohio_South_FIPS_3402
enumeration NAD_1927_StatePlane_Oklahoma_North_FIPS_3501
enumeration NAD_1927_StatePlane_Oklahoma_South_FIPS_3502
enumeration NAD_1927_StatePlane_Oregon_North_FIPS_3601
enumeration NAD_1927_StatePlane_Oregon_South_FIPS_3602
enumeration NAD_1927_StatePlane_Pennsylvania_North_FIPS_3701
enumeration NAD_1927_StatePlane_Pennsylvania_South_FIPS_3702
enumeration NAD_1927_StatePlane_Puerto_Rico_FIPS_5201
enumeration NAD_1927_StatePlane_Rhode_Island_FIPS_3800
enumeration NAD_1927_StatePlane_South_Carolina_North_FIPS_3901
enumeration NAD_1927_StatePlane_South_Carolina_South_FIPS_3902
enumeration NAD_1927_StatePlane_South_Dakota_North_FIPS_4001
enumeration NAD_1927_StatePlane_South_Dakota_South_FIPS_4002
enumeration NAD_1927_StatePlane_Tennessee_FIPS_4100
enumeration NAD_1927_StatePlane_Texas_Central_FIPS_4203
enumeration NAD_1927_StatePlane_Texas_North_Central_FIPS_4202
enumeration NAD_1927_StatePlane_Texas_North_FIPS_4201
enumeration NAD_1927_StatePlane_Texas_South_Central_FIPS_4204
enumeration NAD_1927_StatePlane_Texas_South_FIPS_4205
enumeration NAD_1927_StatePlane_Utah_Central_FIPS_4302
enumeration NAD_1927_StatePlane_Utah_North_FIPS_4301
enumeration NAD_1927_StatePlane_Utah_South_FIPS_4303
enumeration NAD_1927_StatePlane_Vermont_FIPS_3400
enumeration NAD_1927_StatePlane_Virginia_North_FIPS_4501
enumeration NAD_1927_StatePlane_Virginia_South_FIPS_4502
enumeration NAD_1927_StatePlane_Washington_North_FIPS_4601
enumeration NAD_1927_StatePlane_Washington_South_FIPS_4602
enumeration NAD_1927_StatePlane_West_Virginia_North_FIPS_4701
enumeration NAD_1927_StatePlane_West_Virginia_South_FIPS_4702
enumeration NAD_1927_StatePlane_Wisconsin_Central_FIPS_4802
enumeration NAD_1927_StatePlane_Wisconsin_North_FIPS_4801
enumeration NAD_1927_StatePlane_Wisconsin_South_FIPS_4803
enumeration NAD_1927_StatePlane_Wyoming_East_Central_FIPS_4902
enumeration NAD_1927_StatePlane_Wyoming_East_FIPS_4901
enumeration NAD_1927_StatePlane_Wyoming_West_Central_FIPS_4903
enumeration NAD_1927_StatePlane_Wyoming_West_FIPS_4904
enumeration NAD_1983_StatePlane_Alabama_East_FIPS_0101
enumeration NAD_1983_StatePlane_Alabama_West_FIPS_0102
enumeration NAD_1983_StatePlane_Alaska_1_FIPS_5001
enumeration NAD_1983_StatePlane_Alaska_10_FIPS_5010
enumeration NAD_1983_StatePlane_Alaska_2_FIPS_5002
enumeration NAD_1983_StatePlane_Alaska_3_FIPS_5003
enumeration NAD_1983_StatePlane_Alaska_4_FIPS_5004
enumeration NAD_1983_StatePlane_Alaska_5_FIPS_5005
enumeration NAD_1983_StatePlane_Alaska_6_FIPS_5006
enumeration NAD_1983_StatePlane_Alaska_7_FIPS_5007
enumeration NAD_1983_StatePlane_Alaska_8_FIPS_5008
enumeration NAD_1983_StatePlane_Alaska_9_FIPS_5009
enumeration NAD_1983_StatePlane_Arizona_Central_FIPS_0202
enumeration NAD_1983_StatePlane_Arizona_East_FIPS_0201
enumeration NAD_1983_StatePlane_Arizona_West_FIPS_0203
enumeration NAD_1983_StatePlane_Arkansas_North_FIPS_0301
enumeration NAD_1983_StatePlane_Arkansas_South_FIPS_0302
enumeration NAD_1983_StatePlane_California_I_FIPS_0401
enumeration NAD_1983_StatePlane_California_II_FIPS_0402
enumeration NAD_1983_StatePlane_California_III_FIPS_0403
enumeration NAD_1983_StatePlane_California_IV_FIPS_0404
enumeration NAD_1983_StatePlane_California_V_FIPS_0405
enumeration NAD_1983_StatePlane_California_VI_FIPS_0406
enumeration NAD_1983_StatePlane_Colorado_Central_FIPS_0502
enumeration NAD_1983_StatePlane_Colorado_North_FIPS_0501
enumeration NAD_1983_StatePlane_Colorado_South_FIPS_0503
enumeration NAD_1983_StatePlane_Connecticut_FIPS_0600
enumeration NAD_1983_StatePlane_Delaware_FIPS_0700
enumeration NAD_1983_StatePlane_Florida_East_FIPS_0901
enumeration NAD_1983_StatePlane_Florida_North_FIPS_0903
enumeration NAD_1983_StatePlane_Florida_West_FIPS_0902
enumeration NAD_1983_StatePlane_Georgia_East_FIPS_1001
enumeration NAD_1983_StatePlane_Georgia_West_FIPS_1002
enumeration NAD_1983_StatePlane_Guam_FIPS_5400
enumeration NAD_1983_StatePlane_Hawaii_1_FIPS_5101
enumeration NAD_1983_StatePlane_Hawaii_2_FIPS_5102
enumeration NAD_1983_StatePlane_Hawaii_3_FIPS_5103
enumeration NAD_1983_StatePlane_Hawaii_4_FIPS_5104
enumeration NAD_1983_StatePlane_Hawaii_5_FIPS_5105
enumeration NAD_1983_StatePlane_Idaho_Central_FIPS_1102
enumeration NAD_1983_StatePlane_Idaho_East_FIPS_1101
enumeration NAD_1983_StatePlane_Idaho_West_FIPS_1103
enumeration NAD_1983_StatePlane_Illinois_East_FIPS_1201
enumeration NAD_1983_StatePlane_Illinois_West_FIPS_1202
enumeration NAD_1983_StatePlane_Indiana_East_FIPS_1301
enumeration NAD_1983_StatePlane_Indiana_West_FIPS_1302
enumeration NAD_1983_StatePlane_Iowa_North_FIPS_1401
enumeration NAD_1983_StatePlane_Iowa_South_FIPS_1402
enumeration NAD_1983_StatePlane_Kansas_North_FIPS_1501
enumeration NAD_1983_StatePlane_Kansas_South_FIPS_1502
enumeration NAD_1983_StatePlane_Kentucky_FIPS_1600
enumeration NAD_1983_StatePlane_Kentucky_North_FIPS_1601
enumeration NAD_1983_StatePlane_Kentucky_South_FIPS_1602
enumeration NAD_1983_StatePlane_Louisiana_North_FIPS_1701
enumeration NAD_1983_StatePlane_Louisiana_South_FIPS_1702
enumeration NAD_1983_StatePlane_Maine_East_FIPS_1801
enumeration NAD_1983_StatePlane_Maine_West_FIPS_1802
enumeration NAD_1983_StatePlane_Maryland_FIPS_1900
enumeration NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002
enumeration NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001
enumeration NAD_1983_StatePlane_Michigan_Central_FIPS_2202
enumeration NAD_1983_StatePlane_Michigan_North_FIPS_2111
enumeration NAD_1983_StatePlane_Michigan_South_FIPS_2113
enumeration NAD_1983_StatePlane_Minnesota_Central_FIPS_2202
enumeration NAD_1983_StatePlane_Minnesota_North_FIPS_2201
enumeration NAD_1983_StatePlane_Minnesota_South_FIPS_2203
enumeration NAD_1983_StatePlane_Mississippi_East_FIPS_2301
enumeration NAD_1983_StatePlane_Mississippi_West_FIPS_2302
enumeration NAD_1983_StatePlane_Missouri_Central_FIPS_2402
enumeration NAD_1983_StatePlane_Missouri_East_FIPS_2401
enumeration NAD_1983_StatePlane_Missouri_West_FIPS_2403
enumeration NAD_1983_StatePlane_Montana_FIPS_2500
enumeration NAD_1983_StatePlane_Nebraska_FIPS_2600
enumeration NAD_1983_StatePlane_Nevada_Central_FIPS_2702
enumeration NAD_1983_StatePlane_Nevada_East_FIPS_2701
enumeration NAD_1983_StatePlane_Nevada_West_FIPS_2703
enumeration NAD_1983_StatePlane_New_Hampshire_FIPS_2800
enumeration NAD_1983_StatePlane_New_Jersey_FIPS_2900
enumeration NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002
enumeration NAD_1983_StatePlane_New_Mexico_East_FIPS_3001
enumeration NAD_1983_StatePlane_New_Mexico_West_FIPS_3003
enumeration NAD_1983_StatePlane_New_York_Central_FIPS_3102
enumeration NAD_1983_StatePlane_New_York_East_FIPS_3101
enumeration NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104
enumeration NAD_1983_StatePlane_New_York_West_FIPS_3103
enumeration NAD_1983_StatePlane_North_Carolina_FIPS_3200
enumeration NAD_1983_StatePlane_North_Dakota_North_FIPS_3301
enumeration NAD_1983_StatePlane_North_Dakota_South_FIPS_3302
enumeration NAD_1983_StatePlane_Ohio_North_FIPS_3401
enumeration NAD_1983_StatePlane_Ohio_South_FIPS_3402
enumeration NAD_1983_StatePlane_Oklahoma_North_FIPS_3501
enumeration NAD_1983_StatePlane_Oklahoma_South_FIPS_3502
enumeration NAD_1983_StatePlane_Oregon_North_FIPS_3601
enumeration NAD_1983_StatePlane_Oregon_South_FIPS_3602
enumeration NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701
enumeration NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702
enumeration NAD_1983_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200
enumeration NAD_1983_StatePlane_Rhode_Island_FIPS_3800
enumeration NAD_1983_StatePlane_South_Carolina_FIPS_3900
enumeration NAD_1983_StatePlane_South_Dakota_North_FIPS_4001
enumeration NAD_1983_StatePlane_South_Dakota_South_FIPS_4002
enumeration NAD_1983_StatePlane_Tennessee_FIPS_4100
enumeration NAD_1983_StatePlane_Texas_Central_FIPS_4203
enumeration NAD_1983_StatePlane_Texas_North_Central_FIPS_4202
enumeration NAD_1983_StatePlane_Texas_North_FIPS_4201
enumeration NAD_1983_StatePlane_Texas_South_Central_FIPS_4204
enumeration NAD_1983_StatePlane_Texas_South_FIPS_4205
enumeration NAD_1983_StatePlane_Utah_Central_FIPS_4302
enumeration NAD_1983_StatePlane_Utah_North_FIPS_4301
enumeration NAD_1983_StatePlane_Utah_South_FIPS_4303
enumeration NAD_1983_StatePlane_Vermont_FIPS_4400
enumeration NAD_1983_StatePlane_Virginia_North_FIPS_4501
enumeration NAD_1983_StatePlane_Virginia_South_FIPS_4502
enumeration NAD_1983_StatePlane_Washington_North_FIPS_4601
enumeration NAD_1983_StatePlane_Washington_South_FIPS_4602
enumeration NAD_1983_StatePlane_West_Virginia_North_FIPS_4701
enumeration NAD_1983_StatePlane_West_Virginia_South_FIPS_4702
enumeration NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802
enumeration NAD_1983_StatePlane_Wisconsin_North_FIPS_4801
enumeration NAD_1983_StatePlane_Wisconsin_South_FIPS_4803
enumeration NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902
enumeration NAD_1983_StatePlane_Wyoming_East_FIPS_4901
enumeration NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903
enumeration NAD_1983_StatePlane_Wyoming_West_FIPS_4904
enumeration NAD_1983_StatePlane_Alabama_East_FIPS_0101_Feet
enumeration NAD_1983_StatePlane_Alabama_West_FIPS_0102_Feet
enumeration NAD_1983_StatePlane_Alaska_1_FIPS_5001_Feet
enumeration NAD_1983_StatePlane_Alaska_10_FIPS_5010_Feet
enumeration NAD_1983_StatePlane_Alaska_2_FIPS_5002_Feet
enumeration NAD_1983_StatePlane_Alaska_3_FIPS_5003_Feet
enumeration NAD_1983_StatePlane_Alaska_4_FIPS_5004_Feet
enumeration NAD_1983_StatePlane_Alaska_5_FIPS_5005_Feet
enumeration NAD_1983_StatePlane_Alaska_6_FIPS_5006_Feet
enumeration NAD_1983_StatePlane_Alaska_7_FIPS_5007_Feet
enumeration NAD_1983_StatePlane_Alaska_8_FIPS_5008_Feet
enumeration NAD_1983_StatePlane_Alaska_9_FIPS_5009_Feet
enumeration NAD_1983_StatePlane_Arizona_Central_FIPS_0202_Feet
enumeration NAD_1983_StatePlane_Arizona_East_FIPS_0201_Feet
enumeration NAD_1983_StatePlane_Arizona_West_FIPS_0203_Feet
enumeration NAD_1983_StatePlane_Arkansas_North_FIPS_0301_Feet
enumeration NAD_1983_StatePlane_Arkansas_South_FIPS_0302_Feet
enumeration NAD_1983_StatePlane_California_I_FIPS_0401_Feet
enumeration NAD_1983_StatePlane_California_II_FIPS_0402_Feet
enumeration NAD_1983_StatePlane_California_III_FIPS_0403_Feet
enumeration NAD_1983_StatePlane_California_IV_FIPS_0404_Feet
enumeration NAD_1983_StatePlane_California_V_FIPS_0405_Feet
enumeration NAD_1983_StatePlane_California_VI_FIPS_0406_Feet
enumeration NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet
enumeration NAD_1983_StatePlane_Colorado_North_FIPS_0501_Feet
enumeration NAD_1983_StatePlane_Colorado_South_FIPS_0503_Feet
enumeration NAD_1983_StatePlane_Connecticut_FIPS_0600_Feet
enumeration NAD_1983_StatePlane_Delaware_FIPS_0700_Feet
enumeration NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet
enumeration NAD_1983_StatePlane_Florida_North_FIPS_0903_Feet
enumeration NAD_1983_StatePlane_Florida_West_FIPS_0902_Feet
enumeration NAD_1983_StatePlane_Georgia_East_FIPS_1001_Feet
enumeration NAD_1983_StatePlane_Georgia_West_FIPS_1002_Feet
enumeration NAD_1983_StatePlane_Guam_FIPS_5400_Feet
enumeration NAD_1983_StatePlane_Hawaii_1_FIPS_5101_Feet
enumeration NAD_1983_StatePlane_Hawaii_2_FIPS_5102_Feet
enumeration NAD_1983_StatePlane_Hawaii_3_FIPS_5103_Feet
enumeration NAD_1983_StatePlane_Hawaii_4_FIPS_5104_Feet
enumeration NAD_1983_StatePlane_Hawaii_5_FIPS_5105_Feet
enumeration NAD_1983_StatePlane_Idaho_Central_FIPS_1102_Feet
enumeration NAD_1983_StatePlane_Idaho_East_FIPS_1101_Feet
enumeration NAD_1983_StatePlane_Idaho_West_FIPS_1103_Feet
enumeration NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet
enumeration NAD_1983_StatePlane_Illinois_West_FIPS_1202_Feet
enumeration NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet
enumeration NAD_1983_StatePlane_Indiana_West_FIPS_1302_Feet
enumeration NAD_1983_StatePlane_Iowa_North_FIPS_1401_Feet
enumeration NAD_1983_StatePlane_Iowa_South_FIPS_1402_Feet
enumeration NAD_1983_StatePlane_Kansas_North_FIPS_1501_Feet
enumeration NAD_1983_StatePlane_Kansas_South_FIPS_1502_Feet
enumeration NAD_1983_StatePlane_Kentucky_FIPS_1600_Feet
enumeration NAD_1983_StatePlane_Kentucky_North_FIPS_1601_Feet
enumeration NAD_1983_StatePlane_Kentucky_South_FIPS_1602_Feet
enumeration NAD_1983_StatePlane_Louisiana_North_FIPS_1701_Feet
enumeration NAD_1983_StatePlane_Louisiana_South_FIPS_1702_Feet
enumeration NAD_1983_StatePlane_Maine_East_FIPS_1801_Feet
enumeration NAD_1983_StatePlane_Maine_West_FIPS_1802_Feet
enumeration NAD_1983_StatePlane_Maryland_FIPS_1900_Feet
enumeration NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002_Feet
enumeration NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001_Feet
enumeration NAD_1983_StatePlane_Michigan_Central_FIPS_2202_Feet
enumeration NAD_1983_StatePlane_Michigan_North_FIPS_2111_Feet
enumeration NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet
enumeration NAD_1983_StatePlane_Minnesota_Central_FIPS_2202_Feet
enumeration NAD_1983_StatePlane_Minnesota_North_FIPS_2201_Feet
enumeration NAD_1983_StatePlane_Minnesota_South_FIPS_2203_Feet
enumeration NAD_1983_StatePlane_Mississippi_East_FIPS_2301_Feet
enumeration NAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feet
enumeration NAD_1983_StatePlane_Missouri_Central_FIPS_2402_Feet
enumeration NAD_1983_StatePlane_Missouri_East_FIPS_2401_Feet
enumeration NAD_1983_StatePlane_Missouri_West_FIPS_2403_Feet
enumeration NAD_1983_StatePlane_Montana_FIPS_2500_Feet
enumeration NAD_1983_StatePlane_Nebraska_FIPS_2600_Feet
enumeration NAD_1983_StatePlane_Nevada_Central_FIPS_2702_Feet
enumeration NAD_1983_StatePlane_Nevada_East_FIPS_2701_Feet
enumeration NAD_1983_StatePlane_Nevada_West_FIPS_2703_Feet
enumeration NAD_1983_StatePlane_New_Hampshire_FIPS_2800_Feet
enumeration NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet
enumeration NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002_Feet
enumeration NAD_1983_StatePlane_New_Mexico_East_FIPS_3001_Feet
enumeration NAD_1983_StatePlane_New_Mexico_West_FIPS_3003_Feet
enumeration NAD_1983_StatePlane_New_York_Central_FIPS_3102_Feet
enumeration NAD_1983_StatePlane_New_York_East_FIPS_3101_Feet
enumeration NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet
enumeration NAD_1983_StatePlane_New_York_West_FIPS_3103_Feet
enumeration NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet
enumeration NAD_1983_StatePlane_North_Dakota_North_FIPS_3301_Feet
enumeration NAD_1983_StatePlane_North_Dakota_South_FIPS_3302_Feet
enumeration NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet
enumeration NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet
enumeration NAD_1983_StatePlane_Oklahoma_North_FIPS_3501_Feet
enumeration NAD_1983_StatePlane_Oklahoma_South_FIPS_3502_Feet
enumeration NAD_1983_StatePlane_Oregon_North_FIPS_3601_Feet
enumeration NAD_1983_StatePlane_Oregon_South_FIPS_3602_Feet
enumeration NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701_Feet
enumeration NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702_Feet
enumeration NAD_1983_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200_Feet
enumeration NAD_1983_StatePlane_Rhode_Island_FIPS_3800_Feet
enumeration NAD_1983_StatePlane_South_Carolina_FIPS_3900_Feet
enumeration NAD_1983_StatePlane_South_Dakota_North_FIPS_4001_Feet
enumeration NAD_1983_StatePlane_South_Dakota_South_FIPS_4002_Feet
enumeration NAD_1983_StatePlane_Tennessee_FIPS_4100_Feet
enumeration NAD_1983_StatePlane_Texas_Central_FIPS_4203_Feet
enumeration NAD_1983_StatePlane_Texas_North_Central_FIPS_4202_Feet
enumeration NAD_1983_StatePlane_Texas_North_FIPS_4201_Feet
enumeration NAD_1983_StatePlane_Texas_South_Central_FIPS_4204_Feet
enumeration NAD_1983_StatePlane_Texas_South_FIPS_4205_Feet
enumeration NAD_1983_StatePlane_Utah_Central_FIPS_4302_Feet
enumeration NAD_1983_StatePlane_Utah_North_FIPS_4301_Feet
enumeration NAD_1983_StatePlane_Utah_South_FIPS_4303_Feet
enumeration NAD_1983_StatePlane_Vermont_FIPS_4400_Feet
enumeration NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet
enumeration NAD_1983_StatePlane_Virginia_South_FIPS_4502_Feet
enumeration NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet
enumeration NAD_1983_StatePlane_Washington_South_FIPS_4602_Feet
enumeration NAD_1983_StatePlane_West_Virginia_North_FIPS_4701_Feet
enumeration NAD_1983_StatePlane_West_Virginia_South_FIPS_4702_Feet
enumeration NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802_Feet
enumeration NAD_1983_StatePlane_Wisconsin_North_FIPS_4801_Feet
enumeration NAD_1983_StatePlane_Wisconsin_South_FIPS_4803_Feet
enumeration NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902_Feet
enumeration NAD_1983_StatePlane_Wyoming_East_FIPS_4901_Feet
enumeration NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903_Feet
enumeration NAD_1983_StatePlane_Wyoming_West_FIPS_4904_Feet
enumeration NAD_1983_HARN_StatePlane_Alabama_East_FIPS_0101
enumeration NAD_1983_HARN_StatePlane_Alabama_West_FIPS_0102
enumeration NAD_1983_HARN_StatePlane_Arizona_Central_FIPS_0202
enumeration NAD_1983_HARN_StatePlane_Arizona_East_FIPS_0201
enumeration NAD_1983_HARN_StatePlane_Arizona_West_FIPS_0203
enumeration NAD_1983_HARN_StatePlane_California_I_FIPS_0401
enumeration NAD_1983_HARN_StatePlane_California_II_FIPS_0402
enumeration NAD_1983_HARN_StatePlane_California_III_FIPS_0403
enumeration NAD_1983_HARN_StatePlane_California_IV_FIPS_0404
enumeration NAD_1983_HARN_StatePlane_California_V_FIPS_0405
enumeration NAD_1983_HARN_StatePlane_California_VI_FIPS_0406
enumeration NAD_1983_HARN_StatePlane_Colorado_Central_FIPS_0502
enumeration NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501
enumeration NAD_1983_HARN_StatePlane_Colorado_South_FIPS_0503
enumeration NAD_1983_HARN_StatePlane_Connecticut_FIPS_0600
enumeration NAD_1983_HARN_StatePlane_Delaware_FIPS_0700
enumeration NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901
enumeration NAD_1983_HARN_StatePlane_Florida_North_FIPS_0903
enumeration NAD_1983_HARN_StatePlane_Florida_West_FIPS_0902
enumeration NAD_1983_HARN_StatePlane_Georgia_East_FIPS_1001
enumeration NAD_1983_HARN_StatePlane_Georgia_West_FIPS_1002
enumeration NAD_1983_HARN_StatePlane_Hawaii_1_FIPS_5101
enumeration NAD_1983_HARN_StatePlane_Hawaii_2_FIPS_5102
enumeration NAD_1983_HARN_StatePlane_Hawaii_3_FIPS_5103
enumeration NAD_1983_HARN_StatePlane_Hawaii_4_FIPS_5104
enumeration NAD_1983_HARN_StatePlane_Hawaii_5_FIPS_5105
enumeration NAD_1983_HARN_StatePlane_Idaho_Central_FIPS_1102
enumeration NAD_1983_HARN_StatePlane_Idaho_East_FIPS_1101
enumeration NAD_1983_HARN_StatePlane_Idaho_West_FIPS_1103
enumeration NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201
enumeration NAD_1983_HARN_StatePlane_Illinois_West_FIPS_1202
enumeration NAD_1983_HARN_StatePlane_Indiana_East_FIPS_1301
enumeration NAD_1983_HARN_StatePlane_Indiana_West_FIPS_1302
enumeration NAD_1983_HARN_StatePlane_Kansas_North_FIPS_1501
enumeration NAD_1983_HARN_StatePlane_Kansas_South_FIPS_1502
enumeration NAD_1983_HARN_StatePlane_Kentucky_North_FIPS_1601
enumeration NAD_1983_HARN_StatePlane_Kentucky_South_FIPS_1602
enumeration NAD_1983_HARN_StatePlane_Louisiana_North_FIPS_1701
enumeration NAD_1983_HARN_StatePlane_Louisiana_South_FIPS_1702
enumeration NAD_1983_HARN_StatePlane_Maine_East_FIPS_1801
enumeration NAD_1983_HARN_StatePlane_Maine_West_FIPS_1802
enumeration NAD_1983_HARN_StatePlane_Maryland_FIPS_1900
enumeration NAD_1983_HARN_StatePlane_Massachusetts_Island_FIPS_2002
enumeration NAD_1983_HARN_StatePlane_Massachusetts_Mainland_FIPS_2001
enumeration NAD_1983_HARN_StatePlane_Michigan_Central_FIPS_2202
enumeration NAD_1983_HARN_StatePlane_Michigan_North_FIPS_2111
enumeration NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113
enumeration NAD_1983_HARN_StatePlane_Mississippi_East_FIPS_2301
enumeration NAD_1983_HARN_StatePlane_Mississippi_West_FIPS_2302
enumeration NAD_1983_HARN_StatePlane_Montana_FIPS_2500
enumeration NAD_1983_HARN_StatePlane_Nebraska_FIPS_2600
enumeration NAD_1983_HARN_StatePlane_Nevada_Central_FIPS_2702
enumeration NAD_1983_HARN_StatePlane_Nevada_East_FIPS_2701
enumeration NAD_1983_HARN_StatePlane_Nevada_West_FIPS_2703
enumeration NAD_1983_HARN_StatePlane_New_Hampshire_FIPS_2800
enumeration NAD_1983_HARN_StatePlane_New_Jersey_FIPS_2900
enumeration NAD_1983_HARN_StatePlane_New_Mexico_Central_FIPS_3002
enumeration NAD_1983_HARN_StatePlane_New_Mexico_East_FIPS_3001
enumeration NAD_1983_HARN_StatePlane_New_Mexico_West_FIPS_3003
enumeration NAD_1983_HARN_StatePlane_New_York_Central_FIPS_3102
enumeration NAD_1983_HARN_StatePlane_New_York_East_FIPS_3101
enumeration NAD_1983_HARN_StatePlane_New_York_Long_Island_FIPS_3104
enumeration NAD_1983_HARN_StatePlane_New_York_West_FIPS_3103
enumeration NAD_1983_HARN_StatePlane_North_Dakota_North_FIPS_3301
enumeration NAD_1983_HARN_StatePlane_North_Dakota_South_FIPS_3302
enumeration NAD_1983_HARN_StatePlane_Ohio_North_FIPS_3401
enumeration NAD_1983_HARN_StatePlane_Ohio_South_FIPS_3402
enumeration NAD_1983_HARN_StatePlane_Oklahoma_North_FIPS_3501
enumeration NAD_1983_HARN_StatePlane_Oklahoma_South_FIPS_3502
enumeration NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601
enumeration NAD_1983_HARN_StatePlane_Oregon_South_FIPS_3602
enumeration NAD_1983_HARN_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200
enumeration NAD_1983_HARN_StatePlane_Rhode_Island_FIPS_3800
enumeration NAD_1983_HARN_StatePlane_South_Dakota_North_FIPS_4001
enumeration NAD_1983_HARN_StatePlane_South_Dakota_South_FIPS_4002
enumeration NAD_1983_HARN_StatePlane_Tennessee_FIPS_4100
enumeration NAD_1983_HARN_StatePlane_Texas_Central_FIPS_4203
enumeration NAD_1983_HARN_StatePlane_Texas_North_Central_FIPS_4202
enumeration NAD_1983_HARN_StatePlane_Texas_North_FIPS_4201
enumeration NAD_1983_HARN_StatePlane_Texas_South_Central_FIPS_4204
enumeration NAD_1983_HARN_StatePlane_Texas_South_FIPS_4205
enumeration NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302
enumeration NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301
enumeration NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303
enumeration NAD_1983_HARN_StatePlane_Vermont_FIPS_4400
enumeration NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501
enumeration NAD_1983_HARN_StatePlane_Virginia_South_FIPS_4502
enumeration NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601
enumeration NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602
enumeration NAD_1983_HARN_StatePlane_West_Virginia_North_FIPS_4701
enumeration NAD_1983_HARN_StatePlane_West_Virginia_South_FIPS_4702
enumeration NAD_1983_HARN_StatePlane_Wisconsin_Central_FIPS_4802
enumeration NAD_1983_HARN_StatePlane_Wisconsin_North_FIPS_4801
enumeration NAD_1983_HARN_StatePlane_Wisconsin_South_FIPS_4803
enumeration NAD_1983_HARN_StatePlane_Wyoming_East_FIPS_4901
enumeration NAD_1983_HARN_StatePlane_Wyoming_East_Central_FIPS_4902
enumeration NAD_1983_HARN_StatePlane_Wyoming_West_Central_FIPS_4903
enumeration NAD_1983_HARN_StatePlane_Wyoming_West_FIPS_4904
enumeration American_Samoa_1962_StatePlane_American_Samoa_FIPS_5300
enumeration NAD_1983_HARN_Guam_Map_Grid
enumeration NAD_1983_HARN_UTM_Zone_2S
enumeration NAD_Michigan_StatePlane_Michigan_Central_FIPS_2112
enumeration NAD_Michigan_StatePlane_Michigan_Central_Old_FIPS_2102
enumeration NAD_Michigan_StatePlane_Michigan_East_Old_FIPS_2101
enumeration NAD_Michigan_StatePlane_Michigan_North_FIPS_2111
enumeration NAD_Michigan_StatePlane_Michigan_South_FIPS_2113
enumeration NAD_Michigan_StatePlane_Michigan_West_Old_FIPS_2103
enumeration Old_Hawaiian_StatePlane_Hawaii_1_FIPS_5101
enumeration Old_Hawaiian_StatePlane_Hawaii_2_FIPS_5102
enumeration Old_Hawaiian_StatePlane_Hawaii_3_FIPS_5103
enumeration Old_Hawaiian_StatePlane_Hawaii_4_FIPS_5104
enumeration Old_Hawaiian_StatePlane_Hawaii_5_FIPS_5105
enumeration Puerto_Rico_StatePlane_Puerto_Rico_FIPS_5201
enumeration Puerto_Rico_StatePlane_Virgin_Islands_St_Croix_FIPS_5202
enumeration NAD_1927_UTM_Zone_10N
enumeration NAD_1927_UTM_Zone_11N
enumeration NAD_1927_UTM_Zone_12N
enumeration NAD_1927_UTM_Zone_13N
enumeration NAD_1927_UTM_Zone_14N
enumeration NAD_1927_UTM_Zone_15N
enumeration NAD_1927_UTM_Zone_16N
enumeration NAD_1927_UTM_Zone_17N
enumeration NAD_1927_UTM_Zone_18N
enumeration NAD_1927_UTM_Zone_19N
enumeration NAD_1927_UTM_Zone_20N
enumeration NAD_1927_UTM_Zone_21N
enumeration NAD_1927_UTM_Zone_22N
enumeration NAD_1927_UTM_Zone_3N
enumeration NAD_1927_UTM_Zone_4N
enumeration NAD_1927_UTM_Zone_5N
enumeration NAD_1927_UTM_Zone_6N
enumeration NAD_1927_UTM_Zone_7N
enumeration NAD_1927_UTM_Zone_8N
enumeration NAD_1927_UTM_Zone_9N
enumeration NAD_1983_UTM_Zone_10N
enumeration NAD_1983_UTM_Zone_11N
enumeration NAD_1983_UTM_Zone_12N
enumeration NAD_1983_UTM_Zone_13N
enumeration NAD_1983_UTM_Zone_14N
enumeration NAD_1983_UTM_Zone_15N
enumeration NAD_1983_UTM_Zone_16N
enumeration NAD_1983_UTM_Zone_17N
enumeration NAD_1983_UTM_Zone_18N
enumeration NAD_1983_UTM_Zone_19N
enumeration NAD_1983_UTM_Zone_20N
enumeration NAD_1983_UTM_Zone_21N
enumeration NAD_1983_UTM_Zone_22N
enumeration NAD_1983_UTM_Zone_23N
enumeration NAD_1983_UTM_Zone_3N
enumeration NAD_1983_UTM_Zone_4N
enumeration NAD_1983_UTM_Zone_5N
enumeration NAD_1983_UTM_Zone_6N
enumeration NAD_1983_UTM_Zone_7N
enumeration NAD_1983_UTM_Zone_8N
enumeration NAD_1983_UTM_Zone_9N
enumeration Abidjan_1987_UTM_Zone_29N
enumeration Abidjan_1987_UTM_Zone_30N
enumeration Adindan_UTM_Zone_37N
enumeration Adindan_UTM_Zone_38N
enumeration Afgooye_UTM_Zone_38N
enumeration Afgooye_UTM_Zone_39N
enumeration Ain_el_Abd_UTM_Zone_37N
enumeration Ain_el_Abd_UTM_Zone_38N
enumeration Ain_el_Abd_UTM_Zone_39N
enumeration Aratu_UTM_Zone_22S
enumeration Aratu_UTM_Zone_23S
enumeration Aratu_UTM_Zone_24S
enumeration Arc_1950_UTM_Zone_34S
enumeration Arc_1950_UTM_Zone_35S
enumeration Arc_1950_UTM_Zone_36S
enumeration Arc_1960_UTM_Zone_35N
enumeration Arc_1960_UTM_Zone_35S
enumeration Arc_1960_UTM_Zone_36N
enumeration Arc_1960_UTM_Zone_36S
enumeration Arc_1960_UTM_Zone_37N
enumeration Arc_1960_UTM_Zone_37S
enumeration ATS_1977_UTM_Zone_19N
enumeration ATS_1977_UTM_Zone_20N
enumeration Batavia_UTM_Zone_48S
enumeration Batavia_UTM_Zone_49S
enumeration Batavia_UTM_Zone_50S
enumeration Bissau_UTM_Zone_28N
enumeration Bogota_UTM_Zone_17N
enumeration Bogota_UTM_Zone_18N
enumeration Camacupa_UTM_Zone_32S
enumeration Camacupa_UTM_Zone_33S
enumeration Cape_UTM_Zone_34S
enumeration Cape_UTM_Zone_35S
enumeration Cape_UTM_Zone_36S
enumeration Carthage_UTM_Zone_32N
enumeration Conakry_1905_UTM_Zone_28N
enumeration Conakry_1905_UTM_Zone_29N
enumeration Corrego_Alegre_UTM_Zone_23S
enumeration Corrego_Alegre_UTM_Zone_24S
enumeration Dabola_UTM_Zone_28N
enumeration Dabola_UTM_Zone_29N
enumeration Datum_73_UTM_Zone_29N
enumeration Douala_UTM_Zone_32N
enumeration ED_1950_ED77_UTM_Zone_38N
enumeration ED_1950_ED77_UTM_Zone_39N
enumeration ED_1950_ED77_UTM_Zone_40N
enumeration ED_1950_ED77_UTM_Zone_41N
enumeration ELD_1979_UTM_Zone_32N
enumeration ELD_1979_UTM_Zone_33N
enumeration ELD_1979_UTM_Zone_34N
enumeration ELD_1979_UTM_Zone_35N
enumeration ETRF_1989_UTM_Zone_28N
enumeration ETRF_1989_UTM_Zone_29N
enumeration ETRF_1989_UTM_Zone_30N
enumeration ETRF_1989_UTM_Zone_31N
enumeration ETRF_1989_UTM_Zone_32N
enumeration ETRF_1989_UTM_Zone_33N
enumeration ETRF_1989_UTM_Zone_34N
enumeration ETRF_1989_UTM_Zone_35N
enumeration ETRF_1989_UTM_Zone_36N
enumeration ETRF_1989_UTM_Zone_37N
enumeration ETRF_1989_UTM_Zone_38N
enumeration ED_1950_UTM_Zone_28N
enumeration ED_1950_UTM_Zone_29N
enumeration ED_1950_UTM_Zone_30N
enumeration ED_1950_UTM_Zone_31N
enumeration ED_1950_UTM_Zone_32N
enumeration ED_1950_UTM_Zone_33N
enumeration ED_1950_UTM_Zone_34N
enumeration ED_1950_UTM_Zone_35N
enumeration ED_1950_UTM_Zone_36N
enumeration ED_1950_UTM_Zone_37N
enumeration ED_1950_UTM_Zone_38N
enumeration Fahud_UTM_Zone_39N
enumeration Fahud_UTM_Zone_40N
enumeration Garoua_UTM_Zone_33N
enumeration Graciosa_Base_SW_1948_UTM_Zone_26N
enumeration Hito_XVIII_1963_UTM_19S
enumeration Hong_Kong_1980_UTM_Zone_49N
enumeration Hong_Kong_1980_UTM_Zone_50N
enumeration Indian_1954_UTM_Zone_46N
enumeration Indian_1954_UTM_Zone_47N
enumeration Indian_1954_UTM_Zone_48N
enumeration Indian_1960_UTM_Zone_48N
enumeration Indian_1960_UTM_Zone_49N
enumeration Indian_1975_UTM_Zone_47N
enumeration Indian_1975_UTM_Zone_48N
enumeration Indonesian_1974_UTM_Zone_46N
enumeration Indonesian_1974_UTM_Zone_46S
enumeration Indonesian_1974_UTM_Zone_47N
enumeration Indonesian_1974_UTM_Zone_47S
enumeration Indonesian_1974_UTM_Zone_48N
enumeration Indonesian_1974_UTM_Zone_48S
enumeration Indonesian_1974_UTM_Zone_49N
enumeration Indonesian_1974_UTM_Zone_49S
enumeration Indonesian_1974_UTM_Zone_50N
enumeration Indonesian_1974_UTM_Zone_50S
enumeration Indonesian_1974_UTM_Zone_51N
enumeration Indonesian_1974_UTM_Zone_51S
enumeration Indonesian_1974_UTM_Zone_52N
enumeration Indonesian_1974_UTM_Zone_52S
enumeration Indonesian_1974_UTM_Zone_53N
enumeration Indonesian_1974_UTM_Zone_53S
enumeration Indonesian_1974_UTM_Zone_54S
enumeration IRENET95_UTM_Zone_29N
enumeration Kertau_UTM_Zone_47N
enumeration Kertau_UTM_Zone_48N
enumeration La_Canoa_UTM_Zone_18N
enumeration La_Canoa_UTM_Zone_19N
enumeration La_Canoa_UTM_Zone_20N
enumeration La_Canoa_UTM_Zone_21N
enumeration Locodjo_1965_UTM_Zone_29N
enumeration Locodjo_1965_UTM_Zone_30N
enumeration Lome_UTM_Zone_31N
enumeration Mporaloko_UTM_Zone_32N
enumeration Mporaloko_UTM_Zone_32S
enumeration Malongo_1987_UTM_Zone_32S
enumeration Massawa_UTM_Zone_37N
enumeration Mhast_UTM_Zone_32S
enumeration Minna_UTM_Zone_31N
enumeration Minna_UTM_Zone_32N
enumeration Moznet_UTM_Zone_36S
enumeration Moznet_UTM_Zone_37S
enumeration NAD_1927_BLM_Zone_14N
enumeration NAD_1927_BLM_Zone_15N
enumeration NAD_1927_BLM_Zone_16N
enumeration NAD_1927_BLM_Zone_17N
enumeration NAD_1983_HARN_UTM_Zone_2S
enumeration Nahrwan_1967_UTM_Zone_38N
enumeration Nahrwan_1967_UTM_Zone_39N
enumeration Nahrwan_1967_UTM_Zone_40N
enumeration Naparima_1955_UTM_Zone_20N
enumeration Naparima_1972_UTM_Zone_20N
enumeration NGN_UTM_Zone_38N
enumeration NGN_UTM_Zone_39N
enumeration NGO_1948_UTM_Zone_32N
enumeration NGO_1948_UTM_Zone_33N
enumeration NGO_1948_UTM_Zone_34N
enumeration NGO_1948_UTM_Zone_35N
enumeration Nord_Sahara_1959_UTM_Zone_29N
enumeration Nord_Sahara_1959_UTM_Zone_30N
enumeration Nord_Sahara_1959_UTM_Zone_31N
enumeration Nord_Sahara_1959_UTM_Zone_32N
enumeration NZGD_1949_UTM_Zone_58S
enumeration NZGD_1949_UTM_Zone_59S
enumeration NZGD_1949_UTM_Zone_60S
enumeration NZGD_2000_UTM_Zone_58S
enumeration NZGD_2000_UTM_Zone_59S
enumeration NZGD_2000_UTM_Zone_60S
enumeration Observ_Meteorologico_1939_UTM_Zone_25N
enumeration Old_Hawaiian_UTM_Zone_4N
enumeration Old_Hawaiian_UTM_Zone_5N
enumeration PDO_1993_UTM_Zone_39N
enumeration PDO_1993_UTM_Zone_40N
enumeration Pointe_Noire_UTM_Zone_32S
enumeration Porto_Santo_1936_UTM_Zone_28N
enumeration PSAD_1956_UTM_Zone_17S
enumeration PSAD_1956_UTM_Zone_18N
enumeration PSAD_1956_UTM_Zone_18S
enumeration PSAD_1956_UTM_Zone_19N
enumeration PSAD_1956_UTM_Zone_19S
enumeration PSAD_1956_UTM_Zone_20N
enumeration PSAD_1956_UTM_Zone_20S
enumeration PSAD_1956_UTM_Zone_21N
enumeration PSAD_1956_UTM_Zone_22S
enumeration Puerto_Rico_UTM_Zone_20N
enumeration Samboja_UTM_Zone_50S
enumeration Sao_Braz_UTM_Zone_26N
enumeration Sapper_Hill_1943_UTM_Zone_20S
enumeration Sapper_Hill_1943_UTM_Zone_21S
enumeration Schwarzeck_UTM_Zone_33S
enumeration Selvagem_Grande_1938_UTM_Zone_28N
enumeration Sierra_Leone_1968_UTM_Zone_28N
enumeration Sierra_Leone_1968_UTM_Zone_29N
enumeration SIRGAS_UTM_Zone_17N
enumeration SIRGAS_UTM_Zone_17S
enumeration SIRGAS_UTM_Zone_18N
enumeration SIRGAS_UTM_Zone_18S
enumeration SIRGAS_UTM_Zone_19N
enumeration SIRGAS_UTM_Zone_19S
enumeration SIRGAS_UTM_Zone_20N
enumeration SIRGAS_UTM_Zone_20S
enumeration SIRGAS_UTM_Zone_21N
enumeration SIRGAS_UTM_Zone_21S
enumeration SIRGAS_UTM_Zone_22N
enumeration SIRGAS_UTM_Zone_22S
enumeration SIRGAS_UTM_Zone_23S
enumeration SIRGAS_UTM_Zone_24S
enumeration SIRGAS_UTM_Zone_25S
enumeration SAD_1969_UTM_Zone_17S
enumeration SAD_1969_UTM_Zone_18N
enumeration SAD_1969_UTM_Zone_18S
enumeration SAD_1969_UTM_Zone_19N
enumeration SAD_1969_UTM_Zone_19S
enumeration SAD_1969_UTM_Zone_20N
enumeration SAD_1969_UTM_Zone_20S
enumeration SAD_1969_UTM_Zone_21N
enumeration SAD_1969_UTM_Zone_21S
enumeration SAD_1969_UTM_Zone_22N
enumeration SAD_1969_UTM_Zone_22S
enumeration SAD_1969_UTM_Zone_23S
enumeration SAD_1969_UTM_Zone_24S
enumeration SAD_1969_UTM_Zone_25S
enumeration Sudan_UTM_Zone_35N
enumeration Sudan_UTM_Zone_36N
enumeration Tananarive_1925_UTM_Zone_38S
enumeration Tananarive_1925_UTM_Zone_39S
enumeration Tete_UTM_Zone_36S
enumeration Tete_UTM_Zone_37S
enumeration Timbalai_1948_UTM_Zone_49N
enumeration Timbalai_1948_UTM_Zone_50N
enumeration Tokyo_UTM_Zone_51N
enumeration Tokyo_UTM_Zone_52N
enumeration Tokyo_UTM_Zone_53N
enumeration Tokyo_UTM_Zone_54N
enumeration Tokyo_UTM_Zone_55N
enumeration Tokyo_UTM_Zone_56N
enumeration TC_1948_UTM_Zone_39N
enumeration TC_1948_UTM_Zone_40N
enumeration Yemen_NGN_1996_UTM_Zone_38N
enumeration Yemen_NGN_1996_UTM_Zone_39N
enumeration Yoff_1972_UTM_Zone_28N
enumeration Zanderij_1972_UTM_Zone_21N
enumeration WGS_1972_UTM_Zone_10N
enumeration WGS_1972_UTM_Zone_10S
enumeration WGS_1972_UTM_Zone_11N
enumeration WGS_1972_UTM_Zone_11S
enumeration WGS_1972_UTM_Zone_12N
enumeration WGS_1972_UTM_Zone_12S
enumeration WGS_1972_UTM_Zone_13N
enumeration WGS_1972_UTM_Zone_13S
enumeration WGS_1972_UTM_Zone_14N
enumeration WGS_1972_UTM_Zone_14S
enumeration WGS_1972_UTM_Zone_15N
enumeration WGS_1972_UTM_Zone_15S
enumeration WGS_1972_UTM_Zone_16N
enumeration WGS_1972_UTM_Zone_16S
enumeration WGS_1972_UTM_Zone_17N
enumeration WGS_1972_UTM_Zone_17S
enumeration WGS_1972_UTM_Zone_18N
enumeration WGS_1972_UTM_Zone_18S
enumeration WGS_1972_UTM_Zone_19N
enumeration WGS_1972_UTM_Zone_19S
enumeration WGS_1972_UTM_Zone_1N
enumeration WGS_1972_UTM_Zone_1S
enumeration WGS_1972_UTM_Zone_20N
enumeration WGS_1972_UTM_Zone_20S
enumeration WGS_1972_UTM_Zone_21N
enumeration WGS_1972_UTM_Zone_21S
enumeration WGS_1972_UTM_Zone_22N
enumeration WGS_1972_UTM_Zone_22S
enumeration WGS_1972_UTM_Zone_23N
enumeration WGS_1972_UTM_Zone_23S
enumeration WGS_1972_UTM_Zone_24N
enumeration WGS_1972_UTM_Zone_24S
enumeration WGS_1972_UTM_Zone_25N
enumeration WGS_1972_UTM_Zone_25S
enumeration WGS_1972_UTM_Zone_26N
enumeration WGS_1972_UTM_Zone_26S
enumeration WGS_1972_UTM_Zone_27N
enumeration WGS_1972_UTM_Zone_27S
enumeration WGS_1972_UTM_Zone_28N
enumeration WGS_1972_UTM_Zone_28S
enumeration WGS_1972_UTM_Zone_29N
enumeration WGS_1972_UTM_Zone_29S
enumeration WGS_1972_UTM_Zone_2N
enumeration WGS_1972_UTM_Zone_2S
enumeration WGS_1972_UTM_Zone_30N
enumeration WGS_1972_UTM_Zone_30S
enumeration WGS_1972_UTM_Zone_31N
enumeration WGS_1972_UTM_Zone_31S
enumeration WGS_1972_UTM_Zone_32N
enumeration WGS_1972_UTM_Zone_32S
enumeration WGS_1972_UTM_Zone_33N
enumeration WGS_1972_UTM_Zone_33S
enumeration WGS_1972_UTM_Zone_34N
enumeration WGS_1972_UTM_Zone_34S
enumeration WGS_1972_UTM_Zone_35N
enumeration WGS_1972_UTM_Zone_35S
enumeration WGS_1972_UTM_Zone_36N
enumeration WGS_1972_UTM_Zone_36S
enumeration WGS_1972_UTM_Zone_37N
enumeration WGS_1972_UTM_Zone_37S
enumeration WGS_1972_UTM_Zone_38N
enumeration WGS_1972_UTM_Zone_38S
enumeration WGS_1972_UTM_Zone_39N
enumeration WGS_1972_UTM_Zone_39S
enumeration WGS_1972_UTM_Zone_3N
enumeration WGS_1972_UTM_Zone_3S
enumeration WGS_1972_UTM_Zone_40N
enumeration WGS_1972_UTM_Zone_40S
enumeration WGS_1972_UTM_Zone_41N
enumeration WGS_1972_UTM_Zone_41S
enumeration WGS_1972_UTM_Zone_42N
enumeration WGS_1972_UTM_Zone_42S
enumeration WGS_1972_UTM_Zone_43N
enumeration WGS_1972_UTM_Zone_43S
enumeration WGS_1972_UTM_Zone_44N
enumeration WGS_1972_UTM_Zone_44S
enumeration WGS_1972_UTM_Zone_45N
enumeration WGS_1972_UTM_Zone_45S
enumeration WGS_1972_UTM_Zone_46N
enumeration WGS_1972_UTM_Zone_46S
enumeration WGS_1972_UTM_Zone_47N
enumeration WGS_1972_UTM_Zone_47S
enumeration WGS_1972_UTM_Zone_48N
enumeration WGS_1972_UTM_Zone_48S
enumeration WGS_1972_UTM_Zone_49N
enumeration WGS_1972_UTM_Zone_49S
enumeration WGS_1972_UTM_Zone_4N
enumeration WGS_1972_UTM_Zone_4S
enumeration WGS_1972_UTM_Zone_50N
enumeration WGS_1972_UTM_Zone_50S
enumeration WGS_1972_UTM_Zone_51N
enumeration WGS_1972_UTM_Zone_51S
enumeration WGS_1972_UTM_Zone_52N
enumeration WGS_1972_UTM_Zone_52S
enumeration WGS_1972_UTM_Zone_53N
enumeration WGS_1972_UTM_Zone_53S
enumeration WGS_1972_UTM_Zone_54N
enumeration WGS_1972_UTM_Zone_54S
enumeration WGS_1972_UTM_Zone_55N
enumeration WGS_1972_UTM_Zone_55S
enumeration WGS_1972_UTM_Zone_56N
enumeration WGS_1972_UTM_Zone_56S
enumeration WGS_1972_UTM_Zone_57N
enumeration WGS_1972_UTM_Zone_57S
enumeration WGS_1972_UTM_Zone_58N
enumeration WGS_1972_UTM_Zone_58S
enumeration WGS_1972_UTM_Zone_59N
enumeration WGS_1972_UTM_Zone_59S
enumeration WGS_1972_UTM_Zone_5N
enumeration WGS_1972_UTM_Zone_5S
enumeration WGS_1972_UTM_Zone_60N
enumeration WGS_1972_UTM_Zone_60S
enumeration WGS_1972_UTM_Zone_6N
enumeration WGS_1972_UTM_Zone_6S
enumeration WGS_1972_UTM_Zone_7N
enumeration WGS_1972_UTM_Zone_7S
enumeration WGS_1972_UTM_Zone_8N
enumeration WGS_1972_UTM_Zone_8S
enumeration WGS_1972_UTM_Zone_9N
enumeration WGS_1972_UTM_Zone_9S
enumeration WGS_1984_UTM_Zone_10N
enumeration WGS_1984_UTM_Zone_10S
enumeration WGS_1984_UTM_Zone_11N
enumeration WGS_1984_UTM_Zone_11S
enumeration WGS_1984_UTM_Zone_12N
enumeration WGS_1984_UTM_Zone_12S
enumeration WGS_1984_UTM_Zone_13N
enumeration WGS_1984_UTM_Zone_13S
enumeration WGS_1984_UTM_Zone_14N
enumeration WGS_1984_UTM_Zone_14S
enumeration WGS_1984_UTM_Zone_15N
enumeration WGS_1984_UTM_Zone_15S
enumeration WGS_1984_UTM_Zone_16N
enumeration WGS_1984_UTM_Zone_16S
enumeration WGS_1984_UTM_Zone_17N
enumeration WGS_1984_UTM_Zone_17S
enumeration WGS_1984_UTM_Zone_18N
enumeration WGS_1984_UTM_Zone_18S
enumeration WGS_1984_UTM_Zone_19N
enumeration WGS_1984_UTM_Zone_19S
enumeration WGS_1984_UTM_Zone_1N
enumeration WGS_1984_UTM_Zone_1S
enumeration WGS_1984_UTM_Zone_20N
enumeration WGS_1984_UTM_Zone_20S
enumeration WGS_1984_UTM_Zone_21N
enumeration WGS_1984_UTM_Zone_21S
enumeration WGS_1984_UTM_Zone_22N
enumeration WGS_1984_UTM_Zone_22S
enumeration WGS_1984_UTM_Zone_23N
enumeration WGS_1984_UTM_Zone_23S
enumeration WGS_1984_UTM_Zone_24N
enumeration WGS_1984_UTM_Zone_24S
enumeration WGS_1984_UTM_Zone_25N
enumeration WGS_1984_UTM_Zone_25S
enumeration WGS_1984_UTM_Zone_26N
enumeration WGS_1984_UTM_Zone_26S
enumeration WGS_1984_UTM_Zone_27N
enumeration WGS_1984_UTM_Zone_27S
enumeration WGS_1984_UTM_Zone_28N
enumeration WGS_1984_UTM_Zone_28S
enumeration WGS_1984_UTM_Zone_29N
enumeration WGS_1984_UTM_Zone_29S
enumeration WGS_1984_UTM_Zone_2N
enumeration WGS_1984_UTM_Zone_2S
enumeration WGS_1984_UTM_Zone_30N
enumeration WGS_1984_UTM_Zone_30S
enumeration WGS_1984_UTM_Zone_31N
enumeration WGS_1984_UTM_Zone_31S
enumeration WGS_1984_UTM_Zone_32N
enumeration WGS_1984_UTM_Zone_32S
enumeration WGS_1984_UTM_Zone_33N
enumeration WGS_1984_UTM_Zone_33S
enumeration WGS_1984_UTM_Zone_34N
enumeration WGS_1984_UTM_Zone_34S
enumeration WGS_1984_UTM_Zone_35N
enumeration WGS_1984_UTM_Zone_35S
enumeration WGS_1984_UTM_Zone_36N
enumeration WGS_1984_UTM_Zone_36S
enumeration WGS_1984_UTM_Zone_37N
enumeration WGS_1984_UTM_Zone_37S
enumeration WGS_1984_UTM_Zone_38N
enumeration WGS_1984_UTM_Zone_38S
enumeration WGS_1984_UTM_Zone_39N
enumeration WGS_1984_UTM_Zone_39S
enumeration WGS_1984_UTM_Zone_3N
enumeration WGS_1984_UTM_Zone_3S
enumeration WGS_1984_UTM_Zone_40N
enumeration WGS_1984_UTM_Zone_40S
enumeration WGS_1984_UTM_Zone_41N
enumeration WGS_1984_UTM_Zone_41S
enumeration WGS_1984_UTM_Zone_42N
enumeration WGS_1984_UTM_Zone_42S
enumeration WGS_1984_UTM_Zone_43N
enumeration WGS_1984_UTM_Zone_43S
enumeration WGS_1984_UTM_Zone_44N
enumeration WGS_1984_UTM_Zone_44S
enumeration WGS_1984_UTM_Zone_45N
enumeration WGS_1984_UTM_Zone_45S
enumeration WGS_1984_UTM_Zone_46N
enumeration WGS_1984_UTM_Zone_46S
enumeration WGS_1984_UTM_Zone_47N
enumeration WGS_1984_UTM_Zone_47S
enumeration WGS_1984_UTM_Zone_48N
enumeration WGS_1984_UTM_Zone_48S
enumeration WGS_1984_UTM_Zone_49N
enumeration WGS_1984_UTM_Zone_49S
enumeration WGS_1984_UTM_Zone_4N
enumeration WGS_1984_UTM_Zone_4S
enumeration WGS_1984_UTM_Zone_50N
enumeration WGS_1984_UTM_Zone_50S
enumeration WGS_1984_UTM_Zone_51N
enumeration WGS_1984_UTM_Zone_51S
enumeration WGS_1984_UTM_Zone_52N
enumeration WGS_1984_UTM_Zone_52S
enumeration WGS_1984_UTM_Zone_53N
enumeration WGS_1984_UTM_Zone_53S
enumeration WGS_1984_UTM_Zone_54N
enumeration WGS_1984_UTM_Zone_54S
enumeration WGS_1984_UTM_Zone_55N
enumeration WGS_1984_UTM_Zone_55S
enumeration WGS_1984_UTM_Zone_56N
enumeration WGS_1984_UTM_Zone_56S
enumeration WGS_1984_UTM_Zone_57N
enumeration WGS_1984_UTM_Zone_57S
enumeration WGS_1984_UTM_Zone_58N
enumeration WGS_1984_UTM_Zone_58S
enumeration WGS_1984_UTM_Zone_59N
enumeration WGS_1984_UTM_Zone_59S
enumeration WGS_1984_UTM_Zone_5N
enumeration WGS_1984_UTM_Zone_5S
enumeration WGS_1984_UTM_Zone_60N
enumeration WGS_1984_UTM_Zone_60S
enumeration WGS_1984_UTM_Zone_6N
enumeration WGS_1984_UTM_Zone_6S
enumeration WGS_1984_UTM_Zone_7N
enumeration WGS_1984_UTM_Zone_7S
enumeration WGS_1984_UTM_Zone_8N
enumeration WGS_1984_UTM_Zone_8S
enumeration WGS_1984_UTM_Zone_9N
enumeration WGS_1984_UTM_Zone_9S
enumeration World_Aitoff
enumeration World_Behrmann
enumeration World_Bonne
enumeration World_Craster_Parabolic
enumeration World_Cylindrical_Equal_Area
enumeration World_Eckert_I
enumeration World_Eckert_II
enumeration World_Eckert_III
enumeration World_Eckert_IV
enumeration World_Eckert_V
enumeration World_Eckert_VI
enumeration World_Equidistant_Conic
enumeration World_Equidistant_Cylindrical
enumeration World_Flat_Polar_Quartic
enumeration World_Gall_Stereographic
enumeration World_Hammer_Aitoff
enumeration World_Loximuthal
enumeration World_Mercator
enumeration World_Miller_Cylindrical
enumeration World_Mollweide
enumeration World_Plate_Carree
enumeration World_Polyconic
enumeration World_Quartic_Authalic
enumeration World_Robinson
enumeration World_Sinusoidal
enumeration Sphere_Aitoff
enumeration Sphere_Behrmann
enumeration Sphere_Bonne
enumeration Sphere_Craster_Parabolic
enumeration Sphere_Cylindrical_Equal_Area
enumeration Sphere_Eckert_I
enumeration Sphere_Eckert_II
enumeration Sphere_Eckert_III
enumeration Sphere_Eckert_IV
enumeration Sphere_Eckert_V
enumeration Sphere_Eckert_VI
enumeration Sphere_Equidistant_Conic
enumeration Sphere_Equidistant_Cylindrical
enumeration Sphere_Flat_Polar_Quartic
enumeration Sphere_Gall_Stereographic
enumeration Sphere_Hammer_Aitoff
enumeration Sphere_Loximuthal
enumeration Sphere_Mercator
enumeration Sphere_Miller_Cylindrical
enumeration Sphere_Mollweide
enumeration Sphere_Plate_Carree
enumeration Sphere_Polyconic
enumeration Sphere_Quartic_Authalic
enumeration Sphere_Robinson
enumeration Sphere_Sinusoidal
enumeration Sphere_Times
enumeration Sphere_Van_der_Grinten_I
enumeration Sphere_Vertical_Perspective
enumeration Sphere_Winkel_I
enumeration Sphere_Winkel_II
enumeration Sphere_Winkel_Tripel_NGS
enumeration The_World_From_Space
enumeration World_Times
enumeration World_Van_der_Grinten_I
enumeration World_Vertical_Perspective
enumeration World_Winkel_I
enumeration World_Winkel_II
enumeration World_Winkel_Tripel_NGS
Source
<xs:element name="horizCoordSysName">
  <xs:annotation>
    <xs:documentation>tooltip: Horizonal Coordinate System Name summary: The name of a predefined coordinate system description: The name of a coordinate system for which a definition has been provided in the eml-spatialReferenceDictionary.xml file.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="GCS_Abidjan_1987"/>
      <xs:enumeration value="GCS_Accra"/>
      <xs:enumeration value="GCS_Adindan"/>
      <xs:enumeration value="GCS_Afgooye"/>
      <xs:enumeration value="GCS_Agadez"/>
      <xs:enumeration value="GCS_Ain_el_Abd_1970"/>
      <xs:enumeration value="GCS_Arc_1950"/>
      <xs:enumeration value="GCS_Arc_1960"/>
      <xs:enumeration value="GCS_Ayabelle"/>
      <xs:enumeration value="GCS_Beduaram"/>
      <xs:enumeration value="GCS_Bissau"/>
      <xs:enumeration value="GCS_Camacupa"/>
      <xs:enumeration value="GCS_Cape"/>
      <xs:enumeration value="GCS_Carthage_Degree"/>
      <xs:enumeration value="GCS_Carthage_Paris"/>
      <xs:enumeration value="GCS_Carthage"/>
      <xs:enumeration value="GCS_Conakry_1905"/>
      <xs:enumeration value="GCS_Cote_d_Ivoire"/>
      <xs:enumeration value="GCS_Dabola"/>
      <xs:enumeration value="GCS_Douala"/>
      <xs:enumeration value="GCS_Egypt_1907"/>
      <xs:enumeration value="GCS_European_1950"/>
      <xs:enumeration value="GCS_European_Libyan_Datum_1979"/>
      <xs:enumeration value="GCS_Garoua"/>
      <xs:enumeration value="GCS_Hartebeesthoek_1994"/>
      <xs:enumeration value="GCS_Kuwait_Oil_Company"/>
      <xs:enumeration value="GCS_KUDAMS"/>
      <xs:enumeration value="GCS_Leigon"/>
      <xs:enumeration value="GCS_Liberia_1964"/>
      <xs:enumeration value="GCS_Locodjo_1965"/>
      <xs:enumeration value="GCS_Lome"/>
      <xs:enumeration value="GCS_Mporaloko"/>
      <xs:enumeration value="GCS_Madzansua"/>
      <xs:enumeration value="GCS_Mahe_1971"/>
      <xs:enumeration value="GCS_Malongo_1987"/>
      <xs:enumeration value="GCS_Manoca"/>
      <xs:enumeration value="GCS_Massawa"/>
      <xs:enumeration value="GCS_Merchich_Degree"/>
      <xs:enumeration value="GCS_Merchich"/>
      <xs:enumeration value="GCS_Mhast"/>
      <xs:enumeration value="GCS_Minna"/>
      <xs:enumeration value="GCS_Moznet"/>
      <xs:enumeration value="GCS_Nahrwan_1967"/>
      <xs:enumeration value="GCS_NGN"/>
      <xs:enumeration value="GCS_Nord_Sahara_1959"/>
      <xs:enumeration value="GCS_Observatario"/>
      <xs:enumeration value="GCS_Oman"/>
      <xs:enumeration value="GCS_Palestine_1923"/>
      <xs:enumeration value="GCS_PDO_1993"/>
      <xs:enumeration value="GCS_Point_58"/>
      <xs:enumeration value="GCS_Pointe_Noire"/>
      <xs:enumeration value="GCS_Qatar_1948"/>
      <xs:enumeration value="GCS_Qatar"/>
      <xs:enumeration value="GCS_Schwarzeck"/>
      <xs:enumeration value="GCS_Sierra_Leone_1924"/>
      <xs:enumeration value="GCS_Sierra_Leone_1960"/>
      <xs:enumeration value="GCS_Sierra_Leone_1968"/>
      <xs:enumeration value="GCS_South_Yemen"/>
      <xs:enumeration value="GCS_Sudan"/>
      <xs:enumeration value="GCS_Tananarive_1925_Paris"/>
      <xs:enumeration value="GCS_Tananarive_1925"/>
      <xs:enumeration value="GCS_Tete"/>
      <xs:enumeration value="GCS_Trucial_Coast_1948"/>
      <xs:enumeration value="GCS_Voirol_1875_Degree"/>
      <xs:enumeration value="GCS_Voirol_1875_Paris"/>
      <xs:enumeration value="GCS_Voirol_1875"/>
      <xs:enumeration value="GCS_Voirol_Unifie_1960_Degree"/>
      <xs:enumeration value="GCS_Voirol_Unifie_1960_Paris"/>
      <xs:enumeration value="GCS_Voirol_Unifie_1960"/>
      <xs:enumeration value="GCS_Yemen_NGN_1996"/>
      <xs:enumeration value="GCS_Yoff"/>
      <xs:enumeration value="GCS_Camp_Area"/>
      <xs:enumeration value="GCS_Deception_Island"/>
      <xs:enumeration value="GCS_Ain_el_Abd_1970"/>
      <xs:enumeration value="GCS_Batavia_Jakarta"/>
      <xs:enumeration value="GCS_Batavia"/>
      <xs:enumeration value="GCS_Beijing_1954"/>
      <xs:enumeration value="GCS_Bukit_Rimpah"/>
      <xs:enumeration value="GCS_Deir_ez_Zor"/>
      <xs:enumeration value="GCS_European_1950_ED77"/>
      <xs:enumeration value="GCS_European_1950"/>
      <xs:enumeration value="GCS_Everest_def_1962"/>
      <xs:enumeration value="GCS_Everest_def_1967"/>
      <xs:enumeration value="GCS_Everest_def_1975"/>
      <xs:enumeration value="GCS_Everest_Bangladesh"/>
      <xs:enumeration value="GCS_Everest_India_Nepal"/>
      <xs:enumeration value="GCS_Everest_1830"/>
      <xs:enumeration value="GCS_Everest_Modified"/>
      <xs:enumeration value="GCS_Fahud"/>
      <xs:enumeration value="GCS_FD_1958"/>
      <xs:enumeration value="GCS_Gandajika_1970"/>
      <xs:enumeration value="GCS_Gunung_Segara"/>
      <xs:enumeration value="GCS_Hanoi_1972"/>
      <xs:enumeration value="GCS_Herat_North"/>
      <xs:enumeration value="GCS_Hong_Kong_1963"/>
      <xs:enumeration value="GCS_Hong_Kong_1980"/>
      <xs:enumeration value="GCS_Hu_Tzu_Shan"/>
      <xs:enumeration value="GCS_Indian_1954"/>
      <xs:enumeration value="GCS_Indian_1960"/>
      <xs:enumeration value="GCS_Indian_1975"/>
      <xs:enumeration value="GCS_Indonesian_1974"/>
      <xs:enumeration value="GCS_Israel"/>
      <xs:enumeration value="GCS_JGD_2000"/>
      <xs:enumeration value="GCS_Kalianpur_1880"/>
      <xs:enumeration value="GCS_Kalianpur_1937"/>
      <xs:enumeration value="GCS_Kalianpur_1962"/>
      <xs:enumeration value="GCS_Kalianpur_1975"/>
      <xs:enumeration value="GCS_Kandawala"/>
      <xs:enumeration value="GCS_Kertau"/>
      <xs:enumeration value="GCS_Korean_Datum_1985"/>
      <xs:enumeration value="GCS_Korean_Datum_1995"/>
      <xs:enumeration value="GCS_Kuwait_Oil_Company"/>
      <xs:enumeration value="GCS_KUDAMS"/>
      <xs:enumeration value="GCS_Luzon_1911"/>
      <xs:enumeration value="GCS_Makassar_Jakarta"/>
      <xs:enumeration value="GCS_Makassar"/>
      <xs:enumeration value="GCS_Nahrwan_1967"/>
      <xs:enumeration value="GCS_NGN"/>
      <xs:enumeration value="GCS_Oman"/>
      <xs:enumeration value="GCS_Padang_1884_Jakarta"/>
      <xs:enumeration value="GCS_Padang_1884"/>
      <xs:enumeration value="GCS_Palestine_1923"/>
      <xs:enumeration value="GCS_Pulkovo_1942"/>
      <xs:enumeration value="GCS_Pulkovo_1995"/>
      <xs:enumeration value="GCS_Qatar_1948"/>
      <xs:enumeration value="GCS_Qatar"/>
      <xs:enumeration value="GCS_Rassadiran"/>
      <xs:enumeration value="GCS_Samboja"/>
      <xs:enumeration value="GCS_Segora"/>
      <xs:enumeration value="GCS_Serindung"/>
      <xs:enumeration value="GCS_South_Asia_Singapore"/>
      <xs:enumeration value="GCS_Timbalai_1948"/>
      <xs:enumeration value="GCS_Tokyo"/>
      <xs:enumeration value="GCS_Trucial_Coast_1948"/>
      <xs:enumeration value="GCS_Australian_1966"/>
      <xs:enumeration value="GCS_Australian_1984"/>
      <xs:enumeration value="GCS_GDA_1994"/>
      <xs:enumeration value="GCS_New_Zealand_1949"/>
      <xs:enumeration value="GCS_NZGD_2000"/>
      <xs:enumeration value="GCS_Amersfoort"/>
      <xs:enumeration value="GCS_ATF_Paris"/>
      <xs:enumeration value="GCS_Belge_1950_Brussels"/>
      <xs:enumeration value="GCS_Belge_1972"/>
      <xs:enumeration value="GCS_Bern_1898_Bern"/>
      <xs:enumeration value="GCS_Bern_1898"/>
      <xs:enumeration value="GCS_Bern_1938"/>
      <xs:enumeration value="GCS_CH1903+"/>
      <xs:enumeration value="GCS_CH1903"/>
      <xs:enumeration value="GCS_Datum_73"/>
      <xs:enumeration value="GCS_Datum_Lisboa_Bessel"/>
      <xs:enumeration value="GCS_Datum_Lisboa_Bessel"/>
      <xs:enumeration value="GCS_Dealul_Piscului_1933"/>
      <xs:enumeration value="GCS_Dealul_Piscului_1970"/>
      <xs:enumeration value="GCS_Deutsche_Hauptdreiecksnetz"/>
      <xs:enumeration value="GCS_Estonia_1937"/>
      <xs:enumeration value="GCS_Estonia_1992"/>
      <xs:enumeration value="GCS_ETRF_1989"/>
      <xs:enumeration value="GCS_European_1979"/>
      <xs:enumeration value="GCS_European_1950"/>
      <xs:enumeration value="GCS_European_1987"/>
      <xs:enumeration value="GCS_Greek_Athens"/>
      <xs:enumeration value="GCS_Greek"/>
      <xs:enumeration value="GCS_Hermannskogel"/>
      <xs:enumeration value="GCS_Hjorsey_1955"/>
      <xs:enumeration value="GCS_Hungarian_1972"/>
      <xs:enumeration value="GCS_IRENET95"/>
      <xs:enumeration value="GCS_KKJ"/>
      <xs:enumeration value="GCS_Lisbon_Lisbon"/>
      <xs:enumeration value="GCS_Lisbon"/>
      <xs:enumeration value="GCS_LKS_1994"/>
      <xs:enumeration value="GCS_Madrid_1870_Madrid"/>
      <xs:enumeration value="GCS_MGI_Ferro"/>
      <xs:enumeration value="GCS_MGI"/>
      <xs:enumeration value="GCS_Monte_Mario_Rome"/>
      <xs:enumeration value="GCS_Monte_Mario"/>
      <xs:enumeration value="GCS_NGO_1948_Oslo"/>
      <xs:enumeration value="GCS_NGO_1948"/>
      <xs:enumeration value="GCS_Nord_de_Guerre_Paris"/>
      <xs:enumeration value="GCS_NTF"/>
      <xs:enumeration value="GCS_NTF_Paris"/>
      <xs:enumeration value="GCS_OS_SN_1980"/>
      <xs:enumeration value="GCS_OSGB_1936"/>
      <xs:enumeration value="GCS_OSGB_1970_SN"/>
      <xs:enumeration value="GCS_Pulkovo_1942"/>
      <xs:enumeration value="GCS_Pulkovo_1995"/>
      <xs:enumeration value="GCS_Qornoq"/>
      <xs:enumeration value="GCS_Belge_1950"/>
      <xs:enumeration value="GCS_Belge_1972"/>
      <xs:enumeration value="GCS_RGF_1993"/>
      <xs:enumeration value="GCS_RT_1990"/>
      <xs:enumeration value="GCS_RT38_Stockholm"/>
      <xs:enumeration value="GCS_RT38"/>
      <xs:enumeration value="GCS_S42_Hungary"/>
      <xs:enumeration value="GCS_S_JTSK"/>
      <xs:enumeration value="GCS_Swiss_TRF_1995"/>
      <xs:enumeration value="GCS_TM65"/>
      <xs:enumeration value="GCS_TM75"/>
      <xs:enumeration value="GCS_Alaskan_Islands"/>
      <xs:enumeration value="GCS_American_Samoa_1962"/>
      <xs:enumeration value="GCS_ATS_1977"/>
      <xs:enumeration value="GCS_Barbados"/>
      <xs:enumeration value="GCS_Bermuda_1957"/>
      <xs:enumeration value="GCS_Cape_Canaveral"/>
      <xs:enumeration value="GCS_Guam_1963"/>
      <xs:enumeration value="GCS_Jamaica_1875"/>
      <xs:enumeration value="GCS_Jamaica_1969"/>
      <xs:enumeration value="GCS_NAD_1927_CGQ77"/>
      <xs:enumeration value="GCS_NAD_1927_Definition_1976"/>
      <xs:enumeration value="GCS_North_American_Michigan"/>
      <xs:enumeration value="GCS_North_American_1983_CSRS98"/>
      <xs:enumeration value="GCS_North_American_1983_HARN"/>
      <xs:enumeration value="GCS_North_American_1927"/>
      <xs:enumeration value="GCS_North_American_1983"/>
      <xs:enumeration value="GCS_Old_Hawaiian"/>
      <xs:enumeration value="GCS_Puerto_Rico"/>
      <xs:enumeration value="GCS_Qornoq"/>
      <xs:enumeration value="GCS_St_George_Island"/>
      <xs:enumeration value="GCS_St_Lawrence_Island"/>
      <xs:enumeration value="GCS_St_Paul_Island"/>
      <xs:enumeration value="GCS_Alaskan_Islands"/>
      <xs:enumeration value="GCS_American_Samoa_1962"/>
      <xs:enumeration value="GCS_Anguilla_1957"/>
      <xs:enumeration value="GCS_Anna_1_1965"/>
      <xs:enumeration value="GCS_Antigua_1943"/>
      <xs:enumeration value="GCS_Ascension_Island_1958"/>
      <xs:enumeration value="GCS_Beacon_E_1945"/>
      <xs:enumeration value="GCS_DOS_71_4"/>
      <xs:enumeration value="GCS_Astro_1952"/>
      <xs:enumeration value="GCS_Bab_South"/>
      <xs:enumeration value="GCS_Barbados_1938"/>
      <xs:enumeration value="GCS_Barbados"/>
      <xs:enumeration value="GCS_Bellevue_IGN"/>
      <xs:enumeration value="GCS_Bermuda_1957"/>
      <xs:enumeration value="GCS_Canton_1966"/>
      <xs:enumeration value="GCS_Chatham_Island_1971"/>
      <xs:enumeration value="GCS_Dominica_1945"/>
      <xs:enumeration value="GCS_DOS_1968"/>
      <xs:enumeration value="GCS_Easter_Island_1967"/>
      <xs:enumeration value="GCS_Fort_Thomas_1955"/>
      <xs:enumeration value="GCS_Gan_1970"/>
      <xs:enumeration value="GCS_Graciosa_Base_SW_1948"/>
      <xs:enumeration value="GCS_Grenada_1953"/>
      <xs:enumeration value="GCS_Guam_1963"/>
      <xs:enumeration value="GCS_GUX_1"/>
      <xs:enumeration value="GCS_Hjorsey_1955"/>
      <xs:enumeration value="GCS_ISTS_061_1968"/>
      <xs:enumeration value="GCS_ISTS_073_1969"/>
      <xs:enumeration value="GCS_Jamaica_1875"/>
      <xs:enumeration value="GCS_Jamaica_1969"/>
      <xs:enumeration value="GCS_Johnston_Island_1961"/>
      <xs:enumeration value="GCS_Kerguelen_Island_1949"/>
      <xs:enumeration value="GCS_Kusaie_1951"/>
      <xs:enumeration value="GCS_LC5_1961"/>
      <xs:enumeration value="GCS_Mahe_1971"/>
      <xs:enumeration value="GCS_Majuro"/>
      <xs:enumeration value="GCS_Midway_1961"/>
      <xs:enumeration value="GCS_Montserrat_1958"/>
      <xs:enumeration value="GCS_Observ_Meteorologico_1939"/>
      <xs:enumeration value="GCS_Old_Hawaiian"/>
      <xs:enumeration value="GCS_Pico_de_Las_Nieves"/>
      <xs:enumeration value="GCS_Pitcairn_1967"/>
      <xs:enumeration value="GCS_Pohnpei"/>
      <xs:enumeration value="GCS_Porto_Santo_1936"/>
      <xs:enumeration value="GCS_Puerto_Rico"/>
      <xs:enumeration value="GCS_Reunion"/>
      <xs:enumeration value="GCS_Santo_DOS_1965"/>
      <xs:enumeration value="GCS_Sao_Braz"/>
      <xs:enumeration value="GCS_Sapper_Hill_1943"/>
      <xs:enumeration value="GCS_Selvagem_Grande_1938"/>
      <xs:enumeration value="GCS_St_Kitts_1955"/>
      <xs:enumeration value="GCS_St_Lucia_1955"/>
      <xs:enumeration value="GCS_St_Vincent_1945"/>
      <xs:enumeration value="GCS_Tern_Island_1961"/>
      <xs:enumeration value="GCS_Tristan_1968"/>
      <xs:enumeration value="GCS_Viti_Levu_1916"/>
      <xs:enumeration value="GCS_Wake_Island_1952"/>
      <xs:enumeration value="GCS_Wake_Eniwetok_1960"/>
      <xs:enumeration value="GCS_Aratu"/>
      <xs:enumeration value="GCS_Bogota_Bogota"/>
      <xs:enumeration value="GCS_Bogota"/>
      <xs:enumeration value="GCS_Campo_Inchauspe"/>
      <xs:enumeration value="GCS_Chos_Malal_1914"/>
      <xs:enumeration value="GCS_Chua"/>
      <xs:enumeration value="GCS_Corrego_Alegre"/>
      <xs:enumeration value="GCS_Guyane_Francaise"/>
      <xs:enumeration value="GCS_Hito_XVIII_1963"/>
      <xs:enumeration value="GCS_La_Canoa"/>
      <xs:enumeration value="GCS_Lake"/>
      <xs:enumeration value="GCS_Loma_Quintana"/>
      <xs:enumeration value="GCS_Mount_Dillon"/>
      <xs:enumeration value="GCS_Naparima_1955"/>
      <xs:enumeration value="GCS_Naparima_1972"/>
      <xs:enumeration value="GCS_Pampa_del_Castillo"/>
      <xs:enumeration value="GCS_POSGAR"/>
      <xs:enumeration value="GCS_REGVEN"/>
      <xs:enumeration value="GCS_Sapper_Hill_1943"/>
      <xs:enumeration value="GCS_SIRGAS"/>
      <xs:enumeration value="GCS_South_American_1969"/>
      <xs:enumeration value="GCS_Trinidad_1903"/>
      <xs:enumeration value="GCS_Yacare"/>
      <xs:enumeration value="GCS_Zanderij"/>
      <xs:enumeration value="GCS_Airy_1830"/>
      <xs:enumeration value="GCS_Airy_Modified"/>
      <xs:enumeration value="GCS_Australian"/>
      <xs:enumeration value="GCS_Sphere_ARC_INFO"/>
      <xs:enumeration value="GCS_Sphere"/>
      <xs:enumeration value="GCS_ATS_1977"/>
      <xs:enumeration value="GCS_Bessel_1841"/>
      <xs:enumeration value="GCS_Bessel_Modified"/>
      <xs:enumeration value="GCS_Bessel_Namibia"/>
      <xs:enumeration value="GCS_Clarke_1858"/>
      <xs:enumeration value="GCS_Clarke_1866_Michigan"/>
      <xs:enumeration value="GCS_Clarke_1866"/>
      <xs:enumeration value="GCS_Clarke_1880_Arc"/>
      <xs:enumeration value="GCS_Clarke_1880_Benoit"/>
      <xs:enumeration value="GCS_Clarke_1880_IGN"/>
      <xs:enumeration value="GCS_Clarke_1880_RGS"/>
      <xs:enumeration value="GCS_Clarke_1880_SGA"/>
      <xs:enumeration value="GCS_Clarke_1880"/>
      <xs:enumeration value="GCS_Everest_def_1967"/>
      <xs:enumeration value="GCS_Everest_def_1975"/>
      <xs:enumeration value="GCS_Everest_1830"/>
      <xs:enumeration value="GCS_Everest_Modified_1969"/>
      <xs:enumeration value="GCS_Everest_Modified"/>
      <xs:enumeration value="GCS_Fischer_1960"/>
      <xs:enumeration value="GCS_Fischer_1968"/>
      <xs:enumeration value="GCS_Fischer_Modified"/>
      <xs:enumeration value="GCS_GEM_10C"/>
      <xs:enumeration value="GCS_GRS_1967"/>
      <xs:enumeration value="GCS_GRS_1980"/>
      <xs:enumeration value="GCS_Helmert_1906"/>
      <xs:enumeration value="GCS_Hough_1960"/>
      <xs:enumeration value="GCS_Indonesian"/>
      <xs:enumeration value="GCS_International_1924"/>
      <xs:enumeration value="GCS_International_1967"/>
      <xs:enumeration value="GCS_Krasovsky_1940"/>
      <xs:enumeration value="GCS_OSU_86F"/>
      <xs:enumeration value="GCS_OSU_91A"/>
      <xs:enumeration value="GCS_Plessis_1817"/>
      <xs:enumeration value="GCS_Struve_1860"/>
      <xs:enumeration value="GCS_NWL_9D"/>
      <xs:enumeration value="GCS_Walbeck"/>
      <xs:enumeration value="GCS_War_Office"/>
      <xs:enumeration value="GCS_WGS_1966"/>
      <xs:enumeration value="GCS_NSWC_9Z_2"/>
      <xs:enumeration value="GCS_WGS_1966"/>
      <xs:enumeration value="GCS_WGS_1972_BE"/>
      <xs:enumeration value="GCS_WGS_1972"/>
      <xs:enumeration value="GCS_WGS_1984"/>
      <xs:enumeration value="Africa_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="Africa_Equidistant_Conic"/>
      <xs:enumeration value="Africa_Lambert_Conformal_Conic"/>
      <xs:enumeration value="Africa_Sinusoidal"/>
      <xs:enumeration value="Asia_Lambert_Conformal_Conic"/>
      <xs:enumeration value="Asia_North_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="Asia_North_Equidistant_Conic"/>
      <xs:enumeration value="Asia_North_Lambert_Conformal_Conic"/>
      <xs:enumeration value="Asia_South_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="Asia_South_Equidistant_Conic"/>
      <xs:enumeration value="Asia_South_Lambert_Conformal_Conic"/>
      <xs:enumeration value="Europe_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="Europe_Equidistant_Conic"/>
      <xs:enumeration value="Europe_Lambert_Conformal_Conic"/>
      <xs:enumeration value="Alaska_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="Canada_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="Canada_Lambert_Conformal_Conic"/>
      <xs:enumeration value="Hawaii_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="North_America_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="North_America_Equidistant_Conic"/>
      <xs:enumeration value="North_America_Lambert_Conformal_Conic"/>
      <xs:enumeration value="USA_Contiguous_Albers_Equal_Area_Conic_USGS_version"/>
      <xs:enumeration value="USA_Contiguous_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="USA_Contiguous_Equidistant_Conic"/>
      <xs:enumeration value="USA_Contiguous_Lambert_Conformal_Conic"/>
      <xs:enumeration value="South_America_Albers_Equal_Area_Conic"/>
      <xs:enumeration value="South_America_Equidistant_Conic"/>
      <xs:enumeration value="South_America_Lambert_Conformal_Conic"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_13"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_13N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_14"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_14N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_15"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_15N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_16"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_16N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_17"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_17N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_18"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_18N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_19"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_19N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_20"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_20N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_21"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_21N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_22"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_22N"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_23"/>
      <xs:enumeration value="Beijing_1954_GK_Zone_23N"/>
      <xs:enumeration value="Hanoi_1972_GK_Zone_18"/>
      <xs:enumeration value="Hanoi_1972_GK_Zone_19"/>
      <xs:enumeration value="South_Yemen_GK_Zone_8"/>
      <xs:enumeration value="South_Yemen_GK_Zone_9"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_10"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_10N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_11"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_11N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_12"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_12N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_13"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_13N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_14"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_14N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_15"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_15N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_16"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_16N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_17"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_17N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_18"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_18N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_19"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_19N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_2"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_20"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_20N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_21"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_21N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_22"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_22N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_23"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_23N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_24"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_24N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_25"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_25N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_26"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_26N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_27"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_27N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_28"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_28N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_29"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_29N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_2N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_3"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_30"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_30N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_31"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_31N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_32"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_32N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_3N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_4"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_4N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_5"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_5N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_6"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_6N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_7"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_7N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_8"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_8N"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_9"/>
      <xs:enumeration value="Pulkovo_1942_GK_Zone_9N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_10"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_10N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_11"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_11N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_12"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_12N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_13"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_13N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_14"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_14N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_15"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_15N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_16"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_16N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_17"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_17N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_18"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_18N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_19"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_19N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_2"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_20"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_20N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_21"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_21N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_22"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_22N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_23"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_23N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_24"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_24N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_25"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_25N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_26"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_26N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_27"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_27N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_28"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_28N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_29"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_29N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_2N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_3"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_30"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_30N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_31"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_31N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_32"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_32N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_3N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_4"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_4N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_5"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_5N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_6"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_6N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_7"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_7N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_8"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_8N"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_9"/>
      <xs:enumeration value="Pulkovo_1995_GK_Zone_9N"/>
      <xs:enumeration value="Abidjan_1987_TM_5_NW"/>
      <xs:enumeration value="Accra_Ghana_Grid"/>
      <xs:enumeration value="Accra_TM_1_NW"/>
      <xs:enumeration value="Samoa_1962_Samoa_Lambert"/>
      <xs:enumeration value="Anguilla_1957_British_West_Indies_Grid"/>
      <xs:enumeration value="Antigua_1943_British_West_Indies_Grid"/>
      <xs:enumeration value="Argentina_Zone_1"/>
      <xs:enumeration value="Argentina_Zone_2"/>
      <xs:enumeration value="Argentina_Zone_3"/>
      <xs:enumeration value="Argentina_Zone_4"/>
      <xs:enumeration value="Argentina_Zone_5"/>
      <xs:enumeration value="Argentina_Zone_6"/>
      <xs:enumeration value="Argentina_Zone_7"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_48"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_49"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_50"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_51"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_52"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_53"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_54"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_55"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_56"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_57"/>
      <xs:enumeration value="AGD_1966_AMG_Zone_58"/>
      <xs:enumeration value="AGD_1966_VICGRID"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_48"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_49"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_50"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_51"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_52"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_53"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_54"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_55"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_56"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_57"/>
      <xs:enumeration value="AGD_1984_AMG_Zone_58"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_48"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_49"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_50"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_51"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_52"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_53"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_54"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_55"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_56"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_57"/>
      <xs:enumeration value="GDA_1994_MGA_Zone_58"/>
      <xs:enumeration value="GDA_1994_South_Australia_Lambert"/>
      <xs:enumeration value="GDA_1994_VICGRID94"/>
      <xs:enumeration value="Austria_Central_Zone"/>
      <xs:enumeration value="Austria_East_Zone"/>
      <xs:enumeration value="Austria_West_Zone"/>
      <xs:enumeration value="Bahrain_State_Grid"/>
      <xs:enumeration value="Barbados_1938_Barbados_Grid"/>
      <xs:enumeration value="Barbados_1938_British_West_Indies_Grid"/>
      <xs:enumeration value="Belge_Lambert_1950"/>
      <xs:enumeration value="Belge_Lambert_1972"/>
      <xs:enumeration value="Bern_1898_Bern_LV03C"/>
      <xs:enumeration value="British_National_Grid"/>
      <xs:enumeration value="Camacupa_TM_11_30_SE"/>
      <xs:enumeration value="Camacupa_TM_12_SE"/>
      <xs:enumeration value="ATS_1977_MTM_4_Nova_Scotia"/>
      <xs:enumeration value="ATS_1977_MTM_5_Nova_Scotia"/>
      <xs:enumeration value="ATS_1977_New_Brunswick_Stereographic"/>
      <xs:enumeration value="NAD_1927_10TM_AEP_Forest"/>
      <xs:enumeration value="NAD_1927_10TM_AEP_Resource"/>
      <xs:enumeration value="NAD_1927_3TM_111"/>
      <xs:enumeration value="NAD_1927_3TM_114"/>
      <xs:enumeration value="NAD_1927_3TM_117"/>
      <xs:enumeration value="NAD_1927_3TM_120"/>
      <xs:enumeration value="NAD_1927_CGQ77_MTM_10_SCoPQ"/>
      <xs:enumeration value="NAD_1927_CGQ77_MTM_2_SCoPQ"/>
      <xs:enumeration value="NAD_1927_CGQ77_MTM_3_SCoPQ"/>
      <xs:enumeration value="NAD_1927_CGQ77_MTM_4_SCoPQ"/>
      <xs:enumeration value="NAD_1927_CGQ77_MTM_5_SCoPQ"/>
      <xs:enumeration value="NAD_1927_CGQ77_MTM_6_SCoPQ"/>
      <xs:enumeration value="NAD_1927_CGQ77_MTM_7_SCoPQ"/>
      <xs:enumeration value="NAD_1927_CGQ77_MTM_8_SCoPQ"/>
      <xs:enumeration value="NAD_1927_CGQ77_MTM_9_SCoPQ"/>
      <xs:enumeration value="NAD_1927_CGQ77_Quebec_Lambert"/>
      <xs:enumeration value="NAD_1927_CGQ77_UTM_Zone_17N"/>
      <xs:enumeration value="NAD_1927_CGQ77_UTM_Zone_18N"/>
      <xs:enumeration value="NAD_1927_CGQ77_UTM_Zone_19N"/>
      <xs:enumeration value="NAD_1927_CGQ77_UTM_Zone_20N"/>
      <xs:enumeration value="NAD_1927_CGQ77_UTM_Zone_21N"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_10"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_11"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_12"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_13"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_14"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_15"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_16"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_17"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_8"/>
      <xs:enumeration value="NAD_1927_DEF_1976_MTM_9"/>
      <xs:enumeration value="NAD_1927_DEF_1976_UTM_Zone_15N"/>
      <xs:enumeration value="NAD_1927_DEF_1976_UTM_Zone_16N"/>
      <xs:enumeration value="NAD_1927_DEF_1976_UTM_Zone_17N"/>
      <xs:enumeration value="NAD_1927_DEF_1976_UTM_Zone_18N"/>
      <xs:enumeration value="NAD_1927_MTM_1"/>
      <xs:enumeration value="NAD_1927_MTM_2"/>
      <xs:enumeration value="NAD_1927_MTM_3"/>
      <xs:enumeration value="NAD_1927_MTM_4"/>
      <xs:enumeration value="NAD_1927_MTM_5"/>
      <xs:enumeration value="NAD_1927_MTM_6"/>
      <xs:enumeration value="NAD_1927_Quebec_Lambert"/>
      <xs:enumeration value="NAD_1983_10TM_AEP_Forest"/>
      <xs:enumeration value="NAD_1983_10TM_AEP_Resource"/>
      <xs:enumeration value="NAD_1983_3TM_111"/>
      <xs:enumeration value="NAD_1983_3TM_114"/>
      <xs:enumeration value="NAD_1983_3TM_117"/>
      <xs:enumeration value="NAD_1983_3TM_120"/>
      <xs:enumeration value="NAD_1983_BC_Environment_Albers"/>
      <xs:enumeration value="NAD_1983_CRS98_MTM_10"/>
      <xs:enumeration value="NAD_1983_CSRS98_MTM_2_SCoPQ"/>
      <xs:enumeration value="NAD_1983_CRS98_MTM_3"/>
      <xs:enumeration value="NAD_1983_CRS98_MTM_4"/>
      <xs:enumeration value="NAD_1983_CRS98_MTM_5"/>
      <xs:enumeration value="NAD_1983_CRS98_MTM_6"/>
      <xs:enumeration value="NAD_1983_CRS98_MTM_7"/>
      <xs:enumeration value="NAD_1983_CRS98_MTM_8"/>
      <xs:enumeration value="NAD_1983_CRS98_MTM_9"/>
      <xs:enumeration value="NAD_1983_CSRS98_New_Brunswick_Stereographic"/>
      <xs:enumeration value="NAD_1983_CSRS98_Prince_Edward_Island"/>
      <xs:enumeration value="NAD_1983_CSRS98_UTM_Zone_21N"/>
      <xs:enumeration value="NAD_1983_CSRS98_UTM_Zone_11N"/>
      <xs:enumeration value="NAD_1983_CSRS98_UTM_Zone_12N"/>
      <xs:enumeration value="NAD_1983_CSRS98_UTM_Zone_13N"/>
      <xs:enumeration value="NAD_1983_CSRS98_UTM_Zone_17N"/>
      <xs:enumeration value="NAD_1983_CSRS98_UTM_Zone_18N"/>
      <xs:enumeration value="NAD_1983_CSRS98_UTM_Zone_19N"/>
      <xs:enumeration value="NAD_1983_CSRS98_UTM_Zone_20N"/>
      <xs:enumeration value="NAD_1983_MTM_1"/>
      <xs:enumeration value="NAD_1983_MTM_10"/>
      <xs:enumeration value="NAD_1983_MTM_11"/>
      <xs:enumeration value="NAD_1983_MTM_12"/>
      <xs:enumeration value="NAD_1983_MTM_13"/>
      <xs:enumeration value="NAD_1983_MTM_14"/>
      <xs:enumeration value="NAD_1983_MTM_15"/>
      <xs:enumeration value="NAD_1983_MTM_16"/>
      <xs:enumeration value="NAD_1983_MTM_17"/>
      <xs:enumeration value="NAD_1983_MTM_2_SCoPQ"/>
      <xs:enumeration value="NAD_1983_MTM_2"/>
      <xs:enumeration value="NAD_1983_MTM_3"/>
      <xs:enumeration value="NAD_1983_MTM_4"/>
      <xs:enumeration value="NAD_1983_MTM_5"/>
      <xs:enumeration value="NAD_1983_MTM_6"/>
      <xs:enumeration value="NAD_1983_MTM_7"/>
      <xs:enumeration value="NAD_1983_MTM_8"/>
      <xs:enumeration value="NAD_1983_MTM_9"/>
      <xs:enumeration value="NAD_1983_Quebec_Lambert"/>
      <xs:enumeration value="Prince_Edward_Island_Stereographic"/>
      <xs:enumeration value="Carthage_TM_11_NE"/>
      <xs:enumeration value="Centre_France"/>
      <xs:enumeration value="CH1903_LV03"/>
      <xs:enumeration value="CH1903+_LV95"/>
      <xs:enumeration value="Chos_Malal_1914_Argentina_2"/>
      <xs:enumeration value="Colombia_Bogota_Zone"/>
      <xs:enumeration value="Colombia_East_Central_Zone"/>
      <xs:enumeration value="Colombia_East_Zone"/>
      <xs:enumeration value="Colombia_West_Zone"/>
      <xs:enumeration value="Corse"/>
      <xs:enumeration value="Datum_73_Hayford_Gauss_IGeoE"/>
      <xs:enumeration value="Datum_73_Hayford_Gauss_IPCC"/>
      <xs:enumeration value="Deir_ez_Zor_Levant_Stereographic"/>
      <xs:enumeration value="Deir_ez_Zor_Levant_Zone"/>
      <xs:enumeration value="Deir_ez_Zor_Syria_Lambert"/>
      <xs:enumeration value="DHDN_3_Degree_Gauss_Zone_1"/>
      <xs:enumeration value="DHDN_3_Degree_Gauss_Zone_2"/>
      <xs:enumeration value="DHDN_3_Degree_Gauss_Zone_3"/>
      <xs:enumeration value="DHDN_3_Degree_Gauss_Zone_4"/>
      <xs:enumeration value="DHDN_3_Degree_Gauss_Zone_5"/>
      <xs:enumeration value="Dominica_1945_British_West_Indies_Grid"/>
      <xs:enumeration value="ED_1950_TM_0_N"/>
      <xs:enumeration value="ED_1950_TM_5_NE"/>
      <xs:enumeration value="Egypt_Blue_Belt"/>
      <xs:enumeration value="Egypt_Extended_Purple_Belt"/>
      <xs:enumeration value="Egypt_Purple_Belt"/>
      <xs:enumeration value="Egypt_Red_Belt"/>
      <xs:enumeration value="ELD_1979_Libya_10"/>
      <xs:enumeration value="ELD_1979_Libya_11"/>
      <xs:enumeration value="ELD_1979_Libya_12"/>
      <xs:enumeration value="ELD_1979_Libya_13"/>
      <xs:enumeration value="ELD_1979_Libya_5"/>
      <xs:enumeration value="ELD_1979_Libya_6"/>
      <xs:enumeration value="ELD_1979_Libya_7"/>
      <xs:enumeration value="ELD_1979_Libya_8"/>
      <xs:enumeration value="ELD_1979_Libya_9"/>
      <xs:enumeration value="ELD_1979_TM_12_NE"/>
      <xs:enumeration value="Estonian_Coordinate_System_of_1992"/>
      <xs:enumeration value="ETRF_1989_TM_Baltic_1993"/>
      <xs:enumeration value="FD_1958_Iraq"/>
      <xs:enumeration value="Finland_Zone_1"/>
      <xs:enumeration value="Finland_Zone_2"/>
      <xs:enumeration value="Finland_Zone_3"/>
      <xs:enumeration value="Finland_Zone_4"/>
      <xs:enumeration value="France_I"/>
      <xs:enumeration value="France_II"/>
      <xs:enumeration value="France_III"/>
      <xs:enumeration value="France_IV"/>
      <xs:enumeration value="Germany_Zone_1"/>
      <xs:enumeration value="Germany_Zone_2"/>
      <xs:enumeration value="Germany_Zone_3"/>
      <xs:enumeration value="Germany_Zone_4"/>
      <xs:enumeration value="Germany_Zone_5"/>
      <xs:enumeration value="Ghana_Metre_Grid"/>
      <xs:enumeration value="Greek_Grid"/>
      <xs:enumeration value="Grenada_1953_British_West_Indies_Grid"/>
      <xs:enumeration value="Hanoi_1972_GK_106_NE"/>
      <xs:enumeration value="HD_1972_Egyseges_Orszagos_Vetuleti"/>
      <xs:enumeration value="Hito_XVIII_1963_Argentina_2"/>
      <xs:enumeration value="Hong_Kong_1980_Grid"/>
      <xs:enumeration value="Indian_1960_TM_106NE"/>
      <xs:enumeration value="Kalianpur_1880_India_Zone_0"/>
      <xs:enumeration value="Kalianpur_1880_India_Zone_I"/>
      <xs:enumeration value="Kalianpur_1880_India_Zone_IIa"/>
      <xs:enumeration value="Kalianpur_1880_India_Zone_IIb"/>
      <xs:enumeration value="Kalianpur_1880_India_Zone_III"/>
      <xs:enumeration value="Kalianpur_1880_India_Zone_IV"/>
      <xs:enumeration value="Kalianpur_1937_India_Zone_IIb"/>
      <xs:enumeration value="Kalianpur_1937_UTM_Zone_45N"/>
      <xs:enumeration value="Kalianpur_1937_UTM_Zone_46N"/>
      <xs:enumeration value="Kalianpur_1962_India_Zone_I"/>
      <xs:enumeration value="Kalianpur_1962_India_Zone_IIa"/>
      <xs:enumeration value="Kalianpur_1962_UTM_Zone_41N"/>
      <xs:enumeration value="Kalianpur_1962_UTM_Zone_42N"/>
      <xs:enumeration value="Kalianpur_1962_UTM_Zone_43N"/>
      <xs:enumeration value="Kalianpur_1975_India_Zone_I"/>
      <xs:enumeration value="Kalianpur_1975_India_Zone_IIa"/>
      <xs:enumeration value="Kalianpur_1975_India_Zone_IIb"/>
      <xs:enumeration value="Kalianpur_1975_India_Zone_III"/>
      <xs:enumeration value="Kalianpur_1975_India_Zone_IV"/>
      <xs:enumeration value="Kalianpur_1975_UTM_Zone_42N"/>
      <xs:enumeration value="Kalianpur_1975_UTM_Zone_43N"/>
      <xs:enumeration value="Kalianpur_1975_UTM_Zone_44N"/>
      <xs:enumeration value="Kalianpur_1975_UTM_Zone_45N"/>
      <xs:enumeration value="Kalianpur_1975_UTM_Zone_46N"/>
      <xs:enumeration value="Kalianpur_1975_UTM_Zone_47N"/>
      <xs:enumeration value="IRENET95_IRISH_Transverse_Mercator"/>
      <xs:enumeration value="Irish_National_Grid"/>
      <xs:enumeration value="Israel_TM_Grid"/>
      <xs:enumeration value="Jamaica_1875_Old_Grid"/>
      <xs:enumeration value="Jamaica_Grid"/>
      <xs:enumeration value="Japan_Zone_1"/>
      <xs:enumeration value="Japan_Zone_10"/>
      <xs:enumeration value="Japan_Zone_11"/>
      <xs:enumeration value="Japan_Zone_12"/>
      <xs:enumeration value="Japan_Zone_13"/>
      <xs:enumeration value="Japan_Zone_14"/>
      <xs:enumeration value="Japan_Zone_15"/>
      <xs:enumeration value="Japan_Zone_16"/>
      <xs:enumeration value="Japan_Zone_17"/>
      <xs:enumeration value="Japan_Zone_18"/>
      <xs:enumeration value="Japan_Zone_19"/>
      <xs:enumeration value="Japan_Zone_2"/>
      <xs:enumeration value="Japan_Zone_3"/>
      <xs:enumeration value="Japan_Zone_4"/>
      <xs:enumeration value="Japan_Zone_5"/>
      <xs:enumeration value="Japan_Zone_6"/>
      <xs:enumeration value="Japan_Zone_7"/>
      <xs:enumeration value="Japan_Zone_8"/>
      <xs:enumeration value="Japan_Zone_9"/>
      <xs:enumeration value="Kertau_Singapore_Grid"/>
      <xs:enumeration value="KOC_Lambert"/>
      <xs:enumeration value="Korean_1985_Korea_Central_Belt"/>
      <xs:enumeration value="Korean_1985_Korea_East_Belt"/>
      <xs:enumeration value="Korean_1985_Korea_West_Belt"/>
      <xs:enumeration value="KUDAMS_KTM"/>
      <xs:enumeration value="KOC_Lambert"/>
      <xs:enumeration value="KUDAMS_KTM"/>
      <xs:enumeration value="Lake_Maracaibo_Grid_M1"/>
      <xs:enumeration value="Lake_Maracaibo_Grid_M3"/>
      <xs:enumeration value="Lake_Maracaibo_Grid"/>
      <xs:enumeration value="Lake_Maracaibo_La_Rosa_Grid"/>
      <xs:enumeration value="Lietuvos_Koordinaciu_Sistema"/>
      <xs:enumeration value="Lisboa_Bessel_Bonne"/>
      <xs:enumeration value="Lisboa_Hayford_Gauss_IGeoE"/>
      <xs:enumeration value="Lisboa_Hayford_Gauss_IPCC"/>
      <xs:enumeration value="Locodjo_1965_TM_5_NW"/>
      <xs:enumeration value="Madrid_1870_Madrid_Spain"/>
      <xs:enumeration value="MGI_3_Degree_Gauss_Zone_5"/>
      <xs:enumeration value="MGI_3_Degree_Gauss_Zone_6"/>
      <xs:enumeration value="MGI_3_Degree_Gauss_Zone_7"/>
      <xs:enumeration value="MGI_3_Degree_Gauss_Zone_8"/>
      <xs:enumeration value="MGI_Austria_Lambert"/>
      <xs:enumeration value="MGI_Balkans_5"/>
      <xs:enumeration value="MGI_Balkans_6"/>
      <xs:enumeration value="MGI_Balkans_8"/>
      <xs:enumeration value="MGI_Balkans_8"/>
      <xs:enumeration value="MGI_M28"/>
      <xs:enumeration value="MGI_M31"/>
      <xs:enumeration value="MGI_M34"/>
      <xs:enumeration value="Monte_Mario_Rome_Italy_1"/>
      <xs:enumeration value="Monte_Mario_Rome_Italy_2"/>
      <xs:enumeration value="Monte_Mario_Italy_1"/>
      <xs:enumeration value="Monte_Mario_Italy_2"/>
      <xs:enumeration value="Montserrat_1958_British_West_Indies_Grid"/>
      <xs:enumeration value="Mount_Dillon_Tobago_Grid"/>
      <xs:enumeration value="NAD_1927_Cuba_Norte"/>
      <xs:enumeration value="NAD_1927_Cuba_Sur"/>
      <xs:enumeration value="NAD_1927_Guatemala_Norte"/>
      <xs:enumeration value="NAD_1927_Guatemala_Sur"/>
      <xs:enumeration value="NAD_1927_Michigan_GeoRef_Meters"/>
      <xs:enumeration value="NAD_1927_Michigan_GeoRef_Feet_US"/>
      <xs:enumeration value="NAD_1983_HARN_Guam_Map_Grid"/>
      <xs:enumeration value="NAD_1983_Michigan_GeoRef_Meters"/>
      <xs:enumeration value="NAD_1983_Michigan_GeoRef_Feet_US"/>
      <xs:enumeration value="GD_1949_New_Zealand_Map_Grid"/>
      <xs:enumeration value="New_Zealand_North_Island"/>
      <xs:enumeration value="New_Zealand_South_Island"/>
      <xs:enumeration value="NZGD_1949_Amuri_Circuit"/>
      <xs:enumeration value="NZGD_1949_Bay_of_Plenty_Circuit"/>
      <xs:enumeration value="NZGD_1949_Bluff_Circuit"/>
      <xs:enumeration value="NZGD_1949_Buller_Circuit"/>
      <xs:enumeration value="NZGD_1949_Collingwood_Circuit"/>
      <xs:enumeration value="NZGD_1949_Gawler_Circuit"/>
      <xs:enumeration value="NZGD_1949_Grey_Circuit"/>
      <xs:enumeration value="NZGD_1949_Hawkes_Bay_Circuit"/>
      <xs:enumeration value="NZGD_1949_Hokitika_Circuit"/>
      <xs:enumeration value="NZGD_1949_Jacksons_Bay_Circuit"/>
      <xs:enumeration value="NZGD_1949_Karamea_Circuit"/>
      <xs:enumeration value="NZGD_1949_Lindis_Peak_Circuit"/>
      <xs:enumeration value="NZGD_1949_Marlborough_Circuit"/>
      <xs:enumeration value="NZGD_1949_Mount_Eden_Circuit"/>
      <xs:enumeration value="NZGD_1949_Mount_Nicholas_Circuit"/>
      <xs:enumeration value="NZGD_1949_Mount_Pleasant_Circuit"/>
      <xs:enumeration value="NZGD_1949_Mount_York_Circuit"/>
      <xs:enumeration value="NZGD_1949_Nelson_Circuit"/>
      <xs:enumeration value="NZGD_1949_North_Taieri_Circuit"/>
      <xs:enumeration value="NZGD_1949_Observation_Point_Circuit"/>
      <xs:enumeration value="NZGD_1949_Okarito_Circuit"/>
      <xs:enumeration value="NZGD_1949_Poverty_Bay_Circuit"/>
      <xs:enumeration value="NZGD_1949_Taranaki_Circuit"/>
      <xs:enumeration value="NZGD_1949_Timaru_Circuit"/>
      <xs:enumeration value="NZGD_1949_Tuhirangi_Circuit"/>
      <xs:enumeration value="NZGD_1949_UTM_Zone_58S"/>
      <xs:enumeration value="NZGD_1949_UTM_Zone_59S"/>
      <xs:enumeration value="NZGD_1949_UTM_Zone_60S"/>
      <xs:enumeration value="NZGD_1949_Wairarapa_Circuit"/>
      <xs:enumeration value="NZGD_1949_Wanganui_Circuit"/>
      <xs:enumeration value="NZGD_1949_Wellington_Circuit"/>
      <xs:enumeration value="NZGD_2000_Amuri_Circuit"/>
      <xs:enumeration value="NZGD_2000_Bay_of_Plenty_Circuit"/>
      <xs:enumeration value="NZGD_2000_Bluff_Circuit"/>
      <xs:enumeration value="NZGD_2000_Buller_Circuit"/>
      <xs:enumeration value="NZGD_2000_Collingwood_Circuit"/>
      <xs:enumeration value="NZGD_2000_Gawler_Circuit"/>
      <xs:enumeration value="NZGD_2000_Grey_Circuit"/>
      <xs:enumeration value="NZGD_2000_Hawkes_Bay_Circuit"/>
      <xs:enumeration value="NZGD_2000_Hokitika_Circuit"/>
      <xs:enumeration value="NZGD_2000_Jacksons_Bay_Circuit"/>
      <xs:enumeration value="NZGD_2000_Karamea_Circuit"/>
      <xs:enumeration value="NZGD_2000_Lindis_Peak_Circuit"/>
      <xs:enumeration value="NZGD_2000_Marlborough_Circuit"/>
      <xs:enumeration value="NZGD_2000_Mount_Eden_Circuit"/>
      <xs:enumeration value="NZGD_2000_Mount_Nicholas_Circuit"/>
      <xs:enumeration value="NZGD_2000_Mount_Pleasant_Circuit"/>
      <xs:enumeration value="NZGD_2000_Mount_York_Circuit"/>
      <xs:enumeration value="NZGD_2000_Nelson_Circuit"/>
      <xs:enumeration value="NZGD_2000_North_Taieri_Circuit"/>
      <xs:enumeration value="NZGD_2000_Observation_Point_Circuit"/>
      <xs:enumeration value="NZGD_2000_Okarito_Circuit"/>
      <xs:enumeration value="NZGD_2000_Poverty_Bay_Circuit"/>
      <xs:enumeration value="NZGD_2000_Taranaki_Circuit"/>
      <xs:enumeration value="NZGD_2000_Timaru_Circuit"/>
      <xs:enumeration value="NZGD_2000_Tuhirangi_Circuit"/>
      <xs:enumeration value="NZGD_2000_UTM_Zone_58S"/>
      <xs:enumeration value="NZGD_2000_UTM_Zone_59S"/>
      <xs:enumeration value="NZGD_2000_UTM_Zone_60S"/>
      <xs:enumeration value="NZGD_2000_Wairarapa_Circuit"/>
      <xs:enumeration value="NZGD_2000_Wanganui_Circuit"/>
      <xs:enumeration value="NZGD_2000_Wellington_Circuit"/>
      <xs:enumeration value="GD_1949_New_Zealand_Map_Grid"/>
      <xs:enumeration value="New_Zealand_North_Island"/>
      <xs:enumeration value="New_Zealand_South_Island"/>
      <xs:enumeration value="Nigeria_East_Belt"/>
      <xs:enumeration value="Nigeria_Mid_Belt"/>
      <xs:enumeration value="Nigeria_West_Belt"/>
      <xs:enumeration value="Nord_Algerie_Degree"/>
      <xs:enumeration value="Nord_Algerie_Ancienne_Degree"/>
      <xs:enumeration value="Sud_Algerie_Ancienne"/>
      <xs:enumeration value="Nord_Algerie"/>
      <xs:enumeration value="Nord_de_Guerre"/>
      <xs:enumeration value="Nord_France"/>
      <xs:enumeration value="Nord_Maroc_Degree"/>
      <xs:enumeration value="Nord_Maroc"/>
      <xs:enumeration value="Nord_Tunisie"/>
      <xs:enumeration value="NGO_1948_Baerum_Kommune"/>
      <xs:enumeration value="NGO_1948_Bergenhalvoen"/>
      <xs:enumeration value="NGO_1948_Norway_Zone_1"/>
      <xs:enumeration value="NGO_1948_Norway_Zone_2"/>
      <xs:enumeration value="NGO_1948_Norway_Zone_3"/>
      <xs:enumeration value="NGO_1948_Norway_Zone_4"/>
      <xs:enumeration value="NGO_1948_Norway_Zone_5"/>
      <xs:enumeration value="NGO_1948_Norway_Zone_6"/>
      <xs:enumeration value="NGO_1948_Norway_Zone_7"/>
      <xs:enumeration value="NGO_1948_Norway_Zone_8"/>
      <xs:enumeration value="NGO_1948_Oslo_Kommune"/>
      <xs:enumeration value="NGO_1948_Oslo_Norway_Zone_1"/>
      <xs:enumeration value="NGO_1948_Oslo_Norway_Zone_2"/>
      <xs:enumeration value="NGO_1948_Oslo_Norway_Zone_3"/>
      <xs:enumeration value="NGO_1948_Oslo_Norway_Zone_4"/>
      <xs:enumeration value="NGO_1948_Oslo_Norway_Zone_5"/>
      <xs:enumeration value="NGO_1948_Oslo_Norway_Zone_6"/>
      <xs:enumeration value="NGO_1948_Oslo_Norway_Zone_7"/>
      <xs:enumeration value="NGO_1948_Oslo_Norway_Zone_8"/>
      <xs:enumeration value="NTF_France_I_degrees"/>
      <xs:enumeration value="NTF_France_II_degrees"/>
      <xs:enumeration value="NTF_France_III_degrees"/>
      <xs:enumeration value="NTF_France_IV_degrees"/>
      <xs:enumeration value="Palestine_1923_Israel_CS_Grid"/>
      <xs:enumeration value="Palestine_1923_Palestine_Belt"/>
      <xs:enumeration value="Palestine_1923_Palestine_Grid"/>
      <xs:enumeration value="Pampa_del_Castillo_Argentina_2"/>
      <xs:enumeration value="Peru_Central_Zone"/>
      <xs:enumeration value="Peru_East_Zone"/>
      <xs:enumeration value="Peru_West_Zone"/>
      <xs:enumeration value="Philippines_Zone_I"/>
      <xs:enumeration value="Philippines_Zone_II"/>
      <xs:enumeration value="Philippines_Zone_III"/>
      <xs:enumeration value="Philippines_Zone_IV"/>
      <xs:enumeration value="Philippines_Zone_V"/>
      <xs:enumeration value="Portuguese_National_Grid"/>
      <xs:enumeration value="Qatar_1948_Qatar_Grid"/>
      <xs:enumeration value="Qatar_National_Grid"/>
      <xs:enumeration value="RD_Old"/>
      <xs:enumeration value="RGF_1993_Lambert_93"/>
      <xs:enumeration value="Rijksdriehoekstelsel_New"/>
      <xs:enumeration value="RT90_25_gon_W"/>
      <xs:enumeration value="S-JTSK_Ferro_Krovak_East_North"/>
      <xs:enumeration value="S-JTSK_Ferro_Krovak"/>
      <xs:enumeration value="S-JTSK_Krovak_East_North"/>
      <xs:enumeration value="S-JTSK_Krovak"/>
      <xs:enumeration value="SAD_1969_Brazil_Polyconic"/>
      <xs:enumeration value="Sahara_Degree"/>
      <xs:enumeration value="Sahara"/>
      <xs:enumeration value="Sierra_Leone_1924_New_Colony_Grid"/>
      <xs:enumeration value="Sierra_Leone_1924_New_War_Office_Grid"/>
      <xs:enumeration value="St_Kitts_1955_British_West_Indies_Grid"/>
      <xs:enumeration value="St_Lucia_1955_British_West_Indies_Grid"/>
      <xs:enumeration value="St_Vincent_1945_British_West_Indies_Grid"/>
      <xs:enumeration value="Stereo_33"/>
      <xs:enumeration value="Stereo_70"/>
      <xs:enumeration value="Sud_Algerie_Degree"/>
      <xs:enumeration value="Sud_Algerie_Ancienne_Degree"/>
      <xs:enumeration value="Sud_Algerie"/>
      <xs:enumeration value="Sud_France"/>
      <xs:enumeration value="Sud_Maroc_Degree"/>
      <xs:enumeration value="Sud_Maroc"/>
      <xs:enumeration value="Sud_Tunisie"/>
      <xs:enumeration value="Swedish_National_Grid"/>
      <xs:enumeration value="Trinidad_1903_Trinidad_Grid"/>
      <xs:enumeration value="UWPP_1992"/>
      <xs:enumeration value="UWPP_2000_pas_5"/>
      <xs:enumeration value="UWPP_2000_pas_6"/>
      <xs:enumeration value="UWPP_2000_pas_7"/>
      <xs:enumeration value="UWPP_2000_pas_8"/>
      <xs:enumeration value="WGS_1972_BE_TM_106_NE"/>
      <xs:enumeration value="WGS_1984_TM_36_SE"/>
      <xs:enumeration value="Zanderij_Suriname_Old_TM"/>
      <xs:enumeration value="Zanderij_Suriname_TM"/>
      <xs:enumeration value="Zanderij_TM_54_NW"/>
      <xs:enumeration value="North_Pole_Azimuthal_Equidistant"/>
      <xs:enumeration value="North_Pole_Gnomonic"/>
      <xs:enumeration value="North_Pole_Lambert_Azimuthal_Equal_Area"/>
      <xs:enumeration value="North_Pole_Orthographic"/>
      <xs:enumeration value="North_Pole_Stereographic"/>
      <xs:enumeration value="South_Pole_Azimuthal_Equidistant"/>
      <xs:enumeration value="South_Pole_Gnomonic"/>
      <xs:enumeration value="South_Pole_Lambert_Azimuthal_Equal_Area"/>
      <xs:enumeration value="South_Pole_Orthographic"/>
      <xs:enumeration value="South_Pole_Stereographic"/>
      <xs:enumeration value="UPS_North"/>
      <xs:enumeration value="UPS_South"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alabama_East_FIPS_0101"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alabama_West_FIPS_0102"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_1_FIPS_5001"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_10_FIPS_5010"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_2_FIPS_5002"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_3_FIPS_5003"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_4_FIPS_5004"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_5_FIPS_5005"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_6_FIPS_5006"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_7_FIPS_5007"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_8_FIPS_5008"/>
      <xs:enumeration value="NAD_1927_StatePlane_Alaska_9_FIPS_5009"/>
      <xs:enumeration value="NAD_1927_StatePlane_Arizona_Central_FIPS_0202"/>
      <xs:enumeration value="NAD_1927_StatePlane_Arizona_East_FIPS_0201"/>
      <xs:enumeration value="NAD_1927_StatePlane_Arizona_West_FIPS_0203"/>
      <xs:enumeration value="NAD_1927_StatePlane_Arkansas_North_FIPS_0301"/>
      <xs:enumeration value="NAD_1927_StatePlane_Arkansas_South_FIPS_0302"/>
      <xs:enumeration value="NAD_1927_StatePlane_California_I_FIPS_0401"/>
      <xs:enumeration value="NAD_1927_StatePlane_California_II_FIPS_0402"/>
      <xs:enumeration value="NAD_1927_StatePlane_California_III_FIPS_0403"/>
      <xs:enumeration value="NAD_1927_StatePlane_California_IV_FIPS_0404"/>
      <xs:enumeration value="NAD_1927_StatePlane_California_V_FIPS_0405"/>
      <xs:enumeration value="NAD_1927_StatePlane_California_VI_FIPS_0406"/>
      <xs:enumeration value="NAD_1927_StatePlane_California_VII_FIPS_0407"/>
      <xs:enumeration value="NAD_1927_StatePlane_Colorado_Central_FIPS_0502"/>
      <xs:enumeration value="NAD_1927_StatePlane_Colorado_North_FIPS_0501"/>
      <xs:enumeration value="NAD_1927_StatePlane_Colorado_South_FIPS_0503"/>
      <xs:enumeration value="NAD_1927_StatePlane_Connecticut_FIPS_0600"/>
      <xs:enumeration value="NAD_1927_StatePlane_Delaware_FIPS_0700"/>
      <xs:enumeration value="NAD_1927_StatePlane_Florida_East_FIPS_0901"/>
      <xs:enumeration value="NAD_1927_StatePlane_Florida_North_FIPS_0903"/>
      <xs:enumeration value="NAD_1927_StatePlane_Florida_West_FIPS_0902"/>
      <xs:enumeration value="NAD_1927_StatePlane_Georgia_East_FIPS_1001"/>
      <xs:enumeration value="NAD_1927_StatePlane_Georgia_West_FIPS_1002"/>
      <xs:enumeration value="NAD_1927_StatePlane_Guam_FIPS_5400"/>
      <xs:enumeration value="NAD_1927_StatePlane_Idaho_Central_FIPS_1102"/>
      <xs:enumeration value="NAD_1927_StatePlane_Idaho_East_FIPS_1101"/>
      <xs:enumeration value="NAD_1927_StatePlane_Idaho_West_FIPS_1103"/>
      <xs:enumeration value="NAD_1927_StatePlane_Illinois_East_FIPS_1201"/>
      <xs:enumeration value="NAD_1927_StatePlane_Illinois_West_FIPS_1202"/>
      <xs:enumeration value="NAD_1927_StatePlane_Indiana_East_FIPS_1301"/>
      <xs:enumeration value="NAD_1927_StatePlane_Indiana_West_FIPS_1302"/>
      <xs:enumeration value="NAD_1927_StatePlane_Iowa_North_FIPS_1401"/>
      <xs:enumeration value="NAD_1927_StatePlane_Iowa_South_FIPS_1402"/>
      <xs:enumeration value="NAD_1927_StatePlane_Kansas_North_FIPS_1501"/>
      <xs:enumeration value="NAD_1927_StatePlane_Kansas_South_FIPS_1502"/>
      <xs:enumeration value="NAD_1927_StatePlane_Kentucky_North_FIPS_1601"/>
      <xs:enumeration value="NAD_1927_StatePlane_Kentucky_South_FIPS_1602"/>
      <xs:enumeration value="NAD_1927_StatePlane_Louisiana_North_FIPS_1701"/>
      <xs:enumeration value="NAD_1927_StatePlane_Louisiana_South_FIPS_1702"/>
      <xs:enumeration value="NAD_1927_StatePlane_Maine_East_FIPS_1801"/>
      <xs:enumeration value="NAD_1927_StatePlane_Maine_West_FIPS_1802"/>
      <xs:enumeration value="NAD_1927_StatePlane_Maryland_FIPS_1900"/>
      <xs:enumeration value="NAD_1927_StatePlane_Massachusetts_Island_FIPS_2002"/>
      <xs:enumeration value="NAD_1927_StatePlane_Massachusetts_Mainland_FIPS_2001"/>
      <xs:enumeration value="NAD_1927_StatePlane_Michigan_Central_FIPS_2112"/>
      <xs:enumeration value="NAD_1927_StatePlane_Michigan_North_FIPS_2111"/>
      <xs:enumeration value="NAD_1927_StatePlane_Michigan_South_FIPS_2113"/>
      <xs:enumeration value="NAD_1927_StatePlane_Minnesota_Central_FIPS_2202"/>
      <xs:enumeration value="NAD_1927_StatePlane_Minnesota_North_FIPS_2201"/>
      <xs:enumeration value="NAD_1927_StatePlane_Minnesota_South_FIPS_2203"/>
      <xs:enumeration value="NAD_1927_StatePlane_Mississippi_East_FIPS_2301"/>
      <xs:enumeration value="NAD_1927_StatePlane_Mississippi_West_FIPS_2302"/>
      <xs:enumeration value="NAD_1927_StatePlane_Missouri_Central_FIPS_2402"/>
      <xs:enumeration value="NAD_1927_StatePlane_Missouri_East_FIPS_2401"/>
      <xs:enumeration value="NAD_1927_StatePlane_Missouri_West_FIPS_2403"/>
      <xs:enumeration value="NAD_1927_StatePlane_Montana_Central_FIPS_2502"/>
      <xs:enumeration value="NAD_1927_StatePlane_Montana_North_FIPS_2501"/>
      <xs:enumeration value="NAD_1927_StatePlane_Montana_South_FIPS_2503"/>
      <xs:enumeration value="NAD_1927_StatePlane_Nebraska_North_FIPS_2601"/>
      <xs:enumeration value="NAD_1927_StatePlane_Nebraska_South_FIPS_2602"/>
      <xs:enumeration value="NAD_1927_StatePlane_Nevada_Central_FIPS_2702"/>
      <xs:enumeration value="NAD_1927_StatePlane_Nevada_East_FIPS_2701"/>
      <xs:enumeration value="NAD_1927_StatePlane_Nevada_West_FIPS_2703"/>
      <xs:enumeration value="NAD_1927_StatePlane_New_Hampshire_FIPS_2800"/>
      <xs:enumeration value="NAD_1927_StatePlane_New_Jersey_FIPS_2900"/>
      <xs:enumeration value="NAD_1927_StatePlane_New_Mexico_Central_FIPS_3002"/>
      <xs:enumeration value="NAD_1927_StatePlane_New_Mexico_East_FIPS_3001"/>
      <xs:enumeration value="NAD_1927_StatePlane_New_Mexico_West_FIPS_3003"/>
      <xs:enumeration value="NAD_1927_StatePlane_New_York_Central_FIPS_3102"/>
      <xs:enumeration value="NAD_1927_StatePlane_New_York_East_FIPS_3101"/>
      <xs:enumeration value="NAD_1927_StatePlane_New_York_Long_Island_FIPS_3104"/>
      <xs:enumeration value="NAD_1927_StatePlane_New_York_West_FIPS_3103"/>
      <xs:enumeration value="NAD_1927_StatePlane_North_Carolina_FIPS_3200"/>
      <xs:enumeration value="NAD_1927_StatePlane_North_Dakota_North_FIPS_3301"/>
      <xs:enumeration value="NAD_1927_StatePlane_North_Dakota_South_FIPS_3302"/>
      <xs:enumeration value="NAD_1927_StatePlane_Ohio_North_FIPS_3401"/>
      <xs:enumeration value="NAD_1927_StatePlane_Ohio_South_FIPS_3402"/>
      <xs:enumeration value="NAD_1927_StatePlane_Oklahoma_North_FIPS_3501"/>
      <xs:enumeration value="NAD_1927_StatePlane_Oklahoma_South_FIPS_3502"/>
      <xs:enumeration value="NAD_1927_StatePlane_Oregon_North_FIPS_3601"/>
      <xs:enumeration value="NAD_1927_StatePlane_Oregon_South_FIPS_3602"/>
      <xs:enumeration value="NAD_1927_StatePlane_Pennsylvania_North_FIPS_3701"/>
      <xs:enumeration value="NAD_1927_StatePlane_Pennsylvania_South_FIPS_3702"/>
      <xs:enumeration value="NAD_1927_StatePlane_Puerto_Rico_FIPS_5201"/>
      <xs:enumeration value="NAD_1927_StatePlane_Rhode_Island_FIPS_3800"/>
      <xs:enumeration value="NAD_1927_StatePlane_South_Carolina_North_FIPS_3901"/>
      <xs:enumeration value="NAD_1927_StatePlane_South_Carolina_South_FIPS_3902"/>
      <xs:enumeration value="NAD_1927_StatePlane_South_Dakota_North_FIPS_4001"/>
      <xs:enumeration value="NAD_1927_StatePlane_South_Dakota_South_FIPS_4002"/>
      <xs:enumeration value="NAD_1927_StatePlane_Tennessee_FIPS_4100"/>
      <xs:enumeration value="NAD_1927_StatePlane_Texas_Central_FIPS_4203"/>
      <xs:enumeration value="NAD_1927_StatePlane_Texas_North_Central_FIPS_4202"/>
      <xs:enumeration value="NAD_1927_StatePlane_Texas_North_FIPS_4201"/>
      <xs:enumeration value="NAD_1927_StatePlane_Texas_South_Central_FIPS_4204"/>
      <xs:enumeration value="NAD_1927_StatePlane_Texas_South_FIPS_4205"/>
      <xs:enumeration value="NAD_1927_StatePlane_Utah_Central_FIPS_4302"/>
      <xs:enumeration value="NAD_1927_StatePlane_Utah_North_FIPS_4301"/>
      <xs:enumeration value="NAD_1927_StatePlane_Utah_South_FIPS_4303"/>
      <xs:enumeration value="NAD_1927_StatePlane_Vermont_FIPS_3400"/>
      <xs:enumeration value="NAD_1927_StatePlane_Virginia_North_FIPS_4501"/>
      <xs:enumeration value="NAD_1927_StatePlane_Virginia_South_FIPS_4502"/>
      <xs:enumeration value="NAD_1927_StatePlane_Washington_North_FIPS_4601"/>
      <xs:enumeration value="NAD_1927_StatePlane_Washington_South_FIPS_4602"/>
      <xs:enumeration value="NAD_1927_StatePlane_West_Virginia_North_FIPS_4701"/>
      <xs:enumeration value="NAD_1927_StatePlane_West_Virginia_South_FIPS_4702"/>
      <xs:enumeration value="NAD_1927_StatePlane_Wisconsin_Central_FIPS_4802"/>
      <xs:enumeration value="NAD_1927_StatePlane_Wisconsin_North_FIPS_4801"/>
      <xs:enumeration value="NAD_1927_StatePlane_Wisconsin_South_FIPS_4803"/>
      <xs:enumeration value="NAD_1927_StatePlane_Wyoming_East_Central_FIPS_4902"/>
      <xs:enumeration value="NAD_1927_StatePlane_Wyoming_East_FIPS_4901"/>
      <xs:enumeration value="NAD_1927_StatePlane_Wyoming_West_Central_FIPS_4903"/>
      <xs:enumeration value="NAD_1927_StatePlane_Wyoming_West_FIPS_4904"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alabama_East_FIPS_0101"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alabama_West_FIPS_0102"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_1_FIPS_5001"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_10_FIPS_5010"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_2_FIPS_5002"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_3_FIPS_5003"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_4_FIPS_5004"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_5_FIPS_5005"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_6_FIPS_5006"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_7_FIPS_5007"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_8_FIPS_5008"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_9_FIPS_5009"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arizona_Central_FIPS_0202"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arizona_East_FIPS_0201"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arizona_West_FIPS_0203"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arkansas_North_FIPS_0301"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arkansas_South_FIPS_0302"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_I_FIPS_0401"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_II_FIPS_0402"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_III_FIPS_0403"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_IV_FIPS_0404"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_V_FIPS_0405"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_VI_FIPS_0406"/>
      <xs:enumeration value="NAD_1983_StatePlane_Colorado_Central_FIPS_0502"/>
      <xs:enumeration value="NAD_1983_StatePlane_Colorado_North_FIPS_0501"/>
      <xs:enumeration value="NAD_1983_StatePlane_Colorado_South_FIPS_0503"/>
      <xs:enumeration value="NAD_1983_StatePlane_Connecticut_FIPS_0600"/>
      <xs:enumeration value="NAD_1983_StatePlane_Delaware_FIPS_0700"/>
      <xs:enumeration value="NAD_1983_StatePlane_Florida_East_FIPS_0901"/>
      <xs:enumeration value="NAD_1983_StatePlane_Florida_North_FIPS_0903"/>
      <xs:enumeration value="NAD_1983_StatePlane_Florida_West_FIPS_0902"/>
      <xs:enumeration value="NAD_1983_StatePlane_Georgia_East_FIPS_1001"/>
      <xs:enumeration value="NAD_1983_StatePlane_Georgia_West_FIPS_1002"/>
      <xs:enumeration value="NAD_1983_StatePlane_Guam_FIPS_5400"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_1_FIPS_5101"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_2_FIPS_5102"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_3_FIPS_5103"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_4_FIPS_5104"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_5_FIPS_5105"/>
      <xs:enumeration value="NAD_1983_StatePlane_Idaho_Central_FIPS_1102"/>
      <xs:enumeration value="NAD_1983_StatePlane_Idaho_East_FIPS_1101"/>
      <xs:enumeration value="NAD_1983_StatePlane_Idaho_West_FIPS_1103"/>
      <xs:enumeration value="NAD_1983_StatePlane_Illinois_East_FIPS_1201"/>
      <xs:enumeration value="NAD_1983_StatePlane_Illinois_West_FIPS_1202"/>
      <xs:enumeration value="NAD_1983_StatePlane_Indiana_East_FIPS_1301"/>
      <xs:enumeration value="NAD_1983_StatePlane_Indiana_West_FIPS_1302"/>
      <xs:enumeration value="NAD_1983_StatePlane_Iowa_North_FIPS_1401"/>
      <xs:enumeration value="NAD_1983_StatePlane_Iowa_South_FIPS_1402"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kansas_North_FIPS_1501"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kansas_South_FIPS_1502"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kentucky_FIPS_1600"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kentucky_North_FIPS_1601"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kentucky_South_FIPS_1602"/>
      <xs:enumeration value="NAD_1983_StatePlane_Louisiana_North_FIPS_1701"/>
      <xs:enumeration value="NAD_1983_StatePlane_Louisiana_South_FIPS_1702"/>
      <xs:enumeration value="NAD_1983_StatePlane_Maine_East_FIPS_1801"/>
      <xs:enumeration value="NAD_1983_StatePlane_Maine_West_FIPS_1802"/>
      <xs:enumeration value="NAD_1983_StatePlane_Maryland_FIPS_1900"/>
      <xs:enumeration value="NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002"/>
      <xs:enumeration value="NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001"/>
      <xs:enumeration value="NAD_1983_StatePlane_Michigan_Central_FIPS_2202"/>
      <xs:enumeration value="NAD_1983_StatePlane_Michigan_North_FIPS_2111"/>
      <xs:enumeration value="NAD_1983_StatePlane_Michigan_South_FIPS_2113"/>
      <xs:enumeration value="NAD_1983_StatePlane_Minnesota_Central_FIPS_2202"/>
      <xs:enumeration value="NAD_1983_StatePlane_Minnesota_North_FIPS_2201"/>
      <xs:enumeration value="NAD_1983_StatePlane_Minnesota_South_FIPS_2203"/>
      <xs:enumeration value="NAD_1983_StatePlane_Mississippi_East_FIPS_2301"/>
      <xs:enumeration value="NAD_1983_StatePlane_Mississippi_West_FIPS_2302"/>
      <xs:enumeration value="NAD_1983_StatePlane_Missouri_Central_FIPS_2402"/>
      <xs:enumeration value="NAD_1983_StatePlane_Missouri_East_FIPS_2401"/>
      <xs:enumeration value="NAD_1983_StatePlane_Missouri_West_FIPS_2403"/>
      <xs:enumeration value="NAD_1983_StatePlane_Montana_FIPS_2500"/>
      <xs:enumeration value="NAD_1983_StatePlane_Nebraska_FIPS_2600"/>
      <xs:enumeration value="NAD_1983_StatePlane_Nevada_Central_FIPS_2702"/>
      <xs:enumeration value="NAD_1983_StatePlane_Nevada_East_FIPS_2701"/>
      <xs:enumeration value="NAD_1983_StatePlane_Nevada_West_FIPS_2703"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Hampshire_FIPS_2800"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Jersey_FIPS_2900"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Mexico_East_FIPS_3001"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Mexico_West_FIPS_3003"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_York_Central_FIPS_3102"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_York_East_FIPS_3101"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_York_West_FIPS_3103"/>
      <xs:enumeration value="NAD_1983_StatePlane_North_Carolina_FIPS_3200"/>
      <xs:enumeration value="NAD_1983_StatePlane_North_Dakota_North_FIPS_3301"/>
      <xs:enumeration value="NAD_1983_StatePlane_North_Dakota_South_FIPS_3302"/>
      <xs:enumeration value="NAD_1983_StatePlane_Ohio_North_FIPS_3401"/>
      <xs:enumeration value="NAD_1983_StatePlane_Ohio_South_FIPS_3402"/>
      <xs:enumeration value="NAD_1983_StatePlane_Oklahoma_North_FIPS_3501"/>
      <xs:enumeration value="NAD_1983_StatePlane_Oklahoma_South_FIPS_3502"/>
      <xs:enumeration value="NAD_1983_StatePlane_Oregon_North_FIPS_3601"/>
      <xs:enumeration value="NAD_1983_StatePlane_Oregon_South_FIPS_3602"/>
      <xs:enumeration value="NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701"/>
      <xs:enumeration value="NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702"/>
      <xs:enumeration value="NAD_1983_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200"/>
      <xs:enumeration value="NAD_1983_StatePlane_Rhode_Island_FIPS_3800"/>
      <xs:enumeration value="NAD_1983_StatePlane_South_Carolina_FIPS_3900"/>
      <xs:enumeration value="NAD_1983_StatePlane_South_Dakota_North_FIPS_4001"/>
      <xs:enumeration value="NAD_1983_StatePlane_South_Dakota_South_FIPS_4002"/>
      <xs:enumeration value="NAD_1983_StatePlane_Tennessee_FIPS_4100"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_Central_FIPS_4203"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_North_Central_FIPS_4202"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_North_FIPS_4201"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_South_Central_FIPS_4204"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_South_FIPS_4205"/>
      <xs:enumeration value="NAD_1983_StatePlane_Utah_Central_FIPS_4302"/>
      <xs:enumeration value="NAD_1983_StatePlane_Utah_North_FIPS_4301"/>
      <xs:enumeration value="NAD_1983_StatePlane_Utah_South_FIPS_4303"/>
      <xs:enumeration value="NAD_1983_StatePlane_Vermont_FIPS_4400"/>
      <xs:enumeration value="NAD_1983_StatePlane_Virginia_North_FIPS_4501"/>
      <xs:enumeration value="NAD_1983_StatePlane_Virginia_South_FIPS_4502"/>
      <xs:enumeration value="NAD_1983_StatePlane_Washington_North_FIPS_4601"/>
      <xs:enumeration value="NAD_1983_StatePlane_Washington_South_FIPS_4602"/>
      <xs:enumeration value="NAD_1983_StatePlane_West_Virginia_North_FIPS_4701"/>
      <xs:enumeration value="NAD_1983_StatePlane_West_Virginia_South_FIPS_4702"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wisconsin_North_FIPS_4801"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wisconsin_South_FIPS_4803"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wyoming_East_FIPS_4901"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wyoming_West_FIPS_4904"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alabama_East_FIPS_0101_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alabama_West_FIPS_0102_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_1_FIPS_5001_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_10_FIPS_5010_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_2_FIPS_5002_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_3_FIPS_5003_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_4_FIPS_5004_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_5_FIPS_5005_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_6_FIPS_5006_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_7_FIPS_5007_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_8_FIPS_5008_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Alaska_9_FIPS_5009_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arizona_Central_FIPS_0202_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arizona_East_FIPS_0201_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arizona_West_FIPS_0203_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arkansas_North_FIPS_0301_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Arkansas_South_FIPS_0302_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_I_FIPS_0401_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_II_FIPS_0402_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_III_FIPS_0403_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_IV_FIPS_0404_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_V_FIPS_0405_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_California_VI_FIPS_0406_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Colorado_North_FIPS_0501_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Colorado_South_FIPS_0503_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Connecticut_FIPS_0600_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Delaware_FIPS_0700_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Florida_North_FIPS_0903_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Florida_West_FIPS_0902_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Georgia_East_FIPS_1001_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Georgia_West_FIPS_1002_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Guam_FIPS_5400_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_1_FIPS_5101_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_2_FIPS_5102_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_3_FIPS_5103_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_4_FIPS_5104_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Hawaii_5_FIPS_5105_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Idaho_Central_FIPS_1102_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Idaho_East_FIPS_1101_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Idaho_West_FIPS_1103_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Illinois_West_FIPS_1202_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Indiana_West_FIPS_1302_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Iowa_North_FIPS_1401_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Iowa_South_FIPS_1402_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kansas_North_FIPS_1501_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kansas_South_FIPS_1502_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kentucky_FIPS_1600_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kentucky_North_FIPS_1601_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Kentucky_South_FIPS_1602_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Louisiana_North_FIPS_1701_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Louisiana_South_FIPS_1702_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Maine_East_FIPS_1801_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Maine_West_FIPS_1802_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Maryland_FIPS_1900_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Massachusetts_Island_FIPS_2002_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Massachusetts_Mainland_FIPS_2001_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Michigan_Central_FIPS_2202_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Michigan_North_FIPS_2111_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Minnesota_Central_FIPS_2202_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Minnesota_North_FIPS_2201_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Minnesota_South_FIPS_2203_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Mississippi_East_FIPS_2301_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Missouri_Central_FIPS_2402_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Missouri_East_FIPS_2401_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Missouri_West_FIPS_2403_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Montana_FIPS_2500_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Nebraska_FIPS_2600_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Nevada_Central_FIPS_2702_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Nevada_East_FIPS_2701_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Nevada_West_FIPS_2703_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Hampshire_FIPS_2800_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Mexico_Central_FIPS_3002_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Mexico_East_FIPS_3001_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_Mexico_West_FIPS_3003_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_York_Central_FIPS_3102_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_York_East_FIPS_3101_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_New_York_West_FIPS_3103_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_North_Dakota_North_FIPS_3301_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_North_Dakota_South_FIPS_3302_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Oklahoma_North_FIPS_3501_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Oklahoma_South_FIPS_3502_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Oregon_North_FIPS_3601_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Oregon_South_FIPS_3602_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Pennsylvania_South_FIPS_3702_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Rhode_Island_FIPS_3800_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_South_Carolina_FIPS_3900_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_South_Dakota_North_FIPS_4001_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_South_Dakota_South_FIPS_4002_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Tennessee_FIPS_4100_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_Central_FIPS_4203_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_North_Central_FIPS_4202_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_North_FIPS_4201_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_South_Central_FIPS_4204_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Texas_South_FIPS_4205_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Utah_Central_FIPS_4302_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Utah_North_FIPS_4301_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Utah_South_FIPS_4303_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Vermont_FIPS_4400_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Virginia_South_FIPS_4502_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Washington_South_FIPS_4602_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_West_Virginia_North_FIPS_4701_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_West_Virginia_South_FIPS_4702_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wisconsin_Central_FIPS_4802_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wisconsin_North_FIPS_4801_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wisconsin_South_FIPS_4803_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wyoming_East_Central_FIPS_4902_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wyoming_East_FIPS_4901_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wyoming_West_Central_FIPS_4903_Feet"/>
      <xs:enumeration value="NAD_1983_StatePlane_Wyoming_West_FIPS_4904_Feet"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Alabama_East_FIPS_0101"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Alabama_West_FIPS_0102"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Arizona_Central_FIPS_0202"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Arizona_East_FIPS_0201"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Arizona_West_FIPS_0203"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_California_I_FIPS_0401"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_California_II_FIPS_0402"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_California_III_FIPS_0403"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_California_IV_FIPS_0404"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_California_V_FIPS_0405"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_California_VI_FIPS_0406"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Colorado_Central_FIPS_0502"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Colorado_North_FIPS_0501"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Colorado_South_FIPS_0503"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Connecticut_FIPS_0600"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Delaware_FIPS_0700"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Florida_North_FIPS_0903"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Florida_West_FIPS_0902"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Georgia_East_FIPS_1001"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Georgia_West_FIPS_1002"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Hawaii_1_FIPS_5101"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Hawaii_2_FIPS_5102"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Hawaii_3_FIPS_5103"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Hawaii_4_FIPS_5104"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Hawaii_5_FIPS_5105"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Idaho_Central_FIPS_1102"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Idaho_East_FIPS_1101"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Idaho_West_FIPS_1103"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Illinois_East_FIPS_1201"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Illinois_West_FIPS_1202"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Indiana_East_FIPS_1301"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Indiana_West_FIPS_1302"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Kansas_North_FIPS_1501"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Kansas_South_FIPS_1502"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Kentucky_North_FIPS_1601"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Kentucky_South_FIPS_1602"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Louisiana_North_FIPS_1701"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Louisiana_South_FIPS_1702"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Maine_East_FIPS_1801"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Maine_West_FIPS_1802"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Maryland_FIPS_1900"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Massachusetts_Island_FIPS_2002"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Massachusetts_Mainland_FIPS_2001"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Michigan_Central_FIPS_2202"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Michigan_North_FIPS_2111"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Michigan_South_FIPS_2113"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Mississippi_East_FIPS_2301"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Mississippi_West_FIPS_2302"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Montana_FIPS_2500"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Nebraska_FIPS_2600"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Nevada_Central_FIPS_2702"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Nevada_East_FIPS_2701"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Nevada_West_FIPS_2703"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_New_Hampshire_FIPS_2800"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_New_Jersey_FIPS_2900"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_New_Mexico_Central_FIPS_3002"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_New_Mexico_East_FIPS_3001"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_New_Mexico_West_FIPS_3003"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_New_York_Central_FIPS_3102"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_New_York_East_FIPS_3101"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_New_York_Long_Island_FIPS_3104"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_New_York_West_FIPS_3103"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_North_Dakota_North_FIPS_3301"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_North_Dakota_South_FIPS_3302"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Ohio_North_FIPS_3401"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Ohio_South_FIPS_3402"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Oklahoma_North_FIPS_3501"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Oklahoma_South_FIPS_3502"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Oregon_South_FIPS_3602"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Puerto_Rico_Virgin_Islands_FIPS_5200"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Rhode_Island_FIPS_3800"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_South_Dakota_North_FIPS_4001"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_South_Dakota_South_FIPS_4002"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Tennessee_FIPS_4100"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Texas_Central_FIPS_4203"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Texas_North_Central_FIPS_4202"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Texas_North_FIPS_4201"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Texas_South_Central_FIPS_4204"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Texas_South_FIPS_4205"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Utah_Central_FIPS_4302"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Utah_North_FIPS_4301"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Utah_South_FIPS_4303"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Vermont_FIPS_4400"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Virginia_North_FIPS_4501"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Virginia_South_FIPS_4502"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Washington_South_FIPS_4602"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_West_Virginia_North_FIPS_4701"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_West_Virginia_South_FIPS_4702"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Wisconsin_Central_FIPS_4802"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Wisconsin_North_FIPS_4801"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Wisconsin_South_FIPS_4803"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Wyoming_East_FIPS_4901"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Wyoming_East_Central_FIPS_4902"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Wyoming_West_Central_FIPS_4903"/>
      <xs:enumeration value="NAD_1983_HARN_StatePlane_Wyoming_West_FIPS_4904"/>
      <xs:enumeration value="American_Samoa_1962_StatePlane_American_Samoa_FIPS_5300"/>
      <xs:enumeration value="NAD_1983_HARN_Guam_Map_Grid"/>
      <xs:enumeration value="NAD_1983_HARN_UTM_Zone_2S"/>
      <xs:enumeration value="NAD_Michigan_StatePlane_Michigan_Central_FIPS_2112"/>
      <xs:enumeration value="NAD_Michigan_StatePlane_Michigan_Central_Old_FIPS_2102"/>
      <xs:enumeration value="NAD_Michigan_StatePlane_Michigan_East_Old_FIPS_2101"/>
      <xs:enumeration value="NAD_Michigan_StatePlane_Michigan_North_FIPS_2111"/>
      <xs:enumeration value="NAD_Michigan_StatePlane_Michigan_South_FIPS_2113"/>
      <xs:enumeration value="NAD_Michigan_StatePlane_Michigan_West_Old_FIPS_2103"/>
      <xs:enumeration value="Old_Hawaiian_StatePlane_Hawaii_1_FIPS_5101"/>
      <xs:enumeration value="Old_Hawaiian_StatePlane_Hawaii_2_FIPS_5102"/>
      <xs:enumeration value="Old_Hawaiian_StatePlane_Hawaii_3_FIPS_5103"/>
      <xs:enumeration value="Old_Hawaiian_StatePlane_Hawaii_4_FIPS_5104"/>
      <xs:enumeration value="Old_Hawaiian_StatePlane_Hawaii_5_FIPS_5105"/>
      <xs:enumeration value="Puerto_Rico_StatePlane_Puerto_Rico_FIPS_5201"/>
      <xs:enumeration value="Puerto_Rico_StatePlane_Virgin_Islands_St_Croix_FIPS_5202"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_10N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_11N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_12N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_13N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_14N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_15N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_16N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_17N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_18N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_19N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_20N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_21N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_22N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_3N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_4N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_5N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_6N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_7N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_8N"/>
      <xs:enumeration value="NAD_1927_UTM_Zone_9N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_10N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_11N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_12N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_13N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_14N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_15N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_16N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_17N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_18N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_19N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_20N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_21N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_22N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_23N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_3N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_4N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_5N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_6N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_7N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_8N"/>
      <xs:enumeration value="NAD_1983_UTM_Zone_9N"/>
      <xs:enumeration value="Abidjan_1987_UTM_Zone_29N"/>
      <xs:enumeration value="Abidjan_1987_UTM_Zone_30N"/>
      <xs:enumeration value="Adindan_UTM_Zone_37N"/>
      <xs:enumeration value="Adindan_UTM_Zone_38N"/>
      <xs:enumeration value="Afgooye_UTM_Zone_38N"/>
      <xs:enumeration value="Afgooye_UTM_Zone_39N"/>
      <xs:enumeration value="Ain_el_Abd_UTM_Zone_37N"/>
      <xs:enumeration value="Ain_el_Abd_UTM_Zone_38N"/>
      <xs:enumeration value="Ain_el_Abd_UTM_Zone_39N"/>
      <xs:enumeration value="Aratu_UTM_Zone_22S"/>
      <xs:enumeration value="Aratu_UTM_Zone_23S"/>
      <xs:enumeration value="Aratu_UTM_Zone_24S"/>
      <xs:enumeration value="Arc_1950_UTM_Zone_34S"/>
      <xs:enumeration value="Arc_1950_UTM_Zone_35S"/>
      <xs:enumeration value="Arc_1950_UTM_Zone_36S"/>
      <xs:enumeration value="Arc_1960_UTM_Zone_35N"/>
      <xs:enumeration value="Arc_1960_UTM_Zone_35S"/>
      <xs:enumeration value="Arc_1960_UTM_Zone_36N"/>
      <xs:enumeration value="Arc_1960_UTM_Zone_36S"/>
      <xs:enumeration value="Arc_1960_UTM_Zone_37N"/>
      <xs:enumeration value="Arc_1960_UTM_Zone_37S"/>
      <xs:enumeration value="ATS_1977_UTM_Zone_19N"/>
      <xs:enumeration value="ATS_1977_UTM_Zone_20N"/>
      <xs:enumeration value="Batavia_UTM_Zone_48S"/>
      <xs:enumeration value="Batavia_UTM_Zone_49S"/>
      <xs:enumeration value="Batavia_UTM_Zone_50S"/>
      <xs:enumeration value="Bissau_UTM_Zone_28N"/>
      <xs:enumeration value="Bogota_UTM_Zone_17N"/>
      <xs:enumeration value="Bogota_UTM_Zone_18N"/>
      <xs:enumeration value="Camacupa_UTM_Zone_32S"/>
      <xs:enumeration value="Camacupa_UTM_Zone_33S"/>
      <xs:enumeration value="Cape_UTM_Zone_34S"/>
      <xs:enumeration value="Cape_UTM_Zone_35S"/>
      <xs:enumeration value="Cape_UTM_Zone_36S"/>
      <xs:enumeration value="Carthage_UTM_Zone_32N"/>
      <xs:enumeration value="Conakry_1905_UTM_Zone_28N"/>
      <xs:enumeration value="Conakry_1905_UTM_Zone_29N"/>
      <xs:enumeration value="Corrego_Alegre_UTM_Zone_23S"/>
      <xs:enumeration value="Corrego_Alegre_UTM_Zone_24S"/>
      <xs:enumeration value="Dabola_UTM_Zone_28N"/>
      <xs:enumeration value="Dabola_UTM_Zone_29N"/>
      <xs:enumeration value="Datum_73_UTM_Zone_29N"/>
      <xs:enumeration value="Douala_UTM_Zone_32N"/>
      <xs:enumeration value="ED_1950_ED77_UTM_Zone_38N"/>
      <xs:enumeration value="ED_1950_ED77_UTM_Zone_39N"/>
      <xs:enumeration value="ED_1950_ED77_UTM_Zone_40N"/>
      <xs:enumeration value="ED_1950_ED77_UTM_Zone_41N"/>
      <xs:enumeration value="ELD_1979_UTM_Zone_32N"/>
      <xs:enumeration value="ELD_1979_UTM_Zone_33N"/>
      <xs:enumeration value="ELD_1979_UTM_Zone_34N"/>
      <xs:enumeration value="ELD_1979_UTM_Zone_35N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_28N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_29N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_30N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_31N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_32N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_33N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_34N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_35N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_36N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_37N"/>
      <xs:enumeration value="ETRF_1989_UTM_Zone_38N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_28N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_29N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_30N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_31N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_32N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_33N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_34N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_35N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_36N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_37N"/>
      <xs:enumeration value="ED_1950_UTM_Zone_38N"/>
      <xs:enumeration value="Fahud_UTM_Zone_39N"/>
      <xs:enumeration value="Fahud_UTM_Zone_40N"/>
      <xs:enumeration value="Garoua_UTM_Zone_33N"/>
      <xs:enumeration value="Graciosa_Base_SW_1948_UTM_Zone_26N"/>
      <xs:enumeration value="Hito_XVIII_1963_UTM_19S"/>
      <xs:enumeration value="Hong_Kong_1980_UTM_Zone_49N"/>
      <xs:enumeration value="Hong_Kong_1980_UTM_Zone_50N"/>
      <xs:enumeration value="Indian_1954_UTM_Zone_46N"/>
      <xs:enumeration value="Indian_1954_UTM_Zone_47N"/>
      <xs:enumeration value="Indian_1954_UTM_Zone_48N"/>
      <xs:enumeration value="Indian_1960_UTM_Zone_48N"/>
      <xs:enumeration value="Indian_1960_UTM_Zone_49N"/>
      <xs:enumeration value="Indian_1975_UTM_Zone_47N"/>
      <xs:enumeration value="Indian_1975_UTM_Zone_48N"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_46N"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_46S"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_47N"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_47S"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_48N"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_48S"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_49N"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_49S"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_50N"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_50S"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_51N"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_51S"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_52N"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_52S"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_53N"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_53S"/>
      <xs:enumeration value="Indonesian_1974_UTM_Zone_54S"/>
      <xs:enumeration value="IRENET95_UTM_Zone_29N"/>
      <xs:enumeration value="Kertau_UTM_Zone_47N"/>
      <xs:enumeration value="Kertau_UTM_Zone_48N"/>
      <xs:enumeration value="La_Canoa_UTM_Zone_18N"/>
      <xs:enumeration value="La_Canoa_UTM_Zone_19N"/>
      <xs:enumeration value="La_Canoa_UTM_Zone_20N"/>
      <xs:enumeration value="La_Canoa_UTM_Zone_21N"/>
      <xs:enumeration value="Locodjo_1965_UTM_Zone_29N"/>
      <xs:enumeration value="Locodjo_1965_UTM_Zone_30N"/>
      <xs:enumeration value="Lome_UTM_Zone_31N"/>
      <xs:enumeration value="Mporaloko_UTM_Zone_32N"/>
      <xs:enumeration value="Mporaloko_UTM_Zone_32S"/>
      <xs:enumeration value="Malongo_1987_UTM_Zone_32S"/>
      <xs:enumeration value="Massawa_UTM_Zone_37N"/>
      <xs:enumeration value="Mhast_UTM_Zone_32S"/>
      <xs:enumeration value="Minna_UTM_Zone_31N"/>
      <xs:enumeration value="Minna_UTM_Zone_32N"/>
      <xs:enumeration value="Moznet_UTM_Zone_36S"/>
      <xs:enumeration value="Moznet_UTM_Zone_37S"/>
      <xs:enumeration value="NAD_1927_BLM_Zone_14N"/>
      <xs:enumeration value="NAD_1927_BLM_Zone_15N"/>
      <xs:enumeration value="NAD_1927_BLM_Zone_16N"/>
      <xs:enumeration value="NAD_1927_BLM_Zone_17N"/>
      <xs:enumeration value="NAD_1983_HARN_UTM_Zone_2S"/>
      <xs:enumeration value="Nahrwan_1967_UTM_Zone_38N"/>
      <xs:enumeration value="Nahrwan_1967_UTM_Zone_39N"/>
      <xs:enumeration value="Nahrwan_1967_UTM_Zone_40N"/>
      <xs:enumeration value="Naparima_1955_UTM_Zone_20N"/>
      <xs:enumeration value="Naparima_1972_UTM_Zone_20N"/>
      <xs:enumeration value="NGN_UTM_Zone_38N"/>
      <xs:enumeration value="NGN_UTM_Zone_39N"/>
      <xs:enumeration value="NGO_1948_UTM_Zone_32N"/>
      <xs:enumeration value="NGO_1948_UTM_Zone_33N"/>
      <xs:enumeration value="NGO_1948_UTM_Zone_34N"/>
      <xs:enumeration value="NGO_1948_UTM_Zone_35N"/>
      <xs:enumeration value="Nord_Sahara_1959_UTM_Zone_29N"/>
      <xs:enumeration value="Nord_Sahara_1959_UTM_Zone_30N"/>
      <xs:enumeration value="Nord_Sahara_1959_UTM_Zone_31N"/>
      <xs:enumeration value="Nord_Sahara_1959_UTM_Zone_32N"/>
      <xs:enumeration value="NZGD_1949_UTM_Zone_58S"/>
      <xs:enumeration value="NZGD_1949_UTM_Zone_59S"/>
      <xs:enumeration value="NZGD_1949_UTM_Zone_60S"/>
      <xs:enumeration value="NZGD_2000_UTM_Zone_58S"/>
      <xs:enumeration value="NZGD_2000_UTM_Zone_59S"/>
      <xs:enumeration value="NZGD_2000_UTM_Zone_60S"/>
      <xs:enumeration value="Observ_Meteorologico_1939_UTM_Zone_25N"/>
      <xs:enumeration value="Old_Hawaiian_UTM_Zone_4N"/>
      <xs:enumeration value="Old_Hawaiian_UTM_Zone_5N"/>
      <xs:enumeration value="PDO_1993_UTM_Zone_39N"/>
      <xs:enumeration value="PDO_1993_UTM_Zone_40N"/>
      <xs:enumeration value="Pointe_Noire_UTM_Zone_32S"/>
      <xs:enumeration value="Porto_Santo_1936_UTM_Zone_28N"/>
      <xs:enumeration value="PSAD_1956_UTM_Zone_17S"/>
      <xs:enumeration value="PSAD_1956_UTM_Zone_18N"/>
      <xs:enumeration value="PSAD_1956_UTM_Zone_18S"/>
      <xs:enumeration value="PSAD_1956_UTM_Zone_19N"/>
      <xs:enumeration value="PSAD_1956_UTM_Zone_19S"/>
      <xs:enumeration value="PSAD_1956_UTM_Zone_20N"/>
      <xs:enumeration value="PSAD_1956_UTM_Zone_20S"/>
      <xs:enumeration value="PSAD_1956_UTM_Zone_21N"/>
      <xs:enumeration value="PSAD_1956_UTM_Zone_22S"/>
      <xs:enumeration value="Puerto_Rico_UTM_Zone_20N"/>
      <xs:enumeration value="Samboja_UTM_Zone_50S"/>
      <xs:enumeration value="Sao_Braz_UTM_Zone_26N"/>
      <xs:enumeration value="Sapper_Hill_1943_UTM_Zone_20S"/>
      <xs:enumeration value="Sapper_Hill_1943_UTM_Zone_21S"/>
      <xs:enumeration value="Schwarzeck_UTM_Zone_33S"/>
      <xs:enumeration value="Selvagem_Grande_1938_UTM_Zone_28N"/>
      <xs:enumeration value="Sierra_Leone_1968_UTM_Zone_28N"/>
      <xs:enumeration value="Sierra_Leone_1968_UTM_Zone_29N"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_17N"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_17S"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_18N"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_18S"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_19N"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_19S"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_20N"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_20S"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_21N"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_21S"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_22N"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_22S"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_23S"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_24S"/>
      <xs:enumeration value="SIRGAS_UTM_Zone_25S"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_17S"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_18N"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_18S"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_19N"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_19S"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_20N"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_20S"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_21N"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_21S"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_22N"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_22S"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_23S"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_24S"/>
      <xs:enumeration value="SAD_1969_UTM_Zone_25S"/>
      <xs:enumeration value="Sudan_UTM_Zone_35N"/>
      <xs:enumeration value="Sudan_UTM_Zone_36N"/>
      <xs:enumeration value="Tananarive_1925_UTM_Zone_38S"/>
      <xs:enumeration value="Tananarive_1925_UTM_Zone_39S"/>
      <xs:enumeration value="Tete_UTM_Zone_36S"/>
      <xs:enumeration value="Tete_UTM_Zone_37S"/>
      <xs:enumeration value="Timbalai_1948_UTM_Zone_49N"/>
      <xs:enumeration value="Timbalai_1948_UTM_Zone_50N"/>
      <xs:enumeration value="Tokyo_UTM_Zone_51N"/>
      <xs:enumeration value="Tokyo_UTM_Zone_52N"/>
      <xs:enumeration value="Tokyo_UTM_Zone_53N"/>
      <xs:enumeration value="Tokyo_UTM_Zone_54N"/>
      <xs:enumeration value="Tokyo_UTM_Zone_55N"/>
      <xs:enumeration value="Tokyo_UTM_Zone_56N"/>
      <xs:enumeration value="TC_1948_UTM_Zone_39N"/>
      <xs:enumeration value="TC_1948_UTM_Zone_40N"/>
      <xs:enumeration value="Yemen_NGN_1996_UTM_Zone_38N"/>
      <xs:enumeration value="Yemen_NGN_1996_UTM_Zone_39N"/>
      <xs:enumeration value="Yoff_1972_UTM_Zone_28N"/>
      <xs:enumeration value="Zanderij_1972_UTM_Zone_21N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_10N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_10S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_11N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_11S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_12N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_12S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_13N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_13S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_14N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_14S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_15N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_15S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_16N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_16S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_17N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_17S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_18N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_18S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_19N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_19S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_1N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_1S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_20N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_20S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_21N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_21S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_22N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_22S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_23N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_23S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_24N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_24S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_25N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_25S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_26N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_26S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_27N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_27S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_28N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_28S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_29N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_29S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_2N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_2S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_30N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_30S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_31N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_31S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_32N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_32S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_33N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_33S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_34N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_34S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_35N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_35S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_36N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_36S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_37N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_37S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_38N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_38S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_39N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_39S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_3N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_3S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_40N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_40S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_41N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_41S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_42N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_42S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_43N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_43S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_44N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_44S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_45N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_45S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_46N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_46S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_47N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_47S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_48N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_48S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_49N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_49S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_4N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_4S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_50N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_50S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_51N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_51S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_52N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_52S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_53N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_53S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_54N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_54S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_55N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_55S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_56N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_56S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_57N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_57S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_58N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_58S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_59N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_59S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_5N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_5S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_60N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_60S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_6N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_6S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_7N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_7S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_8N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_8S"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_9N"/>
      <xs:enumeration value="WGS_1972_UTM_Zone_9S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_10N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_10S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_11N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_11S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_12N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_12S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_13N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_13S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_14N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_14S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_15N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_15S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_16N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_16S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_17N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_17S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_18N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_18S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_19N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_19S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_1N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_1S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_20N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_20S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_21N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_21S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_22N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_22S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_23N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_23S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_24N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_24S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_25N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_25S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_26N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_26S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_27N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_27S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_28N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_28S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_29N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_29S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_2N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_2S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_30N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_30S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_31N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_31S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_32N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_32S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_33N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_33S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_34N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_34S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_35N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_35S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_36N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_36S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_37N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_37S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_38N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_38S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_39N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_39S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_3N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_3S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_40N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_40S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_41N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_41S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_42N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_42S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_43N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_43S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_44N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_44S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_45N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_45S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_46N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_46S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_47N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_47S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_48N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_48S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_49N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_49S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_4N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_4S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_50N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_50S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_51N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_51S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_52N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_52S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_53N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_53S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_54N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_54S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_55N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_55S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_56N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_56S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_57N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_57S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_58N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_58S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_59N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_59S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_5N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_5S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_60N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_60S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_6N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_6S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_7N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_7S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_8N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_8S"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_9N"/>
      <xs:enumeration value="WGS_1984_UTM_Zone_9S"/>
      <xs:enumeration value="World_Aitoff"/>
      <xs:enumeration value="World_Behrmann"/>
      <xs:enumeration value="World_Bonne"/>
      <xs:enumeration value="World_Craster_Parabolic"/>
      <xs:enumeration value="World_Cylindrical_Equal_Area"/>
      <xs:enumeration value="World_Eckert_I"/>
      <xs:enumeration value="World_Eckert_II"/>
      <xs:enumeration value="World_Eckert_III"/>
      <xs:enumeration value="World_Eckert_IV"/>
      <xs:enumeration value="World_Eckert_V"/>
      <xs:enumeration value="World_Eckert_VI"/>
      <xs:enumeration value="World_Equidistant_Conic"/>
      <xs:enumeration value="World_Equidistant_Cylindrical"/>
      <xs:enumeration value="World_Flat_Polar_Quartic"/>
      <xs:enumeration value="World_Gall_Stereographic"/>
      <xs:enumeration value="World_Hammer_Aitoff"/>
      <xs:enumeration value="World_Loximuthal"/>
      <xs:enumeration value="World_Mercator"/>
      <xs:enumeration value="World_Miller_Cylindrical"/>
      <xs:enumeration value="World_Mollweide"/>
      <xs:enumeration value="World_Plate_Carree"/>
      <xs:enumeration value="World_Polyconic"/>
      <xs:enumeration value="World_Quartic_Authalic"/>
      <xs:enumeration value="World_Robinson"/>
      <xs:enumeration value="World_Sinusoidal"/>
      <xs:enumeration value="Sphere_Aitoff"/>
      <xs:enumeration value="Sphere_Behrmann"/>
      <xs:enumeration value="Sphere_Bonne"/>
      <xs:enumeration value="Sphere_Craster_Parabolic"/>
      <xs:enumeration value="Sphere_Cylindrical_Equal_Area"/>
      <xs:enumeration value="Sphere_Eckert_I"/>
      <xs:enumeration value="Sphere_Eckert_II"/>
      <xs:enumeration value="Sphere_Eckert_III"/>
      <xs:enumeration value="Sphere_Eckert_IV"/>
      <xs:enumeration value="Sphere_Eckert_V"/>
      <xs:enumeration value="Sphere_Eckert_VI"/>
      <xs:enumeration value="Sphere_Equidistant_Conic"/>
      <xs:enumeration value="Sphere_Equidistant_Cylindrical"/>
      <xs:enumeration value="Sphere_Flat_Polar_Quartic"/>
      <xs:enumeration value="Sphere_Gall_Stereographic"/>
      <xs:enumeration value="Sphere_Hammer_Aitoff"/>
      <xs:enumeration value="Sphere_Loximuthal"/>
      <xs:enumeration value="Sphere_Mercator"/>
      <xs:enumeration value="Sphere_Miller_Cylindrical"/>
      <xs:enumeration value="Sphere_Mollweide"/>
      <xs:enumeration value="Sphere_Plate_Carree"/>
      <xs:enumeration value="Sphere_Polyconic"/>
      <xs:enumeration value="Sphere_Quartic_Authalic"/>
      <xs:enumeration value="Sphere_Robinson"/>
      <xs:enumeration value="Sphere_Sinusoidal"/>
      <xs:enumeration value="Sphere_Times"/>
      <xs:enumeration value="Sphere_Van_der_Grinten_I"/>
      <xs:enumeration value="Sphere_Vertical_Perspective"/>
      <xs:enumeration value="Sphere_Winkel_I"/>
      <xs:enumeration value="Sphere_Winkel_II"/>
      <xs:enumeration value="Sphere_Winkel_Tripel_NGS"/>
      <xs:enumeration value="The_World_From_Space"/>
      <xs:enumeration value="World_Times"/>
      <xs:enumeration value="World_Van_der_Grinten_I"/>
      <xs:enumeration value="World_Vertical_Perspective"/>
      <xs:enumeration value="World_Winkel_I"/>
      <xs:enumeration value="World_Winkel_II"/>
      <xs:enumeration value="World_Winkel_Tripel_NGS"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / horizCoordSysDef
Namespace No namespace
Annotations
tooltip: Horizonal Coordinate System Definition

summary: The definition of a coordinate system

description: Terms and parameters necessary to define a geographic or projected coordinate
                system for horizonal distances.
Diagram
Diagram NO_NAMESPACE.tmp#horizCoordSysType_name NO_NAMESPACE.tmp#horizCoordSysType_geogCoordSys NO_NAMESPACE.tmp#horizCoordSysType_projCoordSys spatialReference-2_2_0.tmp#horizCoordSysType
Type horizCoordSysType
Properties
content complex
Model
Children geogCoordSys, projCoordSys
Instance
<horizCoordSysDef name="">
  <geogCoordSys name="">{1,1}</geogCoordSys>
  <projCoordSys>{1,1}</projCoordSys>
</horizCoordSysDef>
Attributes
QName Type Use
name xs:string required
Source
<xs:element name="horizCoordSysDef" type="horizCoordSysType">
  <xs:annotation>
    <xs:documentation>tooltip: Horizonal Coordinate System Definition summary: The definition of a coordinate system description: Terms and parameters necessary to define a geographic or projected coordinate system for horizonal distances.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element horizCoordSysType / geogCoordSys
Namespace No namespace
Annotations
tooltip: Geographic Coordinate System

summary: The coodinate system used to express the geographic
                           coordinates.

description:
Diagram
Diagram NO_NAMESPACE.tmp#geogCoordSysType_name NO_NAMESPACE.tmp#geogCoordSysType_datum NO_NAMESPACE.tmp#geogCoordSysType_spheroid NO_NAMESPACE.tmp#geogCoordSysType_primeMeridian NO_NAMESPACE.tmp#geogCoordSysType_unit spatialReference-2_2_0.tmp#geogCoordSysType
Type geogCoordSysType
Properties
content complex
Model
Children datum, primeMeridian, spheroid, unit
Instance
<geogCoordSys name="">
  <datum name="">{1,1}</datum>
  <spheroid denomFlatRatio="" name="" semiAxisMajor="">{1,1}</spheroid>
  <primeMeridian longitude="" name="">{1,1}</primeMeridian>
  <unit name="">{1,1}</unit>
</geogCoordSys>
Attributes
QName Type Use
name xs:string optional
Source
<xs:element name="geogCoordSys" type="geogCoordSysType">
  <xs:annotation>
    <xs:documentation>tooltip: Geographic Coordinate System summary: The coodinate system used to express the geographic coordinates. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element geogCoordSysType / datum
Namespace No namespace
Annotations
tooltip: Datum

summary: The point on the earth representing the origin for the geographic
            coordinates to which the coorinate system is related to.

description:
Diagram
Diagram NO_NAMESPACE.tmp#geogCoordSysType_geogCoordSysType_datum_name
Properties
content complex
Attributes
QName Type Use
name xs:string optional
Source
<xs:element name="datum">
  <xs:annotation>
    <xs:documentation>tooltip: Datum summary: The point on the earth representing the origin for the geographic coordinates to which the coorinate system is related to. description:</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="name" type="xs:string"/>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element geogCoordSysType / spheroid
Namespace No namespace
Annotations
tooltip: Spheroid

summary: An ellipse that is used to model the earth's surface.

description: An ellipse is used to define a idealized surface that ignores variation in elevation.
Diagram
Diagram NO_NAMESPACE.tmp#geogCoordSysType_geogCoordSysType_spheroid_name NO_NAMESPACE.tmp#geogCoordSysType_geogCoordSysType_spheroid_semiAxisMajor NO_NAMESPACE.tmp#geogCoordSysType_geogCoordSysType_spheroid_denomFlatRatio
Properties
content complex
Attributes
QName Type Use Annotation
denomFlatRatio xs:float optional
name xs:string optional
tooltip: Spheroid name

summary: The name of the spheroid.

description:
semiAxisMajor xs:float optional
tooltip: Semi-axis Major

summary: The larger of two orthogonal axes that define the ellipse

description:
Source
<xs:element name="spheroid">
  <xs:annotation>
    <xs:documentation>tooltip: Spheroid summary: An ellipse that is used to model the earth's surface. description: An ellipse is used to define a idealized surface that ignores variation in elevation.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="name" type="xs:string">
      <xs:annotation>
        <xs:documentation>tooltip: Spheroid name summary: The name of the spheroid. description:</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="semiAxisMajor" type="xs:float">
      <xs:annotation>
        <xs:documentation>tooltip: Semi-axis Major summary: The larger of two orthogonal axes that define the ellipse description:</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="denomFlatRatio" type="xs:float"/>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element geogCoordSysType / primeMeridian
Namespace No namespace
Diagram
Diagram NO_NAMESPACE.tmp#geogCoordSysType_geogCoordSysType_primeMeridian_name NO_NAMESPACE.tmp#geogCoordSysType_geogCoordSysType_primeMeridian_longitude
Properties
content complex
Attributes
QName Type Use Annotation
longitude restriction of xs:float required
tooltip: Longitude

summary: The longitude of the Prime Meridian

description:
name xs:string optional
tooltip: Prime Meridian Name

summary: The name of the Prime Meridian

description:
Source
<xs:element name="primeMeridian">
  <xs:complexType>
    <xs:attribute name="name" type="xs:string">
      <xs:annotation>
        <xs:documentation>tooltip: Prime Meridian Name summary: The name of the Prime Meridian description:</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="longitude" use="required">
      <xs:annotation>
        <xs:documentation>tooltip: Longitude summary: The longitude of the Prime Meridian description:</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:float">
          <xs:minInclusive value="-180"/>
          <xs:maxInclusive value="180"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element geogCoordSysType / unit
Namespace No namespace
Annotations
tooltip: Unit

summary: The unit of angle by which coordinates are expressed.

description:
Diagram
Diagram NO_NAMESPACE.tmp#geogCoordSysType_geogCoordSysType_unit_name
Properties
content complex
Attributes
QName Type Use Annotation
name angleUnits required
tooltip: Unit Name

summary: The name of the unit of measure .

description:
Source
<xs:element name="unit">
  <xs:annotation>
    <xs:documentation>tooltip: Unit summary: The unit of angle by which coordinates are expressed. description:</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="name" type="angleUnits" use="required">
      <xs:annotation>
        <xs:documentation>tooltip: Unit Name summary: The name of the unit of measure . description:</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element horizCoordSysType / projCoordSys
Namespace No namespace
Annotations
tooltip: Projected Coordinate System

summary: The coodinate system used to express planar coordinates.

description:
Diagram
Diagram NO_NAMESPACE.tmp#horizCoordSysType_horizCoordSysType_projCoordSys_geogCoordSys NO_NAMESPACE.tmp#horizCoordSysType_horizCoordSysType_projCoordSys_projection
Properties
content complex
Model
Children geogCoordSys, projection
Instance
<projCoordSys>
  <geogCoordSys name="">{1,1}</geogCoordSys>
  <projection name="">{1,1}</projection>
</projCoordSys>
Source
<xs:element name="projCoordSys">
  <xs:annotation>
    <xs:documentation>tooltip: Projected Coordinate System summary: The coodinate system used to express planar coordinates. description:</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="geogCoordSys" type="geogCoordSysType">
        <xs:annotation>
          <xs:documentation>tooltip: Geographic Coordinate System summary: The coodinate system used to express the geographic coordinates. description:</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="projection">
        <xs:annotation>
          <xs:documentation>tooltip: Projection summary: The method used to tranform between geographic and planar coordinates. description:</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="parameter" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Parameter summary: A parameter required by the projection method. description: Most projections require one or more parameters to control the orientation and positon of the projected coordinate plane.</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:attribute name="name" type="xs:string" use="required">
                  <xs:annotation>
                    <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: If the paramter corresponds to one that has been defined in the existing eml-SpatialReferenceDictionary, then that name should be used to enhance recogonizability.</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
                <xs:attribute name="description" type="xs:string" use="optional">
                  <xs:annotation>
                    <xs:documentation>tooltip: Parameter Description summary: A description of the Parameter. description:</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
                <xs:attribute name="value" type="xs:anySimpleType" use="required">
                  <xs:annotation>
                    <xs:documentation>tooltip: Parameter Value summary: The value supplied for the parameter description:</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
            <xs:element name="unit">
              <xs:annotation>
                <xs:documentation>tooltip: Projection Unit summary: The unit of measure coordinates are expressed in. description:</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                <xs:attribute name="name" type="lengthUnits" use="required">
                  <xs:annotation>
                    <xs:documentation>tooltip: Projection Unit Name summary: The name of the unit of measure. description:</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="name" type="xs:string">
            <xs:annotation>
              <xs:documentation>tooltip: Projection Name summary: The name of the projection method. description: EML does not attempt to document the details of the particular projection algorithm. It is incumbent on metadata provider to ensure that the meaning of the names used to identify the method and its parameters will be as clear as possible.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element horizCoordSysType / projCoordSys / geogCoordSys
Namespace No namespace
Annotations
tooltip: Geographic Coordinate System

summary: The coodinate system used to express the geographic
                           coordinates.

description:
Diagram
Diagram NO_NAMESPACE.tmp#geogCoordSysType_name NO_NAMESPACE.tmp#geogCoordSysType_datum NO_NAMESPACE.tmp#geogCoordSysType_spheroid NO_NAMESPACE.tmp#geogCoordSysType_primeMeridian NO_NAMESPACE.tmp#geogCoordSysType_unit spatialReference-2_2_0.tmp#geogCoordSysType
Type geogCoordSysType
Properties
content complex
Model
Children datum, primeMeridian, spheroid, unit
Instance
<geogCoordSys name="">
  <datum name="">{1,1}</datum>
  <spheroid denomFlatRatio="" name="" semiAxisMajor="">{1,1}</spheroid>
  <primeMeridian longitude="" name="">{1,1}</primeMeridian>
  <unit name="">{1,1}</unit>
</geogCoordSys>
Attributes
QName Type Use
name xs:string optional
Source
<xs:element name="geogCoordSys" type="geogCoordSysType">
  <xs:annotation>
    <xs:documentation>tooltip: Geographic Coordinate System summary: The coodinate system used to express the geographic coordinates. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element horizCoordSysType / projCoordSys / projection
Namespace No namespace
Annotations
tooltip: Projection

summary: The method used to tranform between geographic and planar coordinates.
                  

description:
Diagram
Diagram NO_NAMESPACE.tmp#horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_name NO_NAMESPACE.tmp#horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_parameter NO_NAMESPACE.tmp#horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_unit
Properties
content complex
Model
Children parameter, unit
Instance
<projection name="">
  <parameter description="" name="" value="">{1,unbounded}</parameter>
  <unit name="">{1,1}</unit>
</projection>
Attributes
QName Type Use Annotation
name xs:string optional
tooltip: Projection Name

summary: The name of the projection method.

description: EML does not attempt to document the details
                      of the particular projection algorithm. It is incumbent on metadata provider
                      to ensure that the meaning of the names used to identify the method and its parameters will be
                      as clear as possible.
Source
<xs:element name="projection">
  <xs:annotation>
    <xs:documentation>tooltip: Projection summary: The method used to tranform between geographic and planar coordinates. description:</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="parameter" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Parameter summary: A parameter required by the projection method. description: Most projections require one or more parameters to control the orientation and positon of the projected coordinate plane.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:attribute name="name" type="xs:string" use="required">
            <xs:annotation>
              <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: If the paramter corresponds to one that has been defined in the existing eml-SpatialReferenceDictionary, then that name should be used to enhance recogonizability.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="description" type="xs:string" use="optional">
            <xs:annotation>
              <xs:documentation>tooltip: Parameter Description summary: A description of the Parameter. description:</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="value" type="xs:anySimpleType" use="required">
            <xs:annotation>
              <xs:documentation>tooltip: Parameter Value summary: The value supplied for the parameter description:</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
      <xs:element name="unit">
        <xs:annotation>
          <xs:documentation>tooltip: Projection Unit summary: The unit of measure coordinates are expressed in. description:</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:attribute name="name" type="lengthUnits" use="required">
            <xs:annotation>
              <xs:documentation>tooltip: Projection Unit Name summary: The name of the unit of measure. description:</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="name" type="xs:string">
      <xs:annotation>
        <xs:documentation>tooltip: Projection Name summary: The name of the projection method. description: EML does not attempt to document the details of the particular projection algorithm. It is incumbent on metadata provider to ensure that the meaning of the names used to identify the method and its parameters will be as clear as possible.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element horizCoordSysType / projCoordSys / projection / parameter
Namespace No namespace
Annotations
tooltip: Parameter

summary: A parameter required by the projection method.

description: Most projections require one or more parameters to control the
                          orientation and positon of the projected coordinate plane.
Diagram
Diagram NO_NAMESPACE.tmp#horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_parameter_name NO_NAMESPACE.tmp#horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_parameter_description NO_NAMESPACE.tmp#horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_parameter_value
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use Annotation
description xs:string optional
tooltip: Parameter Description

summary: A description of the Parameter.

description:
name xs:string required
tooltip: Parameter Name

summary: The name of the parameter.

description: If the paramter corresponds to one that has been
                            defined in the existing eml-SpatialReferenceDictionary, then that name should be
                            used to enhance recogonizability.
value required
tooltip: Parameter Value

summary: The value supplied for the parameter

description:
Source
<xs:element name="parameter" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter summary: A parameter required by the projection method. description: Most projections require one or more parameters to control the orientation and positon of the projected coordinate plane.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="name" type="xs:string" use="required">
      <xs:annotation>
        <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: If the paramter corresponds to one that has been defined in the existing eml-SpatialReferenceDictionary, then that name should be used to enhance recogonizability.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="description" type="xs:string" use="optional">
      <xs:annotation>
        <xs:documentation>tooltip: Parameter Description summary: A description of the Parameter. description:</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="value" type="xs:anySimpleType" use="required">
      <xs:annotation>
        <xs:documentation>tooltip: Parameter Value summary: The value supplied for the parameter description:</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element horizCoordSysType / projCoordSys / projection / unit
Namespace No namespace
Annotations
tooltip: Projection Unit

summary: The unit of measure coordinates are expressed in.

description:
Diagram
Diagram NO_NAMESPACE.tmp#horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_horizCoordSysType_horizCoordSysType_projCoordSys_horizCoordSysType_horizCoordSysType_projCoordSys_projection_unit_name
Properties
content complex
Attributes
QName Type Use Annotation
name lengthUnits required
tooltip: Projection Unit Name

summary: The name of the unit of measure.

description:
Source
<xs:element name="unit">
  <xs:annotation>
    <xs:documentation>tooltip: Projection Unit summary: The unit of measure coordinates are expressed in. description:</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="name" type="lengthUnits" use="required">
      <xs:annotation>
        <xs:documentation>tooltip: Projection Unit Name summary: The name of the unit of measure. description:</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys
Namespace No namespace
Annotations
tooltip: Vertical Coordinate System Definition

summary: The reference frame or system from which vertical
              distances (altitudes or depths) are measured.

description:
Diagram
Diagram NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_altitudeSysDef NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_depthSysDef
Properties
content complex
minOccurs 0
Model
Children altitudeSysDef, depthSysDef
Instance
<vertCoordSys>
  <altitudeSysDef>{0,1}</altitudeSysDef>
  <depthSysDef>{0,1}</depthSysDef>
</vertCoordSys>
Source
<xs:element name="vertCoordSys" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Vertical Coordinate System Definition summary: The reference frame or system from which vertical distances (altitudes or depths) are measured. description:</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="altitudeSysDef" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Altitude System Definition summary: the reference frame or system from which altitudes (elevations) are measured. description: The term "altitude"' is used instead of the common term "elevation" to conform to the terminology in Federal Information Processing Standards 70-1 and 173.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="altitudeDatumName" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Altitude Datum Name summary: The identification given to the surface taken as the surface of reference from which altitudes are measured. description:</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="altitudeResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Altitude Resolution summary: The minimum distance possible between two adjacent altitude values, expressed in Altitude Distance Units of measure. description:</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="altitudeDistanceUnits" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Altitude Distance Units summary: Units in which altitude is measured. description:</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="altitudeEncodingMethod" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Altitude Encoding Method summary: The means used to encode the altitudes. description:</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="depthSysDef" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Depth System Definition summary: The reference frame or system from which depths are measured. description:</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="depthDatumName" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Depth Datum Name summary: The identification given to surface of reference from which depths are measured. description:</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="depthResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
              <xs:annotation>
                <xs:documentation>tooltip: Depth Resolution summary: The minimum distance possible between two adjacent depth values, expressed in Depth Distance Units of measure. description:</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="depthDistanceUnits" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Depth Distance Units summary: The units in which depths are recorded. description:</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="depthEncodingMethod" type="res:NonEmptyStringType">
              <xs:annotation>
                <xs:documentation>tooltip: Depth Encoding Method summary: The means used to encode depths. description:</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / altitudeSysDef
Namespace No namespace
Annotations
tooltip: Altitude System Definition

summary: the reference frame or system from which
                    altitudes (elevations) are measured.

description: The term "altitude"' is used instead of
                    the common term "elevation" to conform to the terminology
                    in Federal Information Processing Standards 70-1 and
                    173.
Diagram
Diagram NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_SpatialReferenceType_SpatialReferenceType_vertCoordSys_altitudeSysDef_altitudeDatumName NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_SpatialReferenceType_SpatialReferenceType_vertCoordSys_altitudeSysDef_altitudeResolution NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_SpatialReferenceType_SpatialReferenceType_vertCoordSys_altitudeSysDef_altitudeDistanceUnits NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_SpatialReferenceType_SpatialReferenceType_vertCoordSys_altitudeSysDef_altitudeEncodingMethod
Properties
content complex
minOccurs 0
Model
Children altitudeDatumName, altitudeDistanceUnits, altitudeEncodingMethod, altitudeResolution
Instance
<altitudeSysDef>
  <altitudeDatumName>{1,1}</altitudeDatumName>
  <altitudeResolution>{1,unbounded}</altitudeResolution>
  <altitudeDistanceUnits>{1,1}</altitudeDistanceUnits>
  <altitudeEncodingMethod>{1,1}</altitudeEncodingMethod>
</altitudeSysDef>
Source
<xs:element name="altitudeSysDef" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Altitude System Definition summary: the reference frame or system from which altitudes (elevations) are measured. description: The term "altitude"' is used instead of the common term "elevation" to conform to the terminology in Federal Information Processing Standards 70-1 and 173.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="altitudeDatumName" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Altitude Datum Name summary: The identification given to the surface taken as the surface of reference from which altitudes are measured. description:</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="altitudeResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Altitude Resolution summary: The minimum distance possible between two adjacent altitude values, expressed in Altitude Distance Units of measure. description:</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="altitudeDistanceUnits" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Altitude Distance Units summary: Units in which altitude is measured. description:</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="altitudeEncodingMethod" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Altitude Encoding Method summary: The means used to encode the altitudes. description:</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / altitudeSysDef / altitudeDatumName
Namespace No namespace
Annotations
tooltip: Altitude Datum Name

summary: The identification given to the surface
                          taken as the surface of reference from which
                          altitudes are measured.

description:
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="altitudeDatumName" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Altitude Datum Name summary: The identification given to the surface taken as the surface of reference from which altitudes are measured. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / altitudeSysDef / altitudeResolution
Namespace No namespace
Annotations
tooltip: Altitude Resolution

summary: The minimum distance possible between
                          two adjacent altitude values, expressed in Altitude
                          Distance Units of measure.

description:
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="altitudeResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Altitude Resolution summary: The minimum distance possible between two adjacent altitude values, expressed in Altitude Distance Units of measure. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / altitudeSysDef / altitudeDistanceUnits
Namespace No namespace
Annotations
tooltip: Altitude Distance Units

summary: Units in which altitude is
                          measured.

description:
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="altitudeDistanceUnits" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Altitude Distance Units summary: Units in which altitude is measured. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / altitudeSysDef / altitudeEncodingMethod
Namespace No namespace
Annotations
tooltip: Altitude Encoding Method

summary: The means used to encode the
                          altitudes.

description:
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="altitudeEncodingMethod" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Altitude Encoding Method summary: The means used to encode the altitudes. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / depthSysDef
Namespace No namespace
Annotations
tooltip: Depth System Definition

summary: The reference frame or system from which
                    depths are measured.

description:
Diagram
Diagram NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_SpatialReferenceType_SpatialReferenceType_vertCoordSys_depthSysDef_depthDatumName NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_SpatialReferenceType_SpatialReferenceType_vertCoordSys_depthSysDef_depthResolution NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_SpatialReferenceType_SpatialReferenceType_vertCoordSys_depthSysDef_depthDistanceUnits NO_NAMESPACE.tmp#SpatialReferenceType_SpatialReferenceType_vertCoordSys_SpatialReferenceType_SpatialReferenceType_vertCoordSys_depthSysDef_depthEncodingMethod
Properties
content complex
minOccurs 0
Model
Children depthDatumName, depthDistanceUnits, depthEncodingMethod, depthResolution
Instance
<depthSysDef>
  <depthDatumName>{1,1}</depthDatumName>
  <depthResolution>{1,unbounded}</depthResolution>
  <depthDistanceUnits>{1,1}</depthDistanceUnits>
  <depthEncodingMethod>{1,1}</depthEncodingMethod>
</depthSysDef>
Source
<xs:element name="depthSysDef" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Depth System Definition summary: The reference frame or system from which depths are measured. description:</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="depthDatumName" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Depth Datum Name summary: The identification given to surface of reference from which depths are measured. description:</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="depthResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Depth Resolution summary: The minimum distance possible between two adjacent depth values, expressed in Depth Distance Units of measure. description:</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="depthDistanceUnits" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Depth Distance Units summary: The units in which depths are recorded. description:</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="depthEncodingMethod" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Depth Encoding Method summary: The means used to encode depths. description:</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / depthSysDef / depthDatumName
Namespace No namespace
Annotations
tooltip: Depth Datum Name

summary: The identification given to surface of
                          reference from which depths are
                          measured.

description:
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="depthDatumName" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Depth Datum Name summary: The identification given to surface of reference from which depths are measured. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / depthSysDef / depthResolution
Namespace No namespace
Annotations
tooltip: Depth Resolution

summary: The minimum distance possible between
                          two adjacent depth values, expressed in Depth
                          Distance Units of measure.

description:
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="depthResolution" type="res:NonEmptyStringType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Depth Resolution summary: The minimum distance possible between two adjacent depth values, expressed in Depth Distance Units of measure. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / depthSysDef / depthDistanceUnits
Namespace No namespace
Annotations
tooltip: Depth Distance Units

summary: The units in which depths are
                          recorded.

description:
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="depthDistanceUnits" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Depth Distance Units summary: The units in which depths are recorded. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialReferenceType / vertCoordSys / depthSysDef / depthEncodingMethod
Namespace No namespace
Annotations
tooltip: Depth Encoding Method

summary: The means used to encode
                          depths.

description:
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="depthEncodingMethod" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Depth Encoding Method summary: The means used to encode depths. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Element SpatialRasterType / georeferenceInfo
Namespace No namespace
Annotations
tooltip: Georeferenc information

summary: Information on how to position the grid within the coordinate
                    system defined in the spatial reference module.

description: Information on how to position the grid within the coordinate
                    system defined in the spatial reference module.
Diagram
Diagram NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_cornerPoint NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_controlPoint NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_bilinearFit
Properties
content complex
minOccurs 0
Model
Children bilinearFit, controlPoint, cornerPoint
Instance
<georeferenceInfo>
  <cornerPoint>{1,4}</cornerPoint>
  <controlPoint>{1,unbounded}</controlPoint>
  <bilinearFit>{1,1}</bilinearFit>
</georeferenceInfo>
Source
<xs:element name="georeferenceInfo" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Georeferenc information summary: Information on how to position the grid within the coordinate system defined in the spatial reference module. description: Information on how to position the grid within the coordinate system defined in the spatial reference module.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="cornerPoint" maxOccurs="4">
        <xs:annotation>
          <xs:documentation>tooltip: Corner point summary: Location of a corner on a rectified grid within the coordinate system. description: Location of a corner on the coordinate system defined in the spatial reference module. Use this element when the rows and columns of the grid are aligned with the coordinate system. One or more corner points are needed to locate a rectified grid.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="xCoordinate" type="xs:float">
              <xs:annotation>
                <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="yCoordinate" type="xs:float">
              <xs:annotation>
                <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="pointInPixel">
              <xs:annotation>
                <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="upperLeft"/>
                  <xs:enumeration value="upperRight"/>
                  <xs:enumeration value="lowerRight"/>
                  <xs:enumeration value="lowerLeft"/>
                  <xs:enumeration value="center"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
            <xs:element name="corner" type="rasterOriginType">
              <xs:annotation>
                <xs:documentation>tooltip: Corner summary: Identification of the corner in the grid corresponding to the coordinates provided. description: Identification of the corner in the grid corresponding to the coordinates provided.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="controlPoint" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Georeference Point summary: A point defined in both grid cell and georeferenced coordinates that is used to position the raster grid within the coordinate system defined in the spatialReference modoule. description: If the grid is rectified to the coordinate system, then a single point may be used to position the grid. Otherwise, a series of points is necessary to fit the grid to the coordinate system.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="column" type="xs:int">
              <xs:annotation>
                <xs:documentation>tooltip: Column summary: Column location of the georeferencing point in the grid. description: Column location of the georeferencing point indicated as the nth column counting the cell indicated in rasterOrigin as column 1.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="row" type="xs:int">
              <xs:annotation>
                <xs:documentation>tooltip: Row summary: Row location of the georeferencing point in the grid. description: Row location of the georeferencing point indicated as the nth row counting the cell indicated in rasterOrigin as row 1.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="xCoordinate" type="xs:float">
              <xs:annotation>
                <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="yCoordinate" type="xs:float">
              <xs:annotation>
                <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="pointInPixel">
              <xs:annotation>
                <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="upperLeft"/>
                  <xs:enumeration value="upperRight"/>
                  <xs:enumeration value="lowerRight"/>
                  <xs:enumeration value="lowerLeft"/>
                  <xs:enumeration value="center"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="bilinearFit">
        <xs:annotation>
          <xs:documentation>tooltip: Bilinear Fit summary: Terms of a bilinear model to fit the grid to the coordinate system. description: Intercept and slope terms to describe the orientation and position of the grid to the coordinate system based on corner point identified in the rasterOrigin element. defined in the spatial Reference module.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="xIntercept" type="xs:float">
              <xs:annotation>
                <xs:documentation>tooltip: X Intercept summary: Location of the rasterOrigin point on the x axis of the the coordinate system. description: X Intercept of the rasterOrigin point within the coordinate system.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="xSlope" type="xs:float">
              <xs:annotation>
                <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into x coordinates. description: Slope describing transformation of grid cell distances into x coordinates.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="yIntercept" type="xs:float">
              <xs:annotation>
                <xs:documentation>tooltip: Y Intercept summary: Location of the rasterOrigin point on the y axis of the the coordinate system. description: Location of the rasterOrigin point on the y axis of the the coordinate system.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="ySlope" type="xs:float">
              <xs:annotation>
                <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into y axis coordinates. description: Slope describing transformation of grid cell distances into y axis coordinates.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / cornerPoint
Namespace No namespace
Annotations
tooltip: Corner point

summary: Location of a corner on a rectified grid within the coordinate
                    system.

description: Location of a corner on the coordinate system defined in
                    the spatial reference module. Use this element when the rows and columns
                     of the grid are aligned with the coordinate system. One or more corner
                     points are needed to locate a rectified grid.
Diagram
Diagram NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_cornerPoint_xCoordinate NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_cornerPoint_yCoordinate NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_cornerPoint_pointInPixel NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_cornerPoint_corner
Properties
content complex
maxOccurs 4
Model
Children corner, pointInPixel, xCoordinate, yCoordinate
Instance
<cornerPoint>
  <xCoordinate>{1,1}</xCoordinate>
  <yCoordinate>{1,1}</yCoordinate>
  <pointInPixel>{1,1}</pointInPixel>
  <corner>{1,1}</corner>
</cornerPoint>
Source
<xs:element name="cornerPoint" maxOccurs="4">
  <xs:annotation>
    <xs:documentation>tooltip: Corner point summary: Location of a corner on a rectified grid within the coordinate system. description: Location of a corner on the coordinate system defined in the spatial reference module. Use this element when the rows and columns of the grid are aligned with the coordinate system. One or more corner points are needed to locate a rectified grid.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="xCoordinate" type="xs:float">
        <xs:annotation>
          <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="yCoordinate" type="xs:float">
        <xs:annotation>
          <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="pointInPixel">
        <xs:annotation>
          <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="upperLeft"/>
            <xs:enumeration value="upperRight"/>
            <xs:enumeration value="lowerRight"/>
            <xs:enumeration value="lowerLeft"/>
            <xs:enumeration value="center"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="corner" type="rasterOriginType">
        <xs:annotation>
          <xs:documentation>tooltip: Corner summary: Identification of the corner in the grid corresponding to the coordinates provided. description: Identification of the corner in the grid corresponding to the coordinates provided.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / cornerPoint / xCoordinate
Namespace No namespace
Annotations
tooltip: X coordinate

summary: X Location of the georeferencing point in the X diminsion of the
                       coordinate system.

description: Location of the georeferencing point expressed in units of the
                           coordinate system
                      defined in the spatial Reference module.
Diagram
Diagram
Type xs:float
Properties
content simple
Source
<xs:element name="xCoordinate" type="xs:float">
  <xs:annotation>
    <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / cornerPoint / yCoordinate
Namespace No namespace
Annotations
tooltip: Y coordinate

summary: Location of the georeferencing point in the Y dimension of the
                       coordinate system.

description: Y Location of the georeferencing point expressed in units of the coordinate system
                      defined in the spatial Reference module.
Diagram
Diagram
Type xs:float
Properties
content simple
Source
<xs:element name="yCoordinate" type="xs:float">
  <xs:annotation>
    <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / cornerPoint / pointInPixel
Namespace No namespace
Annotations
tooltip: Point in Pixel

summary: Location within the pixel of the georeferencing point.

description: Location within the pixel of the georeferencing point.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration upperLeft
enumeration upperRight
enumeration lowerRight
enumeration lowerLeft
enumeration center
Source
<xs:element name="pointInPixel">
  <xs:annotation>
    <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="upperLeft"/>
      <xs:enumeration value="upperRight"/>
      <xs:enumeration value="lowerRight"/>
      <xs:enumeration value="lowerLeft"/>
      <xs:enumeration value="center"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / cornerPoint / corner
Namespace No namespace
Annotations
tooltip: Corner

summary: Identification of the corner in the grid corresponding to the
                    coordinates provided.

description: Identification of the corner in the grid corresponding to the
                    coordinates provided.
Diagram
Diagram spatialRaster-2_2_0.tmp#rasterOriginType
Type rasterOriginType
Properties
content simple
Facets
enumeration Upper Left
enumeration Lower Left
enumeration Upper Right
enumeration Lower Right
Source
<xs:element name="corner" type="rasterOriginType">
  <xs:annotation>
    <xs:documentation>tooltip: Corner summary: Identification of the corner in the grid corresponding to the coordinates provided. description: Identification of the corner in the grid corresponding to the coordinates provided.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / controlPoint
Namespace No namespace
Annotations
tooltip: Georeference Point

summary: A point defined in both grid cell and georeferenced
                    coordinates that is used to position  the raster grid within the
                    coordinate system defined in the spatialReference modoule.

description: If the grid is rectified to the coordinate system, then
                     a single point may be used to position the grid. Otherwise, a series of
                     points is necessary to fit the grid to the coordinate system.
Diagram
Diagram NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_controlPoint_column NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_controlPoint_row NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_controlPoint_xCoordinate NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_controlPoint_yCoordinate NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_controlPoint_pointInPixel
Properties
content complex
maxOccurs unbounded
Model
Children column, pointInPixel, row, xCoordinate, yCoordinate
Instance
<controlPoint>
  <column>{1,1}</column>
  <row>{1,1}</row>
  <xCoordinate>{1,1}</xCoordinate>
  <yCoordinate>{1,1}</yCoordinate>
  <pointInPixel>{1,1}</pointInPixel>
</controlPoint>
Source
<xs:element name="controlPoint" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Georeference Point summary: A point defined in both grid cell and georeferenced coordinates that is used to position the raster grid within the coordinate system defined in the spatialReference modoule. description: If the grid is rectified to the coordinate system, then a single point may be used to position the grid. Otherwise, a series of points is necessary to fit the grid to the coordinate system.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="column" type="xs:int">
        <xs:annotation>
          <xs:documentation>tooltip: Column summary: Column location of the georeferencing point in the grid. description: Column location of the georeferencing point indicated as the nth column counting the cell indicated in rasterOrigin as column 1.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="row" type="xs:int">
        <xs:annotation>
          <xs:documentation>tooltip: Row summary: Row location of the georeferencing point in the grid. description: Row location of the georeferencing point indicated as the nth row counting the cell indicated in rasterOrigin as row 1.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="xCoordinate" type="xs:float">
        <xs:annotation>
          <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="yCoordinate" type="xs:float">
        <xs:annotation>
          <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="pointInPixel">
        <xs:annotation>
          <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point.</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="upperLeft"/>
            <xs:enumeration value="upperRight"/>
            <xs:enumeration value="lowerRight"/>
            <xs:enumeration value="lowerLeft"/>
            <xs:enumeration value="center"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / controlPoint / column
Namespace No namespace
Annotations
tooltip: Column

summary: Column location of the georeferencing point in the grid.

description: Column location of the georeferencing point indicated as the nth column
                      counting the cell indicated in rasterOrigin as column 1.
Diagram
Diagram
Type xs:int
Properties
content simple
Source
<xs:element name="column" type="xs:int">
  <xs:annotation>
    <xs:documentation>tooltip: Column summary: Column location of the georeferencing point in the grid. description: Column location of the georeferencing point indicated as the nth column counting the cell indicated in rasterOrigin as column 1.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / controlPoint / row
Namespace No namespace
Annotations
tooltip: Row

summary: Row location of the georeferencing point in the grid.

description: Row location of the georeferencing point indicated as the nth row
                      counting the cell indicated in rasterOrigin as row 1.
Diagram
Diagram
Type xs:int
Properties
content simple
Source
<xs:element name="row" type="xs:int">
  <xs:annotation>
    <xs:documentation>tooltip: Row summary: Row location of the georeferencing point in the grid. description: Row location of the georeferencing point indicated as the nth row counting the cell indicated in rasterOrigin as row 1.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / controlPoint / xCoordinate
Namespace No namespace
Annotations
tooltip: X coordinate

summary: X Location of the georeferencing point in the X diminsion of the
                       coordinate system.

description: Location of the georeferencing point expressed in units of the coordinate system
                      defined in the spatial Reference module.
Diagram
Diagram
Type xs:float
Properties
content simple
Source
<xs:element name="xCoordinate" type="xs:float">
  <xs:annotation>
    <xs:documentation>tooltip: X coordinate summary: X Location of the georeferencing point in the X diminsion of the coordinate system. description: Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / controlPoint / yCoordinate
Namespace No namespace
Annotations
tooltip: Y coordinate

summary: Location of the georeferencing point in the Y dimension of the
                       coordinate system.

description: Y Location of the georeferencing point expressed in units of the
                           coordinate system
                      defined in the spatial Reference module.
Diagram
Diagram
Type xs:float
Properties
content simple
Source
<xs:element name="yCoordinate" type="xs:float">
  <xs:annotation>
    <xs:documentation>tooltip: Y coordinate summary: Location of the georeferencing point in the Y dimension of the coordinate system. description: Y Location of the georeferencing point expressed in units of the coordinate system defined in the spatial Reference module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / controlPoint / pointInPixel
Namespace No namespace
Annotations
tooltip: Point in Pixel

summary: Location within the pixel of the georeferencing point.

description: Location within the pixel of the georeferencing point.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration upperLeft
enumeration upperRight
enumeration lowerRight
enumeration lowerLeft
enumeration center
Source
<xs:element name="pointInPixel">
  <xs:annotation>
    <xs:documentation>tooltip: Point in Pixel summary: Location within the pixel of the georeferencing point. description: Location within the pixel of the georeferencing point.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="upperLeft"/>
      <xs:enumeration value="upperRight"/>
      <xs:enumeration value="lowerRight"/>
      <xs:enumeration value="lowerLeft"/>
      <xs:enumeration value="center"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / bilinearFit
Namespace No namespace
Annotations
tooltip: Bilinear Fit

summary: Terms of a bilinear model to fit the grid to the coordinate system.
                          

description: Intercept and slope terms to describe the orientation and position of the
                          grid to the coordinate system based on corner point identified in the rasterOrigin element.
                      defined in the spatial Reference module.
Diagram
Diagram NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_bilinearFit_xIntercept NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_bilinearFit_xSlope NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_bilinearFit_yIntercept NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_georeferenceInfo_SpatialRasterType_SpatialRasterType_georeferenceInfo_bilinearFit_ySlope
Properties
content complex
Model
Children xIntercept, xSlope, yIntercept, ySlope
Instance
<bilinearFit>
  <xIntercept>{1,1}</xIntercept>
  <xSlope>{1,1}</xSlope>
  <yIntercept>{1,1}</yIntercept>
  <ySlope>{1,1}</ySlope>
</bilinearFit>
Source
<xs:element name="bilinearFit">
  <xs:annotation>
    <xs:documentation>tooltip: Bilinear Fit summary: Terms of a bilinear model to fit the grid to the coordinate system. description: Intercept and slope terms to describe the orientation and position of the grid to the coordinate system based on corner point identified in the rasterOrigin element. defined in the spatial Reference module.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="xIntercept" type="xs:float">
        <xs:annotation>
          <xs:documentation>tooltip: X Intercept summary: Location of the rasterOrigin point on the x axis of the the coordinate system. description: X Intercept of the rasterOrigin point within the coordinate system.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="xSlope" type="xs:float">
        <xs:annotation>
          <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into x coordinates. description: Slope describing transformation of grid cell distances into x coordinates.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="yIntercept" type="xs:float">
        <xs:annotation>
          <xs:documentation>tooltip: Y Intercept summary: Location of the rasterOrigin point on the y axis of the the coordinate system. description: Location of the rasterOrigin point on the y axis of the the coordinate system.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="ySlope" type="xs:float">
        <xs:annotation>
          <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into y axis coordinates. description: Slope describing transformation of grid cell distances into y axis coordinates.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / bilinearFit / xIntercept
Namespace No namespace
Annotations
tooltip: X Intercept

summary: Location of the rasterOrigin point on the x axis of the the coordinate system.
                          

description: X Intercept of the rasterOrigin point within the coordinate system.
Diagram
Diagram
Type xs:float
Properties
content simple
Source
<xs:element name="xIntercept" type="xs:float">
  <xs:annotation>
    <xs:documentation>tooltip: X Intercept summary: Location of the rasterOrigin point on the x axis of the the coordinate system. description: X Intercept of the rasterOrigin point within the coordinate system.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / bilinearFit / xSlope
Namespace No namespace
Annotations
tooltip: X slope

summary: Slope describing transformation of grid cell distances into x coordinates.
                          

description: Slope describing transformation of grid cell distances into x coordinates.
Diagram
Diagram
Type xs:float
Properties
content simple
Source
<xs:element name="xSlope" type="xs:float">
  <xs:annotation>
    <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into x coordinates. description: Slope describing transformation of grid cell distances into x coordinates.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / bilinearFit / yIntercept
Namespace No namespace
Annotations
tooltip: Y Intercept

summary: Location of the rasterOrigin point on the y axis of the the coordinate
                          system. 

description: Location of the rasterOrigin point on the y axis of the the coordinate
                           system.
Diagram
Diagram
Type xs:float
Properties
content simple
Source
<xs:element name="yIntercept" type="xs:float">
  <xs:annotation>
    <xs:documentation>tooltip: Y Intercept summary: Location of the rasterOrigin point on the y axis of the the coordinate system. description: Location of the rasterOrigin point on the y axis of the the coordinate system.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / georeferenceInfo / bilinearFit / ySlope
Namespace No namespace
Annotations
tooltip: X slope

summary: Slope describing transformation of grid cell distances into y axis
                          coordinates.  

description: Slope describing transformation of grid cell distances into y axis
                          coordinates.
Diagram
Diagram
Type xs:float
Properties
content simple
Source
<xs:element name="ySlope" type="xs:float">
  <xs:annotation>
    <xs:documentation>tooltip: X slope summary: Slope describing transformation of grid cell distances into y axis coordinates. description: Slope describing transformation of grid cell distances into y axis coordinates.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / horizontalAccuracy
Namespace No namespace
Annotations
tooltip: Horizontal Accuracy

summary: 
              The accuracy of horizontal locational measurements within the data.
              

description: Horizontal accuracy may be reported either as a quantitative estimate
              expressed in the units of the coordinate system or as a text assessment.
Diagram
Diagram NO_NAMESPACE.tmp#DataQuality_accuracyReport NO_NAMESPACE.tmp#DataQuality_quantitativeAccuracyReport spatialRaster-2_2_0.tmp#DataQuality
Type DataQuality
Properties
content complex
Model
Children accuracyReport, quantitativeAccuracyReport
Instance
<horizontalAccuracy>
  <accuracyReport>{1,1}</accuracyReport>
  <quantitativeAccuracyReport>{0,unbounded}</quantitativeAccuracyReport>
</horizontalAccuracy>
Source
<xs:element name="horizontalAccuracy" type="DataQuality">
  <xs:annotation>
    <xs:documentation>tooltip: Horizontal Accuracy summary: The accuracy of horizontal locational measurements within the data. description: Horizontal accuracy may be reported either as a quantitative estimate expressed in the units of the coordinate system or as a text assessment.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element DataQuality / accuracyReport
Namespace No namespace
Annotations
tooltip: Accuracy Report

summary: A qualitative statement about the accuracy of the data.

description: A text statement of the data quality, included the means by which it was determined.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="accuracyReport" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Accuracy Report summary: A qualitative statement about the accuracy of the data. description: A text statement of the data quality, included the means by which it was determined.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element DataQuality / quantitativeAccuracyReport
Namespace No namespace
Annotations
tooltip: Quantitative Accuracy Report

summary: A quantitative assessment of the data quality.

description: A quantitative assessment of the data quality expressed as a value and
            the method of its determination.
Diagram
Diagram NO_NAMESPACE.tmp#DataQuality_DataQuality_quantitativeAccuracyReport_quantitativeAccuracyValue NO_NAMESPACE.tmp#DataQuality_DataQuality_quantitativeAccuracyReport_quantitativeAccuracyMethod
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children quantitativeAccuracyMethod, quantitativeAccuracyValue
Instance
<quantitativeAccuracyReport>
  <quantitativeAccuracyValue>{1,1}</quantitativeAccuracyValue>
  <quantitativeAccuracyMethod>{1,1}</quantitativeAccuracyMethod>
</quantitativeAccuracyReport>
Source
<xs:element name="quantitativeAccuracyReport" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Quantitative Accuracy Report summary: A quantitative assessment of the data quality. description: A quantitative assessment of the data quality expressed as a value and the method of its determination.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element DataQuality / quantitativeAccuracyReport / quantitativeAccuracyValue
Namespace No namespace
Annotations
tooltip: Quantitative Accuracy Value

summary: The value resulting from the accuracy test.

description: The value resulting from the accuracy test. Typically, this will be expressed
                  in units corresponding to those declared for the parameter being assessed.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element DataQuality / quantitativeAccuracyReport / quantitativeAccuracyMethod
Namespace No namespace
Annotations
tooltip: Quantitative Accuracy Method

summary: The method used to calculate the accuracy value.

description: Identification and explanation of the method used to calculate the quantitative
                  accuracy assessment.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / verticalAccuracy
Namespace No namespace
Annotations
tooltip: Vertical Accuracy

summary: The accuracy of vertical locational measurements within the data.


description: Vertical accuracy may be reported either as a quantitative estimate
              expressed in the units of the height or depth measurement system or as a text
              assessment.
Diagram
Diagram NO_NAMESPACE.tmp#DataQuality_accuracyReport NO_NAMESPACE.tmp#DataQuality_quantitativeAccuracyReport spatialRaster-2_2_0.tmp#DataQuality
Type DataQuality
Properties
content complex
Model
Children accuracyReport, quantitativeAccuracyReport
Instance
<verticalAccuracy>
  <accuracyReport>{1,1}</accuracyReport>
  <quantitativeAccuracyReport>{0,unbounded}</quantitativeAccuracyReport>
</verticalAccuracy>
Source
<xs:element name="verticalAccuracy" type="DataQuality">
  <xs:annotation>
    <xs:documentation>tooltip: Vertical Accuracy summary: The accuracy of vertical locational measurements within the data. description: Vertical accuracy may be reported either as a quantitative estimate expressed in the units of the height or depth measurement system or as a text assessment.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / cellSizeXDirection
Namespace No namespace
Annotations
tooltip: Cell Size X Direction

summary: The width of the cell in the x direction.

description: Cell sizes should be expressed in the units declared in the spatialReference module.
Diagram
Diagram
Source
<xs:element name="cellSizeXDirection">
  <xs:annotation>
    <xs:documentation>tooltip: Cell Size X Direction summary: The width of the cell in the x direction. description: Cell sizes should be expressed in the units declared in the spatialReference module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / cellSizeYDirection
Namespace No namespace
Annotations
tooltip: Cell Size Y Direction

summary: The width of the cell in the x direction.

description: Cell sizes should be expressed in the units declared in the spatialReference module.
Diagram
Diagram
Source
<xs:element name="cellSizeYDirection">
  <xs:annotation>
    <xs:documentation>tooltip: Cell Size Y Direction summary: The width of the cell in the x direction. description: Cell sizes should be expressed in the units declared in the spatialReference module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / numberOfBands
Namespace No namespace
Annotations
tooltip: Number Of Bands

summary: The number of bands in the image.

description: Image data may have more than one sensor band represented for each pixel.
Diagram
Diagram
Source
<xs:element name="numberOfBands">
  <xs:annotation>
    <xs:documentation>tooltip: Number Of Bands summary: The number of bands in the image. description: Image data may have more than one sensor band represented for each pixel.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / rasterOrigin
Namespace No namespace
Annotations
tooltip: Raster Origin

summary: The corner location of the pixel having the minimum
              x and y values

description: Identification the corner of the grid where the
              first values for both the x and y axes begin in the
              file.
Diagram
Diagram spatialRaster-2_2_0.tmp#rasterOriginType
Type rasterOriginType
Properties
content simple
Facets
enumeration Upper Left
enumeration Lower Left
enumeration Upper Right
enumeration Lower Right
Source
<xs:element name="rasterOrigin" type="rasterOriginType">
  <xs:annotation>
    <xs:documentation>tooltip: Raster Origin summary: The corner location of the pixel having the minimum x and y values description: Identification the corner of the grid where the first values for both the x and y axes begin in the file.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / rows
Namespace No namespace
Annotations
tooltip: Rows

summary: Maximum number of raster objects along the ordinate
              (y) axis

description: Maximum number of raster objects along the
              ordinate (y) axis
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="rows" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Rows summary: Maximum number of raster objects along the ordinate (y) axis description: Maximum number of raster objects along the ordinate (y) axis</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / columns
Namespace No namespace
Annotations
tooltip: Columns

summary: Maximum number of raster objects along the abscissa
              (x) axis

description: Maximum number of raster objects along the
              abscissa (x) axis
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="columns" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Columns summary: Maximum number of raster objects along the abscissa (x) axis description: Maximum number of raster objects along the abscissa (x) axis</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / verticals
Namespace No namespace
Annotations
tooltip: Verticals

summary: Maximum number of raster objects along the vertical
              (z) axis

description: Maximum number of raster objects along the
              vertical (z) axis.
Diagram
Diagram
Source
<xs:element name="verticals">
  <xs:annotation>
    <xs:documentation>tooltip: Verticals summary: Maximum number of raster objects along the vertical (z) axis description: Maximum number of raster objects along the vertical (z) axis.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / cellGeometry
Namespace No namespace
Annotations
tooltip: Cell Geometry

summary: Geometric representation of the cell's content.

description: Indication of whether the cell value is representative of a single
              point(matrix) within the cell or the entire cell (pixel)
Diagram
Diagram spatialRaster-2_2_0.tmp#CellGeometryType
Type CellGeometryType
Properties
content simple
Facets
enumeration pixel
enumeration matrix
Source
<xs:element name="cellGeometry" type="CellGeometryType">
  <xs:annotation>
    <xs:documentation>tooltip: Cell Geometry summary: Geometric representation of the cell's content. description: Indication of whether the cell value is representative of a single point(matrix) within the cell or the entire cell (pixel)</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / toneGradation
Namespace No namespace
Annotations
tooltip: Tone Gradation

summary: Number of colors present in the image.
              

description: Number of colors present in the
              image.
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
<xs:element name="toneGradation" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Tone Gradation summary: Number of colors present in the image. description: Number of colors present in the image.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / scaleFactor
Namespace No namespace
Annotations
tooltip: Scale Factor

summary: The value used for scaling the source
              raster.

description: The scale factor is used for raster-rescaling
              operations, where the following operation is applied to each
              pixel in the data in the source:
              rescaled=(source*scaleFactor)+offset.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="scaleFactor" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Scale Factor summary: The value used for scaling the source raster. description: The scale factor is used for raster-rescaling operations, where the following operation is applied to each pixel in the data in the source: rescaled=(source*scaleFactor)+offset.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / offset
Namespace No namespace
Annotations
tooltip: Offset

summary: The offset value used for scaling the source
              raster.

description: The offset is used for raster-rescaling
              operations, where the following operation is applied to each
              pixel in the data in the source:
              rescaled=(source*scaleFactor)+offset.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="offset" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Offset summary: The offset value used for scaling the source raster. description: The offset is used for raster-rescaling operations, where the following operation is applied to each pixel in the data in the source: rescaled=(source*scaleFactor)+offset.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription
Namespace No namespace
Annotations
tooltip: Image Description

summary: Detailed information for data derived from image
              sensors.

description: Provides information about the image's
              suitability for use, sensor properties, and individual band
              descriptions.
Diagram
Diagram NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_illuminationElevationAngle NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_illuminationAzimuthAngle NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_imageOrientationAngle NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_imagingCondition NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_imageQualityCode NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_cloudCoverPercentage NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_preProcessingTypeCode NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_compressionGenerationQuality NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_triangulationIndicator NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_radiometricDataAvailability NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_cameraCalibrationInformationAvailability NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_filmDistortionInformationAvailability NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_lensDistortionInformationAvailability NO_NAMESPACE.tmp#SpatialRasterType_SpatialRasterType_imageDescription_bandDescription
Properties
content complex
minOccurs 0
Model
Children bandDescription, cameraCalibrationInformationAvailability, cloudCoverPercentage, compressionGenerationQuality, filmDistortionInformationAvailability, illuminationAzimuthAngle, illuminationElevationAngle, imageOrientationAngle, imageQualityCode, imagingCondition, lensDistortionInformationAvailability, preProcessingTypeCode, radiometricDataAvailability, triangulationIndicator
Instance
<imageDescription>
  <illuminationElevationAngle>{0,1}</illuminationElevationAngle>
  <illuminationAzimuthAngle>{0,1}</illuminationAzimuthAngle>
  <imageOrientationAngle>{0,1}</imageOrientationAngle>
  <imagingCondition>{0,1}</imagingCondition>
  <imageQualityCode>{0,1}</imageQualityCode>
  <cloudCoverPercentage>{0,1}</cloudCoverPercentage>
  <preProcessingTypeCode>{0,1}</preProcessingTypeCode>
  <compressionGenerationQuality>{0,1}</compressionGenerationQuality>
  <triangulationIndicator>{0,1}</triangulationIndicator>
  <radiometricDataAvailability>{0,1}</radiometricDataAvailability>
  <cameraCalibrationInformationAvailability>{0,1}</cameraCalibrationInformationAvailability>
  <filmDistortionInformationAvailability>{0,1}</filmDistortionInformationAvailability>
  <lensDistortionInformationAvailability>{0,1}</lensDistortionInformationAvailability>
  <bandDescription>{0,unbounded}</bandDescription>
</imageDescription>
Source
<xs:element name="imageDescription" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Image Description summary: Detailed information for data derived from image sensors. description: Provides information about the image's suitability for use, sensor properties, and individual band descriptions.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="illuminationElevationAngle" type="xs:float" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Illumination Elevation Angle summary: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface. description: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="illuminationAzimuthAngle" type="xs:float" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Illumination Azimuth Angle summary: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken. description: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="imageOrientationAngle" type="xs:float" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Image Orientation Angle summary: Angle from the first row of the image to true north in degrees, clockwise. description: Angle from the first row of the image to true north in degrees, clockwise.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="imagingCondition" type="ImagingConditionCode" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Imaging Condition summary: Code which indicates conditions which affect the quality of the image. description: Code which indicates conditions which affect the quality of the image.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="imageQualityCode" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Image Quality Code summary: Specifies the image quality. description: Specifies the image quality.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="cloudCoverPercentage" type="xs:float" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Cloud Cover Percentage summary: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent. description: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="preProcessingTypeCode" type="res:NonEmptyStringType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Preprocessing Type Code summary: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image. description: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="compressionGenerationQuality" type="xs:integer" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Compression Generation Quality summary: Counts the number of lossy compression cycles performed on the image. description: Counts the number of lossy compression cycles performed on the image.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="triangulationIndicator" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Triangulation Indicator summary: Code which indicates whether or not triangulation has been performed upon the image. description: Code which indicates whether or not triangulation has been performed upon the image.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="radiometricDataAvailability" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Radiometric Data Availability summary: Code which indicates whether or not Standard Radiometric Product data is available. description: Code which indicates whether or not Standard Radiometric Product data is available.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="cameraCalibrationInformationAvailability" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Camera Calibration Information Availability summary: Code which indicates whether or not constants are available which allow for camera calibration corrections. description: Code which indicates whether or not constants are available which allow for camera calibration corrections.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="filmDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Film Distortion Information Availability summary: Code which indicates whether or not Calibration Reseau information is available description: Code which indicates whether or not Calibration Reseau information is available</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="lensDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
        <xs:annotation>
          <xs:documentation>tooltip: Lens Distortion Information Availability summary: Code which indicates whether or not lens aberration correction information is available description: Code which indicates whether or not lens aberration correction information is available</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="bandDescription" type="BandType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Band Description summary: Description of the wavelength domain that the sensor operates in. description: Description of the wavelength domain that the sensor operates in</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / illuminationElevationAngle
Namespace No namespace
Annotations
tooltip: Illumination Elevation Angle

summary: Illumination elevation measured in degrees
                    clockwise from the target plane at intersection of the
                    optical line of sight with the earth's
                    surface.

description: Illumination elevation measured in degrees
                    clockwise from the target plane at intersection of the
                    optical line of sight with the earth's
                    surface.
Diagram
Diagram
Type xs:float
Properties
content simple
minOccurs 0
Source
<xs:element name="illuminationElevationAngle" type="xs:float" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Illumination Elevation Angle summary: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface. description: Illumination elevation measured in degrees clockwise from the target plane at intersection of the optical line of sight with the earth's surface.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / illuminationAzimuthAngle
Namespace No namespace
Annotations
tooltip: Illumination Azimuth Angle

summary: Illumination azimuth measured in degrees
                    clockwise from true north at the time the image is
                    taken.

description: Illumination azimuth measured in degrees
                    clockwise from true north at the time the image is
                    taken.
Diagram
Diagram
Type xs:float
Properties
content simple
minOccurs 0
Source
<xs:element name="illuminationAzimuthAngle" type="xs:float" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Illumination Azimuth Angle summary: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken. description: Illumination azimuth measured in degrees clockwise from true north at the time the image is taken.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / imageOrientationAngle
Namespace No namespace
Annotations
tooltip: Image Orientation Angle

summary: Angle from the first row of the image to true
                    north in degrees, clockwise.

description: Angle from the first row of the image to
                    true north in degrees, clockwise.
Diagram
Diagram
Type xs:float
Properties
content simple
minOccurs 0
Source
<xs:element name="imageOrientationAngle" type="xs:float" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Image Orientation Angle summary: Angle from the first row of the image to true north in degrees, clockwise. description: Angle from the first row of the image to true north in degrees, clockwise.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / imagingCondition
Namespace No namespace
Annotations
tooltip: Imaging Condition

summary: Code which indicates conditions which affect
                    the quality of the image.

description: Code which indicates conditions which
                    affect the quality of the image.
Diagram
Diagram spatialRaster-2_2_0.tmp#ImagingConditionCode
Type ImagingConditionCode
Properties
content simple
minOccurs 0
Facets
enumeration blurredimage
enumeration cloud
enumeration degradingObliquity
enumeration fog
enumeration heavySmokeorDust
enumeration night
enumeration rain
enumeration semiDarkness
enumeration shadow
enumeration snow
enumeration terrainMasking
Source
<xs:element name="imagingCondition" type="ImagingConditionCode" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Imaging Condition summary: Code which indicates conditions which affect the quality of the image. description: Code which indicates conditions which affect the quality of the image.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / imageQualityCode
Namespace No namespace
Annotations
tooltip: Image Quality Code

summary: Specifies the image quality.

description: Specifies the image
                    quality.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="imageQualityCode" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Image Quality Code summary: Specifies the image quality. description: Specifies the image quality.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / cloudCoverPercentage
Namespace No namespace
Annotations
tooltip: Cloud Cover Percentage

summary: Area of the dataset obscured by clouds,
                    expressed as a percentage of the spatial
                    extent.

description: Area of the dataset obscured by clouds,
                    expressed as a percentage of the spatial
                    extent.
Diagram
Diagram
Type xs:float
Properties
content simple
minOccurs 0
Source
<xs:element name="cloudCoverPercentage" type="xs:float" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Cloud Cover Percentage summary: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent. description: Area of the dataset obscured by clouds, expressed as a percentage of the spatial extent.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / preProcessingTypeCode
Namespace No namespace
Annotations
tooltip: Preprocessing Type Code

summary: Image distributor's code that identifies the
                    level of radiometric and geometric processing applied
                    against the image.

description: Image distributor's code that identifies
                    the level of radiometric and geometric processing applied
                    against the image.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="preProcessingTypeCode" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Preprocessing Type Code summary: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image. description: Image distributor's code that identifies the level of radiometric and geometric processing applied against the image.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / compressionGenerationQuality
Namespace No namespace
Annotations
tooltip: Compression Generation Quality

summary: Counts the number of lossy compression cycles
                    performed on the image.

description: Counts the number of lossy compression
                    cycles performed on the image.
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
<xs:element name="compressionGenerationQuality" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Compression Generation Quality summary: Counts the number of lossy compression cycles performed on the image. description: Counts the number of lossy compression cycles performed on the image.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / triangulationIndicator
Namespace No namespace
Annotations
tooltip: Triangulation Indicator

summary: Code which indicates whether or not
                    triangulation has been performed upon the
                    image.

description: Code which indicates whether or not
                    triangulation has been performed upon the
                    image.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
<xs:element name="triangulationIndicator" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Triangulation Indicator summary: Code which indicates whether or not triangulation has been performed upon the image. description: Code which indicates whether or not triangulation has been performed upon the image.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / radiometricDataAvailability
Namespace No namespace
Annotations
tooltip: Radiometric Data Availability

summary: Code which indicates whether or not Standard
                    Radiometric Product data is available.

description: Code which indicates whether or not
                    Standard Radiometric Product data is
                    available.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
<xs:element name="radiometricDataAvailability" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Radiometric Data Availability summary: Code which indicates whether or not Standard Radiometric Product data is available. description: Code which indicates whether or not Standard Radiometric Product data is available.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / cameraCalibrationInformationAvailability
Namespace No namespace
Annotations
tooltip: Camera Calibration Information
                    Availability

summary: Code which indicates whether or not constants
                    are available which allow for camera calibration
                    corrections.

description: Code which indicates whether or not
                    constants are available which allow for camera calibration
                    corrections.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
<xs:element name="cameraCalibrationInformationAvailability" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Camera Calibration Information Availability summary: Code which indicates whether or not constants are available which allow for camera calibration corrections. description: Code which indicates whether or not constants are available which allow for camera calibration corrections.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / filmDistortionInformationAvailability
Namespace No namespace
Annotations
tooltip: Film Distortion Information
                    Availability

summary: Code which indicates whether or not
                    Calibration Reseau information is available

description: Code which indicates whether or not
                    Calibration Reseau information is
                    available
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
<xs:element name="filmDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Film Distortion Information Availability summary: Code which indicates whether or not Calibration Reseau information is available description: Code which indicates whether or not Calibration Reseau information is available</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / lensDistortionInformationAvailability
Namespace No namespace
Annotations
tooltip: Lens Distortion Information
                    Availability

summary: Code which indicates whether or not lens
                    aberration correction information is
                    available

description: Code which indicates whether or not lens
                    aberration correction information is
                    available
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
<xs:element name="lensDistortionInformationAvailability" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Lens Distortion Information Availability summary: Code which indicates whether or not lens aberration correction information is available description: Code which indicates whether or not lens aberration correction information is available</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element SpatialRasterType / imageDescription / bandDescription
Namespace No namespace
Annotations
tooltip: Band Description

summary: Description of the wavelength domain that the sensor operates
                    in.

description: Description of the wavelength domain that the sensor operates
                    in
Diagram
Diagram NO_NAMESPACE.tmp#BandType_sequenceIdentifier NO_NAMESPACE.tmp#BandType_highWavelength NO_NAMESPACE.tmp#BandType_lowWaveLength NO_NAMESPACE.tmp#BandType_waveLengthUnits NO_NAMESPACE.tmp#BandType_peakResponse spatialRaster-2_2_0.tmp#BandType
Type BandType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children highWavelength, lowWaveLength, peakResponse, sequenceIdentifier, waveLengthUnits
Instance
<bandDescription>
  <sequenceIdentifier>{0,1}</sequenceIdentifier>
  <highWavelength>{0,1}</highWavelength>
  <lowWaveLength>{0,1}</lowWaveLength>
  <waveLengthUnits>{0,1}</waveLengthUnits>
  <peakResponse>{0,1}</peakResponse>
</bandDescription>
Source
<xs:element name="bandDescription" type="BandType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Band Description summary: Description of the wavelength domain that the sensor operates in. description: Description of the wavelength domain that the sensor operates in</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element BandType / sequenceIdentifier
Namespace No namespace
Annotations
tooltip: Sequence Identifier

summary: Number that uniquely identifies instances of bands of
            wavelengths on which a sensor operates.

description: Number that uniquely identifies instances of bands
            of wavelengths on which a sensor operates.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="sequenceIdentifier" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Sequence Identifier summary: Number that uniquely identifies instances of bands of wavelengths on which a sensor operates. description: Number that uniquely identifies instances of bands of wavelengths on which a sensor operates.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element BandType / highWavelength
Namespace No namespace
Annotations
tooltip: High Wavelength

summary: Highest wavelength that the sensor is capable of
            collecting within a designated band in metres.

description: Highest wavelength that the sensor is capable of
            collecting within a designated band.
Diagram
Diagram
Type xs:float
Properties
content simple
minOccurs 0
Source
<xs:element name="highWavelength" type="xs:float" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: High Wavelength summary: Highest wavelength that the sensor is capable of collecting within a designated band in metres. description: Highest wavelength that the sensor is capable of collecting within a designated band.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element BandType / lowWaveLength
Namespace No namespace
Annotations
tooltip: Low Wavelength

summary: Lowest wavelength that the sensor is capable of
            collecting within a designated band in metres.

description: Lowest wavelength that the sensor is capable of
            collecting within a designated band.
Diagram
Diagram
Type xs:float
Properties
content simple
minOccurs 0
Source
<xs:element name="lowWaveLength" type="xs:float" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Low Wavelength summary: Lowest wavelength that the sensor is capable of collecting within a designated band in metres. description: Lowest wavelength that the sensor is capable of collecting within a designated band.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element BandType / waveLengthUnits
Namespace No namespace
Annotations
tooltip: Wave Length Units

summary: Units in which the sensor wavelegths are
            expressed.

description: Units of measure for the wavelength at which the
            sensor collected the data.
Diagram
Diagram spatialReference-2_2_0.tmp#lengthUnits
Type lengthUnits
Properties
content simple
minOccurs 0
Facets
enumeration meter
enumeration nanometer
enumeration micrometer
enumeration micron
enumeration millimeter
enumeration centimeter
enumeration decimeter
enumeration dekameter
enumeration hectometer
enumeration kilometer
enumeration megameter
enumeration angstrom
enumeration inch
enumeration Foot_US
enumeration foot
enumeration Foot_Gold_Coast
enumeration fathom
enumeration nauticalMile
enumeration yard
enumeration Yard_Indian
enumeration Link_Clarke
enumeration Yard_Sears
enumeration mile
Source
<xs:element name="waveLengthUnits" type="spref:lengthUnits" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Wave Length Units summary: Units in which the sensor wavelegths are expressed. description: Units of measure for the wavelength at which the sensor collected the data.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element BandType / peakResponse
Namespace No namespace
Annotations
tooltip: Peak Response

summary: Wavelength at which the response is the highest.

description:
Diagram
Diagram
Properties
minOccurs 0
Source
<xs:element name="peakResponse" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Peak Response summary: Wavelength at which the response is the highest. description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Element DatasetType / spatialVector
Namespace No namespace
Annotations
tooltip: spatial vector

summary: The spatialVector field describes any
                spatial vectors included in this dataset.

description: The spatialVector field describes any
                spatial vectors included in this dataset.
Diagram
Diagram NO_NAMESPACE.tmp#SpatialVectorType_id NO_NAMESPACE.tmp#SpatialVectorType_system NO_NAMESPACE.tmp#SpatialVectorType_scope NO_NAMESPACE.tmp#EntityGroup_alternateIdentifier NO_NAMESPACE.tmp#EntityGroup_entityName NO_NAMESPACE.tmp#EntityGroup_entityDescription NO_NAMESPACE.tmp#EntityGroup_physical NO_NAMESPACE.tmp#EntityGroup_coverage NO_NAMESPACE.tmp#EntityGroup_methods NO_NAMESPACE.tmp#EntityGroup_additionalInfo NO_NAMESPACE.tmp#EntityGroup_annotation entity-2_2_0.tmp#EntityGroup NO_NAMESPACE.tmp#SpatialVectorType_attributeList NO_NAMESPACE.tmp#SpatialVectorType_constraint NO_NAMESPACE.tmp#SpatialVectorType_geometry NO_NAMESPACE.tmp#SpatialVectorType_geometricObjectCount NO_NAMESPACE.tmp#SpatialVectorType_topologyLevel NO_NAMESPACE.tmp#SpatialVectorType_spatialReference NO_NAMESPACE.tmp#SpatialVectorType_horizontalAccuracy NO_NAMESPACE.tmp#SpatialVectorType_verticalAccuracy NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup spatialVector-2_2_0.tmp#SpatialVectorType
Type SpatialVectorType
Properties
content complex
Model
Children additionalInfo, alternateIdentifier, annotation, attributeList, constraint, coverage, entityDescription, entityName, geometricObjectCount, geometry, horizontalAccuracy, methods, physical, references, spatialReference, topologyLevel, verticalAccuracy
Instance
<spatialVector id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <entityName>{1,1}</entityName>
  <entityDescription>{0,1}</entityDescription>
  <physical id="" scope="document" system="">{0,unbounded}</physical>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <methods>{0,1}</methods>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <annotation>{0,unbounded}</annotation>
  <attributeList id="">{1,1}</attributeList>
  <constraint id="" scope="document" system="">{0,unbounded}</constraint>
  <geometry>{1,unbounded}</geometry>
  <geometricObjectCount>{0,1}</geometricObjectCount>
  <topologyLevel>{0,1}</topologyLevel>
  <spatialReference id="" scope="document" system="">{0,1}</spatialReference>
  <horizontalAccuracy>{0,1}</horizontalAccuracy>
  <verticalAccuracy>{0,1}</verticalAccuracy>
  <references system="">{1,1}</references>
</spatialVector>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="spatialVector" type="sv:SpatialVectorType">
  <xs:annotation>
    <xs:documentation>tooltip: spatial vector summary: The spatialVector field describes any spatial vectors included in this dataset. description: The spatialVector field describes any spatial vectors included in this dataset.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element SpatialVectorType / attributeList
Namespace No namespace
Annotations
tooltip: Attribute List

summary: The list of attributes associated with this
              entity.

description: The list of attributes associated with this
              entity.  For more information see the eml-attribute
              module.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeListType_id NO_NAMESPACE.tmp#AttributeListType_attribute NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#AttributeListType
Type AttributeListType
Properties
content complex
Model
Children attribute, references
Instance
<attributeList id="">
  <attribute id="" scope="document" system="">{1,unbounded}</attribute>
  <references system="">{1,1}</references>
</attributeList>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="attributeList" type="att:AttributeListType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element SpatialVectorType / constraint
Namespace No namespace
Annotations
tooltip: Constraint

summary: Description of any relational constraints on
              this entity.

description: Description of any relational constraints on
              this entity.  For more information see the eml-constraint
              module.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_id NO_NAMESPACE.tmp#ConstraintType_system NO_NAMESPACE.tmp#ConstraintType_scope NO_NAMESPACE.tmp#ConstraintType_primaryKey NO_NAMESPACE.tmp#ConstraintType_uniqueKey NO_NAMESPACE.tmp#ConstraintType_checkConstraint NO_NAMESPACE.tmp#ConstraintType_foreignKey NO_NAMESPACE.tmp#ConstraintType_joinCondition NO_NAMESPACE.tmp#ConstraintType_notNullConstraint constraint-2_2_0.tmp#ConstraintType
Type ConstraintType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children checkConstraint, foreignKey, joinCondition, notNullConstraint, primaryKey, uniqueKey
Instance
<constraint id="" scope="document" system="">
  <primaryKey>{1,1}</primaryKey>
  <uniqueKey>{1,1}</uniqueKey>
  <checkConstraint language="">{1,1}</checkConstraint>
  <foreignKey>{1,1}</foreignKey>
  <joinCondition>{1,1}</joinCondition>
  <notNullConstraint>{1,1}</notNullConstraint>
</constraint>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Constraint summary: Description of any relational constraints on this entity. description: Description of any relational constraints on this entity. For more information see the eml-constraint module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element SpatialVectorType / geometry
Namespace No namespace
Annotations
tooltip: Geometry

summary: Type of geometric feature(s) represented in the
              entity.

description: Geometric feature classification is based on an
              enumeration of simple feature classes defined by the OpenGIS
              consortium and implemented in Geographic Markup Language as
              simple feature types.
Diagram
Diagram spatialVector-2_2_0.tmp#GeometryType
Type GeometryType
Properties
content simple
maxOccurs unbounded
Facets
enumeration Point
enumeration LineString
enumeration LinearRing
enumeration Polygon
enumeration MultiPoint
enumeration MultiLineString
enumeration MultiPolygon
enumeration MultiGeometry
Source
<xs:element name="geometry" type="GeometryType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Geometry summary: Type of geometric feature(s) represented in the entity. description: Geometric feature classification is based on an enumeration of simple feature classes defined by the OpenGIS consortium and implemented in Geographic Markup Language as simple feature types.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element SpatialVectorType / geometricObjectCount
Namespace No namespace
Annotations
tooltip: Geometric Object Count

summary: Total number of the geometric objects
              occurring in the dataset.

description: Total number of the geometric objects
              occurring in the dataset.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="geometricObjectCount" type="res:NonEmptyStringType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Geometric Object Count summary: Total number of the geometric objects occurring in the dataset. description: Total number of the geometric objects occurring in the dataset.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element SpatialVectorType / topologyLevel
Namespace No namespace
Annotations
tooltip: Topology Level

summary: Code which identifies the degree of
              complexity.

description: This element describes the relative complexity
              of the geometric information in the data file.
Diagram
Diagram spatialVector-2_2_0.tmp#TopologyLevel
Type TopologyLevel
Properties
content simple
minOccurs 0
Facets
enumeration geometryOnly
enumeration nonPlanarGraph
enumeration planarLineGraph
enumeration fullPlanarGraph
enumeration surfaceGraph
enumeration fullTopology3D
Source
<xs:element name="topologyLevel" type="TopologyLevel" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Topology Level summary: Code which identifies the degree of complexity. description: This element describes the relative complexity of the geometric information in the data file.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element SpatialVectorType / spatialReference
Namespace No namespace
Annotations
tooltip: Spatial Reference

summary: 

description:
Diagram
Diagram NO_NAMESPACE.tmp#SpatialReferenceType_id NO_NAMESPACE.tmp#SpatialReferenceType_system NO_NAMESPACE.tmp#SpatialReferenceType_scope NO_NAMESPACE.tmp#SpatialReferenceType_horizCoordSysName NO_NAMESPACE.tmp#SpatialReferenceType_horizCoordSysDef NO_NAMESPACE.tmp#SpatialReferenceType_vertCoordSys NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup spatialReference-2_2_0.tmp#SpatialReferenceType
Type SpatialReferenceType
Properties
content complex
minOccurs 0
Model
Children horizCoordSysDef, horizCoordSysName, references, vertCoordSys
Instance
<spatialReference id="" scope="document" system="">
  <horizCoordSysName>{1,1}</horizCoordSysName>
  <horizCoordSysDef name="">{1,1}</horizCoordSysDef>
  <vertCoordSys>{0,1}</vertCoordSys>
  <references system="">{1,1}</references>
</spatialReference>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="spatialReference" type="spref:SpatialReferenceType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Spatial Reference summary: description:</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element SpatialVectorType / horizontalAccuracy
Namespace No namespace
Annotations
tooltip: Horizontal Accuracy

summary: Horizontal positional accuracy of the data

description: Horizontal positional accuracy of the data
              expressed as either text or quantitative assessment.
Diagram
Diagram NO_NAMESPACE.tmp#eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality_accuracyReport NO_NAMESPACE.tmp#eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality_quantitativeAccuracyReport spatialVector-2_2_0.tmp#eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality
Type DataQuality
Properties
content complex
minOccurs 0
Model
Children accuracyReport, quantitativeAccuracyReport
Instance
<horizontalAccuracy>
  <accuracyReport>{1,1}</accuracyReport>
  <quantitativeAccuracyReport>{0,unbounded}</quantitativeAccuracyReport>
</horizontalAccuracy>
Source
<xs:element name="horizontalAccuracy" type="DataQuality" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Horizontal Accuracy summary: Horizontal positional accuracy of the data description: Horizontal positional accuracy of the data expressed as either text or quantitative assessment.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element DataQuality / accuracyReport
Namespace No namespace
Annotations
tooltip: Accuracy Report

summary: A qualitative statement about the accuracy of the data.

description: A text statement of the data quality, included the means by which it was determined.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="accuracyReport" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Accuracy Report summary: A qualitative statement about the accuracy of the data. description: A text statement of the data quality, included the means by which it was determined.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element DataQuality / quantitativeAccuracyReport
Namespace No namespace
Annotations
tooltip: Quantitative Accuracy Report

summary: A quantitative assessment of the data quality.

description: A quantitative assessment of the data quality expressed as a value and
            the method of its determination.
Diagram
Diagram NO_NAMESPACE.tmp#eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality_eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality_quantitativeAccuracyReport_quantitativeAccuracyValue NO_NAMESPACE.tmp#eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality_eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality_quantitativeAccuracyReport_quantitativeAccuracyMethod
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children quantitativeAccuracyMethod, quantitativeAccuracyValue
Instance
<quantitativeAccuracyReport>
  <quantitativeAccuracyValue>{1,1}</quantitativeAccuracyValue>
  <quantitativeAccuracyMethod>{1,1}</quantitativeAccuracyMethod>
</quantitativeAccuracyReport>
Source
<xs:element name="quantitativeAccuracyReport" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Quantitative Accuracy Report summary: A quantitative assessment of the data quality. description: A quantitative assessment of the data quality expressed as a value and the method of its determination.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
        <xs:annotation>
          <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element DataQuality / quantitativeAccuracyReport / quantitativeAccuracyValue
Namespace No namespace
Annotations
tooltip: Quantitative Accuracy Value

summary: The value resulting from the accuracy test.

description: The value resulting from the accuracy test. Typically, this will be expressed
                  in units corresponding to those declared for the parameter being assessed.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="quantitativeAccuracyValue" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Quantitative Accuracy Value summary: The value resulting from the accuracy test. description: The value resulting from the accuracy test. Typically, this will be expressed in units corresponding to those declared for the parameter being assessed.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element DataQuality / quantitativeAccuracyReport / quantitativeAccuracyMethod
Namespace No namespace
Annotations
tooltip: Quantitative Accuracy Method

summary: The method used to calculate the accuracy value.

description: Identification and explanation of the method used to calculate the quantitative
                  accuracy assessment.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="quantitativeAccuracyMethod" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Quantitative Accuracy Method summary: The method used to calculate the accuracy value. description: Identification and explanation of the method used to calculate the quantitative accuracy assessment.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element SpatialVectorType / verticalAccuracy
Namespace No namespace
Annotations
tooltip: Vertical Accuracy

summary: Vertical positional accuracy of the data

description: Vertical positional accuracy of the data
              expressed as either text or quantitative assessment.
Diagram
Diagram NO_NAMESPACE.tmp#eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality_accuracyReport NO_NAMESPACE.tmp#eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality_quantitativeAccuracyReport spatialVector-2_2_0.tmp#eml___ecoinformatics.org_spatialVector-2.2.0_DataQuality
Type DataQuality
Properties
content complex
minOccurs 0
Model
Children accuracyReport, quantitativeAccuracyReport
Instance
<verticalAccuracy>
  <accuracyReport>{1,1}</accuracyReport>
  <quantitativeAccuracyReport>{0,unbounded}</quantitativeAccuracyReport>
</verticalAccuracy>
Source
<xs:element name="verticalAccuracy" type="DataQuality" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Vertical Accuracy summary: Vertical positional accuracy of the data description: Vertical positional accuracy of the data expressed as either text or quantitative assessment.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Element DatasetType / storedProcedure
Namespace No namespace
Annotations
tooltip: stored procedure

summary: The storedProcedure field contains information
                about any stored procedures included with this
                dataset.

description: The storedProcedure field contains information
                about any stored procedures included with this dataset.
                This usually implies that the dataset is stored in a DBMS or
                some other data management system capable of processing your
                dataset.
Diagram
Diagram NO_NAMESPACE.tmp#StoredProcedureType_id NO_NAMESPACE.tmp#StoredProcedureType_system NO_NAMESPACE.tmp#StoredProcedureType_scope NO_NAMESPACE.tmp#EntityGroup_alternateIdentifier NO_NAMESPACE.tmp#EntityGroup_entityName NO_NAMESPACE.tmp#EntityGroup_entityDescription NO_NAMESPACE.tmp#EntityGroup_physical NO_NAMESPACE.tmp#EntityGroup_coverage NO_NAMESPACE.tmp#EntityGroup_methods NO_NAMESPACE.tmp#EntityGroup_additionalInfo NO_NAMESPACE.tmp#EntityGroup_annotation entity-2_2_0.tmp#EntityGroup NO_NAMESPACE.tmp#StoredProcedureType_attributeList NO_NAMESPACE.tmp#StoredProcedureType_constraint NO_NAMESPACE.tmp#StoredProcedureType_parameter NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup storedProcedure-2_2_0.tmp#StoredProcedureType
Type StoredProcedureType
Properties
content complex
Model
Children additionalInfo, alternateIdentifier, annotation, attributeList, constraint, coverage, entityDescription, entityName, methods, parameter, physical, references
Instance
<storedProcedure id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <entityName>{1,1}</entityName>
  <entityDescription>{0,1}</entityDescription>
  <physical id="" scope="document" system="">{0,unbounded}</physical>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <methods>{0,1}</methods>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <annotation>{0,unbounded}</annotation>
  <attributeList id="">{1,1}</attributeList>
  <constraint id="" scope="document" system="">{0,unbounded}</constraint>
  <parameter>{0,unbounded}</parameter>
  <references system="">{1,1}</references>
</storedProcedure>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="storedProcedure" type="sp:StoredProcedureType">
  <xs:annotation>
    <xs:documentation>tooltip: stored procedure summary: The storedProcedure field contains information about any stored procedures included with this dataset. description: The storedProcedure field contains information about any stored procedures included with this dataset. This usually implies that the dataset is stored in a DBMS or some other data management system capable of processing your dataset.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element StoredProcedureType / attributeList
Namespace No namespace
Annotations
tooltip: Attribute List

summary: The list of attributes associated with this
              entity.

description: The list of attributes associated with this
              entity.  For more information see the eml-attribute
              module.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeListType_id NO_NAMESPACE.tmp#AttributeListType_attribute NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#AttributeListType
Type AttributeListType
Properties
content complex
Model
Children attribute, references
Instance
<attributeList id="">
  <attribute id="" scope="document" system="">{1,unbounded}</attribute>
  <references system="">{1,1}</references>
</attributeList>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="attributeList" type="att:AttributeListType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Element StoredProcedureType / constraint
Namespace No namespace
Annotations
tooltip: Constraint

summary: 

description: Description of any relational constraints on '
              this entity.  For more information see the eml-constraint
              module.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_id NO_NAMESPACE.tmp#ConstraintType_system NO_NAMESPACE.tmp#ConstraintType_scope NO_NAMESPACE.tmp#ConstraintType_primaryKey NO_NAMESPACE.tmp#ConstraintType_uniqueKey NO_NAMESPACE.tmp#ConstraintType_checkConstraint NO_NAMESPACE.tmp#ConstraintType_foreignKey NO_NAMESPACE.tmp#ConstraintType_joinCondition NO_NAMESPACE.tmp#ConstraintType_notNullConstraint constraint-2_2_0.tmp#ConstraintType
Type ConstraintType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children checkConstraint, foreignKey, joinCondition, notNullConstraint, primaryKey, uniqueKey
Instance
<constraint id="" scope="document" system="">
  <primaryKey>{1,1}</primaryKey>
  <uniqueKey>{1,1}</uniqueKey>
  <checkConstraint language="">{1,1}</checkConstraint>
  <foreignKey>{1,1}</foreignKey>
  <joinCondition>{1,1}</joinCondition>
  <notNullConstraint>{1,1}</notNullConstraint>
</constraint>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Element StoredProcedureType / parameter
Namespace No namespace
Annotations
tooltip: Parameter

summary: A parameter that is required as input to the
              stored procedure.

description: The parameter elements defines the fields that
              may be required to invoke a stored procedure.
Diagram
Diagram NO_NAMESPACE.tmp#ParameterType_name NO_NAMESPACE.tmp#ParameterType_domainDescription NO_NAMESPACE.tmp#ParameterType_required NO_NAMESPACE.tmp#ParameterType_repeats storedProcedure-2_2_0.tmp#ParameterType
Type ParameterType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children domainDescription, name, repeats, required
Instance
<parameter>
  <name>{1,1}</name>
  <domainDescription>{1,1}</domainDescription>
  <required>{1,1}</required>
  <repeats>{1,1}</repeats>
</parameter>
Source
<xs:element name="parameter" type="ParameterType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter summary: A parameter that is required as input to the stored procedure. description: The parameter elements defines the fields that may be required to invoke a stored procedure.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Element ParameterType / name
Namespace No namespace
Annotations
tooltip: Parameter Name

summary: The name of the parameter.

description: The value of the name field is the name of the
            parameter.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="name" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: The value of the name field is the name of the parameter.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Element ParameterType / domainDescription
Namespace No namespace
Annotations
tooltip: Domain Description

summary: A description of domain of valid values for the
            parameter.

description: The domainDescription field is used to describe
            the valid entries for the parameter being described. A stored
            procedure will work only when the parameter's value corresponds to
            an actual value in a database.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="domainDescription" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Domain Description summary: A description of domain of valid values for the parameter. description: The domainDescription field is used to describe the valid entries for the parameter being described. A stored procedure will work only when the parameter's value corresponds to an actual value in a database.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Element ParameterType / required
Namespace No namespace
Annotations
tooltip: Required

summary: Whether or not the parameter is
            required.

description: The required field is used to document whether the
            parameter being described is or is not required when invoking the
            stored procedure.
Diagram
Diagram
Type xs:boolean
Properties
content simple
Source
<xs:element name="required" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>tooltip: Required summary: Whether or not the parameter is required. description: The required field is used to document whether the parameter being described is or is not required when invoking the stored procedure.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Element ParameterType / repeats
Namespace No namespace
Annotations
tooltip: Repeats

summary: Whether or not the parameter repeats.

description: The repeats field is used to document whether or
            not the parameter being described can be repeated when invoking the
            stored procedure.
Diagram
Diagram
Type xs:boolean
Properties
content simple
Source
<xs:element name="repeats" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>tooltip: Repeats summary: Whether or not the parameter repeats. description: The repeats field is used to document whether or not the parameter being described can be repeated when invoking the stored procedure.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Element DatasetType / view
Namespace No namespace
Annotations
tooltip: view

summary: The view field contains information
                about any views included with this
                dataset.

description: The view field contains information
                about any view included with this dataset.
                This usually implies that the dataset is stored in a DBMS or
                some other data management system capable of processing your
                dataset.
Diagram
Diagram NO_NAMESPACE.tmp#ViewType_id NO_NAMESPACE.tmp#ViewType_system NO_NAMESPACE.tmp#ViewType_scope NO_NAMESPACE.tmp#EntityGroup_alternateIdentifier NO_NAMESPACE.tmp#EntityGroup_entityName NO_NAMESPACE.tmp#EntityGroup_entityDescription NO_NAMESPACE.tmp#EntityGroup_physical NO_NAMESPACE.tmp#EntityGroup_coverage NO_NAMESPACE.tmp#EntityGroup_methods NO_NAMESPACE.tmp#EntityGroup_additionalInfo NO_NAMESPACE.tmp#EntityGroup_annotation entity-2_2_0.tmp#EntityGroup NO_NAMESPACE.tmp#ViewType_attributeList NO_NAMESPACE.tmp#ViewType_constraint NO_NAMESPACE.tmp#ViewType_queryStatement NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup view-2_2_0.tmp#ViewType
Type ViewType
Properties
content complex
Model
Children additionalInfo, alternateIdentifier, annotation, attributeList, constraint, coverage, entityDescription, entityName, methods, physical, queryStatement, references
Instance
<view id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <entityName>{1,1}</entityName>
  <entityDescription>{0,1}</entityDescription>
  <physical id="" scope="document" system="">{0,unbounded}</physical>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <methods>{0,1}</methods>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <annotation>{0,unbounded}</annotation>
  <attributeList id="">{1,1}</attributeList>
  <constraint id="" scope="document" system="">{0,unbounded}</constraint>
  <queryStatement>{1,1}</queryStatement>
  <references system="">{1,1}</references>
</view>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="view" type="v:ViewType">
  <xs:annotation>
    <xs:documentation>tooltip: view summary: The view field contains information about any views included with this dataset. description: The view field contains information about any view included with this dataset. This usually implies that the dataset is stored in a DBMS or some other data management system capable of processing your dataset.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element ViewType / attributeList
Namespace No namespace
Annotations
tooltip: Attribute List

summary: The list of attributes associated with this
              entity.

description: The list of attributes associated with this
              entity.  For more information see the eml-attribute
              module.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeListType_id NO_NAMESPACE.tmp#AttributeListType_attribute NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#AttributeListType
Type AttributeListType
Properties
content complex
Model
Children attribute, references
Instance
<attributeList id="">
  <attribute id="" scope="document" system="">{1,unbounded}</attribute>
  <references system="">{1,1}</references>
</attributeList>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="attributeList" type="att:AttributeListType">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-view.xsd
Element ViewType / constraint
Namespace No namespace
Annotations
tooltip: Constraint

summary: 

description: Description of any relational constraints on '
              this entity.  For more information see the eml-constraint
              module.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_id NO_NAMESPACE.tmp#ConstraintType_system NO_NAMESPACE.tmp#ConstraintType_scope NO_NAMESPACE.tmp#ConstraintType_primaryKey NO_NAMESPACE.tmp#ConstraintType_uniqueKey NO_NAMESPACE.tmp#ConstraintType_checkConstraint NO_NAMESPACE.tmp#ConstraintType_foreignKey NO_NAMESPACE.tmp#ConstraintType_joinCondition NO_NAMESPACE.tmp#ConstraintType_notNullConstraint constraint-2_2_0.tmp#ConstraintType
Type ConstraintType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children checkConstraint, foreignKey, joinCondition, notNullConstraint, primaryKey, uniqueKey
Instance
<constraint id="" scope="document" system="">
  <primaryKey>{1,1}</primaryKey>
  <uniqueKey>{1,1}</uniqueKey>
  <checkConstraint language="">{1,1}</checkConstraint>
  <foreignKey>{1,1}</foreignKey>
  <joinCondition>{1,1}</joinCondition>
  <notNullConstraint>{1,1}</notNullConstraint>
</constraint>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-view.xsd
Element ViewType / queryStatement
Namespace No namespace
Annotations
tooltip: Query Statement

summary: Query syntax that produced the view

description: The value of a queryStatement field is the
              actual query statement stored in the database is entered here.
              The query statement generates the entity being
              documented.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="queryStatement" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Query Statement summary: Query syntax that produced the view description: The value of a queryStatement field is the actual query statement stored in the database is entered here. The query statement generates the entity being documented.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-view.xsd
Element DatasetType / otherEntity
Namespace No namespace
Annotations
tooltip: other entity

summary: The otherEntity field contains information
                about any entity in the dataset that is not any of the
                preceding entities.

description: The otherEntity field contains information
                about any entity in the dataset that is not any of the
                preceding entities.  (i.e. it is not a table, spatialRaster,
                spatialVector, storedProcedure or view.)  OtherEntity allows
                the documentation of basic entity fields as well as
                a plain text field to allow you to type your
                entity.
Diagram
Diagram NO_NAMESPACE.tmp#OtherEntityType_id NO_NAMESPACE.tmp#OtherEntityType_system NO_NAMESPACE.tmp#OtherEntityType_scope NO_NAMESPACE.tmp#EntityGroup_alternateIdentifier NO_NAMESPACE.tmp#EntityGroup_entityName NO_NAMESPACE.tmp#EntityGroup_entityDescription NO_NAMESPACE.tmp#EntityGroup_physical NO_NAMESPACE.tmp#EntityGroup_coverage NO_NAMESPACE.tmp#EntityGroup_methods NO_NAMESPACE.tmp#EntityGroup_additionalInfo NO_NAMESPACE.tmp#EntityGroup_annotation entity-2_2_0.tmp#EntityGroup NO_NAMESPACE.tmp#OtherEntityType_attributeList NO_NAMESPACE.tmp#OtherEntityType_constraint NO_NAMESPACE.tmp#OtherEntityType_entityType NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup entity-2_2_0.tmp#OtherEntityType
Type OtherEntityType
Properties
content complex
Model
Children additionalInfo, alternateIdentifier, annotation, attributeList, constraint, coverage, entityDescription, entityName, entityType, methods, physical, references
Instance
<otherEntity id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <entityName>{1,1}</entityName>
  <entityDescription>{0,1}</entityDescription>
  <physical id="" scope="document" system="">{0,unbounded}</physical>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <methods>{0,1}</methods>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <annotation>{0,unbounded}</annotation>
  <attributeList id="">{0,1}</attributeList>
  <constraint id="" scope="document" system="">{0,unbounded}</constraint>
  <entityType>{1,1}</entityType>
  <references system="">{1,1}</references>
</otherEntity>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="otherEntity" type="ent:OtherEntityType">
  <xs:annotation>
    <xs:documentation>tooltip: other entity summary: The otherEntity field contains information about any entity in the dataset that is not any of the preceding entities. description: The otherEntity field contains information about any entity in the dataset that is not any of the preceding entities. (i.e. it is not a table, spatialRaster, spatialVector, storedProcedure or view.) OtherEntity allows the documentation of basic entity fields as well as a plain text field to allow you to type your entity.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element OtherEntityType / attributeList
Namespace No namespace
Annotations
tooltip: Attribute List

summary: The list of attributes associated with this
                entity.

description: The list of attributes associated with this
                entity.  For more information see the eml-attribute
                module.
Diagram
Diagram NO_NAMESPACE.tmp#AttributeListType_id NO_NAMESPACE.tmp#AttributeListType_attribute NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup attribute-2_2_0.tmp#AttributeListType
Type AttributeListType
Properties
content complex
minOccurs 0
Model
Children attribute, references
Instance
<attributeList id="">
  <attribute id="" scope="document" system="">{1,unbounded}</attribute>
  <references system="">{1,1}</references>
</attributeList>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="attributeList" type="att:AttributeListType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>tooltip: Attribute List summary: The list of attributes associated with this entity. description: The list of attributes associated with this entity. For more information see the eml-attribute module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element OtherEntityType / constraint
Namespace No namespace
Annotations
tooltip: Constraint

summary: 

description: Description of any relational constraints on '
                this entity.  For more information see the eml-constraint
                module.
Diagram
Diagram NO_NAMESPACE.tmp#ConstraintType_id NO_NAMESPACE.tmp#ConstraintType_system NO_NAMESPACE.tmp#ConstraintType_scope NO_NAMESPACE.tmp#ConstraintType_primaryKey NO_NAMESPACE.tmp#ConstraintType_uniqueKey NO_NAMESPACE.tmp#ConstraintType_checkConstraint NO_NAMESPACE.tmp#ConstraintType_foreignKey NO_NAMESPACE.tmp#ConstraintType_joinCondition NO_NAMESPACE.tmp#ConstraintType_notNullConstraint constraint-2_2_0.tmp#ConstraintType
Type ConstraintType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children checkConstraint, foreignKey, joinCondition, notNullConstraint, primaryKey, uniqueKey
Instance
<constraint id="" scope="document" system="">
  <primaryKey>{1,1}</primaryKey>
  <uniqueKey>{1,1}</uniqueKey>
  <checkConstraint language="">{1,1}</checkConstraint>
  <foreignKey>{1,1}</foreignKey>
  <joinCondition>{1,1}</joinCondition>
  <notNullConstraint>{1,1}</notNullConstraint>
</constraint>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="constraint" type="con:ConstraintType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Constraint summary: description: Description of any relational constraints on ' this entity. For more information see the eml-constraint module.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element OtherEntityType / entityType
Namespace No namespace
Annotations
tooltip: Entity type

summary: Contains the name of the type for this
                entity.

description: The entityType field contains the name of the
                entity's type. The entity's type is typically the name of the
                type of data represented in the entity, such as "photograph".
                This field is used only if this is an 'other' entity and you
                want to specify the kind of "other" entity this
                is.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="entityType" type="res:NonEmptyStringType">
  <xs:annotation>
    <xs:documentation>tooltip: Entity type summary: Contains the name of the type for this entity. description: The entityType field contains the name of the entity's type. The entity's type is typically the name of the type of data represented in the entity, such as "photograph". This field is used only if this is an 'other' entity and you want to specify the kind of "other" entity this is.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Element DatasetType / referencePublication
Namespace No namespace
Annotations
tooltip: Reference Publication

summary: A citation to an additional publication that serves as an important reference for a dataset.

description: A citation to an additional publication that serves as an important reference for a dataset. People using this dataset should generally cite the dataset itself (using the creator, pubDate, title, publisher, and packageId fields), and consider providing an additional citation to the Reference Publication. Common cases where a Reference Publication may be useful include when a data paper is published that describes the dataset, or when a paper is intended to be the canonical or examplar reference to the dataset.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<referencePublication id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</referencePublication>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="referencePublication" type="cit:CitationType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>tooltip: Reference Publication summary: A citation to an additional publication that serves as an important reference for a dataset. description: A citation to an additional publication that serves as an important reference for a dataset. People using this dataset should generally cite the dataset itself (using the creator, pubDate, title, publisher, and packageId fields), and consider providing an additional citation to the Reference Publication. Common cases where a Reference Publication may be useful include when a data paper is published that describes the dataset, or when a paper is intended to be the canonical or examplar reference to the dataset.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / usageCitation
Namespace No namespace
Annotations
tooltip: Usage Citation

summary: A citation to articles or products in which the
              dataset is used or referenced.

description: A citation to articles or products in which the
              dataset is used or referenced. The citation element contains
              general information about a literature resource that has used or
              references this dataset resource. It is not expected that the list of
              usageCitations will necessarily be complete, but rather they serve as
              examples and pointers to scholarly works in which this dataset has been
              used.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<usageCitation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</usageCitation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="usageCitation" type="cit:CitationType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Usage Citation summary: A citation to articles or products in which the dataset is used or referenced. description: A citation to articles or products in which the dataset is used or referenced. The citation element contains general information about a literature resource that has used or references this dataset resource. It is not expected that the list of usageCitations will necessarily be complete, but rather they serve as examples and pointers to scholarly works in which this dataset has been used.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element DatasetType / literatureCited
Namespace No namespace
Annotations
tooltip: Literature Cited

summary: A citation to articles or products which were referenced
              in the dataset or its associated metadata.

description: A citation to articles or products which were referenced
              in the dataset or its associated metadata. The list represents the bibliography
              of works related to the dataset, whether for reference, comparison, or others
              purposes.
Diagram
Diagram NO_NAMESPACE.tmp#CitationListType_citation NO_NAMESPACE.tmp#CitationListType_bibtex literature-2_2_0.tmp#CitationListType
Type CitationListType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children bibtex, citation
Instance
<literatureCited>
  <citation id="" scope="document" system="">{1,1}</citation>
  <bibtex>{1,1}</bibtex>
</literatureCited>
Source
<xs:element name="literatureCited" type="cit:CitationListType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Literature Cited summary: A citation to articles or products which were referenced in the dataset or its associated metadata. description: A citation to articles or products which were referenced in the dataset or its associated metadata. The list represents the bibliography of works related to the dataset, whether for reference, comparison, or others purposes.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Element CitationListType / citation
Namespace No namespace
Annotations
tooltip: citation

summary: A citation within a list of citations.

description: A citation within a list of citations, usually used for a literatureCited
                            cited list or similar. Each citation is formatted following the EML CitationType
                            structure.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<citation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</citation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="citation" type="CitationType">
  <xs:annotation>
    <xs:documentation>tooltip: citation summary: A citation within a list of citations. description: A citation within a list of citations, usually used for a literatureCited cited list or similar. Each citation is formatted following the EML CitationType structure.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element CitationListType / bibtex
Namespace No namespace
Annotations
tooltip: Bibtex Citation List

summary: List of citations in Bibtex format.

description: The bibtex field provides a parseable list of citations formatted according to the Bibtex formatting conventions. Each citation entry is assigned a unique key that must be unique across all bibtex fields in the EML document. The citation key can be used in markdown sections of the text to refer to this citation using the pandoc-style of inline citation keys.  See the markdown element for more details. The record is delimited using curly braces. Most reference software can both import and export citations in Bibtex format, so this is a simpler representation to produce and consume than native EML citation representations.
Diagram
Diagram
Type xs:string
Properties
content simple
Source
<xs:element name="bibtex" type="xs:string">
  <xs:annotation>
    <xs:documentation>tooltip: Bibtex Citation List summary: List of citations in Bibtex format. description: The bibtex field provides a parseable list of citations formatted according to the Bibtex formatting conventions. Each citation entry is assigned a unique key that must be unique across all bibtex fields in the EML document. The citation key can be used in markdown sections of the text to refer to this citation using the pandoc-style of inline citation keys. See the markdown element for more details. The record is delimited using curly braces. Most reference software can both import and export citations in Bibtex format, so this is a simpler representation to produce and consume than native EML citation representations.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Element eml / citation
Namespace No namespace
Annotations
tooltip: Literature Resource

summary: A resource that describes a literature citation that one might find in
                  a bibliography. 

description: A resource that describes a literature citation that one might find
                  in a bibliography. If included, this represents the primary resource that is
                  described in this eml document.
Diagram
Diagram NO_NAMESPACE.tmp#CitationType_id NO_NAMESPACE.tmp#CitationType_system NO_NAMESPACE.tmp#CitationType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#CitationType_contact NO_NAMESPACE.tmp#CitationType_article NO_NAMESPACE.tmp#CitationType_book NO_NAMESPACE.tmp#CitationType_chapter NO_NAMESPACE.tmp#CitationType_editedBook NO_NAMESPACE.tmp#CitationType_manuscript NO_NAMESPACE.tmp#CitationType_report NO_NAMESPACE.tmp#CitationType_thesis NO_NAMESPACE.tmp#CitationType_conferenceProceedings NO_NAMESPACE.tmp#CitationType_personalCommunication NO_NAMESPACE.tmp#CitationType_map NO_NAMESPACE.tmp#CitationType_generic NO_NAMESPACE.tmp#CitationType_audioVisual NO_NAMESPACE.tmp#CitationType_presentation NO_NAMESPACE.tmp#CitationType_bibtex NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup literature-2_2_0.tmp#CitationType
Type CitationType
Properties
content complex
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, article, associatedParty, audioVisual, bibtex, book, chapter, conferenceProceedings, contact, coverage, creator, distribution, editedBook, generic, intellectualRights, keywordSet, language, licensed, manuscript, map, metadataProvider, personalCommunication, presentation, pubDate, references, report, series, shortName, thesis, title
Instance
<citation id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <contact id="" scope="document" system="">{0,unbounded}</contact>
  <article>{1,1}</article>
  <book>{1,1}</book>
  <chapter>{1,1}</chapter>
  <editedBook>{1,1}</editedBook>
  <manuscript>{1,1}</manuscript>
  <report>{1,1}</report>
  <thesis>{1,1}</thesis>
  <conferenceProceedings>{1,1}</conferenceProceedings>
  <personalCommunication>{1,1}</personalCommunication>
  <map>{1,1}</map>
  <generic>{1,1}</generic>
  <audioVisual>{1,1}</audioVisual>
  <presentation>{1,1}</presentation>
  <bibtex>{1,1}</bibtex>
  <references system="">{1,1}</references>
</citation>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="citation" type="cit:CitationType">
  <xs:annotation>
    <xs:documentation>tooltip: Literature Resource summary: A resource that describes a literature citation that one might find in a bibliography. description: A resource that describes a literature citation that one might find in a bibliography. If included, this represents the primary resource that is described in this eml document.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element eml / software
Namespace No namespace
Annotations
tooltip: Software Resource

summary: A resource that describes a software package, which can include
                  commercial and non-commercial software as well as data processing programs. 

description: A resource that describes a software package, which can include
                  commercial and non-commercial software as well as data processing programs. If
                  included, this represents the primary resource that is described in this eml
                  document.
Diagram
Diagram NO_NAMESPACE.tmp#SoftwareType_id NO_NAMESPACE.tmp#SoftwareType_system NO_NAMESPACE.tmp#SoftwareType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#SoftwareType_implementation NO_NAMESPACE.tmp#SoftwareType_dependency NO_NAMESPACE.tmp#SoftwareType_licenseURL NO_NAMESPACE.tmp#SoftwareType_license NO_NAMESPACE.tmp#SoftwareType_version NO_NAMESPACE.tmp#SoftwareType_project NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup software-2_2_0.tmp#SoftwareType
Type SoftwareType
Properties
content complex
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, associatedParty, coverage, creator, dependency, distribution, implementation, intellectualRights, keywordSet, language, license, licenseURL, licensed, metadataProvider, project, pubDate, references, series, shortName, title, version
Instance
<software id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <implementation>{1,unbounded}</implementation>
  <dependency>{0,unbounded}</dependency>
  <licenseURL>{1,1}</licenseURL>
  <license>{1,1}</license>
  <version>{1,1}</version>
  <project id="" scope="document" system="">{0,1}</project>
  <references system="">{1,1}</references>
</software>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="software" type="sw:SoftwareType">
  <xs:annotation>
    <xs:documentation>tooltip: Software Resource summary: A resource that describes a software package, which can include commercial and non-commercial software as well as data processing programs. description: A resource that describes a software package, which can include commercial and non-commercial software as well as data processing programs. If included, this represents the primary resource that is described in this eml document.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element eml / protocol
Namespace No namespace
Annotations
tooltip: Protocol Resource

summary: A resource that describes a scientific protocol, which can include one
                  or more descriptions of methods and procedures. 

description: A resource that describes a scientific protocol, which can include
                  one or more descriptions of methods and procedures. If included, this represents
                  the primary resource that is described in this eml document.
Diagram
Diagram NO_NAMESPACE.tmp#ProtocolType_id NO_NAMESPACE.tmp#ProtocolType_system NO_NAMESPACE.tmp#ProtocolType_scope NO_NAMESPACE.tmp#ResourceGroup_alternateIdentifier NO_NAMESPACE.tmp#ResourceGroup_shortName NO_NAMESPACE.tmp#ResourceGroup_title NO_NAMESPACE.tmp#ResourceGroup_creator NO_NAMESPACE.tmp#ResourceGroup_metadataProvider NO_NAMESPACE.tmp#ResourceGroup_associatedParty NO_NAMESPACE.tmp#ResourceGroup_pubDate NO_NAMESPACE.tmp#ResourceGroup_language NO_NAMESPACE.tmp#ResourceGroup_series NO_NAMESPACE.tmp#ResourceGroup_abstract NO_NAMESPACE.tmp#ResourceGroup_keywordSet NO_NAMESPACE.tmp#ResourceGroup_additionalInfo NO_NAMESPACE.tmp#ResourceGroup_intellectualRights NO_NAMESPACE.tmp#ResourceGroup_licensed NO_NAMESPACE.tmp#ResourceGroup_distribution NO_NAMESPACE.tmp#ResourceGroup_coverage NO_NAMESPACE.tmp#ResourceGroup_annotation resource-2_2_0.tmp#ResourceGroup NO_NAMESPACE.tmp#ProtocolType_proceduralStep NO_NAMESPACE.tmp#ReferencesGroup_references resource-2_2_0.tmp#ReferencesGroup protocol-2_2_0.tmp#ProtocolType
Type ProtocolType
Properties
content complex
Model
Children abstract, additionalInfo, alternateIdentifier, annotation, associatedParty, coverage, creator, distribution, intellectualRights, keywordSet, language, licensed, metadataProvider, proceduralStep, pubDate, references, series, shortName, title
Instance
<protocol id="" scope="document" system="">
  <alternateIdentifier system="">{0,unbounded}</alternateIdentifier>
  <shortName>{0,1}</shortName>
  <title xml:lang="">{1,unbounded}</title>
  <creator id="" scope="document" system="">{1,unbounded}</creator>
  <metadataProvider id="" scope="document" system="">{0,unbounded}</metadataProvider>
  <associatedParty id="" scope="document" system="">{0,unbounded}</associatedParty>
  <pubDate>{0,1}</pubDate>
  <language xml:lang="">{0,1}</language>
  <series>{0,1}</series>
  <abstract xml:lang="">{0,1}</abstract>
  <keywordSet>{0,unbounded}</keywordSet>
  <additionalInfo xml:lang="">{0,unbounded}</additionalInfo>
  <intellectualRights xml:lang="">{0,1}</intellectualRights>
  <licensed>{0,unbounded}</licensed>
  <distribution id="" scope="document" system="">{0,unbounded}</distribution>
  <coverage id="" scope="document" system="">{0,1}</coverage>
  <annotation>{0,unbounded}</annotation>
  <proceduralStep>{0,unbounded}</proceduralStep>
  <references system="">{1,1}</references>
</protocol>
Attributes
QName Type Default Use
id IDType optional
scope ScopeType document optional
system SystemType optional
Source
<xs:element name="protocol" type="pro:ProtocolType">
  <xs:annotation>
    <xs:documentation>tooltip: Protocol Resource summary: A resource that describes a scientific protocol, which can include one or more descriptions of methods and procedures. description: A resource that describes a scientific protocol, which can include one or more descriptions of methods and procedures. If included, this represents the primary resource that is described in this eml document.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element eml / annotations
Namespace No namespace
Annotations
tooltip: Semantic Annotation List

summary: A list of precisely-defined semantic statements about this resource.
					

description: A list of annotations defining precise semantics
						for parts of this resource.  The list consists of a set
						of annotation elements, each referring to a subject within
						the EML document using its references attribute, which provides
						a pointer to the id of the element being annotated.
Diagram
Diagram NO_NAMESPACE.tmp#eml_eml_annotations_annotation
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children annotation
Instance
<annotations>
  <annotation references="">{1,unbounded}</annotation>
</annotations>
Source
<xs:element name="annotations" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>tooltip: Semantic Annotation List summary: A list of precisely-defined semantic statements about this resource. description: A list of annotations defining precise semantics for parts of this resource. The list consists of a set of annotation elements, each referring to a subject within the EML document using its references attribute, which provides a pointer to the id of the element being annotated.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="annotation" minOccurs="1" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about an element in the EML document. description: An annotation represents a precisely-defined semantic statement that applies to this resource. This semantic statement is used to associate precise semantics with a particular element in the EML document. The id of the element being annotated is listed in the references attribute, and must point to a unique id within the EML document. Each annotation consists of a propertyURI and valueURI that define a property and value that apply to the resource. The subject of the statement is implicitly the element that is listed in the references attribute. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:complexContent>
            <xs:extension base="sem:SemanticAnnotation">
              <xs:attribute name="references" type="xs:string" use="required"/>
            </xs:extension>
          </xs:complexContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element eml / annotations / annotation
Namespace No namespace
Annotations
tooltip: Semantic Annotation

summary: A precisely-defined semantic statement about
									an element in the EML document.
								

description: An annotation represents a precisely-defined semantic
									statement that applies to this resource.  This semantic
									statement is used to associate precise semantics with a
									particular element in the EML document.  The id of the
									element being annotated is listed in the references attribute,
									and must point to a unique id within the EML document.
									Each annotation consists of a propertyURI and
									valueURI that define a property and value that apply to the
									resource. The subject of the statement is implicitly the
									element that is listed in the references attribute.
									The associated labels can be used to display the statement to users.
									Each URI is resolvable to a controlled vocabulary
									that provides a definition, relationships to other terms, and
									multiple labels for displaying the statement.
Diagram
Diagram NO_NAMESPACE.tmp#SemanticAnnotation_propertyURI NO_NAMESPACE.tmp#SemanticAnnotation_valueURI semantics-2_2_0.tmp#SemanticAnnotation NO_NAMESPACE.tmp#eml_eml_annotations_eml_eml_annotations_annotation_references
Type extension of SemanticAnnotation
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children propertyURI, valueURI
Instance
<annotation references="">
  <propertyURI label="">{1,1}</propertyURI>
  <valueURI label="">{1,1}</valueURI>
</annotation>
Attributes
QName Type Use
references xs:string required
Source
<xs:element name="annotation" minOccurs="1" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Semantic Annotation summary: A precisely-defined semantic statement about an element in the EML document. description: An annotation represents a precisely-defined semantic statement that applies to this resource. This semantic statement is used to associate precise semantics with a particular element in the EML document. The id of the element being annotated is listed in the references attribute, and must point to a unique id within the EML document. Each annotation consists of a propertyURI and valueURI that define a property and value that apply to the resource. The subject of the statement is implicitly the element that is listed in the references attribute. The associated labels can be used to display the statement to users. Each URI is resolvable to a controlled vocabulary that provides a definition, relationships to other terms, and multiple labels for displaying the statement.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:complexContent>
      <xs:extension base="sem:SemanticAnnotation">
        <xs:attribute name="references" type="xs:string" use="required"/>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element eml / additionalMetadata
Namespace No namespace
Annotations
tooltip: Additional Metadata

summary: A flexible field for including any other relevant metadata that pertains
                to the resource being described.

description: A flexible field for including any other relevant metadata that
                pertains to the resource being described. This field allows EML to be extensible in
                that any XML-based metadata can be included in this element, including metadata from
                other standards such as the FGDC CSDGM. The "describes" element of this field allows
                the specific part of the resource which is described by the additional metadata to
                be indicated formally.
Diagram
Diagram NO_NAMESPACE.tmp#eml_eml_additionalMetadata_id NO_NAMESPACE.tmp#eml_eml_additionalMetadata_describes NO_NAMESPACE.tmp#eml_eml_additionalMetadata_metadata
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children describes, metadata
Instance
<additionalMetadata id="">
  <describes>{0,unbounded}</describes>
  <metadata>{1,1}</metadata>
</additionalMetadata>
Attributes
QName Type Use
id IDType optional
Source
<xs:element name="additionalMetadata" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Additional Metadata summary: A flexible field for including any other relevant metadata that pertains to the resource being described. description: A flexible field for including any other relevant metadata that pertains to the resource being described. This field allows EML to be extensible in that any XML-based metadata can be included in this element, including metadata from other standards such as the FGDC CSDGM. The "describes" element of this field allows the specific part of the resource which is described by the additional metadata to be indicated formally.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="describes" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>tooltip: Describes Reference summary: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. description: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. This is a formal field in that it is an error to provide a value in the "describes" element that does not correspond to the value of one of the "id" attributes in another eml module. This is designed to allow automated processors to discover the contextual relationship between the additional metadata and the resource it describes.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="metadata">
        <xs:annotation>
          <xs:documentation>tooltip: Additional metadata summary: This element contains the additional metadata that is to be included in the document. The content of this field can be any well-formed XML fragment. description: This element contains the additional metadata to be included in the document. This element should be used for extending EML to include metadata that is not already available in another part of the EML specification, or to include site- or system-specific extensions that are needed beyond the core metadata. The additional metadata contained in this field describes the element referenced in the 'describes' element preceding it. The content of this field is any well-formed XML fragment. If that content contains namespace declarations, and if the namespace declaration can be resolved to a schema definition, then the content will be validated against that schema definition. If no namespace is present, or if no schema can be resolved, validation for this fragment will be skipped (validation is "lax").</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:any processContents="lax">
              <xs:annotation>
                <xs:documentation>tooltip: Any Metadata summary: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur. description: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur.</xs:documentation>
              </xs:annotation>
            </xs:any>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="id" type="res:IDType" use="optional"/>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element eml / additionalMetadata / describes
Namespace No namespace
Annotations
tooltip: Describes Reference

summary: A pointer to the id attribute for the sub-portion of the resource
                      that is described by this additional metadata. 

description: A pointer to the id attribute for the sub-portion of the
                      resource that is described by this additional metadata. This is a formal field
                      in that it is an error to provide a value in the "describes" element that does
                      not correspond to the value of one of the "id" attributes in another eml
                      module. This is designed to allow automated processors to discover the
                      contextual relationship between the additional metadata and the resource it
                      describes.
Diagram
Diagram resource-2_2_0.tmp#NonEmptyStringType
Type NonEmptyStringType
Properties
content simple
minOccurs 0
maxOccurs unbounded
Facets
minLength 1
pattern [\s]*[\S][\s\S]*
Source
<xs:element name="describes" type="res:NonEmptyStringType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Describes Reference summary: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. description: A pointer to the id attribute for the sub-portion of the resource that is described by this additional metadata. This is a formal field in that it is an error to provide a value in the "describes" element that does not correspond to the value of one of the "id" attributes in another eml module. This is designed to allow automated processors to discover the contextual relationship between the additional metadata and the resource it describes.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element eml / additionalMetadata / metadata
Namespace No namespace
Annotations
tooltip: Additional metadata

summary: This element contains the additional metadata that is to be
                      included in the document. The content of this field can be any well-formed XML
                      fragment. 

description: This element contains the additional metadata to be included in
                      the document. This element should be used for extending EML to include
                      metadata that is not already available in another part of the EML
                      specification, or to include site- or system-specific extensions that are
                      needed beyond the core metadata. The additional metadata contained in this
                      field describes the element referenced in the 'describes' element preceding
                      it. The content of this field is any well-formed XML fragment. If that content
                      contains namespace declarations, and if the namespace declaration can be
                      resolved to a schema definition, then the content will be validated against
                      that schema definition. If no namespace is present, or if no schema can be
                      resolved, validation for this fragment will be skipped (validation is "lax").
Diagram
Diagram
Properties
content complex
Model
ANY element from ANY namespace
Source
<xs:element name="metadata">
  <xs:annotation>
    <xs:documentation>tooltip: Additional metadata summary: This element contains the additional metadata that is to be included in the document. The content of this field can be any well-formed XML fragment. description: This element contains the additional metadata to be included in the document. This element should be used for extending EML to include metadata that is not already available in another part of the EML specification, or to include site- or system-specific extensions that are needed beyond the core metadata. The additional metadata contained in this field describes the element referenced in the 'describes' element preceding it. The content of this field is any well-formed XML fragment. If that content contains namespace declarations, and if the namespace declaration can be resolved to a schema definition, then the content will be validated against that schema definition. If no namespace is present, or if no schema can be resolved, validation for this fragment will be skipped (validation is "lax").</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:any processContents="lax">
        <xs:annotation>
          <xs:documentation>tooltip: Any Metadata summary: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur. description: Any well-formed XML-formatted metadata may be inserted at this location in the EML document. If an element inserted here contains a reference to its namespace, and if there is an association between that namespace and an XML Schema that can be located by the processing application, then the processing application must validate the metadata element. If these conditions are not met, then validation need not occur.</xs:documentation>
        </xs:annotation>
      </xs:any>
    </xs:sequence>
  </xs:complexType>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Element projectionList / horizCoordSysDef
Namespace No namespace
Annotations
tooltip: Horizonal Coordinate System Definition

summary: The definition of a coordinate system

description: Terms and parameters necessary to define a geographic or projected coordinate
                system for horizonal distances.
Diagram
Diagram NO_NAMESPACE.tmp#horizCoordSysType_name NO_NAMESPACE.tmp#horizCoordSysType_geogCoordSys NO_NAMESPACE.tmp#horizCoordSysType_projCoordSys spatialReference-2_2_0.tmp#horizCoordSysType
Type horizCoordSysType
Properties
content complex
maxOccurs unbounded
Model
Children geogCoordSys, projCoordSys
Instance
<horizCoordSysDef name="">
  <geogCoordSys name="">{1,1}</geogCoordSys>
  <projCoordSys>{1,1}</projCoordSys>
</horizCoordSysDef>
Attributes
QName Type Use
name xs:string required
Source
<xs:element name="horizCoordSysDef" type="horizCoordSysType" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>tooltip: Horizonal Coordinate System Definition summary: The definition of a coordinate system description: Terms and parameters necessary to define a geographic or projected coordinate system for horizonal distances.</xs:documentation>
  </xs:annotation>
</xs:element>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute ReferencesGroup / references / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Source
<xs:attribute name="system" type="SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute AccessType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type AccessType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-access.xsd
Attribute AccessType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type AccessType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-access.xsd
Attribute AccessType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type AccessType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-access.xsd
Attribute AccessType / @order
Namespace No namespace
Annotations
tooltip: Rule order

summary: The order in which the allow and deny rules should be
          applied.

description: To obtain the desired access control, use the order
          attribute to define which rules should be applied first. The acceptable
          values are 'allowFirst' and 'denyFirst'. If 'allowFirst' is
          specified, then all 'allow' rules are processed, and then overridden
          by all 'deny' rules.  If 'denyFirst' is specified, then all 'deny'
          rules are processed, and then overridden by all 'allow' rules.
Type restriction of xs:string
Properties
use optional
default allowFirst
Facets
enumeration allowFirst
enumeration denyFirst
Used by
Complex Type AccessType
Source
<xs:attribute name="order" use="optional" default="allowFirst">
  <xs:annotation>
    <xs:documentation>tooltip: Rule order summary: The order in which the allow and deny rules should be applied. description: To obtain the desired access control, use the order attribute to define which rules should be applied first. The acceptable values are 'allowFirst' and 'denyFirst'. If 'allowFirst' is specified, then all 'allow' rules are processed, and then overridden by all 'deny' rules. If 'denyFirst' is specified, then all 'deny' rules are processed, and then overridden by all 'allow' rules.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="allowFirst"/>
      <xs:enumeration value="denyFirst"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-access.xsd
Attribute AccessType / @authSystem
Namespace No namespace
Annotations
tooltip: Authentication system

summary: The authentication system is used to verify the user or
          group to whom access is allowed or denied.

description: The authentication system determines the set of
          principals (users + groups) that can be used in the access control
          list, and the membership of users in groups. This element is intended
          to provide a reference to the authentication system that is used to
          verify the user or group. This reference is typically in the form
          of a URI, which includes the connection protocol, Internet host, and
          path to the authentication mechanism.
Type xs:string
Properties
use required
Used by
Complex Type AccessType
Source
<xs:attribute name="authSystem" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Authentication system summary: The authentication system is used to verify the user or group to whom access is allowed or denied. description: The authentication system determines the set of principals (users + groups) that can be used in the access control list, and the membership of users in groups. This element is intended to provide a reference to the authentication system that is used to verify the user or group. This reference is typically in the form of a URI, which includes the connection protocol, Internet host, and path to the authentication mechanism.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-access.xsd
Attribute ResourceGroup / alternateIdentifier / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Source
<xs:attribute name="system" type="SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute Address / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type Address
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Attribute Address / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type Address
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Attribute Address / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type Address
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Attribute ResponsibleParty / phone / @phonetype
Namespace No namespace
Annotations
tooltip: Phone type

summary: The type of the phone to which this number
                      applies

description: This attribute gives the type of phone
                      to which this number applies. By default, this is assumed
                      to be of type "voice", but other possibilities include
                      "facsimile" and "tdd".
Type xs:string
Properties
use optional
default voice
Used by
Source
<xs:attribute name="phonetype" type="xs:string" use="optional" default="voice">
  <xs:annotation>
    <xs:documentation>tooltip: Phone type summary: The type of the phone to which this number applies description: This attribute gives the type of phone to which this number applies. By default, this is assumed to be of type "voice", but other possibilities include "facsimile" and "tdd".</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Attribute ResponsibleParty / userId / @directory
Namespace No namespace
Annotations
tooltip: Directory

summary: The directory system within which the
                      directoryId can be retrieved.

description: This attribute names the directory system
                      to which this userId applies. This will generally
                      be a URL that shows how to look up information, for
                      example an LDAP URL. However, it could also be a
                      non-parsable description of the directory system if
                      that is all that is available.
Type xs:string
Properties
use required
Used by
Source
<xs:attribute name="directory" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Directory summary: The directory system within which the directoryId can be retrieved. description: This attribute names the directory system to which this userId applies. This will generally be a URL that shows how to look up information, for example an LDAP URL. However, it could also be a non-parsable description of the directory system if that is all that is available.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Attribute ResponsibleParty / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type ResponsibleParty
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Attribute ResponsibleParty / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type ResponsibleParty
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Attribute ResponsibleParty / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type ResponsibleParty
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-party.xsd
Attribute ParagraphType / ulink / @url
Namespace No namespace
Annotations
Properties
Used by
Source
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-text.xsd
Attribute ResourceGroup / keywordSet / keyword / @keywordType
Namespace No namespace
Annotations
tooltip: Keyword type

summary: The type of each keyword.

description: This field classifies the keyword
                          that has been provided from a list of pre-determined
                          categories. The possible types are listed in the
                          example.
Type KeyTypeCode
Properties
use optional
Facets
enumeration place
tooltip: Place Keywords

summary: Keywords pertaining to a spatial location

description: Keywords naming geographic locations associated
            with the data set.
enumeration stratum
tooltip: Stratum Keywords

summary: Keywords pertaining to a vertical stratum

description: Keywords naming vertical strata associated
            with the data set (e.g., soil horizons).
enumeration temporal
tooltip: Temporal Keywords

summary: Keywords pertaining to temporal data

description: Keywords listing time periods associated
            with the data set.
enumeration theme
tooltip: Thematic Keywords

summary: Keywords pertaining to thematic subject

description: Keywords naming thematics subjects associated
            with the data set.
enumeration taxonomic
tooltip: Taxonomic Keywords

summary: Keywords pertaining to taxon information

description: Keywords listing taxonomic terms associated
            with the data set.  Note that lists of species names or other taxon
            lists should be presented in the taxonomicCoverage element.
Used by
Source
<xs:attribute name="keywordType" type="KeyTypeCode" use="optional">
  <xs:annotation>
    <xs:documentation>tooltip: Keyword type summary: The type of each keyword. description: This field classifies the keyword that has been provided from a list of pre-determined categories. The possible types are listed in the example.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute UrlType / @function
Namespace No namespace
Type FunctionType
Properties
use optional
default download
Facets
enumeration download
enumeration information
Used by
Complex Type UrlType
Source
<xs:attribute name="function" type="FunctionType" use="optional" default="download"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute ConnectionDefinitionType / schemeName / @system
Namespace No namespace
Annotations
tooltip: Scheme System

summary: The system in which this scheme name is
                      relevant

description: The computing system within which this
                      scheme name has relevance. This attribute qualifies the
                      scheme name in order to decrease the likelihood of scheme
                      name collisions when more that one EML user defines a
                      scheme name with the same name but different semantics.
Type SystemType
Properties
use optional
Used by
Source
<xs:attribute name="system" type="SystemType" use="optional">
  <xs:annotation>
    <xs:documentation>tooltip: Scheme System summary: The system in which this scheme name is relevant description: The computing system within which this scheme name has relevance. This attribute qualifies the scheme name in order to decrease the likelihood of scheme name collisions when more that one EML user defines a scheme name with the same name but different semantics.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute ConnectionDefinitionType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Source
<xs:attribute name="id" type="IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute ConnectionDefinitionType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Source
<xs:attribute name="system" type="SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute ConnectionDefinitionType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Source
<xs:attribute name="scope" type="ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute ConnectionType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type ConnectionType
Source
<xs:attribute name="id" type="IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute ConnectionType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type ConnectionType
Source
<xs:attribute name="system" type="SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute ConnectionType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type ConnectionType
Source
<xs:attribute name="scope" type="ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute DistributionType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type DistributionType
Source
<xs:attribute name="id" type="IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute DistributionType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type DistributionType
Source
<xs:attribute name="system" type="SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute DistributionType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type DistributionType
Source
<xs:attribute name="scope" type="ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-resource.xsd
Attribute GeographicCoverage / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type GeographicCoverage
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute GeographicCoverage / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type GeographicCoverage
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute GeographicCoverage / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type GeographicCoverage
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute CitationType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type CitationType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Attribute CitationType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type CitationType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Attribute CitationType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type CitationType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-literature.xsd
Attribute TemporalCoverage / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type TemporalCoverage
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute Coverage / temporalCoverage / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute Coverage / temporalCoverage / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute TaxonomicClassificationType / taxonId / @provider
Namespace No namespace
Annotations
tooltip: Taxon ID Provider

summary: The taxonomic authority or catalog from which the
                      taxonId can be retrieved, defined
                      as the namespace URI for the provider.

description: This attribute holds the namespace URI
                      for the taxonomic authority or catalog to which this taxonId applies.
                      taxonId providers should be chosen for their stability and longevity,
                      and with discernable website URIs or APIs.
Type xs:anyURI
Properties
use required
Used by
Source
<xs:attribute name="provider" type="xs:anyURI" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Taxon ID Provider summary: The taxonomic authority or catalog from which the taxonId can be retrieved, defined as the namespace URI for the provider. description: This attribute holds the namespace URI for the taxonomic authority or catalog to which this taxonId applies. taxonId providers should be chosen for their stability and longevity, and with discernable website URIs or APIs.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute TaxonomicClassificationType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute TaxonomicCoverage / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type TaxonomicCoverage
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute Coverage / taxonomicCoverage / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute Coverage / taxonomicCoverage / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute Coverage / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type Coverage
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute Coverage / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type Coverage
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute Coverage / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type Coverage
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-coverage.xsd
Attribute SemanticAnnotation / propertyURI / @label
Namespace No namespace
Annotations
tooltip: Property Label

summary: 
                                    A human readable representation of the controlled property.
                                

description: 
                                    A label that provides a human readable representation of
                                    the controlled property. The label is often used to represent
                                    the controlled property when displaying annotations in
                                    software. The label is often redundant with one or more labels
                                    that are defined in the controlled vocabulary itself,
                                    but is repreated here within the EML document to make it easy
                                    for consumers to display the annotation to users.  Other
                                    labels, including labels in multiple languages, may often be
                                    accessible from within the ontology or controlled
                                    vocabularly accessible at the propertyURI.  Property definitions
                                    and relationships to other properties are also typically
                                    provided within the vocabularly accessible at the propertyURI.
                                    Software and people may be able to resolve the URI to find out
                                    the definition and retrieve additional labels and other metadata
                                    for presentation to users.
Type xs:string
Properties
use required
Used by
Source
<xs:attribute name="label" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Property Label summary: A human readable representation of the controlled property. description: A label that provides a human readable representation of the controlled property. The label is often used to represent the controlled property when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the propertyURI. Property definitions and relationships to other properties are also typically provided within the vocabularly accessible at the propertyURI. Software and people may be able to resolve the URI to find out the definition and retrieve additional labels and other metadata for presentation to users.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-semantics.xsd
Attribute SemanticAnnotation / valueURI / @label
Namespace No namespace
Annotations
tooltip: Value Label

summary: 
                                  A human readable representation of the controlled value.
                              

description: 
                                  A label that provides a human readable representation of
                                  the controlled value. The label is often used to represent the
                                  controlled value when displaying annotations in software. The
                                  label is often redundant with one or more labels that are
                                  defined in the controlled vocabulary itself, but is repreated
                                  here within the EML document to make it easy for consumers to
                                  display the annotation to users.  Other labels, including
                                  labels in multiple languages, may often be accessible from
                                  within the ontology or controlled vocabularly accessible at
                                  the valueURI.  Value definitions and relationships to
                                  other terms are also typically provided within the vocabularly
                                  accessible at the valueURI.  Software and people can resolve
                                  the value URI to find out the definition of the value and
                                  retrieve additional labels and other metadata about the value
                                  for presentation to users.
Type xs:string
Properties
use required
Used by
Source
<xs:attribute name="label" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Value Label summary: A human readable representation of the controlled value. description: A label that provides a human readable representation of the controlled value. The label is often used to represent the controlled value when displaying annotations in software. The label is often redundant with one or more labels that are defined in the controlled vocabulary itself, but is repreated here within the EML document to make it easy for consumers to display the annotation to users. Other labels, including labels in multiple languages, may often be accessible from within the ontology or controlled vocabularly accessible at the valueURI. Value definitions and relationships to other terms are also typically provided within the vocabularly accessible at the valueURI. Software and people can resolve the value URI to find out the definition of the value and retrieve additional labels and other metadata about the value for presentation to users.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-semantics.xsd
Attribute PhysicalDistributionType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Attribute PhysicalDistributionType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Attribute PhysicalDistributionType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Attribute ResearchProjectType / studyAreaDescription / descriptor / descriptorValue / @name_or_id
Namespace No namespace
Annotations
tooltip: The name or ID of a descriptor
                                  value.

summary: The name part of a name/value
                                  pair of a descriptor; or ID portion of a
                                  classification, if applicable.

description: The name_or_id field is the
                                  name part of a name/value pair of a
                                  descriptor; or ID portion of a
                                  classification, if applicable. The values of
                                  biogeophysical classification systems, e.g.
                                  Bailey-Ecoregions, often take the form of an
                                  ID or Code along with a text representation.
                                  For example, the ID/Code M131 refers to the
                                  phrase "Open Woodland -Tundra". M131 is an
                                  unambiguous reference to a more detailed
                                  description. If one is using a published
                                  classification system then there should be a
                                  corresponding citation to the source, e.g.,
                                  Bailey,R.G., 1996 "Ecosystem
                                  Geography".
Type xs:string
Properties
use optional
Used by
Source
<xs:attribute name="name_or_id" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>tooltip: The name or ID of a descriptor value. summary: The name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. description: The name_or_id field is the name part of a name/value pair of a descriptor; or ID portion of a classification, if applicable. The values of biogeophysical classification systems, e.g. Bailey-Ecoregions, often take the form of an ID or Code along with a text representation. For example, the ID/Code M131 refers to the phrase "Open Woodland -Tundra". M131 is an unambiguous reference to a more detailed description. If one is using a published classification system then there should be a corresponding citation to the source, e.g., Bailey,R.G., 1996 "Ecosystem Geography".</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Attribute ResearchProjectType / studyAreaDescription / descriptor / @name
Namespace No namespace
Annotations
tooltip: name

summary: The name of the descriptor
                        system.

description: The name of the descriptor system. The
                        name can be either a theme such as climate or
                        hydrology, or the name of a citable classification
                        system.
Type DescriptorType
Properties
use required
Used by
Source
<xs:attribute name="name" type="DescriptorType" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: name summary: The name of the descriptor system. description: The name of the descriptor system. The name can be either a theme such as climate or hydrology, or the name of a citable classification system.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Attribute ResearchProjectType / studyAreaDescription / descriptor / @citableClassificationSystem
Namespace No namespace
Annotations
tooltip: citation classification
                        system

summary: This boolean attribute defines whether
                        this descriptor comes from a citable classification
                        system or not.

description: This boolean attribute defines whether
                        this descriptor comes from a citable classification
                        system or not.
Type xs:boolean
Properties
use required
Used by
Source
<xs:attribute name="citableClassificationSystem" type="xs:boolean" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: citation classification system summary: This boolean attribute defines whether this descriptor comes from a citable classification system or not. description: This boolean attribute defines whether this descriptor comes from a citable classification system or not.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Attribute ResearchProjectType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type ResearchProjectType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Attribute ResearchProjectType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type ResearchProjectType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Attribute ResearchProjectType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type ResearchProjectType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-project.xsd
Attribute SoftwareType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type SoftwareType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Attribute SoftwareType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type SoftwareType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Attribute SoftwareType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type SoftwareType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-software.xsd
Attribute ProtocolType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type ProtocolType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-protocol.xsd
Attribute ProtocolType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type ProtocolType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-protocol.xsd
Attribute ProtocolType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type ProtocolType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-protocol.xsd
Attribute EntityGroup / alternateIdentifier / @system
Namespace No namespace
Annotations
tooltip: Identifier System

summary: The system in which this id is
                    relevant

description: The information management system within
                    which this identifier has relevance. Generally, the
                    identifier would be unique within the "system" and would be
                    sufficient to retrieve the entity from the system. The
                    system is often a URL or URI that identifies the main entry
                    point for the information management
                    system.
Type SystemType
Properties
use optional
Used by
Source
<xs:attribute name="system" type="res:SystemType" use="optional">
  <xs:annotation>
    <xs:documentation>tooltip: Identifier System summary: The system in which this id is relevant description: The information management system within which this identifier has relevance. Generally, the identifier would be unique within the "system" and would be sufficient to retrieve the entity from the system. The system is often a URL or URI that identifies the main entry point for the information management system.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Attribute PhysicalType / size / @unit
Namespace No namespace
Annotations
tooltip: Unit of measurement

summary: Unit of measurement for the entity
                            size, by default byte

description: This element gives the unit of
                            measurement for the size of the entity, and is
                            by default a byte.
Properties
use optional
default byte
Used by
Source
<xs:attribute name="unit" use="optional" default="byte">
  <xs:annotation>
    <xs:documentation>tooltip: Unit of measurement summary: Unit of measurement for the entity size, by default byte description: This element gives the unit of measurement for the size of the entity, and is by default a byte.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Attribute PhysicalType / authentication / @method
Namespace No namespace
Annotations
tooltip: Authentication method

summary: The method used to calculate an
                            authentication checksum.

description: This element names the method used
                            to calculate and authentication checksum that can
                            be used to validate a bytestream. Typical checksum
                            methods include MD5 and CRC.
Type xs:string
Properties
use optional
Used by
Source
<xs:attribute name="method" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>tooltip: Authentication method summary: The method used to calculate an authentication checksum. description: This element names the method used to calculate and authentication checksum that can be used to validate a bytestream. Typical checksum methods include MD5 and CRC.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Attribute PhysicalType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type PhysicalType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Attribute PhysicalType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type PhysicalType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Attribute PhysicalType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type PhysicalType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-physical.xsd
Attribute AttributeType / storageType / @typeSystem
Namespace No namespace
Annotations
tooltip: Storage Type System

summary: The system used to define the storage types.
                      This should be an identifier of a well known and
                      published typing system.

description: The typeSystem attribute is the system
                      used to define the storage types. This should be an
                      identifier of a well known and published typing system.
                      The default and recommended system is the XML Schema data
                      type system. For details go to http://www.w3.org. If
                      another system is used (such as Java or C++ types),
                      typeSystem should be changed to match the
                      system.
Type xs:string
Properties
use optional
default http://www.w3.org/2001/XMLSchema-datatypes
Used by
Source
<xs:attribute name="typeSystem" type="xs:string" use="optional" default="http://www.w3.org/2001/XMLSchema-datatypes">
  <xs:annotation>
    <xs:documentation>tooltip: Storage Type System summary: The system used to define the storage types. This should be an identifier of a well known and published typing system. description: The typeSystem attribute is the system used to define the storage types. This should be an identifier of a well known and published typing system. The default and recommended system is the XML Schema data type system. For details go to http://www.w3.org. If another system is used (such as Java or C++ types), typeSystem should be changed to match the system.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute NonNumericDomainType / enumeratedDomain / codeDefinition / @order
Namespace No namespace
Annotations
tooltip: Order

summary: Mechanism for specifying what the
			order of the code-definitions included should
			be

description: Ordinal scale measurements have a discrete list
			of values with a specific ordering of those values. This attributes
			specifies that order from low to high. For example, for LOW,
            MEDIUM, HIGH, the order attribute might be "LOW=1, MEDIUM=2 and
            HIGH=3".
Type xs:long
Properties
use optional
Used by
Source
<xs:attribute name="order" type="xs:long" use="optional">
  <xs:annotation>
    <xs:documentation>tooltip: Order summary: Mechanism for specifying what the order of the code-definitions included should be description: Ordinal scale measurements have a discrete list of values with a specific ordering of those values. This attributes specifies that order from low to high. For example, for LOW, MEDIUM, HIGH, the order attribute might be "LOW=1, MEDIUM=2 and HIGH=3".</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute NonNumericDomainType / enumeratedDomain / @enforced
Namespace No namespace
Annotations
tooltip: Enforced Domain

summary: Indicates whether the enumerated
                  domain values enforced.

description: Indicates whether the enumerated
                  domain values are the only allowable values for
                  the domain.  In some exceedingly rare cases, users may
                  wish to present a list of value codes in
                  enumeratedDomain but not formally restrict the value
                  space for the attribute to those values.  If so, they
                  can indicate this by setting the enforced attribute
                  to the value no.  Acceptable values are yes and no, and
                  the default value is yes.
Type restriction of xs:string
Properties
use optional
default yes
Facets
enumeration yes
enumeration no
Used by
Source
<xs:attribute name="enforced" use="optional" default="yes">
  <xs:annotation>
    <xs:documentation>tooltip: Enforced Domain summary: Indicates whether the enumerated domain values enforced. description: Indicates whether the enumerated domain values are the only allowable values for the domain. In some exceedingly rare cases, users may wish to present a list of value codes in enumeratedDomain but not formally restrict the value space for the attribute to those values. If so, they can indicate this by setting the enforced attribute to the value no. Acceptable values are yes and no, and the default value is yes.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="yes"/>
      <xs:enumeration value="no"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute NonNumericDomainType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type NonNumericDomainType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute BoundsGroup / bounds / minimum / @exclusive
Namespace No namespace
Annotations
tooltip: Exclusive
                        

summary: Exclusive bounds flag
                        

description: If exclusive is set to true, then
                        the value specifies a lower bound not including
                        the value itself.  Setting exclusive to true is
                        the equivalent of using a less-than or greater-than
                        operator, while setting it to false is the same as
                        using a less-than-or-equals or greater-than-or-equals
                        operator. For example, if the minimum is "5" and
                        exclusive is false, then all values must be greater
                        than or equal to 5, but if exclusive is true than
                        all values must be greater than 5 (not including
                        5.0 itself).
Type xs:boolean
Properties
use required
Used by
Source
<xs:attribute name="exclusive" type="xs:boolean" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute BoundsGroup / bounds / maximum / @exclusive
Namespace No namespace
Annotations
tooltip: Exclusive
                        

summary: Exclusive bounds flag
                        

description: If exclusive is set to true, then
                        the value specifies a lower bound not including
                        the value itself.  Setting exclusive to true is
                        the equivalent of using a less-than or greater-than
                        operator, while setting it to false is the same as
                        using a less-than-or-equals or greater-than-or-equals
                        operator. For example, if the minimum is "5" and
                        exclusive is false, then all values must be greater
                        than or equal to 5, but if exclusive is true than
                        all values must be greater than 5 (not including
                        5.0 itself).
Type xs:boolean
Properties
use required
Used by
Source
<xs:attribute name="exclusive" type="xs:boolean" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute NumericDomainType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type NumericDomainType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute BoundsDateGroup / bounds / minimum / @exclusive
Namespace No namespace
Annotations
tooltip: Exclusive
                        

summary: Exclusive bounds flag
                        

description: If exclusive is set to true, then
                        the value specifies a lower bound not including
                        the value itself.  Setting exclusive to true is
                        the equivalent of using a less-than or greater-than
                        operator, while setting it to false is the same as
                        using a less-than-or-equals or greater-than-or-equals
                        operator. For example, if the minimum is "5" and
                        exclusive is false, then all values must be greater
                        than or equal to 5, but if exclusive is true than
                        all values must be greater than 5 (not including
                        5.0 itself).
Type xs:boolean
Properties
use required
Used by
Source
<xs:attribute name="exclusive" type="xs:boolean" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute BoundsDateGroup / bounds / maximum / @exclusive
Namespace No namespace
Annotations
tooltip: Exclusive
                        

summary: Exclusive bounds flag
                        

description: If exclusive is set to true, then
                        the value specifies a lower bound not including
                        the value itself.  Setting exclusive to true is
                        the equivalent of using a less-than or greater-than
                        operator, while setting it to false is the same as
                        using a less-than-or-equals or greater-than-or-equals
                        operator. For example, if the minimum is "5" and
                        exclusive is false, then all values must be greater
                        than or equal to 5, but if exclusive is true than
                        all values must be greater than 5 (not including
                        5.0 itself).
Type xs:boolean
Properties
use required
Used by
Source
<xs:attribute name="exclusive" type="xs:boolean" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Exclusive summary: Exclusive bounds flag description: If exclusive is set to true, then the value specifies a lower bound not including the value itself. Setting exclusive to true is the equivalent of using a less-than or greater-than operator, while setting it to false is the same as using a less-than-or-equals or greater-than-or-equals operator. For example, if the minimum is "5" and exclusive is false, then all values must be greater than or equal to 5, but if exclusive is true than all values must be greater than 5 (not including 5.0 itself).</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute DateTimeDomainType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type DateTimeDomainType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute AttributeType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type AttributeType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute AttributeType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type AttributeType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute AttributeType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type AttributeType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute AttributeListType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type AttributeListType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-attribute.xsd
Attribute ConstraintType / checkConstraint / @language
Namespace No namespace
Annotations
tooltip: Language

summary: The language that the is used to express or
                implement the check constraint.

description: The language element declares the language
                that is used to implement the check constraint.  This is
                typically the name and version of a programming language such as
                Java, C, Perl, Basic, or other.  Sometime it is the name and
                version of a scriptable analysis system such as SAS, Matlab, R,
                or SPlus.
Type xs:string
Properties
use optional
Used by
Source
<xs:attribute name="language" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>tooltip: Language summary: The language that the is used to express or implement the check constraint. description: The language element declares the language that is used to implement the check constraint. This is typically the name and version of a programming language such as Java, C, Perl, Basic, or other. Sometime it is the name and version of a scriptable analysis system such as SAS, Matlab, R, or SPlus.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Attribute ConstraintType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type ConstraintType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Attribute ConstraintType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type ConstraintType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Attribute ConstraintType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type ConstraintType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-constraint.xsd
Attribute DataTableType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type DataTableType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataTable.xsd
Attribute DataTableType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type DataTableType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataTable.xsd
Attribute DataTableType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type DataTableType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataTable.xsd
Attribute geogCoordSysType / datum / @name
Namespace No namespace
Type xs:string
Properties
content simple
Used by
Source
<xs:attribute name="name" type="xs:string"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute geogCoordSysType / spheroid / @name
Namespace No namespace
Annotations
tooltip: Spheroid name

summary: The name of the spheroid.

description:
Type xs:string
Properties
content simple
Used by
Source
<xs:attribute name="name" type="xs:string">
  <xs:annotation>
    <xs:documentation>tooltip: Spheroid name summary: The name of the spheroid. description:</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute geogCoordSysType / spheroid / @semiAxisMajor
Namespace No namespace
Annotations
tooltip: Semi-axis Major

summary: The larger of two orthogonal axes that define the ellipse

description:
Type xs:float
Properties
content simple
Used by
Source
<xs:attribute name="semiAxisMajor" type="xs:float">
  <xs:annotation>
    <xs:documentation>tooltip: Semi-axis Major summary: The larger of two orthogonal axes that define the ellipse description:</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute geogCoordSysType / spheroid / @denomFlatRatio
Namespace No namespace
Type xs:float
Properties
content simple
Used by
Source
<xs:attribute name="denomFlatRatio" type="xs:float"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute geogCoordSysType / primeMeridian / @name
Namespace No namespace
Annotations
tooltip: Prime Meridian Name

summary: The name of the Prime Meridian

description:
Type xs:string
Properties
content simple
Used by
Source
<xs:attribute name="name" type="xs:string">
  <xs:annotation>
    <xs:documentation>tooltip: Prime Meridian Name summary: The name of the Prime Meridian description:</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute geogCoordSysType / primeMeridian / @longitude
Namespace No namespace
Annotations
tooltip: Longitude

summary: The longitude of the Prime Meridian

description:
Type restriction of xs:float
Properties
use required
Facets
maxInclusive 180
minInclusive -180
Used by
Source
<xs:attribute name="longitude" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Longitude summary: The longitude of the Prime Meridian description:</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:float">
      <xs:minInclusive value="-180"/>
      <xs:maxInclusive value="180"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute geogCoordSysType / unit / @name
Namespace No namespace
Annotations
tooltip: Unit Name

summary: The name of the unit of measure .

description:
Type angleUnits
Properties
use required
Facets
enumeration radian
enumeration degree
enumeration grad
enumeration degree
enumeration grad
Used by
Source
<xs:attribute name="name" type="angleUnits" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Unit Name summary: The name of the unit of measure . description:</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute geogCoordSysType / @name
Namespace No namespace
Type xs:string
Properties
content simple
Used by
Complex Type geogCoordSysType
Source
<xs:attribute name="name" type="xs:string"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute horizCoordSysType / projCoordSys / projection / parameter / @name
Namespace No namespace
Annotations
tooltip: Parameter Name

summary: The name of the parameter.

description: If the paramter corresponds to one that has been
                            defined in the existing eml-SpatialReferenceDictionary, then that name should be
                            used to enhance recogonizability.
Type xs:string
Properties
use required
Used by
Source
<xs:attribute name="name" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter Name summary: The name of the parameter. description: If the paramter corresponds to one that has been defined in the existing eml-SpatialReferenceDictionary, then that name should be used to enhance recogonizability.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute horizCoordSysType / projCoordSys / projection / parameter / @description
Namespace No namespace
Annotations
tooltip: Parameter Description

summary: A description of the Parameter.

description:
Type xs:string
Properties
use optional
Used by
Source
<xs:attribute name="description" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter Description summary: A description of the Parameter. description:</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute horizCoordSysType / projCoordSys / projection / parameter / @value
Namespace No namespace
Annotations
tooltip: Parameter Value

summary: The value supplied for the parameter

description:
Properties
use required
Used by
Source
<xs:attribute name="value" type="xs:anySimpleType" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Parameter Value summary: The value supplied for the parameter description:</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute horizCoordSysType / projCoordSys / projection / unit / @name
Namespace No namespace
Annotations
tooltip: Projection Unit Name

summary: The name of the unit of measure.

description:
Type lengthUnits
Properties
use required
Facets
enumeration meter
enumeration nanometer
enumeration micrometer
enumeration micron
enumeration millimeter
enumeration centimeter
enumeration decimeter
enumeration dekameter
enumeration hectometer
enumeration kilometer
enumeration megameter
enumeration angstrom
enumeration inch
enumeration Foot_US
enumeration foot
enumeration Foot_Gold_Coast
enumeration fathom
enumeration nauticalMile
enumeration yard
enumeration Yard_Indian
enumeration Link_Clarke
enumeration Yard_Sears
enumeration mile
Used by
Source
<xs:attribute name="name" type="lengthUnits" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Projection Unit Name summary: The name of the unit of measure. description:</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute horizCoordSysType / projCoordSys / projection / @name
Namespace No namespace
Annotations
tooltip: Projection Name

summary: The name of the projection method.

description: EML does not attempt to document the details
                      of the particular projection algorithm. It is incumbent on metadata provider
                      to ensure that the meaning of the names used to identify the method and its parameters will be
                      as clear as possible.
Type xs:string
Properties
content simple
Used by
Source
<xs:attribute name="name" type="xs:string">
  <xs:annotation>
    <xs:documentation>tooltip: Projection Name summary: The name of the projection method. description: EML does not attempt to document the details of the particular projection algorithm. It is incumbent on metadata provider to ensure that the meaning of the names used to identify the method and its parameters will be as clear as possible.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute horizCoordSysType / @name
Namespace No namespace
Type xs:string
Properties
use required
Used by
Complex Type horizCoordSysType
Source
<xs:attribute name="name" type="xs:string" use="required"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute SpatialReferenceType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type SpatialReferenceType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute SpatialReferenceType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type SpatialReferenceType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute SpatialReferenceType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type SpatialReferenceType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialReference.xsd
Attribute SpatialRasterType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type SpatialRasterType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Attribute SpatialRasterType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type SpatialRasterType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Attribute SpatialRasterType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type SpatialRasterType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialRaster.xsd
Attribute SpatialVectorType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type SpatialVectorType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Attribute SpatialVectorType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type SpatialVectorType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Attribute SpatialVectorType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type SpatialVectorType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-spatialVector.xsd
Attribute StoredProcedureType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type StoredProcedureType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Attribute StoredProcedureType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type StoredProcedureType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Attribute StoredProcedureType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type StoredProcedureType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-storedProcedure.xsd
Attribute ViewType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type ViewType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-view.xsd
Attribute ViewType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type ViewType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-view.xsd
Attribute ViewType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type ViewType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-view.xsd
Attribute OtherEntityType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type OtherEntityType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Attribute OtherEntityType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type OtherEntityType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Attribute OtherEntityType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type OtherEntityType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-entity.xsd
Attribute DatasetType / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Complex Type DatasetType
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Attribute DatasetType / @system
Namespace No namespace
Type SystemType
Properties
use optional
Used by
Complex Type DatasetType
Source
<xs:attribute name="system" type="res:SystemType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Attribute DatasetType / @scope
Namespace No namespace
Type ScopeType
Properties
use optional
default document
Facets
enumeration system
enumeration document
Used by
Complex Type DatasetType
Source
<xs:attribute name="scope" type="res:ScopeType" use="optional" default="document"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml-dataset.xsd
Attribute eml / annotations / annotation / @references
Namespace No namespace
Type xs:string
Properties
use required
Used by
Source
<xs:attribute name="references" type="xs:string" use="required"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Attribute eml / additionalMetadata / @id
Namespace No namespace
Type IDType
Properties
use optional
Used by
Source
<xs:attribute name="id" type="res:IDType" use="optional"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Attribute eml / @packageId
Namespace No namespace
Annotations
tooltip: Package Identifer

summary: A globally unique identifier for the data package described by this EML metadata document that can be used
              to cite it elsewhere.

description: A globally unique identifier for the data package described by this EML metadata document
              that can be used to cite it elsewhere. This identifier can be interpreted as the formal
              accession number for the data package, and is therefore required. It must be globally unique
              within a particular data management system, which should be specified in the system
              attribute as a URI. Typically a DOI or other identifier that is both citable and
              resolvable is used for published data packages.
Type xs:string
Properties
use required
Used by
Element eml
Source
<xs:attribute name="packageId" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>tooltip: Package Identifer summary: A globally unique identifier for the data package described by this EML metadata document that can be used to cite it elsewhere. description: A globally unique identifier for the data package described by this EML metadata document that can be used to cite it elsewhere. This identifier can be interpreted as the formal accession number for the data package, and is therefore required. It must be globally unique within a particular data management system, which should be specified in the system attribute as a URI. Typically a DOI or other identifier that is both citable and resolvable is used for published data packages.</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Attribute eml / @system
Namespace No namespace
Type SystemType
Properties
use required
Used by
Element eml
Source
<xs:attribute name="system" type="res:SystemType" use="required"/>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd
Attribute eml / @scope
Namespace No namespace
Annotations
tooltip: Identifer Scope

summary: The scope of the identifier.

description: The scope of the identifier. Scope is generally set to either "system",
              meaning that it is scoped according to the "system" attribute, or "document" if it is
              only to be in scope within this single document instance. In this particular use of
              scope, it is FIXED to be "system" because the packageId is required and always has the
              scope of the required "system".
Type ScopeType
Properties
fixed system
Facets
enumeration system
enumeration document
Used by
Element eml
Source
<xs:attribute name="scope" type="res:ScopeType" fixed="system">
  <xs:annotation>
    <xs:documentation>tooltip: Identifer Scope summary: The scope of the identifier. description: The scope of the identifier. Scope is generally set to either "system", meaning that it is scoped according to the "system" attribute, or "document" if it is only to be in scope within this single document instance. In this particular use of scope, it is FIXED to be "system" because the packageId is required and always has the scope of the required "system".</xs:documentation>
  </xs:annotation>
</xs:attribute>
Schema location file:/Volumes/mob/EML_schema/EML-2.2.0/git_checkouts/eml/tmp/eml.xsd