- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Mon, 13 Apr 2015 10:34:52 +0200
- To: Kjetil Kjernsmo <kjetil@kjernsmo.net>
- Cc: public-hydra@w3.org
Dear all, > So, you could of course say that TPFs are *just* for the public Internet, > but I think that would be a mistake. The Triple Pattern Fragments specification has been updated such that it is no longer specific to HTTP. The specification now fully reflects that TPF is a hypermedia-driven REST API: “A REST API should spend almost all of its descriptive effort in defining the media type(s) used for representing resources and driving application state” [1] The main section of the specification now details the document type (http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/#document-type) and HTTP is merely a non-normative example (http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/#http-based-implementation). In the future, I want to make some editorial changes for readability. In particular, the hypermedia controls section is too vague still. After that, the specification document should be stable. As always, your feedback is most welcome. Best, Ruben [1] http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
Received on Monday, 13 April 2015 08:35:21 UTC