-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HUSE in Exiobase has information on product country of origin, we miss an activity type for that #4
Comments
The current ontology already allows a flow to be bont:outputOf one activity and bont:inputOf another activity. But for the SUT, the product flow origin is redundant information that should be ignored. In a true SUT, the flows enter and leave an activity but do not yet have information on their origin and destination. This information is added when linking the different activities into a Direct Requirements Matrix. The EXIOBASE SUT is overspecified in this sense that it already has interpreted the information in the trade statistics in a specific (attributional) way. This error should not be imported into the BONSAI implementation, which should leave the user free to link SUT activities with different linking algorithms (including one that we may decide on being the preferred consensus one for "official" BONSAI footprints). |
Just to clarify, given the current EXIOBASE excel file, there are rows where an activity X recieves as input some flow object Y from two sources (assume water for paddy rice cultivation, it reiceves a quantity of M water from source 1 and then a quantity of N water from source 2 ). There are then 2 options: |
It has been decided for option 2 (see BONSAMURAIS/EXIOBASE-conversion-software#3) This can be closed now. |
the file
rdf/activitytype/exiobase3_3_17/exiobase3_3_17.ttl
should define an activity type for modeling the origin of flows of products in the use table.
E.g., the Motor Gasoline from Belgium is supplied to Australia wheat production
This come from a discussion with Søren.
The text was updated successfully, but these errors were encountered: