<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>Re: OA2.0d11: Minor nit-pick regarding normalization</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Agreed, good catch!<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Josh Hoyt [<A HREF="mailto:josh@janrain.com">mailto:josh@janrain.com</A>]<BR>
Sent: Friday, February 02, 2007 01:20 AM Pacific Standard Time<BR>
To: Martin Atkins<BR>
Cc: specs@openid.net<BR>
Subject: Re: OA2.0d11: Minor nit-pick regarding normalization<BR>
<BR>
On 2/1/07, Martin Atkins <mart@degeneration.co.uk> wrote:<BR>
> The normalization table in appendix A.1 lists several examples of the<BR>
> normalization of URIs. The last few examples are as follows:<BR>
><BR>
> <A HREF="http://example4.com/">http://example4.com/</A> => <A HREF="http://example4.com/">http://example4.com/</A><BR>
> <A HREF="https://example5.com/">https://example5.com/</A> => <A HREF="https://example5.com/">https://example5.com/</A><BR>
> example6.com => <A HREF="http://example6.com">http://example6.com</A><BR>
><BR>
> I believe that the last example should instead normalize to:<BR>
> <A HREF="http://example6.com/">http://example6.com/</A><BR>
<BR>
You're right that the example needs to have the slash added. I don't<BR>
think that we need any extra wording because RFC3986, which we<BR>
reference for the normalization rules says:<BR>
<BR>
a URI that uses the generic syntax for authority with an<BR>
empty path should be normalized to a path of "/".<BR>
<BR>
Josh<BR>
_______________________________________________<BR>
specs mailing list<BR>
specs@openid.net<BR>
<A HREF="http://openid.net/mailman/listinfo/specs">http://openid.net/mailman/listinfo/specs</A><BR>
</FONT>
</P>
</BODY>
</HTML>