<xml.lt>

I looked at the design of some well-known public APIs for inspiration, especially for RESTful designs.
Last.fm API and Flickr API are pretty neat and quite similar. They offer a set of methods (such as artist.getSimilar to get artists similar to an artist, or photos.getInfo to get information about a photo) and different request methods to call them, such as REST, XML-RPC and SOAP.

However, when I looked into the RESTful method, neither Last.fm REST Requests nor Flickr REST Request Format impressed me because in my eyes the design is not really RESTful. With the aforementioned methods, they go like this:

http://ws.audioscrobbler.com/2.0/?method=artist.getSimilar&api_key=...
http://api.flickr.com/services/rest/?method=flickr.photos.getInfo&api_key=...

I would have expected something along the lines of:

http://ws.audioscrobbler.com/2.0/music/Fridge/similar
http://api.flickr.com/services/rest/photos/2733/&api_key=...

Yesterday OpenID Denmark organized an event, which focused on practical and commercial advantages of OpenID support. Main speaker Nat Sakimura presented status, opportunities and roadmap for OpenID, as well as market development and use cases of OpenID in Japan, where it is extremely successful.

Friday also brought a couple exciting news for OpenID. Facebook decided to join OpenID Foundation and is expected to help improving user experience.
The other news come from Lithuania, where all new electronic personal identity cards issued after 1th of January 2009 now have a digital certificate (x.509) and full OpenID 2.0 and PAPE extension support. National Sertificate Center under the Ministry of Inferior will be the national OpenID provider (at openid.vrm.lt). It is currently in testing mode.