While it's true that the OCL Tools component in MDT has not yet been
provisioned, I guess we may anyway keep discussing future steps for that
component. In line with that, I've posted the draft of a Technical Article,
"OCL Tools: Status and Perspectives"

With the availability of infrastructural support for OCL (Object Constraint
Language) provided by MDT OCL, the next step consists in simplifying the
authoring of OCL specifications with feature-rich tools, as part of the more
general task of model authoring. The capabilities of the OCL Tools project
are
described (currently they comprise an OCL -> Java compiler and a text editor
for OCL). A discussion of areas for improvement and related work follows
(refactoring of OCL expressions, detecting code smells, analyzing and
optimizing OCL expressions). These ideas for future work fall under the
umbrella of model compilers, essential elements of Model-Driven Software
Engineering.

Actually most of the off-list emails I've received about OCL Tools focus on
merging efforts for the OCL Text Editor. The article describes the status of
a prototype my team has developed, thus offering a base for comparison. It's
not yet an initial contribution, only the OCL -> Java compiler component is.

It's a brave new world all this model-driven tooling stuff. And I'm talking
just about the OCL-related tools. I hope we can manage as a community :)

For those OCLers attending the Eclipse Summit Europe in two weeks, perhaps
we could gather in a BOF. What do you think?