| ### Showing:
Annotations
Attributes
Diagrams
Facets
Instances
Model
Properties

Imported schema eml-attribute.xsd

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    '$RCSfile: eml-attribute.xsd,v $'
           Copyright: 1997-2002 Regents of the University of California,
                                University of New Mexico, and
                                Arizona State University
            Sponsors: National Center for Ecological Analysis and Synthesis and
                      Partnership for Interdisciplinary Studies of Coastal Oceans,
                         University of California Santa Barbara
                      Long-Term Ecological Research Network Office,
                         University of New Mexico
                      Center for Environmental Studies, Arizona State University
       Other funding: National Science Foundation (see README for details)
                      The David and Lucile Packard Foundation
         For Details: http://knb.ecoinformatics.org/

            '$Author: obrien $'
              '$Date: 2009-02-25 23:51:54 $'
          '$Revision: 1.123 $'

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

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

        You should have received a copy of the GNU General Public License
        along with this program; if not, write to the Free Software
        Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
    moduleName: eml-attribute

    moduleDescription:

                The eml-attribute module - Attribute level information within
                dataset entities

    recommendedUsage: any dataset that uses dataTable, spatialRaster,
            spatialVector, storedProcedure, view or otherEntity or in a custom
            module where one wants to document an attribute
            (variable)

    standAlone: yes
Properties |
attribute form default | unqualified
element form default | unqualified

Element AttributeListType / attribute

Namespace | No namespace
Diagram |
Type | AttributeType
Properties |
content | complex
maxOccurs | unbounded
Model | (attributeName , attributeLabel* , attributeDefinition , storageType* , measurementScale , missingValueCode* , accuracy{0,1} , coverage{0,1} , methods{0,1} , annotation*) | (references)
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 id="" scope="document" system="">{0,unbounded}</annotation>
      <references system="">{1,1}</references>
    </attribute>
Attributes |
QName | Type | Default | Use |
--- | --- | --- | --- | ---
id | IDType |  | optional |
scope | ScopeType | document | optional |
system | SystemType |  | optional |

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.

    example: spden

    example: spatialden

    example: site

    example: spcode
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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'.

    example: Species Density

    example: Spatial Density

    example: Name of Site

    example: Species Code
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
minOccurs | 0
maxOccurs | unbounded
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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.

    example: "spden" is the number of individuals of all
                  macro invertebrate species found in the plot
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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).

    example: integer

    example: int
Diagram |
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.

    example:
                          http://www.w3.org/2001/XMLSchema-datatypes

    example: java

    example: C

    example: Oracle 8i

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.

    example: 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.

    example: 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.

    example: 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).

    example: 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 |
Properties |
content | complex
Model | nominal | ordinal | interval | ratio | dateTime
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>

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 |
Properties |
content | complex
Model | nonNumericDomain
Children | nonNumericDomain
Instance |
    <nominal>
      <nonNumericDomain id="">{1,1}</nonNumericDomain>
    </nominal>

Element AttributeType / measurementScale / nominal / nonNumericDomain

Namespace | No namespace
Diagram |
Type | NonNumericDomainType
Properties |
content | complex
Model | enumeratedDomain | textDomain | (references)
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 |

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 |
Properties |
content | complex
Model | codeDefinition+ | externalCodeSet | entityCodeList
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.

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 |
Properties |
content | complex
maxOccurs | unbounded
Model | code , definition , source{0,1}
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".

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

    example: 1

    example: HIGH

    example: BEPA

    example: 24
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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.

    example: high density, above 10 per square
                              meter
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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.

    example: ISO country codes
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
minOccurs | 0
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Properties |
content | complex
Model | codesetName , (citation | codesetURL)
Children | citation, codesetName, codesetURL
Instance |
    <externalCodeSet>
      <codesetName>{1,1}</codesetName>
      <citation id="" scope="document" system="">{1,1}</citation>
      <codesetURL>{1,1}</codesetURL>
    </externalCodeSet>

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.

    example: FIPS State Abbreviation
                              Codes
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Type | CitationType
Properties |
content | complex
Model | (alternateIdentifier* , shortName{0,1} , title+ , creator+ , metadataProvider* , associatedParty* , pubDate{0,1} , language{0,1} , series{0,1} , abstract{0,1} , keywordSet* , additionalInfo* , intellectualRights{0,1} , licensed* , distribution* , coverage{0,1} , annotation* , contact* , (article | book | chapter | editedBook | manuscript | report | thesis | conferenceProceedings | personalCommunication | map | generic | audioVisual | presentation)) | bibtex | (references)
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 id="" scope="document" system="">{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 |

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 |
Type | xs:anyURI
Properties |
content | simple

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 |
Properties |
content | complex
Model | entityReference , valueAttributeReference , definitionAttributeReference , orderAttributeReference{0,1}
Children | definitionAttributeReference, entityReference, orderAttributeReference, valueAttributeReference
Instance |
    <entityCodeList>
      <entityReference>{1,1}</entityReference>
      <valueAttributeReference>{1,1}</valueAttributeReference>
      <definitionAttributeReference>{1,1}</definitionAttributeReference>
      <orderAttributeReference>{0,1}</orderAttributeReference>
    </entityCodeList>

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 |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Type | NonEmptyStringType
Properties |
content | simple
minOccurs | 0
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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.

    example: Typically, a text domain will have an empty
                  pattern or one that constrains allowable values. For
                  example, '[0-9]{3}-[0-9]{3}-[0-9]{4}' allows for only
                  numeric digits in the pattern of a US phone
                  number.
Diagram |
Properties |
content | complex
Model | definition , pattern* , source{0,1}
Children | definition, pattern, source
Instance |
    <textDomain>
      <definition>{1,1}</definition>
      <pattern>{0,unbounded}</pattern>
      <source>{0,1}</source>
    </textDomain>

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.

    example: US telephone numbers in the format
                        "(999) 888-7777"
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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.

    example: '[0-9a-zA-Z]' matches simple
                        alphanumeric strings and '(\d\d\d) \d\d\d-\d\d\d\d'
                        represents telephone strings in the US of the form
                        '(704) 876-1734'
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
minOccurs | 0
maxOccurs | unbounded
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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.

    example: ISO country codes
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
minOccurs | 0
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Properties |
content | complex
Model | nonNumericDomain
Children | nonNumericDomain
Instance |
    <ordinal>
      <nonNumericDomain id="">{1,1}</nonNumericDomain>
    </ordinal>

Element AttributeType / measurementScale / ordinal / nonNumericDomain

Namespace | No namespace
Diagram |
Type | NonNumericDomainType
Properties |
content | complex
Model | enumeratedDomain | textDomain | (references)
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 |

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 |
Properties |
content | complex
Model | unit , precision{0,1} , numericDomain
Children | numericDomain, precision, unit
Instance |
    <interval>
      <unit>{1,1}</unit>
      <precision>{0,1}</precision>
      <numericDomain id="">{1,1}</numericDomain>
    </interval>

Element AttributeType / measurementScale / interval / unit

Namespace | No namespace
Diagram |
Type | UnitType
Properties |
content | complex
Model | standardUnit | customUnit
Children | customUnit, standardUnit
Instance |
    <unit>
      <standardUnit>{1,1}</standardUnit>
      <customUnit>{1,1}</customUnit>
    </unit>

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.

    example: meter

    example: second

    example: joule
Diagram |
Type | unit:StandardUnitDictionary
Properties |
content | simple

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.

    example: gramsPerOneThirdMeter
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

Element AttributeType / measurementScale / interval / precision

Namespace | No namespace
Diagram |
Type | PrecisionType
Properties |
content | complex
minOccurs | 0

Element AttributeType / measurementScale / interval / numericDomain

Namespace | No namespace
Diagram |
Type | NumericDomainType
Properties |
content | complex
Model | (numberType , bounds*) | (references)
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 |

Element NumericDomainType / numberType

Namespace | No namespace
Annotations |
    tooltip: number type
Diagram |
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).

    example: 4.1516

    example: 2.5

    example: .3333333...

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 |
Properties |
content | complex
minOccurs | 0
maxOccurs | unbounded
Model | minimum{0,1} , maximum{0,1}
Children | maximum, minimum
Instance |
    <bounds>
      <minimum exclusive="">{0,1}</minimum>
      <maximum exclusive="">{0,1}</maximum>
    </bounds>

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 |
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).

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 |
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).

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 |
Properties |
content | complex
Model | unit , precision{0,1} , numericDomain
Children | numericDomain, precision, unit
Instance |
    <ratio>
      <unit>{1,1}</unit>
      <precision>{0,1}</precision>
      <numericDomain id="">{1,1}</numericDomain>
    </ratio>

Element AttributeType / measurementScale / ratio / unit

Namespace | No namespace
Diagram |
Type | UnitType
Properties |
content | complex
Model | standardUnit | customUnit
Children | customUnit, standardUnit
Instance |
    <unit>
      <standardUnit>{1,1}</standardUnit>
      <customUnit>{1,1}</customUnit>
    </unit>

Element AttributeType / measurementScale / ratio / precision

Namespace | No namespace
Diagram |
Type | PrecisionType
Properties |
content | complex
minOccurs | 0

Element AttributeType / measurementScale / ratio / numericDomain

Namespace | No namespace
Diagram |
Type | NumericDomainType
Properties |
content | complex
Model | (numberType , bounds*) | (references)
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 |

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 |
Properties |
content | complex
Model | formatString , dateTimePrecision{0,1} , dateTimeDomain{0,1}
Children | dateTimeDomain, dateTimePrecision, formatString
Instance |
    <dateTime>
      <formatString>{1,1}</formatString>
      <dateTimePrecision>{0,1}</dateTimePrecision>
      <dateTimeDomain id="">{0,1}</dateTimeDomain>
    </dateTime>

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 Datetime   YYYY-MM-DDThh:mm:ss-hh 2002-10-14T09:13:45-07
                      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.

    example: YYYY-MM-DDThh:mm:ss

    example: YYYY-MM-DD

    example: YYYY

    example: hh:mm:ss

    example: hh:mm:ss.sss
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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.

    example: 0.1

    example: 0.01
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
minOccurs | 0
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Type | DateTimeDomainType
Properties |
content | complex
minOccurs | 0
Model | (bounds*) | (references)
Children | bounds, references
Instance |
    <dateTimeDomain id="">
      <bounds>{0,unbounded}</bounds>
      <references system="">{1,1}</references>
    </dateTimeDomain>
Attributes |
QName | Type | Use |
--- | --- | --- | ---
id | IDType | optional |

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 |
Properties |
content | complex
minOccurs | 0
maxOccurs | unbounded
Model | minimum{0,1} , maximum{0,1}
Children | maximum, minimum
Instance |
    <bounds>
      <minimum exclusive="">{0,1}</minimum>
      <maximum exclusive="">{0,1}</maximum>
    </bounds>

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 |
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).

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 |
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).

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 |
Properties |
content | complex
minOccurs | 0
maxOccurs | unbounded
Model | code , codeExplanation
Children | code, codeExplanation
Instance |
    <missingValueCode>
      <code>{1,1}</code>
      <codeExplanation>{1,1}</codeExplanation>
    </missingValueCode>

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.

    example: -9999

    example: -1

    example: N/A

    example: MISSING
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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.

    example: Sensor down time.

    example: Technician error.
Diagram |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Type | Accuracy
Properties |
content | complex
minOccurs | 0
Model | attributeAccuracyReport , quantitativeAttributeAccuracyAssessment*
Children | attributeAccuracyReport, quantitativeAttributeAccuracyAssessment
Instance |
    <accuracy>
      <attributeAccuracyReport>{1,1}</attributeAccuracyReport>
      <quantitativeAttributeAccuracyAssessment>{0,unbounded}</quantitativeAttributeAccuracyAssessment>
    </accuracy>

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 |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Properties |
content | complex
minOccurs | 0
maxOccurs | unbounded
Model | attributeAccuracyValue , attributeAccuracyExplanation
Children | attributeAccuracyExplanation, attributeAccuracyValue
Instance |
    <quantitativeAttributeAccuracyAssessment>
      <attributeAccuracyValue>{1,1}</attributeAccuracyValue>
      <attributeAccuracyExplanation>{1,1}</attributeAccuracyExplanation>
    </quantitativeAttributeAccuracyAssessment>

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 |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Type | NonEmptyStringType
Properties |
content | simple
Facets |
minLength | 1 |
pattern | [\s]*[\S][\s\S]* |

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 |
Type | Coverage
Properties |
content | complex
minOccurs | 0
Model | geographicCoverage | temporalCoverage | taxonomicCoverage | (references)
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 |

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 |
Type | MethodsType
Properties |
content | complex
minOccurs | 0
Model | methodStep+ , sampling{0,1} , qualityControl*
Children | methodStep, qualityControl, sampling
Instance |
    <methods>
      <methodStep>{1,unbounded}</methodStep>
      <sampling>{0,1}</sampling>
      <qualityControl>{0,unbounded}</qualityControl>
    </methods>

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 |
Type | SemanticAnnotation
Properties |
content | complex
minOccurs | 0
maxOccurs | unbounded
Model | propertyURI , valueURI
Children | propertyURI, valueURI
Instance |
    <annotation id="" scope="document" system="">
      <propertyURI label="">{1,1}</propertyURI>
      <valueURI label="">{1,1}</valueURI>
    </annotation>
Attributes |
QName | Type | Default | Use |
--- | --- | --- | --- | ---
id | IDType |  | optional |
scope | ScopeType | document | optional |
system | SystemType |  | optional |

Element attribute

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: Attribute

    summary: Characteristics of a 'field' or 'variable' in a data
            entity (ie. dataTable).

    description: The content model for attribute is a CHOICE between
            "references" and all of the elements that let you describe the
            attribute (e.g., attributeName, attributeDefinition, precision). The
            attribute element allows a user to document the characteristics that
            describe a 'field' or 'variable' in a data entity (e.g. dataTable).
            Complete attribute descriptions are perhaps the most important aspect
            to making data understandable to others. An attribute element describes
            a single attribute or an attribute element can contain a reference
            to an attribute defined elsewhere. Using a reference means that the
            referenced attribute is (semantically) identical, not just in name
            but identical in its complete description. For example, if attribute
            "measurement1" in dataTable "survey1" has a precision of 0.1 and
            you are documenting dataTable survey2 which has an attribute called
            "measurement1" but the survey2's measurement1 has a precision of
            0.001 then these are different attributes and must be described
            separately.
Diagram |
Type | AttributeType
Properties |
content | complex
Model | (attributeName , attributeLabel* , attributeDefinition , storageType* , measurementScale , missingValueCode* , accuracy{0,1} , coverage{0,1} , methods{0,1} , annotation*) | (references)
Children | accuracy, annotation, attributeDefinition, attributeLabel, attributeName, coverage, measurementScale, methods, missingValueCode, references, storageType
Instance |
    <attribute id="" scope="document" system="" xmlns="https://eml.ecoinformatics.org/attribute-2.2.0">
      <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 id="" scope="document" system="">{0,unbounded}</annotation>
      <references system="">{1,1}</references>
    </attribute>
Attributes |
QName | Type | Default | Use |
--- | --- | --- | --- | ---
id | IDType |  | optional |
scope | ScopeType | document | optional |
system | SystemType |  | optional |

Element attributeList

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: Attribute list

    summary: A list of attributes

    description: This is the root element of the eml-attribute module.
            It is mainly used for testing, but can also be used for creating
            stand-alone eml-attribute modules where a list of attributes is
            needed.
Diagram |
Type | AttributeListType
Properties |
content | complex
Model | attribute+ | (references)
Children | attribute, references
Instance |
    <attributeList id="" xmlns="https://eml.ecoinformatics.org/attribute-2.2.0">
      <attribute id="" scope="document" system="">{1,unbounded}</attribute>
      <references system="">{1,1}</references>
    </attributeList>
Attributes |
QName | Type | Use |
--- | --- | --- | ---
id | IDType | optional |

Complex Type AttributeListType

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: Attribute List

    summary: List of attributes

    description: This complexType defines the structure of the
            attributeList element. The content model is a choice between one or
            more attribute elements, and references. References links to an
            attribute list defined elsewhere.
Diagram |
Model | attribute+ | (references)
Children | attribute, references
Attributes |
QName | Type | Use |
--- | --- | --- | ---
id | IDType | optional |

Complex Type AttributeType

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: Attribute Type

    summary:
            Type definition for the content of an attribute (variable)
            that can be part of an entity.

    description:  Type definition for the content of an
            attribute (variable) that can be part of an entity.
Diagram |
Model | (attributeName , attributeLabel* , attributeDefinition , storageType* , measurementScale , missingValueCode* , accuracy{0,1} , coverage{0,1} , methods{0,1} , annotation*) | (references)
Children | accuracy, annotation, attributeDefinition, attributeLabel, attributeName, coverage, measurementScale, methods, missingValueCode, references, storageType
Attributes |
QName | Type | Default | Use |
--- | --- | --- | --- | ---
id | IDType |  | optional |
scope | ScopeType | document | optional |
system | SystemType |  | optional |

Complex Type NonNumericDomainType

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: Non-numeric domain

    summary:

    description: The non-numeric domain field describes the domain
            of the attribute being documented.  It can describe two
            different types of domains: enumerated and text.  Enumerated
            domains are lists of values that are explicitly provided as
            legitimate values.  Only values from that list should occur
            in the attribute.  They are often used for response codes
            such as "HIGH" and "LOW".  Text domains are used for attributes
            that allow more free-form text fields, but still permit some
            specification of the value-space through pattern matching.  A
            text domain is usually used for comment and notes attributes,
            and other character attributes that don't have a precise set of
            constrained values. This is an important field for post processing
            and error checking of the dataset. It represents a formal
            specification of the value space for the attribute, and so there
            should never be a value for the attribute that falls outside of
            the set of values prescribed by the domain.
Diagram |
Model | enumeratedDomain | textDomain | (references)
Children | enumeratedDomain, references, textDomain
Attributes |
QName | Type | Use |
--- | --- | --- | ---
id | IDType | optional |

Complex Type UnitType

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: Unit of measurement

    summary: Unit of measurement for data in the
            field

    description: This field identifies the unit of measurement
            for this attribute. It is a choice of either a standard unit,
            or a custom unit. If it is a custom unit,
            the definition of the unit must be provided in the document using
            the STMML syntax, and the name provided in the customUnit element must
            reference the id of its associated STMML definition precisely. For
            further information on STMML (http://www.xml-cml.org/stmml/) or
            see stmml.xsd which is included with the EML 2.0 distribution for
            details.
Diagram |
Model | standardUnit | customUnit
Children | customUnit, standardUnit

Complex Type PrecisionType

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: Precision

    summary: The precision of the measurement.

    description: Precision indicates how close together or how
            repeatable measurements are.  A precise measuring instrument will give
            very nearly the same result each time it is used. This means that
            someone interpreting the data should expect that if a measurement were
            repeated, most measured values would fall within the interval specified
            by the precision. The value of precision should be expressed in the
            same unit as the measurement. For example, for an attribute with unit
            "meter", a precision of "0.1" would be interpreted to mean that most
            repeat measurements would fall within an interval of 1/10th of a meter.

    example: 0.1

    example: 0.5

    example: 1
Diagram |
Type | extension of xs:float

Complex Type NumericDomainType

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: Numeric Domain

    summary: Numeric domain of attribute specifying allowed
            values.

    description: The numericDomain element specifies 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). The information in
            numericDomain and in precision together constitute
            sufficient information to decide upon an appropriate
            system specific data type for representing a particular
            attribute. For example, an attribute with a numeric domain
            from 0-50,000 and a precision of 1 could be represented in
            the C language using a 'long' value, but if the precision is
            changed to '0.5' then a 'float' type would be needed.
Diagram |
Model | (numberType , bounds*) | (references)
Children | bounds, numberType, references
Attributes |
QName | Type | Use |
--- | --- | --- | ---
id | IDType | optional |

Simple Type NumberType

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    description: This is the enumeration for the allowed values
    of the element numberType.
Diagram |
Type | restriction of xs:string
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).

    example: 4.1516

    example: 2.5

    example: .3333333...

Complex Type DateTimeDomainType

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: DateTime Domain

    summary: DateTime domain of attribute specifying allowed
            values.

    description: The DateTimeDomain specifies the
            minimum and maximum values 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). The domain expressions should
            be in the same dateTime format as is used in the "formatString"
            description for the attribute.  For example, if the format
            string is "YYYY-MM-DD", then a valid minimum in the domain
            would be "2001-05-29".  The "bounds" element is optional, and
            if it is missing then any legitimate value from the Gregorian
            calendar system is allowed in the attribute as long as its
            representation matches its corresponding formatString.
Diagram |
Model | (bounds*) | (references)
Children | bounds, references
Attributes |
QName | Type | Use |
--- | --- | --- | ---
id | IDType | optional |

Complex Type Accuracy

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Diagram |
Model | attributeAccuracyReport , quantitativeAttributeAccuracyAssessment*
Children | attributeAccuracyReport, quantitativeAttributeAccuracyAssessment

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.

    example:
                          http://www.w3.org/2001/XMLSchema-datatypes

    example: java

    example: C

    example: Oracle 8i
Type | xs:string
Properties |
use | optional
default | http://www.w3.org/2001/XMLSchema-datatypes

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

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 |

Attribute NonNumericDomainType / @id

Namespace | No namespace
Type | IDType
Properties |
use | optional

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

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

Attribute NumericDomainType / @id

Namespace | No namespace
Type | IDType
Properties |
use | optional

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

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

Attribute DateTimeDomainType / @id

Namespace | No namespace
Type | IDType
Properties |
use | optional

Attribute AttributeType / @id

Namespace | No namespace
Type | IDType
Properties |
use | optional

Attribute AttributeType / @system

Namespace | No namespace
Type | SystemType
Properties |
use | optional

Attribute AttributeType / @scope

Namespace | No namespace
Type | ScopeType
Properties |
use | optional
default | document
Facets |
enumeration | system |
enumeration | document |

Attribute AttributeListType / @id

Namespace | No namespace
Type | IDType
Properties |
use | optional

Element Group BoundsGroup

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: Bounds

    summary: Elements for specifying allowed
            values range.

    description: The bounds element 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).
Diagram |
Model | bounds*
Children | bounds

Element Group BoundsDateGroup

Namespace | https://eml.ecoinformatics.org/attribute-2.2.0
Annotations |
    tooltip: BoundsDateGroup

    summary: Elements for specifying allowed
            value ranges.

    description: The BoundsDateGroup specifies the
            minimum and maximum dates allowed for 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). The domain expressions should
            be in the same dateTime format as is used in the attribute's "formatString".
            For example, if the format
            string is "YYYY-MM-DD", then a valid minimum in the domain
            would be "2001-05-29".  The "bounds" element is optional, and
            if it is missing then any legitimate value from the Gregorian
            calendar system is allowed in the attribute as long as its
            representation matches its corresponding formatString.
Diagram |
Model | bounds*
Children | bounds