Valid Intermediate Exchange
Multiple occurrencesNoRequiredYes
Contains a list of valid intermediate exchanges.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
@originalSource5700newanyURINoNoNoNo
Reference to the location of the original document. Can be used to verify the data and/or to check for updates in the future.
@majorRelease5701newintegerNoYesNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The release version number is used as follows: with a major update (e.g. every second year) the major release number is increased by one (1.00, 2.00, etc.).
@minorRelease5702newintegerNoYesNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The release version number is used as follows: minor updates (corrected errors) within the period of two major updates increase the minor release version.
@majorRevision5703newintegerNoNoNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The revision version number is used to discern different versions during the working period until the dataset is entered into the database). The revision is generated automatically with each change made in the dataset or related file.
@minorRevision5704newintegerNoNoNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The revision Version number is used to discern different versions during the working period until the dataset is entered into the database). The revision is generated automatically with each change made in the dataset or related file.
@contextId5705newTUuid36NoNoNoNo
Reference to the context of the master data file.
contextName5706newTString8080NoNoYesYes
The name of the context referenced by field 3880.
requiredContext5707newTRequiredContextReferenceYesNoNoNo
Reference to context required to load this document with all its master data references intact.
intermediateExchange5710newTValidIntermediateExchangeYesYesNoNo
A list of valid intermediate exchanges. This element provides hierarchical grouping only and contains no information on its own. For details see complex type TValidIntermediateExchange below.

Top

TValidIntermediateExchange
Multiple occurrencesYesRequiredYes
Describes a single intermediate exchange dataset (a product or waste). An exchange is solely identified by its name and there must not be two exchanges with the same name but different units.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
@id5720newTUuid36NoYesNoNo
Universally unique identifier for each exchange. This is referenced by field 1515 in activity datasets.
name5730401TString120120NoYesYesNo
Name of the intermediate exchange.
classification5740newTClassificationYesNoNoNo
Contains classification system/value pairs to specify the optional classification of the exchange.
@unitId57503706TUuid36NoYesNoNo
Reference to the unit of the amount.
@unitContextId5751newTUuid36NoNoNoNo
Reference to the context of the unit.
If this attribute is omitted the context of the document itself will be used instead.
unitName5755newes:TString40NoYesYesYes
Name of the Unit of the intermediate exchange.
@casNumber5758502zero fill from frontTCasNumber11NoNoNoNo
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).
synonym5760491TSynonym80YesNoYesNo
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.
property5765newTPropertyYesNoNoNo
Structure to define flow properties of exchanges.
See below for the format definition.
These are default values that can be over-written by a specific entry for the same property in a specific dataset.
@defaultVariableName5770newTVariableName40NoNoNoNo
The default variable name is a suggestion that should be used when a new exchange is added to a dataset based on this master data entry.
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).
comment5775492TString3200032000NoNoYesNo
A general comment can be made about each individual exchange.
productInformation5785newTTextAndImageNoNoYesNo
Further information about the product. Contrary to the data in the comment field, this information will not be transferred into actual exchanges using a valid intermediate exchange.
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

Classification
Multiple occurrencesYesRequiredNo
Contains classification pairs to specify the activity.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
classificationSystem300501TString255255NoYesYesYes
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).
classificationValue310newTString120120NoYesYesYes
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).
@classificationId320newTUuid36NoYesNoNo
Reference to the value of a classification system. Must be defined in list of valid classifications (see field 5160).
@classificationContextId321newTUuid36NoNoNoNo
Reference to the context of the classification.
If this attribute is omitted the context of the dataset itself will be used instead.

Top

TProperty
Multiple occurrencesYesRequiredNo
Format to specify properties of exchanges.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
@propertyId2300newTUuid36NoYesNoNo
Reference to the master data entry for this property.
@propertyContextId2301newTUuid36NoNoNoNo
Reference to the context of the property.
If this attribute is omitted the context of the dataset itself will be used instead.
name2310newTString8080NoYesYesYes
Descriptive name of the property.
@unitId23203706TUuid36NoNoNoYes
Reference to the unit of the amount.
@unitContextId2321newTUuid36NoNoNoYes
Reference to the context of the unit.
If this attribute is omitted the context of the dataset itself will be used instead.
unitName23253706TString4040NoNoYesYes
Unit name of the property amount.
@amount2330newTFloatNumberNoYesNoNo
The value of the property.
@isDefiningValue2335newbooleanNoNoNoNo
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.
@mathematicalRelation2340newTBaseString3200032000NoNoNoNo
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.
@isCalculatedAmount2345newbooleanNoNoNoNo
If true the value of the amount field is the calculated value of the mathematicalRelation.
@variableName2350newTVariableName40NoNoNoNo
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).
uncertainty2360newTUncertaintyNoNoNoNo
Uncertainty of the property value.
@sourceId2370newTUuid36NoNoNoNo
A reference to a valid source. It indicates the publication where the property is documented.
@sourceContextId2371newTUuid36NoNoNoNo
Reference to the context of the source.
If this attribute is omitted the context of the dataset itself will be used instead.
@sourceIdOverwrittenByChild2372newbooleanNoNoNoNo
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".
@sourceYear2375newTBaseString3030NoNoNoYes
Indicates the year of publication and communication, respectively. For web-sites: last visited.
@sourceFirstAuthor2376newTBaseString4040NoNoNoYes
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.
comment2380newTString3200032000NoNoYesNo
A general comment can be made about each individual property of a particular exchange.

Top

TUncertainty
Multiple occurrencesYesRequiredNo
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.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
comment20103792TString3200032000NoNoYesNo
A general comment can be made about each uncertainty information
lognormal2100newNoYesNoNo
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.
@meanValue2101newTFloatNumberNoYesNoNo
Geometric mean
@mu2102newTFloatNumberNoYesNoNo
Arithmetic mean of the underlying normal distribution
@variance2103newTFloatNumberNoNoNoNo
Unbiased variance of the underlying normal distribution
@varianceWithPedigreeUncertainty2104newTFloatNumberNoYesNoNo
Unbiased variance of the underlying normal distribution, basic uncertainty with pedigree uncertainty
normal2110newNoYesNoNo
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.
@meanValue2111newTFloatNumberNoYesNoNo
Arithemtic mean
@variance2112newTFloatNumberNoNoNoNo
Unbiased variance
@varianceWithPedigreeUncertainty2113newTFloatNumberNoYesNoNo
Unbiased variance, basic uncertainty with pedigree uncertainty
triangular2120newNoYesNoNo
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.
@minValue2121newTFloatNumberNoYesNoNo
Minimum value
@mostLikelyValue2122newTFloatNumberNoYesNoNo
Mode
@maxValue2123newTFloatNumberNoYesNoNo
Maximum value
uniform2130newNoYesNoNo
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.
@minValue2131newTFloatNumberNoYesNoNo
Minimum value
@maxValue2132newTFloatNumberNoYesNoNo
Maximum value
beta2140newNoYesNoNo
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.
@minValue2141newTFloatNumberNoYesNoNo
Minimum value (a)
@mostFrequentValue2142newTFloatNumberNoYesNoNo
Most Frequent value (m)
@maxValue2143newTFloatNumberNoYesNoNo
Maximum value (b)
gamma2150newNoYesNoNo
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.
@shape2151newTFloatNumberNoYesNoNo
Shape parameter
@scale2152newTFloatNumberNoYesNoNo
Scale parameter
@minValue2153newTFloatNumberNoYesNoNo
Minimum value (location parameter)
binomial2160newNoYesNoNo
Binomial distribution using n and p parameter.
@n2161newintegerNoYesNoNo
Number of independant trials
@p2162newTFloatNumberNoYesNoNo
Probability of success in each trial
undefined2170newNoYesNoNo
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.
@minValue2171newTFloatNumberNoYesNoNo
Minimum value
@maxValue2172newTFloatNumberNoYesNoNo
Maximum value
@standardDeviation952173newTFloatNumberNoYesNoNo
The value, extended from both sides of the mean, that would be necessary to cover 95% of the population
pedigreeMatrix2270newintegerNoNoNoNo
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.
@reliability2271newintegerNoYesNoNo
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)
@completeness2272newintegerNoYesNoNo
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
@temporalCorrelation2273newintegerNoYesNoNo
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)
@geographicalCorrelation2274newintegerNoYesNoNo
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)
@furtherTechnologyCorrelation2275newintegerNoYesNoNo
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

Required Context Reference
Multiple occurrencesYesRequiredNo
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.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
@majorRelease7810newintegerNoYesNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity.
@minorRelease7820newintegerNoYesNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity.
@majorRevision7830newintegerNoNoNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity.
@minorRevision7840newintegerNoNoNoNo
This version number can be used to make sure that the necessary master data entries are present for an activity.
@requiredContextId7850newTUuid36NoYesNoNo
Reference to the context of the master data file.
If this attribute is omitted the context of the dataset itself should be used instead.
requiredContextName7855newTString8080NoYesYesYes
The name of the context referenced by field 7850.
@requiredContextFileLocation7860newanyURINoNoNoNo
Optional URI reference to the directory containing the master data files of this context.

Top