[Trac] [OpenMath] #36: alg1.ocd in OM3/MathML3 group examples.

OpenMath trac at strawberry.eecs.jacobs-university.de
Wed Jan 30 05:35:08 CET 2008


#36: alg1.ocd in OM3/MathML3 group examples.
----------------------------+-----------------------------------------------
     Reporter:  kohlhase    |          Owner:  jhd             
         Type:  proposal    |         Status:  new             
     Priority:  blocker     |      Milestone:  MathML3CD Draft1
    Component:  MathML CDs  |        Version:                  
   Resolution:              |       Keywords:                  
Include_gantt:  0           |   Dependencies:                  
   Due_assign:  YYYY/MM/DD  |      Due_close:  YYYY/MM/DD      
----------------------------+-----------------------------------------------
Comment (by kohlhase):

 Replying to [comment:5 david]:
 > Replying to [comment:3 kohlhase]:
 >
 > > Do you really think that the MathWG would value that?
 > I don't see why not.
 OK, if you are for it, then I can see the biggest potential hurdle gone,
 so I would suggest we go for it.
 >
 > >And what do you consider the "core" set?
 > http://people.bath.ac.uk/masjhd/ReduceOpenMath/html/node11.html
 > (google  supplied link:-)
 Yes, I know the general principle, but I would like to have a concrete
 list, so that we can get an overview.
 > at one time we had an explicit core CD group of which the mathml CD
 group was a subset, we seem to have let it drop out of usage, partly I
 think because the CD browser navigation that developed worked better if
 each CD was only in one cdgroup.
 > but it doesn't matter, take it as meaning all the "official" ones. We
 have to (I think) support these anyway going forward from OM2 to OM3, so
 supporting the same set on the MML3 side makes sense to me.

 I agree with you in principle, the closest I can get to "official CDs" is
 URL: https://svn.openmath.org/cd/Official
 that would mean that we have to add alg1.ocd, altenc.ocd, and
 bigfloat1.ocd. alg1 and bigfloat make sense to me, but altenc is a meta-
 thing that should not go into the OM3/MathML3 set I think.

 What about transc2.ocd and fns2.ocd from the experimental set? They are
 also used as examples. The first is used in exactly one example (two-
 argument arctan) in complex1.ocd. We should probably just replace or drop
 the example, because transc2 is not K-14 in my view.

  From fns2.ocd, we use apply_to_list, which we could add to fns1.ocd or we
 could just take in all of fns2 to the OM3/MathML3 group (even though I
 must say that I have my doubts whether 'kernel' should be in fns?.ocd at
 all). Depending on how much leeway we give ourselves with CD restructuring
 (see #25), we have some freedom here (especially, since fns2.ocd is
 experimental).

-- 
Ticket URL: <https://trac.mathweb.org/OM3/ticket/36#comment:6>
OpenMath <http://www.openmath.org>
The development of the OpenMath Standard and Content Dictionaries.


More information about the Trac mailing list