Element Definitions:
|
identifier |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
Attributes:
|
Required?:
|
Default Value:
|
|
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:
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. Multiple
titles may be provided, particularly when trying to express
the title in more than one language (use the "xml:lang"
attribute to indicate the language if not English/en).
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).
|
originator |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Originator
Summary:
A person or organization asociated with this resource.
Description:
The 'originator' element provides the full name of the
person, organization, or position associated with the resource.
Typically, the originator role is set to "owner"
to indicate the list of parties who "own" the resource,
but other roles such as "principal investigator", "author",
and "editor" are provided.
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:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
paragraph | Optional | Multiple Times |
) |
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)
|
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 one or more paragraphs 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.
|
keywordSet |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
keyword | Optional | Multiple Times |
keywordThesaurus | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Keyword information
Summary:
Keyword information that describes the resource.
Description:
The 'keywordSet' element is a container for the 'keyword' and
'keywordThesaurus' fields. Each keywordSet field can contain
one or more keywords and a name of a thesaurus for the set of
keywords. Each keyword field should contain one and only one
keyword (i.e., keywords should not be separated by commas or
other delimiters).
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)
|
keyword |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Keyword
Summary:
A single keyword that describes the resource.
Description:
This field names a keyword or keyphrase that concisely
describes the resource or is related to the resource.
Each keyword field should contain one and only one
keyword (i.e., keywords should not be separated by commas or
other delimiters).
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).
|
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).
|
additionalInfo |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
paragraph | Optional | Multiple Times |
) |
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:
Paragraph
Summary:
The paragraph field for the additional text.
Description:
This field is intended for the text
that gives additional information about the resource.
There may be one or more paragraphs.
Example:
Copyright 2001, Robert Warner
Lineage:
This field was introduced into EML 2.0.
|
rights |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
paragraph | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Rights
Summary:
Rights regarding usage and licensing of this resource.
Description:
Typically, a Rights element will contain a rights management statement
for the resource, or reference a service providing such information.
Rights information often encompasses Intellectual Property Rights (IPR),
Copyright, and various Property Rights. In the case of a data set,
rights might incude requirements for use, requirements for attribution,
or other requirements the owner would like to impose.
Example:
Copyright 2001 Regents of the University of California Santa Barbara.
Free for use by all individulas provided that the owners are acknowledged
in any use or publication.
Lineage:
Introduced in EML 2.0, derived from Dublin Core Element Set 1.1.
|
paragraph |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Paragraph
Summary:
The paragraph field for the additional text.
Description:
This field is intended for the text
that gives additional information about the resource.
There may be one or more paragraphs.
Example:
Copyright 2001, Robert Warner
Lineage:
This field was introduced into EML 2.0.
|
onlineURL |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Download site URL
Summary:
A URL (Uniform Resource Locator) from which this resource can be downloaded
Description:
A URL (Uniform Resource Locator) from which this resource can be downloaded.
This includes any information needed to access this site, such as
connection information.
Example:
http://data.org/getdata?id=98332
Lineage:
ISO CD 19115.3, Geographic information - Metadata
|
offlineMedium |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
medName | Optional | Multiple Times |
medDensity | Optional | Multiple Times |
medDensityUnits | Optional | Multiple Times |
medVol | Optional | Multiple Times |
medFormat | Optional | Multiple Times |
medNote | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
medium of the resource
Summary:
the medium on which this resource is distributed, either digitally or as hardcopy
Description:
the medium on which this resource is distributed digitally, such as 3.5"
floppy disk, or various tape media types, or 'hardcopy'
Example:
CD-ROM, 3.5 in. floppy disk, Zip disk
Lineage:
ISO CD 19115.3, Geographic information - Metadata
|
medName |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Medium name
Summary:
Name of the medium that for this resource distribution
Description:
Name of the medium on which this resource is distributed.
Can be various digital media such as tapes and disks, or
printed media which can collectively be termed 'hardcopy'.
Example:
Tape, 3.5 inch Floppy Disk, hardcopy
Lineage:
ISO CD 19115.3,
Geographic information - Metadata
|
medDensity |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
density of the digital medium
Summary:
the density of the digital medium if this is
relevant.
Description:
the density of the digital medium if this is
relevant. Used mainly for floppy disks
or tape.
Example:
High Density (HD), Double Density (DD)
Lineage:
ISO CD 19115.3,
Geographic information - Metadata
|
medDensityUnits |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
units of a numerical density
Summary:
a numerical density's units
Description:
if a density is given numerically, the units
should be given here.
Example:
B/cm
Lineage:
ISO CD 19115.3,
Geographic information - Metadata
|
medVol |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
storage volume
Summary:
total volume of the storage medium
Description:
the total volume of the storage medium on
which this resource is shipped.
Example:
650 MB
Lineage:
ISO CD 19115.3,
Geographic information - Metadata
|
medFormat |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
medium format
Summary:
format of the medium on which the resource is
shipped.
Description:
the file system format of the medium on
which the resource is shipped
Example:
NTFS, FAT32, EXT2, QIK80
Lineage:
ISO CD 19115.3,
Geographic information - Metadata
|
medNote |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
note about the media
Summary:
note about the media
Description:
any additional pertitant information about the
media
Example:
Lineage:
ISO CD 19115.3,
Geographic information - Metadata
|
triple |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
subject | Optional | Multiple Times |
relationship | Optional | Multiple Times |
object | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Component list
Summary:
The definition of a relationship between component objects
in a resource package
Description:
The triple element lists all relationships in the resource,
which effectively enumerates the components of the resource.
The relationships are in the form of:
<subject> <relationship> <object>
A triple allows a user to define a relationship between two
objects. This relationship can also be recursive so that an
object can point back to the package of which it is a part.
In order for a package to make sense, the use of triples must be
somewhat contrained. The following guidelines should be used
when constructing a package if you wish your package to be usable
with other ecoinformatics.org software.
subject relationship object
------- ------------ ------
attribute_instance isAttributeInformationFor entity_instance
DATAFILE isDataFileFor(DATAFILE_name) dataset_instance
entity_instance isEntityInformationFor DATAFILE (or
dataset_instance
if no data file
is present)
physical_instance isPhysicalInformationFor entity_instance
access_instance isAccessControlFor any module that
these access
controls should
apply to. note
that the
access_instance
should be at
least associated
with the dataset_
instance.
project_instance isProjectInformationFor dataset_instance
protocol_instance isProtocolInformationFor dataset_instance
constraint_instance isConstraintFor entity_instance
note that
constraint
contains an
internal mechanism
for showing
the relationship
between two entities
if it is required
i.e. for a
foreign key
constraint
Note that triple relationships can also be created from
within eml-literature and eml-software since both of these
modules implement the eml-resource/resourceBase complexType.
Software and literature modules can also be linked into
an eml-dataset based package by linking them directly to the
eml-dataset.
Example:
Normal (nonrecursive):
<subject>knb.3.4</subject>
<relationship>isFileMetadataFor</relationship>
<object>knb.5</object>
Recursive:
<subject>lter.123</subject>
<relationship>isPackageMember</relationship>
<object>lter.18</object>
where object lter.18 is the identifier of the resource
in which this relationship exists.
Lineage:
Derived from the eml-dataset.dtd element called "relation" in
EML 1.4.
|
subject |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Subject element
Summary:
Subject element of the relationship.
Description:
Subject is the identifier of the metadata object or file
that is the actor in the triple.
Example:
<subject>knb.3.4</subject>
Lineage:
Subject element was introduce into EML 2.0 Proposed.
|
relationship |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Relationship type
Summary:
The type of relationship between the subject and
object of the triple
Description:
Relationship is a descriptive phrase that specifies the
how the subject of the triple is related to the object.
This is typically meant to label the type of descriptor
that a metadata file (the subject) represents for a data
file (the object). This allows one to express concepts
such as "knb.32.3 lists access control rules for knb.2.2".
Example:
<relationship>is metadata describing</relationship>
Lineage:
The relationship element was introduced in EML 2.0.
|
object |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Object element
Summary:
The object element of the relationship.
Description:
Object is the identifier of the metadata or data object
that is acted upon according to the relationship in the
triple.
Example:
<subject>knb.8.4</subject>
Lineage:
The object element was introduced in EML 2.0.
|
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:
Lineage:
New to EML 2.0.
|
keywordType |
Type: KeyTypCode
Use: optional
|
Tooltip:
Keyword type
Summary:
The type of each keyword.
Description:
This field classifies the keyword that has been
provided from a list of pre-determined categories. The
possible types are listed in the example.
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).
|
Complex Type Definitions:
|
ResourceBase |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Resource Base
Summary:
Generic information about any 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 all resources.
Example:
Please see the individual sub-fields for specific examples.
Lineage:
The 'ResourceBase' element was introduced into EML 2.0.
|
Simple Type Definitions:
|
|
Derived from: xs:string
(by xs:restriction)
Allowed values:
- place
- stratum
- temporal
- theme
|
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:
|