HTTP-APIs / hydrus

REST server - Flask Hydra-powered for Semantic Web
https://pypi.org/project/hydrus/
MIT License
195 stars 130 forks source link

Querying: Linked Data Fragments #174

Closed Mec-iS closed 6 years ago

Mec-iS commented 6 years ago

I'm submitting a

Current Behaviour:

hydrus has no support for :

hydra-cg.com states:

Linked Data Fragments: API and client designs to publish and query Linked Data at Web-scale Get familiar with Linked Data Fragments or read the triple pattern fragments specification Various LDF data sources are already available. Query them.

Notes:

Expected Behaviour:

Triple Pattern Fragments are part of the Hydra specification. When and how should we implement them? It probably should be the right way to go to implement querying on the API.

[UPDATE] Implementation of Fragments have been moved to https://github.com/HTTP-APIs/python-hydra-agent/issues/3 This issue is about TPF only. How can we make hydrus a TPF-query enabled server?

Mec-iS commented 6 years ago

NOTE: General overview for the architecture for the TPF querying feature:

  1. The client represents the subsets as a TPF ? ? someObject
  2. The client passes the query to the server in a server-understandable format, that can be: http://localhost/api/someClass/tpf?s=query?p=query?o=someObject
  3. The server parse the fragment into its internal querying language, that can be CYPHER for Redis Lib or any other depending on the database supported
  4. The server responds with a JSON-LD of the requests subset of the dataset

See this link for more definitions.

vddesai1871 commented 6 years ago

The client passes the query to the server in a server-understandable format, that can be: http://localhost/api/someClass/tpf?s=query?p=query?o=someObject

What kind of effect someClass will have on the query? Can't it be http://localhost/api/tpf?s=query?p=query?o=someObject to expose the whole dataset?

Mec-iS commented 6 years ago

This has been moved to https://github.com/HTTP-APIs/python-hydra-agent/issues/3