Microformats attempt to address this by using an alternative approach. They use the existing syntax of XHTML as the means for providing the semantics of the structured content. What this means in practicality is that web browsers are already set up to display them without a lick of extra code or plug-in.

Does this mean we’ll see an hMath format? Unlikely. The Microformat community embraces the approach of solving the 80% case quickly. This means focusing on putting structure around the basic types of information that we see commonly on the web, such as people, events, reviews, etc.

While I have nothing against Microformats at all, I do feel the need to dispute the implication that reliance on 3rd party plugins is a “bad thing”. The same people that feel that plugins are bad also probably argue that bloated, do everything apps like Microsoft Office are also bad. One gets the feeling that the underlying opinion is really Microsoft is bad — not that there’s anything wrong with that.

Although there may be valid reasons for believing that builtin support is better (don’t have to download and install the plugin for one thing), there is another, more important (IMHO), reason that plugins may be better.

While the builtin MathML support for Firefox is adequate, it doesn’t include Content MathML support and it doesn’t include interface with screen readers for accessibility via math-to-speech. Our MathPlayer does include these things but my point is that by providing a rich, powerful plugin mechanism, IE makes it possible for any closed source or open source company or individual to provide a plugin that does a better job or does it in a way that the consumer prefers. In other words, it is an enabling technology.

Bottom line: plugins are better than builtin, iMHO.

Paul Topping,
Design Science