Modeling Business Objects with XML Schema

Product Description
XML Schema is the new language standard from the W3C and the new foundation for defining data in Web-based systems. There is a wealth of information available about Schemas but very little understanding of how to use this highly formal specification for creating documents. Grasping the power of Schemas means going back to the basics of documents themselves, and the semantic rules, or grammars, that define them. Written for schema designers, system architects, programmers, and document authors, Modeling Business Objects with XML Schema guides you through understanding Schemas from the basic concepts, type systems, type derivation, inheritance, namespace handling, through advanced concepts in schema design.

*Reviews basic XML syntax and the Schema recommendation in detail.
*Builds a knowledge base model step by step (about jazz music) that is used throughout the book.
*Discusses Schema design in larg. . . More >>

Modeling Business Objects with XML Schema

5 thoughts on “Modeling Business Objects with XML Schema”

  1. This is the best book out there on XML. If you want an intro to XML get Mark Johnson’s article “XML for the Absolute Beginner. ” If you want to go in depth, this is the place to go.

    Unlike the hundreds of other books that just describe what XML and XML Schema are, Daum’s book gets deeply into why it is the way it is, by exploring how it fits in with conceptual modeling and how you would fit it into a complex environment.

    He introduces a beguiling simple example domain (jazz musicians) which he revisits over and over again throughout the book. Through this simple example he works out subtle differences in different approaches to modeling, to schema construction, to constaint definition and modeling and finally how would you map this back to Object or Relational technology.

    He introduces Asset Oriented Modeling, which is a form of conceptual modeling more attuned to XML schema model creation. His treatement of polymorphism in Schema, and techniques for evolving schema are as good as I’ve seen anywhere.

    Excellent treatment of constraints, both conceptually as well as practical approaches to realizing the constraints in XPath or XSLT. These were worth the price of the book by themselves.

    It’s probably too late, but if you get no other book on XML and XML Schemas, this is the one to get.
    Rating: 5 / 5

  2. I just finished reading “Modeling business Objects with XML Schema” for the second time. It is the most useful book on XML modeling that I have read. After defining the ERM and UML modeling techniques, the author introduces AOM (Asset-Oriented Modeling) in a simple and thorough way. The book emphasizes on the best practices for modeling heterogeneous and multi-namespace systems. It emphasizes on the compatibility of the XML Schema with RDF and SQL. The reuse and composition of XML Schemata constitute the main focus of the book. The example given in the book is processed through several iterations and improvements, with complete and clear explanations for improving the XML code. The KLEEN Modeler tool (http://www. aomodeling. org/tools. htm) is used to create the conceptual models throughout the book. Mapping the XML Schema code into SQL, and normalization of the XSD code is clearly defined. The XML metalanguage itself, is concisely and efficiently covered in the book. I highly recommend this book; you learn a lot from this book.
    Rating: 5 / 5

  3. This is a useful book for analysts and programmers who are coming from an Entity Relationship Modeling background – and who need to understand the theory and mechanics of developing XML Schemas for applications.
    Rating: 3 / 5

  4. The book is poorly organized. If one does not know the context of the topic ahead, it would be very hard to follow. The book did not even mention where to download, how to use its companion modeling tool. The reader has to figure that out.

    There are a lot of theoretical sections that I don’t see necessity to be empasized or even presented.

    The author conveyed the idea of AOM (Asset Oriented Modeling), but I am still clueless about the value of this AOM modeling. I am not convinced to adopt this modeling methodology to solve a real world problem. To me, it is just another proprietary practice of modeling, with no or very little pratical value. The material is very difficult to be tied to technical implementation, thus it is only good on paper.

    I don’t understand why there are so many good comments about this book. But after going through the book briefly, I realized it is a waste of time and money.

    Rating: 2 / 5

Leave a Comment