Hi Neil, 
> 
> Since the new design is moving along well--it can compile and might even be
> able to validate some kinds of simple schemas even in its current
> condition--I'd like to propose that the v1 package be done away with.  If
> no one is using it or planning to work with it there's no point in having
> it around; and at any rate having it on the main line encourages v2 code to
> rely on v1 classes, something that must be avoided.  So if no one cares
> I'll remove it; if only one person does I'll put it on a branch (unless
> they veto me :-)) and if more people care then speak up and let us know
> what's up!  :-)

In my early presence on alias, I was having some interest to go for porting but 
later decided to opt for V2 *only*.

> Assuming the v1 package goes away and that the new design keeps moving
> forward at a good pace, we'll need to think about packaging it.  Any and
> all ideas solicited here; but here's a first cut at a proposal:
> 

> - port/move the v1.util.regex package to util.regex

I agree with Andy's suggestion on this.

> - move the code in v2.xpath to util.xpath
> - move the v2.XSD*Traverser, v2.SubstitutionGroupHandler, XSDocumentInfo
> and XSDHandler classes to impl.schema.traversers
> - move v2.CMBuilder, XSSimpleCM, XSCMValidator  to impl.schema.models
> - move v2.identity.* and v2.datatypes.* to schema.identity and
> schema.datatypes respectively

All the changes are looking fine & will be making things much clear.

> - rename impl.validation to impl.dtd to reflect the fact that only
> DTD-related stuff lives there

Clear definition again, nice

> - leave the rest of the contents of v2 in the schema package
> (SchemaGrammar, SchemaSymbols, the XS*Decl classes perhaps, the error
> infrastructure etc.)

Sure ..

> - find a sensible home for v2.SAXParser, v2.SchemaParser,
> v2.SchemaParserConfiguration

I feel, we can put them in xerces.parser or xerces.parser.schema (Just for time 
being ).



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to