Skip to content
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

HSUT to IO exiobase #19

Open
3 of 4 tasks
mfastudillo opened this issue Mar 27, 2019 · 5 comments
Open
3 of 4 tasks

HSUT to IO exiobase #19

mfastudillo opened this issue Mar 27, 2019 · 5 comments

Comments

@mfastudillo
Copy link
Contributor

mfastudillo commented Mar 27, 2019

for export we will be using the input output version of exiobase, the correspondence table will show which activities have been aggregated

the file is here, it just need some cleaning and to move it to the final tables folder (and metadata)

  • clean if necessary.
  • add metadata.
  • create csv
  • define predicate
@mfastudillo
Copy link
Contributor Author

we can't create a non-ambiguous correspondence until we have URIs for both the hsut names and the IO names. The namespace for hsut names is not yet there https://github.com/BONSAMURAIS/rdf/tree/master/activitytype/exiobase3_3_17

@kuzeko
Copy link

kuzeko commented Jan 20, 2020

@mfastudillo who is assigned to this issue?
The missing hsut names and the IO names is a different issue?

@mfastudillo
Copy link
Contributor Author

@kuzeko nobody has taken the responsability yet.

I am not sure which other issue you refer to. The supply table has 200 products, the input-output table has 164. This is done "aggregating" several products, for example aviation gasoline, motor gasoline, kerosene type jet fuel all become refined petroleum in the input-output table

@kuzeko
Copy link

kuzeko commented Jan 20, 2020

Regarding assignment, who is best equipped to fix this?
Regarding the "other issue" , you say we can't create a non-ambiguous correspondence until we have URIs for both the hsut names and the IO names.

Then you say The namespace for hsut names is not yet there , so my question is "this namespace missing, is this issue or is another issue?"

@mfastudillo
Copy link
Contributor Author

probably not all data should be here, but I added some tables with the labels, the "type(?)" and the relation to the hsut flow objects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants