XML modules' public classes are often used as an
API. It's OK as many classes are really considered
to become an API. However until that time all
clients must use implementation dependencies to
get access to these. It's complicated to manage as
by default the implementation version is derived
from build time.

Now right before release I do not plan to change
any public class in XML modules. And I want to
simplify life of dependant modules by exporting
current public classes as ranged API:
 - no backward comparability guaranteed
 - still the same public classes for several releases
   (NB3.5, Nevada, NB3.5.# and Nevada JP#)
 - the ranged API visibility is closely tied with
   module enableness rules
 - no upgrade guide, dependent modules are
   considered friends

I plan to use constant implementation version:

  XML-2003-03

to achieve it.