Re: Re: Comments on LDP TR http://www.w3.org/TR/2013/WD-ldp-20130730/ ( LC-2836)

 Dear Tim Berners-Lee ,

The Linked Data Platform (LDP) Working Group has reviewed the comments you
sent [1] on the Last Call Working Draft [2] of the Linked Data Platform 1.0
published on 30 Jul 2013. Thank you for having taken the time to review the
document and to send us comments!

The Working Group's response to your comment is included below.

Please review it carefully and let us know by email at
public-ldp-comments@w3.org if you agree with it or not before 29 November
2013. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track.

Thanks,

For the Linked Data Platform (LDP) Working Group,
Eric Prud'hommeaux
Yves Lafon
W3C Staff Contacts

 1. http://www.w3.org/mid/34BE20B3-86E3-434F-B454-B004E9A338F0@w3.org
 2. http://www.w3.org/TR/ldp/


=====

Your comment on :
> #########################
> 4.10.2.3   303 lis a basically very unsatisfactory design because of the
> round trip.  As this is a new spec, suggest defined 20X code meaning
> like a 303 but containing the representation of the thing 303d to.  This
> has been found to a problem in LD. LDP can avoid it now.
> Benefit: First page back to user in one less round trip.
> #########################
> 
> 
> 4.10.2.4.3   This design puts the type and next links in the data.  I
> prefer I think using HTTP headers here as elsewhere.  Page control stuff
> is very meta, messy to have it in with actual data.
> Not a problem for containers, but for normal LDPRs IMHO.


Working Group Resolution (LC-2836):
Given the time constraints under which the WG is it is deemed unpractical
to depend on defining a new response code as suggested. However, based on
input from several HTTP experts the WG decided to return the first page
with 200 response code on initial GET which prevents the additional
roundtrip you objected to.
See http://www.w3.org/2013/meeting/ldp/2013-11-04#resolution_2

Move Paging information out of the RDF content into HTTP headers.
See http://www.w3.org/2013/meeting/ldp/2013-09-30#resolution_2


----

Received on Saturday, 16 November 2013 01:19:51 UTC