Last active
April 9, 2016 14:33
-
-
Save NTerpo/b81a0b195ceb99a7e53a to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"language": "en", | |
"name": "Paris Data", | |
"description": "City of Paris Open Data portal", | |
"url": "http://opendata.paris.fr/", | |
"linked_portals": ["http://data.gouv.fr", "http://data.iledefrance.fr"], | |
"data_language": ["fr"], | |
"modified": "2016-03-04T13:44:44+00:00", | |
"themes": ["Culture, Heritage", "Education, Training, Research, Teaching", "Environment", "Transport, Movements", "Spatial Planning, Town Planning, Buildings, Equipment, Housing", "Health", "Economy, Business, SME, Economic development, Employment", "Services, Social", "Administration, Government, Public finances, Citizenship", "Justice, Safety, Police, Crime", "Sports, Leisure", "Accommodation, Hospitality Industry"], | |
"links": [ | |
{"url": "http://opendata.paris.fr/explore/download/", "rel": "Catalog CSV"}, | |
{"url": "http://opendata.paris.fr/api/", "rel": "API v1"}, | |
{"url": "http://opendata.paris.fr/api/datasets/1.0/search?format=rdf", "rel": "Catalog RDF"} | |
], | |
"version": "1.0", | |
"number_of_datasets": 176, | |
"organization_in_charge_of_the_portal":{ | |
"name": "City of Paris", | |
"url": "http://www.paris.fr/" | |
}, | |
"spatial": { | |
"country": "FR", | |
"coordinates": [ | |
48.8567, | |
2.3508 | |
], | |
"locality": "Paris", | |
"data_spatial_coverage": "a Geojson with the data coverage" | |
}, | |
"type": "Local Government Open Data Portal", | |
"datapackages": [ | |
"http://opendata.paris.fr/explore/dataset/liste_des_sites_des_hotspots_paris_wifi/datapackage.json", | |
"http://opendata.paris.fr/explore/dataset/points-de-vote-du-budget-participatif/datapackage.json", | |
"http://opendata.paris.fr/explore/dataset/cinemas-a-paris/datapackage.json" | |
] | |
} |
Anyway, for better alignment with DCAT please change:
name
->title
url
->homepage
version
->conformsTo
and change the value to the URL for the documentation of this format (which should be a versioned web page)organization_in_charge_of_the_portal
->publisher
url
->homepage
spatial
-> make the value an actual GeoJSON feature, so:
{
"type": "Feature",
"geometry": {
"type": ...,
"coordinates": ...
},
"properties": {
"name": "Paris",
"country": "FR"
}
}
I've created a draft JSON-LD fork in order to actually enable round tripping with RDF: https://gist.github.com/ColinMaudry/5163ecade149a837aa25694fdd7ac46f. It's still incomplete, but it gives an idea.
And here is how it behaves when processing the JSON to RDF with the context: http://tinyurl.com/hdza9yp
Suggestions if we want to go further in that direction:
type
value should either be a keyword that we can resolve to a URI (ex: local-government) or a URI- As-is,
themes
values cannot be used in a UI in another language than English. A pity for French data :) Setting up a list of themes URI would enable multilingual support. As fortype
, in the JSON, thethemes
value could either be lower case keywords in English or URIs - I'm not very comfortable with property name in plural form. I assume it's a hint to know that the value is an array.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The best way to understand why a standard isn't being adopted is to ask the potential adopters (with an unbiased questionnaire, methodology, etc.). That said, I don't think the problem is that DCAT is too hard. I think it's that:
In short we need:
Creating some new format is not a solution for any of those. I really don't believe the problem is, "DCAT is hard." Let's at least validate what the real problems are before investing time and effort into a solution. Does that make sense?