New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change to Comunica as a datasource #120

Open

1 of 4 tasks

pietercolpaert opened this issue Jul 21, 2019 · 0 comments

Member

pietercolpaert commented Jul 21, 2019

Right now, the data is fetched by individual classes resolving data using LDFetch

As an alternative, and from the moment comunica/comunica#473 is merged into master in Comunica, we must try to use this as a back-end.

To do:

Refactor Comunica to support custom hypermedia forms Refactor source type handling comunica/comunica#473
Add Tree ontology and tile referencing into Comunica as an actor
Add the Linked Connections departureTimeQuery search form into Comunica as an actor
Add an alternate data fetching strategies through Comunica

The ultimate goal is that we only configure Planner.js with 1 catalog, and that it knows where to fetch all the right datasets on the fly.

pietercolpaert mentioned this issue

Skip RDF parsing of json-ld files, parse them as JSON directly #102

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment