[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: building an object model of a XML schema
- From: Amit Bhatiani <firstname.lastname@example.org>
- To: Ronald Bourret <email@example.com>,"Bullard, Claude L (Len)" <firstname.lastname@example.org>
- Date: Tue, 10 Jul 2001 18:49:27 -0400
> "Bullard, Claude L (Len)" wrote:
> > An excellent paper, BTW.
> > In it, you suggest that it is better NOT to
> > generate classes from XML Schemas. It is better use
> > a data modeling language such as UML and generate the
> > schema from that. Do you still support that position?
> Yes, although it's based on theoretical work, not real-world experience.
> XML Schemas are designed to model XML documents, not objects.
> Consequently, you get some weirdnesses when trying to map the schema
> data model to an object model. If your application really thinks in
> terms of objects, better to start with an object/generic modelling
> language and go the other direction. That way, the XML schema is just a
> serialization syntax, not a model.
I can give you some real-world reasons why you should start with objects and
1. As business requirements change, they require both data and behavior
changes. This obviously means that you design, code and test your changes in
the object model. This means you want the object model to be your ongoing
starting point, not the schema.
2. Expressing type constraints in the xml schema is cumbersome at best.
Strong type checking is important in most application scenarios.