Re: Fwd: Seeking Feedback on Capability URLs Draft

An interesting question that 4.4 raises IMO is the question:

  Is the unattenuated resource actualy the same resource as the attenuated
  resource?

Apart from that, I think 5.1 starts off with the wrong mindset. Yes there
are problems, but not remotely close to those with the use of identity
where no identity is required. I would go as far as to sugest that the
sentences:


"The use of capability URLs should not be the default choice in the design
of a web application because they are only secure in tightly controlled
circumstances."

and

"If you are considering using capability URLs, you should consider other
options, the costs of implementing them and the risks of using capability
URLs instead."

would probably be more accurate if we were to replace 'capability url' by
' identity' :

"The use of 'identity' should not be the default choice in the design of a
web application because it is only secure in tightly controlled
circumstances."

and

"If you are considering using 'identity', you should consider other
options, the costs of implementing it and the risks of using 'identity'
instead."




On Fri, May 23, 2014 22:37, Jonathan Rees wrote:
> I am forwarding the below request for comments as a courtesy. I no longer
> have any affiliation with W3C or the W3C TAG.
>
> There is some discussion in the thread that Dan's message initiates,
> starting with John Kemp's reply here:
> http://lists.w3.org/Archives/Public/www-tag/2014May/0037.html
>
> Best
> Jonathan
>
> Begin forwarded message:
>
>> Resent-From: [email protected]
>> From: Daniel Appelquist <[email protected]>
>> Subject: Seeking Feedback on Capability URLs Draft
>> Date: May 23, 2014 9:28:04 AM EDT
>> To: www-tag <[email protected]>
>>
>> Hi folks - as discussed, I’ve made a blog post
>> http://www.w3.org/blog/TAG/2014/05/22/capability-urls-feedback/ seeking
>> some feedback on the Capability URLs draft. The goal here is to get some
>> more eyeballs looking at this and feeding back to us so we can finalize
>> this document and get it out the door as a finding by the July f2f. If
>> you
>> can help spread the word on this it will help get more feedback which
>> will
>> mean a better finding.
>>
>> Thanks,
>> Dan
>
> _______________________________________________
> cap-talk mailing list
> [email protected]
> http://www.eros-os.org/mailman/listinfo/cap-talk
>