bonsamurais / rdf Goto Github PK

Some provenance annotations have the URI not following the URI schema, i.e., their URI does not refer to the correct name graph or path.

Probably the relevant script needs to be fixed

The RDF files in the following

activitytype/ 
flowobject/ 
location/ 

foaf/ 
time/ 
unit/

are using the # scheme instead of the / scheme
This, per HTTP protocol implies that the entire content of the graph is downloade when we ask for somthing like

https://rdf.bonsai.uno/time#1802

While this is ok there because those contents are small, the data file are very large.

So, everything that will be deployed in the

http://rdf.bonsai.uno/data/

e.g.,

http://rdf.bonsai.uno/data/exiobase3_3_17/hsup

space needs to use the / scheme instead

This means that

 <http://rdf.bonsai.uno/data/exiobase3_3_17/huse#F_1111694>

needs to become

 <http://rdf.bonsai.uno/data/exiobase3_3_17/huse/F_1111694>

instead

Right now deployment is executed via a cron job on the serve.
So the Travis files are not used anymore.

E.g., https://github.com/BONSAMURAIS/rdf/blob/master/.travis.yml

Should be removed to avoid confusion (in all repos)

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 exiobase3_3_17.ttl file contains a definition for

<http://rdf.bonsai.uno/prov>

But it should contain at most a definition for

<http://rdf.bonsai.uno/prov/exiobase3_3_17>

Plus, it does not contain definition for

prov:hadMember

relationships

Files like
MR_HFD_2011_v3_3_1 7.xlsb
and
MR_HSUT_2011_v3_3_17_extensions.xlsb

define things like Acquatic plants and Final consumption expenditure by government

the corresponding RDF encoding in

https://github.com/BONSAMURAIS/rdf/tree/master/activitytype/exiobase3_3_17

and

https://github.com/BONSAMURAIS/rdf/tree/master/flowobject/exiobase3_3_17

are missing.

From a discussion with Søren

The exiobase foaf file and the ystafdb foaf files have duplicate information, they both define bfoaf:bonsai a prov:Agent,

Also the exiobase foaf file defines the <http://rdf.bonsai.uno/foaf> a dtype:Dataset ; instead of the <http://rdf.bonsai.uno/foaf/exiobase> a dtype:Dataset ; (or something similar)

A bonsai global foaf file is probably missing, while the two dataset specific should only contain information that is, indeed, dataset-specific

Missing declarations of type <http://purl.org/dc/dcmitype/Dataset> in the following:

./rdf/unit/unit.ttl
./rdf/foaf/foaf.ttl
./rdf/time/time.ttl
./rdf/location/exiobase3_3_17/exiobase3_3_17.ttl
./rdf/activitytype/exiobase3_3_17/exiobase3_3_17.ttl
./rdf/flowobject/exiobase3_3_17/exiobase3_3_17.ttl

To have the bonsai dataset added to the Linked Data Cloud
We need to satisfy the Linked Data Principles

In particular, we need to satisfy the following (quoting from the website):

• There must be resolvable http:// (or https://) URIs.
• They must resolve, with or without content negotiation, to RDF data in one of the popular RDF formats (RDFa, RDF/XML, Turtle, N-Triples).
• The dataset must contain at least 1000 triples.
• The dataset must be connected via RDF links to a dataset that is already in the diagram. This means, either your dataset must use URIs from the other dataset, or vice versa. We arbitrarily require at least 50 links.
• Access of the entire dataset must be possible via RDF crawling, via an RDF dump, or via a SPARQL endpoint.

The missing issue is then the "resolving" of URIs, I think we need something like an .htaccess file or a script that does the correct redirect to our rdf server or to the correct query at our sparql endpoint.

Where is this data going to ?
How is it generated (arborist ?)