The XML Schema Complete Reference

The XML Schema Complete Reference

5.0 1
by Cliff Binstock, Mitchell Smith, David Cleary, Diane Kennedy
     
 

ISBN-10: 0672323745

ISBN-13: 9780672323744

Pub. Date: 10/04/2002

Publisher: Addison-Wesley

With the successful implementation of XML Schema, developers are learning how to increase productivity, improve software reliability, minimize development time, and decrease time to market. This in-depth reference is an all-in-one resource designed to help developers leverage the power and potential of XML schemas by offering a complete roadmap to their creation,…  See more details below

Overview

With the successful implementation of XML Schema, developers are learning how to increase productivity, improve software reliability, minimize development time, and decrease time to market. This in-depth reference is an all-in-one resource designed to help developers leverage the power and potential of XML schemas by offering a complete roadmap to their creation, design, and use. This authoritative reference and tutorial is filled with practical insights and detailed examples. The book begins by providing a conceptual introduction to XML Schema. From there, coverage shifts to the W3C Schema Recommendation and how to apply schemas to specific business goals. The authors provide insight and instruction throughout on integrating XML schemas into existing technologies such as .NET, Java, Visual Basic, Oracle, and more. The book concludes with a complete case study designed to reinforce and illustrate material covered. Whether designing a schema from scratch or integrating schemas into contemporary technologies. The XML Schema Complete Reference is the most complete and definitive sourcebook available for the XML Schema environment.

Read More

Product Details

ISBN-13:
9780672323744
Publisher:
Addison-Wesley
Publication date:
10/04/2002
Pages:
965
Product dimensions:
7.38(w) x 9.26(h) x 1.76(d)

Table of Contents

Preface
Acknowledgments
Pt. IXML Schema Overview1
1Introduction3
2XML Processing27
3XML Namespaces35
4XPath and XPointer45
5The Structure of Documents and Schemas57
Pt. IICreating XML Schema Documents73
6Overview of an XML Schema Document75
7Creating an XML Schema Document105
8Element Types137
9Attribute Types173
10Simple Types201
11Complex Types229
12Built-in Datatypes293
13Identity Constraints331
14Regular Expressions357
Pt. IIIValidation385
15XML Schema Component Detail387
16PSVI Detail413
17Java and the Apache XML Project427
18MSXML and the Schema Object Model (SOM)471
Pt. IVResult-oriented Schemas505
19Object-oriented Schemas507
20Document-oriented Schemas541
21Application-oriented Schemas555
Pt. VData-oriented Schemas585
22Data-oriented Schemas: Datatypes587
23Data-oriented Schemas: Simple Types673
24Data-oriented Schemas: Complex Types707
Pt. VIA Case Study: The Campus Resource and Scheduling System (CRSS)755
25The Business Case757
26The Architecture773
27The Server Tier809
28The Integrated Solution835
Pt. VIIAppendixes855
App. AXML Schema Quick Reference857
App. BXML Schema Regular Expression Grammar867
App. CThe Thematic Catalog XML Schema877
App. DData-oriented Schemas: Oracle8i Datatypes901
App. E: Glossary923
About the Authors939
Index941

Read More

Customer Reviews

Average Review:

Write a Review

and post it to your social network

     

Most Helpful Customer Reviews

See all customer reviews >

5 out of 5 based on 0 ratings. 1 reviews.
Guest More than 1 year ago
If you are already using XML, it is probably with DTDs, as this was the first implementation of XML. Both came out of SGML, in which the role of DTDs was defined in the early 1990s. Unfortunately, the drawbacks of DTDs were not fully appreciated until they began to be widely used in XML. A DTD cannot easily constrain an integer variable to a range of values from 5 to 10, say. It has no conception of common primitive types like float or double found in many programming languages. Also, the structure of a DTD is quite unlike that of the XML document it supports. From the point of view of writing parsers, you end up effectively needing two parsing algorithms to read a DTD and an XML document. XML Schemas answer all these issues. Plus namespaces are built into them, to handle collisions in tag names when you use multiple Schemas in a document. With DTDs, namespaces came into being after DTDs were first defined, and had to be bolted on in a most awkward fashion. XML Schema notation for namespaces is much more natural. The problem right now with XML Schema is that it is new. Most XML books use DTDs, in part because when they were written, the Schema specification was not finished by W3C (in May 2001). Some XML books since then do describe Schema. They usually give a good overview and provide examples that work for the XML document examples they describe. So if you have an application that you want to write a Schema for, you can get started. But chances are, you soon run into problems if your application is not a carbon copy of a text's example. You soon need some Schema component or attribute whose usage or even existence was not disclosed in that book. This book addresses that shortfall. It provides at least one example of how to use every attribute of EVERY Schema element. A formidably comprehensive task. Which accounts for the near thousand page size. But this is far more than just some dictionary-style exposition. They describe important closely related issues, like how to use the DOM and Xerces SAX parsers, and the different outlooks these take. Also, from your viewpoint of how to write a Schema for YOUR application, they offer a top-down approach. Schemas can be result-oriented or data-oriented. You get enough details to help decide which case yours fits. This can greatly aid developing a facile "natural" Schema. One where once you have it and an example XML document that uses it, the layout taxonomy seems axiomatic. Which should be your goal. It is not enough to define a Schema that can hold all the information you have. The skill is in making a Schema that does that and has a clear, obvious logic. Because in many cases others, probably not as technically adept as you, get to fill in documents based on it. So the logic should be clear to them. Even if they do not directly write into an XML document, but build it from a GUI, the clearer the Schema, the easier it is for someone to build a GUI to populate a document based on it. The authors also provide a website (XMLSchemaReference.com) that has the code described in the book, and many more examples. Worth bookmarking. So try this book and its website if you need an authoritative guide to writing Schemas.