I think it would be a mistake to bake too many restrictions into the general framework. There is a certain mental model that prevails in LCA, but we don't want BONSAI to accept these restrictions at

Thanks Massimo, now I would like to get a consensus from you and the other domain experts about the following statement you wrote: - the determining flow is always a product _output_ flow If this is

(Disclaimer: I am simplifying things a bit here I hope the LCA people will forgive me) Dear Matteo I believe you have understood how it works, but there are some other details that perhaps you should

the production volume of the activity" the activity from flows that are caused by the activity. Now I see, so, as you suggested earlier, a waste can be the determining flow as input of a waste

Den 2019-03-11 kl. 16.22 skrev Matteo Lissandrini (AAU): The more semantically precise term is actually "determining flow". The definition is: "Flow of an activity for which a change will affect the

About why do we separate between two subclass "input" and "output", here is my reasoning. On the one hand this is at the ontology level to restrict the domain of the input and output

On the topic bu also as a general comment - I would suggest to distinguish them not only to make clear that the "Carbon dioxide" is an emission (in the example made) but also to make more intuitive

>>>Environmental exchanges are also just flows (or flow-objects). CO2 can both be an emission to the environment and a (by-)product, but as a chemical it is the same. For this reason, it may be

Den 2019-03-11 kl. 12.42 skrev Matteo Lissandrini (AAU): Is there a semantic difference of the input of data and the input of a physical "thing"? We may need to distinguish between "stock" as an

Den 2019-03-11 kl. 14.09 skrev Massimo Pizzol: Good point. No need for separate subclasses, as also Agneta pointed out. It is just an input relation or an output relation of a

Den 2019-03-11 kl. 14.14 skrev Agneta: The flow-object is the "thing" that can flow, e.g. "steel". The flow is the instance of a flow-object flowing in or out of an activity, e.g.

The problem is that "flow" can be a verb or a noun - we want to make sure people use it as a noun, hence "object." +1 The working example should have a model of how we can store data related to the

Thanks Matteo for bringing the discussion to the platform. My questions in relation to the schema and our discussions on friday are: 1. I personally find the terms ‘Flow’ and ‘Flow object’

Dear Matteo and all Looks good to me but I am a bit puzzled about two things: Why do we separate between two subclass “input” and “output” when we have already the two relations:

Hi all, after the call and the discussion I've drafted a possible schema with an example (please see [1]). It is based on the works of : A) A minimal ontology pattern for life cycle assessment data,

Sorry; I missed it. I had two concurrent meeting this morning.

Default is omnivourous. That is why I ask. Bo Den 2019-03-08 kl. 09.38 skrev Tom:

Hi Bo, Unfortunately I am still gluten intolerant. Thank you! Best, Stefano -- Best,S.

Could you confirm please if the food will be vegetarian by default? Thanks!

Hi all, I have updated the agenda ( https://github.com/BONSAMURAIS/hackathon-2019/blob/master/Agenda.md ) with timing, including the timing of zoom meetings (all in BCN time). Some one will probably