Recently, there has been an interesting question about user nomenclature in federated micro blogging systems. By micro blogging systems, I’m talking about sites like Twitter, Plurk, Rejaw, and Identi.ca. Right now, Identi.ca is the only one that truly supports the ability to subscribe to be subscribed from other micro blogging systems, although there are some sites that that facilitate exchanging messages between different micro blogging systems.

So, the question of nomenclature: How do you refer to a person on a remote micro blogging system? Typically, users are referred to with an at sign prepended to their username. The problem is that @bob might be one person on one system and someone completely different on a different system. So, to clarify, people have been kicking around ideas of how to refer to people at other systems.

Personally, I like the format @username/system e.g. @ahynes1/identica Concerns are to keep the name short. After all you only have 140 characters to deal with in an SMS message and putting in full qualification can eat up valuable message space. Others have suggested using the at sign as a separator between the username and the system, e.g. @ahynes1@identica To me, that looks cumbersome and kludgy. On my cellphone, where spacing is harder to differentiate, I would be confused about whether this were to the user ahynes1 on the identica system, or to two people, ahynes1 and identica.

Another reason I like the @username/system format is that it fits nicely with XRIs which fit nicely with OpenID 2.0. @username/system is an accepted shortcut to xri://@username/system which can be accessed via the http protocol as http://xri.net/@username/system The at sign is an indicator of a company, which isn’t great. Registering a company in XRI costs $55/year, which is pretty excessive. Nonetheless, I thought it would be nice to register @ahynes1.

A long time ago, I registered =aldon.hynes. I never ended up using it much, other than for some software testing and as a forwarder so people could send me email without knowing my current email address.

As OpenID 2.0 came along and started supporting XRI logins, I found that I could login to identi.ca using =aldon.hynes. I thought that was pretty cool and changed my OpenID delegation to point to my XRI registrar. Unfortunately, many sites do not yet support XRI based OpenID logins, but it seems to be growing.

So, to test things out a little bit, I registered @ahynes1. Initially, I was going to use 2idi.com, since that is where I have =aldon.hynes registered. Unfortunately, for some reason, they wouldn’t take my credit card, so I checked out some other services and found that 1id.com took Paypal and would gladly take my money.

The next step was to set up a few forwarders. I set up @ahynes1/identica to point to http://identi.ca/ahynes1 and @ahynes1/twitter to point to http://twitter.com/ahynes1. So, for any microblogging site that takes @username/system and uses it as an XRI reference, at least my name will resolve in both Twitter and Identica.

With that, I then tested an added benefit. Would @username XRI references resolve properly in OpenID? I logged into Identi.ca as =aldon.hynes and added @ahynes1 as a valid alternate OpenID. So, now I can log into my Identi.ca account by using the OpenID @ahynes1 Pretty cool.

Now, there are people that have voice concerns about XRI. Why do we need XRI if we already have URIs? For me, XRIs are how we identify resources. URIs specify a transport to get to the resource. So, =aldon.hynes, or xri://=aldon.hynes identifies me. http://xri.net/=aldon.hynes is how to get to my identification information over the http protocol. Nice and clean in my name.

The other issue is pricing. $55/year is very steep for registering an XRI corporate domain. I can register a corporate DNS domain for something like $10/year. If XRI is going to take off, the pricing structure will have to change. At $12/year for an individual I-name, it is still a tad expensive, but a little more reasonable.

So, Identi.ca, OpenID and XRI work nicely together. It will be interesting to see where things go from here.