Module Documentation: eml-resource
The eml-resource module contains general information that describes dataset resources, literature resources, collection resources, and software resources. It is intended to provide overview information about the resource, including title, abstract, keywords, contacts, and the links to associated metadata for the given resource.

Element Definitions:

resource
Content of this field: Description of this field:
Elements: Required?: How many:
A choice of (
datasetOptionalMultiple Times
OR
literatureOptionalMultiple Times
OR
softwareOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Resource type
Summary:
The class of resource being documented.
Description:
The 'resource' element is the generic class for all types of resources. A user may choose to document a resource according to one of the following subtypes, which are presented as a choice: dataset, literature, collection, or software.
Example:
Please see the examples for each subelement of the 'Resource' type.
Lineage:
The 'Resource' type was introduced into EML 2.0.
dataset
Content of this field: Description of this field:

Derived from: ResourceBase (by xs:extension)

Elements: Required?: How many:
A sequence of (
temporalCoverageOptionalMultiple Times
geographicCoverageOptionalMultiple Times
geoFormOptionalOnce
)
Attributes: Required?: Default Value:

Tooltip:
Dataset type
Summary:
The container for fields describing a dataset resource.
Description:
The dataset element defines extend the ResourceBase complexType in order to provide information that is specific to describing a set of data. Therefore, dataset elements contain all of the general resource elements, but also specific dataset elements.
Example:
Please see the examples for each subelement.
Lineage:
This element was introduced in EML 2.0, and is derived from the eml-dataset module in EML 1.4.
temporalCoverage
Content of this field: Description of this field:
Type: TemporalCoverage
Attributes: Required?: Default Value:

Tooltip:
Temporal coverage
Summary:
Information about the temporal extent of the resource.
Description:
This element describes the temporal extent of the resource expressed in a start date and a stop date.
Example:

Lineage:
The temporalCoverage element was introduced into EML 1.4.
geographicCoverage
Content of this field: Description of this field:
Type: GeographicCoverage
Attributes: Required?: Default Value:

Tooltip:
Geographic coverage
Summary:
Description of the geographic area which data are collected in the entity.
Description:
This element describes the geographic area which data are collected in the entity: descriptive paragraph of text or Cartesian coordinates of the area.
Example:

Lineage:
The geographicCoverage element was introduced into EML 1.4.
geoForm
Content of this field: Description of this field:
Type: GeoForm
Attributes: Required?: Default Value:

Tooltip:
Geospatial representation
Summary:
The mode in which the geospatial data are represented.
Description:
This field provides the 'geospatial representation format' of the resource being described. The possible values are derived from a list that include such formats as 'atlas', 'map', and 'globe'. The list has also been extended to include other datatype formats such as 'spreadsheet', 'document', or 'video'. The complete list of values are provided in the example.
Example:
Possible values include: "atlas", "audio", "diagram", "document", "globe", "map", "model", "multimediaPresentation", "profile", "rasterDigitalData", "remoteSensingImage", "section", "spreadsheet", "tabularDigitalData", "vectorDigitalData", "video", and "view".
Lineage:
This element was derived from elements described in FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999)
literature
Content of this field: Description of this field:
Type: LitCitation
Attributes: Required?: Default Value:
software
Content of this field: Description of this field:

Derived from: ResourceBase (by xs:extension)

Elements: Required?: How many:
A sequence of (
versionNumberOptionalMultiple Times
sourceModuleOptionalMultiple Times
binaryFileOptionalMultiple Times
locationOptionalMultiple Times
programmingLanguageOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Software
Summary:
General information about a software resource.
Description:
the 'software' element contains general information about a software resource that is being documented. This is field is intended to give information for software tools that are needed to interpret a dataset, software that was written to process a resource, or software as a resource in itself. It includes the version, the programming language, and the location of the software, along with the source code information or binary file information. The information provided in the subelements are specific to software resources and extend the Resource type.
Example:
Please see the examples for each subelement of the 'Software' type.
Lineage:
The 'software' element was introduced into EML 2.0, however it was derived from the eml-software module in EML 1.4.
versionNumber
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Version number
Summary:
The version number of the software resource.
Description:
This field provides the version number of the software that is being documented. The version number may be a vendor-assigned number, or it may be a version tag from a software versioning system such as CVS (Concurrent Versioning System).
Example:
8.2.1 or WEBSITE_2_BETA_1
Lineage:
This field was introduced into EML 2.0 beta 1, and is derived from the eml-software module in EML 1.4.
sourceModule
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Source module
Summary:
The name of the source code module.
Description:
This field provides the name of the source code module that contains the non-binary source.
Example:
eml-2.0b1.tgz
Lineage:
This field was introduced into EML 2.0 beta 1, and is derived from the eml-software module in EML 1.4.
binaryFile
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Binary file
Summary:
The name of the binary file for the software.
Description:
This field provides the name of the compiled binary file for the software distribution.
Example:
morpho-macintosh-1.2.bin
Lineage:
This field was introduced into EML 2.0 beta 1, and is derived from the eml-software module in EML 1.4.
location
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Software location
Summary:
The Internet location of the software resource.
Description:
This field provides the Uniform Resource Locator of where the software resource is available on the Internet.
Example:
http://knb.ecoinformatics.org/software/metacat/
Lineage:
This field was introduced into EML 2.0 beta 1, and is derived from the eml-software module in EML 1.4.
programmingLanguage
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Programming Language
Summary:
The programming language for the software resource.
Description:
This field provides the name and version of the programming language in which the software resource was written.
Example:
PERL version 5.005_03
Lineage:
This field was introduced into EML 2.0 beta 1, and is derived from the eml-software module in EML 1.4.
ISBN
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
International Standard Book Number
Summary:
The unique Internation Standard Book Number
Description:
The ISBN, or International Standard Book Number that has been assigned to this literature resource.
Example:
ISBN 1-861003-11-0
Lineage:
This field was introduced into EML 2.0 and was derived from the ISO 19115.3 standard (iso-geo-md-2000June-draft) and the ISO Standard 2108.
ISSN
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
International Standard Serial Number
Summary:
The unique Internation Standard Serial Number
Description:
The ISSN, or International Standard Serial Number that has been assigned to this literature resource.
Example:
ISSN 1234-5679
Lineage:
This field was introduced into EML 2.0 and was derived from the ISO 19115.3 standard (iso-geo-md-2000June-draft) and the ISO 3297-1975; ANSI Z39.9-1979 standard.
editor
Content of this field: Description of this field:
Type: rp:Person
Attributes: Required?: Default Value:

Tooltip:
Editor
Summary:
The name of the editor of the literature resource.
Description:
This field provides a container for the information that describes the editor of the literature resource. The editor may be a person or organization or a role within an organization.
Example:
Please see the examples within the subelements.
Lineage:
This field was introduced into EML 2.0 beta 1, and was derived from the FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999)
edition
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Edition
Summary:
The edition of the literature resource.
Description:
The edition that has been assigned to a literature resource by its publisher.
Example:
2nd Edition
Lineage:
This field was introduced into EML 2.0 beta 1, and was derived from the FGDC-STD-001.1-1999 (nbii-fgdc-std-001.1-1999) and ISO 19115.3 (iso-geo-md-2000June-draft) standards.
volume
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Volume
Summary:
The volume number of the resource.
Description:
The volume number that has been assigned to a resource by its publisher.
Example:
Volume 7
Lineage:
This field was introduced into EML 2.0 beta 1
identifier
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
systemoptional

Tooltip:
Unique identifier
Summary:
The unique identifier of this metadata file or object.
Description:
The identifier field provides a unique identifier for this metadata documentation. It will most likely be part of a sequence of numbers or letters that are meaningful in a larger context, such as a metadata catalog. That larger system can be identified in the "system" attribute. Multiple identifiers can be listed corresponding to different catalog systems.
Example:
<identifier system="metacat">nceas.3.2</identifier>
Lineage:
The 'identifier' field is derived from the eml-dataset meta_file_id filed in EML 1.4.
shortName
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Short Name
Summary:
A short name that describes the resource, sometimes a filename.
Description:
The 'shortName' field provides a concise name that describes the resource that is being documented. It is the appropriate place to store a filename associated with other storage systems.
Example:
vernal-data-1999
Lineage:
This element was derived from elements described in the ISO 19115.3 standard (iso-geo-md-2000June-draft).
title
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Title
Summary:
A brief description of the resource, providing enough detail to differentiate it from other similar resources.
Description:
The 'title' field provides a description of the resource that is being documented that is long enough to differentiate it from other similar resources.
Example:
Vernal pool amphibian density data, Isla Vista, 1990-1996.
Lineage:
This element was derived from elements described in the ISO 19115.3 standard (iso-geo-md-2000June-draft).
alternateTitle
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:

Summary:
A secondary short title that describes the resource.
Description:
The 'alternateTitle' field provides a concise name or other language name that describes the resource that is being documented.
Example:
They're not just mud puddles: fragile ecosystems in Isla Vista
Lineage:
This element was derived from elements described in the ISO 19115.3 standard (iso-geo-md-2000June-draft).
originator
Content of this field: Description of this field:
Type: rp:ResponsibleParty
Attributes: Required?: Default Value:

Tooltip:
Originator
Summary:
A person or organization asociated with this resource.
Description:
The 'originator' element provides the full name of the person, organization, or role associated with the resource. Typically, the originator role code is set to "owner" to indicate the list of parties who "own" the resource, but other roles such as "principal investigator", "author", and "editor" are provided.
Example:
Please see the examples within the sub fields for the responsible party.
Lineage:
This element was derived from elements described in the FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999)
pubDate
Content of this field: Description of this field:
Type: xs:date
Attributes: Required?: Default Value:

Tooltip:
Publication date
Summary:
The publication date of the resource.
Description:
The 'pubDate' field represents the date that the resource was published. The format should be represented as: CCYY-MM-DD, which denotes the full year, month, and day.
Example:
1999-10-26
Lineage:
This element was derived from elements described in the FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999) The type 'xs:date' folllows the date standard described in ISO 8601.
pubPlace
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Publication place
Summary:
The location that the resource was published.
Description:
the 'pubPlace' field is the location where the resource was published, which may be different from where the resource was created.
Example:
San Francisco, CA, USA
Lineage:
This element was derived from elements described in the FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999)
series
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Series
Summary:
The series from which the resource came.
Description:
This field describes the series of resources that include the resource being described. For example, a volume of a journal may be part of a series of the journal for a particular year.
Example:
Volume 20
Lineage:
This element was derived from elements described in the FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999) and ISO 19115.3 standard (iso-geo-md-2000June-draft)
abstract
Content of this field: Description of this field:
Type: Abstract
Attributes: Required?: Default Value:

Tooltip:
Abstract
Summary:
A brief overview of the resource.
Description:
This field provides a container for one or more paragraph fields that give a brief overview of the resource that is being documented.
Example:
Please see the examples for the subfields contained within this field.
Lineage:
This element was derived from elements described in the FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999)
keywordInfo
Content of this field: Description of this field:
Type: KeywordInfo
Attributes: Required?: Default Value:

Tooltip:
Keyword information
Summary:
Keyword information that describes the resource.
Description:
The 'keywordInfo' element is a container for the 'keyword' and 'keywordThesaurus' fields.
Example:
Please see the examples for the subfields contained within this field.
Lineage:
This element was derived from elements described in the FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999)
URL
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Uniform resource locator
Summary:
The Uniform Resource Locator referring to the resource.
Description:
The 'URL' field provides the Internet address that references a particular resource. It should conform to standard URL syntax, giving the connection protocol, followed by '://', followed by the name of the machine to connect to, followed by the resource location on the machine.
Example:
http://data.nceas.ucsb.edu/datafile.txt
Lineage:
This element was derived from elements described in the FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999)
additionalInfo
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Additional Information
Summary:
Any extra information pertitent to the resource.
Description:
This field provides any information that is not characterized by the other resource metadata fields.
Example:
Copyright 2001, Robert Warner
Lineage:
This element was derived from elements described in the FGDC-STD-001.1-1999 standard (nbii-fgdc-std-001.1-1999)
paragraph
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Abstract paragraph
Summary:
The paragraph field for the text in an abstract.
Description:
This field is intended for the text of an abstract that gives a brief overview of the resource. there may be multiple paragragh field within the abstract.
Example:
The major unanswered question in marine ecology is the degree of connectedness between local populations. Put another way, what proportion of young arriving into a local population are products of local production? What is the source of recruits for any local population, and where do the young produced in a local population go? The answers to these questions are unknown for any widespread species with a pelagic dispersal phase. Proper marine management depends on knowledge in this area: the efficacy of any reserve design, for example, is highly dependent on the degree to which it is dependent on other populations for recruitment, and the degree to which it supplies other areas.
Lineage:
This field was introduced into EML 2.0, and was derived from EML 1.3.
keyword
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Keyword
Summary:
A keyword that describes the resource.
Description:
This field names a keyword or keyphrase that concisely describes the resource or is related to the resource.
Example:
biodiversity
Lineage:
This field was introduced into EML 2.0 beta 1, and was derived from EML 1.3. and the ISO 19115.3 standard (iso-geo-md-2000June-draft).
keywordType
Content of this field: Description of this field:
Type: KeyTypCode
Attributes: Required?: Default Value:

Tooltip:
Keyword type
Summary:
The type of each keyword.
Description:
This field classifies the keyword that has been provided from a list of pre-determined categories. The possible types are listed in the example.
Example:
"discipline","place","stratum","temporal","thematic", or "taxonomic"
Lineage:
This field was introduced into EML 2.0, and was derived from EML 1.3. and the ISO 19115.3 standard(iso-geo-md-2000June-draft).
keywordThesaurus
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Keyword thesaurus
Summary:
The name of a thesaurus from which the keyword is derived.
Description:
this field provides the name of the official keyword thesaurus from which keyword was derived. The keyword thesauri are usually discipline specific.
Example:
IRIS keyword thesaurus
Lineage:
This field was introduced into EML 2.0, and was derived from EML 1.3. and the ISO 19115.3 standard(iso-geo-md-2000June-draft).
startDate
Content of this field: Description of this field:
Type: DateTime
Attributes: Required?: Default Value:

Tooltip:
Start date
Summary:
Start date of the temporal coverage.
Description:
This element specifies the start date of the temporal coverage.
Example:

Lineage:
The startDate element was introduced into EML 1.4.
stopDate
Content of this field: Description of this field:
Type: DateTime
Attributes: Required?: Default Value:

Tooltip:
Stop date
Summary:
Stop date of the temporal coverage.
Description:
This element specifies the stop date of the temporal coverage.
Example:

Lineage:
The stopDate element was introduced into EML 1.4.
year
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
month
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
day
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
hour
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
minute
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
second
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
secondFraction
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
timeZoneDesignator
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
paragraph
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:

Tooltip:
Paragraph of text
Summary:
Paragraph of text describing the geographic area which data are collected in the entity.
Description:
This element describes the geographic area which data are collected in the entity.
Example:

Lineage:
The paragraph element was introduced into EML 1.4.
coordinates
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
latitudeRequiredOnce
longitudeRequiredOnce
)
Attributes: Required?: Default Value:

Tooltip:
Cartesian coordinates
Summary:
Cartesian coordinates for the geographic area.
Description:
This element specifies the Cartesian coordinates: latitude and longitude of the geographic area covered by the entity's data.
Example:

Lineage:
The coordinates element was introduced into EML 1.4.
latitude
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
directionrequired

Tooltip:
latitude coordinates
Summary:
latitude coordinates for the geographic area.
Description:
This element specifies the latitude coordinates of the geographic area covered by the entity's data. The element's attribute "direction" should specify the coordinate's direction to "north" or "south".
Example:

Lineage:
The latitude element was introduced into EML 1.4.
longitude
Content of this field: Description of this field:
Type: xs:string
Attributes: Required?: Default Value:
directionrequired

Tooltip:
Longitude coordinates
Summary:
Longitude coordinates for the geographic area.
Description:
This element specifies the longitude coordinates of the geographic area covered by the entity's data. The element's attribute "direction" should specify the coordinate's direction to "east" or "west".
Example:

Lineage:
The longitude element was introduced into EML 1.4.

Attribute Definitions:

system

Type: xs:string

Use: optional


Tooltip:
Catalog system
Summary:
The catalog system in which this identifier is used.
Description:
This element gives the name of the catalog system in which this identifier is used. It is useful to determine the scope of the identifier, and to determine the semantics of the various subparts of the identifier. Unresolved issue: can or should this be a URI/URL pointing to the catalog system, or just the name?
Example:
<identifier system="metacat">nceas.3.2</identifier>
Lineage:
New to EML 2.0.
direction

Use: required


Tooltip:
Attribute of latitude element
Summary:
Specification of latitude direction.
Description:
This attribute specifies latitude direction of the collected data. The attribute assertion is required.
Example:
The valid attribute values are "north" and "south".
Lineage:
This attribute was introduced into EML 1.4.
direction

Use: required


Tooltip:
Attribute of longitude element
Summary:
Specification of longitude direction.
Description:
This attribute specifies longitude direction of the collected data. The attribute assertion is required.
Example:
The valid attribute values are "east" or "west".
Lineage:
This attribute was introduced into EML 1.4.

Complex Type Definitions:

LitCitation
Content of this field: Description of this field:

Derived from: ResourceBase (by xs:extension)

Derived from: ResourceBase (by xs:extension)

Elements: Required?: How many:
A sequence of (
ISBNOptionalOnce
ISSNOptionalOnce
editorOptionalMultiple Times
editionOptionalOnce
volumeOptionalOnce
)
Attributes: Required?: Default Value:

Tooltip:
Literature Citation
Summary:
Information describing a literature resource.
Description:
The 'LitCitation' type contains general information about a literature resource that is being documented, or a piece of literature that is being cited in support of a given resource, such as a dataset. It contains subelements that are specific to a literature resource such as a book, a journal article, a thesis, etc. It extends the generic resource elements with literature specific fields.
Example:
Please see the examples within the subelements for this type.
Lineage:
This field was introduced in EML 2.0.
ResourceBase
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
identifierRequiredMultiple Times
shortNameOptionalOnce
titleRequiredOnce
alternateTitleOptionalOnce
originatorRequiredMultiple Times
pubDateOptionalOnce
pubPlaceOptionalOnce
seriesOptionalOnce
abstractOptionalOnce
keywordInfoOptionalMultiple Times
URLOptionalMultiple Times
additionalInfoOptionalOnce
)
Attributes: Required?: Default Value:

Tooltip:
Resource Base
Summary:
Generic information about every resource that is being described.
Description:
The 'ResourceBase' complexType contains information that is inherited by each resource type that is being documented. The subelements with the resource base are common to al resources.
Example:
Please see the examples within the sub-elements of the 'ResourceBase' complexType.
Lineage:
The 'ResourceBase' element was introduced into EML 2.0 beta 1.
Abstract
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
paragraphRequiredMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Abstract type
Summary:
Information that provides an overview of the resource.
Description:
The 'Abstract' type provides paragraph containers that are used to give a brief overview of the resource in abstract format.
Example:
Please see the examples within the sub elements of this type.
Lineage:
This field was introduced into EML 2.0 beta 1, and was derived from EML 1.4.
KeywordInfo
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
keywordRequiredOnce
keywordTypeOptionalOnce
keywordThesaurusOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Keyword Information
Summary:
Keyword information that describes a resource.
Description:
The 'KeywordInfo' type provides a container for information relating to keywords, including the type of the keyword and the thesaurus from which the keyword was derived.
Example:
Please see the examples within the sub elements of this type.
Lineage:
This field was introduced into EML 2.0 beta 1, and was derived from EML 1.3.
TemporalCoverage
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
startDateRequiredOnce
stopDateOptionalOnce
)
Attributes: Required?: Default Value:

Tooltip:
Temporal coverage
Summary:
Temporal coverage descriptor.
Description:
This element specifies temporal coverage by start and stop date.
Example:

Lineage:
The TemporalCoverage complex type was introduced into EML 1.4.
DateTime
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
yearOptionalOnce
monthOptionalOnce
dayOptionalOnce
hourOptionalOnce
minuteOptionalOnce
secondOptionalOnce
secondFractionOptionalOnce
timeZoneDesignatorOptionalOnce
)
Attributes: Required?: Default Value:

Tooltip:
Date and time
Summary:
Date and time as designated in ISO 8601
Description:
This complex type specifies date and time as designated in ISO 8601. We can consider to drop this type, but to use XML Schema's timeDuration instead.
Example:

Lineage:
The DateTime complex type was introduced into EML 1.4, and is based on the ISO 8601 time standard.
GeographicCoverage
Content of this field: Description of this field:
Elements: Required?: How many:
A sequence of (
paragraphOptionalMultiple Times
coordinatesOptionalMultiple Times
)
Attributes: Required?: Default Value:

Tooltip:
Geographic coverage
Summary:
Geographic coverage information.
Description:
Geographic Coverage is a container for spatial information about a a project, a resource, or an entity within a resource.
Example:

Lineage:
The GeographicCoverage complex type was derived from the eml-entity module in EML 1.4.

Simple Type Definitions:

Derived from: xs:string (by xs:restriction)

Allowed values:

  • north
  • south

Derived from: xs:string (by xs:restriction)

Allowed values:

  • east
  • west

GeoForm

Derived from: xs:string (by xs:restriction)

Allowed values:

  • atlas
  • audio
  • diagram
  • document
  • globe
  • map
  • model
  • multimediaPresentation
  • profile
  • rasterDigitalData
  • remoteSensingImage
  • section
  • spreadsheet
  • tabularDigitalData
  • vectorDigitalData
  • video
  • view


Tooltip:
Geospatial format type
Summary:
The list of geospatial representation formats
Description:
This field provides a restricted list of resource formats that describe a dataset.
Example:
atlas
Lineage:

KeyTypCode

Derived from: xs:string (by xs:restriction)

Allowed values:

  • discipline
  • place
  • stratum
  • temporal
  • thematic
  • taxonomic


Tooltip:
Keyword type codes
Summary:
The list of keyword categories
Description:
This field provides a restricted list of categories that a keyword may fall under.
Example:
place
Lineage:

Web Contact: jones@nceas.ucsb.edu