OA2.0d11: Minor nit-pick regarding normalization

[Gavin Baumanis]

Hi Josh / Martin,

For the sake of an appropriate "short" sentence, is it not appropriate
to include Martin's text (or similar).
Does anyone really want to have read 1/2 a dozen extra specifications
for clarification of a single points that could be simply included in
the OpenID spec? For the sake of allowing me to more easily adopt
OpenID.

Sure  - we MUST have appropriate references, and SHOULD use a "quote"
from the authorative document - if it is clearly understood. If not, I
think it prudent to provide as a plain an English description / example
as is possible.

I have read a few specifications after being asked to
implement/incorporate them into work I was doing here at the university
- but for the most part I ended up throwing out the "spec" and visiting
a wiki or a mailing list - with regards to sourcing information on how
to implement the specification. I can't "ever" remember actually reading
a spec from start to finish for the purpose of implementing it. Used it
as a reference for information I collected elsewhere - most
certainly...

I realise the importance of the SPEC and I understand the technical
space in which they live, but surely we should practice what we preach 
- ease of uptake etc in our own documentation?


>>> On Friday, February 02, 2007 at 20:19, in message
<34714aad0702020119h138bc062qc688db331d8e8694 at mail.gmail.com>, "Josh
Hoyt"
<josh at janrain.com> wrote:
> On 2/1/07, Martin Atkins <mart at degeneration.co.uk> wrote:
>> The normalization table in appendix A.1 lists several examples of
the
>> normalization of URIs. The last few examples are as follows:
>>
>>      http://example4.com/ => http://example4.com/ 
>>      https://example5.com/ => https://example5.com/ 
>>      example6.com => http://example6.com 
>>
>> I believe that the last example should instead normalize to:
>>      http://example6.com/ 
> 
> You're right that the example needs to have the slash added. I don't
> think that we need any extra wording because RFC3986, which we
> reference for the normalization rules says:
> 
>    a URI that uses the generic syntax for authority with an
>    empty path should be normalized to a path of "/".
> 
> Josh
> _______________________________________________
> specs mailing list
> specs at openid.net 
> http://openid.net/mailman/listinfo/specs