Show: Field nameElement/attribute nameRequirementOccurrencesData typeDefinitioneDoc ID

ILCD Format 1.1 Documentation - Flow property data set

Field name Element/attribute name Requ. Occ. Data type Definition eDoc ID
Flow property data set flowPropertyDataSet m [1,1] 4
@version m SchemaVersion
Flow property information flowPropertiesInformation m [1,1] 4-25
Data set information dataSetInformation m [1,1] 4-25-104
UUID of flow property data set UUID m [1,1] UUID Automatically generated Universally Unique Identifier of this data set. Together with the "Data set version", the UUID uniquely identifies each data set. 4-25-104-273
Name of flow property name r [0,1] StringMultiLang Name of flow property. 4-25-104-274
Synonyms synonyms o [0,1] FTMultiLang 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. 1-1-2-7-2
Classification system name @name r string Name of the classification system. 1-1-2-7-2-a
Classes @classes r anyURI 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.] 1-1-2-7-2-b
Class name class r [1,n] Name of the class. 1-1-2-7-2-1
Hierarchy level @level r LevelType 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. 1-1-2-7-2-1-a
Unique class identifier @classId r string 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.] 1-1-2-7-2-1-b
Other content other o [0,1] May contain arbitrary content. 0
General comment on data set generalComment o [0,1] FTMultiLang 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). 4-25-106
Reference unit referenceToReferenceUnitGroup r [1,1] GlobalReferenceType "Unit group data set" and its reference unit, in which the Flow property is measured. 4-25-106-279
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0
Modelling and validation modellingAndValidation o [0,1] Covers the five sub-sections 1) LCI method (not used), 2) Data sources, treatment and representativeness (only 3 fields), 3) Completeness (not used), 4) Validation, and 5) Compliance. 4-27
Data sources, treatment and representativeness dataSourcesTreatmentAndRepresentativeness o [0,1] 4-27-118
Data source referenceToDataSource o [0,n] GlobalReferenceType "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.). 1-3-22
Compliance compliance r [1,n] one compliance declaration 1-3-22-1
Compliance system name referenceToComplianceSystem r [1,1] GlobalReferenceType "Source data set" of the "Compliance system" that is declared to be met by the data set. 1-3-22-90
Approval of overall compliance approvalOfOverallCompliance o [0,1] ComplianceValues
Fully compliantMeets all requirements of this compliance aspect as defined in the respective "Compliance system".
Not compliantDoes not meet all requirements of this compliance aspect, as defined for the respective "Compliance system".
Not definedFor this compliance aspect the named "Compliance system" has not defined compliance requirements.
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. 4-29-130
Time stamp (last saved) timeStamp r [0,1] dateTime Date and time stamp of data set generation, typically an automated entry ("last saved"). 1-5-28-104
Data set format(s) referenceToDataSetFormat r [0,n] GlobalReferenceType "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. 4-29-132
Data set version dataSetVersion m [1,1] Version 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. 1-5-30-111
Preceding data set version referenceToPrecedingDataSetVersion o [0,n] GlobalReferenceType 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). 1-5-30-112
Permanent data set URI permanentDataSetURI r [0,1] anyURI 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.] 1-5-30-300
Owner of data set referenceToOwnershipOfDataSet r [0,1] GlobalReferenceType "Contact data set" of the person or entity who owns this data set. (Note: this is not necessarily the publisher of the data set.) 1-5-30-115
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0
Other content other o [0,1] May contain arbitrary content. 0