[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: building an object model of a XML schema
> From: Jeff Lowery [mailto:jlowery@s...] <snip/> > Right now, that information is missing from XML Schema, and > various code > generation implementations have their own unique ways of adding the > information. As it should be? I hope not. Actually, I would not want to see that in XML Schema. If XML Schema were intended as a data modelling language, rather than as a "foundation" spec for other XML specs, I wouldn't have a problem with this. But in my mind, XML Schema has already veered too far in this direction, and this has nothing to do with XML; it has more to do with how particular applications *use" XML, and there are plenty of applications that deal with XML that have no use for this stuff. I see great utility in XML Schema, but there is also in my mind a sharp distinction between modelling the XML syntax for a document type, and modelling the information my application will synthesize and use from that XML document. Some might find it useful to combine the two, but the whole XML world should not have to follow their lead. I much prefer to keep the two separate. Note, that it is also possible to annotate an XML Schema with attributes and elements from other namespaces. You can add application specific info to the model to suit your needs in a way that is compatible with other schema processors (they can ignore your application specific info). You can also do this with RELAX NG. This is a sound approach, IMHO, to let users extend the model in useful ways without the core XML Schema grammar having to accomodate everyone's use case.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|