EcoSpold02 Schema Documentation

This documentation provides a simplified view of the EcoSpold02 schemata. Developers should consult the schema files as well to make sure the format is implemented correctly.

To distinguish Xml attributes from elements attribute names are prefixed by "@".

Additions behind the numbers in the "SpoldID, version 1" column are used to indicate changes compared to EcoSpold01.

The "SpoldID, version 1" column is used to help find EcoSpold01 fields. Please use the new "fieldId" column for communications regarding the format.

The following version 1 SpoldIds have been removed in the EcoSpold02 format:

205 languageCode, 206 localLanguageCode, 208 impactAssessmentResult
400 datasetRelatesToProduct, 403 unit, 404 amount
490 localName, 493 infrastructureProcess, 494 infrastructureIncluded, 495 category, 496 subCategory, 497 localCategory, 498 localSubCategory, 499 formula
502 CASNumber
727 uncertaintyAdjustments, 761 countryCode
2401 referenceToCoProduct, 2403 allocationMethod, 2404 fraction, 2492 referenceToInputOutput
3506 category, 3507 subCategory, 3508 infrastructureProcess, 3509 localCategory, 3510 localSubCategory
3703 location, 3709 standardDeviation95, 3711 formula, 3794 localName, 3795 minValue, 3796 maxValue, 3797 mostLikelyValue
5807 companyCode, 5808 countryCode

Activity Description

Activity

Multiple occurrences	No	Required	Yes
Contains the identifying information of an activity dataset including name and classification.

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
activityName	100	401-rename		TString120	120	No	Yes	Yes	Yes
	A name for the activity that is represented by this dataset.
@id	102	200-type		TUuid	36	No	Yes	No	No
	Unique identifier for this activity. The datat type UUID is a 36 characters string with hexadecimal characters and ensures a world-wide unique identifier. A UUID for a new item must be supplied by external software. There are several UUID generators on the web and implementations in most programming languages.
@activityNameId	105	new		TUuid	36	No	Yes	No	No
	Reference to the activity name master data entry for this activity.
@activityNameContextId	106	new		TUuid	36	No	No	No	No
	Reference to the context of the activity name.
	If this attribute is omitted the context of the dataset itself will be used instead.
@type	110	201-type	1 = Unit process; 2 = System terminated	integer		No	Yes	No	No
	Indicates the kind of data (1 = Unit process; 2 = System terminated) that is represented by this dataset. Data are always entered by the data providers as Unit process. The database-generated, attributional and consequential datasets are available both at the unit process level and as aggregated (terminated) system dataset (i.e. the life cycle inventory results) containing the aggregated elementary exchanges and impacts of the product system related to one specific product from the unit process. The terminated product systems include all upstream activity datasets, as linked by the intermediate exchanges, and therefore do not themselves have any intermediate exchanges, only environmental exchanges and accumulated impact assessment results.
@specialActivityType	115	new	0 = ordinary transforming activity (default), 1 = market activity, 10 = market group, 2 = IO activity, 3 = Residual activity, 4 = production mix, 5 = import activity, 6 = supply mix, 7 = export activity, 8 = re-export activity, 9 = correction activity	integer		No	Yes	No	No
	The special activity types are: 0 = “ordinary” transforming activities. Transforming activities are human activities that transform inputs, so that the output of the activity is different from the inputs, e.g. a hard coal mine that transforms hard coal in ground to the marketable product hard coal. Transforming activities are here understood in the widest possible sense, including extraction, production, transport, consumption and waste treatment activities, i.e. any human activity where the intermediate output is different from the intermediate input. The concept “transforming activities” is introduced here simply to distinguish – in the further modelling and linking of activities – these “ordinary” activities from the market activities, production and supply mixes, import and export activities, and correction datasets.1 = market activity. Market activities do not transform their inputs, but simply transfer the intermediate output from a transforming activity to the transforming activities that consume this intermediate output as an input, e.g. from hard coal at the supplier to hard coal at the consumer. Market activities typically mix similar intermediate outputs from different transforming activities. Market activities therefore supply consumption mixes of the intermediate outputs.10 = market group. Market groups are to markets what markets are to transforming activities. In the undefined system model a market group only contains a reference product. The linking algorithm will add supplying markets as inputs which are contained in the location of the market group and have the same reference product.2 = IO activity. An IO activity represents an activity dataset from a national supply-use table, i.e. typically the supply and use of one specific industry.3 = Residual activity. A residual activity is the resulting activity when subtracting all available unit processes within an activity class from the supply-use data (IO activity) of the same activity class, for the same year and geo-graphical area. 4 = production mix. A production mix represents the production-volume-weighted average of the suppliers of a specific product within a geographical area.5 = import activity. An import activity represents the import of a specified product to a specified geographical area, solely for use in national balancing (not contributing to any auto-generated consumption mixes). Imports to administratively constrained markets and from partly isolated markets are modelled as ordinary transforming activities in order to be included in the relevant market activities (consumption mixes).6 = supply mix. A supply mix is a production mix with the addition of the import of a specified product to a specified geographical area.7 = export activity. An export activity represents the export volume of a national production mix that has the national area as its geographical location and does not contribute to any auto-generated consumption mixes. To give the correct value of the export, the same activities and data that are included with the market activities are added directly to the export activity. This includes transport activities, production losses, wholesaler and retailer activities, and product taxes and subsidies.8 = re-export activity. A re-export activity represents the re-export volume of a geographical area and does not contribute to any auto-generated consumption mixes.9 = correction activity. A correction activity is an activity that is added twice to a product system, one with a positive and once with a negative flow, in order to move one or more exchanges from one part of the system to another, e.g. to correct for downstream effects of an upstream activity, or to correct a bias in the mass-balance introduced by an allocation. More details on this is provided in the Chapters on "Downstream changes caused by differences in product quality" and "Allocation corrections" in the ecoinvent Data Quality Guidelines.
generalComment	120	492		TTextAndImage		No	No	Yes	No
	Text and image field for general information about the dataset. Only comments and references of more general nature that cannot be placed in any of the more specific comment fields, should be placed here. In general, the information in the dataset should be sufficient to judge the appropriateness of a dataset for a specific application.Text and image fields are list of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
	List of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
@parentActivityId	130	new		TUuid	36	No	No	No	No
	The parentActivityId is a UUID to the parent activity dataset. When this field is filled with a UUID, all the field content from the parent activity dataset is taken over by the child activity dataset (the activity that calls the parent via the UUID).
	Child activity is derived (inherited) from its parent activity and only the content changes in comparison to its parent are stored in the child process. Child activity datasets cannot be validated using the EcoSpold02 schema, since most of the required fields will not be filled. Please refer to the additional documentation regarding inheritance of datasets in the ecoinvent database for further details.
	There are 5 ways to fill a field in a child activity dataset ("http://www.EcoInvent.org/EcoSpold02Child"):
	1) Leave a field blank: In this case, the value from the parent activity dataset applies.
	2) Fill in content: In this case, the filled in value applies, and the value from the parent activity dataset is ignored.
	3) In a string field, fill in content including the text {{PARENTTEXT}} in which case the field content from the parent activity dataset is included at this place in the filled in text in the child dataset.
	4) In a field with type TTextAndImage, both {{PARENTTEXT}} and {{text_variables}} are supported; the latter allows to define text variables in the parent dataset and use them in the text as {{variablename}}. If a parent textfield includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
	5) In an amount field with corresponding mathematical relation fields, fill in content in the mathematicalRelation field including the reserved variable PARENTVALUE, e.g. the formula PARENTVALUE*0.5 results in halfing the value of the original amount field.
@parentActivityContextId	131	new		TUuid	36	No	No	No	No
	Reference to the context of the parent activity.
	If this attribute is omitted the context of the dataset itself will be used instead.
@inheritanceDepth	135	new		integer		No	No	No	No
	The inheritance depth expresses the maximum number of parent datasets for the current dataset. The following values are used in the ecoinvent context: 0 = not a child, 1 = a geography child, 2 = a temporal child, 3 = a macro-economic scenario child.
includedActivitiesStart	145	402-type		TString32000	32000	No	No	Yes	No
	Describes the starting point of the activity. For "system terminated" the starting point is always "From cradle, i.e. including all upstream activities". For unit processes, the starting point may be described in terms of the nature of the inputs, e.g. "From reception of [e.g. raw material X]..." or "Service starting with the input of [e.g. labour and energy].
includedActivitiesEnd	150	402-type		TString32000	32000	No	No	Yes	No
	Describes the included activities to the extent that this is not self-explanatory from the activity name, as well as activities or inputs that are intentionally excluded, e.g. if the activity “application of pesticides” as a service excludes the pesticide, in order to be applicable for many different active ingredients. The description ends by mentioning the last activity and/or point of delivery, e.g. “until and including loading of the product on lorries”.
synonym	170	491-type		TSynonym	80	Yes	No	Yes	No
	List of synonyms for the name. Contrary to normal multi language strings, synonyms may contain more than one element with the same xml:lang attribute value.
	0..n entries are allowed with a max. length of 80 each.
tag	175	new		TTag	40	Yes	No	No	No
	The tag field allows an open list of keywords which describes the activity and can be used for filtering, grouping and searching. The validTags file reference provides a list of predefined tags, but the semantic validation procedure should only display an information (not an error) if a tag entry cannot be found in the validTags master file.
@energyValues	180	203	0 = Undefined (default); 1 = Net values; 2 = Gross values	integer		No	No	No	No
	Indicates the way energy values are applied in the dataset. The codes are: 0=Undefined (default). 1=Net (lower) heating value. 2=Gross (higher) heating value.
	This data field is by default set to 0.
@masterAllocationPropertyId	190	new		TUuid	36	No	No	No	No
	References the default Allocation Property (via UUID) for all exchanges of this dataset. The Allocation Property can be overwritten for each exchange (see field 1150 specificAllocationPropertyId).
	The allocation factor for a specific output is then the declared TProperty value for this output multiplied by the amount of the output divided by the sum of the all such multiplied TProperty values for all outputs.
@masterAllocationPropertyContextId	191	new		TUuid	36	No	No	No	No
	Reference to the context of the master allocation property.
	If this attribute is omitted the context of the dataset itself will be used instead.
@masterAllocationPropertyIdOverwrittenByChild	192	new		boolean		No	No	No	No
	If a reference to a master data entity must be removed in a child dataset it is required to set the corresponding xxxOverwrittenByChild attribute to true. Otherwise the removed referenced will be interpreted as "Keep the Parent Value".
allocationComment	195	2407		TTextAndImage		No	No	Yes	No
	Text and image field for further information about the allocation procedure and the allocation properties chosen. An eventual coincidence in allocation factors when comparing different allocation parameters (like physical and economic ones) may be reported here as well.Text and image fields are list of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
	List of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
@datasetIcon	200	new		anyURI		No	No	No	No
	The URL of the dataset icon. A dataset icon serves a quick identification of the specific dataset, and may also be used for product brands and company logos. The icon is not directly part of the dataset, but is stored locally or on the ecoinvent web-server, from where it is retrievable via the Http protocol.

Top

Classification

Multiple occurrences	Yes	Required	No
Contains classification pairs to specify the activity.

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
classificationSystem	300	501	TString255	255	No	Yes	Yes	Yes
	The name of the classification system used, e.g. ISIC Rev. 4. This is an optional plaintext value of the referenced classification system (field 320).
classificationValue	310	new	TString120	120	No	Yes	Yes	Yes
	The class that the activity belongs to within the specified classification system. This is an optional plaintext value of the referenced classification value (field 320).
@classificationId	320	new	TUuid	36	No	Yes	No	No
	Reference to the value of a classification system. Must be defined in list of valid classifications (see field 5160).
@classificationContextId	321	new	TUuid	36	No	No	No	No
	Reference to the context of the classification.
	If this attribute is omitted the context of the dataset itself will be used instead.

Top

Geography

Multiple occurrences	No	Required	Yes
Contains information about the geographic validity of the process. The geography may be the point location of the activity, a line describing a mobile activity, or an area of a distributed activity or of a production mix, containing several located activities. For markets (consumption mixes), the geography describes the market boundaries, across which imports and exports are limited.

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@geographyId	400	new	TUuid	36	No	Yes	No	No
	Reference to valid locations file with detailed geography information.
@geographyContextId	401	new	TUuid	36	No	No	No	No
	Reference to the context of the geography.
	If this attribute is omitted the context of the dataset itself will be used instead.
shortname	410	662	TString40	40	No	Yes	Yes	Yes
	Descriptive shortname of the location referenced by geographyId, e.g. the regional codes of EcoSpold version 1.
comment	420	663	TTextAndImage		No	No	Yes	No
	Text and image field for further explanations of the geography. Especially for area descriptions, the nature of the geographical delimitation may be given, especially when this is not an administrative area. Justifications for market boundaries may also be provided here.Text and image fields are list of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
	List of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.

Top

Technology

Multiple occurrences	No	Required	Yes
Contains a description of the technology for which data has been collected. The text should cover information necessary to identify the properties and particularities of the technology(ies) underlying the activity data.

Name	FieldID	SpoldID, version 1	Options	Type	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@technologyLevel	500	new	0 = undefined, 1 = New, 2 = Modern, 3 = Current (default), 4 = Old, 5 = Outdated	integer	No	No	No	No
	Label that grossly classifies the technology of the described activity and can be used in modelling to select processes with a specific technological level. The codes used are:0=Undefined. For market activities that do not have a technology level.1=New. For a technology assumed to be on some aspects technically superior to modern technology, but not yet the most commonly installed when investment is based on purely economic considerations.2=Modern. For a technology currently used when installing new capacity, when investment is based on purely economic considerations (most competitive technology). 3=Current (default). For a technology in between modern and old.4=Old. For a technology that is currently taken out of use, when decommissioning is based on purely economic considerations (least competitive technology).5=Outdated. For a technology no longer in use.The terms used does not necessarily reflect the age of the technologies. A modern technology can be a century old, if it is still the most competitive technology, and an old technology can be relatively young, if it is one that has quickly become superseded by other more competitive ones. The technology level is relative to the year for which the data are valid, as given under Time Period. In a time series, the same technology can move between different technology levels over time. The same technology can also be given different technology levels in different geographical locations, even in the same year.
comment	510	692		TTextAndImage	No	No	Yes	No
	Text and image field to describe the technology of the activity. The text should cover information necessary to identify the properties and particularities of the technology(ies) underlying the activity data. Describes the technological properties of the unit process. If the activity comprises several subactivities, the corresponding technologies should be reported as well. Professional nomenclature should be used for the description.Text and image fields are list of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
	List of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.

Top

Time period

Multiple occurrences	No	Required	Yes
Describes start and end date of the time period for which the dataset is valid.

Name	FieldID	SpoldID, version 1	Type	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@startDate	600	601	date	No	Yes	No	No
	Start date of the time period for which the dataset is valid, presented as a complete date (year-month-day).
@endDate	610	602	date	No	Yes	No	No
	End date of the time period for which the dataset is valid, presented as a complete date (year-month-day).
@isDataValidForEntirePeriod	620	603	boolean	No	Yes	No	No
	Indicates whether or not the activity data (elementary and intermediate exchanges reported under flow data) are valid for the entire time period stated. If not, explanations may be given under 'comment'.
comment	630	611	TTextAndImage	No	No	Yes	No
	Text and image field for additional explanations concerning the temporal validity of the data reported. It may e.g. include information about:- how strong the temporal correlation is for the unit process at issue (e.g., are four year old data still adequate for the activity operated today?),- why data is not valid for the entire period, and for which smaller periods data are then valid. Text and image fields are list of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
	List of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.

Top

Macro-economic Scenario

Multiple occurrences	No	Required	Yes
References the macro-economic scenario used in this dataset.

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@macroEconomicScenarioId	700	new	TUuid	36	No	Yes	No	No
	A reference to a macro-economic scenario defined in the list of valid scenarios (see field 3715).
@macroEconomicScenarioContextId	701	new	TUuid	36	No	No	No	No
	Reference to the context of the macro-economic scenario. If this attribute is omitted the context of the dataset itself will be used instead.
name	720	new	TString80	80	No	Yes	Yes	Yes
	Name of the macro-economic scenario that this dataset belongs to.
comment	740	new	TString32000	32000	No	No	Yes	No
	Description of how a macro-economic child dataset deviates from the default scenario of the parent dataset.

Top

Flow Data

Exchanges

Multiple occurrences	Yes	Required	Yes
This section contains elements used in both exchange types. Elements unique to either Intermediate exchanges or Exchanges with environment are listed in the sections below.

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
name	1000	3702		TString120	120	No	Yes	Yes	Yes
	Name of the exchange.
@id	1005	new		TUuid	36	No	Yes	No	No
	Unique identifier for this exchange. The intermediateExchangeId or the elementaryExchangeId can not be used to identify an exchange because one master data entry can be referenced by more than one exchange of a dataset.
@amount	1020	3707		TFloatNumber		No	Yes	No	No
	Amount of an elementary or intermediate exchange.
@unitId	1030	3706		TUuid	36	No	Yes	No	Yes
	Reference to the unit of the amount.
@unitContextId	1031	new		TUuid	36	No	No	No	Yes
	Reference to the context of the unit.
	If this attribute is omitted the context of the dataset itself will be used instead.
unitName	1035	3706		TString40	40	No	Yes	Yes	Yes
	Unit name of the amount.
@variableName	1040	new		TVariableName	40	No	No	No	No
	The variable name is a short name for the exchange, used when refering to the exchange amount in mathematical relations (formulas). Variables may contain characters, numbers and underscores (_). Variable names must start with a character (a-z). Variable names are not case sensitive (calorific_Value equals Calorific_value).
@isCalculatedAmount	1050	new		boolean		No	No	No	No
	If true the value of the amount field is the calculated value of the mathematicalRelation or the transferCoefficient.
@mathematicalRelation	1060	new		TBaseString32000	32000	No	No	No	No
	Defines a mathematical formula with references to values of flows, parameters or properties by variable names or REF function.
	The result of the formula with a specific set of variable values is written into the amount field.
@casNumber	1100	3701		TCasNumber	11	No	No	No	Yes
	Indicates the number according to the Chemical Abstract Service (CAS). The Format of the CAS-number: 000000-00-0, where the first string of digits needs not to be complete (i.e. less than six digits are admitted).
comment	1110	3792		TString32000	32000	No	No	Yes	No
	A general comment can be made about each individual exchange.
@sourceId	1120	3715	Reference to a source defined in the modelling and validation section.	TUuid	36	No	No	No	No
	A reference to a valid source.
@sourceContextId	1121	new		TUuid	36	No	No	No	No
	Reference to the context of the source.
	If this attribute is omitted the context of the dataset itself will be used instead.
@sourceIdOverwrittenByChild	1122	new		boolean		No	No	No	No
	If a reference to a master data entity must be removed in a child dataset it is required to set the corresponding xxxOverwrittenByChild attribute to true. Otherwise the removed referenced will be interpreted as "Keep the Parent Value".
@sourceYear	1125	new		TBaseString30	30	No	No	No	Yes
	Indicates the year of publication and communication, respectively. For web-sites: last visited.
@sourceFirstAuthor	1126	new		TBaseString40	40	No	No	No	Yes
	Indicates the first author by surname and abbreviated name (e.g., Einstein A.). In case of measurement on site, oral communication, personal written communication and questionnaries ('sourceType'=4, 5, 6, 7) the name of the communicating person is mentioned here.
@pageNumbers	1130	3716		TBaseString30	30	No	No	No	No
	The relevant page numbers if the data are sourced on specific pages in an article or larger publication.
@specificAllocationPropertyId	1150	new		TUuid	36	No	No	No	No
	Reference to the Property used by the allocation. This overrides the dataset wide default defined by masterAllocationPropertyId.
@specificAllocationPropertyContextId	1151	new		TUuid	36	No	No	No	No
	Reference to the context of the property.
	If this attribute is omitted the context of the dataset itself will be used instead.
@specificAllocationPropertyIdOverwrittenByChild	1152	new		boolean		No	No	No	No
	If a reference to a master data entity must be removed in a child dataset it is required to set the corresponding xxxOverwrittenByChild attribute to true. Otherwise the removed referenced will be interpreted as "Keep the Parent Value".
transferCoefficient	1200	new		TTransferCoefficient		Yes	No	No	No
	Transfer coefficients relate specific inputs to specific outputs and record the share of this specific input that contributes to this specific output.
	For the format definition see the complex type section below.
uncertainty	1300	3708		TUncertainty		No	No	No	No
	Uncertainty information in the form of distribution functions and their parameters and/or pedigree data.
	For the format definition see the complex type section below.
property	1400	new		TProperty		Yes	No	No	No
	Properties of the exchange, e.g. dry mass, water content, price, content of specific elements or substances.
	For the format definition see the complex type section below.
tag	1450	new		TTag	40	Yes	No	No	No
	The tag field allows an open list of keywords which describes the activity and can be used for filtering, grouping and searching. The validTags file reference provides a list of predefined tags, but the semantic validation procedure should only display an information (not an error) if a tag entry cannot be found in the validTags master file.
synonym	1470	new		TSynonym	80	Yes	No	Yes	Yes
	List of synonyms for the name. Contrary to normal multi language strings, synonyms may contain more than one element with the same xml:lang attribute value.
	0..n entries are allowed with a max. length of 80 each.

Top

Only valid for Intermediate Exchanges

Multiple occurrences	Yes	Required	Yes
Comprises fields (additional to the exchanges section) which are only valid for intermediate exchanges. Intermediate exchanges are product or waste inputs and outputs recorded in a unit process and its related information.
This section extends the exchanges section in case of intermediate exchanges.

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
inputGroup	1500	3503	1 = Materials/Fuels; 2 = Electricity/Heat; 3 = Services; 5 = From Technosphere (unspecified)	integer		No	Yes	No	No
	Indicates the kind of input flow. The codes are: 1=Materials/Fuels, 2=Electricity/Heat, 3=Services, 5=From Technosphere (unspecified).
	For each exchange only an inputGroup or outputGroup shall exist. This indicates the direction of the flow.
outputGroup	1510	3504	0 = ReferenceProduct; 2 = By-product; 3 = Material for Treatment; 5=Stock Additions	integer		No	Yes	No	No
	Indicates the kind of output flow. The codes are: 0=ReferenceProduct, 2=By-product, 3=MaterialForTreatment, 5=Stock Additions
	For each exchange only an inputGroup or outputGroup shall exist. This indicates the direction of the flow.
@intermediateExchangeId	1515	3793		TUuid	36	No	Yes	No	No
	Reference to the master data entry for this intermediate exchange
@intermediateExchangeContextId	1516	new		TUuid	36	No	No	No	No
	Reference to the context of the intermediate exchange.
	If this attribute is omitted the context of the dataset itself will be used instead.
@activityLinkId	1520	3715	Reference to 105 (in another activity dataset).	TUuid	36	No	No	No	No
	Explicit reference to the activity which supplies the intermediate product. If this field is empty the activity will determined by a linking rule, which uses geographical and temporal information of this activity.
@activityLinkContextId	1521	new		TUuid	36	No	No	No	No
	Reference to the context of the activity link.
	If this attribute is omitted the context of the dataset itself will be used instead.
@activityLinkIdOverwrittenByChild	1522	new		boolean		No	No	No	No
	If a reference to a master data entity must be removed in a child dataset it is required to set the corresponding xxxOverwrittenByChild attribute to true. Otherwise the removed referenced will be interpreted as "Keep the Parent Value".
@productionVolumeAmount	1530	new		TFloatNumber		No	No	No	No
	The product volume expressed per year in the same unit as the exchange.
@productionVolumeSourceIdOverwrittenByChild	1531	new		boolean		No	No	No	No
	If a reference to a master data entity must be removed in a child dataset it is required to set the corresponding xxxOverwrittenByChild attribute to true. Otherwise the removed referenced will be interpreted as "Keep the Parent Value".
@productionVolumeVariableName	1532	new		TVariableName	40	No	No	No	No
	The variable name is a short name for the production volume of the exchange, used when refering to the production volume amount in mathematical relations (formulas). Variables may contain characters, numbers and underscores (_). Variable names must start with a character (a-z). Variable names are not case sensitive (calorific_Value equals Calorific_value).
@productionVolumeSourceId	1533	new	Reference to a source defined in the modelling and validation section.	TUuid	36	No	No	No	No
	A reference to a valid source.
@productionVolumeMathematicalRelation	1534	new		TBaseString32000	32000	No	No	No	No
	Defines a mathematical formula which references to values of flows, parameters or properties by variable names or REF function.
	The result of the formula with a specific set of variable values is written into the amount field.
productionVolumeComment	1535	724		TString32000	32000	No	No	Yes	No
	A general comment can be made on the data source, assumptions and calculations for the production volume data.
@productionVolumeSourceContextId	1536	new		TUuid	36	No	No	No	No
	Reference to the context of the source.
	If this attribute is omitted the context of the dataset itself will be used instead.
@productionVolumeSourceYear	1537	new		TBaseString30	30	No	No	No	Yes
	Indicates the year of publication and communication, respectively. For web-sites: last visited.
@productionVolumeSourceFirstAuthor	1538	new		TBaseString40	40	No	No	No	Yes
	Indicates the first author by surname and abbreviated name (e.g., Einstein A.). In case of measurement on site, oral communication, personal written communication and questionnaries ('sourceType'=4, 5, 6, 7) the name of the communicating person is mentioned here.
productionVolumeUncertainty	1539	new		TUncertainty		No	No	No	No
	Uncertainty information in the form of distribution functions and their parameters and/or pedigree data.
	For the format definition see the complex type section below.
classification	1540	new		TClassification		Yes	No	No	Yes
	Contains classification pairs to specify the product.

Top

Only valid for Elementary Exchanges

Multiple occurrences	Yes	Required	No
Comprises fields (additional to the exchanges section) which are only valid for elementary exchanges. Exchanges with environment are elementary flows as inputs and outputs recorded in a unit process and its related information.
This section extends the exchanges section in case of exchanges with environment.

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
inputGroup	1600	3503	4 = From Environment	integer		No	Yes	No	No
	Indicates the kind of input flow. The codes are: 4=From Environment
	For each exchange only an inputGroup or outputGroup shall exist. This indicates the direction of the flow.
	This field is the equivalent of field 1500 with a different set of valid values.
outputGroup	1610	3504	4 = ToEnvironment	integer		No	Yes	No	No
	Indicates the kind of output flow. The codes are: 4=ToEnvironment
	For each exchange only an inputGroup or outputGroup shall exist. This indicates the direction of the flow.
	This field is the equivalent of field 1510 with a different set of valid values.
@elementaryExchangeId	1615	3793		TUuid	36	No	Yes	No	No
	Reference to the master data entry for this elementary exchange
@elementaryExchangeContextId	1616	new		TUuid	36	No	No	No	No
	Reference to the context of the elementary exchange.
	If this attribute is omitted the context of the dataset itself will be used instead.
compartment	1660	new		TCompartment		No	Yes	No	Yes
	Name of the compartment and subcompartment of the exchange. The xml document referenced by validCompartments contains definitions of valid compartment/subcompartment pairs for a given language.
@formula	1670	3711		TBaseString40	40	No	No	No	Yes
	Chemical formula (e.g. sum formula) may be entered.

Top

Parameters

Multiple occurrences	Yes	Required	No
Dataset parameters for use in formulas.

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
name	1700	new	TString80	80	No	Yes	Yes	Yes
	Descriptive name of the parameter.
@parameterId	1705	new	TUuid	36	No	Yes	No	No
	A reference to a valid master data parameter.
@parameterContextId	1706	new	TUuid	36	No	No	No	No
	Reference to the context of the parameter.
	If this attribute is omitted the context of the dataset itself will be used instead.
@amount	1710	new	TFloatNumber		No	Yes	No	No
	The current value of the parameter.
@unitId	1712	3706	TUuid	36	No	No	No	Yes
	Reference to the unit of the parameter amount.
@unitContextId	1713	new	TUuid	36	No	No	No	Yes
	Reference to the context of the unit. If this attribute is omitted the context of the dataset itself will be used instead.
unitName	1714	3706	TString40	40	No	No	Yes	Yes
	Unit name of the parameter amount.
@variableName	1715	new	TVariableName	40	No	No	No	No
	The variable name is a short name for the exchange, used when refering to the exchange amount in mathematical relations (formulas). Variables may contain characters, numbers and underscores (_). Variable names must start with a character (a-z). Variable names are not case sensitive (calorific_Value equals Calorific_value).
@mathematicalRelation	1720	new	TBaseString32000	32000	No	No	No	No
	Defines a mathematical formula with references to values of flows, parameters or properties by variable names or REF function.
	The result of the formula with a specific set of variable values is written into the amount field.
@isCalculatedAmount	1725	new	boolean		No	No	No	No
	If true the value of the amount field is the calculated value of the mathematicalRelation.
uncertainty	1730	new	TUncertainty		No	No	No	No
	Uncertainty of the parameter amount.
comment	1740	new	TString32000	32000	No	No	Yes	No
	A general comment can be made about each individual parameter.

Top

Impact Indicator Results

Multiple occurrences	Yes	Required	No
Calculated impact indicators

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@impactIndicatorId	1800	new	TUuid	36	No	Yes	No	No
	Reference to the impact indicator.
@impactIndicatorContextId	1801	new	TUuid	36	No	No	No	No
	Reference to the context of the impact indicator. If this attribute is omitted the context of the dataset itself will be used instead.
@impactMethodId	1810	new	TUuid	36	No	Yes	No	No
	Reference to the method of the impact indicator.
@impactMethodContextId	1811	new	TUuid	36	No	No	No	No
	Reference to the context of the impact method. If this attribute is omitted the context of the dataset itself will be used instead.
impactMethodName	1815	new	TString120	120	No	Yes	Yes	Yes
	Name of the impact method.
@impactCategoryId	1820	new	TUuid	36	No	Yes	No	No
	Reference to the method of the impact category.
@impactCategoryContextId	1821	new	TUuid	36	No	No	No	No
	Reference to the context of the impact category. If this attribute is omitted the context of the dataset itself will be used instead.
impactCategoryName	1825	new	TString120	120	No	Yes	Yes	Yes
	Name of the impact category.
@amount	1830	new	TFloatNumber		No	Yes	No	No
	The value of the impact indicator.
name	1840	new	TString120	120	No	Yes	Yes	Yes
	Name of the impact indicator.
unitName	1850	new	TString40	40	No	Yes	Yes	Yes
	Unit name of the impact indicator amount.

Top

Complex Types

TCompartment

Multiple occurrences	No	Required	No
Contains compartment pairs to specify an exchange.

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
compartment	330	new	TCompartmentName	40	No	Yes	Yes	Yes
	The name of the compartment.This is the plaintext value of the referenced compartment (field 5315).
subcompartment	340	new	TCompartmentName	40	No	Yes	Yes	Yes
	The name of the subcompartment.This is the plaintext value of the referenced subcompartment (field 5325).
@subcompartmentId	350	new	TUuid	36	No	Yes	No	No
	Reference to the compartment/subcompartment pair. Must be defined in list of valid compartments (see field 5330).
@subcompartmentContextId	351	new	TUuid	36	No	No	No	No
	Reference to the context of the subcompartment
	If this attribute is omitted the context of the dataset itself will be used instead.

Top

TUncertainty

Multiple occurrences	No	Required	No
Of the following uncertainty methods (lognormal, normal, ..., undefined) exactly one must be selected. The TUncertainty complex type is used in several places, so one dataset may contain several uncertainty elements in distinct places. But each element which has uncertainty may only contain one.

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
comment	2010	3792	TString32000	32000	No	No	Yes	No
	A general comment can be made about each uncertainty information
lognormal	2100	new			No	Yes	No	No
	The Lognormal-distribution with average value μ (Mu parameter) and variance σ (Variance parameter) is a Normal-distribution, shaping the natural logarithm of the characteristic values ln(x) instead of x-values.
@meanValue	2101	new	TFloatNumber		No	Yes	No	No
	Geometric mean
@mu	2102	new	TFloatNumber		No	Yes	No	No
	Arithmetic mean of the underlying normal distribution
@variance	2103	new	TFloatNumber		No	No	No	No
	Unbiased variance of the underlying normal distribution
@varianceWithPedigreeUncertainty	2104	new	TFloatNumber		No	Yes	No	No
	Unbiased variance of the underlying normal distribution, basic uncertainty with pedigree uncertainty
normal	2110	new			No	Yes	No	No
	Normal (also known as "Gaussian") distribution. It is a family of distributions of the same general form, differing in their location and scale parameters: the mean ("MeanValue") and standard deviation ("Deviation"), respectively.
@meanValue	2111	new	TFloatNumber		No	Yes	No	No
	Arithemtic mean
@variance	2112	new	TFloatNumber		No	No	No	No
	Unbiased variance
@varianceWithPedigreeUncertainty	2113	new	TFloatNumber		No	Yes	No	No
	Unbiased variance, basic uncertainty with pedigree uncertainty
triangular	2120	new			No	Yes	No	No
	Parameter are minValue, mostLikelyValue, maxValue.
	In case of triangular uncertainty distribution, the meanValue shall be calculated from the mostLikelyValue. The field mostLikelyValue (#3797) must not be used in the ecoinvent context.
@minValue	2121	new	TFloatNumber		No	Yes	No	No
	Minimum value
@mostLikelyValue	2122	new	TFloatNumber		No	Yes	No	No
	Mode
@maxValue	2123	new	TFloatNumber		No	Yes	No	No
	Maximum value
uniform	2130	new			No	Yes	No	No
	Uniform distribution of values between the minValue and the maxValue parameter. If the maxValue parameter is smaller than the minValue parameter their values will be swapped.
@minValue	2131	new	TFloatNumber		No	Yes	No	No
	Minimum value
@maxValue	2132	new	TFloatNumber		No	Yes	No	No
	Maximum value
beta	2140	new			No	Yes	No	No
	Beta distribution using minValue (a), maxValue (b) and mostFrequentValue (m) parameters to calculate the two shape parameters of the underlying Gamma distributions. The parameters must follow this condition: ((a <= m) and (m <= b)) or (a = b). The shape values will be calculated by these formulas: Shape1 = 1 + 4 * ((m-a) / (b-a)). Shape2 = 6 - Shape1.
@minValue	2141	new	TFloatNumber		No	Yes	No	No
	Minimum value (a)
@mostFrequentValue	2142	new	TFloatNumber		No	Yes	No	No
	Most Frequent value (m)
@maxValue	2143	new	TFloatNumber		No	Yes	No	No
	Maximum value (b)
gamma	2150	new			No	Yes	No	No
	Gamma distribution using scale and shape parameter. Absolute values of the values entered here will be used. The value of the minimum parameter will be added to all samples.
@shape	2151	new	TFloatNumber		No	Yes	No	No
	Shape parameter
@scale	2152	new	TFloatNumber		No	Yes	No	No
	Scale parameter
@minValue	2153	new	TFloatNumber		No	Yes	No	No
	Minimum value (location parameter)
binomial	2160	new			No	Yes	No	No
	Binomial distribution using n and p parameter.
@n	2161	new	integer		No	Yes	No	No
	Number of independant trials
@p	2162	new	TFloatNumber		No	Yes	No	No
	Probability of success in each trial
undefined	2170	new			No	Yes	No	No
	This "distribution" can be used to hold legacy data of the EcoSpold01 format which reused the minValue, maxValue and standardDeviation95 fields to store undefined distribution data.
@minValue	2171	new	TFloatNumber		No	Yes	No	No
	Minimum value
@maxValue	2172	new	TFloatNumber		No	Yes	No	No
	Maximum value
@standardDeviation95	2173	new	TFloatNumber		No	Yes	No	No
	The value, extended from both sides of the mean, that would be necessary to cover 95% of the population
pedigreeMatrix	2270	new	integer		No	No	No	No
	The data quality indicators provides a qualitative assessment of data quality. This can be converted to a quantitative additional uncertainty, which can be added to the basic uncertainty. The pedigreeMatrix element groups the 5 data quality indicators and contains no data itself.
@reliability	2271	new	integer		No	Yes	No	No
	1=Verified data based on measurements
	2=Verified data partly based on assumptions OR nonverified data based on measurements
	3=Non-verified data partly based on qualified estimates
	4=Qualified estimate (e.g. by industrial expert)
	5=Non-qualified estimate (default)
@completeness	2272	new	integer		No	Yes	No	No
	1=Representative data from all sites relevant for the market considered over an adequate period to even out normal fluctuations
	2=Representative data from >50% of the sites relevant for the market considered over an adequate period to even out normal fluctuations
	3=Representative data from only some sites (<<50%) relevant for the market considered OR >50% of sites but from shorter periods
	4=Representative data from only one site relevant for the market considered OR some sites but from shorter periods
	5=Representativeness unknown or data from a small number of sites AND from shorter periods
@temporalCorrelation	2273	new	integer		No	Yes	No	No
	1=Less than 3 years of difference to the time period of the dataset (fields 600-610)
	2=Less than 6 years of difference to the time period of the dataset (fields 600-610)
	3=Less than 10 years of difference to the time period of the dataset (fields 600-610)
	4=Less than 15 years of difference to the time period of the dataset (fields 600-610)
	5=Age of data unknown or more than 15 years of difference to the time period of the dataset (fields 600-610)
@geographicalCorrelation	2274	new	integer		No	Yes	No	No
	1=Data from area under study
	2=Average data from larger area in which the area under study is included
	3=Data from area with similar production conditions
	4=Data from are with slightly similar production conditions
	5=Data from unknown OR distinctly different area (north america instead of middle east, OECD-Europe instead of Russia)
@furtherTechnologyCorrelation	2275	new	integer		No	Yes	No	No
	1=Data from enterprises, processes and materials under study
	2=Data from processes and materials under study (i.e. identical technology) but from different enterprises
	3=Data from processes and materials under study but from different technology
	4=Data on related processes or materials
	5=Data on related processes on laboratory scale or from different technology

Top

TProperty

Multiple occurrences	Yes	Required	No
Format to specify properties of exchanges.

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@propertyId	2300	new	TUuid	36	No	Yes	No	No
	Reference to the master data entry for this property.
@propertyContextId	2301	new	TUuid	36	No	No	No	No
	Reference to the context of the property.
	If this attribute is omitted the context of the dataset itself will be used instead.
name	2310	new	TString80	80	No	Yes	Yes	Yes
	Descriptive name of the property.
@unitId	2320	3706	TUuid	36	No	No	No	Yes
	Reference to the unit of the amount.
@unitContextId	2321	new	TUuid	36	No	No	No	Yes
	Reference to the context of the unit.
	If this attribute is omitted the context of the dataset itself will be used instead.
unitName	2325	3706	TString40	40	No	No	Yes	Yes
	Unit name of the property amount.
@amount	2330	new	TFloatNumber		No	Yes	No	No
	The value of the property.
@isDefiningValue	2335	new	boolean		No	No	No	No
	If this field is true, the value of this property is a part of the definition of the exchange and therefore has a fixed relation to the amount of the exchange that cannot be changed for individual instances of the exchange in different datasets.
@mathematicalRelation	2340	new	TBaseString32000	32000	No	No	No	No
	Defines a mathematical formula with references to values of flows, parameters or properties by variable names or REF function.
	The result of the formula with a specific set of variable values is written into the amount field.
@isCalculatedAmount	2345	new	boolean		No	No	No	No
	If true the value of the amount field is the calculated value of the mathematicalRelation.
@variableName	2350	new	TVariableName	40	No	No	No	No
	Defines a variable name for referencing the property amount in a mathematicalrelation.
	Variable names must start with a character (a-z) and may contain characters, numbers and underscores (_). Variable names are not case sensitive (calorific_Value equals Calorific_value).
uncertainty	2360	new	TUncertainty		No	No	No	No
	Uncertainty of the property value.
@sourceId	2370	new	TUuid	36	No	No	No	No
	A reference to a valid source. It indicates the publication where the property is documented.
@sourceContextId	2371	new	TUuid	36	No	No	No	No
	Reference to the context of the source.
	If this attribute is omitted the context of the dataset itself will be used instead.
@sourceIdOverwrittenByChild	2372	new	boolean		No	No	No	No
	If a reference to a master data entity must be removed in a child dataset it is required to set the corresponding xxxOverwrittenByChild attribute to true. Otherwise the removed referenced will be interpreted as "Keep the Parent Value".
@sourceYear	2375	new	TBaseString30	30	No	No	No	Yes
	Indicates the year of publication and communication, respectively. For web-sites: last visited.
@sourceFirstAuthor	2376	new	TBaseString40	40	No	No	No	Yes
	Indicates the first author by surname and abbreviated name (e.g., Einstein A.). In case of measurement on site, oral communication, personal written communication and questionnaries ('sourceType'=4, 5, 6, 7) the name of the communicating person is mentioned here.
comment	2380	new	TString32000	32000	No	No	Yes	No
	A general comment can be made about each individual property of a particular exchange.

Top

TTransferCoefficient

Multiple occurrences	Yes	Required	No
Transfer coefficients for calculating amounts of outputs from amounts of inputs.

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@exchangeId	2400	new		TUuid	36	No	Yes	No	No
	Reference to the UUID of an exchange.
@amount	2410	new		TFloatNumber		No	Yes	No	No
	The amount of the transfer coefficient is to be multiplied with the amount of this referenced exchange.
@mathematicalRelation	2420	new		TBaseString32000	32000	No	No	No	No
	defines a mathematical formula with references to values of flows, parameters or properties by variable names or REF function
	the result of the formula with a specific set of variable values is written into the amount field
@isCalculatedAmount	2425	new		boolean		No	No	No	No
	If true the value of the amount field is the calculated value of the mathematicalRelation.
uncertainty	2430	new		TUncertainty		No	No	No	No
	Uncertainty of the transfer coefficient amount.
@sourceId	2440	new	Reference to a source defined in the modellingAndValidation section.	TUuid	36	No	No	No	No
	A reference to a valid source.
@sourceContextId	2441	new		TUuid	36	No	No	No	No
	Reference to the context of the source.
	If this attribute is omitted the context of the dataset itself will be used instead.
@sourceIdOverwrittenByChild	2442	new		boolean		No	No	No	No
	If a reference to a master data entity must be removed in a child dataset it is required to set the corresponding xxxOverwrittenByChild attribute to true. Otherwise the removed referenced will be interpreted as "Keep the Parent Value".
@sourceYear	2445	new		TBaseString30	30	No	No	No	Yes
	Indicates the year of publication and communication, respectively. For web-sites: last visited.
@sourceFirstAuthor	2446	new		TBaseString40	40	No	No	No	Yes
	Indicates the first author by surname and abbreviated name (e.g., Einstein A.). In case of measurement on site, oral communication, personal written communication and questionnaries ('sourceType'=4, 5, 6, 7) the name of the communicating person is mentioned here.
comment	2450	3792		TString32000	32000	No	No	Yes	No
	A general comment can be made about each individual transfer coefficient.

Top

TTextAndImage

Multiple occurrences	No	Required	No
List of text, imageUri and variable elements. These can be combined in any order. Their desired order in the result must be given by the index attributes of the text and imageUrl elements.

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
text	3900	new	TIndexedString32000	32000	Yes	No	No	No
	Free text used to describe the current section. Its index attribute is used to enforce a specific order of text and image elements.
imageUrl	3910	new	anyURI		Yes	No	No	No
	Can be used to mix images between texts. Its index attribute is used to enforce a specific order of text and image elements.
variable	3920	new	TNamedString32000	32000	Yes	No	No	No
	Defines a varible name and its value used in a text element in this section. These can be overriden by derived datasets to change the value of variables.

Top

Modelling and validation

Representativeness

Multiple occurrences	No	Required	No
Contains information about the representativeness of the information in the dataset and about how data have been sampled and/or calculated.

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@systemModelId	3000	new		TUuid	36	No	Yes	No	No
	The system model describes how activity datasets are linked to form product systems. Some options in the ecoinvent network are 'undefined', 'attributional, average current suppliers, revenue allocation', 'consequential, small-scale, long-term decisions'.
@systemModelContextId	3001	new		TUuid	36	No	No	No	No
	Reference to the context of the system model.
	If this attribute is omitted the context of the dataset itself will be used instead.
systemModelName	3005	new		TString120	120	No	Yes	Yes	Yes
	This is the plaintext value of the referenced system model (field 3000).
@percent	3010	722	Maximum 100	TPercent		No	No	No	No
	Percent of data sampled out of the total that the activity is intended to represent (as given by the fields under Geography, Technology and Time Period).
samplingProcedure	3030	725		TString32000	32000	No	No	Yes	No
	Text describing the sampling and calculation procedures applied for quantifying the exchanges. Reports whether the sampling procedure for particular elementary and intermediate exchanges differ from the general procedure. Mentions possible problems in combining different sampling procedures.Text and image fields are list of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
extrapolations	3040	726		TString32000	32000	No	No	Yes	No
	Describes extrapolations of data from another time period, another geographical area or another technology and the way these extrapolations have been carried out.
	It should be reported whether different extrapolations have been done on the level of individual exchanges.
	If data representative for a activity operated in one country is used for another country's activity, its original representativity can be indicated here.
	Changes in mean values due to extrapolations may also be reported here.

Top

Review

Multiple occurrences	Yes	Required	No
Contains information about who carried out the critical review and about the main results and conclusions of the review and the recommendations made.
Multiple reviewers allowed

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@reviewerId	3300	5616	Reference to 3610.	TUuid	36	No	Yes	No	No
	Indicates the person who carried out the review.
@reviewerContextId	3301	new		TUuid	36	No	No	No	No
	Reference to the context of the reviewer.
	If this attribute is omitted the context of the dataset itself will be used instead.
@reviewerName	3305	new		TBaseString40	40	No	Yes	No	Yes
	Name and surname of the person.
@reviewerEmail	3306	new		TBaseString80	80	No	Yes	No	Yes
	Complete email address of the person.
@reviewDate	3310	new		date		No	Yes	No	No
	Date of validation or review.
@reviewedMajorRelease	3320	new		integer		No	Yes	No	No
	The dataset version validated or reviewed. Refers to 3800.
@reviewedMinorRelease	3325	new		integer		No	Yes	No	No
	The dataset version validated or reviewed. Refers to 3805.
@reviewedMajorRevision	3330	new		integer		No	Yes	No	No
	The dataset version validated or reviewed. Refers to 3810.
@reviewedMinorRevision	3335	new		integer		No	Yes	No	No
	The dataset version validated or reviewed. Refers to 3815.
details	3340	5615		TTextAndImage		No	No	Yes	No
	Text and image field for the comment of the reviewer of the dataset. Text and image fields are list of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
	List of text, imageUri and variable elements. The text and imageUri elements can used to describe the current section and they can be combined in any order given by their index attribute. Text variables are defined by the variable elements, which may be used in the text as {{variablename}}. If a parent text field includes a variable, this variable may be redefined by the child activity dataset while keeping the rest of the parent text intact. This allows easy changes of text parts in child processes.
otherDetails	3350	5619		TString32000	32000	No	No	Yes	No
	Contains further information from the review process, e.g. on smaller corrections added after the first publication of the dataset.

Top

Administrative information

Data entry by

Multiple occurrences	No	Required	Yes
Contains information about the author of the dataset, i.e. the person that entered data into the database format and thereby is the person responsible for the data.

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@personId	3400	302	Entry must be identical to an existing entry in field 3610	TUuid	36	No	Yes	No	No
	ID number for the person that prepared the dataset and enters the dataset into the database.
@personContextId	3401	new		TUuid	36	No	No	No	No
	Reference to the context of the person.
	If this attribute is omitted the context of the dataset itself will be used instead.
@isActiveAuthor	3403	new		boolean		No	No	No	No
	This field defines if the person specified by field 3400 is the active author for this dataset. The active author will be consulted in case of future changes to the dataset by different data providers.
@personName	3405	new		TBaseString40	40	No	Yes	No	Yes
	Name and surname of the person.
@personEmail	3406	new		TBaseString80	80	No	Yes	No	Yes
	Complete email address of the person.

Top

Data generator and publication

Multiple occurrences	No	Required	Yes
Contains information about who collected, compiled or published the orginal data. This may or may not be the same person as under 'DataEntryBy'. Furthermore contains information about kind of publication underlying the dataset and the accessibility of the dataset.

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@personId	3500	751	ID number for the data generator, i.e. the person or organisation that collected, compiled or published the original data. This may or may not be the same person as the author (see 'DataEntryBy'). The purpose of this field is to acknowledge and reference the origin of the data and the person or organisation that performed the majority of the work in data collection.	TUuid	36	No	Yes	No	No
	ID number for the person that generated the dataset. It must correspond to an ID number of a person listed in the respective dataset.
@personContextId	3501	new		TUuid	36	No	No	No	No
	Reference to the context of the person.
	If this attribute is omitted the context of the dataset itself will be used instead.
@personName	3505	new		TBaseString40	40	No	Yes	No	Yes
	Name and surname of the person.
@personEmail	3506	new		TBaseString80	80	No	Yes	No	Yes
	Complete email address of the person.
@dataPublishedIn	3510	756	0 = Data as such not published elsewhere (default), 1 = The data of some unit processes or subsystems are published, 2 = Data has been published entirely in (refers to field 757)	integer		No	No	No	No
	Indicates whether the dataset has been published (not, partly, entirely).
	The codes are: 0=Data as such not published (default). 1=The data of some unit processes or subsystems are published. 2=Data has been published entirely in 'referenceToPublishedSource'.
@publishedSourceId	3520	757	Reference to 801	TUuid	36	No	No	No	No
	ID number for the report in which the dataset is documented.
@publishedSourceContextId	3521	new		TUuid	36	No	No	No	No
	Reference to the context of the published source.
	If this attribute is omitted the context of the dataset itself will be used instead.
@publishedSourceIdOverwrittenByChild	3522	new		boolean		No	No	No	No
	If a reference to a master data entity must be removed in a child dataset it is required to set the corresponding xxxOverwrittenByChild attribute to true. Otherwise the removed referenced will be interpreted as "Keep the Parent Value".
@publishedSourceYear	3525	new		TBaseString30	30	No	No	No	Yes
	Indicates the year of publication and communication, respectively. For web-sites: last visited.
@publishedSourceFirstAuthor	3526	new		TBaseString40	40	No	No	No	Yes
	Indicates the first author by surname and abbreviated name (e.g., Einstein A.). In case of measurement on site, oral communication, personal written communication and questionnaries ('sourceType'=4, 5, 6, 7) the name of the communicating person is mentioned here.
@pageNumbers	3530	762		TBaseString30	30	No	No	No	No
	The relevant page numbers if the data are sourced on specific pages in an article or larger publication.
@isCopyrightProtected	3540	758		boolean		No	Yes	No	No
	Indicates whether or not a copyright exists. '1' (Yes) or '0' (No) should be entered correspondingly.
@accessRestrictedTo	3550	759	0=Public, 1=Licensees, 2=Results only, 3=Restricted	integer		No	No	No	No
	Indicates possible access restrictions for the dataset.
	The codes used are: 0=Public, 1=Licensees, 2=Results only, 3=Restricted
	accessRestrictedTo=0: No access restrictions.
	accessRestrictedTo=1: only license holders (as defined by context) have access.
	accessRestrictedTo=2: license holders (as defined by context) have access to LCI results but not to unit process raw data. Database administrator have full access.
	accessRestrictedTo=3: only the organisation specified by 'companyCode' and the database administrator have access.
@companyId	3560	760	If 759=3	TUuid	36	No	No	No	No
	Reference to an organisation/institute that the use of this dataset is restricted to.
@companyContextId	3561	new		TUuid	36	No	No	No	No
	Reference to the context of the company.
	If this attribute is omitted the context of the dataset itself will be used instead.
@companyCode	3562	760	If 759=3	TCompanyCode	7	No	No	No	Yes
	Optional 7 letter code plaintext of the referenced company (field 3560)
@companyIdOverwrittenByChild	3563	new		boolean		No	No	No	No
	If a reference to a master data entity must be removed in a child dataset it is required to set the corresponding xxxOverwrittenByChild attribute to true. Otherwise the removed referenced will be interpreted as "Keep the Parent Value".

Top

File attributes

Multiple occurrences	No	Required	Yes
Contains metainformation regarding the file as a whole.

Name	FieldID	SpoldID, version 1	Options	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@majorRelease	3800	202		integer		No	Yes	No	No
	The major release number is increased by one with each major update (e.g. every second year).
@minorRelease	3805	202		integer		No	Yes	No	No
	The minor release number is increased by one for each release within the period of two major updates.
@majorRevision	3810	207		integer		No	Yes	No	No
	The revision number is specific to each dataset and is independent of the overall database release version and is used to discern different versions of the dataset within the database major/minor release versions. The major revision number reflects the amount of accepted changes to the dataset. It will only increase over time and must not be changed manually. In the ecoinvent context the major revision is increased each time changes to an activity are added to the database (i.e. after they passed the review process). This also resets the minor revision to 1.
@minorRevision	3815	207		integer		No	Yes	No	No
	The minor revision number describes versions of the dataset during the editing process before it is submitted for review. In th eecoinvent context it is increased automatically every time the data provider saves changes made to the dataset either locally or as a draft on the ecoinvent server. The minor revision number is reset to “1” each time the major revision number is increased (when changes to a dataset are accepted by a reviewer).
@defaultLanguage	3820	new		string		No	No	No	No
	Default language for all multi language fields of this dataset. Any multi language field should contain a value at least for the default language. If no defaultLanguage is given, the default value ("en") will be used.
@creationTimestamp	3830	204a	Time of creation of dataset	dateTime		No	No	No	No
	Automatically generated date when dataset is created.
@lastEditTimestamp	3840	204b	Time of last editing of dataset	dateTime		No	No	No	No
	Automatically generated date when dataset is saved.
@internalSchemaVersion	3850	new		TBaseString80	80	No	No	No	No
	Dataset is generated based on this internal schema version.
@fileGenerator	3860	new		TBaseString255	255	No	No	No	No
	Description of the program which created this file. Preferably including version.
@fileTimestamp	3870	new		dateTime		No	No	No	No
	Time and date this file was created.
@contextId	3880	new		TUuid	36	No	No	No	No
	Indicates the context for which this dataset is designed. The information is used, e.g. for restricting the accessibility of dataset information to one particular context and to determine which master data files are needed to access it. If this attribute is omitted the dataset is assumed to be a standalone dataset and masterdata references can not be dereferenced.
	The context replaces the ecoSpold01 quality network (field id 304). The context id for the ecoinvent quality network can be found in the Context.xml master data file.
contextName	3885	new		TString80	80	No	No	Yes	Yes
	The name of the context referenced by field 3880.
	The context replaces the ecoSpold01 quality network (field id 304). The context id for the ecoinvent quality network can be found in the Context.xml master data file.
requiredContext	3890	new		TRequiredContextReference		Yes	No	No	No
	Reference to a context required to load this document with all its master data references intact.

Top

Required Context Reference

Multiple occurrences	No	Required	No
This type allows to specify which context(s) must be known if a dataset is to be read using the master data referenced by it.
It can be used signal that master data entries from different contexts are needed to read this dataset. The software reading the dataset must be aware of those contexts and must know where to find the actual master data files of each context.

Name	FieldID	SpoldID, version 1	Type	Size	Multiple Occurrence	Req	Multi Language	Redundant Master Data
@majorRelease	7810	new	integer		No	Yes	No	No
	This version number can be used to make sure that the necessary master data entries are present for an activity.
@minorRelease	7820	new	integer		No	Yes	No	No
	This version number can be used to make sure that the necessary master data entries are present for an activity.
@majorRevision	7830	new	integer		No	No	No	No
	This version number can be used to make sure that the necessary master data entries are present for an activity.
@minorRevision	7840	new	integer		No	No	No	No
	This version number can be used to make sure that the necessary master data entries are present for an activity.
@requiredContextId	7850	new	TUuid	36	No	Yes	No	No
	Reference to the context of the master data file.
	If this attribute is omitted the context of the dataset itself should be used instead.
requiredContextName	7855	new	TString80	80	No	Yes	Yes	Yes
	The name of the context referenced by field 7850.
@requiredContextFileLocation	7860	new	anyURI		No	No	No	No
	Optional URI reference to the directory containing the master data files of this context.

Top