Drummond, 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. bob wyman http://www.openidenabled.com/resources/yadis-test/yadis-detect?url=http%3A%2F%2Fxri.net%2F%3Dbobwyman&negotiation=on Results for *http://xri.net/=bobwyman*: - I fetched http://xri.net/=bobwyman, asking for content type application/xrds+xml - 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 at http://2idi.com/contact/ - I found a service, but it's not a type I recognize. It's a xri://+i-service*(+contact)*($v*1.0) service at http://2idi.com/contact/ - I found a service: OpenID at https://2idi.com/openid/ with delegate None - I found a service: OpenID at http://2idi.com/openid/ with delegate None - *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 service.
_______________________________________________ specs mailing list specs@openid.net http://openid.net/mailman/listinfo/specs
