W3C home > Mailing lists > Public > public-xg-webid@w3.org > April 2011

Re: self-signed

From: Jiří Procházka <ojirio@gmail.com>
Date: Tue, 19 Apr 2011 23:27:07 +0200
Message-ID: <4DADFE2B.5000408@gmail.com>
To: public-xg-webid@w3.org
On 04/19/2011 11:17 PM, Dan Brickley wrote:
> On 19 April 2011 23:01, Mo McRoberts <Mo.McRoberts@bbc.co.uk> wrote:
>>
>> On 19 Apr 2011, at 21:49, Kingsley Idehen wrote:
>>
>>> On 4/19/11 4:14 PM, Mo McRoberts wrote:
>>>> You yourself gave a key example of this right at the beginning of the
>>>> thread: you had certificates
>>>> with unsupported schemes, and they didn't work. You were confused as a
>>>> result, and thought there
>>>>   was a bug. You're a smart, experienced, technically-savvy user — how's
>>>> my grandmother going
>>>>   to cope with that situation?
>>
>>> Which is why implementers should deliver clear messages when they hit
>>> faults related to a URI that
>>> serve as WebID in a Cert.. That's basically the essence of the matter.
>>> This issue is a few steps away
>>> from grandma as she shouldn't really care about such details.  Not caring
>>> doesn't mean HTTP scheme
>>> specificity couldn't adversely affect her ability to control her own
>>> vulnerability (privacy) in cyberspace,
>>> at the very least.
>>
>> Okay then — excuse my ignorance — please outline to me, how _exactly_ it
>> will work when:
>>
>> a) Grandma has a "WebID" certificate containing only a SAN with a mailto:
>> URI
>>
>> and
>>
>> b) the server (with a "Log in with your WebID!” button) only supports http:
>> and https: URIs
>>
>> What *exactly* do you think should happen in this instance?
> 
> It shouldn't come to that. Where did Grandma get her mailto:-based
> WebID? Can we discourage the provider from this practice without
> saying "it's not WebID"? Can we write the spec in a way that
> discourages people from pushing out such things to non-technical users
> before there are enough consumers?
> 
> Some version of http://en.wikipedia.org/wiki/Robustness_principle "Be
> conservative in what you send; be liberal in what you accept."
> 
> So consumers MUST understand http/https, MAY understand others;
> publishers/providers SHOULD [your words here] ...?

Hi, that is pretty much what I have been advocating on foaf-protocol
list few months ago, but not re schema agnosticism, but the profile
syntax agnosticism - defining in a separate spec a brand of webid
suitable for marketing on general level, ie. not only to the tech savvy
people who will understand the value of agnosticism, but only to common
users and engineers who want something which just works and is fully
interoperable with every implementation of it.

http://lists.foaf-project.org/pipermail/foaf-protocols/2010-December/004322.html

I think it would be good if there was agreement of this, eventhough I
know you can dismiss my external comment, not being part of this XG, but
please consider it.

Best,
Jiri



> Dan
> 


Received on Tuesday, 19 April 2011 21:27:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:24 UTC