- From: Neil Soiffer <NeilS@dessci.com>
- Date: Thu, 31 Jul 2003 13:40:19 -0700
- To: "Robert Miner" <RobertM@dessci.com>
- Cc: <RobertM@dessci.com>, <jpederse@wiley.com>, <www-math@w3.org>
> > <menclose> or a new construct such as <moverstrike> would be the way to do > > it if we were talking about an addition to MathML, but that is not an option > > at the present. Hence, I don't think your suggestion is a good one since > > it means writing invalid MathML. Perhaps a private namespace a new > > attribute to menclose that would be understood by MathPlayer would be > > better. > > No. The value list for menclose is explicitly open-ended (CDATA) to > facilitate just exactly this kind of extension. I made sure that was > the case in 2.0 2nd Edition, since I've long thought this was the way > to handle strikeouts. It bugs me no end that I didn't think of > strikeouts until after 2.0 had been published, or they would have been > in there in the first place. In fact, it looks like all of the attribute values (at least of the ones I looked at) are declared as CDATA for the DTD. The schema appears to limit the legal values. The text in chapter 3 also appears to limit the legal values: "In addition to the attributes listed below, this element permits id, xref, class and style attributes, as described in ..." Before the 2nd edition is finalized (I think it is in proposed edition status), perhaps a sentence can be added as an editorial clarification that the list of values is not restricted to those values listed. Neil Soiffer email: neils@dessci.com Senior Scientist phone: 562-433-0685 Design Science, Inc. http://www.dessci.com "How Science Communicates" MathType, WebEQ, MathPlayer, Equation Editor, TeXaide
Received on Thursday, 31 July 2003 16:40:34 UTC