[OpenID] URL normalization issues
jernst+openid.net at netmesh.us
Sat Mar 24 04:18:11 UTC 2007
On Mar 23, 2007, at 19:22, Gabe Wachob wrote:
> There's lots of forgotten history here.
Here is another example ;-)
> What people forget is that XRD (and XRDS) document is and always
> has been
> defined in the XRI Resolution specification. YADIS was actually
> completely different before the IIW meeting in October 2005 where
> we (the
> XRI folks) had a discussion with the LID and OpenID folks about
> using the
> XRDS document as the result of discovery on identifiers - until
> that point,
> there was *no* discovery in LID or OpenID, afaik.
There wasn't in OpenID, but there certainly was in LID. Turns out
that Yadis 1.0 is more powerful (also more complex) than the slightly
modified version of the LID discovery scheme that we (Brad, David,
Joaquin, myself) took into IIW as the original Yadis discovery draft,
which is why we are obsoleting the LID one.
> That XRD document can contain *any* metadata, but "service blocks"
> are what
> we (the XRI tc) defined and they are what OpenID uses.
> XRD documents can contain arbitrary XML - there was a lot of
> thought that
> was put into the extensibility model, including trying to anticipate
> versioning, extensions to existing elements, etc.
> So while the discussion here are about OpenID authentication (and
> services), the discovery mechanisms in XRI Resolution (including
> the thing
> formerly known as YADIS Discovery) could be used to discover *any*
> associated service metadata or any other metadata you wish to publish.
>> -----Original Message-----
>> From: general-bounces at openid.net [mailto:general-
>> bounces at openid.net] On
>> Behalf Of Steve Bjorg
>> Sent: Friday, March 23, 2007 7:17 PM
>> To: Martin Atkins
>> Cc: yadis at lists.danga.com; general at openid.net
>> Subject: Re: [OpenID] URL normalization issues
>> 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
>> 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
>>> 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
>>> 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
>> general mailing list
>> general at openid.net
> general mailing list
> general at openid.net
More information about the general