W3C home > Mailing lists > Public > www-math@w3.org > August 2003

RE: menclose

From: <jpederse@wiley.com>
Date: Fri, 8 Aug 2003 11:03:58 -0400
To: "Pepping, Simon (ELS)" <S.Pepping@elsevier.nl>
Cc: Neil Soiffer <NeilS@dessci.com>, Robert Miner <RobertM@dessci.com>, www-math@w3.org
Message-ID: <OFE3C9EB0F.ABA783B5-ON85256D7C.004F7331@wiley.com>


I'm waiting on this naming issue to be resolved so that we can finish
marking up a product. So the sooner it can be decided, the better.  I agree
with Simon's comment about the repeated "s", and it would seem to make
sense to stay consistent with the existing values "longdiv", etc., so we
shouldn't start doing camel case upwardsStrike. Some shorter non-compass
names would be

upstrike   or  upcancel
downstrike  or downcancel
hstrike    or hcancel
ulcorner
urcorner
llcorner
lrcorner

But at this point I'd be very happy for someone just to lay down the law so
we can proceed.

John.

-----------------------------
John Pedersen
Content Systems,
John Wiley & Sons, Inc.




                                                                                                         
                      "Pepping, Simon                                                                    
                      (ELS)"                   To:       "'jpederse@wiley.com'" <jpederse@wiley.com>,    
                      <S.Pepping@elsevi         Neil Soiffer <NeilS@dessci.com>                          
                      er.nl>                   cc:       Robert Miner <RobertM@dessci.com>,              
                                                www-math@w3.org                                          
                      08/08/03 06:27 AM        Subject:  RE: menclose                                    
                                                                                                         
                                                                                                         




> > NESWstrike
> > NWSEstrike
> > WEstrike
> > NEcorner
> > SEcorner
> > SWcorner
> > NWcorner
> >
> upwardsstrike
> downwardsstrike
> horizontalstrike
> verticalstrike
> upperleft
> upperright
> lowerleft
> lowerright

I find the latter set of names more intuitive than the compass directions.
I
like them esp. for the corners and the horizontal and vertical. I am less
sure about upward and downward, but I do believe that they are unambiguous.

verticalstrike does not work with menclose. It was not in Robert's list.

I do prefer the longer variants, with strikeout and corner; they describe
the intention.

I do not like the double s in upwardsstrike; I will forget to write it most
of the time.

Regarding the earlier discussion about the DTD. I consider the DTD as an
approximation of the standard. When the text lists three allowed values for
the attribute, then that is the MathML spec. So the current discusson is
about an extension of the spec.

Regards,
Simon Pepping
DTD Development and Maintenance
Elsevier
s.pepping@elsevier.com
www.elsevier.com/locate/sgml


> -----Original Message-----
> From: jpederse@wiley.com [mailto:jpederse@wiley.com]
> Sent: 07 August 2003 14:33
> To: Neil Soiffer
> Cc: Robert Miner; www-math@w3.org
> Subject: Re: menclose
>
>
>
>
> There is also precedent in the entity names for using directions, for
> example nwarr and nearr in isoamsa.ent (nwarrow, nearrow in
> mmlalias.ent).
> Personally I think upwards/downwards for the diagonal strokes could be
> slightly ambiguous (I know some Windows people who insist on
> calling \ a
> forwards slash); using compass directions leaves no doubt.
>
> John.
>
> -----------------------------
> John Pedersen
> Content Systems,
> John Wiley & Sons, Inc.
Received on Friday, 8 August 2003 21:00:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 20 February 2010 06:12:55 GMT