[OpenID] Dumb Question: Why isn't http://xri.net/=bobwyman an OpenID?
bob at wyman.us
Thu Jan 4 07:37:38 UTC 2007
Thanks for the detailed response. BTW: Below, you'll see what is happening
when I use the Yadis diagnostic on the HXRI. I believe that users will, in
fact, expect XRI's, i-names, and HXRI's to be interchangeable. I'm using
2idi.com, so I guess I have to wait for them to put in the fix?
Also, I find it a bit odd that the Yadis diagnostic reports a "pass" for
OpenID... Apparently, the metric for "passing" is pretty forgiving.
Results for *http://xri.net/=bobwyman*:
- I fetched http://xri.net/=bobwyman, asking for content type
- The document's content type is application/xrds+xml;trust=none. That
is the XRDS content type.
- There was no YADIS HTTP header.
- I got a document. It is 916 bytes long and begins '<?xml version="
1.0" encoding="UTF-8"?>\n<XRDS ref="xri://=bobwyman" x'
- I parsed an XRDS document.
- I found a service, but it's not a type I recognize. It's a service
- I found a service, but it's not a type I recognize. It's a
xri://+i-service*(+contact)*($v*1.0) service at
- I found a service: OpenID at https://2idi.com/openid/ with delegate
- I found a service: OpenID at http://2idi.com/openid/ with delegate
- *XRDS:* *Passed* Your YADIS URL leads to an XRDS document. Your
YADIS URL is http://xri.net/=bobwyman
- *OpenID:* *Passed* Your YADIS URL leads to at least one OpenID
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the general