I'm sure that there will be similar classes. No matter how it works, there
have to be classes that represent the concepts that the schema works in
terms of. I guess the big difference might be that, if we end up with an
'uber validator' that is really a Schema validator and which just treats a
DTD as a simplistic Schema, then some of the data in them will just be
defaulted in because the DTD has no way to say those things.
But, other than that, its really too early to say much. Of course you could
look at the partial Schema support in the Java version, but I wouldn't be
so sure that that is really close to how the end product will look, though
I've seen a lot of checkins lately on that stuff, and I assume that its due
to moving the Schema stuff closer to what has been recently discussed
internally.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
[EMAIL PROTECTED] on 04/06/2000 06:12:48 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: Dean Roddey/Cupertino/[EMAIL PROTECTED]
Subject: RE: xerces linking side effect ...
When schemas become a standard, Would there be classes supporting schema
parsing. Like we have the
DTDElement DTDAttribute etc, would schema support involve this. Or would it
be considered as parsing a XML file. It would be beneficial to know what
approach would be taken??
Kiran
