Doing More With XML Schemas (part 4) - Closing Time
(Page 7 of 7 )
And that's about it for the moment. Over the four parts of this article, I've given you a crash course in some of the more advanced aspects of XML schema design, explaining how you can use built-in schema constructs to design more efficient and extensible schemas.
I've shown you how to derive new types from existing types, either by extending or restricting them, and how to break up your schema definitions into separate files for greater maintainability. I've also shown you how to enforce basic referential integrity in a schema with primary and foreign key references, and how to enforce the use of namespaces in document instances to avoid name clashes between different document instances.
If you'd like more information on any of these topics, here are a few links you should look at:
The W3C's XML Schema section, at
http://www.w3.org/XML/Schema The XML Schema Primer, at
http://www.w3.org/TR/xmlschema-0/ XML Schema Structures, at
http://www.w3.org/TR/xmlschema-1/ XML Schema Datatypes, at
http://www.w3.org/TR/xmlschema-2/ Till next time - happy XML-ing!
Note: All examples in this article have been tested on Linux/i586. Examples are illustrative only, and are not meant for a production environment. Melonfire provides no warranties or support for the source code described in this article. YMMV!
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 7 
