Module contains several actions such as Generate
DTD that could be used from several entry points.
This particular case could be accessed from the
<New> action and as XML context action.

The same idea could apply to other actions:
  - SAX Wizard
  - DOM Scanner Generator
  - DTD2Schema converter
  - XSLT with scenario
  - XML2Schema converter
  - etc.

The question is: Do we have to move selected
context actions into <New> action? It typically
means that we provide a wizard that will gather a
context from a user. It makes perfect sense to me
because it follows better user task flow. 

Particular task: A user want to create new DTD.
Unfortunatelly he does not know all context module
features so he probably miss that module can
generate it for him from XML instance. He goes
into <new> and get empty DTD.

I can imagine that you could disagree claiming
that it pollutes the <New> action. Your complain
can be invalidated by wizard approach (such
approach used for new XML document spared several
standalone templates).

Second thing that need to be investigated is that
some actions should have several entry points
under <New>. Take SAX wizard action as an example.
It could be present under:
  <New>/Java/XML/SAX Document Handler
  <New>/XML/Java/SAX Document Handler
Generally Java/XML could be linked to XML/Java.