XRDS Simple for Movable Type

[Steve Ivy]

Hey DiSo-ers,

I know most of you are WordPress folks, but here's something fun: my
memorial Day contribution to MT -- XRDS Simple for Movable Type 0.1.

http://redmonk.net/archives/2008/05/27/xrds-simple-for-movable-type/

This plugin is a faceless app that gives other plugins the ability to
register services to be included in the XRDS doc. I'm hoping for some
feedback from the MTOS crowd in the next few days.

Cheers,

--Steve

--
Steve Ivy
http://redmonk.net // http://diso-project.org
This email is: [ ] bloggable [x] ask first [ ] private

[Chris Messina]

Excellent! Does Stephen's plugin offer this? If not, we'll need to make changes to his plugin to maintain parity...

Chris

--
Chris Messina
Citizen-Participant &
Open Source Advocate-at-Large
factoryjoe.com # diso-project.org
citizenagency.com# vidoop.com
This email is: [ ] bloggable [X] ask first [ ] private

[Steve Ivy]

I believe it does, after a fashion.

[Stephen Paul Weber]

It does, although the API is different (the MT version is more focused
on services which happen to go into XRDSs documents, mine is more
focussed around the way the XRDSs document ends up structured : mostly
because of the way OAuth works).

--
- Stephen Paul Weber (Singpolyma)

Web: http://singpolyma.net/
Twitter: http://twitter.com/singpolyma
IM: singp...@gmail.com

[Steve Ivy]

Hi Stephen,

On Wed, May 28, 2008 at 6:34 AM, Stephen Paul Weber
<singp...@gmail.com> wrote:
>
> It does, although the API is different (the MT version is more focused
> on services which happen to go into XRDSs documents, mine is more
> focussed around the way the XRDSs document ends up structured : mostly
> because of the way OAuth works).

What do you mean by this? I want to make sure I'm not missing
something or limiting developers in how my plugin works...

[Stephen Paul Weber]

On Wed, May 28, 2008 at 9:35 AM, Steve Ivy <stev...@gmail.com> wrote:
>
> Hi Stephen,
>
> On Wed, May 28, 2008 at 6:34 AM, Stephen Paul Weber
> <singp...@gmail.com> wrote:
>>
>> It does, although the API is different (the MT version is more focused
>> on services which happen to go into XRDSs documents, mine is more
>> focussed around the way the XRDSs document ends up structured : mostly
>> because of the way OAuth works).
>
> What do you mean by this? I want to make sure I'm not missing
> something or limiting developers in how my plugin works...

Well I haven't been through the code in your plugin yet (my skillz in
the language being less than there yet) - but the way I understand it
you register services that go into the XRD, yes? Mine you register
either a Service (specifying what XRD it should go into) or you can
register a whole XRD (and then put services into it, ususally), to
facilitate for OAuth:

<XRD xml:id="oauth">
...oauth services...
</XRD>

<XRD>
<Service>
...oauth main service...
<URI>#oauth</URI>
</Service>
</XRD>

Yours may well be able to do this after a different fashion though.
Both our plugins seem meant for exactly the same thing - just written
in a slightly different way (oh, and for different platforms, heh, ++
on all the MT work! annoys me when people think we're just WP around
here...).

[Steve Ivy]

Ah, I actually recoded my plugin to format the XRDS file the way you
have it (based on ma.gnolia's oauth XRDS file). Gimme a sec and I'll
upload a sample.

On Wed, May 28, 2008 at 6:40 AM, Stephen Paul Weber

--

[Steve Ivy]

Ok, you can see an example here:

http://www.wallrazer.com/mt/mt.cgi?__mode=xrds_simple

I've modified that instance to serve as "text/plain"rather than as
"application/xrds+xml" so that it's easier to view. I created a sample
config there that has both an openid2 config and the complete
ma.gnolia oauth config. Here's the config YAML:

http://pastie.textmate.org/204725

--Steve

[Stephen Paul Weber]

Does OpenID work like that? Last time I read the spec it looked like
it wanted all the data in the last XRD - do they support #openid like
that ?

[Steve Ivy]

Hm, I assumed that it was standard, but I'll go check out the spec.

On Wed, May 28, 2008 at 8:01 AM, Stephen Paul Weber

[Steve Ivy]

well, that's embarassing.

http://openid.net/specs/openid-authentication-2_0.html#XRDS_Sample

guess I'll have to special case openid.

[Steve Ivy]

Ok, I've fixed that. The openid section is now rendered completely
inside the final, global, XRD element, with no changes to the
configuration.

http://www.wallrazer.com/mt/mt.cgi?__mode=xrds_simple

--Steve

[Eran Hammer-Lahav]

XRDS parsing defaults to the last XRD in the document. XRDS-Simple adds official support for pointing at specific XRDs within the document. For now to be safe all OpenID services should be in the last XRD. Eventually we’ll get XRDS-Simple support everywhere.

EHL