At the end of March, the W3C announced the launch of the Internationalization Tag Set (ITS) Interest Group (IG) as a forum to foster a community of users that promotes the tag set's adoption and further development. Like Unicode's CLDR initiative, the emphasis on community interaction and collaboration underscores the ever-increasing, Web-driven impact of cooperative spirit.

As the Web nears its 20th birthday, we would imagine efforts such as ITS IG continue to be music to the ears of its inventor and W3C founder, Tim Berners-Lee. This particular interest group is certainly not the first nor the last of the educational and outreach efforts the W3C has launched since 1994.

It is also not the first nor the last of the activities from W3C's Internationalization (I18n) Activity, known worldwide as simply I18n. The mission? "To ensure that W3C's formats and protocols are usable worldwide in all languages and in all writing systems." The goals? Ensure universal access, support the internationalization and localization of documents, and help reduce the time and cost associated with internationalization and localization projects. Consistent and admirable objectives, described eloquently by Richard Ishida, Activity Lead for the I18n Core Working Group in his article, It's All About Customer Focus.

I18n accomplishments include a treasure trove of information from specifications and recommendations to educational materials to the newest initiative, hosting the Planet I18n Blog aggregator. Worth checking out; give yourself time to stay a while.

Using XML and Databases: W3C Standards in Practice serves as a handy reference guide to the current status of the major XML standards.

Component Content Management in Practice: Meeting the Demands of the Most Complex Content Applications provides an overview of the requirements for technology that manages content at a granular level. To quote the executive summary:

[The paper] compares the requirements of component content management with the capabilities of more general content management technologies, notably web content management and document management. It then looks at the technology behind CCMS in depth, and concludes with example applications where CCMS can have the most impact on an enterprise.

No registration is required to read or download the papers.

UPDATE: Updegrove is now reporting OOXML will pass the vote, and Slashdot has a roundup that includes reports of irregularities in the voting.

The XSL Working Group has published the First Public Working Draft of Extensible Stylesheet Language (XSL) Requirements Version 2.0. This document enumerates the collected requirements for a 2.0 version of XSL Formatting Objects (XSL-FO), not for XSLT. XSL-FO is widely deployed in industry and academia where multiple output forms (typically print and online) are needed from single source XML. It is used in many diverse applications and countries on a large number of implementations to create technical documentation, reports and contracts, terms and conditions, invoices and other forms processing, such as driver's licenses and postal forms. The XSL Working Group invites people to help prioritize the feature set of XSL 2.0 by completing a survey until the end of September 2008.

I talk to developers who have ideas about improving XLST. Now is your chance.

I need to do some housework in my blog list. Out of those 50 or so blogs, at least 10 seem to be completely dormant, and a number are very rarely updated. But there are some I read regularly. These include:

• General CMS blogs like Trendwatch at CMS Watch and the blog Conquering Information Chaos by AIIM's John Mancini


• Two titans of the general technology blogosphere, Dave Winer and Jon Udell.


• The DITA blogs at XML.org.


• The blog by Mark Logic CEO Dave Kellogg.


• The amazing eBook blog at TeleRead, maybe the most in-depth technology blog on a single subject out there.


• The blog by Brian Jones at Microsoft, who is fronting a lot of their work with Microsoft Office file formats at ISO.


• For DRM, the one and only source, Bill Rosenblatt's DRM Watch.

Aside from blogs, I read XML.com of course, and Robin Cover's Cover Pages. (You have XML pretty much covered if you read these two things--and Gilbane.com of course!)

One other thing I do is use Google news and blog alerts, though sparingly, as you can really get overwhelmed. I get a daily Google Alert on XForms, for example, that is usually very good.

Note that I didn't mention email. I do get a lot of things in my inbox, and read some, but I spend more time pruning my email than I do reading it. I also periodically unsubscribe to email lists and then curse myself for joining them in the first place. I read a few yahoo groups regularly (notably dita-users, now 1824 members strong!), but use the browser interface for that more and more.

So that's my bag of tricks. Any thing else I should be reading?

Like XBRL, RIXML has great potential to enhance how financial analysts work with financial content. With rich, XML-encoded financial information, you can imagine analysts finding ways to better filter information, to develop powerful queries and reports, and to commingle research content from various sources. I was talking to colleague Geoff Bock about this, and we both know financial analysts who do all this now, but do it with Excel. They are the ultimate Excel power users, and they consume and model vast amounts of financial information. And they typically do this under tremendous time pressure.

XBRL clearly has traction--9,540,000 Google hits, lots of vendor support, and a roadmap to mandatory SEC adoption (warning, big PDF file!). RIXML is a more nascent effort--9,740 Google hits--but its potential impact is significant. Financial reporting and research data already has an important lifecycle. We see it in the markets every day, though most of us only from a distance. XML has the potential to make this lifecycle much more efficient, much more content-rich, and much less dependent on the manual efforts of those frazzled financial analysts. Instead of 16-hour days during earnings season, maybe they can work, heck, 14-hour days! (Actually, their managers will likely just give them a few more companies to cover...)

By the way, an obvious question to ask about RIXML is how it might integrate with XBRL. This too is nascent, though the two organizations have signed a very general memorandum of understanding. You can also find a related presentation here (PDF again).

UPDATE: The SEC has launched a new website, Financial Explorer, that enables users to generate custom data from the underlying XBRL-encoded reports.

Hat tip, Dave Winer.