W3C home > Mailing lists > Public > public-ldp@w3.org > March 2013

Re: Hypermedia as the Engine of Application State

From: David Wood <david@3roundstones.com>
Date: Fri, 15 Mar 2013 11:30:22 -0400
Message-Id: <2191AE1F-EA61-40CB-8918-4BE1509513EA@3roundstones.com>
Cc: "public-ldp-wg@w3.org Working Group" <public-ldp-wg@w3.org>, "public-ldp@w3.org" <public-ldp@w3.org>
To: James Leigh <james@3roundstones.com>
Hi James,

Thank you for your comment.  This issue is being formally tracked at:
 https://www.w3.org/2012/ldp/track/issues/55

NB: This issue should probably be tied to earlier discussions started by Mark Baker.  I could not find an existing issue relating to HATEOAS.

On Thu, 14 Mar 2013 09:18:35 -0400, James Leigh wrote:
> 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.

Regards,
Dave
--
http://about.me/david_wood





Received on Friday, 15 March 2013 15:30:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:03:10 UTC