[OpenID] URL normalization issues
steveb at mindtouch.com
Sat Mar 24 02:16:47 UTC 2007
I'm new to the list, but have been reading it for a while. I say
that, because I don't agree with statement below. Maybe that's due
to my misunderstanding, but it seems that Yadis has a greater purpose
than to just serve OpenID. I was actually thinking of leveraging it
to create additional associations with different non-identification
based services. Being able to find everything in one place
(identity, preferences, etc) is very appealing. So, coupling XRDS
to OpenID would diminish it potential in my opinion.
Does anybody else use XRDS for more than just identification?
Steve G. Bjorg
On Mar 23, 2007, at 6:50 PM, Martin Atkins wrote:
> Lukas Rosenstock wrote:
>>> One of the problems with XRDS discovery (formerly known as Yadis) is
>> Is it not Yadis anymore?
> I'm not sure it was ever really completely accepted, but I was working
> on splitting Yadis into two chunks, where one is how to do service
> discovery on a subset of the XRDS format, and the other was how to
> resolve an XRDS document for an HTTP URI.
> I never actually did write up the draft of the HTTP URI discovery
> though. I should do that.
> The dropping of the Yadis name is a separate issue, but one I do
> support: Yadis was originally a separate spec because it was to bring
> together several technologies such as LID, Sxip, etc. Now that most
> (all?) of the former Yadis stakeholders are taking part in OpenID
> there's no longer the big political reason to keep the HTTP-based
> discovery distinct from the OpenID brand, and having all of the
> specs be
> part of a single family makes things easier to understand for
> general mailing list
> general at openid.net
More information about the general