Hi.
> > The open question is what should happen when the MathML has an error in the
> > XML parser sense. David and I both lean to "don't try to guess, because
> > you'll likely get it wrong and I won't know" school. We think the "repair"
> > should be to wrap the offending part in an mtext (if it was missing a tag),
> > do what it takes to build a valid MathML DOM, and wrap the whole thing in
> > <merror> so that the user is informed something went wrong.
>
> That is clearly right for XML. It may be too draconian for HTML,
> which traditionally never shows an error message.
My own preference would be to do the repair in place with an merror (as opposed to fixing things up with mtext and then wrapping the whole equation). However, I could live with a user agent choosing to render merror as a standard mrow. In other words, merror would be there in the DOM, but there wouldn't be any visual indication of the error in the rendering.
Example:
<math>
<mfrac> <mn>1</mn> <mn>2</mn> <mn>3</mn> </mfrac>
</math>
would appear in the DOM as
<math>
<mfrac>
<mn>1</mn>
<merror> <mn>2</mn> <mn>3</mn> </merror>
</mfrac>
</math>
and render on screen as 1/23. (Obviously it would really render as a case fraction, and 1/23 is just my ASCII art approximation of it.)
I presume that would also allow one to add a <style> .merror {background: red} </style> or whatever you want to the document and have errors highlighted in red if you want to see them.
--Robert
Dr. Robert Miner
W3C Math WG co-chair
Vice President, Research and Development
Design Science, Inc.
140 Pine Avenue, 4th Floor
Long Beach, California 90802
USA
Main: (562) 432-2920
Direct: (651) 223-2883
Fax: (651) 292-0014
robertm@dessci.com
www.dessci.com
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.519 / Virus Database: 269.22.1/1352 - Release Date: 3/31/2008 10:13 AM