Date   
Data group on Transport Energy

Bo Weidema
 

Hi,

Some interesting parallel work going on on transport energy: https://transportenergy.org/

Best regards

Bo

Re: Import of Exiobase data #exiobase

Massimo Pizzol
 

Thanks. I must say I didn’t know that this exiobase “extension table” existed, specifying the mass composition of a monetary output.

I think what you propose below is fine then, or at least I don’t see any limitation at first sight. Indeed both the dry mass content, steel content, wood content, etc.,  and the monetary value, price, weight, etc. are all characteristics or “properties” of the same flow.

 

Massimo

 

 

From: <main@bonsai.groups.io> on behalf of "Bo Weidema via Groups.Io" <bo.weidema@...>
Reply-To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Date: Tuesday, 21 January 2020 at 19.31
To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Subject: Re: [bonsai] Import of Exiobase data #exiobase

 

Dear Massimo,

Good with critical questions.

Although Matteo's example is correct, maybe the example would have been easier to understand if using as the second flow "dry mass" as such, rather than "dry mass of steel", the point being that the same flow, namely that of cars has many "balanceable properties" that can each be measured and expressed separately. The flow of car can be expressed by its value (in currency) or its dry mass (in mass units), but also in terms of its material composition, separately reporting its content of steel (in mass units), wood (in mass units), etc. all adding up to the total mass. Each of these baleanceable properties can be balanced across the activity, hence the name, in terms of "what goes in must come out".

So to your specific questions:

  • Steel is usually not in an extension table. I would expect Carbon Dioxide to be in the extension table. Or do you mean something else?

In the exiobase hybrid, the cars are reported in currency units, while the mass specified per material is reported in teh extensions tables. This is specific to cars, and is of course not the ideal way to do this. Exiobase is not yet a fully multi-property-layer database....

  • Are you saying that 200 kg of Steel is worth 1000 euros? Is this the relationship we need to maintain? Or that we need 200 kg steel to produce 100euros of cars?
  • Seems like cars and steel are the same thing here…

What Matteo's example says is that the flow of a car with 200 kg of steel trades at a value of 1000 Euro. Both pieces of information relates to the same flow and are useful for different purposes.

  • Are we talking about the same sector modelled in two different tables (a monetary one and a physical units one) or about one sector in a hybrid table?

Sector is not in the BONSAI vocabulary. If you mean the same activity and the same flow in different property tables (layers), then yes. The two (and more) balanceable properties can be represented in the same graph, but for balancing you should query only for one specific balanceable property at a time (althoug simultaneous balancing of all balanceable properties is possible).

I hope this helps?

Bo

 

Den 2020/01/21 kl. 17.27 skrev Massimo Pizzol:

Thanks. I have several questions on this mail from Matteo.

 

  • Steel is usually not in an extension table. I would expect Carbon Dioxide to be in the extension table. Or do you mean something else?
  • Are you saying that 200 kg of Steel is worth 1000 euros? Is this the relationship we need to maintain? Or that we need 200 kg steel to produce 100euros of cars?
  • Seems like cars and steel are the same thing here…
  • Are we talking about the same sector modelled in two different tables (a monetary one and a physical units one) or about one sector in a hybrid table?

 

I am afraid this confusion is due to the poor example, so I suggest using a more accurate one.


BR
Massimo

 

From: <main@bonsai.groups.io> on behalf of "Matteo Lissandrini (AAU) via Groups.Io" <matteo@...>
Reply-To:
"main@bonsai.groups.io" <main@bonsai.groups.io>
Date: Tuesday, 21 January 2020 at 17.13
To:
"main@bonsai.groups.io" <main@bonsai.groups.io>
Subject: Re: [bonsai] Import of Exiobase data #exiobase

 

Hi all,

 

in order to model correctly the data in Exiobase (and not only there)

we have investigated our current model of representing flows and quantity of flows.

 

Following is a (toy) example:

 

The Exiobase supply table represents a flow of `1000Euros` of `Cars` as `output` of activity `A1`

 

Yet, some other extension table will tell us that the flow above "at the same time" corresponds to some `200Kg` of Steel that is still `output` of activity `A1`   (although in some processed form)

 

Hence, 100Euros and 200Kg are different way to "measure" the very same flow.

The current name of this is "balanceable property".

 

In the first case we are representing the "currency" balanceable property of the flow of cars,

in the second the "dry mass of Steel" balanceable property .

 

We do not want to miss the link between these two instances and they are effectively properties of the same flow.

 

Hence the following model (in the attached picture).

 

The triple statements (in natural language) following this new model will be:

 

Flow1 output of A1

A1 has activity type "Car production"

Flow1 has object  "Car"

Flow1 has balanceable property P1

P1 has type "currency"

P1 has numeric value "1000"

P1 has unit "Euros"

Flow1 has balanceable property P2

P2 has type "dry mass of Steel"

P2 has numeric value "200"

P2 has unit "Kg"

 

Please let us know if you have comments and/or questions.

 

@Bo, please correct me if I'm wrong

@Chris, shoot your questions, I know you have them :)

 

A suggestion: if you understand what we are trying to do, at this stage refrain from discussing the actual name "balanceable property" (it might or might not be ugly) 

and first see if there are problems with the modeling itself, naming comes as second step.

 

 

Thanks,

Matteo

 

 

 

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo

 

Re: Import of Exiobase data #exiobase

Bo Weidema
 

Dear Massimo,

Good with critical questions.

Although Matteo's example is correct, maybe the example would have been easier to understand if using as the second flow "dry mass" as such, rather than "dry mass of steel", the point being that the same flow, namely that of cars has many "balanceable properties" that can each be measured and expressed separately. The flow of car can be expressed by its value (in currency) or its dry mass (in mass units), but also in terms of its material composition, separately reporting its content of steel (in mass units), wood (in mass units), etc. all adding up to the total mass. Each of these baleanceable properties can be balanced across the activity, hence the name, in terms of "what goes in must come out".

So to your specific questions:

  • Steel is usually not in an extension table. I would expect Carbon Dioxide to be in the extension table. Or do you mean something else?

In the exiobase hybrid, the cars are reported in currency units, while the mass specified per material is reported in teh extensions tables. This is specific to cars, and is of course not the ideal way to do this. Exiobase is not yet a fully multi-property-layer database....

  • Are you saying that 200 kg of Steel is worth 1000 euros? Is this the relationship we need to maintain? Or that we need 200 kg steel to produce 100euros of cars?
  • Seems like cars and steel are the same thing here…

What Matteo's example says is that the flow of a car with 200 kg of steel trades at a value of 1000 Euro. Both pieces of information relates to the same flow and are useful for different purposes.

  • Are we talking about the same sector modelled in two different tables (a monetary one and a physical units one) or about one sector in a hybrid table?

Sector is not in the BONSAI vocabulary. If you mean the same activity and the same flow in different property tables (layers), then yes. The two (and more) balanceable properties can be represented in the same graph, but for balancing you should query only for one specific balanceable property at a time (althoug simultaneous balancing of all balanceable properties is possible).

I hope this helps?

Bo


Den 2020/01/21 kl. 17.27 skrev Massimo Pizzol:

Thanks. I have several questions on this mail from Matteo.

 

  • Steel is usually not in an extension table. I would expect Carbon Dioxide to be in the extension table. Or do you mean something else?
  • Are you saying that 200 kg of Steel is worth 1000 euros? Is this the relationship we need to maintain? Or that we need 200 kg steel to produce 100euros of cars?
  • Seems like cars and steel are the same thing here…
  • Are we talking about the same sector modelled in two different tables (a monetary one and a physical units one) or about one sector in a hybrid table?

 

I am afraid this confusion is due to the poor example, so I suggest using a more accurate one.


BR
Massimo

 

From: <main@bonsai.groups.io> on behalf of "Matteo Lissandrini (AAU) via Groups.Io" <matteo@...>
Reply-To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Date: Tuesday, 21 January 2020 at 17.13
To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Subject: Re: [bonsai] Import of Exiobase data #exiobase

 

Hi all,

 

in order to model correctly the data in Exiobase (and not only there)

we have investigated our current model of representing flows and quantity of flows.

 

Following is a (toy) example:

 

The Exiobase supply table represents a flow of `1000Euros` of `Cars` as `output` of activity `A1`

 

Yet, some other extension table will tell us that the flow above "at the same time" corresponds to some `200Kg` of Steel that is still `output` of activity `A1`   (although in some processed form)

 

Hence, 100Euros and 200Kg are different way to "measure" the very same flow.

The current name of this is "balanceable property".

 

In the first case we are representing the "currency" balanceable property of the flow of cars,

in the second the "dry mass of Steel" balanceable property .

 

We do not want to miss the link between these two instances and they are effectively properties of the same flow.

 

Hence the following model (in the attached picture).

 

The triple statements (in natural language) following this new model will be:

 

Flow1 output of A1

A1 has activity type "Car production"

Flow1 has object  "Car"

Flow1 has balanceable property P1

P1 has type "currency"

P1 has numeric value "1000"

P1 has unit "Euros"

Flow1 has balanceable property P2

P2 has type "dry mass of Steel"

P2 has numeric value "200"

P2 has unit "Kg"

 

Please let us know if you have comments and/or questions.

 

@Bo, please correct me if I'm wrong

@Chris, shoot your questions, I know you have them :)

 

A suggestion: if you understand what we are trying to do, at this stage refrain from discussing the actual name "balanceable property" (it might or might not be ugly) 

and first see if there are problems with the modeling itself, naming comes as second step.

 

 

Thanks,

Matteo

 

 

 

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo


Re: Import of Exiobase data #exiobase

Matteo Lissandrini (AAU)
 

Thanks for the good questions Massimo.


@Chris, assuming my example clarifies our discussion, can you just replace names/numbers with what you found in the excel file when looking at cars?

I think this will clarify Massimo's and other people's initial doubts.


Thanks,

Matteo


---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Massimo Pizzol via Groups.Io <massimo@...>
Sent: 21 January 2020 17:27:38
To: main@bonsai.groups.io
Subject: Re: [bonsai] Import of Exiobase data #exiobase
 

Thanks. I have several questions on this mail from Matteo.

 

  • Steel is usually not in an extension table. I would expect Carbon Dioxide to be in the extension table. Or do you mean something else?
  • Are you saying that 200 kg of Steel is worth 1000 euros? Is this the relationship we need to maintain? Or that we need 200 kg steel to produce 100euros of cars?
  • Seems like cars and steel are the same thing here…
  • Are we talking about the same sector modelled in two different tables (a monetary one and a physical units one) or about one sector in a hybrid table?

 

I am afraid this confusion is due to the poor example, so I suggest using a more accurate one.


BR
Massimo

 

From: <main@bonsai.groups.io> on behalf of "Matteo Lissandrini (AAU) via Groups.Io" <matteo@...>
Reply-To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Date: Tuesday, 21 January 2020 at 17.13
To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Subject: Re: [bonsai] Import of Exiobase data #exiobase

 

Hi all,

 

in order to model correctly the data in Exiobase (and not only there)

we have investigated our current model of representing flows and quantity of flows.

 

Following is a (toy) example:

 

The Exiobase supply table represents a flow of `1000Euros` of `Cars` as `output` of activity `A1`

 

Yet, some other extension table will tell us that the flow above "at the same time" corresponds to some `200Kg` of Steel that is still `output` of activity `A1`   (although in some processed form)

 

Hence, 100Euros and 200Kg are different way to "measure" the very same flow.

The current name of this is "balanceable property".

 

In the first case we are representing the "currency" balanceable property of the flow of cars,

in the second the "dry mass of Steel" balanceable property .

 

We do not want to miss the link between these two instances and they are effectively properties of the same flow.

 

Hence the following model (in the attached picture).

 

The triple statements (in natural language) following this new model will be:

 

Flow1 output of A1

A1 has activity type "Car production"

Flow1 has object  "Car"

Flow1 has balanceable property P1

P1 has type "currency"

P1 has numeric value "1000"

P1 has unit "Euros"

Flow1 has balanceable property P2

P2 has type "dry mass of Steel"

P2 has numeric value "200"

P2 has unit "Kg"

 

Please let us know if you have comments and/or questions.

 

@Bo, please correct me if I'm wrong

@Chris, shoot your questions, I know you have them :)

 

A suggestion: if you understand what we are trying to do, at this stage refrain from discussing the actual name "balanceable property" (it might or might not be ugly) 

and first see if there are problems with the modeling itself, naming comes as second step.

 

 

Thanks,

Matteo

 

 

 

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo





From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Chris Mutel via Groups.Io <cmutel@...>
Sent: 21 January 2020 16:36:26
To: main@bonsai.groups.io
Subject: [bonsai] Import of Exiobase data #exiobase

 

The Aalborg BONSAI contingent and visitors are running a mini-hack-a-thon Jan. 20 & 21 to make progress on finalizing the Exiobase import into the BONSAI ontology. During this time, we have prepared the following:

Trade data and model

Trade data will be imported from the use table. In the initial import, we just take the data as it is - aggregation and cleaning steps will happen afterwards.

Every trade data point will have a unique activity, with the type "Export," and with a single edge to a flow. This is in contrast with so-called normal activities, which can have many input and output edges to flows. As a reminder, activities are resolved in time and space, but flow objects are not, and flows are not explicitly (though you can infer their temporal and spatial context by their linked activity/ies).



Environmental and other extensions

Exiobase has a number of extensions. Some are easy, but others pose modelling or data architecture challenges.

The easy ones: Emissions, resource use, land use, crop residues

Each "thing," such as CO2, is a single new flow object. We store this using the standard flow object / flow / activity approach, and the activity is the activity that produces or consumes the flow.

There is a small exception for emissions, which are also provided in a separate worksheet listing avoided emissions due to the use of manure. This is essentially information used already by the manure treatment activity to calculate its net emissions - a flavor of consequential LCA, if you will. For our purposes, this information is not needing and won't be used.

There is also a question for what Exiobase calls "emissions of activities from unregistered waste." Currently, we plan to skip this, but are investigating whether these values are ever significant (compared to "normal" emissions from the activities).

The hard one: waste / materials

Exiobase has 19 materials (measured in mass), such as wood, textiles, glass, and steel. These can give data on waste production, but also on the material composition of packaging and products. There are multiple worksheets, and they need to be handled separately.

Supply and use of waste

This is the simple case. Each waste material is a flow object (regardless of production or consumption), linked as any other industrial import or export.

Packaging materials

Take the case of production of canned vegetables. Exiobase will give the mass of the produced vegetables, but the mass of the can is given separately in the packaging worksheets, both as a production (linked to the producing activity), and as a consumption (for the consuming activity, such as final demand). When the packaging material is disposed of by the consuming activity, its mass is already included in the total waste figures.

We will give the production or consumption of packaging material as a separate flow & flow object, and provide documentation and examples on how to correctly query for and use the activities that have these linked multiple products.

Supply and use of materials in heterogenous products by activities

In Exiobase, automobile manufacturing is denoted in euros. It is useful to know about the material composition of these cars, however, and Exiobase gives these material compositions (e.g. kg steel per euro) in the above strange title.

This case is tricky, as it is not a case of flow & flow object, but is rather a property of the already existing automobile flow. This is the first time we have to use the ontology section "balancable property" with real data, and it has exposed some elements that we could improve. The relevant people are looking into this.

Supply of materials accumulated at the end of the period, and supply of waste from materials accumulated previously in the society

Exiobase (and, you know, the world) has the concept of stocks: buildings, warehouses, your aunt's toy closet. In a given year, products can enter into stocks, or be removed from stocks. Exiobase gives these stock additions in two perspectives: the product perspective, with normal Exiobase products (in the supply table), and the material composition perspective. The sums of both perspectives should be identical. The above categories list the composition of things either entering the stock pool and staying there are the Exiobase representative year, or things that were added to stock beforehand and turned into waste during the Exiobase representative year.

Next steps

I have written this up to the best of my understanding, but certainly there are some technical errors or places where clarification will be needed. We will be documenting this work, and the BONSAI ontology in general, with easier manuals and examples before the next hackathon.

Re: Import of Exiobase data #exiobase

Massimo Pizzol
 

Thanks. I have several questions on this mail from Matteo.

 

  • Steel is usually not in an extension table. I would expect Carbon Dioxide to be in the extension table. Or do you mean something else?
  • Are you saying that 200 kg of Steel is worth 1000 euros? Is this the relationship we need to maintain? Or that we need 200 kg steel to produce 100euros of cars?
  • Seems like cars and steel are the same thing here…
  • Are we talking about the same sector modelled in two different tables (a monetary one and a physical units one) or about one sector in a hybrid table?

 

I am afraid this confusion is due to the poor example, so I suggest using a more accurate one.


BR
Massimo

 

From: <main@bonsai.groups.io> on behalf of "Matteo Lissandrini (AAU) via Groups.Io" <matteo@...>
Reply-To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Date: Tuesday, 21 January 2020 at 17.13
To: "main@bonsai.groups.io" <main@bonsai.groups.io>
Subject: Re: [bonsai] Import of Exiobase data #exiobase

 

Hi all,

 

in order to model correctly the data in Exiobase (and not only there)

we have investigated our current model of representing flows and quantity of flows.

 

Following is a (toy) example:

 

The Exiobase supply table represents a flow of `1000Euros` of `Cars` as `output` of activity `A1`

 

Yet, some other extension table will tell us that the flow above "at the same time" corresponds to some `200Kg` of Steel that is still `output` of activity `A1`   (although in some processed form)

 

Hence, 100Euros and 200Kg are different way to "measure" the very same flow.

The current name of this is "balanceable property".

 

In the first case we are representing the "currency" balanceable property of the flow of cars,

in the second the "dry mass of Steel" balanceable property .

 

We do not want to miss the link between these two instances and they are effectively properties of the same flow.

 

Hence the following model (in the attached picture).

 

The triple statements (in natural language) following this new model will be:

 

Flow1 output of A1

A1 has activity type "Car production"

Flow1 has object  "Car"

Flow1 has balanceable property P1

P1 has type "currency"

P1 has numeric value "1000"

P1 has unit "Euros"

Flow1 has balanceable property P2

P2 has type "dry mass of Steel"

P2 has numeric value "200"

P2 has unit "Kg"

 

Please let us know if you have comments and/or questions.

 

@Bo, please correct me if I'm wrong

@Chris, shoot your questions, I know you have them :)

 

A suggestion: if you understand what we are trying to do, at this stage refrain from discussing the actual name "balanceable property" (it might or might not be ugly) 

and first see if there are problems with the modeling itself, naming comes as second step.

 

 

Thanks,

Matteo

 

 

 

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo





From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Chris Mutel via Groups.Io <cmutel@...>
Sent: 21 January 2020 16:36:26
To: main@bonsai.groups.io
Subject: [bonsai] Import of Exiobase data #exiobase

 

The Aalborg BONSAI contingent and visitors are running a mini-hack-a-thon Jan. 20 & 21 to make progress on finalizing the Exiobase import into the BONSAI ontology. During this time, we have prepared the following:

Trade data and model

Trade data will be imported from the use table. In the initial import, we just take the data as it is - aggregation and cleaning steps will happen afterwards.

Every trade data point will have a unique activity, with the type "Export," and with a single edge to a flow. This is in contrast with so-called normal activities, which can have many input and output edges to flows. As a reminder, activities are resolved in time and space, but flow objects are not, and flows are not explicitly (though you can infer their temporal and spatial context by their linked activity/ies).



Environmental and other extensions

Exiobase has a number of extensions. Some are easy, but others pose modelling or data architecture challenges.

The easy ones: Emissions, resource use, land use, crop residues

Each "thing," such as CO2, is a single new flow object. We store this using the standard flow object / flow / activity approach, and the activity is the activity that produces or consumes the flow.

There is a small exception for emissions, which are also provided in a separate worksheet listing avoided emissions due to the use of manure. This is essentially information used already by the manure treatment activity to calculate its net emissions - a flavor of consequential LCA, if you will. For our purposes, this information is not needing and won't be used.

There is also a question for what Exiobase calls "emissions of activities from unregistered waste." Currently, we plan to skip this, but are investigating whether these values are ever significant (compared to "normal" emissions from the activities).

The hard one: waste / materials

Exiobase has 19 materials (measured in mass), such as wood, textiles, glass, and steel. These can give data on waste production, but also on the material composition of packaging and products. There are multiple worksheets, and they need to be handled separately.

Supply and use of waste

This is the simple case. Each waste material is a flow object (regardless of production or consumption), linked as any other industrial import or export.

Packaging materials

Take the case of production of canned vegetables. Exiobase will give the mass of the produced vegetables, but the mass of the can is given separately in the packaging worksheets, both as a production (linked to the producing activity), and as a consumption (for the consuming activity, such as final demand). When the packaging material is disposed of by the consuming activity, its mass is already included in the total waste figures.

We will give the production or consumption of packaging material as a separate flow & flow object, and provide documentation and examples on how to correctly query for and use the activities that have these linked multiple products.

Supply and use of materials in heterogenous products by activities

In Exiobase, automobile manufacturing is denoted in euros. It is useful to know about the material composition of these cars, however, and Exiobase gives these material compositions (e.g. kg steel per euro) in the above strange title.

This case is tricky, as it is not a case of flow & flow object, but is rather a property of the already existing automobile flow. This is the first time we have to use the ontology section "balancable property" with real data, and it has exposed some elements that we could improve. The relevant people are looking into this.

Supply of materials accumulated at the end of the period, and supply of waste from materials accumulated previously in the society

Exiobase (and, you know, the world) has the concept of stocks: buildings, warehouses, your aunt's toy closet. In a given year, products can enter into stocks, or be removed from stocks. Exiobase gives these stock additions in two perspectives: the product perspective, with normal Exiobase products (in the supply table), and the material composition perspective. The sums of both perspectives should be identical. The above categories list the composition of things either entering the stock pool and staying there are the Exiobase representative year, or things that were added to stock beforehand and turned into waste during the Exiobase representative year.

Next steps

I have written this up to the best of my understanding, but certainly there are some technical errors or places where clarification will be needed. We will be documenting this work, and the BONSAI ontology in general, with easier manuals and examples before the next hackathon.

Re: Import of Exiobase data #exiobase

Matteo Lissandrini (AAU)
 

Hi all,


in order to model correctly the data in Exiobase (and not only there)

we have investigated our current model of representing flows and quantity of flows.


Following is a (toy) example:


The Exiobase supply table represents a flow of `1000Euros` of `Cars` as `output` of activity `A1`


Yet, some other extension table will tell us that the flow above "at the same time" corresponds to some `200Kg` of Steel that is still `output` of activity `A1`   (although in some processed form)


Hence, 100Euros and 200Kg are different way to "measure" the very same flow.

The current name of this is "balanceable property".


In the first case we are representing the "currency" balanceable property of the flow of cars,

in the second the "dry mass of Steel" balanceable property .


We do not want to miss the link between these two instances and they are effectively properties of the same flow.


Hence the following model (in the attached picture).


The triple statements (in natural language) following this new model will be:


Flow1 output of A1

A1 has activity type "Car production"

Flow1 has object  "Car"

Flow1 has balanceable property P1

P1 has type "currency"

P1 has numeric value "1000"

P1 has unit "Euros"

Flow1 has balanceable property P2

P2 has type "dry mass of Steel"

P2 has numeric value "200"

P2 has unit "Kg"


Please let us know if you have comments and/or questions.

@Bo, please correct me if I'm wrong

@Chris, shoot your questions, I know you have them :)


A suggestion: if you understand what we are trying to do, at this stage refrain from discussing the actual name "balanceable property" (it might or might not be ugly) 

and first see if there are problems with the modeling itself, naming comes as second step.



Thanks,

Matteo




---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Chris Mutel via Groups.Io <cmutel@...>
Sent: 21 January 2020 16:36:26
To: main@bonsai.groups.io
Subject: [bonsai] Import of Exiobase data #exiobase
 
The Aalborg BONSAI contingent and visitors are running a mini-hack-a-thon Jan. 20 & 21 to make progress on finalizing the Exiobase import into the BONSAI ontology. During this time, we have prepared the following:

Trade data and model

Trade data will be imported from the use table. In the initial import, we just take the data as it is - aggregation and cleaning steps will happen afterwards.

Every trade data point will have a unique activity, with the type "Export," and with a single edge to a flow. This is in contrast with so-called normal activities, which can have many input and output edges to flows. As a reminder, activities are resolved in time and space, but flow objects are not, and flows are not explicitly (though you can infer their temporal and spatial context by their linked activity/ies).



Environmental and other extensions

Exiobase has a number of extensions. Some are easy, but others pose modelling or data architecture challenges.

The easy ones: Emissions, resource use, land use, crop residues

Each "thing," such as CO2, is a single new flow object. We store this using the standard flow object / flow / activity approach, and the activity is the activity that produces or consumes the flow.

There is a small exception for emissions, which are also provided in a separate worksheet listing avoided emissions due to the use of manure. This is essentially information used already by the manure treatment activity to calculate its net emissions - a flavor of consequential LCA, if you will. For our purposes, this information is not needing and won't be used.

There is also a question for what Exiobase calls "emissions of activities from unregistered waste." Currently, we plan to skip this, but are investigating whether these values are ever significant (compared to "normal" emissions from the activities).

The hard one: waste / materials

Exiobase has 19 materials (measured in mass), such as wood, textiles, glass, and steel. These can give data on waste production, but also on the material composition of packaging and products. There are multiple worksheets, and they need to be handled separately.

Supply and use of waste

This is the simple case. Each waste material is a flow object (regardless of production or consumption), linked as any other industrial import or export.

Packaging materials

Take the case of production of canned vegetables. Exiobase will give the mass of the produced vegetables, but the mass of the can is given separately in the packaging worksheets, both as a production (linked to the producing activity), and as a consumption (for the consuming activity, such as final demand). When the packaging material is disposed of by the consuming activity, its mass is already included in the total waste figures.

We will give the production or consumption of packaging material as a separate flow & flow object, and provide documentation and examples on how to correctly query for and use the activities that have these linked multiple products.

Supply and use of materials in heterogenous products by activities

In Exiobase, automobile manufacturing is denoted in euros. It is useful to know about the material composition of these cars, however, and Exiobase gives these material compositions (e.g. kg steel per euro) in the above strange title.

This case is tricky, as it is not a case of flow & flow object, but is rather a property of the already existing automobile flow. This is the first time we have to use the ontology section "balancable property" with real data, and it has exposed some elements that we could improve. The relevant people are looking into this.

Supply of materials accumulated at the end of the period, and supply of waste from materials accumulated previously in the society

Exiobase (and, you know, the world) has the concept of stocks: buildings, warehouses, your aunt's toy closet. In a given year, products can enter into stocks, or be removed from stocks. Exiobase gives these stock additions in two perspectives: the product perspective, with normal Exiobase products (in the supply table), and the material composition perspective. The sums of both perspectives should be identical. The above categories list the composition of things either entering the stock pool and staying there are the Exiobase representative year, or things that were added to stock beforehand and turned into waste during the Exiobase representative year.

Next steps

I have written this up to the best of my understanding, but certainly there are some technical errors or places where clarification will be needed. We will be documenting this work, and the BONSAI ontology in general, with easier manuals and examples before the next hackathon.

Import of Exiobase data #exiobase

 

The Aalborg BONSAI contingent and visitors are running a mini-hack-a-thon Jan. 20 & 21 to make progress on finalizing the Exiobase import into the BONSAI ontology. During this time, we have prepared the following:

Trade data and model

Trade data will be imported from the use table. In the initial import, we just take the data as it is - aggregation and cleaning steps will happen afterwards.

Every trade data point will have a unique activity, with the type "Export," and with a single edge to a flow. This is in contrast with so-called normal activities, which can have many input and output edges to flows. As a reminder, activities are resolved in time and space, but flow objects are not, and flows are not explicitly (though you can infer their temporal and spatial context by their linked activity/ies).



Environmental and other extensions

Exiobase has a number of extensions. Some are easy, but others pose modelling or data architecture challenges.

The easy ones: Emissions, resource use, land use, crop residues

Each "thing," such as CO2, is a single new flow object. We store this using the standard flow object / flow / activity approach, and the activity is the activity that produces or consumes the flow.

There is a small exception for emissions, which are also provided in a separate worksheet listing avoided emissions due to the use of manure. This is essentially information used already by the manure treatment activity to calculate its net emissions - a flavor of consequential LCA, if you will. For our purposes, this information is not needing and won't be used.

There is also a question for what Exiobase calls "emissions of activities from unregistered waste." Currently, we plan to skip this, but are investigating whether these values are ever significant (compared to "normal" emissions from the activities).

The hard one: waste / materials

Exiobase has 19 materials (measured in mass), such as wood, textiles, glass, and steel. These can give data on waste production, but also on the material composition of packaging and products. There are multiple worksheets, and they need to be handled separately.

Supply and use of waste

This is the simple case. Each waste material is a flow object (regardless of production or consumption), linked as any other industrial import or export.

Packaging materials

Take the case of production of canned vegetables. Exiobase will give the mass of the produced vegetables, but the mass of the can is given separately in the packaging worksheets, both as a production (linked to the producing activity), and as a consumption (for the consuming activity, such as final demand). When the packaging material is disposed of by the consuming activity, its mass is already included in the total waste figures.

We will give the production or consumption of packaging material as a separate flow & flow object, and provide documentation and examples on how to correctly query for and use the activities that have these linked multiple products.

Supply and use of materials in heterogenous products by activities

In Exiobase, automobile manufacturing is denoted in euros. It is useful to know about the material composition of these cars, however, and Exiobase gives these material compositions (e.g. kg steel per euro) in the above strange title.

This case is tricky, as it is not a case of flow & flow object, but is rather a property of the already existing automobile flow. This is the first time we have to use the ontology section "balancable property" with real data, and it has exposed some elements that we could improve. The relevant people are looking into this.

Supply of materials accumulated at the end of the period, and supply of waste from materials accumulated previously in the society

Exiobase (and, you know, the world) has the concept of stocks: buildings, warehouses, your aunt's toy closet. In a given year, products can enter into stocks, or be removed from stocks. Exiobase gives these stock additions in two perspectives: the product perspective, with normal Exiobase products (in the supply table), and the material composition perspective. The sums of both perspectives should be identical. The above categories list the composition of things either entering the stock pool and staying there are the Exiobase representative year, or things that were added to stock beforehand and turned into waste during the Exiobase representative year.

Next steps

I have written this up to the best of my understanding, but certainly there are some technical errors or places where clarification will be needed. We will be documenting this work, and the BONSAI ontology in general, with easier manuals and examples before the next hackathon.

BONSAI ontology: case study for application and extension

 

Dear all-

Bo noticed that the Yale MFA database has finally been publicly
released. This is a very nice opportunity to apply our tools and
ontology, as it will both require us to get a specific implementation
of stocks, and show how what we are doing is relevant to people doing
MFA and Industrial Ecology.

The paper describing the data is here:
https://www.nature.com/articles/s41597-019-0085-7
The data is hosted by USGS here:
https://www.sciencebase.gov/catalog/item/5b9a7c28e4b0d966b485d915
Stefan Pauliuk has already written some parsing/translation code here:
https://github.com/IndEcol/IE_data_commons/commit/1b3948d1fb01b81df8a100a6f02bc90c372352eb

In a similar vein, it would be good to be able to parse the wide
variety of IE data that Stefan and his group have prepared:
http://www.database.industrialecology.uni-freiburg.de/

Before the Spring hackathon, we should have a specific implementation
plan on how to import and use this data. Feel free to reply to this
message if you would be interested.

-Chris

--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################

Re: Call-in details for meeting with TraseEarth

Bo Weidema
 

Oops, I got that wrong. The meeting is Friday 21st February (!)

Bo

Den 2020/01/15 kl. 10.36 skrev Bo Weidema via Groups.Io:

Dear all,

As previously announced, on Tuesday January 21st, from 15:00-16:00 CET, TraseEarth will present their project, and I understand that Chris will prepare some slides on BONSAI to present to them as well.

BONSAI is inviting you to join the scheduled Zoom meeting, courtesy of 2.-0 LCA consultants:

Topic: BONSAI meets TraseEarth
Time: Jan 21, 2020 03:00 PM Copenhagen

Join Zoom Meeting
https://zoom.us/j/942489554

Meeting ID: 942 489 554

Best regards

Bo

--
--

Call-in details for meeting with TraseEarth Tuesday

Bo Weidema
 

Dear all,

As previously announced, on Tuesday January 21st, from 15:00-16:00 CET, TraseEarth will present their project, and I understand that Chris will prepare some slides on BONSAI to present to them as well.

BONSAI is inviting you to join the scheduled Zoom meeting, courtesy of 2.-0 LCA consultants:

Topic: BONSAI meets TraseEarth
Time: Jan 21, 2020 03:00 PM Copenhagen

Join Zoom Meeting
https://zoom.us/j/942489554

Meeting ID: 942 489 554

Best regards

Bo

--

Re: Do not forget the meeting with Hestia this Friday

Matteo Lissandrini (AAU)
 

Sorry for the confusion, indeed was just a mistake from my overzealous  calendar application.


Looking forward to participate in the call.


Thanks and Happy New Year,


Matteo


---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Bo Weidema via Groups.Io <bo.weidema@...>
Sent: 07 January 2020 15:03:09
To: main@bonsai.groups.io
Subject: [bonsai] Do not forget the meeting with Hestia this Friday
 

In spite of the maybe confusing messages from Matteo, the meeting is NOT cancelled. We do look forward to exchange views on Friday.

Best regards

Bo

Den 2020/01/06 kl. 10.18 skrev Bo Weidema via Groups.Io:

Dear all,

As previously annouced, on Friday, January 10, from 15:00-16:00 CET, Joseph Poore will present Hestia, a new initiative to make agriculture and food LCA data more open and comprehensive, initially building on this article: https://science.sciencemag.org/content/360/6392/987.full?ijkey=ffyeW1F0oSl6k&keytype=ref&siteid=sci.

BONSAI is inviting you to join the scheduled Zoom meeting, courtesy of 2.-0 LCA consultants:

Topic: BONSAI meeting Hestia
Time: Jan 10, 2020 03:00 PM Copenhagen

Join Zoom Meeting
https://zoom.us/j/261081130?pwd=aVRsYTJGa2ZOdGt0V0x0cU0vK3lBUT09

Meeting ID: 261 081 130
Password: 990797

Best regards

Bo

Do not forget the meeting with Hestia this Friday

Bo Weidema
 

In spite of the maybe confusing messages from Matteo, the meeting is NOT cancelled. We do look forward to exchange views on Friday.

Best regards

Bo

Den 2020/01/06 kl. 10.18 skrev Bo Weidema via Groups.Io:

Dear all,

As previously annouced, on Friday, January 10, from 15:00-16:00 CET, Joseph Poore will present Hestia, a new initiative to make agriculture and food LCA data more open and comprehensive, initially building on this article: https://science.sciencemag.org/content/360/6392/987.full?ijkey=ffyeW1F0oSl6k&keytype=ref&siteid=sci.

BONSAI is inviting you to join the scheduled Zoom meeting, courtesy of 2.-0 LCA consultants:

Topic: BONSAI meeting Hestia
Time: Jan 10, 2020 03:00 PM Copenhagen

Join Zoom Meeting
https://zoom.us/j/261081130?pwd=aVRsYTJGa2ZOdGt0V0x0cU0vK3lBUT09

Meeting ID: 261 081 130
Password: 990797

Best regards

Bo

_._,_._,_

Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#203) | Reply To Group | Reply To Sender | Mute This Topic | New Topic

Your Subscription | Contact Group Owner | Unsubscribe [bo.weidema@...]

_._,_._

Canceled: [bonsai] Call Hestia

Matteo Lissandrini (AAU)
 

As previously annouced, on Friday, January 10, from 15:00-16:00

Call-in details for meeting with Hestia this Friday

Matteo Lissandrini (AAU)
 

As previously annouced, on Friday, January 10, from 15:00-16:00

Call-in details for meeting with Hestia this Friday

Bo Weidema
 

Dear all,

As previously annouced, on Friday, January 10, from 15:00-16:00 CET, Joseph Poore will present Hestia, a new initiative to make agriculture and food LCA data more open and comprehensive, initially building on this article: https://science.sciencemag.org/content/360/6392/987.full?ijkey=ffyeW1F0oSl6k&keytype=ref&siteid=sci.

BONSAI is inviting you to join the scheduled Zoom meeting, courtesy of 2.-0 LCA consultants:

Topic: BONSAI meeting Hestia
Time: Jan 10, 2020 03:00 PM Copenhagen

Join Zoom Meeting
https://zoom.us/j/261081130?pwd=aVRsYTJGa2ZOdGt0V0x0cU0vK3lBUT09

Meeting ID: 261 081 130
Password: 990797

Best regards

Bo

Web Client to access the data #rdf #ontology #infrastructure

Matteo Lissandrini (AAU)
 

Hi all,
combined with the access to the provenance data (which will proceed with new improvements soon),
we are testing also a simplified web interface for the data.

Now if you visit https://odas.aau.dk/
you'll see a 'Comunica' client. Fuseki is still up and running.

The nice thing here is that we will have some pre-configured query that people can run.
Also, probably this will help us to run queries linked to other datasets, like Geonames or Dbpedia (but we will see how far we will manage to go).
This is not a tool we built, but we are just testing out, Emil did the installation.

Feel free to play around.

All the best,
Matteo

Re: Adding provenance #ontology #intro #provenance

Matteo Lissandrini (AAU)
 

Thanks,


then we will proceed :)


---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Søren via Groups.Io <loekke@...>
Sent: 19 December 2019 13:37:31
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance
 

Go for it!

 

From: main@bonsai.groups.io <main@bonsai.groups.io> On Behalf Of Massimo Pizzol via Groups.Io
Sent: 19 December 2019 13:11
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance

 

Fine for me


From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Matteo Lissandrini (AAU) via Groups.Io <matteo@...>
Sent: Tuesday, December 17, 2019 10:43:46 AM
To: main@bonsai.groups.io
Cc: Christopher Mutel; Michele De Rosa
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance

 

Hi all,

 

the pull request is still pending,

Brandon had a nice comment that we are working on addressing.

 

Emil is anxious to get some more work done on this, I think we should not have his excitement fade ;)

 

If you all agree I would proceed merging the current pull request, and we will followup with more of them to enhance the current solution.

 

Please let us know.

 

Thanks,

Matteo

 

 

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo





From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Matteo Lissandrini (AAU) via Groups.Io <matteo@...>
Sent: 06 December 2019 09:06:56
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance

 

Hi Chris, Michele, everyone.

 

We would really like to get your input on Emil's pull request.

It is not a lot of code and it adds at least some minimum of metadata regarding the datasets and their provenance/lineage.

Please let us know if we can merge it in.

 

Thanks,

Matteo

 

 

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo





From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Emil Riis Hansen via Groups.Io <emilrh@...>
Sent: 03 December 2019 11:51:24
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance

 

Hi everyone,

I have prepared a pull request for the initial implementation of provenance.

The request extends upon the work by the Arborist working group, by an initial minimal provenance implementation, which adds lineage information between instances of entities and the EXIOBASE dataset, as well as provenance information regarding the Arborist script itself.
Further improvements will be needed and will arrive.

The request also fixes the issue of "missing dataset declarations" from the RDF repository.

Matteo has helped review the request before the submit, but I look forward to your feedback.

Pull request: https://github.com/BONSAMURAIS/arborist/pull/14
Issue: https://github.com/BONSAMURAIS/rdf/issues/3

Best Regards,
Emil

Re: Adding provenance #ontology #intro #provenance

Søren
 

Go for it!

 

From: main@bonsai.groups.io <main@bonsai.groups.io> On Behalf Of Massimo Pizzol via Groups.Io
Sent: 19 December 2019 13:11
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance

 

Fine for me


From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Matteo Lissandrini (AAU) via Groups.Io <matteo@...>
Sent: Tuesday, December 17, 2019 10:43:46 AM
To: main@bonsai.groups.io
Cc: Christopher Mutel; Michele De Rosa
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance

 

Hi all,

 

the pull request is still pending,

Brandon had a nice comment that we are working on addressing.

 

Emil is anxious to get some more work done on this, I think we should not have his excitement fade ;)

 

If you all agree I would proceed merging the current pull request, and we will followup with more of them to enhance the current solution.

 

Please let us know.

 

Thanks,

Matteo

 

 

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo





From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Matteo Lissandrini (AAU) via Groups.Io <matteo@...>
Sent: 06 December 2019 09:06:56
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance

 

Hi Chris, Michele, everyone.

 

We would really like to get your input on Emil's pull request.

It is not a lot of code and it adds at least some minimum of metadata regarding the datasets and their provenance/lineage.

Please let us know if we can merge it in.

 

Thanks,

Matteo

 

 

---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo





From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Emil Riis Hansen via Groups.Io <emilrh@...>
Sent: 03 December 2019 11:51:24
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance

 

Hi everyone,

I have prepared a pull request for the initial implementation of provenance.

The request extends upon the work by the Arborist working group, by an initial minimal provenance implementation, which adds lineage information between instances of entities and the EXIOBASE dataset, as well as provenance information regarding the Arborist script itself.
Further improvements will be needed and will arrive.

The request also fixes the issue of "missing dataset declarations" from the RDF repository.

Matteo has helped review the request before the submit, but I look forward to your feedback.

Pull request: https://github.com/BONSAMURAIS/arborist/pull/14
Issue: https://github.com/BONSAMURAIS/rdf/issues/3

Best Regards,
Emil

Re: Adding provenance #ontology #intro #provenance

Massimo Pizzol
 

Fine for me


From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Matteo Lissandrini (AAU) via Groups.Io <matteo@...>
Sent: Tuesday, December 17, 2019 10:43:46 AM
To: main@bonsai.groups.io
Cc: Christopher Mutel; Michele De Rosa
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance
 

Hi all,


the pull request is still pending,

Brandon had a nice comment that we are working on addressing.


Emil is anxious to get some more work done on this, I think we should not have his excitement fade ;)


If you all agree I would proceed merging the current pull request, and we will followup with more of them to enhance the current solution.


Please let us know.


Thanks,

Matteo



---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Matteo Lissandrini (AAU) via Groups.Io <matteo@...>
Sent: 06 December 2019 09:06:56
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance
 

Hi Chris, Michele, everyone.


We would really like to get your input on Emil's pull request.

It is not a lot of code and it adds at least some minimum of metadata regarding the datasets and their provenance/lineage.

Please let us know if we can merge it in.


Thanks,

Matteo



---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Emil Riis Hansen via Groups.Io <emilrh@...>
Sent: 03 December 2019 11:51:24
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance
 
Hi everyone,

I have prepared a pull request for the initial implementation of provenance.

The request extends upon the work by the Arborist working group, by an initial minimal provenance implementation, which adds lineage information between instances of entities and the EXIOBASE dataset, as well as provenance information regarding the Arborist script itself.
Further improvements will be needed and will arrive.

The request also fixes the issue of "missing dataset declarations" from the RDF repository.

Matteo has helped review the request before the submit, but I look forward to your feedback.

Pull request: https://github.com/BONSAMURAIS/arborist/pull/14
Issue: https://github.com/BONSAMURAIS/rdf/issues/3

Best Regards,
Emil

Re: Adding provenance #ontology #intro #provenance

Matteo Lissandrini (AAU)
 

Hi all,


the pull request is still pending,

Brandon had a nice comment that we are working on addressing.


Emil is anxious to get some more work done on this, I think we should not have his excitement fade ;)


If you all agree I would proceed merging the current pull request, and we will followup with more of them to enhance the current solution.


Please let us know.


Thanks,

Matteo



---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Matteo Lissandrini (AAU) via Groups.Io <matteo@...>
Sent: 06 December 2019 09:06:56
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance
 

Hi Chris, Michele, everyone.


We would really like to get your input on Emil's pull request.

It is not a lot of code and it adds at least some minimum of metadata regarding the datasets and their provenance/lineage.

Please let us know if we can merge it in.


Thanks,

Matteo



---
Matteo Lissandrini

Department of Computer Science
Aalborg University

http://people.cs.aau.dk/~matteo






From: main@bonsai.groups.io <main@bonsai.groups.io> on behalf of Emil Riis Hansen via Groups.Io <emilrh@...>
Sent: 03 December 2019 11:51:24
To: main@bonsai.groups.io
Subject: Re: [bonsai] Adding provenance #ontology #intro #provenance
 
Hi everyone,

I have prepared a pull request for the initial implementation of provenance.

The request extends upon the work by the Arborist working group, by an initial minimal provenance implementation, which adds lineage information between instances of entities and the EXIOBASE dataset, as well as provenance information regarding the Arborist script itself.
Further improvements will be needed and will arrive.

The request also fixes the issue of "missing dataset declarations" from the RDF repository.

Matteo has helped review the request before the submit, but I look forward to your feedback.

Pull request: https://github.com/BONSAMURAIS/arborist/pull/14
Issue: https://github.com/BONSAMURAIS/rdf/issues/3

Best Regards,
Emil