XRDS and Self Asserted Claims
Andy Dale posted posted some cautions in response to my post on using XRDS. He later summarized his concerns very succinctly: SEPs in XRDS must be considered self asserted claims and as such should not be trusted on their face. Service Providers should publish the mechanisms by which SEP claims should be validated to be about a specific subject (authenticated identifier). From The Tao of XDIReferenced Tue Jun 05 2007 13:48:15 GMT-0600 (MDT) For an authentication service, this isn't a problem. If I claim 2idi.com is my authentication service, the method for a relying party to check that claim
Continue reading {XRDS and Self Asserted Claims}
I-names and Usability
Kaliya likes i-names. She does a good job in this post of articulating why. There are a few things she points out, however, that will only be "good" and "simple" if we choose to make them so. In particular, she says "[d]omain names system usability sucks." The unstated implication is that XRI resolution won't. It's hard to tell since the tools for letting users do that aren't really available yet. Will they be better and easier to use? WE can only hope. Also, i-names are deceptively simple now because not many people are using them. What happens when all
Continue reading {I-names and Usability}
OpenID Delegation
Simon Willison (whose blog used to be green) has an excellent tutorial on setting up OpenID delegations so that you can use your own domain name (see what I said about persistence here) as your OpenID. In fact, you can use any URL where you control the resource (what gets returned when you GET the URL) as an OpenID. Delegation is an important part of OpenID because it allows you to switch OpenID identity providers, your OpenID stays the same. Just change the link tags in the resource associated with the URL you're using as an OpenID and you're
Continue reading {OpenID Delegation}
Making XRIs With XRDS
User-friendly view of my XRDS file(click to enlarge) Yesterday I posted a piece on XRIs and i-names at Between the Lines. Now that 2idi, my i-name registrar, is supporting forwarding, I've configured several XRIs that resolve to specific places on the 'Net including my blog, RSS feed, and even me at Skype. I mentioned William Tan's FoXRI extension to Firefox that allows native resolution of XRIs (e.g. xri://=windley/(+blog)) instead of using an XRI proxy. Playing with that tool, I realized that the XRDS document for =windley was pretty skimpy. William informed me that 2idi has a new experimental feature that
Continue reading {Making XRIs With XRDS}
i-names...Again
Salim Ismail(click to enlarge) I went to a session on the future of i-names this morning. Drummond Reed started off talking about what they are now. DNS names abstract IP numbers. URLs, based on DNS, typically point to specific locations. XRI provides an abstraction layer on top of the URL. i-names and i-numbers are synonyms. i-names provide a semantic identifier and i-numbers are a persistent identifier. i-numbers are never reassigned, but i-names might be. Having a non-assignable identifier ensures that I can't lose my identity (and the rights that go with it). Any synonym in the XRI namespace resolves to
Continue reading {i-names...Again}
IIW2006: Tuesday Afternoon Sessions
Doc, Dave Winer, and Don Park(click to enlarge) The afternoon started for me with a session that Dave Winer led on identity in OPML and RSS. There's a need to identify owners and authors in OPML and RSS without creating email addresses that can harvested by spammers. This is a good time to have this discussion because OPML 2.0 is being spec'd. The <head> section in the spec includes a <ownerId> that is defined thusly: [T]he http address of a web page that contains an HTML a form that allows a human reader to communicate with the author of the
Continue reading {IIW2006: Tuesday Afternoon Sessions}





