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.
Note that this field, used in conjunction with 'organizationName'
and 'positionName' make up a single logical originator. Because
of this, an originator with only the individualName of 'Joe Smith'
is NOT the same as an originator with the name of 'Joe Smith' and
the organizationName of 'NSF'. Also, the positionName should not
be used in conjunction with individualName unless only that
individual at that position would be considered an originator
for the data package. If a positionName is used in conjunction
with an organizationName, then that
implies that any person who currently occupies said positionName
at organizationName is the originator of the data package.
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.
Note that this field, used in conjunction with 'individualName'
and 'positionName' make up a single logical originator. Because
of this, an originator with only the individualName of 'Joe Smith'
is NOT the same as an originator with the name of 'Joe Smith' and
the organizationName of 'NSF'. Also, the positionName should not
be used in conjunction with individualName unless only that
individual at that position would be considered an originator
for the data package. If a positionName is used in conjunction
with an organizationName, then that
implies that any person who currently occupies said positionName
at organizationName is the originator of the data package.
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.
Note that this field, used in conjunction with 'organizationName'
and 'individualName' make up a single logical originator. Because
of this, an originator with only the individualName of 'Joe Smith'
is NOT the same as an originator with the name of 'Joe Smith' and
the organizationName of 'NSF'. Also, the positionName should not
be used in conjunction with individualName unless only that
individual at that position would be considered an originator
for the data package. If a positionName is used in conjunction
with an organizationName, then that
implies that any person who currently occupies said positionName
at organizationName is the originator of the data package.
Example:
Niwot Ridge Data Manager
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).
|
phone |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
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 an attribute used
to identify the type.
Example:
<phone phonetype="voice">805-555-2500</phone>
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
party. It is intended to be an Internet SMTP email
address, which should consist of a username folowed by the
@ symbol, followd by the email server domain name address.
Other address types are allowable.
Example:
my-email@mydomain.edu
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
onlineLink |
Content of this field:
|
Description of this field:
|
Type: xs:anyURI |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Online Link
Summary:
A link to associated online information, usually a web site.
Description:
A link to associated online information, usually a web site.
When the party represents an organization, this is the URL
to a website or other online information about the organization.
If the party is an individual, it might be their personal web
site or other related online information about the party.
Example:
http://www.yourdomain.edu/~doe
Lineage:
This field was derived from the ISO 19115.3 standard
(iso-geo-md-2000June-draft).
|
role |
Content of this field:
|
Description of this field:
|
Type: RoleType |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Role
Summary:
The role, or category, of the associated party in this context.
Description:
The role 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:
Jane
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:
Doe
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., or Province in Canada. 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).
|
Attribute Definitions:
|
phonetype |
Type: xs:string
Use: optional
|
Tooltip:
Phone type
Summary:
The type of the phone to which this number applies
Description:
This attribute gives the type of phone to which this
number applies. By default, this is assumed to be
of type "voice", but other possibilities include
"facsimile" and "tdd".
Example:
Lineage:
Derived from NBII and related standards.
|
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 | 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).
|
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).
|
Simple Type Definitions:
|
|
Derived from: xs:string
(by xs:restriction)
Allowed values:
- contentProvider
- custodianSteward
- owner
- user
- distributor
- metadataProvider
- originator
- pointOfContact
- principalInvestigator
- processor
- publisher
- author
- editor
|
Tooltip:
Role
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.
|