Introduction to XML XML was designed to transport and store data. HTML was designed to display data.

What You Should Already Know Before you continue you should have a basic understanding of the following:   HTML JavaScript

If you want to study these subjects first, find the tutorials on our Home page. What is XML?       XML stands for EXtensible Markup Language XML is a markup language much like HTML XML was designed to carry data, not to display data XML tags are not predefined. You must define your own tags XML is designed to be self-descriptive XML is a W3C Recommendation

The Difference Between XML and HTML XML is not a replacement for HTML. XML and HTML were designed with different goals:   XML was designed to transport and store data, with focus on what data is HTML was designed to display data, with focus on how data looks

HTML is about displaying information, while XML is about carrying information. XML Does Not DO Anything Maybe it is a little hard to understand, but XML does not DO anything. XML was created to structure, store, and transport information. The following example is a note to Tove, from Jani, stored as XML: <note> <to>Tove</to> <from>Jani</from> <heading>Reminder</heading> <body>Don't forget me this weekend!</body> </note> The note above is quite self descriptive. It has sender and receiver information, it also has a heading and a message body.

please read our W3C Tutorial. XML is used to transport data. and be sure that changes in the underlying data will not require any changes to the HTML. In most web applications. The tags used in HTML are predefined.But still. etc. data can be stored in separate XML files. With XML. Someone must write a piece of software to send. To read more about the XML activities at W3C. XML is Everywhere XML is now as important for the Web as HTML was to the foundation of the Web. XML is the most common tool for data transmissions between all sorts of applications. It is important to understand that XML is not a replacement for HTML. XML allows the author to define his/her own tags and his/her own document structure. With a few lines of JavaScript code.). XML is a W3C Recommendation XML became a W3C Recommendation on February 10. receive or display it. <h1>. These tags are "invented" by the author of the XML document. while HTML is used to format and display the data. this XML document does not DO anything. With XML You Invent Your Own Tags The tags in the example above (like <to> and <from>) are not defined in any XML standard. That is because the XML language has no predefined tags. HTML documents can only use tags defined in the HTML standard (like <p>. XML is Not a Replacement for HTML XML is a complement to HTML. My best description of XML is this: XML is a software. 1998. you can read an external XML file and update the data content of your web page. often to simplify data storage and sharing. XML Separates Data from HTML If you need to display dynamic data in your HTML document. This way you can concentrate on using HTML/CSS for display and layout. How Can XML be Used? XML is used in many aspects of web development. . it will take a lot of work to edit the HTML each time the data changes. It is just information wrapped in tags.and hardware-independent tool for carrying information.

Exchanging data as XML greatly reduces this complexity. but also from XML data sources. not only in HTML pages. Here are some examples:       XHTML WSDL for describing available web services WAP and WML as markup languages for handheld devices RSS languages for news feeds RDF and OWL for describing resources and ontology SMIL for describing multimedia for the web If Developers Have Sense If they DO have sense. This provides a software. without any conversion utilities in between. XML is Used to Create New Internet Languages A lot of new Internet languages are created with XML. XML data is stored in plain text format. XML Makes Your Data More Available Different applications can access your data.XML Simplifies Data Sharing In the real world. since the data can be read by different incompatible applications. spreadsheet applications and databases that can read each other's data in XML format. With XML. without losing data. XML Simplifies Data Transport One of the most time-consuming challenges for developers is to exchange data between incompatible systems over the Internet. . XML Simplifies Platform Changes Upgrading to new systems (hardware or software platforms). future applications will exchange their data in XML. This makes it much easier to create data that can be shared by different applications. and make it more available for blind people. This makes it easier to expand or upgrade to new operating systems. or people with other disabilities. The future might give us word processors. voice machines. XML data is stored in text format. computer systems and databases contain data in incompatible formats. etc). news feeds. is always time consuming. your data can be available to all kinds of "reading machines" (Handheld computers. Large amounts of data must be converted and incompatible data is often lost. or new browsers. new applications.and hardware-independent way of storing data.

. that the XML document contains a note to Tove from Jani. Don't you agree that XML is pretty self-descriptive? XML Documents Form a Tree Structure XML documents must contain a root element.. All elements can have sub elements (child elements): <root> <child> <subchild>. The next line describes the root element of the document (like saying: "this document is a note"): <note> The next 4 lines describe 4 child elements of the root (to.. from.0) and the encoding used (ISO-8859-1 = Latin-1/West European character set). The tree starts at the root and branches to the lowest level of the tree.XML Tree XML documents form a tree structure that starts at "the root" and branches to "the leaves". from this example.</subchild> </child> </root> . An Example XML Document XML documents use a self-describing and simple syntax: <?xml version="1. It defines the XML version (1. and body): <to>Tove</to> <from>Jani</from> <heading>Reminder</heading> <body>Don't forget me this weekend!</body> And finally the last line defines the end of the root element: </note> You can assume. This element is "the parent" of all other elements.0" encoding="ISO-8859-1"?> <note> <to>Tove</to> <from>Jani</from> <heading>Reminder</heading> <body>Don't forget me this weekend!</body> </note> The first line is the XML declaration.. heading. The elements in an XML document form a document tree.

Parent elements have children. Ray</author> <year>2003</year> <price>39.00</price> </book> <book category="CHILDREN"> <title lang="en">Harry Potter</title> <author>J K. All <book> elements in the document are contained within <bookstore>. <price>. Rowling</author> <year>2005</year> <price>29. and sibling are used to describe the relationships between elements. Example: The image above represents one book in the XML below: <bookstore> <book category="COOKING"> <title lang="en">Everyday Italian</title> <author>Giada De Laurentiis</author> <year>2005</year> <price>30.95</price> </book> </bookstore> The root element in the example is <bookstore>. The <book> element has 4 children: <title>. child. <year>. . All elements can have text content and attributes (just like in HTML). Children on the same level are called siblings (brothers or sisters).< author>.99</price> </book> <book category="WEB"> <title lang="en">Learning XML</title> <author>Erik T.The terms parent.

. Use whatever you prefer. it must be closed inside the <b> element. and easy to use. All elements must have a closing tag: <p>This is a paragraph.XML Syntax Rules The syntax rules of XML are very simple and logical.. all elements must be properly nested within each other: <b><i>This text is bold and italic</i></b> In the example above. <br> In XML. <root> <child> <subchild>. Opening and closing tags must be written with the same case: <Message>This is incorrect</message> <message>This is correct</message> Note: "Opening and closing tags" are often referred to as "Start and end tags". The rules are easy to learn. it is illegal to omit the closing tag. you might see improperly nested elements: <b><i>This text is bold and italic</b></i> In XML.. The declaration is not a part of the XML document itself. All XML Elements Must Have a Closing Tag In HTML. The tag <Letter> is different from the tag <letter>.. This element is called the root element. XML Elements Must be Properly Nested In HTML.</p> <br /> Note: You might have noticed from the previous example that the XML declaration did not have a closing tag. XML Documents Must Have a Root Element XML documents must contain one element that is the parent of all other elements.</subchild> </child> </root> . and it has no closing tag. XML Tags are Case Sensitive XML tags are case sensitive. "Properly nested" simply means that since the <i> element is opened inside the <b> element. This is not an error. some elements do not have to have a closing tag: <p>This is a paragraph. It is exactly the same thing.

&quot. &apos. it will generate an error because the parser interprets it as the start of a new element. This will generate an XML error: <message>if salary < 1000 then</message> To avoid this error. If you place a character like "<" inside an XML element. &amp. &gt. The greater than character is legal. Entity References Some characters have a special meaning in XML. the second is correct: <note date=12/11/2007> <to>Tove</to> <from>Jani</from> </note> <note date="12/11/2007"> <to>Tove</to> <from>Jani</from> </note> The error in the first document is that the date attribute in the note element is not quoted. < > & ' " less than greater than ampersand apostrophe quotation mark Note: Only the characters "<" and "&" are strictly illegal in XML. Study the two XML documents below. the attribute values must always be quoted. replace the "<" character with an entity reference: <message>if salary &lt.XML Attribute Values Must be Quoted XML elements can have attributes in name/value pairs just like in HTML. The first one is incorrect. but it is a good habit to replace it. 1000 then</message> There are 5 predefined entity references in XML: &lt. In XML. .

XML stores a new line as LF.. An element can contain:     other elements text attributes or a mix of all of the above.This is a comment --> White-space is Preserved in XML HTML truncates multiple white-space characters to one single white-space: HTML: Hello Output: Hello Tove Tove With XML. a new line is normally stored as an LF character. Ray</author> <year>2003</year> <price>39. XML Stores New Line as LF In Windows applications.Comments in XML The syntax for writing comments in XML is similar to that of HTML. What is an XML Element? An XML element is everything from (including) the element's start tag to (including) the element's end tag. Macintosh applications also use an LF to store a new line.99</price> </book> <book category="WEB"> <title>Learning XML</title> <author>Erik T. <bookstore> <book category="CHILDREN"> <title>Harry Potter</title> <author>J K. XML Elements An XML document contains XML Elements.. a new line is normally stored as a pair of characters: carriage return (CR) and line feed (LF). Rowling</author> <year>2005</year> <price>29. <!-.95</price> </book> </bookstore> . In Unix applications. the white-space in a document is not truncated.

Look at the following XML example: <note> <to>Tove</to> <from>Jani</from> <body>Don't forget me this weekend!</body> </note> . Colons are reserved to be used for something called namespaces (more later). and other characters Names cannot start with a number or punctuation character Names cannot start with the letters xml (or XML. If you name something "first-name. but watch out for problems if your software vendor doesn't support" some software may think you want to subtract name from first. <author>. Avoid ". A good practice is to use the naming rules of your database for the elements in the XML documents. XML Elements are Extensible XML elements can be extended to carry more information. numbers. like this: <book_title> not like this: <the_title_of_the_book>." some software may think that "name" is a property of the object "first. Avoid "-" characters. etc) Names cannot contain spaces Any name can be used. no words are reserved. Names should be short and simple. or Xml. <last_name>. <year>." Avoid ":" characters. Non-English letters like éòá are perfectly legal in XML. XML documents often have a corresponding database. <title>. Best Naming Practices Make names descriptive. XML Naming Rules XML elements must follow these naming rules:     Names can contain letters.In the example above." characters. and <price> have text content because they contain text. <bookstore> and <book> have element contents. because they contain other elements. If you name something "first. <book> also has an attribute (category="CHILDREN"). Names with an underscore separator are nice: <first_name>.

One of the beauties of XML. and <body> elements in the XML document and produce the same output. is that it can be extended without breaking applications. . The application should still be able to find the <to>. <from>.Let's imagine that we created an application that extracted the <to>. and <body> elements from the XML document to produce this output: MESSAGE To: Tove From: Jani Don't forget me this weekend! Imagine that the author of the XML document added some extra information to it: <note> <date>2008-01-10</date> <to>Tove</to> <from>Jani</from> <heading>Reminder</heading> <body>Don't forget me this weekend!</body> </note> Should the application break or crash? No. <from>.

please read our W3C Tutorial . If you want to study these subjects first. SOAP is a W3C Recommendation SOAP became a W3C Recommendation 24. What is SOAP?            SOAP stands for Simple Object Access Protocol SOAP is a communication protocol SOAP is for communication between applications SOAP is a format for sending messages SOAP communicates via Internet SOAP is platform independent SOAP is language independent SOAP is based on XML SOAP is simple and extensible SOAP allows you to get around firewalls SOAP is a W3C recommendation Why SOAP? It is important for application development to allow Internet communication between programs. June 2003. To read more about the SOAP activities at W3C. because HTTP is supported by all Internet browsers and servers. RPC represents a compatibility and security problem. with different technologies and programming languages. please read our XML Tutorial. Today's applications communicate using Remote Procedure Calls (RPC) between objects like DCOM and CORBA. Or more simply: SOAP is a protocol for accessing a Web Service. SOAP provides a way to communicate between applications running on different operating systems.SOAP Introduction SOAP is a simple XML-based protocol to let applications exchange information over HTTP. but HTTP was not designed for this. What You Should Already Know Before you study SOAP you should have a basic understanding of XML and XML Namespaces. A better way to communicate between applications is over HTTP. firewalls and proxy servers will normally block this kind of traffic. SOAP was created to accomplish this.

.org/2001/12/soap-encoding Syntax Rules Here are some important syntax rules:      A SOAP message MUST be encoded using XML A SOAP message MUST use the SOAP Envelope namespace A SOAP message MUST use the SOAP Encoding namespace A SOAP message must NOT contain a DTD reference A SOAP message must NOT contain XML Processing Instructions Skeleton SOAP Message <?xml version="" soap:encodingStyle="http://www..SOAP Syntax SOAP Building Blocks A SOAP message is an ordinary XML document containing the following elements:     An Envelope element that identifies the XML document as a SOAP message A Header element that contains header information A Body element that contains call and response information A Fault element containing errors and status information All the elements above are declared in the default namespace for the SOAP envelope: http://www. </soap:Header> <soap:Body> .org/2001/12/soap-encoding"> <soap:Header> .org/2001/12/soap-envelope and the default namespace for SOAP encoding and data types is: http://www.w3.. </soap:Fault> </soap:Body> </soap:Envelope> . <soap:Fault> .w3.0"?> <soap:Envelope xmlns:soap="http://www.w3.

</soap:Envelope> . The encodingStyle Attribute The encodingStyle attribute is used to define the data types used in the document.0"?> <soap:Envelope xmlns:soap="http://www. </soap:Envelope> The xmlns:soap Namespace Notice the xmlns:soap namespace in the example above.w3.. It should always have the value of: "http://www.. Syntax soap:encodingStyle="URI" Example <?xml version=""> . the application generates an error and discards the". If a different namespace is used.SOAP Envelope Element The SOAP Envelope element is the root element of a SOAP message..w3. Message information goes here . This attribute may appear on any SOAP element. and applies to the element's contents and all child elements. Message information goes here .w3. A SOAP message has no default encoding. This element defines the XML document as a SOAP" soap:encodingStyle="http://www.w3. The SOAP Envelope Element The required SOAP Envelope element is the root element of a SOAP" soap:encodingStyle="http://www.0"?> <soap:Envelope xmlns:soap="http://www. Example <?xml version=""> .. The namespace defines the Envelope as a SOAP Envelope.

and encodingStyle. .SOAP Header Element The SOAP Header element contains header information. Note: All immediate child elements of the Header element must be namespace-qualified.. etc) about the SOAP message. The SOAP Header Element The optional SOAP Header element contains application-specific information (like authentication. These attributes are:" soap:encodingStyle=""> <soap:Header> <m:Trans xmlns:m="http://www. and a value of 234. Syntax soap:mustUnderstand="0|1" Example <?xml version="1." soap:mustUnderstand="1">234 </m:Trans> </soap:Header>"). If the receiver does not recognize the element it will fail when processing the Header. If you add mustUnderstand="1" to a child element of the Header element it indicates that the receiver processing the Header must recognize the"> .w3. The mustUnderstand Attribute The SOAP mustUnderstand attribute can be used to indicate whether a header entry is mandatory or optional for the recipient to process.w3. If the Header element is present. SOAP defines three attributes in the default namespace ("http://www. The attributes defined in the SOAP Header defines how a recipient should process the SOAP message.0"?> <soap:Envelope xmlns:soap="http://www.w3. </soap:Envelope> The example above contains a header with a "Trans" element. <?xml version="1.w3.0"?> <soap:Envelope xmlns:soap="" soap:encodingStyle="http://www. actor. a "mustUnderstand" attribute with a value of 1. it must be the first child element of the Envelope element.

However. </soap:Envelope> The encodingStyle Attribute The encodingStyle attribute is used to define the data types used in the document." soap:actor="http://www..<soap:Header> <m:Trans xmlns:m="http://www.w3schools.w3. and it will apply to that element's contents and all child">234 </m:Trans> </soap:Header> . </soap:Envelope> The actor Attribute A SOAP message may travel from a sender to a receiver by passing different endpoints along the message" soap:mustUnderstand="1">234 </m:Trans> </soap:Header> . Syntax soap:actor="URI" Example <?xml version="1. instead. This attribute may appear on any SOAP element.. Syntax soap:encodingStyle="URI" .. not all parts of a SOAP message may be intended for the ultimate endpoint. A SOAP message has no default encoding.. it may be intended for one or more of the endpoints on the message" soap:encodingStyle="http://www.0"?> <soap:Envelope xmlns:soap="http://www.w3. .org/2001/12/soap-encoding"> <soap:Header> <m:Trans xmlns:m="http://www. The SOAP actor attribute is used to address the Header element to a specific endpoint.

w3. The SOAP Body Element The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message. A SOAP response could look something like this: <?xml version=""> <soap:Body> <m:GetPrice xmlns:m="http://www. They are not a part of the SOAP namespace. Note that the m:GetPrice and the Item elements above are application-specific elements.0"?> <soap:Envelope xmlns:soap="" soap:encodingStyle="http://www.w3schools.SOAP Body Element The SOAP Body element contains the actual SOAP message.w3. Example <?xml version=""> <m:Price>1. Immediate child elements of the SOAP Body element may be"> <soap:Body> <m:GetPriceResponse xmlns:m=""> <m:Item>Apples</m:Item> </m:GetPrice> </soap:Body> </soap:Envelope> The example above requests the price of" soap:encodingStyle="http://www.0"?> <soap:Envelope xmlns:soap="http://www.w3schools.90</m:Price> </m:GetPriceResponse> </soap:Body> </soap:Envelope> .

Sign up to vote on this title
UsefulNot useful