SREG namespace URI rollback

[Johnny Bufu]

Josh,

On 2-Apr-07, at 12:43 PM, Josh Hoyt wrote:

> I'd like to change the simple registration specification so that it
> uses the type URI that is currently in use in at least PIP and
> MyOpenID as the namespace URI instead of defining a new value.
>
> As far as I can tell, the only difference between the 1.0 and 1.1
> simple registration specifications is adding the namespace URI. The
> names and meanings of all of the fields are the same, so there is no
> compatibility issue, and the URI for 1.0 is already reserved (because
> it's used as the Type URI in XRDS documents).
>
> In short, I don't think that the SREG namespace/type URI should change
> until there are incompatible changes to the simple registration
> specification.
>
> So are there any objections to rolling the URI back to
> <http://openid.net/sreg/1.0> from
> <http://openid.net/extensions/sreg/1.1>?


I think the missing namespace in SREG1.0 can cause problems; take  
this example:

- RP doesn't support SREG1.0, but does support 2.0 extensions
- RP sees in an XRDS that the OP supports SREG1.* (if the same  
namespace is used for both)
- the OP actually only supports SREG1.0
- RP gets an SREG response without the namespace param
- RP tries to extract SREG1.1, doesn't find a namespace and can't  
handle it

So the OPs that will implement only SREG1.0 will not honor their  
statement in their XRDS files, which would require them to implement  
both versions.


Johnny