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

Re: Discovery/Affordances (Issue-32/Issue-57)

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Mon, 10 Jun 2013 14:44:21 -0400
Message-ID: <51B61E85.2090000@openlinksw.com>
To: public-ldp-wg@w3.org
On 6/10/13 2:22 PM, Arnaud Le Hors wrote:
> Henry Story <henry.story@bblfish.net> wrote on 06/10/2013 09:09:43 AM:
> > ...
> > So as argued above you can use the Link header and also use the
> > ldp:Container there in the same
> > way as you do with the body. What is the profile adding?  What
> > vocabulary would need to be used to
> > describe the profile?  Do we need this now or can we add it later?
> > Unless those questions are answered
> > this seems like a lot of work to do when we can just use
> > ldp:Container to mean: you can POST to this
> > container.
> > ...
> I have to admit not to know what it takes to create a profile but I 
> wonder why you think this is a lot of work. 

Is that a fair comment in a forum like this? You are promoting a 
solution for which you have no sense of what implementation takes?

Henry and I are going to immense degrees of detail to defend our 
positions, and you can casually throw something into the mix without 
clarity about the implementation details?

> Maybe Erik can help us there?

Yes, we have been waiting on him to actually provide concrete examples 
to defend his positions.

> I see this is as a simple marker that doesn't require much anything 
> else than be defined in the spec as a way the server can advertise it 
> is supporting LDP.

Well, I don't buy the use of "simple" as the exit from critical matters 
like this. May I remind you, the Web itself is "deceptively simple" 
rather than "simply simple".

If you want' to know the cost of trivializing the architecture of the 
Web via the Web 2.0 "simply simple" mantra, just look at the effects of 
PRISM on the privacy of every Web user that's had the misfortune of 
buying into the "simply simple" approach to negating good and robust 

The Web isn't based on casual architecture, it simple enables you work 
with it casually. That's a solid architecture affordance.

> I think the advantage is that it can be used on all types of 
> resources, independently of whether it's an ldp:Container or not.

Really? Please tell us how.

> Regards.
> --
> Arnaud  Le Hors - Software Standards Architect - IBM Software Group



Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

Received on Monday, 10 June 2013 18:44:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:51 UTC