The big long todo list

* An event model
  The OMF really needs one of these - especially for real application
  development. Expect one to show up (although not be fully integrated)
  around 1.1 - it's the next job up.

o A facility for persistent extensions
  The lighweight extension mechanism needs to be expanded to provide
  lightweight persistent extensions. While this isn't overly difficult
  I need to make sure that it integrates well with the XMI reader and
  writer.

o Improve the autotool support
  Right now, the autotool build is pretty flaky. It doesn't actually
  check for certain requirements like Boost or Python. I should also
  build up some m4 scripts so people can check for OMF versions. That
  would be nice.

o Figure out the actual distribution
  There are some files that I need to distribute as pure data and install
  in well known places (like metamodel files). These should go into some
  place like /usr/share/omf2 or something like that.

o Refactor the build
  This would correspond to the omf2-2.x series. At some point I'm going
  to completely break the build into a number of different projects.
  For example, you could install just the OMF core or the core and UML.
  Anyways, the metamodel implementations may no longer be included, but
  consist of additional downloads Also, the names of the libraries and
  the include paths may be rewritten to scope everything to the OMF
  rather than to metamodel specific directies (OMF/Model/... or
  OMF/MOF2/...)

o Provide MOF2/UML2 implementations
  The REAL goal of the OMF... Just kidding. Actually, I should start
  working on this just after finishing the build refactoring.

o An OCL parser and evaluation engine (thesis project)
  This is a very, very large project. I would love to get this working,
  but it's probably too complex given my limited scope. However if
  somebody wanted to come pick this up and build a true OCL evaluation
  engine for the OMF, they could probably get a master's thesis out
  of it.

o Finish regression tests
  Make sure everything works right.

o Programmer's guides
  Actually, in progress, but unpublished.

o Other bindings? I'd love .NET bindings
  Could be used to increase usability of the OMF?

o Binary distributions (would be nice)
  Of course...

o Actually put this in cvs/subversion...
  Naturally... Actually, the project will at some point (i suspect)
  move to SourceForge.
