Closed Mec-iS closed 6 years ago
NOTE: General overview for the architecture for the TPF querying feature:
? ? someObject
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?
This has been moved to https://github.com/HTTP-APIs/python-hydra-agent/issues/3
I'm submitting a
Current Behaviour:
hydrus has no support for :
hydra-cg.com states:
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?