The day Google Chrome supports all the extensions I use with Firefox I can see myself switch to Chrome completely.

Less than two weeks ago, we brought to your attention 10 unique and fun easter eggs within Wolfram Alpha, the new computational knowledge engine that calculates answers based on your queries. You the readers though did your own sleuthing and found ten even better Wolfram easter eggs. And while that may have seemed like the end, it was not.

In my blog last year Is ODF the new RTF or the new .DOC? Can it be both? Do we need either? I raised the question of whether ODF would replace RTF or DOC. I think this issue has come…

In which I open the ODF 1.1 spec in Office 2007 SP2, immediately discover a bug with page breaks, trace it through the standards, find a workaround, then find the standard is not as clear as it should be.

This article looks at some trends and challenges for document validation. The challenges come in two classes: first, raw capabilities for lifecycle support for standards; second, coping with transitions from technologies defined by implementation to technologies defined by standards with the necessary agility.

An effort at ISO SC34 WG1 to try to get an agreed on way to associate documents with schemas. Plus some recent editors that support ISO Schematron, and a link to a good video introduction to Schematron for developers.

Lets look at the assertions in draft of HTML 5: The Markup Language which collects constraints about the markup: the kinds of things that are susceptible for schema testing.

Schematron run from inside JavaScript on the web-browser, editing structured documents/data trascribed to HTML. Click “validate” and a box comes up with a list of the validation problems; click on of those and the corresponding text or element is background-highlighted. Very slick. 300 lines of code only.

Here is a letter I have mailed to the W3C Technical Architecture Group (TAG) and to the W3C XML Schemas Working Group, regarding the XML Schemas 1.1 proposed recommendation. “I would like to register with the W3C TAG and the W3C XML Schema WG that, on having considered the XSD 1.1 draft, I think it is exactly the wrong direction for the WG and W3C to be taking. That is, while each individual decision may be well-founded, and each change justifiable and beneficial, the total effect will not help get us out of the mess that XML Schemas has created, but mire us further in it.”

The scene: a document of pharmaceutical data keeps on displaying  after each major drug name but before a generated trademark sign.