search

openbudgets / datasets

OpenBudgets.eu datasets
5 stars 3 forks source link

Epirus expenditure code lists 2012 and 2013 and revenue code lists 2015 and 2016 contain spaces in IRIs #66

Closed jindrichmynarz closed 8 years ago

jindrichmynarz commented 8 years ago

Epirus expenditure code lists 2012 and 2013 and revenue code lists 2015 and 2016 contain spaces in IRIs, which makes them invalid. For example:

skos:narrower <http://data.openbudgets.eu/resource/dataset/budget-epirus-expenditure-2013/codelist/04/071/9483 (α)> , <http://data.openbudgets.eu/resource/dataset/budget-epirus-expenditure-2013/codelist/04/071/9483 (β) ;

These invalid IRIs are also used in the Epirus datasets for 2012, 2013, 2015, and 2016.

NotisPhil commented 8 years ago

Fixed the expenditure datasets/codelists. Couldn't find the case in revenue code lists. Can you provide some more info?

jindrichmynarz commented 8 years ago

You can find invalid IRIs in RDF data using an RDF parser, such as Apache Jena's Riot.

riot --validate epirus-budget-revenue-codelist-2015.ttl
10:01:07 ERROR riot                 :: [line: 3898, col: 110] Bad character in IRI (space): <http://data.openbudgets.eu/resource/dataset/budget-epirus-revenue-2015/codelist/01/071/Τ.110[space]...>

This indicates an invalid IRI on line 3898. Similarly, you can test the 2016 revenue code list:

riot --validate epirus-budget-revenue-codelist-2016.ttl
10:02:58 ERROR riot                 :: [line: 4260, col: 110] Bad character in IRI (space): <http://data.openbudgets.eu/resource/dataset/budget-epirus-revenue-2016/codelist/01/071/Τ.110[space]...>
NotisPhil commented 8 years ago

Fixed them too.