Study the XML Schema design issue "Global versus Local" on the site XML Schemas: Best practices (The MITRE Corporation and the xml-dev list group) . Describe briefly what is meant with "Russian Doll Design", "Salami Slice Design", and "Venetian Blind Design". List some recommendations (or good and bad sides) of using these design styles.
Assume you have XML documents containing information about books and their prices, as follows:
<?xml version="1.0"?>
<books>
<book category="reference">
<author>Nigel Rees</author>
<title>Sayings of the Century</title>
<price>8.95</price>
</book>
<book category="fiction">
<author>Evelyn Waugh</author>
<title>Sword of Honour</title>
<price>12.99</price>
</book>
<book category="fiction">
<author>Herman Melville</author>
<title>Moby Dick</title>
<price>8.99</price>
</book>
</books>
Give SAX content handlers that output the average price of the fiction books in the document (category="fiction").
Project, Part 3:
Assume Company B wants to buy some products from Company A and sends a purchase order to Company A.
Create an XML document that is sent from Company B to Company A. You can choose freely which information is relevant for the order.
Assume Company A uses SAX as a programming interface to process the orders. Give SAX content handlers which output an XML document that can be sent to Company B as an invoice. The invoice should contain the total price of the products, but otherwise you can choose freely the content of the document.
P.S. You can find some general information about the application area on the web page: Web Services Architecture Usage Scenarios, Section 3.2 EDI-like purchasing.