CitySDK vocabulary merge

[pietercolpaert]

Today I came across a similar vocabulary which has been recently created:

https://github.com/waagsociety/citysdk/blob/master/rdf/public/citysdk.ttl

This might be interesting to consider?

[pietercolpaert]

404

[elf-pavlik]

I see @waagsociety has fork of OpenTripPlanner

• https://github.com/waagsociety/OpenTripPlanner

Also @bertspaan has relevant repo "Demo of CitySDK/OpenTripPlanner Analyst combination"

• https://github.com/waagsociety/schools

I guess they still may work on it...

[bertspaan]

@elf-pavlik You're right, we're still working on it - on both our CitySDK LD API as well as some tools combining data from CitySDK with OpenTripPlanner Analyst. As part of an European project (called CitySDK), Waag Society has developed the CitySDK Linked Data API, a REST API/datastore which combines city data from different data sources, and exposes this data in an uniform format - in GeoJSON, JSON-LD and Turtle. And over the last six months, we've been working towards version 1.0.

More information about version 1.0's capabilities and URI structure can be found in the project's wiki.

We currently have the 1.0 working branch running on test-api.citysdk.waag.org, and we hope to re-import data and add JSON-LD contexts for each data set soon. Example URLs:

• GeoJSON (default): http://test-api.citysdk.waag.org/layers
• JSON-LD: http://test-api.citysdk.waag.org/layers?format=jsonld
• Turtle: http://test-api.citysdk.waag.org/layers?format=turtle

[pietercolpaert]

Hi @bertspaan! Nice to hear from you! There are a couple of problems with the turtle and the json-ld documents, but this is probably because it's still a work in progress.

Regardless of that, could you point towards the JSON-LD context you use for the gtfs (or the vocabulary) and other transport datasets? What transport use cases are you providing a solution for with citySDK? Do you think any convergence is possible between our vocabularies and the ones citySDK is using atm?

[bertspaan]

@pietercolpaert Yes, it is. But I'd love some feedback - it would be great if you could open an issue in our citysdk-ld repo.

We have not yet created a context for the GTFS/public transport layers. We are currently in the middle of refactoring our old GTFS code to fit the new API. I see you are working on creating a GTFS vocabulary, I'll make sure we'll use this in CitySDK LD, too.

About the use cases: our API can be used to answer the following queries, for example:

• Return all bus stops in neighbourhood X in city Y.
• Return all tram lines calling at Amsterdam Central Station.
• Return the realtime departure time for stop X.

[elf-pavlik]

@bertspaan FYI https://github.com/OpenTransport/gtfs-csv2rdf

[pietercolpaert]

@bertspaan That's very interesting! Would you be interested in contributing the JSON-LD contexts for these use cases to this repository? I think it's interesting that other systems outside of CitySDK would use the same context

[bertspaan]

@pietercolpaert Of course! What can I do to contribute?

I could start with composing specifying some default JSON for each request/use case, and then see how the this JSON structure relates to the JSON LD contexts/ontologies you are working on.

[elf-pavlik]

once we have first draft we can link to if from https://github.com/json-ld/json-ld.org/wiki/existing-contexts

i will also try to contribute to writing JSON-LD context! :smile:

@bertspaan getting some examples of requests and responses sounds like a good start!

[bertspaan]

@elf-pavlik ok, I'll post some examples here next week when our GTFS code is working...

[pietercolpaert]

Awesome! If you're using our URIs, I'll add a link towards citysdk on our main README. If it's in production, I'll do a blogpost at http://transport.okfn.org :)