OWL/RDF ILCD schema used in the LCABIM project. It provides the structural vocabulary (classes and properties) for representing ILCD-based datasets and instances.
OWL/RDF-ILCD-Schema verwendet im LCABIM-Projekt. Es stellt das strukturelle Vokabular (Klassen und Properties) zur Repräsentation von ILCD-basierten Datensätzen und Instanzen bereit.
LCABIM ILCD core schema
LCABIM ILCD-Kernschema
Container for the administrativeInformation section.
A flexible extension pattern that can carry name-value pairs, optional metadata, references, or embedded structures like scenarios or margins.
Classification information for the data set.
Holds the reference about the goal and scope of the dataset.
Container for compliance-related declarations.
Holds a reference to a specific compliance system.
One entry in the otherDSTAR array. Has a 'name' and a typed 'value'.
Self-contained container for the otherDSTAR section.
The typed structure that appears under 'value' in each otherDSTAR entry.
Holds timestamp and references to data set formats.
Holds the reference to the person or entity generating the dataset.
Holds references to data sources, usage advice, and other extras.
Simple object for classification with 'classHierarchy' and 'name'.
Top-level container for the 'exchanges' section.
Extended multi-language string with a default value and additional language strings.
Represents a reference to another dataset or file. Either refObjectId and version, or refObjectUri, or both have to be specified.
Single LCIA result represented as a list of LCIAResultEntry objects.
Top-level container for the LCIAResults section.
LCI methodological modelling aspects including allocation / substitution information.
Holds LCI method, allocation info, references, and other content.
Material property list with name, value, unit, unitDescription.
Top-level container for the modellingAndValidation section.
A container holding 'anies' a list of anies objects
Container for the process information section.
Contains dataset version, ownership references, etc.
A single review entry containing reviewer/institution details.
Technology information for the data set.
Time-related information for the data set.
Unique Universal Identifier, 16-byte hex number.
A wrapper for a UUID value provided as a dictionary.
Represents the validation information, including review entries.
Access restrictions / use conditions for this data set as free text or referring to e.g. license conditions. In case of no restrictions "None" is entered.
A list of DSTAR items, each containing name + typed value.
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".
General descriptive name of the process and/or its main good(s) or service(s) and/or it's level of processing.
Classification hierarchy string (e.g., 'Quantities').
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.]
Optional statistical or other classification of the data set. Typically also used for structuring LCA databases.
Flow classification object with classHierarchy and name.
Hierarchical classification of the good, service, or process. (Note: This entry is NOT required for the identification of a Process. It should nevertheless be avoided to use identical names for Processes in the same category.
Basic information about the goal and scope of the dataset.
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.).
Indicates whether or not a copyright on the data set exists. Decided upon by the "Owner of data set". [Note: See also field "Access and use restrictions".]
Identifies the way by which the Flow property value was derived (e.g., measured, estimated, etc.), respectively the status and relevancy of missing data. Example values: "Measured", "Calculated", "Estimated", "Unknown derivation".
Staff or entity, that documented the generated data set, entering the information into the database; plus administrative information linked to the data entry activity.
Expert(s), that compiled and modelled the data set as well as internal administrative information linked to the data generation activity.
General data set information. Section covers all single fields in the ISO/TS 14048 "Process description", which are not part of the other sub-sections. In ISO/TS 14048 no own sub-section is foreseen for these entries.
Automated entry: internal ID, used in the "Quantitative reference" section to identify the "Reference flow(s)" in case the quantitative reference of this Process data set is of this type.
General descriptive and specifying name of the process.
End year of the time period for which the data set is still valid / sufficiently representative. This date also determines when a data set revision / remodelling is required or recommended due to expected relevant changes in environmentally or technically relevant inventory values, including in the background system.
Dataset version string (e.g., '07.01.004').
The type of data source used. Example values: "Primary", "> 90% primary", "Mixed primary / secondary", "Secondary"
Data selection, completeness, and treatment principles and procedures, data sources and market coverage information.
Date when the data set was revised for the last time, typically manually set.
Indicates whether this is the default scenario.
Default value for shortDescriptionExtended
Further explanations about additional aspects of the location: e.g. a company and/or site description and address, whether for certain sub-areas within the "Location" the data set is not valid, whether data is only valid for certain regions within the location indicated, or whether certain elementary flows or intermediate product flows are extrapolated from another geographical area.
Documentation/Reporting compliance of this data set with the respective requirements set by the 'compliance system' referred to.
Input/Output list of exchanges with the quantitative inventory data as well as pre-calculated LCIA results. Represented in the YAML schema as a list of ExchangeEntry objects.
Renamed from 'exchange direction'; indicates flow direction (INPUT/OUTPUT).
Further, quantitative specifying information on the good, service or process in technical term(s): qualifying constituent(s)-content and / or energy-content per unit etc. as appropriate. Separated by commata. (Note: non-qualifying flow properties, CAS No, Synonyms, Chemical formulas etc. are documented exclusively in the "Flow data set".)
General information about the data set, including e.g. general (internal, not reviewed) quality statements as well as information sources used. (Note: Please also check the more specific fields e.g. on "Advice on data set use" to avoid overlapping entries.)
Provides information about the geographical representativeness of the data set.
Unique ID for building URIs, e.g. 'ex:admininfo/123'.
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.
Type of license that applies to the access and use of this data set.
Location, country or region the data set represents. [Note 1: This field does not refer to e.g. the country in which a specific site is located that is represented by this data set but to the actually represented country, region, or site. Note 2: Entry can be of type "two-letter ISO 3166 country code" for countries, "seven-letter regional codes" for regions or continents, or "market areas and market organisations", as predefined for the ILCD. Also a name for e.g. a specific plant etc. can be given here (e.g. "FR, Lyon, XY Company, Z Site"; user defined). Note 3: The fact whether the entry refers to production or to consumption / supply has to be stated in the name-field "Mix and location types" e.g. as "Production mix".]
The amount (in percent) of the included uncertainty margins
The maximum amount of the specified quantity.
Mean numeric value for the exchange and LCIA indicator.
Mean numeric value of the flow property.
Methodological compliance of this data set with the respective requirements set by the 'compliance system' referred to.
The minimum amount of the specified quantity.
Covers the five sub-sections: 1) LCI method and allocation, 2) Data sources, treatment and representativeness, 3) Completeness, 4) Validation, and 5) Compliance. (Section refers to LCI modelling and data treatment aspects etc., NOT the modeling of e.g. the input/output-relationships of a parameterised data set.)
Module name for environmental indicatores.
Classification system name (e.g., 'GaBiCategories').
Nomenclature compliance of this data set with the respective requirements set by the 'compliance system' referred to.
A list of scenario objects inside 'anies'.
Typed local object for 'other' data in dataSourcesTreatmentAndRepresentativeness.
Equivalent to 'other' in JSON, storing anies with modules or references.
Additional LCI method and allocation content.
Additional time-related dictionary data. May contain arbitrary content.
Corresponds to the ISO/TS 14048 section "Process description". It comprises the following six sub-sections: 1) "Data set information" for data set identification and overarching information items, 2) "Quantitative reference", 3) "Time", 4) "Geography", 5) "Technology" and 6) "Mathematical relations".
Information related to publication and version management of the data set including copyright and access restrictions.
Quality compliance of this data set with the respective requirements set by the 'compliance system' referred to.
This section names the quantitative reference used for this data set, i.e. the reference to which the inputs and outputs quantiatively relate.
If true, indicates this is a reference flow.
Indicates if this property is the reference flow property.
"Contact data set" of the commissioner / financing party of the data collection / compilation and of the dataset modelling. For groups of commissioners, each single organisation should be named. For dataset updates and for direct use of data from formerly commissioned studies, also the original commissioner should be named.
"Source data set" of the complete review report.
"Source data set" of the "Compliance system" that is declared to be met by the data set.
"Source data set" of the used version of the ILCD format. If additional data format fields have been integrated into the dataset file using the "namespace" option, the used format namespace(s) are to be given. This applies when the dataset carries additional information specified by other LCA formats, such as those from different database networks or LCA software.
"Source data set(s)" of the data source(s) used for the data set e.g. paper, questionnaire, monography etc. The main data sources e.g. for underlying substance properties are named, too.
"Source data set(s)" of detailed LCA study on the process or product represented by this data set, as well as documents / files with overarching documentative information on technology, geographical and / or time aspects etc. (e.g. basic engineering studies, process simulation results, patents, plant documentation, model behind the parameterisation of the "Mathematical model" section, etc.) (Note: can indirectly reference to digital file.)
"Flow data set" of this Input or Output.
List of references to LCA method details.
"LCIA method data set" applied to calculate the LCIA results.
"Contact data set" of reviewer. The full name of reviewer(s) and institution(s) as well as a contact address and/or email should be provided in that contact data set.
"Contact data set" of the person or entity who owns this data set. (Note: this is not necessarily the publisher of the data set.)
"Contact data set" of the responsible person or entity that has documented this data set, i.e. entered the data and the descriptive information.
"Contact data set" of the person(s), working group(s), organisation(s) or database network, that generated the data set, i.e. being responsible for its correctness regarding methods, inventory, and documentative information.
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).
One or more of the Inputs or Outputs in case "Type of quantitative reference" is of type "Reference flow(s)". (Data set internal reference.)
"Contact data set" of the authority that has registered this data set.
"Source data set" of the flow diagramm(s) and/or photo(s) of the good, service, technology, plant etc represented by this data set. For clearer illustration and documentation of data set.
"Source data set" of the pictogramme of the good, service, technogy, plant etc. represented by this data set. For use in graphical user interfaces of LCA software.
Start year of the time period for which the data set is valid (until year of "Data set valid until:"). For data sets that combine data from different years, the most representative year is given regarding the overall environmental impact. In that case, the reference year is derived by expert judgement.
Reference to "UUID of source"(s) in the "Source data set" of data source(s) used for modelling the value of this single LCIA factor e.g. a specific paper, questionnaire, monography etc. If, as typical, more than one data source was used, more than one source can be referenced.
A unique identifying number for this data set issued by the registration authority.
The resulting overall uncertainty of the calculated variable value considering uncertainty of measurements, modelling, appropriateness, etc. Notes: For log-normal distribution, the square of the geometric standard deviation (SDg^2) is stated. Mean value times SDg^2 equals the 97.5% value (= Maximum value), and mean value divided by SDg^2 equals the 2.5% value (= Minimum value). For normal distribution, the doubled standard deviation value (2*SD) is entered. Mean value plus 2*SD equals the 97.5% value (= Maximum value), and mean value minus 2*SD equals the 2.5% value (= Minimum value). This data field remains empty when uniform or triangular uncertainty distribution is applied.
Review/Verification compliance of this data set with the respective requirements set by the 'compliance system' referred to.
Summary of the review. All the following items should be explicitly addressed: Representativeness, completeness, and precision of Inputs and Outputs for the process in its documented location, technology and time i.e. both completeness of technical model (product, waste, and elementary flows) and completeness of coverage of the relevant problem fields (environmental, human health, resource use) for this specific good, service, or process. Plausibility of data. Correctness and appropriateness of the data set documentation. Appropriateness of system boundaries, cut-off rules, LCI modelling choices such as e.g. allocation, consistency of included processes and of LCI methodology. If the data set comprises pre-calculated LCIA results, the correspondence of the Input and Output elementary flows (including their geographical validity) with the applied LCIA method(s) should be addressed by the reviewer. An overall quality statement on the data set may be included here.
Reusable advanced multi-language string (from shared definitions).
Synonyms / alternative names / brands of the good, service, or process. Separated by semicolon.
Description of the intended / possible applications of the good, service, or process. E.g. for which type of products the material, represented by this data set, is used. Examples: "This high purity chemical is used for analytical laboratories only." or "This technical quality bulk chemical is used for large scale synthesis in chemical industry.". Or: "This truck is used only for long-distance transport of liquid bulk chemicals".
Provides information about the technological representativeness of the data set.
Description of the technological characteristics including operating conditions of the process or product system. For the latter this includes the relevant upstream and downstream processes included in the data set. Professional terminology should be used.
Provides information about the time representativeness of the data set.
Description of the valid time span of the data set including information on limited usability within sub-time spans (e.g. summer/winter).
Date and time stamp of data set generation, typically an automated entry ("last saved").
Type of the data set regarding systematic inclusion/exclusion of upstream or downstream processes, transparency and internal (hidden) multi-functionality, and the completeness of modelling.
String identifying the type of flow (e.g., 'Product flow', 'Other flow').
Defines the kind of uncertainty distribution that is valid for this particular object or parameter. Example values: "undefined", "log-normal", "normal", "triangular", "uniform".
Methodological advice for the use and application of this data set, such as limits in applicability or representativeness as well as recommendations to use it together with others from the same LCIA methodology to ensure consistency.
Wrapper for a UUID value provided as a dictionary.
The actual UUID value extracted from a UUID dictionary.
Structured version info (from shared definitions).
Version as a formatted string (e.g., '00.00.001').
Flag indicating a zero or special version.