|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Den 2019-10-30 kl. 16.07 skrev Agneta:
Why do the EXIOBASE consortium not just publish these on the website, saving us the hazzle of re-constructing the original data?
Bo
Den 2019-10-30 kl. 16.07 skrev Agneta:
Why do the EXIOBASE consortium not just publish these on the website, saving us the hazzle of re-constructing the original data?
Bo
|
By
Bo Weidema
·
#141
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Hi Bo/2.0 LCA Team
You (trough Stefano) have access to the repository having the country SUT tables. I can add more people to the box account if needed.
Best
Konstantin
Hi Bo/2.0 LCA Team
You (trough Stefano) have access to the repository having the country SUT tables. I can add more people to the box account if needed.
Best
Konstantin
|
By
Konstantin Stadler
·
#142
·
|
|
Re: Categories for Exiobase Activities and Flow Objects to enable Exploration
#ontology
#toolbox
Hi,
All available EXIOBASE concordances are gathered here
https://ntnu.app.box.com/s/ziox4zmkgt3cdsg549brr0qaecskgjsd/folder/47855342420
In the folder "other_ind_prod" you will find NACE and ISIC
Hi,
All available EXIOBASE concordances are gathered here
https://ntnu.app.box.com/s/ziox4zmkgt3cdsg549brr0qaecskgjsd/folder/47855342420
In the folder "other_ind_prod" you will find NACE and ISIC
|
By
Konstantin Stadler
·
#143
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
I am aware that we have priority access as consortium members. I was hinting to making this publicly available...
Bo
Den 2019-11-01 kl. 15.28 skrev Konstantin Stadler:
I am aware that we have priority access as consortium members. I was hinting to making this publicly available...
Bo
Den 2019-11-01 kl. 15.28 skrev Konstantin Stadler:
|
By
Bo Weidema
·
#144
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
These folders are as public as the updates of EXIOBASE (for everyone who contacts us) - they are in the public folder. I know that this is not the most elegant solution (not much I can do...).
These folders are as public as the updates of EXIOBASE (for everyone who contacts us) - they are in the public folder. I know that this is not the most elegant solution (not much I can do...).
|
By
Konstantin Stadler
·
#145
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Dear Konstantin,
This is good news to me! This implies that anyone who cares can re-publish them under the same license...
Best regards
Bo
Den 2019-11-01 kl. 15.49 skrev
Dear Konstantin,
This is good news to me! This implies that anyone who cares can re-publish them under the same license...
Best regards
Bo
Den 2019-11-01 kl. 15.49 skrev
|
By
Bo Weidema
·
#146
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Hi Bo,
That's muddy waters. The version on exiobase.eu has a licence which applies to the data there. This is the outcome of the EU-funded project.
The data on box is without licence. We worked on
Hi Bo,
That's muddy waters. The version on exiobase.eu has a licence which applies to the data there. This is the outcome of the EU-funded project.
The data on box is without licence. We worked on
|
By
Konstantin Stadler
·
#147
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Hi all,
I can provide the Exiobase hybrid version of national tables but I wonder whether this is the way to go. I try to explain it better.
Exiobase is a multi-regional IO
Hi all,
I can provide the Exiobase hybrid version of national tables but I wonder whether this is the way to go. I try to explain it better.
Exiobase is a multi-regional IO
|
By
Stefano Merciai
·
#148
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Dear Stefano,
Thanks for your reflections. In the long run, BONSAI should of course not rely on Exiobase or any other processed data, but on as a "raw" data source as possible. For IO
Dear Stefano,
Thanks for your reflections. In the long run, BONSAI should of course not rely on Exiobase or any other processed data, but on as a "raw" data source as possible. For IO
|
By
Bo Weidema
·
#149
·
|
|
Re: Categories for Exiobase Activities and Flow Objects to enable Exploration
#ontology
#toolbox
Hi
I did a correspondence between exiobase activities and nace 2 sections
(highest level of aggregation). It's in the repo
Hi
I did a correspondence between exiobase activities and nace 2 sections
(highest level of aggregation). It's in the repo
|
By
Miguel Fernández Astudillo
·
#150
·
|
|
Re: Categories for Exiobase Activities and Flow Objects to enable Exploration
#ontology
#toolbox
Thanks Miguel, this is great.
I don't remember, what do we need for the FlowObject instead?
---
Matteo Lissandrini
Department of Computer Science
Aalborg University
http://people.cs.aau.dk/~matteo
Thanks Miguel, this is great.
I don't remember, what do we need for the FlowObject instead?
---
Matteo Lissandrini
Department of Computer Science
Aalborg University
http://people.cs.aau.dk/~matteo
|
By
Matteo Lissandrini (AAU)
·
#151
·
|
|
Re: Categories for Exiobase Activities and Flow Objects to enable Exploration
#ontology
#toolbox
Hi Matteo
I think that would be the different sections of the CPC (central product classification). Classifing by “sections” is quite crude but relatively easy.
Hi Matteo
I think that would be the different sections of the CPC (central product classification). Classifing by “sections” is quite crude but relatively easy.
|
By
Miguel Fernández Astudillo
·
#152
·
|
|
Re: Categories for Exiobase Activities and Flow Objects to enable Exploration
#ontology
#toolbox
Thanks Miguel,
I will work on the activity one for now then.
In the current one I see tare only strings, isn't there a "code" for these ? Like for activities we have the Exiobase code
Thanks Miguel,
I will work on the activity one for now then.
In the current one I see tare only strings, isn't there a "code" for these ? Like for activities we have the Exiobase code
|
By
Matteo Lissandrini (AAU)
·
#153
·
|
|
Re: Categories for Exiobase Activities and Flow Objects to enable Exploration
#ontology
#toolbox
True, I did the correspondence to the label not the code. Currently it looks like this:
https://github.com/BONSAMURAIS/rdf/blob/master/activitytype/exiobase3_3_17/exiobase3_3_17.ttl
True, I did the correspondence to the label not the code. Currently it looks like this:
https://github.com/BONSAMURAIS/rdf/blob/master/activitytype/exiobase3_3_17/exiobase3_3_17.ttl
|
By
Miguel Fernández Astudillo
·
#154
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Sorry for chiming in late here.
+1 to the idea of only using the publicly available data, it seems to
me a very unnecessary and dangerous step to start using private (and
unlicensed!) data at the
Sorry for chiming in late here.
+1 to the idea of only using the publicly available data, it seems to
me a very unnecessary and dangerous step to start using private (and
unlicensed!) data at the
|
By
Chris Mutel
·
#155
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Hi Chris,
unfortunately half of what you say is alien to me, but I have the impression that this is about the numeric data that the RDF converter is handling.
Will this require to write from scratch
Hi Chris,
unfortunately half of what you say is alien to me, but I have the impression that this is about the numeric data that the RDF converter is handling.
Will this require to write from scratch
|
By
Matteo Lissandrini (AAU)
·
#156
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Hi Chris
The disaggregation to country level data is mainly to avoid the assumptions made using the trade matrix (info on markets for different flow objects). Current SUT tables include this
Hi Chris
The disaggregation to country level data is mainly to avoid the assumptions made using the trade matrix (info on markets for different flow objects). Current SUT tables include this
|
By
Agneta
·
#157
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
OK, but we can just... ignore... this location? Each national S or U
table by definition only has one location anyway.
In any case, I don't think there needs to be a discussion here, as our
ontology
OK, but we can just... ignore... this location? Each national S or U
table by definition only has one location anyway.
In any case, I don't think there needs to be a discussion here, as our
ontology
|
By
Chris Mutel
·
#158
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Indeed, this was not clear. Sorry. I was referring to
https://frictionlessdata.io/specs/data-package/ and
https://frictionlessdata.io/specs/tabular-data-resource/
Indeed, this was not clear. Sorry. I was referring to
https://frictionlessdata.io/specs/data-package/ and
https://frictionlessdata.io/specs/tabular-data-resource/
|
By
Chris Mutel
·
#159
·
|
|
Re: #rdf #issues #exiobase
#rdf
#issues
#exiobase
Hi Chris,
for how the data is now in the publicly available excel file, we can ignore for the SUPPLY, but we cannot "just ignore" the location for the USE table, we need to recompute the
Hi Chris,
for how the data is now in the publicly available excel file, we can ignore for the SUPPLY, but we cannot "just ignore" the location for the USE table, we need to recompute the
|
By
Matteo Lissandrini (AAU)
·
#160
·
|