Automatically generated Universally Unique Identifier of this data set. Together with the "Data set version", the UUID uniquely identifies each data set.
Synonyms are alternative names for the "Name" of the Flow property.
4-25-104-275
Classification information
classificationInformation
r
[0,1]
Hierachical classification of the Flow property foreseen to be used to structure the Flow property content of the database. (Note: This entry is NOT required for the identification of the Flow property data set. It should nevertheless be avoided to use identical names for Flow properties in the same class.
4-25-104-276
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.]
Free text for general information about the data set. It may contain comments on e.g. information sources used as well as general (internal, not reviewed) quality statements.
4-25-104-278
Other content
other
o
[0,1]
May contain arbitrary content.
0
Quantitative reference
quantitativeReference
r
[0,1]
This section allows to refer to the Flow property's quantitative reference, which is always a unit (i.e. that unit, in which the property is measured, e.g. "MJ" for energy-related Flow properties).
"Source data set" of data source(s) used for the data set e.g. a paper, a questionnaire, a monography etc. The main raw data sources should be named, too. [Note: relevant especially for market price data.]
4-27-118-280
Other content
other
o
[0,1]
May contain arbitrary content.
0
Compliance declarations
complianceDeclarations
r
[0,1]
Statements on compliance of several data set aspects with compliance requirements as defined by the referenced compliance system (e.g. an EPD scheme, handbook of a national or international data network such as the ILCD, etc.).
Official approval whether or not and in how far the data set meets all the requirements of the "Compliance system" refered to. This approval should be issued/confirmed by the owner of that compliance system, who is identified via the respective "Contact data set".
1-3-22-95
Other content
other
o
[0,1]
May contain arbitrary content.
0
Other content
other
o
[0,1]
May contain arbitrary content.
0
Administrative information
administrativeInformation
r
[0,1]
Information on data set management and administration.
4-29
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.]