Element Definitions:
|
individualName |
Content of this field:
|
Description of this field:
|
Type: Person |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Individual Name
Summary:
The full name of the person being described
Description:
The responsible party field contains the full name of the person
that is associated with the resource. This field contains
subfields that break the persons name down into first and last
name, and the values are entered into those field containers.
Example:
Because this is an 'elementOnly' field, please look at the
examples for the subfields 'givenName' and 'surName'.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
organizationName |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Organization name
Summary:
The full name of the organization being described
Description:
The responsible party field contains the full name of the
organization that is associated with the resource. This field
is intended to describe which institution or overall
organization is associated with the resource being described.
Example:
National Center for Ecological Analysis and Synthesis
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
positionName |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Position Name
Summary:
The name of the title or position associated with the resource.
Description:
This field is intended to be used instead of a particular person
or full organization name. If the associated person that holds
the role changes frequently, then Position Name would be used
for consistency.
Example:
Niwot Ridge Data Manager
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
contactInfo |
Content of this field:
|
Description of this field:
|
Type: Contact |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Contact information
Summary:
Information needed in order to communicate with the associated
party.
Description:
The contact information field contains a series of sub fields that
provide information about contacting the associated party. The
subfields contain information such as the party's telephone
number, email address, postal address, online internet address,
etc.
Example:
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
roleCode |
Content of this field:
|
Description of this field:
|
Type: RoleCode |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Role code
Summary:
The role, or category, of the associated party.
Description:
The role code field is intended to provide some context about the
person or organization that is associated with the resource.
Since there may be many people associated, such as multiple
principal investigators, data collectors, curators, etc., this
field provides a means of describing how the individual or
organization is associated with the resource.
Example:
This field may contain values from a predefined list, which
includes: "contentProvider", "custodianSteward", "owner", "user",
"distributor", "metadataProvider", "originator", "pointOfContact",
"principalInvestigator", "processor", "publisher", "author",
"editor".
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
salutation |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Salutation
Summary:
The salutation used to address an individual
Description:
The salutation field is used in addressing an individual with a
particular title, such as Dr., Ms., Mrs., Mr., etc.
Example:
Dr.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
givenName |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Given name
Summary:
The given name of the individual.
Description:
The given name field is used for the first name of the individual
associated with the resource.
Example:
Corinna
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
surName |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Last name
Summary:
The last name of the individual.
Description:
The surname field is used for the last name of the individual
associated with the resource.
Example:
Gries
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
userName |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
systemType | required |
|
Tooltip:
Username of contact
Summary:
The username of the contact.
Description:
The username of the contact on the system to which the user
authenticates himself. This should be a distinguished username
on the system that the attribute "systemType" points to.
Example:
"uid=cjones,dc=pisco,dc=ecoinformatics,dc=org", "berkley"
Lineage:
new to EML 2.0
|
phone |
Content of this field:
|
Description of this field:
|
Type: Telephone |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Phone
Summary:
Information about the contact's telephone
Description:
The phone field describes information about the responsible
party's telephone, be it a voice phone, fax, or TTD/TTY type
telephone. This field contains subfields that are used for each
type.
Example:
Please see the subfield examples.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
address |
Content of this field:
|
Description of this field:
|
Type: Address |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Contact address
Summary:
The full address information for a given responsible party entry.
Description:
The address field is a container for multiple subfields that
describe the physical or electronic address of the responsible
party for a resource.
Example:
Please see the subfield examples.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
onlineResource |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Online resource
Summary:
The online resource field contains electronic/web contact
information.
Description:
the online resource field gives detailed information about a
contact that may be found via the Internet. It contains
multiple sufields that describe the location of the information
and the protocols used to retrieve it.
Example:
Please see the subfield examples.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
hoursOfService |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Hours of Service
Summary:
The hours of service field describes the times that a responsible
party may be contacted.
Description:
The hours of service field describes the dates and times that a
particular party that is associated with a resource amy be
contacted.
Example:
Monday through Friday, 8am to 5pm, PST
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
contactInstructions |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Contact instructions
Summary:
Any instructions needed in order to contact a responsible party.
Description:
The Contact instructions field describes any how a person or
organization may be contacted in reference to a resource.
Example:
Send email preferentially, or call between 10am and 12pm.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
voice |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Voice number
Summary:
The telephone number for voice communication.
Description:
The voice field is used to provide the voice telephone number for
a contact. It should include a country code, an area code, and
the number.
Example:
1 (805) 886-8686
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
facsimile |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Fax number
Summary:
The telephone number for facsimile communication.
Description:
The facsimile field is used to provide the facsimile telephone
number for a contact. It should include a country code, an area
code, and the number.
Example:
1 (805) 886-8687
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
other |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Other number
Summary:
A telephone number for commincation other than voice or fax.
Description:
The other telephone field is intended for any other type of
telephone communication, such as a TTD/TTY phone. The type of
number is described in the otherType field.
Example:
1 (805) 886-8688
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
otherType |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Other telephone type
Summary:
The type of phone number described in the other phone field.
Description:
The other type field is used to describe what type of phone
number is being used within the other phone field. This allows
the contact to provide multiple means of telephone contact, and
can be used for future communication types as well.
Example:
TTD/TTY
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
deliveryPoint |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Delivery point
Summary:
The location for postal deliveries.
Description:
The delivery point field is used for the physical address for
postal communication. This field is used to accomodate the many
different international conventions that are the equivalent
to a U.S. 'street address'.
Example:
7209 Coast Drive, Building 44
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
city |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
City
Summary:
The name of the city for the contact.
Description:
The city field is used for the city name of the contact associated
with a particular resource.
Example:
San Francisco
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
administrativeArea |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Administrative area
Summary:
The political area of a country.
Description:
The administrative area field is the equivalent of a 'state' in
the U.S. This field is intended to accomodate the many types of
international administrative areas.
Example:
Colorado
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
postalCode |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Postal code
Summary:
The postal code used for routing to an address.
Description:
The postal code is equivalent to a U.S. zip code, or the number
used for routing to an international address. The U.S. postal
code should include the 5 digit code plus the 4 digit extension.
Example:
93106-2231
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
country |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Country
Summary:
The name of the country for the contact's address.
Description:
The country field is used for the name of the contact's country.
Example:
U.S.A
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
electronicMailAddress |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Email address
Summary:
The email address of the contact.
Description:
The electronic mail address is the email address for the contact.
It should consist of a username folowed by the @ symbol, followd
by the email server domain name address.
Example:
jbrunt@lternet.edu
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
linkage |
Content of this field:
|
Description of this field:
|
Type: URL |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Online link
Summary:
The online link for the resource.
Description:
the linkage field is used to provide an online address for the
resource being accessed. It should conform to the Uniform
Resource Locator standard.
Example:
Please see the subfields for an example.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
protocol |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Protocol
Summary:
The connection protocol used to access an online resource.
Description:
The protocol field provides the name of the connection protocol
used to access an online resource. This field allows for a
detailed description of the protocol, or the acronym used in
refering to the protocol.
Example:
HTTP (Hypertext Transfer Protocol)
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
applicationProfile |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Application profile
Summary:
The name of an application profile that can be used with the
online resource.
Description:
The name of an application profile that can be used with the
online resource.
Example:
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
name |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Resource name
Summary:
The name of the online resource.
Description:
The name field provides the name of the resource that may be
accessed from the online URL. It may be the name of a dataset
file, or a form to access a database, or perhaps a directory
listing.
Example:
tree-heights.txt
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
description |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Resource description
Summary:
The description of what the online resource is or does.
Description:
The description field provides more detailed information about the
particular online resource.
Example:
The file tree-heights.txt is a listing of average tree heights for
all tree species found in the sample area.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
functionCode |
Content of this field:
|
Description of this field:
|
Type: xs:string |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Function code
Summary:
the function performed by the resource.
Description:
The function code provides information about the function that the
resource performs. For example, it may be a download resource, or
an instruction set, or a search facility.
Example:
metadata search engine
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
Attribute Definitions:
|
systemType |
Type: xs:string
Use: required
|
Tooltip:
System Type
Summary:
The system type to which the user name authenticates.
Description:
The system type to which the user name authenticates. This
should not be a server name. It should be more general.
Example:
LDAP, Metacat, MCAT
Lineage:
new to EML 2.0.
|
Complex Type Definitions:
|
ResponsibleParty |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Responsible party
Summary:
The individual, organization, or role associated with a resource.
Description:
The responsible party field contains multiple subfields that are used
to describe the person, organization, or position within an
organization that is associated in some way with a resource. It is
intended to be used to fully fully document contact information for
many types of associations, such as owner, manager, steward, curator,
etc.
Example:
Please see the examples for the particular subfields.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
Person |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
salutation | Optional | Multiple Times |
givenName | Optional | Multiple Times |
surName | Required | Once |
userName | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Person
Summary:
The full name of the individual associated with the resource.
Description:
The person field is used to enter the salutation, first name, and last
name of the individual associated with the resource. It uses three
subfields in order to help parse the person's entire name.
Example:
Please see the examples within each subfield.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
Contact |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Contact information
Summary:
detailed information about how to contact a responsible party.
Description:
The Contact field contains detailed subfields that describe when
and how a person or organization may be contacted. It includes
fields for telephone, email, hours of service, facsimile, etc.
Example:
Please see the examples within each subfield.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
Telephone |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
voice | Optional | Multiple Times |
facsimile | Optional | Multiple Times |
A sequence of ( |
other | Optional | Multiple Times |
otherType | Optional | Multiple Times |
) |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Telephone information
Summary:
The telephone field is intended to be used to provide the telephone
number for the contact.
Description:
The telephone field contains a number of subfields that provide voice,
fax, or other (such as TTD/TTY) telephone numbers.
Example:
Please see the subfield examples.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
Address |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Address
Summary:
The full address of the resposible party.
Description:
The address field is provides detailed information for communicating
with a party contact via electronic mail or postal mail, including the
physical delivery location.
Example:
Please see the examples for each subfield
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
OnlineResource |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Online resource
Summary:
The full description of the online resource.
Description:
The online resource field provides detailed information on where to
access a resource on the Internet, what the function is provided by
the resource, and the means of accessing it.
Example:
Please see the examples in the subfields.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
Simple Type Definitions:
|
|
Derived from: xs:string
(by xs:restriction)
Allowed values:
|
Tooltip:
Uniform Resource Locator
Summary:
The online resource locator address for the resource.
Description:
The URL field defines a syntax for addressing resources that are
available on the Internet. It is composed of a connection protocol,
followed by '://' followed by the domain name of the machine that
stores the resource, followed by the path to the resource.
Example:
http://knb.ecoinformatics.org/software/examples.txt
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
|
Derived from: xs:string
(by xs:restriction)
Allowed values:
- contentProvider
- custodianSteward
- owner
- user
- distributor
- metadataProvider
- originator
- pointOfContact
- principalInvestigator
- processor
- publisher
- author
- editor
|
Tooltip:
Role code
Summary:
The classification of the associated person or organization.
Description:
The role code field provides information on how a person or
organization is related to a resource. There may be many people
associated, including an 'originator' of a dataset, an 'author',
'editor', or 'publisher' of a literature resource, or an organization
that is a 'distributor'. the full list of choices is included in the
example.
Example:
author, contentProvider, custodianSteward, distributor, editor,
metadataProvider, originator, pointOfContact, principalInvestigator,
processor, publisher, or user.
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft), with the addition of a few new roleCode
values.
|