- From: Henry Story <henry.story@bblfish.net>
- Date: Thu, 6 Dec 2012 13:29:14 +0100
- To: WebID Group <public-webid@w3.org>
- Message-Id: <D7B25AFB-09F0-4685-AF31-19CBFAEBE00B@bblfish.net>
In the MUST camp we have the following argument [[ Non #URI are problematic for LDP. What would it mean to: 1 to PATCH such a resource? 2. to DELETE it? 3. how would one create such a resource in an LDP Collection? [kidehen: LDP references are irrelevant unless this is WebID-for-LDP or LDP-WebID etc.. ] ]] ( I am very tempted to remove Kingsley's remark that LDP is irrelevant, since I don't see how he can argue that LDP is irrelevant AND argue that the Apple-Keychain-bug is relevant in other parts of the wiki. ) Still I don't see that argument is sufficient yet for a MUST, and I'd like some more input from those that support it. Here are counterarguments that I have heard and that seem valid: - if you want to PATCH, DELETE, APPEND a resource that sends a 303 that redirects to a document then you can PATCH, DELETE, etc the document linked to in the 303. Would it not be up to the server then to update the other URIs too? - Facebook has 1 billion #uris as one can see by trying out: $ curl -i -H "Accept: text/turtle" http://graph.facebook.com/bblfish But the don't use LDP. So is this an argument that those who don't have #URIs won't be able to move to LDP? Henry Social Web Architect http://bblfish.net/
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Thursday, 6 December 2012 12:29:47 UTC