Namespaces ruin XML

I was reading up on FOAF today, and checking out an introduction at XML.com. On first blush, my gut feeling looking at the examples was that the FOAF dialect was messy and cumbersome. However, being the XML geek that I am, I stuck with it for another few minutes and decided it’s really very simple and straightforward.

I think the problem is that namespaces totally ruin the flow of reading for people, and if developers get turned off initially, it’s hard to ever win their hearts. Now I know all the logical reasons behind namespaces, but there has to be a way to get all the benefits of controlled, typed vocabularies while maintaining ease of reading and writing.

My proposal is to slightly modify the way XML elements are checked for their namespace. Right now, you can only have one (default) namespace that doesn’t have to be prefixed. I say why not make all namespace prefixes optional. Parsers should check the namespaces in the order they are listed at the top of the XML file to locate what namespace the element comes from. Using this method, only XML elements that are present in more than one listed namespace would have to be prefixed. Sure, it’s more work for parsers, but that’s a small price to pay for readability, writeability, and XML adoption.

ETech 2009: How the Tech Community Can Reinvent Risk Ratings

One of the most interesting presentations I saw at ETech was on credit risk data. Here’s a summary from: http://en.oreilly.com/et2009/public/schedule/detail/7513

With our latest project, FreeRisk, we aggregate accurate, accredited risk data, enabling users to generate crowd-sourced algorithms to analyze credit risk and allowing anyone to view the results of these algorithms. FreeRisk aggregates both all standardized XBRL data and public-domain financial data, as well as user-generated content incorporating unstructured data released in financial reports like footnotes, critical to accurate risk assessment. This system allows credit evaluators to focus exclusively on creating and applying risk analytics, instead of working through the complex data management tasks traditionally required to solve these problems or relying on black-box credit ratings.

These guys are extremely smart and have spent a lot of time working with XBRL, and yet one of their main conclusions was that XBRL was too complicated and therefore didn’t have a bright future. Thought that was very interesting.

Are Pigs Flying? Microsoft’s Big Interoperability News

Needless to say, I was shocked and amazed when I saw this statement on Microsoft’s new Interoperability Principles this weekend. To summarize, they are committing to make open and public the protocols and APIs for their major products, including Vista, Exchange, SQL Server, and Office. And, wait for this, access to those documents will be free. Is your mind blown yet? How about reading on and seeing that they plan to embrace non-Microsoft standards, and “increase interoperability with open source solutions”? I’m going to take all this at face value and say, “Bravo Microsoft!” I hope it all plays out according to this plan. The IT world will be a much better place if it does.