- From: Pieter Colpaert <pieter.colpaert@ugent.be>
- Date: Sun, 8 Nov 2015 10:13:15 +0100
- To: public-dwbp-wg@w3.org
Hi Bernadette,
GTFS at this moment is the de facto standard for timetables today. Thus,
using it to publish transit data is the way to go.
Linked GTFS [1] (I'm the author) is indeed a direct mapping of GTFS
terms to URIs. It's thus interesting to be able to link to both the
terms ("this thing is a transit stop as defined by gtfs:Stop") and the
instances from the data ("this thing follows the service schedule as
defined in this GTFS feed").
At this moment, there's a nodejs mapping script [2] to convert a zip
archive in GTFS-CSV to Linked GTFS. It would be a great use case for
this WG to recommend a way to configure the baseURIs of the identifiers,
and a way for Linked GTFS to become the vocabulary/context (cfr.
json-ld) of the GTFS files. I'd be glad to implement this in [2] as a
proof of concept of your work here.
Mind that Linked GTFS however, is less (or not?) interesting to use to
e.g., SPARQL for route planning advice. Instead, you could use Linked
Connections [3] (my PhD topic - WIP).
Kind regards,
Pieter
[1] http://vocab.gtfs.org
[2] https://github.com/OpenTransport/gtfs-csv2rdf
[3] http://linkedconnections.org/
--
+32486747122
Linked Open Transport Data researcher
UGent - MMLab - iMinds
Board of Directors Open Knowledge Belgium
http://openknowledge.be
Open Transport working group coordinator at Open Knowledge International
http://transport.okfn.org
Received on Sunday, 8 November 2015 09:13:44 UTC