-
Notifications
You must be signed in to change notification settings - Fork 2
LDP, Hydra, LDF
elf Pavlik edited this page Nov 1, 2015
·
5 revisions
Comparison of commonalities and differences between LDP, Hydra and LDF APIs
- http://www.w3.org/TR/ldp/
- http://www.w3.org/TR/ldp-paging/
- http://www.hydra-cg.com/spec/latest/core/
- http://www.hydra-cg.com/spec/latest/linked-data-fragments/
- http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/
Hydra
- Interoperability with Linked Data Platform (especially regarding collections and paging)
- Add support for describing headers accepted in supported operations
- The TPF spec should recommend paging
- Discuss how usage of Collections "breaks" relationships
LDP and Hydra/LDF provide vocabularies for describing APIs, distinct from vocabularies to describe data which agents can pragmatically access through those interfaces.
- Link relations describedBy & describes
- foaf:primaryTopic
- void:inDataset
- http://www.w3.org/TR/ldp/#ldpdc | http://www.w3.org/TR/ldp/#ldpic
- http://www.hydra-cg.com/spec/latest/core/#collections | https://www.w3.org/community/hydra/wiki/Collection_Design
- http://www.w3.org/TR/2015/WD-activitystreams-core-20151006/#collections
- http://www.w3.org/TR/ldp-paging/
- http://www.hydra-cg.com/spec/latest/core/#collections
- http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/#paging
- http://www.w3.org/TR/2015/WD-activitystreams-core-20151006/#collections
One of main difference between LDP and Hydra/LDF seems to relate to difference in where one can find statements about the response. While LDP puts it in HTTP Headers, Hydra/LDF include it in the body of response.
See also: