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 classificationfile.]
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Identity constraints
QName
Type
Refer
Selector
Field(s)
ClassificationLevelUniqueConstraint
unique
common:class
@level
Source
<xs:element name="classification" type="ClassificationType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2" name="classification"/><ilcd:display-name>Classification</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Optional statistical or other classification of the data set. Typically also used for structuring LCA databases.</xs:documentation></xs:annotation><xs:unique name="ClassificationLevelUniqueConstraint"><xs:selector xpath="common:class"/><xs:field xpath="@level"/></xs:unique></xs:element>
Unique identifier for the class. [Notes: If such identifiers are also defined in the referenced category file, they should be identical. Identifiers canbe UUID's, but also other forms are allowed.]
If more than one class is specified in a hierachical classification system, the hierarchy level (1,2,...) could be specified with this attribute ofclass.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:element name="class" maxOccurs="unbounded" type="ClassType"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-1" name="class"/><ilcd:display-name>Class name</ilcd:display-name><ilcd:iso-field-id>(1.1.2)</ilcd:iso-field-id><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of the class.</xs:documentation></xs:annotation></xs:element>
<xs:element name="subReference" type="String" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Valid only for references of type "source data set". Allows to make references to sections, pages etc. within a source.</xs:documentation></xs:annotation></xs:element>
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
Source
<xs:element name="shortDescription" type="STMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:documentation>Short, clear-text summary of the referenced object that can be used as a hint what to expect behind the reference in cases where it cannot be resolved.</xs:documentation></xs:annotation></xs:element>
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
Element ValidationGroup3 / referenceToNameOfReviewerAndInstitution
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
"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 thatcontact data set.
<xs:element name="referenceToNameOfReviewerAndInstitution" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-87" name="referenceToNameOfReviewerAndInstitution"/><ilcd:display-name>Reviewer name and institution</ilcd:display-name><ilcd:iso-field-id>2.6.4</ilcd:iso-field-id><ilcd:iso-field-name>Validator</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"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.</xs:documentation></xs:annotation><xs:unique name="referenceToNameOfReviewerAndInstitutionShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
Further information from the review process, especially comments received from third parties once the data set has been published or additional reviewercomments from an additional external review.
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
Source
<xs:element name="otherReviewDetails" type="FTMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-88" name="otherReviewDetails"/><ilcd:display-name>Subsequent review comments</ilcd:display-name><ilcd:iso-field-id>(2.6.2) and (2.6.3)</ilcd:iso-field-id><ilcd:iso-field-name>(Procedure), (Result)</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>Further information from the review process, especially comments received from third parties once the data set has been published or additional reviewer comments from an additional external review.</xs:documentation></xs:annotation></xs:element>
<xs:element name="referenceToComplianceSystem" type="GlobalReferenceType" minOccurs="1"><xs:annotation><xs:appinfo><ilcd:element id="1-3-22-90" name="referenceToComplianceSystem"/><ilcd:display-name>Compliance system name</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"Source data set" of the "Compliance system" that is declared to be met by the data set.</xs:documentation></xs:annotation><xs:unique name="referenceToComplianceSystemShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
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 beissued/confirmed by the owner of that compliance system, who is identified via the respective "Contact data set".
Meets all requirements of this compliance aspect as defined in the respective "Compliance system".
enumeration
Not compliant
Does not meet all requirements of this compliance aspect, as defined for the respective "Compliance system".
enumeration
Not defined
For this compliance aspect the named "Compliance system" has not defined compliance requirements.
Source
<xs:element name="approvalOfOverallCompliance" type="ComplianceValues" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-3-22-95" name="approvalOfOverallCompliance"/><ilcd:display-name>Approval of overall compliance</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>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".</xs:documentation></xs:annotation></xs:element>
Element nomenclatureCompliance
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Nomenclature compliance of this data set with the respective requirements set by the "compliance system" refered to.
<xs:element name="nomenclatureCompliance" type="ComplianceValues"><xs:annotation><xs:appinfo><ilcd:element id="1-3-22-92" name="nomenclatureCompliance"/><ilcd:display-name>Nomenclature compliance</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Nomenclature compliance of this data set with the respective requirements set by the "compliance system" refered to.</xs:documentation></xs:annotation></xs:element>
Element methodologicalCompliance
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Methodological compliance of this data set with the respective requirements set by the "compliance system" refered to.
<xs:element name="methodologicalCompliance" type="ComplianceValues"><xs:annotation><xs:appinfo><ilcd:element id="1-3-22-91" name="methodologicalCompliance"/><ilcd:display-name>Methodological compliance</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Methodological compliance of this data set with the respective requirements set by the "compliance system" refered to.</xs:documentation></xs:annotation></xs:element>
Element reviewCompliance
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Review/Verification compliance of this data set with the respective requirements set by the "compliance system" refered to.
<xs:element name="reviewCompliance" type="ComplianceValues"><xs:annotation><xs:appinfo><ilcd:element id="1-3-22-93" name="reviewCompliance"/><ilcd:display-name>Review compliance</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Review/Verification compliance of this data set with the respective requirements set by the "compliance system" refered to.</xs:documentation></xs:annotation></xs:element>
Element documentationCompliance
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Documentation/Reporting compliance of this data set with the respective requirements set by the "compliance system" refered to.
<xs:element name="documentationCompliance" type="ComplianceValues"><xs:annotation><xs:appinfo><ilcd:element id="1-3-22-94" name="documentationCompliance"/><ilcd:display-name>Documentation compliance</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Documentation/Reporting compliance of this data set with the respective requirements set by the "compliance system" refered to.</xs:documentation></xs:annotation></xs:element>
Element qualityCompliance
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Quality compliance of this data set with the respective requirements set by the "compliance system" refered to.
<xs:element name="qualityCompliance" type="ComplianceValues"><xs:annotation><xs:appinfo><ilcd:element id="1-3-22-96" name="qualityCompliance"/><ilcd:display-name>Quality compliance</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Quality compliance of this data set with the respective requirements set by the "compliance system" refered to.</xs:documentation></xs:annotation></xs:element>
Element commissionerAndGoal
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Basic information about goal and scope of the data set.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Identity constraints
QName
Type
Refer
Selector
Field(s)
projectLangUniqueConstraint
unique
common:project
@xml:lang
intendedApplicationsLangUniqueConstraint
unique
common:intendedApplications
@xml:lang
Source
<xs:element name="commissionerAndGoal" type="CommissionerAndGoalType"><xs:annotation><xs:appinfo><ilcd:element id="" name="baseName"/><ilcd:display-name>Commissioner and goal</ilcd:display-name><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Basic information about goal and scope of the data set.</xs:documentation></xs:annotation><xs:unique name="projectLangUniqueConstraint"><xs:selector xpath="common:project"/><xs:field xpath="@xml:lang"/></xs:unique><xs:unique name="intendedApplicationsLangUniqueConstraint"><xs:selector xpath="common:intendedApplications"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
"Contact data set" of the commissioner / financing party of the data collection / compilation and of the data set modelling. For groups of commissioners,each single organisation should be named. For data set updates and for direct use of data from formerly commissioned studies, also the original commissioner should benamed.
<xs:element name="referenceToCommissioner" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-5-24-96" name="referenceToCommissioner"/><ilcd:display-name>Commissioner of data set</ilcd:display-name><ilcd:iso-field-id>3.4</ilcd:iso-field-id><ilcd:iso-field-name>Data commissioner</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"Contact data set" of the commissioner / financing party of the data collection / compilation and of the data set modelling. For groups of commissioners, each single organisation should be named. For data set updates and for direct use of data from formerly commissioned studies, also the original commissioner should be named.</xs:documentation></xs:annotation><xs:unique name="referenceToCommissionerShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
Project within which the data set was modelled in its present version. [Note: If the project was published e.g. as a report, this can be referenced in the"Publication of data set in:" field in the "Publication and ownership" sub-section.
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
Source
<xs:element name="project" type="StringMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-5-24-97" name="project"/><ilcd:display-name>Project</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>Project within which the data set was modelled in its present version. [Note: If the project was published e.g. as a report, this can be referenced in the "Publication of data set in:" field in the "Publication and ownership" sub-section.</xs:documentation></xs:annotation></xs:element>
Documentation of the intended application(s) of data collection and data set modelling. This indicates / includes information on the level of detail, thespecifidity, and the quality ambition in the effort.
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
Source
<xs:element name="intendedApplications" type="FTMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-5-24-98" name="intendedApplications"/><ilcd:display-name>Intended applications</ilcd:display-name><ilcd:iso-field-id>2.1</ilcd:iso-field-id><ilcd:iso-field-name>Intended application</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Documentation of the intended application(s) of data collection and data set modelling. This indicates / includes information on the level of detail, the specifidity, and the quality ambition in the effort.</xs:documentation></xs:annotation></xs:element>
Element referenceToPersonOrEntityGeneratingTheDataSet
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
"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 itscorrectness regarding methods, inventory, and documentative information.
<xs:element name="referenceToPersonOrEntityGeneratingTheDataSet" type="GlobalReferenceType"><xs:annotation><xs:appinfo><ilcd:element id="1-5-26-99" name="referenceToPersonOrEntityGeneratingTheDataSet"/><ilcd:display-name>Data set generator / modeller</ilcd:display-name><ilcd:iso-field-id>3.5</ilcd:iso-field-id><ilcd:iso-field-name>Data generator</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"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.</xs:documentation></xs:annotation><xs:unique name="referenceToPersonOrEntityGeneratingTheDataSetShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
<xs:element name="timeStamp" type="dateTime" minOccurs="0" maxOccurs="1"><xs:annotation><xs:appinfo><ilcd:element id="1-5-28-104" name="timeStamp"/><ilcd:display-name>Time stamp (last saved)</ilcd:display-name><ilcd:iso-field-id>3.7</ilcd:iso-field-id><ilcd:iso-field-name>Date completed</ilcd:iso-field-name><ilcd:field-motivation>t</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Date and time stamp of data set generation, typically an automated entry ("last saved").</xs:documentation></xs:annotation></xs:element>
"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 LCAformats, e.g. of other database networks or LCA softwares.
<xs:element name="referenceToDataSetFormat" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-5-28-105" name="referenceToDataSetFormat"/><ilcd:display-name>Data set format(s)</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>t</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"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.</xs:documentation></xs:annotation><xs:unique name="referenceToDataSetFormatShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
Element DataEntryByGroup2 / referenceToPersonOrEntityEnteringTheData
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
"Contact data set" of the responsible person or entity that has documented this data set, i.e. entered the data and the descriptiveinformation.
<xs:element name="referenceToPersonOrEntityEnteringTheData" type="GlobalReferenceType" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-28-103" name="referenceToPersonOrEntityEnteringTheData"/><ilcd:display-name>Data entry by:</ilcd:display-name><ilcd:iso-field-id>3.6</ilcd:iso-field-id><ilcd:iso-field-name>Data documentator</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>"Contact data set" of the responsible person or entity that has documented this data set, i.e. entered the data and the descriptive information.</xs:documentation></xs:annotation><xs:unique name="referenceToPersonOrEntityEnteringTheDataShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
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 threedigits are intended for automatic and internal counting of versions during data set development. Together with the data set's UUID, the "Data set version" uniquelyidentifies each data set.
<xs:element name="dataSetVersion" type="Version" minOccurs="1"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-111" name="dataSetVersion"/><ilcd:display-name>Data set version</ilcd:display-name><ilcd:iso-field-id>3.3</ilcd:iso-field-id><ilcd:iso-field-name>Version number</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>m</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element>
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 isgiven (or both).
<xs:element name="referenceToPrecedingDataSetVersion" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-112" name="referenceToPrecedingDataSetVersion"/><ilcd:display-name>Preceding data set version</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>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).</xs:documentation></xs:annotation><xs:unique name="referenceToPrecedingDataSetVersionShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
URI (i.e. an internet address) of the original of this data set. [Note: This equally globally unique identifier supports users and software tools toidentify 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 itshould 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.]
Diagram
Type
xs:anyURI
Properties
content
simple
minOccurs
0
Source
<xs:element name="permanentDataSetURI" type="xs:anyURI" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-300" name="permanentDataSetURI"/><ilcd:display-name>Permanent data set URI</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.]</xs:documentation></xs:annotation></xs:element>
Element referenceToOwnershipOfDataSet
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Quality compliance of this data set with the respective requirements set by the "compliance system" refered to.
<xs:element name="referenceToOwnershipOfDataSet" type="GlobalReferenceType"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-115" name="referenceToOwnershipOfDataSet"/><ilcd:display-name>Owner of data set</ilcd:display-name><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Quality compliance of this data set with the respective requirements set by the "compliance system" refered to.</xs:documentation></xs:annotation><xs:unique name="referenceToOwnershipOfDataSetShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
Element copyright
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
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 userestrictions".]
<xs:element name="copyright" type="boolean"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-116" name="copyright"/><ilcd:display-name>Copyright?</ilcd:display-name><ilcd:iso-field-id>3.9</ilcd:iso-field-id><ilcd:iso-field-name>Copyright</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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".]</xs:documentation></xs:annotation></xs:element>
"Contact data set" of those entities or persons (or groups of these), to which an exclusive access to this data set is granted. Mainly intended to be usedin confidentiality management in projects. [Note: See also field "Access and use restrictions".]
<xs:element name="referenceToEntitiesWithExclusiveAccess" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-117" name="referenceToEntitiesWithExclusiveAccess"/><ilcd:display-name>Entities or persons with exclusive access to this data set</ilcd:display-name><ilcd:iso-field-id>(3.10)</ilcd:iso-field-id><ilcd:iso-field-name>(Access restrictions)</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>"Contact data set" of those entities or persons (or groups of these), to which an exclusive access to this data set is granted. Mainly intended to be used in confidentiality management in projects. [Note: See also field "Access and use restrictions".]</xs:documentation></xs:annotation><xs:unique name="referenceToEntitiesWithExclusiveAccessShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
This data set can be freely accessed and used by all user types and for all uses, including for commercial purposes
enumeration
Free of charge for some user types or use types
This data set can be accessed free of charge for certain user types, such as academic institutions, students, publicadministration/government, etc., or for certain types of uses, e.g. not-for-profit. Details and license conditions are to be obtained from the "Data setowner" or electronically via the "Permanent URI", if implemented by data owner. Also see "Access and use restrictions".
enumeration
Free of charge for members only
Data set is accessible free of charge only for members. Membership itself must be for free, while not all user types may be able to becomemember. Membership conditions are to be obtained from the "Data set owner" or electronically via the "Permanent URI", if implemented by data owner. Also see"Access and use restrictions".
enumeration
License fee
Data set is accessible for a license fee. This can be a fee per data set, for a group of data sets, a whole database, or for obtaining amembership to get access to the data. Details and license conditions are to be obtained from the "Data set owner" or electronically via the "Permanent URI",if implemented by data owner. Also see "Access and use restrictions".
enumeration
Other
Another license type applies. Details are given in "Access and use restrictions".
Source
<xs:element name="licenseType" type="LicenseTypeValues" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-119" name="licenseType"/><ilcd:display-name>License type</ilcd:display-name><ilcd:iso-field-id>(3.10)</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Type of license that applies to the access and use of this data set.</xs:documentation></xs:annotation></xs:element>
Element accessRestrictions
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Access restrictions / use conditions for this data set as free text or referring to e.g. license conditions. In case of no restrictions "None" isentered.
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
Source
<xs:element name="accessRestrictions" type="FTMultiLang"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-118" name="accessRestrictions"/><ilcd:display-name>Access and use restrictions</ilcd:display-name><ilcd:iso-field-id>3.10</ilcd:iso-field-id><ilcd:iso-field-name>Access restrictions</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element>
Data quality indicators serve to provide the reviewed key information on the data set in a defined, computer-readable (and hence searchable) form. Thisserves to support LCA practitioners to identify/select the highest quality and most appropriate data sets.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:element name="dataQualityIndicator" type="DataQualityIndicatorType" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-91" name="dataQualityIndicator"/><ilcd:display-name>Data quality indicator</ilcd:display-name><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Data quality indicators serve to provide the reviewed key information on the data set in a defined, computer-readable (and hence searchable) form. This serves to support LCA practitioners to identify/select the highest quality and most appropriate data sets.</xs:documentation></xs:annotation></xs:element>
Unique identifier of the category. [Note: May be used by LCA software for it's category system. If used the identifer should be identical to the ondefined in the referenced category file. Identifiers can be UUIDs, but also other forms are possible.]
Hierarchy level (1,2,...), if the categorization system is hierachical, otherwise emtpy or not used.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:element name="category" type="CategoryType" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-1" name="category"/><ilcd:display-name>Category name</ilcd:display-name><ilcd:iso-field-id>(1.1.2)</ilcd:iso-field-id><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of the category of this elementary flow.</xs:documentation></xs:annotation></xs:element>
URL or file name of a file containing all categories of this categorization system. [Note: The file is to be in form of the "ILCDCategories.xml" format.If a category file is specified, only categories of the referenced categories file should be used.]
Name of the categorization system. E.g. "ILCD 1.1" or another elementary flow categorization/compartment scheme applied, as defined e.g. in other LCAdatabase (systems).
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Identity constraints
QName
Type
Refer
Selector
Field(s)
FlowClassificationLevelUniqueConstraint
unique
common:category
@level
Source
<xs:element name="elementaryFlowCategorization" type="FlowCategorizationType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144" name="elementaryFlowCategorization"/><ilcd:display-name>Elementary flow categorization</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name/><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Identifying category/compartment information exclusively used for elementary flows. E.g. "Emission to air", "Renewable resource", etc.</xs:documentation></xs:annotation><xs:unique name="FlowClassificationLevelUniqueConstraint"><xs:selector xpath="common:category"/><xs:field xpath="@level"/></xs:unique></xs:element>
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 classificationfile.]
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Identity constraints
QName
Type
Refer
Selector
Field(s)
ClassificationLevelUniqueConstraint2
unique
common:class
@level
Source
<xs:element name="classification" type="ClassificationType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-145" name="classification"/><ilcd:display-name>Classification</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Optional statistical or other classification of the data set. Typically also used for structuring LCA databases.</xs:documentation></xs:annotation><xs:unique name="ClassificationLevelUniqueConstraint2"><xs:selector xpath="common:class"/><xs:field xpath="@level"/></xs:unique></xs:element>
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 differentyears, the most representative year is given regarding the overall environmental impact. In that case, the reference year is derived by expertjudgement.
<xs:element name="referenceYear" type="Year" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-1-6-18" name="referenceYear"/><ilcd:display-name>Reference year</ilcd:display-name><ilcd:iso-field-id>1.1.7.1</ilcd:iso-field-id><ilcd:iso-field-name>Start date</ilcd:iso-field-name><ilcd:field-motivation>t</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element>
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 backgroundsystem.
<xs:element name="dataSetValidUntil" type="Year" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-1-6-19" name="dataSetValidUntil"/><ilcd:display-name>Data set valid until:</ilcd:display-name><ilcd:iso-field-id>1.1.7.2</ilcd:iso-field-id><ilcd:iso-field-name>End date</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element>
Element TimeType / timeRepresentativenessDescription
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Description of the valid time span of the data set including information on limited usability within sub-time spans (e.g.summer/winter).
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
Source
<xs:element name="timeRepresentativenessDescription" type="FTMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-1-6-20" name="timeRepresentativenessDescription"/><ilcd:display-name>Time representativeness description</ilcd:display-name><ilcd:iso-field-id>1.1.7.3</ilcd:iso-field-id><ilcd:iso-field-name>Time span description</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Description of the valid time span of the data set including information on limited usability within sub-time spans (e.g. summer/winter).</xs:documentation></xs:annotation></xs:element>
Data set is in preliminary status of on-going development.
enumeration
Final draft for internal review
Data set is finished and ready for internal review.
enumeration
Final draft for external review
Data set is ready for an external review (after a potential internal review and correction if required).
enumeration
Data set finalised; unpublished
Data set is finalised (with or without an internal and/or external review and correction if required), but it is not or not yetpublished.
enumeration
Under revision
Data set is under revision and the publication of the revised data set is foreseen.
enumeration
Withdrawn
Data set has been withdrawn and must not be used anymore. For details contact the "Data set owner".
enumeration
Data set finalised; subsystems published
Data set is finalised (with or without an internal and/or external review and correction if required), and sub-system(s) / included processeshave been published.
enumeration
Data set finalised; entirely published
Data set is finalised (with or without an internal and/or external review and correction if required), and was entirelypublished.
Source
<xs:element name="workflowAndPublicationStatus" type="WorkflowAndPublicationStatusValues" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-110" name="workflowAndPublicationStatus"/><ilcd:display-name>Workflow and publication status</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>Workflow or publication status of data set. Details e.g. of foreseen publication dates should be provided on request by the "Data set owner".</xs:documentation></xs:annotation></xs:element>
"Source data set" of the publication, in which this data set was published for the first time. [Note: This refers to exactly this data set as it is,without any format conversion, adjustments, flow name mapping, etc. In case this data set was modified/converted, the original source is documented in "Convertedoriginal data set from:" in section "Data entry by".]
<xs:element name="referenceToUnchangedRepublication" type="GlobalReferenceType" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-114" name="referenceToUnchangedRepublication"/><ilcd:display-name>Unchanged re-publication of:</ilcd:display-name><ilcd:iso-field-id>3.8</ilcd:iso-field-id><ilcd:iso-field-name>Publication</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>"Source data set" of the publication, in which this data set was published for the first time. [Note: This refers to exactly this data set as it is, without any format conversion, adjustments, flow name mapping, etc. In case this data set was modified/converted, the original source is documented in "Converted original data set from:" in section "Data entry by".]</xs:documentation></xs:annotation><xs:unique name="referenceToPublicationShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
Scope of review regarding which aspects and components of the data set was reviewed or verified. In case of aggregated e.g. LCI results also and on whichlevel of detail (e.g. LCI results only, included unit processes, ...) the review / verification was performed.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Identity constraints
QName
Type
Refer
Selector
Field(s)
Method
unique
common:method
@name
Source
<xs:element name="scope" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-82" name="scope"/><ilcd:display-name>Scope of review</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Scope of review regarding which aspects and components of the data set was reviewed or verified. In case of aggregated e.g. LCI results also and on which level of detail (e.g. LCI results only, included unit processes, ...) the review / verification was performed.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="method" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-83" name="method"/><ilcd:display-name>Method(s) of review</ilcd:display-name><ilcd:iso-field-id>2.6.1</ilcd:iso-field-id><ilcd:iso-field-name>Method</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Validation method(s) used in the respective "Scope of review".</xs:documentation></xs:annotation><xs:complexType><xs:attribute name="name" type="MethodOfReviewValues" use="required"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-83-1" name="name"/><ilcd:display-name>Method name</ilcd:display-name><ilcd:iso-field-id>2.6.1</ilcd:iso-field-id><ilcd:iso-field-name>Method</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Method name</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType></xs:element></xs:sequence><xs:attribute name="name" type="ScopeOfReviewValues" use="required"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-82-1" name="name"/><ilcd:display-name>Scope name</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation/></xs:annotation></xs:attribute><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType><xs:unique name="Method"><xs:selector xpath="common:method"/><xs:field xpath="@name"/></xs:unique></xs:element>
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:element name="method" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-83" name="method"/><ilcd:display-name>Method(s) of review</ilcd:display-name><ilcd:iso-field-id>2.6.1</ilcd:iso-field-id><ilcd:iso-field-name>Method</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Validation method(s) used in the respective "Scope of review".</xs:documentation></xs:annotation><xs:complexType><xs:attribute name="name" type="MethodOfReviewValues" use="required"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-83-1" name="name"/><ilcd:display-name>Method name</ilcd:display-name><ilcd:iso-field-id>2.6.1</ilcd:iso-field-id><ilcd:iso-field-name>Method</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Method name</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType></xs:element>
Summary of the review. All the following items should be explicitly addressed: Representativeness, completeness, and precision of Inputs and Outputs forthe process in its documented location, technology and time i.e. both completeness of technical model (product, waste, and elementary flows) and completeness ofcoverage of the relevant problem fields (environmental, human health, resource use) for this specific good, service, or process. Plausibility of data. Correctness andappropriateness of the data set documentation. Appropriateness of system boundaries, cut-off rules, LCI modelling choices such as e.g. allocation, consistency ofincluded processes and of LCI methodology. If the data set comprises pre-calculated LCIA results, the correspondence of the Input and Output elementary flows (includingtheir geographical validity) with the applied LCIA method(s) should be addressed by the reviewer. An overall quality statement on the data set may be includedhere.
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
Source
<xs:element name="reviewDetails" type="FTMultiLang"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-84" name="reviewDetails"/><ilcd:display-name>Review details</ilcd:display-name><ilcd:iso-field-id>(2.6.2) and (2.6.3)</ilcd:iso-field-id><ilcd:iso-field-name>(Procedure), (Result)</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element>
Element dateOfLastRevision
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Date when the data set was revised for the last time, typically manually set.
<xs:element name="dateOfLastRevision" type="dateTime"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-113" name="dateOfLastRevision"/><ilcd:display-name>Date of last revision</ilcd:display-name><ilcd:iso-field-id>3.3</ilcd:iso-field-id><ilcd:iso-field-name>Version number</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Date when the data set was revised for the last time, typically manually set.</xs:documentation></xs:annotation></xs:element>
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
"Source data set" of source(s) where the raw data of the Process is documented. (External data sources used for deriving the (final) raw data areidentified in the field "Data sources used for this data set" in the section "Data sources, treatment and representativeness".)
<xs:element name="referenceToRawDataDocumentation" type="GlobalReferenceType"><xs:annotation><xs:appinfo><ilcd:element id="1-5-26-101" name="referenceToRawDataDocumentation"/><ilcd:display-name>Raw data documentation</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>"Source data set" of source(s) where the raw data of the Process is documented. (External data sources used for deriving the (final) raw data are identified in the field "Data sources used for this data set" in the section "Data sources, treatment and representativeness".)</xs:documentation></xs:annotation><xs:unique name="referenceToRawDataDocumentationShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element>
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string.
<xs:complexType name="ClassificationInformationType"><xs:sequence><xs:element name="classification" type="ClassificationType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2" name="classification"/><ilcd:display-name>Classification</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Optional statistical or other classification of the data set. Typically also used for structuring LCA databases.</xs:documentation></xs:annotation><xs:unique name="ClassificationLevelUniqueConstraint"><xs:selector xpath="common:class"/><xs:field xpath="@level"/></xs:unique></xs:element></xs:sequence></xs:complexType>
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 classificationfile.]
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:complexType name="ClassificationType"><xs:sequence><xs:element name="class" maxOccurs="unbounded" type="ClassType"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-1" name="class"/><ilcd:display-name>Class name</ilcd:display-name><ilcd:iso-field-id>(1.1.2)</ilcd:iso-field-id><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of the class.</xs:documentation></xs:annotation></xs:element><xs:element ref="other" maxOccurs="1" minOccurs="0"/></xs:sequence><xs:attribute name="name" type="xs:string" default="ILCD"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-a" name="name"/><ilcd:display-name>Classification system name</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of the classification system.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="classes" type="xs:anyURI"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-b" name="classes"/><ilcd:display-name>Classes</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.]</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute processContents="lax" namespace="##other"/></xs:complexType>
Unique identifier for the class. [Notes: If such identifiers are also defined in the referenced category file, they should be identical. Identifiers canbe UUID's, but also other forms are allowed.]
If more than one class is specified in a hierachical classification system, the hierarchy level (1,2,...) could be specified with this attribute ofclass.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:complexType name="ClassType"><xs:simpleContent><xs:extension base="xs:string"><xs:attribute name="level" type="LevelType" use="required"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-1-a" name="level"/><ilcd:display-name>Hierarchy level</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="classId" type="xs:string"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-1-b" name="classId"/><ilcd:display-name>Unique class identifier</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.]</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute processContents="lax" namespace="##other"/></xs:extension></xs:simpleContent></xs:complexType>
Complex Type GlobalReferenceType
Namespace
http://lca.jrc.it/ILCD/Common
Annotations
Represents a reference to another dataset or file. Either refObjectId and version, or uri, or both have to be specified.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:complexType name="GlobalReferenceType"><xs:annotation><xs:documentation>Represents a reference to another dataset or file. Either refObjectId and version, or uri, or both have to be specified.</xs:documentation></xs:annotation><xs:sequence><xs:element name="subReference" type="String" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:documentation>Valid only for references of type "source data set". Allows to make references to sections, pages etc. within a source.</xs:documentation></xs:annotation></xs:element><xs:element name="shortDescription" type="STMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:documentation>Short, clear-text summary of the referenced object that can be used as a hint what to expect behind the reference in cases where it cannot be resolved.</xs:documentation></xs:annotation></xs:element><xs:element ref="other" minOccurs="0" maxOccurs="1"/></xs:sequence><xs:attribute name="type" type="GlobalReferenceTypeValues" use="required"><xs:annotation><xs:documentation>(required) - indicates the type of the referenced dataset/file. One of GlobalReferenceTypeValues.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="refObjectId" type="UUID" use="optional"><xs:annotation><xs:documentation>UUID of the referenced object</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="version" type="Version" use="optional"><xs:annotation><xs:documentation>version number of the referenced object</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="uri" type="xs:anyURI" use="optional"><xs:annotation><xs:documentation>URI of the referenced object</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType>
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:complexType name="CommissionerAndGoalType" mixed="false"><xs:sequence><xs:element name="referenceToCommissioner" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-5-24-96" name="referenceToCommissioner"/><ilcd:display-name>Commissioner of data set</ilcd:display-name><ilcd:iso-field-id>3.4</ilcd:iso-field-id><ilcd:iso-field-name>Data commissioner</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"Contact data set" of the commissioner / financing party of the data collection / compilation and of the data set modelling. For groups of commissioners, each single organisation should be named. For data set updates and for direct use of data from formerly commissioned studies, also the original commissioner should be named.</xs:documentation></xs:annotation><xs:unique name="referenceToCommissionerShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element><xs:element name="project" type="StringMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-5-24-97" name="project"/><ilcd:display-name>Project</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>Project within which the data set was modelled in its present version. [Note: If the project was published e.g. as a report, this can be referenced in the "Publication of data set in:" field in the "Publication and ownership" sub-section.</xs:documentation></xs:annotation></xs:element><xs:element name="intendedApplications" type="FTMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-5-24-98" name="intendedApplications"/><ilcd:display-name>Intended applications</ilcd:display-name><ilcd:iso-field-id>2.1</ilcd:iso-field-id><ilcd:iso-field-name>Intended application</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Documentation of the intended application(s) of data collection and data set modelling. This indicates / includes information on the level of detail, the specifidity, and the quality ambition in the effort.</xs:documentation></xs:annotation></xs:element><xs:element ref="other" minOccurs="0" maxOccurs="1"/></xs:sequence><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType>
Unique identifier of the category. [Note: May be used by LCA software for it's category system. If used the identifer should be identical to the ondefined in the referenced category file. Identifiers can be UUIDs, but also other forms are possible.]
Hierarchy level (1,2,...), if the categorization system is hierachical, otherwise emtpy or not used.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:complexType name="CategoryType"><xs:simpleContent><xs:extension base="String"><xs:attribute name="level" type="LevelType" use="required"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-1-a" name="level"/><ilcd:display-name>Hierarchy level</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Hierarchy level (1,2,...), if the categorization system is hierachical, otherwise emtpy or not used.</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="catId" type="xs:string"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-1-b" name="catId"/><ilcd:display-name>Unique category identifier</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Unique identifier of the category. [Note: May be used by LCA software for it's category system. If used the identifer should be identical to the on defined in the referenced category file. Identifiers can be UUIDs, but also other forms are possible.]</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute namespace="##other" processContents="lax"/></xs:extension></xs:simpleContent></xs:complexType>
<xs:complexType name="DataQualityIndicatorsType"><xs:sequence><xs:element name="dataQualityIndicator" type="DataQualityIndicatorType" minOccurs="1" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-91" name="dataQualityIndicator"/><ilcd:display-name>Data quality indicator</ilcd:display-name><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Data quality indicators serve to provide the reviewed key information on the data set in a defined, computer-readable (and hence searchable) form. This serves to support LCA practitioners to identify/select the highest quality and most appropriate data sets.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:complexType>
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:complexType name="DataQualityIndicatorType"><xs:attribute name="name" use="required" type="DataQualityIndicatorValues"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-91-1" name="name"/><ilcd:display-name>Name of data quality indicator</ilcd:display-name><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of indicator</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="value" use="required" type="QualityValues"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-91-2" name="value"/><ilcd:display-name>Value of data quality indicator</ilcd:display-name><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Value of indicator</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType>
URL or file name of a file containing all categories of this categorization system. [Note: The file is to be in form of the "ILCDCategories.xml" format.If a category file is specified, only categories of the referenced categories file should be used.]
Name of the categorization system. E.g. "ILCD 1.1" or another elementary flow categorization/compartment scheme applied, as defined e.g. in other LCAdatabase (systems).
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:complexType name="FlowCategorizationType"><xs:sequence><xs:element name="category" type="CategoryType" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-1" name="category"/><ilcd:display-name>Category name</ilcd:display-name><ilcd:iso-field-id>(1.1.2)</ilcd:iso-field-id><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of the category of this elementary flow.</xs:documentation></xs:annotation></xs:element><xs:element ref="other" minOccurs="0" maxOccurs="1"/></xs:sequence><xs:attribute name="name" type="xs:string" default="ILCD"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-a" name="name"/><ilcd:display-name>Name of categorization system</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of the categorization system. E.g. "ILCD 1.1" or another elementary flow categorization/compartment scheme applied, as defined e.g. in other LCA database (systems).</xs:documentation></xs:annotation></xs:attribute><xs:attribute name="categories" type="xs:anyURI"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-b" name="categories"/><ilcd:display-name>Categories file</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>URL or file name of a file containing all categories of this categorization system. [Note: The file is to be in form of the "ILCDCategories.xml" format. If a category file is specified, only categories of the referenced categories file should be used.]</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType>
<xs:complexType name="FlowCategoryInformationType"><xs:sequence><xs:element name="elementaryFlowCategorization" type="FlowCategorizationType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144" name="elementaryFlowCategorization"/><ilcd:display-name>Elementary flow categorization</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name/><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Identifying category/compartment information exclusively used for elementary flows. E.g. "Emission to air", "Renewable resource", etc.</xs:documentation></xs:annotation><xs:unique name="FlowClassificationLevelUniqueConstraint"><xs:selector xpath="common:category"/><xs:field xpath="@level"/></xs:unique></xs:element><xs:element name="classification" type="ClassificationType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-145" name="classification"/><ilcd:display-name>Classification</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Optional statistical or other classification of the data set. Typically also used for structuring LCA databases.</xs:documentation></xs:annotation><xs:unique name="ClassificationLevelUniqueConstraint2"><xs:selector xpath="common:class"/><xs:field xpath="@level"/></xs:unique></xs:element></xs:sequence></xs:complexType>
Geographical latitude and longitude reference of "Location" / "Sub-location". For area-type locations (e.g. countries, continents) the field isempty.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:complexType name="LocationType"><xs:simpleContent><xs:extension base="common:String"><xs:attribute name="latitudeAndLongitude" type="GIS" use="optional"><xs:annotation><xs:appinfo><ilcd:element id="1-1-8-23" name="latitudeAndLongitude"/><ilcd:display-name>Latitude and Longitude</ilcd:display-name><ilcd:iso-field-id>1.1.8.4</ilcd:iso-field-id><ilcd:iso-field-name>GIS reference</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>Geographical latitude and longitude reference of "Location" / "Sub-location". For area-type locations (e.g. countries, continents) the field is empty.</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute processContents="lax" namespace="##other"/></xs:extension></xs:simpleContent></xs:complexType>
Wildcard: ANY attribute from ANY namespace OTHER than 'http://lca.jrc.it/ILCD/Common'
Source
<xs:complexType name="TimeType" mixed="false"><xs:sequence><xs:element name="referenceYear" type="Year" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-1-6-18" name="referenceYear"/><ilcd:display-name>Reference year</ilcd:display-name><ilcd:iso-field-id>1.1.7.1</ilcd:iso-field-id><ilcd:iso-field-name>Start date</ilcd:iso-field-name><ilcd:field-motivation>t</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element><xs:element name="dataSetValidUntil" type="Year" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-1-6-19" name="dataSetValidUntil"/><ilcd:display-name>Data set valid until:</ilcd:display-name><ilcd:iso-field-id>1.1.7.2</ilcd:iso-field-id><ilcd:iso-field-name>End date</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element><xs:element name="timeRepresentativenessDescription" type="FTMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-1-6-20" name="timeRepresentativenessDescription"/><ilcd:display-name>Time representativeness description</ilcd:display-name><ilcd:iso-field-id>1.1.7.3</ilcd:iso-field-id><ilcd:iso-field-name>Time span description</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Description of the valid time span of the data set including information on limited usability within sub-time spans (e.g. summer/winter).</xs:documentation></xs:annotation></xs:element><xs:element ref="other" minOccurs="0" maxOccurs="1"/></xs:sequence><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType>
If more than one class is specified in a hierachical classification system, the hierarchy level (1,2,...) could be specified with this attribute ofclass.
<xs:attribute name="level" type="LevelType" use="required"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-1-a" name="level"/><ilcd:display-name>Hierarchy level</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:attribute>
Unique identifier for the class. [Notes: If such identifiers are also defined in the referenced category file, they should be identical. Identifiers canbe UUID's, but also other forms are allowed.]
<xs:attribute name="classId" type="xs:string"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-1-b" name="classId"/><ilcd:display-name>Unique class identifier</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.]</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="name" type="xs:string" default="ILCD"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-a" name="name"/><ilcd:display-name>Classification system name</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of the classification system.</xs:documentation></xs:annotation></xs:attribute>
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 classificationfile.]
<xs:attribute name="classes" type="xs:anyURI"><xs:annotation><xs:appinfo><ilcd:element id="1-1-2-7-2-b" name="classes"/><ilcd:display-name>Classes</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.]</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="type" type="GlobalReferenceTypeValues" use="required"><xs:annotation><xs:documentation>(required) - indicates the type of the referenced dataset/file. One of GlobalReferenceTypeValues.</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="refObjectId" type="UUID" use="optional"><xs:annotation><xs:documentation>UUID of the referenced object</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="version" type="Version" use="optional"><xs:annotation><xs:documentation>version number of the referenced object</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="uri" type="xs:anyURI" use="optional"><xs:annotation><xs:documentation>URI of the referenced object</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="level" type="LevelType" use="required"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-1-a" name="level"/><ilcd:display-name>Hierarchy level</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Hierarchy level (1,2,...), if the categorization system is hierachical, otherwise emtpy or not used.</xs:documentation></xs:annotation></xs:attribute>
Unique identifier of the category. [Note: May be used by LCA software for it's category system. If used the identifer should be identical to the ondefined in the referenced category file. Identifiers can be UUIDs, but also other forms are possible.]
<xs:attribute name="catId" type="xs:string"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-1-b" name="catId"/><ilcd:display-name>Unique category identifier</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Unique identifier of the category. [Note: May be used by LCA software for it's category system. If used the identifer should be identical to the on defined in the referenced category file. Identifiers can be UUIDs, but also other forms are possible.]</xs:documentation></xs:annotation></xs:attribute>
Degree to which the data set reflects the true population of interest regarding technology, including for included background data sets, ifany.
enumeration
Time representativeness
Degree to which the data set reflects the true population of interest regarding time / age of the data, including for included background datasets, if any.
enumeration
Geographical representativeness
Degree to which the data set reflects the true population of interest regarding geography such as e.g. country or site, including for includedbackground data sets, if any.
enumeration
Completeness
Share of (elementary) flows that are quantitatively included in the inventory. Note that also the completeness of interim product and wasteflows in the product model contributes to the overall completeness of the inventory.
enumeration
Precision
Measure of the variability of the data values for each data expressed (e.g. low variance = high precision).
enumeration
Methodological appropriateness and consistency
The applied LCI methods and methodological choices (e.g. allocation, substitution, etc.) are in line with the goal and scope of the data set,especially its intended applications and decision support context (e.g. monitoring, product-specific decision support, strategic long-term decisionsupport). The methods also have been consistently applied across all data including for included processes, if any.
enumeration
Overall quality
The degree to which the data set’s overall representativeness, completeness, precision as well as methodological appropriateness andconsistency reflects the reality the data set is representing.
<xs:attribute name="name" use="required" type="DataQualityIndicatorValues"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-91-1" name="name"/><ilcd:display-name>Name of data quality indicator</ilcd:display-name><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of indicator</xs:documentation></xs:annotation></xs:attribute>
Meets the criterium to a very high degree, having or no relevant need for improvement. This is to be judged in view of the criterium'scontribution to the data set's potential overall environmental impact and in comparison to an ideal situation.
enumeration
Good
Meets the criterium to a high degree, having little yet significant need for improvement. This is to be judged in view of the criterium'scontribution to the data set's potential overall environmental impact and in comparison to an ideal situation.
enumeration
Fair
Meets the criterium to a still sufficient degree, while having the need for improvement. This is to be judged in view of the criterium'scontribution to the data set's potential overall environmental impact and in comparison to an ideal situation.
enumeration
Poor
Does not meet the criterium to a sufficient degree, having the need for relevant improvement. This is to be judged in view of the criterium'scontribution to the data set's potential overall environmental impact and in comparison to an ideal situation.
enumeration
Very poor
Does not at all meet the criterium, having the need for very substantial improvement. This is to be judged in view of the criterium'scontribution to the data set's potential overall environmental impact and in comparison to an ideal situation.
enumeration
Not evaluated / unknown
This criterium was not reviewed or its quality could not be verified.
enumeration
Not applicable
This criterium is not applicable to this data set, e.g. its geographical representative can not be evaluated as it is a location-unspecifictechnology unit process.
<xs:attribute name="value" use="required" type="QualityValues"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-91-2" name="value"/><ilcd:display-name>Value of data quality indicator</ilcd:display-name><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Value of indicator</xs:documentation></xs:annotation></xs:attribute>
Name of the categorization system. E.g. "ILCD 1.1" or another elementary flow categorization/compartment scheme applied, as defined e.g. in other LCAdatabase (systems).
<xs:attribute name="name" type="xs:string" default="ILCD"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-a" name="name"/><ilcd:display-name>Name of categorization system</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Name of the categorization system. E.g. "ILCD 1.1" or another elementary flow categorization/compartment scheme applied, as defined e.g. in other LCA database (systems).</xs:documentation></xs:annotation></xs:attribute>
URL or file name of a file containing all categories of this categorization system. [Note: The file is to be in form of the "ILCDCategories.xml" format.If a category file is specified, only categories of the referenced categories file should be used.]
<xs:attribute name="categories" type="xs:anyURI"><xs:annotation><xs:appinfo><ilcd:element id="2-9-36-144-b" name="categories"/><ilcd:display-name>Categories file</ilcd:display-name><ilcd:iso-field-id/><ilcd:iso-field-name>(Class)</ilcd:iso-field-name><ilcd:field-motivation>u</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>URL or file name of a file containing all categories of this categorization system. [Note: The file is to be in form of the "ILCDCategories.xml" format. If a category file is specified, only categories of the referenced categories file should be used.]</xs:documentation></xs:annotation></xs:attribute>
<xs:attribute name="latitudeAndLongitude" type="GIS" use="optional"><xs:annotation><xs:appinfo><ilcd:element id="1-1-8-23" name="latitudeAndLongitude"/><ilcd:display-name>Latitude and Longitude</ilcd:display-name><ilcd:iso-field-id>1.1.8.4</ilcd:iso-field-id><ilcd:iso-field-name>GIS reference</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>Geographical latitude and longitude reference of "Location" / "Sub-location". For area-type locations (e.g. countries, continents) the field is empty.</xs:documentation></xs:annotation></xs:attribute>
Analysis of all data sources declared, checking their context-specific correct use as well as their relevance and quality.
enumeration
Sample tests on calculations
Values in the inventory are re-calculated from the raw data, or other calculations are validated exemplarily, e.g. scaling, averaging, summing up,stochiometric calculations, formulas in the mathematical models, etc.
enumeration
Energy balance
The energy balance (e.g. gross or net calorific value or exergy) of the Inputs and Outputs is validated. [Note: For processes that have undergoneallocation or consequential modeling the value of this review method is limited.]
enumeration
Element balance
The balance of the relevant chemical elements of the Inputs and Outputs is calculated and validated. The validated elements should be named in thereview comments. [Note: For processes that have undergone allocation or consequential modeling the value of this review method is limited.]
enumeration
Cross-check with other source
Comparison with other, independent data and/or information sources (can be both database and literature).
enumeration
Cross-check with other data set
Comparison with similar process or product system from the same or from other sources (can be both database and literature).
enumeration
Expert judgement
Analysis by means of expert opinions. The expert(s) have methodological and detailed technical expertise on the item to be verified and the processor product system in question.
enumeration
Mass balance
The mass balance of the Inputs and Outputs is validated. [Note: For processes that have undergone allocation or consequential modeling the value ofthis review method is limited.]
enumeration
Compliance with legal limits
Regulated Inputs and Outputs e.g. emission data are validated for compliance with legal limits, typically after relating and scaling the data tothe regulated processes/sites etc.
enumeration
Compliance with ISO 14040 to 14044
Methodological compliance with ISO 14040 to 14044 was checked by an LCA expert.
enumeration
Documentation
Evidence collection by means of documentation (e.g. data set's meta data, background report)
enumeration
Evidence collection by means of plant visits and/or interviews
Interviews and/or plant visits are performed to validate data and other informtion, tyically in case of inconsistencies, uncertainties, or doubts.People interviewed have detailed technical expertise on the analysed process(es).
Review/verification is done on basis of the original "raw data", i.e. the data before it was scaled, converted, or treated in other ways to be usedfor modelling of a unit process.
enumeration
Unit process(es), single operation
The review is done on the level of the "Unit operation type unit process(es)" that can not be further subdivided. Covers multi-functional processesof unit operation type.
enumeration
Unit process(es), black box
The review is done on the level of process-chain(s) or plant level unit process(es). This covers horizontally averaged unit processes acrossdifferent sites. Covers also those multi-functional unit processes, where the different co-products undergo different processing steps within the blackbox.
enumeration
LCI results or Partly terminated system
The LCI result or Partly terminated system is the level of review/verification.
enumeration
LCIA results
The LCIA results of the LCI result or Partly terminated system data set are reviewed/verified, i.e. on level of Climate Change potential, Primaryenergy consumption, Ecosystem damage etc. [Note: see also definition for entry "LCIA results calculation".]
enumeration
Documentation
The reporting/documentation of the process or product system, i.e. the data set's sections "Process description", Modelling and validation" and"Administrative information" have been reviewed, while this does not include the "Inputs/Outputs". This can include a review of detailed backgroundreports.
enumeration
Life cycle inventory methods
The application of the LCI method(s) in accordance to the goal and scope have been reviewed. This covers data collection including dealing withmissing data, data calculation/modelling principles (e.g. consequential or attributional or other/combination), and the application of the related modellingapproaches such as allocation and system expansion etc. for the process / throughout the product system.
enumeration
LCIA results calculation
The selection and application of the LCIA method(s) that have been used for calculation of the LCIA results have been reviewed. This especiallyrefers to a correspondance of the elementary flows in the Inputs and Outputs of the product system with the once referenced by the applied LCIA method(s)regarding e.g. correct assignment, coverage/gaps, doublecounting, etc. [Note: See also definition for entry "LCIA results".]
enumeration
Goal and scope definition
Review/verification is done regarding e.g. goal definition, subsequent scope definition and corresponding product system description, appropriateidentification and definition of function and functional unit, system boundary and cut-off criteria setting, choice of appropriate LCI modelling principles andapproaches for multi-functional processes.
<xs:group name="ValidationGroup3"><xs:sequence><xs:element name="referenceToNameOfReviewerAndInstitution" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-87" name="referenceToNameOfReviewerAndInstitution"/><ilcd:display-name>Reviewer name and institution</ilcd:display-name><ilcd:iso-field-id>2.6.4</ilcd:iso-field-id><ilcd:iso-field-name>Validator</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"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.</xs:documentation></xs:annotation><xs:unique name="referenceToNameOfReviewerAndInstitutionShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element><xs:element name="otherReviewDetails" type="FTMultiLang" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-88" name="otherReviewDetails"/><ilcd:display-name>Subsequent review comments</ilcd:display-name><ilcd:iso-field-id>(2.6.2) and (2.6.3)</ilcd:iso-field-id><ilcd:iso-field-name>(Procedure), (Result)</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>Further information from the review process, especially comments received from third parties once the data set has been published or additional reviewer comments from an additional external review.</xs:documentation></xs:annotation></xs:element><xs:element name="referenceToCompleteReviewReport" type="GlobalReferenceType" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-89" name="referenceToCompleteReviewReport"/><ilcd:display-name>Complete review report</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"Source data set" of the complete review report.</xs:documentation></xs:annotation><xs:unique name="referenceToCompleteReviewReportShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element></xs:sequence></xs:group>
<xs:group name="ComplianceGroup"><xs:sequence><xs:element name="referenceToComplianceSystem" type="GlobalReferenceType" minOccurs="1"><xs:annotation><xs:appinfo><ilcd:element id="1-3-22-90" name="referenceToComplianceSystem"/><ilcd:display-name>Compliance system name</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"Source data set" of the "Compliance system" that is declared to be met by the data set.</xs:documentation></xs:annotation><xs:unique name="referenceToComplianceSystemShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element><xs:element name="approvalOfOverallCompliance" type="ComplianceValues" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-3-22-95" name="approvalOfOverallCompliance"/><ilcd:display-name>Approval of overall compliance</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>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".</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:group>
<xs:group name="DataEntryByGroup1"><xs:sequence><xs:element name="timeStamp" type="dateTime" minOccurs="0" maxOccurs="1"><xs:annotation><xs:appinfo><ilcd:element id="1-5-28-104" name="timeStamp"/><ilcd:display-name>Time stamp (last saved)</ilcd:display-name><ilcd:iso-field-id>3.7</ilcd:iso-field-id><ilcd:iso-field-name>Date completed</ilcd:iso-field-name><ilcd:field-motivation>t</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Date and time stamp of data set generation, typically an automated entry ("last saved").</xs:documentation></xs:annotation></xs:element><xs:element name="referenceToDataSetFormat" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-5-28-105" name="referenceToDataSetFormat"/><ilcd:display-name>Data set format(s)</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>t</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>"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.</xs:documentation></xs:annotation><xs:unique name="referenceToDataSetFormatShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element></xs:sequence></xs:group>
<xs:group name="DataEntryByGroup2"><xs:sequence><xs:element name="referenceToPersonOrEntityEnteringTheData" type="GlobalReferenceType" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-28-103" name="referenceToPersonOrEntityEnteringTheData"/><ilcd:display-name>Data entry by:</ilcd:display-name><ilcd:iso-field-id>3.6</ilcd:iso-field-id><ilcd:iso-field-name>Data documentator</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>"Contact data set" of the responsible person or entity that has documented this data set, i.e. entered the data and the descriptive information.</xs:documentation></xs:annotation><xs:unique name="referenceToPersonOrEntityEnteringTheDataShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element></xs:sequence></xs:group>
<xs:group name="PublicationAndOwnershipGroup1"><xs:sequence><xs:element name="dataSetVersion" type="Version" minOccurs="1"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-111" name="dataSetVersion"/><ilcd:display-name>Data set version</ilcd:display-name><ilcd:iso-field-id>3.3</ilcd:iso-field-id><ilcd:iso-field-name>Version number</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>m</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element><xs:element name="referenceToPrecedingDataSetVersion" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-112" name="referenceToPrecedingDataSetVersion"/><ilcd:display-name>Preceding data set version</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>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).</xs:documentation></xs:annotation><xs:unique name="referenceToPrecedingDataSetVersionShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element><xs:element name="permanentDataSetURI" type="xs:anyURI" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-300" name="permanentDataSetURI"/><ilcd:display-name>Permanent data set URI</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.]</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:group>
<xs:group name="PublicationAndOwnershipGroup3"><xs:sequence><xs:element ref="copyright" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-116" name="copyright"/><ilcd:display-name>Copyright?</ilcd:display-name><ilcd:iso-field-id>3.9</ilcd:iso-field-id><ilcd:iso-field-name>Copyright</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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".]</xs:documentation></xs:annotation></xs:element><xs:element name="referenceToEntitiesWithExclusiveAccess" type="GlobalReferenceType" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-117" name="referenceToEntitiesWithExclusiveAccess"/><ilcd:display-name>Entities or persons with exclusive access to this data set</ilcd:display-name><ilcd:iso-field-id>(3.10)</ilcd:iso-field-id><ilcd:iso-field-name>(Access restrictions)</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>"Contact data set" of those entities or persons (or groups of these), to which an exclusive access to this data set is granted. Mainly intended to be used in confidentiality management in projects. [Note: See also field "Access and use restrictions".]</xs:documentation></xs:annotation><xs:unique name="referenceToEntitiesWithExclusiveAccessShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element><xs:element name="licenseType" type="LicenseTypeValues" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-119" name="licenseType"/><ilcd:display-name>License type</ilcd:display-name><ilcd:iso-field-id>(3.10)</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Type of license that applies to the access and use of this data set.</xs:documentation></xs:annotation></xs:element><xs:element ref="accessRestrictions" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-118" name="accessRestrictions"/><ilcd:display-name>Access and use restrictions</ilcd:display-name><ilcd:iso-field-id>3.10</ilcd:iso-field-id><ilcd:iso-field-name>Access restrictions</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:group>
<xs:group name="PublicationAndOwnershipGroup2"><xs:sequence><xs:element name="workflowAndPublicationStatus" type="WorkflowAndPublicationStatusValues" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-110" name="workflowAndPublicationStatus"/><ilcd:display-name>Workflow and publication status</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>Workflow or publication status of data set. Details e.g. of foreseen publication dates should be provided on request by the "Data set owner".</xs:documentation></xs:annotation></xs:element><xs:element name="referenceToUnchangedRepublication" type="GlobalReferenceType" minOccurs="0"><xs:annotation><xs:appinfo><ilcd:element id="1-5-30-114" name="referenceToUnchangedRepublication"/><ilcd:display-name>Unchanged re-publication of:</ilcd:display-name><ilcd:iso-field-id>3.8</ilcd:iso-field-id><ilcd:iso-field-name>Publication</ilcd:iso-field-name><ilcd:field-motivation>r</ilcd:field-motivation><ilcd:field-requirement>o</ilcd:field-requirement></xs:appinfo><xs:documentation>"Source data set" of the publication, in which this data set was published for the first time. [Note: This refers to exactly this data set as it is, without any format conversion, adjustments, flow name mapping, etc. In case this data set was modified/converted, the original source is documented in "Converted original data set from:" in section "Data entry by".]</xs:documentation></xs:annotation><xs:unique name="referenceToPublicationShortDescriptionLangUniqueConstraint"><xs:selector xpath="common:shortDescription"/><xs:field xpath="@xml:lang"/></xs:unique></xs:element></xs:sequence></xs:group>
<xs:group name="ValidationGroup1"><xs:sequence><xs:element name="scope" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-82" name="scope"/><ilcd:display-name>Scope of review</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Scope of review regarding which aspects and components of the data set was reviewed or verified. In case of aggregated e.g. LCI results also and on which level of detail (e.g. LCI results only, included unit processes, ...) the review / verification was performed.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="method" minOccurs="0" maxOccurs="unbounded"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-83" name="method"/><ilcd:display-name>Method(s) of review</ilcd:display-name><ilcd:iso-field-id>2.6.1</ilcd:iso-field-id><ilcd:iso-field-name>Method</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Validation method(s) used in the respective "Scope of review".</xs:documentation></xs:annotation><xs:complexType><xs:attribute name="name" type="MethodOfReviewValues" use="required"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-83-1" name="name"/><ilcd:display-name>Method name</ilcd:display-name><ilcd:iso-field-id>2.6.1</ilcd:iso-field-id><ilcd:iso-field-name>Method</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Method name</xs:documentation></xs:annotation></xs:attribute><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType></xs:element></xs:sequence><xs:attribute name="name" type="ScopeOfReviewValues" use="required"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-82-1" name="name"/><ilcd:display-name>Scope name</ilcd:display-name><ilcd:iso-field-id>0</ilcd:iso-field-id><ilcd:iso-field-name/><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation/></xs:annotation></xs:attribute><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType><xs:unique name="Method"><xs:selector xpath="common:method"/><xs:field xpath="@name"/></xs:unique></xs:element><xs:element ref="dataQualityIndicators" minOccurs="0" maxOccurs="1"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-90" name="dataQualityIndicators"/><ilcd:display-name>Data quality indicators</ilcd:display-name><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>Data quality indicators serve to provide the reviewed key information on the data set in a defined, computer-readable (and hence searchable) form. This serves to support LCA practitioners to identify/select the highest quality and most appropriate data sets.</xs:documentation></xs:annotation></xs:element><xs:element ref="reviewDetails" minOccurs="0" maxOccurs="100"><xs:annotation><xs:appinfo><ilcd:element id="1-3-20-84" name="reviewDetails"/><ilcd:display-name>Review details</ilcd:display-name><ilcd:iso-field-id>(2.6.2) and (2.6.3)</ilcd:iso-field-id><ilcd:iso-field-name>(Procedure), (Result)</ilcd:iso-field-name><ilcd:field-motivation>q</ilcd:field-motivation><ilcd:field-requirement>r</ilcd:field-requirement></xs:appinfo><xs:documentation>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.</xs:documentation></xs:annotation></xs:element></xs:sequence></xs:group>