W3C home > Mailing lists > Public > public-rww@w3.org > October 2013

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

From: <lehors@us.ibm.com>
Date: Sat, 26 Oct 2013 15:58:26 +0000
Message-Id: <E1Va6Fu-0008T0-KS@jessica.w3.org>
To: Tim Berners-Lee <timbl@w3.org>
Cc: public-ldp-comments@w3.org,Read-Write-Web <public-rww@w3.org>, Tabulator Developers <tabulator@lists.csail.mit.edu>
 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, and has
been implemented in the new version of the document available at:
https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html.

Please review it carefully and let us know by email at
public-ldp-comments@w3.org if you agree with it or not before 1 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.11 Resource Inlining: Representing Multiple Resources in
a Response:
> 4.11.1   "LDP does not provide clients with any way to detect whether or
> not the server is capable of inlining (all its resources or any specific
> resource), nor does it provide clients with any way to influence which
> (if any) resources are inlined in any given response."    This implies
> cleints must all be able to handle inlining and recover from it if they
> didn't really want it.
> 
> Need to define a protocol here properly or abandon the feature.
> 
> (N3 or one of its weak imitations is obviously a clear choice for a
> inlined data, as it allows you to preserve the provenance, and basically
> explain which triples are from which resource.  I understand this would
> frighten people at this stage.)


Working Group Resolution (LC-2837):
Drop inlining from the spec, put it on the wish list for LDPnext
See http://www.w3.org/2013/meeting/ldp/2013-09-12#resolution_2

----
Received on Saturday, 26 October 2013 15:58:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:10:43 UTC