ldp-ISSUE-55 (HATEOAS Compliance): Hypermedia as the Engine of Application State (HATEOAS) Compliance [Linked Data Platform core]

ldp-ISSUE-55 (HATEOAS Compliance): Hypermedia as the Engine of Application State (HATEOAS) Compliance [Linked Data Platform core]

http://www.w3.org/2012/ldp/track/issues/55

Raised by: David Wood
On product: Linked Data Platform core

This issue was raised by James Leigh on the public-ldp mailing list:

The description of containers does not read like a RESTful interface. I
think the specification should follow the REST guidelines closely.

http://www.w3.org/TR/2013/WD-ldp-20130307/#linked-data-platform-containers

One possible way to fix this is to:
      * Remove ?non-member-properties and ?firstPage query token from
        the spec.
      * Allow the server to omit some or all container members from the
        primary resource description (non-member-properties by default).
      * If some membership triples are omitted a link to the first/next
        page of membership triples (for each subject/predicate pair)
        must be present in the response.

The above still allows small containers to be represented completely in
one response and still allows paging for large containers. However, all
representations (all pages) are linked to from the default description.
By adopting the above the ldp spec would be RESTful.

Received on Friday, 15 March 2013 15:25:00 UTC