Hi all, I think this is really a well made guide. We should probably collect useful introductory materials about RDF, LCIA, and other topics interesecting the BONSAI project. “An easy-to-read guide fo

#ontology #rdf #communication

Amazing, thanks a lot! --- Matteo Lissandrini Department of Computer Science Aalborg University http://people.cs.aau.dk/~matteo ________________________________________ Sent: 05 May 2020 15:15:09 To:

#infrastructure #rdf #ontology

The VM was blocked in a reboot cycle. I will investigate later why. After rebooting the VM, I triggered a new build ( #50 ) and it passed, I'm now verifying the state of the services.

#infrastructure #rdf #ontology

I think we can move to a resource in AAU --- Matteo Lissandrini Department of Computer Science Aalborg University http://people.cs.aau.dk/~matteo ________________________________________ Sent: 05 May

#infrastructure #rdf #ontology

* The server is a virtual machine hosted at digitalocean (see screenshot below) * I received a notification on maintenance on the "FRA1" network (where our VM is located) [see text below] * the error

#infrastructure #rdf #ontology

I'm on it. -----main@bonsai.groups.io escribió: ----- Para: main@bonsai.groups.io De: "Matteo Lissandrini (AAU)" Enviado por: main@bonsai.groups.io Fecha: 05/05/2020 11:23 Asunto: [bonsai] CI Deploy f

#infrastructure #rdf #ontology

https://bukk.it/error.jpg --- Matteo Lissandrini Department of Computer Science Aalborg University http://people.cs.aau.dk/~matteo ________________________________________ Sent: 05 May 2020 11:43:22 T

#infrastructure #rdf #ontology

The error is quite clear though: unexplained error

#infrastructure #rdf #ontology

Hi all, Tomas, the automatic deploy of the ontology is failing and we cannot understand why, see here: https://travis-ci.org/BONSAMURAIS/ontology Do you have any idea? Thanks, Matteo

#infrastructure #rdf #ontology

Hi all, combined with the access to the provenance data (which will proceed with new improvements soon), we are testing also a simplified web interface for the data. Now if you visit https://odas.aau.

#rdf #ontology #infrastructure

Hi, please see my answer below. SM: Yes, transports, insurance, etc. linked to imports are just accounted separately as normal inputs, but non necessarily in the national data. They can also be import

#rdf #issues #exiobase

>>>The trade data appear as imports in the Exiobase use table. Note that this is different from the way it appears in national supply-use tables. I am the only one who got lost? The trade data you ref

#rdf #issues #exiobase

Den 2019-11-08 kl. 10.59 skrev Chris Mutel: International trade activities, i.e. activities that move use of an export to become an import supply, do need to be FlowObject specific. Each such trade ac

#rdf #issues #exiobase

Hi Chris, trade data is only in the USE tables. The SUPPLY tables just show the production of activities and the location of the outputs is the same of the activities which produce them. Roughly speak

#rdf #issues #exiobase

Thanks Bo, this is clear and (at least in my opinion) completely consistent with all group decisions. Maybe I just missed it - entirely possible! - but the issue discussions did not seem to have this

#rdf #issues #exiobase

Hi all, I am not in the position of taking sides. I just want to provide one clarification here. Both options (keep the data as is in Exiobase, or re-aggregate) are compatible with the ontology. I wou

#rdf #issues #exiobase

Dear Chris, The issue is not about interpreting or deleting data, but simply to make the import of it consistent with our ontology. The Exiobase SUT data includes two kinds of data 1) inputs and outpu

#rdf #issues #exiobase

Sorry, I don't want to be a pain in the ass, but I think we are going a bit down the raod of Stalin's ideological purity here... In an ideal world, we would have separate sources of trade data, and co

#rdf #issues #exiobase

>> Will this require to write from scratch the Exiobase RDF converter? do I understand correctly or is this about some other data? > But we need to update this software anyway to a) make it a proper >

#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 aggregates: S

#rdf #issues #exiobase