OMG and legacy rules

Paul Vincent so nicely sent us to an OMG website (http://admin/omg.org/) where members understand the benefits of mining rules.  In that regard, what more should we know about such work, how to use it now, and what may be coming in the (near?) future?

So, Paul and other OMG members, we are noticing more and more companies being interested in mining the rules from the code, not just recasting the IT semantics into new code.  Reasons vary from simply wanting to trace the rules (in business language) to where they are in the code for maintenance purposes and to re-deploying in a BRMS, like Blaze Advisor.  So, the benefits of mining them are becoming more obvious.

That said, I am glad that you commented on the work of the OMG in this regard.  Can you (or someone else) point to a specific white paper or presentation for the blog readers to refer to? 

If there isn’t a favorite, how will the current OMG work in this regard help us?  Is it expected to lead to

(1) better ways to determine where in the code the rules are buried (to limit searches) or

(2) extension to more programming languages (although many tools cover a wide variety today or

(3) more automated assistance in recasting an actual code slice into more abstract rule sentences (perhaps applying the SBVR OMG standard to new software for doing so? 

(4) provide repositories through which we can access the code, create "slices" of it, mine rules, correlate these rules to BlazeAdvisor (for example), all in one wonderful repository solution?

These are the areas that are a bit limiting today, in our experience.