XML.HTMLTeacher.Com
[Search] [Contact] [Sitemap]
XML
[Main]
[XML]
[XML Document Preparation]
[Classes]
[XHTML]
[XML]
[CSS]
[Design]
[Programming]
[Marketing]

Tag Names
* Decide what tags you will need to use to accurately describe the contents of the document and/or to match application needs. Ask the following questions:
  • Will tag names need to match database filed names?
  • Will case be an issue?
  • What is the most logical structure of the document?
  • Will this structure be best for our needs?
  • Can we grow with these tags and this structure?
  • Ask "What if?"
  • Be consistent in naming conventions.
  • Be case consistent.
Document Analysis
* Document analysis allows the developer to markup a document to meet the needs of the business. In analysis design, the developer will name the elements, entities and attributes that will form a relationship with each other. A document's structure is the resulting mix of these elements, entities and attributes.

* This structure then becomes a roadmap to the document's content as described by the elements. Processing instructions follow these roadmaps to define the final output of the the document. Please see XSLT for more information.


Document Structure
* An example of structure could be in something as simple as an addressing an envelope. First the full name of the recipient is stated, then the full street address, then the city, state, and zip code.

The resulting markup might look like this:

<address_label>

<full_name>   </full_name>
<street_address>   </street_address>
<city>   </city>
<state>   </state>
<zip_code>   </zip_code>

</address_label>


* Another example is a customer invoice. The name of the company, the company's address and invoice number and date along with the services rendered and amount charged are normally all part of an invoice.

The resulting markup might look like this:
(The parent opening and closing elements are stated in red.)

<customer_invoice>

<company>

<company_name>   </company_name>

<company_address>

<street_address>   </street_address>
<city>   </city>
<state>   </state>
<zip_code>   </zip_code>

</company_address>

<invoice>

<invoice_number>   <invoice_number>
<invoice_date>   <invoice_date>

<services>

<service1>   </service1>
<service1_fee>   </service1_fee>

<service2>   </service2>
<service2_fee>   </service2_fee>

<service3>   </service3>
<service3_fee>   </service3_fee>

</services>

</invoice>

</company>

</customer_invoice>


Does XML need any supporting document(s)?
* XML may use a DTD (Document Type Definition) or a schema to formally describe the data. These are optional, but their use increases the overall strengths of XML by providing a standard in the creation of the XML document.


All materials, tutorials and content are copyrighted by HTMLTeacher.Com.
Any use of any material, tutorials and/or content provided by this site is prohibited without expressed written consent of the author.

Copyright ©2003 HTMLTeacher.Com and Sonia Weimann