Module Documentation: eml-party
Back to EML Contents

The eml-party module describes a responsible party (person or organization), and is typically used to name the originator of a resource or metadata document. It contains detailed contact information for the party, be it an individual person, an organization, or a named position within an organization. The eml-party module is used throughout the other EML modules where detailed contact information is needed.

The eml-party module, like other modules, may be "referenced" via the <references> tag. This allows a party to be described once, and then used as a reference in other locations within the EML document via it's ID.

Module details
Recommended Usage: all datasets
Stand-alone: yes
Imports: eml-documentation, eml-resource
Imported By:
View an image of the schema: eml-party image

Element Definitions:

individualName  This element has no default value.
Content of this field: Description of this field:
Type: Person
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(s):
Because this is an 'elementOnly' field, please look at the examples for the subfields 'givenName' and 'surName'.
organizationName  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
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(s):
National Center for Ecological Analysis and Synthesis
positionName  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
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(s):
Niwot Ridge Data Manager
address  This element has no default value.
Content of this field: Description of this field:
Type: Address
The address field is a container for multiple subfields that describe the physical or electronic address of the responsible party for a resource.
Example(s):
Please see the subfield examples.
phone  This element has no default value.
Content of this field: Description of this field:
Attributes: Use: Default Value:
phonetypeoptionalvoice
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(s):
<phone phonetype="voice">805-555-2500</phone>
electronicMailAddress  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
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(s):
my-email@mydomain.edu
onlineUrl  This element has no default value.
Content of this field: Description of this field:
Type: xs:anyURI
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(s):
http://www.yourdomain.edu/~doe
userId  This element has no default value.
Content of this field: Description of this field:
Attributes: Use: Default Value:
directoryrequired
An identifier that links this party to a directory of personnell. Although specific contact information for a party might change, the underlying correspondence to a real individual does not. This identifer provides a pointer within a personnell directory that may contain further, and possibly more current, information about the party.
Example(s):
uid=jtown,o=NCEAS,dc=ecoinformatics,dc=org
salutation  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
The salutation field is used in addressing an individual with a particular title, such as Dr., Ms., Mrs., Mr., etc.
Example(s):
Dr.
givenName  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
The given name field is used for the first name of the individual associated with the resource.
Example(s):
Jane
surName  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
The surname field is used for the last name of the individual associated with the resource.
Example(s):
Doe
deliveryPoint  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
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(s):
7209 Coast Drive, Building 44
city  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
The city field is used for the city name of the contact associated with a particular resource.
Example(s):
San Francisco
administrativeArea  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
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(s):
Colorado
postalCode  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
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(s):
93106-2231
country  This element has no default value.
Content of this field: Description of this field:
Type: xs:string
The country field is used for the name of the contact's country.
Example(s):
U.S.A
party  This element has no default value.
Content of this field: Description of this field:
Type: ResponsibleParty
The responsible party contains multiple subfields that are used to describe a person, organization, or position within an organization. It is intended to be used to fully document contact information for many types of associations, such as owner, manager, steward, curator, etc.

Attribute Definitions:

phonetype

Type: xs:string

Use: optional

Default value: voice

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".
directory

Type: xs:string

Use: required

This attribute names the directory system to which this userId applies. This will generally be a URL that shows how to look up information, for example an LDAP url. However, it could also be a non-parseable description of the directory system if that is all that is available.
Example(s):
ldap:///ldap.ecoinformatics.org/dc=ecoinformatics,dc=org
id

Type: res:IDType

Use: optional

system

Type: res:SystemType

Use: optional

scope

Type: res:ScopeType

Use: optional

Default value: document

id

Type: res:IDType

Use: optional

system

Type: res:SystemType

Use: optional

scope

Type: res:ScopeType

Use: optional

Default value: document

Complex Type Definitions:

ResponsibleParty 
Content of this field: Description of this field:
Elements: Use: How many:
A choice of (
A sequence of (
A choice of (
individualNamerequired
OR
organizationNamerequired
OR
positionNamerequired
)
addressoptionalunbounded
phoneoptionalunbounded
electronicMailAddressoptionalunbounded
onlineUrloptionalunbounded
userIdoptionalunbounded
)
OR
res:ReferencesGroup  
)
Attributes: Use: Default Value:
idoptional
systemoptional
scopeoptionaldocument
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 document contact information for many types of associations, such as owner, manager, steward, curator, etc.
Example(s):
Please see the examples for the particular subfields.
Person 
Content of this field: Description of this field:
Elements: Use: How many:
A sequence of (
salutationoptionalunbounded
givenNameoptionalunbounded
surNamerequired
)
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(s):
Please see the examples within each subfield.
Address 
Content of this field: Description of this field:
Elements: Use: How many:
A choice of (
A sequence of (
deliveryPointoptionalunbounded
cityoptional
administrativeAreaoptional
postalCodeoptional
countryoptional
)
OR
res:ReferencesGroup  
)
Attributes: Use: Default Value:
idoptional
systemoptional
scopeoptionaldocument
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(s):
Please see the examples for each subfield

Simple Type Definitions:

RoleType

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(s):
author, contentProvider, custodianSteward, distributor, editor, metadataProvider, originator, pointOfContact, principalInvestigator, processor, publisher, or user.

Group Definitions:

Web Contact: jones@nceas.ucsb.edu