boweidema
commented
5 years ago The issue of "compartments" has historically been solved in the LCA community by adding the compartment as a property to the flow-object, while the semantically correct place would be to add the compartment information to the flow itself. The compartment information also has the problem that it is very static, i.e. it relies on enumerating different compartments rather than using underlying properties of the flows. Example: Underlying the distinction between household and industry indoor emissions characterisation factors is that the air flow (volume/time) and number of persons exposed are different, leading to different levels of exposure/emission. By stating the air flow and person-hours as properties, it is possible to add new "compartments" without having to change anything in the database or software structure. Thus more flexible and smarter. Conclusion: Add compartment information as properties of flows, and as far as possible as continuous parameter values.
agneta20
Biosphere & Technosphere are fo
In my vocabulary, compartments are some physical places where flows occur, mostly emissions. Ex: air urban area, air rural area, freshwater, ocean, soil, ...
In turn, the technosphere is a list of Activities and the biosphere is a list of flowObjects of environmental concern (a subset of all flowObjects).
I raise two points:
Compartments seem to be related to the issue of handling of stocks: e.g. CO2 emissions to air - urban area ; stock of CO2 in atm is changed e.g. PM emissions to air - rural area
When importing a dataset to the rdf database, should we state its provenance via a property? e.g. all activities from Exiobase having the property "bont:ActivityFrom" "uriOfexiobase3SUT"; same for the flow objects