Use an XML editor tool to build and verify a XML schema document. To download a free XML editor tool (<[url removed, login to view]>).
A1. Suppose we have a tree representation of an XML document for e-mail, which can be read with popular web browser. Suppose output style looks like figure F1. Provide an example e-mail in XML document based on your own e-mail information. The XML document may not be formally constrained with any DTD (document type definition) or XML Schema.
A2. Provide a DTD for the e-mail XML document created in question A1
A3. Provide an XML Schema for the e-mail XML document created in question A1 by means of XML editor
A4. Design an XSLT Stylesheet for above e-mail XML document. Output style is shown in figure F1
A5. Provide an XML Schema for the e-mail XML document created in question A1 by means of XML editor
A6. Design an XSLT Stylesheet for above e-mail XML document. Output style is shown in figure F1
In this part, you will use JDOM 1.0 (<[url removed, login to view]>) to process XML and use BlueJ tool (<[url removed, login to view]>) (2.0.2 version) to organize Java code. You need to use java platform JDK1.5.0 (<[url removed, login to view]>) or greater version.
B1. Design an e-mail editor program in Java. E-mail should be kept in XML document as question A3 does. Besides basic items described in figure F1, you may add more interface menu and items to make editor easily be used. You need to provide a document for presenting XML schema tree for the e-mail XML document.
B2. Implement an e-mail address book in Java. Suppose all records of the address book are kept in XML document. Each record should contain the following items:
(B2a). Contact information: first name, last name, display name, e-mail address, and phone number.
(B2b). Address information: title, department, organization, address, city, state/province, postal code, and country
You need to provide a document for presenting XML schema tree for the address-book XML document.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).