Element Definitions:
|
eml-package |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
resource | Required | Once |
triple | Optional | Multiple Times |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Package descriptor
Summary:
The eml-package element describes and lists the components of
a data package
Description:
The eml-package element represents a data package , which describes a
collection of metadata and data files and enumerates a list of
relationships between the metadata and data file(s).
The relationships are in the form of:
<subject> <relationship> <object>
Example:
Lineage:
The package element is derived from package.dtd, version 1.5
|
resource |
Content of this field:
|
Description of this field:
|
|
Tooltip:
Package contact information
Summary:
Contact information for the people or organization that manage/
own this package.
Description:
Contact information for the owners/managers/PIs of this package.
This should contain contact information for anyone who has
contributed to this package.
Example:
see examples in eml-resource.xsd
Lineage:
new to EML 2.0
|
triple |
Content of this field:
|
Description of this field:
|
Elements:
|
Required?:
|
How many:
|
A sequence of ( |
subject | Required | Once |
relationship | Required | Once |
object | Required | Once |
) |
Attributes:
|
Required?:
|
Default Value:
|
|
Tooltip:
Relationship list
Summary:
The definition of a relationship between component objects
in a package
Description:
The triple element lists all relationships in the package,
which effectively enumerates the components of the package.
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.
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 package file
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:
|
Complex Type Definitions:
|
Simple Type Definitions:
|