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

Imported schema eml-semantics.xsd

Namespace | https://eml.ecoinformatics.org/semantics-2.2.0
Annotations |
    Copyright: 2017 Regents of the University of California

        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-semantics

    moduleDescription:

                    The eml-semantics module - Semantic annotations for formalized
                    statements about EML components

    recommendedUsage: all datasets

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

Element SemanticAnnotation / propertyURI

Namespace | No namespace
Annotations |
    tooltip: Property URI

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

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

    example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-characteristics.owl#ofCharacteristic

    example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-standards.owl#usesStandard
Diagram |
Type | extension of xs:anyURI
Properties |
content | complex
minOccurs | 1
maxOccurs | 1
Attributes |
QName | Type | Use | Annotation
--- | --- | --- | ---
label | xs:string | required |
    tooltip: Property Label

    summary:
                                        A human readable representation of the controlled property.

    description:
                                        A label that provides a human readable representation of
                                        the controlled property. The label is often used to represent
                                        the controlled property when displaying annotations in
                                        software. The label is often redundant with one or more labels
                                        that are defined in the controlled vocabulary itself,
                                        but is repreated here within the EML document to make it easy
                                        for consumers to display the annotation to users.  Other
                                        labels, including labels in multiple languages, may often be
                                        accessible from within the ontology or controlled
                                        vocabularly accessible at the propertyURI.  Property definitions
                                        and relationships to other properties are also typically
                                        provided within the vocabularly accessible at the propertyURI.
                                        Software and people may be able to resolve the URI to find out
                                        the definition and retrieve additional labels and other metadata
                                        for presentation to users.

    example: has characteristic

    example: uses protocol

Element SemanticAnnotation / valueURI

Namespace | No namespace
Annotations |
    tooltip: Value URI

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

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

    example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-characteristics.owl#Mass

    example: http://ecoinformatics.org/oboe/oboe.1.2/oboe-standards.owl#Kilogram
Diagram |
Type | extension of xs:anyURI
Properties |
content | complex
minOccurs | 1
maxOccurs | 1
Attributes |
QName | Type | Use | Annotation
--- | --- | --- | ---
label | xs:string | required |
    tooltip: Value Label

    summary:
                                      A human readable representation of the controlled value.

    description:
                                      A label that provides a human readable representation of
                                      the controlled value. The label is often used to represent the
                                      controlled value when displaying annotations in software. The
                                      label is often redundant with one or more labels that are
                                      defined in the controlled vocabulary itself, but is repreated
                                      here within the EML document to make it easy for consumers to
                                      display the annotation to users.  Other labels, including
                                      labels in multiple languages, may often be accessible from
                                      within the ontology or controlled vocabularly accessible at
                                      the valueURI.  Value definitions and relationships to
                                      other terms are also typically provided within the vocabularly
                                      accessible at the valueURI.  Software and people can resolve
                                      the value URI to find out the definition of the value and
                                      retrieve additional labels and other metadata about the value
                                      for presentation to users.

    example: Mass

    example: Kilogram

    example: Net Primary Production

    example: Carbon

    example: Density

Element annotation

Namespace | https://eml.ecoinformatics.org/semantics-2.2.0
Annotations |
    tooltip: Semantic Annotation

    summary: A precisely-defined semantic statement.

    description: An annotation represents a precisely-defined semantic
                statement that is used to semantically label another structure
                within EML, such as an attribute, entity, or dataset. The annotation
                is composed of a subject (implied by the element containing
                the annotation or pointed at from within eml:additionalMetadata), a
                property that defines the relationship between the
                subject and the object of the statement, and the value of that
                property. This is equivalent to RDF Statements that consist of a
                Subject, Predicate, and Object.  More concretely, the annotation
                provides a way to state that an element within EML has a specific
                property with a specific value.

    example: For example, a common annotation would state that a containing
                'attribute' uses a measurement unit of 'grams'. This would be equivalent
                to defining a statement using the OBOE design pattern that says:
                'attribute7' 'oboe:usesStandard' 'oboe:Gram', where 'attribute7' is
                shorthand for the attribute in EML containing the annotation, and
                'oboe:' is shorthand for the full OBOE URI. In this example,
                'attribute7' is the subject represented as the id of the attribute
                containing the annotation, 'oboe:standard' is the propertyURI for the
                statement, and 'oboe:Gram' is the object of the statement.
Diagram |
Type | SemanticAnnotation
Properties |
content | complex
Model | propertyURI , valueURI
Children | propertyURI, valueURI
Instance |
    <annotation id="" scope="document" system="" xmlns="https://eml.ecoinformatics.org/semantics-2.2.0">
      <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 |

Complex Type SemanticAnnotation

Namespace | https://eml.ecoinformatics.org/semantics-2.2.0
Annotations |
    tooltip: Semantic annotation

    summary: A semantically-precise statement about an EML element.

    description:

                The SemanticAnnotation Type contains
                    elements that are used to associate a semantic statement using
                    a property and value from specific formal vocabularies with
                    other elements within EML.  For example, one
                    might want to provide the precise set of semantic statements that
                    clarify the measurement semantics of an attribute (variable)
                    within a data set, or associate a specific statement with a
                    data table or dataset.
                    The eml-semantics module defines an 'annotation' element and
                    associated type that can be used within EML resources (dataset,
                    software, etc.), EML Entities (dataTable, spatialRaster,
                    spatialVector, otherEntity), and EML Attributes.  They can also
                    be applied within the EML additionalMetadata field to label
                    arbitrary structures within EML, in which case the subject of
                    the annotation is the element listed in the describes element
                    within the additionalMetadata field.

    example: Please see the examples for the particular
            subfields.
Diagram |
Model | propertyURI , valueURI
Children | propertyURI, valueURI
Attributes |
QName | Type | Default | Use |
--- | --- | --- | --- | ---
id | IDType |  | optional |
scope | ScopeType | document | optional |
system | SystemType |  | optional |

Attribute SemanticAnnotation / propertyURI / @label

Namespace | No namespace
Annotations |
    tooltip: Property Label

    summary:
                                        A human readable representation of the controlled property.

    description:
                                        A label that provides a human readable representation of
                                        the controlled property. The label is often used to represent
                                        the controlled property when displaying annotations in
                                        software. The label is often redundant with one or more labels
                                        that are defined in the controlled vocabulary itself,
                                        but is repreated here within the EML document to make it easy
                                        for consumers to display the annotation to users.  Other
                                        labels, including labels in multiple languages, may often be
                                        accessible from within the ontology or controlled
                                        vocabularly accessible at the propertyURI.  Property definitions
                                        and relationships to other properties are also typically
                                        provided within the vocabularly accessible at the propertyURI.
                                        Software and people may be able to resolve the URI to find out
                                        the definition and retrieve additional labels and other metadata
                                        for presentation to users.

    example: has characteristic

    example: uses protocol
Type | xs:string
Properties |
use | required

Attribute SemanticAnnotation / valueURI / @label

Namespace | No namespace
Annotations |
    tooltip: Value Label

    summary:
                                      A human readable representation of the controlled value.

    description:
                                      A label that provides a human readable representation of
                                      the controlled value. The label is often used to represent the
                                      controlled value when displaying annotations in software. The
                                      label is often redundant with one or more labels that are
                                      defined in the controlled vocabulary itself, but is repreated
                                      here within the EML document to make it easy for consumers to
                                      display the annotation to users.  Other labels, including
                                      labels in multiple languages, may often be accessible from
                                      within the ontology or controlled vocabularly accessible at
                                      the valueURI.  Value definitions and relationships to
                                      other terms are also typically provided within the vocabularly
                                      accessible at the valueURI.  Software and people can resolve
                                      the value URI to find out the definition of the value and
                                      retrieve additional labels and other metadata about the value
                                      for presentation to users.

    example: Mass

    example: Kilogram

    example: Net Primary Production

    example: Carbon

    example: Density
Type | xs:string
Properties |
use | required

Attribute SemanticAnnotation / @id

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

Attribute SemanticAnnotation / @system

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

Attribute SemanticAnnotation / @scope

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