CitySDK LD API
Now ⇒ Next ⇒ Later ⇒
We try to solve the following problem:
Data portal
Different silos
● not linked
Different file formats
Different data models & field names (1)
Different data models & field names (2)
Different data models & field names (3)
CitySDK Linked Data API
Data from different data sources
One unified REST API
Concept (1)
Concept (2)
Concept (3)
URI for each object
API for a read/write city
Public transport ●
parking ●
traffic information ●
weather forecasts ●
bicycles ●
addresses ●
events ●
monuments ●
POIs
Now
CBS - API
CBS - Map
Data: only key-value data
Fields + semantics per layer
Output: JSON & Turtle
Rijkswaterstaat
Turtle
Next
JSON LD context per layer
Data: any (nested) JSON object
Output: GeoJSON, Turtle, JSON-LD
JSON LD context per layer
require 'rdf/turtle'
require 'json/ld'
Examples!
Later
Research ways to make publishing linked data easier
1. Linking data sets
Rule-based, between pairs of data sets
1: Linking data sets
1: Linking data sets
2. Categorize objects
OpenStreetMap, DBpedia, Schema.org, …
2: Categorize objects
tourism=museum
dbpedia:Museum
schema:Museum
2: Categorize objects
3. Automatic linking
Linking rules + categories: automatic linking
3. Automatic linking
Support changing data sets
3. Automatic linking
