Hungary votes for open standards | The Open Road – CNET News
The Open Standards Alliance proposed and lobbied for the change to Act LX of 2009 on electronic public services within Hungarian law. The goal? To “promote the spread of monopoly-free markets that foster the development of interchangeable and interoperable products,” thereby opening up the market to “broad competition.”
Open Messaging Here We Come: Tumblr Releases Twitter Client API – ReadWriteStart
In response to today’s Tumblr announcement, RSS pioneer and blogger Dave Winer writes, “Conventional wisdom says that open standards are created by endless deliberations among experts and big tech companies, and those sometimes gain traction, but this is how it usually happens. Someone goes first. No one thinks of it as an open standard. Then someone clones it. All of a sudden people get ideas. Inspired, someone goes third. At this point it’s inevitable that there will be a fourth and fifth and so on.”
How open standards are created. (Scripting News)
Marco at Tumblr says that he was inspired by the “seriously clever” use of the Twitter API by WordPress. Of course I was too. When they came out with it I wondered out loud if the Twitter API is now an open standard.
Well, less than a week later, Tumblr now has implemented the Twitter API, and as a result you can use any Twitter-compatible tool to post to and read from Tumblr.
TomsTechBlog.com – Not Everything Needs To Be Standard
Which brings me to my final point. APIs aren’t file formats. In a file format the whole point of it is to store and retrieve data so it makes sense to adhere to standards because not doing so would prevent the data from fulfilling it’s purpose (to be read). But APIs aren’t like that. Having a different API isn’t going to break anything. So while developers should always look at the APIs of other companies for inspiration they shouldn’t treat successful APIs like Gospel
The Twitter API is Finished. Now What? – Anil Dash
Twitter’s API has spawned over 50,000 applications that connect to it, taking the promise of fertile APIs we first saw with Flickr half a decade ago and bringing it to new heights. Now, the first meaningful efforts to support Twitter’s API on other services mark the maturation of the API as a de facto industry standard and herald the end of its period of rapid fundamental iteration.
Anil Dash is Wrong About Treehouse Clubs | Workbench
I used to think that too, but after spending so many years involved with RSS, I have a better understanding of the costs that developers incur because of half-assed specs. During the 18 months in which the RSS Advisory Board drafted the RSS Best Practices Profile, we accumulated more information on how RSS has been implemented than anybody else on the planet. It’s never a good thing for a specification to be “potentially ambiguous.” If two developers disagree on what a spec means, their software will not interoperate. And once their software ships, they’ll be mad as hell if the specification is revised to make their interpretation the incorrect one.
Posted from Diigo. The rest of my favorite links are here.