Skip to content
This repository has been archived by the owner on May 21, 2019. It is now read-only.

LD Fragments integration #14

Open
ktk opened this issue Nov 1, 2015 · 1 comment
Open

LD Fragments integration #14

ktk opened this issue Nov 1, 2015 · 1 comment

Comments

@ktk
Copy link
Contributor

ktk commented Nov 1, 2015

It's not top priority but I do think it would make sense to think about how we could integrate LD Fragments support as well. I probably could do it with Varnish and a LD Fragments server on another node instance but maybe there are smarter ways to do this.

@bergos
Copy link

bergos commented Nov 1, 2015

I see the biggest problem in the LDF requirement that all blank nodes must be mapped to IRIs.

common:

  • add a .getTriplePatternFragment method to handler

ldp-module-handler:

  • blank node to IRI mapping could be done once during the server startup
  • a generic package, like the ldp module, could implement the LDF HTTP interface

sparql-handler:

  • maybe a script could create shadow named graphs with the mapped nodes
  • add a .buildLDFQuery method with a default implementation to the handler

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants