Automatically generated Universally Unique Identifier of this data set. Together with the "Data set version", the UUID uniquely identifies each data set.
Short name for the contact, that is used for display e.g. of links to this data set (especially in case the full name of the contact is rather long, e.g. "FAO" for "Food and Agriculture Organization").
Name of the person, working group, organisation, or database network, which is represented by this contact data set.
6-41-172-329
Classification Information
classificationInformation
r
[0,1]
Hierachical classification of the contact foreseen to be used to structure the contact content of the database. (Note: This entry is NOT required for the identification of the contact data set. It should nevertheless be avoided to use identical names for contacts in the same class.
6-41-172-336
Classification
classification
r
[0,n]
Optional statistical or other classification of the data set. Typically also used for structuring LCA databases.
URL or file name of a file listing all classes of this classification system. [Notes: the referenced file has to be in form of the "ILCDClassification.xml" format. If a classification file is specified, the "class" entry should correspond to the classes defined in the classification file.]
If more than one class is specified in a hierachical classification system, the hierarchy level (1,2,...) could be specified with this attribute of class.
Unique identifier for the class. [Notes: If such identifiers are also defined in the referenced category file, they should be identical. Identifiers can be UUID's, but also other forms are allowed.]
Mail address of the contact; specific for the person, working group, or department. [Note: A general contact point to the organisation is to be given in "General contact point".]
Alternative address / contact details for the contact. Provides contact information in case e.g. the person or group represented by this contact has left the organisation or changed office/telephone. This alternative contact point can hence contain also a central telephone number, e-mail, www-address etc. of the organisation.
"Contact data set"s of working groups, organisations or database networks to which EITHER this person or entity OR this database, data set format, or compliance system belongs. [Note: This does not necessarily imply a legally binding relationship, but may also be a voluntary membership.]
"Source data set" of the logo of the organisation or source to be used in reports etc.
6-41-172-346
Other content
other
o
[0,1]
May contain arbitrary content.
0
Entity identifiers
e:entityIds
o
[0,1]
Identifiers which uniquely identify the entity (person or organization). Different identifiers commonly used, such as VAT ID or Tax Identification Number (TIN).
Entity identifier
e:entityId
o
[0,1]
Identifier which uniquely identifies the entity (person or organization).
Identifier type
@e:type
o
[0,1]
xs:string
Type of identifier (e.g. 'VATID', 'TIN').
Other content
other
o
[0,1]
May contain arbitrary content.
0
Administrative information
administrativeInformation
r
[0,1]
Information on data set management and administration.
1-5
Data entry by
dataEntryBy
r
[0,1]
Staff or entity, that documented the generated data set, entering the information into the database; plus administrative information linked to the data entry activity.
"Source data set" of the used version of the ILCD format. If additional data format fields have been integrated into the data set file, using the "namespace" option, the used format namespace(s) are to be given. This is the case if the data sets carries additional information as specified by other, particular LCA formats, e.g. of other database networks or LCA softwares.
1-5-28-105
Other content
other
o
[0,1]
May contain arbitrary content.
0
Publication and ownership
publicationAndOwnership
r
[0,1]
Information related to publication and version management of the data set including copyright and access restrictions.
Version number of data set. First two digits refer to major updates, the second two digits to minor revisions and error corrections etc. The third three digits are intended for automatic and internal counting of versions during data set development. Together with the data set's UUID, the "Data set version" uniquely identifies each data set.
Last preceding data set, which was replaced by this version. Either a URI of that data set (i.e. an internet address) or its UUID plus version number is given (or both).
URI (i.e. an internet address) of the original of this data set. [Note: This equally globally unique identifier supports users and software tools to identify and retrieve the original version of a data set via the internet or to check for available updates. The URI must not represent an existing WWW address, but it should be unique and point to the data access point, e.g. by combining the data owner's www path with the data set's UUID, e.g. http://www.mycompany.com/lca/processes/50f12420-8855-12db-b606-0900210c9a66.]