XML Extensible Markup Language XML n n n

XML Extensible Markup Language

XML n n n A descendent of SGML (Standard Generalized Markup Language) A recommendation of W 3 C in 1998 A universal language for data on the Web n n n A meta markup language n n n HTML for the presentation of data XML for the structuring of data Enables the creation of new markup languages to markup anything imaginable (math formulas, molecular structure of chemical, etc. ) Gives developers the power to deliver structured data from a wide variety of applications to the desktop for local computation and presentation An ideal format for server-to-server transfer of structured data

XML and its Derivatives n n n n Math. ML Chem. ML Voice. ML Fp. ML (Financial Products Markup Language) BSML (Bio-Sequence Markup Language) SMIL (Synchronized Multimedia Interface Language) XMI (XML Metadata Interchange) n XML + UML n n => universal format for exchanging OO system analysis and design documents More …

How XML is similar to HTML n XML uses tags just like HTML, but those tags don’t define text formatting. Instead the tags are used to create data structures Let’s see some examples…

Examples of HTML and XML HTML Code: XML Code: <b> This is bold text… </b> <President> Clinton </President> Using our own custom tag named “President, ” we have stored a small piece of information.

Detailed Example n XML documents is organized in a hierarchal fashion. Each tag or node can have “sub” nodes under it. <President> <Name>Clinton, Bill</Name> <Age>52</Age> <Terms>2</Terms> </President> n Well-Formedness: Any number of nodes can be created under any given node. But each node must be “closed” using a closing tag, like </President>. n Exception: “empty” element does not have a closing tag n E. g. , <flag id = “Y” /> Must end with a forward slash

XML Elements n n A “Node” in an XML document is known as an Element. An XML document can have any number of elements. n n For example we could store information about 10 Presidents in a document. There is only one root element, i. e. , </President>

Multiple Elements <Car> <Manufacturer>Mitsubishi</Manufacturer> <Model>Eclipse</Model> <Year>1998</Year> </Car> <Manufacturer>Pontiac</Manufacturer> <Model>Sun Fire</Model> <Year>1997<Year> </Car> <Manufacturer>Nissan</Manufacturer> <Model>X-Terra</Model> <Year>2000<Year> <SUV>Yes</SUV> </Car>

Attributes n n n Besides having “sub-elements, ” every element can also have what are known as Attributes are declared “inside” the tag. You may already know how to use attributes if you have used the <IMG> or <A> tags in HTML. For example: <A HREF=“somepage. html”>click here</A>

XML Attributes n Here’s an example of an XML element with an Attribute…. <Vehicle VIN=“ 3232382432832”> <Year>1997</Year> <Manufacturer>Toyota</Manufacturer> </Vehicle> n We could make any element an attribute. n For example, Manufacturer and Year could also have been made attributes. However you usually want only meta-data or scalar to be an attribute.

A Complete Example (1) <? xml version = "1. 0"? > <!–- Deitel 2000, Fig. 28. 1: article. xml -->  <article> <title>Simple XML</title> <date>September 6, 1999</date> <author> <fname>Tem</fname> <lname>Nieto</lname> </author> <summary>XML is pretty easy. </summary> <content>Once you have mastered HTML, XML is easily learned. You must remember that XML is not for displaying information but for managing information. </content> </article>

A Complete Example (2 a) <? xml version = "1. 0"? >

A Complete Example (2 b) <contact type = "to"> <name>Joe Schmoe</name> <address 1>Box 12345</address 1> <address 2>15 Any Ave. </address 2> <city>Othertown</city> <state>Otherstate</state> <zip>67890</zip> <phone>555 -4321</phone> <flag id = "B"/> </contact> <paragraph>Dear Sir, </paragraph> <paragraph>It is our privilege to inform you about our new database managed with XML. This new system will allow you to reduce the load of your inventory list server by having the client machine perform the work of sorting and filtering the data. </paragraph> <paragraph>Sincerely, Mr. Doe</paragraph>

DTD n DTD = Document Type Definition n n Defines the grammatical rules for the document Not required for XML but recommended for document conformity n n n Can check the Validity of a XML document (contains proper elements, attributes, etc. ) Uses EBNF grammar Represented by the DOCTYPE tag, which contains three parts if it refers to an external subset: n n n Root element applied Flag (e. g. , SYSTEM (personal, non-standardized), PUBLIC (standardized, publicly available)) DTD name and location

DTD: Example <!ELEMENT letter (contact+, paragraph+)> <!ELEMENT contact (name, address 1, address 2, city, state, zip, phone, flag)> <!ATTLIST contact type CDATA #IMPLIED> <!ELEMENT <!ELEMENT <!ATTLIST name (#PCDATA)> address 1 (#PCDATA)> address 2 (#PCDATA)> city (#PCDATA)> state (#PCDATA)> zip (#PCDATA)> phone (#PCDATA)> flag EMPTY> flag id CDATA #IMPLIED> <!ELEMENT paragraph (#PCDATA)>

DTD: Example (cont’d) n !ELEMENT element type declaration n n n Specifies that an element is being created Here, a letter is being created with one or more contact element and one or more paragraph element, in that order. Operator + means one or more occurrences Operator * means zero or more occurrences Operator ? means zero or exactly one occurrence If no operator is included, exactly one occurrence is assumed. Others: “|” - alternatives

DTD: Example (cont’d) n !ATTLIST element type declaration n n Defines the attribute of an element Here, the type of contract is defined to have: n n n A string (as given by CDATA), which is unspecified and optional (as given by #IMPLIED). The string will not be parsed by XML processor and will simply be passed directly to the application Others: n n #PCDATA means this element can store parsed character data (i. e. , text) EMPTY means the element does not contain any element n n Commonly used for an element’s attribute More Others: n IDs and IDREFs (your next assignment!)

XML Schema [Silberschatz et al. ’ 02] n XML Schema is a more sophisticated schema language which addresses the drawbacks of DTDs. Supports n Typing of values n n User defined types Is itself specified in XML syntax, unlike DTDs n n n More standard representation, but verbose Is integrated with namespaces Many more features n n E. g. integer, string, etc Also, constraints on min/max values List types, uniqueness and foreign key constraints, inheritance. . BUT: significantly more complicated than DTDs, not yet widely used (yet!).

Namespaces n n When XML data has to be exchanged between organizations, same tag name may have different meaning in different organizations, causing confusion on exchanged documents. Specifying a unique string as an element name avoids confusion Better solution: use unique-name: element-name Avoid using long unique names all over document by using XML Namespaces <bank xmlns: FB=‘http: //www. First. Bank. com’> … <FB: branch> <FB: branchname>Downtown</FB: branchname> <FB: branchcity> Brooklyn</FB: branchcity> </FB: branch> … </bank>

XML Schema: Example <xsd: schema xmlns: xsd=http: //www. w 3. org/2001/XMLSchema> <xsd: element name=“bank-2” type=“Bank. Type”/> <xsd: element name=“account”> <xsd: complex. Type> <xsd: sequence> <xsd: element name=“account-number” type=“xsd: string”/> <xsd: element name=“branch-name” type=“xsd: string”/> <xsd: element name=“balance” type=“xsd: decimal”/> </xsd: squence> </xsd: complex. Type> </xsd: element> …. . definitions of customer and depositor …. <xsd: complex. Type name=“Bank. Type”> <xsd: squence> <xsd: element ref=“account” min. Occurs=“ 0” max. Occurs=“unbounded”/> <xsd: element ref=“customer” min. Occurs=“ 0” max. Occurs=“unbounded”/> <xsd: element ref=“depositor” min. Occurs=“ 0” max. Occurs=“unbounded”/> </xsd: sequence> </xsd: complex. Type> </xsd: schema>

Example <bank-2> <account-number>A-102</account-number> <branch-name>Perryridge</branch-name> <balance>400</balance> </account> <account> … </account> <customer-name>Hayes</customer-name> <customer-street>Main</customer-street> <customer-city>Harrison</customer-city> </customer>. . </bank-2>

Querying and Transforming XML Data [Silberschatz et al. ’ 02] n n Translation of information from one XML schema to another Querying on XML data Above two are closely related, and handled by the same tools Standard XML querying/translation languages n XPath n n XSLT n n Simple language designed for translation from XML to XML and XML to HTML XQuery n n Simple language consisting of path expressions An XML query language with a rich set of features Wide variety of other languages have been proposed, and some served as basis for the XQuery standard n XML-QL, Quilt, XQL, …

Tree Model of XML Data n n Query and transformation languages are based on a tree model of XML data An XML document is modeled as a tree, with nodes corresponding to elements and attributes n n n Element nodes have children nodes, which can be attributes or subelements Text in an element is modeled as a text node child of the element Children of a node are ordered according to their order in the XML document Element and attribute nodes (except for the root node) have a single parent, which is an element node The root node has a single child, which is the root element of the document We use the terminology of nodes, children, parent, siblings, ancestor, descendant, etc. , which should be interpreted in the above tree model of XML data.

XPath n n XPath is used to address (select) parts of documents using path expressions A path expression is a sequence of steps separated by “/” n n n Think of file names in a directory hierarchy Result of path expression: set of values that along with their containing elements/attributes match the specified path E. g. /bank-2/customer/name evaluated on the bank-2 data we saw earlier returns <name>Joe</name> <name>Mary</name> n E. g. /bank-2/customer/name/text( ) returns the same names, but without the enclosing tags

XPath n n The initial “/” denotes root of the document (above the top -level tag) Path expressions are evaluated left to right n n Each step operates on the set of instances produced by the previous step Selection predicates may follow any step in a path, in [ ] n E. g. n n n /bank-2/account[balance > 400] returns account elements with a balance value greater than 400 /bank-2/account[balance] returns account elements containing a balance subelement Attributes are accessed using “@” n E. g. /bank-2/account[balance > 400]/@account-number n returns the account numbers of those accounts with balance > 400

XPath n Operator “|” used to implement union n E. g. /bank-2/account/id(@owner) | /bank-2/loan/id(@borrower) n n n “//” can be used to skip multiple levels of nodes n E. g. /bank-2//name n n gives customers with either accounts or loans However, “|” cannot be nested inside other operators. finds any name element anywhere under the /bank-2 element, regardless of the element in which it is contained. A step in the path can go to: parents, siblings, ancestors and descendants of the nodes generated by the previous step, not just to the children n n “//”, described above, is a short from for specifying “all descendants” “. . ” specifies the parent.

Functions in XPath provides several functions n The function count() at the end of a path counts the number of elements in the set generated by the path n E. g. /bank-2/account[customer/count() > 2] n n Returns accounts with > 2 customers Also function for testing position (1, 2, . . or last()) of node w. r. t. siblings Boolean connectives and, or and function not() can be used in predicates IDREFs can be referenced using function id() n n id() can also be applied to sets of references such as IDREFS and even to strings containing multiple references separated by blanks E. g. /bank-2/account/id(@owner) n returns all customers referred to from the owners attribute of account elements.

XSL n n Extensible Style Language (XSL) Defines the layout of an XML (much like CSS defines the layout of an HTML document) n n XSL style sheet provides the rules for displaying an XML document XSL also defines rules on how an XML document is transformed into another XML document (i. e. , XSLT for XSL Transformation)

XSL: Example (cont’d) <xsl: for-each order-by = “+Lastname; +Firstname” select = “contact” xmlns: xsl = http: //www. w 3. org/TR/WD-xsl> n for-each n n order-by n n + means ascending; - means descending select n n Iterate over each element of contact Defines which elements are selected xmlns n n XML namespace Indicates where the specification for this element is located

XSL: Example (cont’d) <Lastname><xsl: value-of select = “Lastname”/> n xsl: value-of n n Retrieves the data specified in attribute select Empty element and thus the ‘/’ <xsl: for-each select = “contact[Lastname=‘Neito’]” n contact[Lastname=‘Neito’] n [] specifies XSL conditional statement

XSL: Example (cont’d) var xmldoc = xml. Data. clone. Node( true ); n n Copy xml. Data object so that we don’t lose the original true means recursively copy function sort( xsldoc ) { xmldoc. document. Element. transform. Node. To. Object( xsldoc. document. Element, xml. Data. XMLDocument ); } n transform. Node. To. Object n Applies a specified XSL style sheet to the data contained in the parent object n document. Element gets the root element n XMLDocument accesses the XML document to which xml. Data refers

XML Editors

XML Resources § § W 3 C XML Standards Body § http: //www. w 3 c. org/xml Microsoft Developer Network (MSDN) § http: //msdn. microsoft. com/xml The Biz. Talk Framework § http: //www. biztalk. org IBM’s XML Zone § http: //www. ibm. com/developer/xml/

XSL, <XML> tag, DOM <!DOCTYPE HTML PUBLIC "-//W 3 C//DTD HTML 4. 0 Transitional//EN"> <HTML>  <BODY> <XML ID = "xml. Data" src = "contact. xml"></XML> <XML ID = "xml. Sort. Last. Name"> <contacts> <xsl: for-each order-by = "+Last. Name; +First. Name" select = "contact" xmlns: xsl = "http: //www. w 3. org/TR/WD-xsl"> <contact> <Last. Name><xsl: value-of select = "Last. Name"/> </Last. Name> <First. Name><xsl: value-of select = "First. Name"/> </First. Name> </contact> </xsl: for-each> </contacts> </XML>

<XML ID = "xml. Filter. Last. Name"> <contacts> <xsl: for-each select = "contact[Last. Name='Nieto']" xmlns: xsl = "http: //www. w 3. org/TR/WD-xsl"> <contact> <Last. Name><xsl: value-of select = "Last. Name"/> </Last. Name> <First. Name><xsl: value-of select = "First. Name"/> </First. Name> </contact> </xsl: for-each> </contacts> </XML> <SCRIPT LANGUAGE = "Javascript"> var xmldoc = xml. Data. clone. Node( true ); function sort( xsldoc ) { xmldoc. document. Element. transform. Node. To. Object ( xsldoc. document. Element, xml. Data. XMLDocument ); } </SCRIPT>

<TABLE BORDER = "1" DATASRC = "# xml. Data" DATAPAGESIZE = "2" ID = "tbl"> <THEAD> <TR> <TH>Last Name</TH> <TH>First Name</TH> </TR> </THEAD> <TR> <TD><SPAN DATAFLD = " Last. Name"></SPAN></TD> <TD><SPAN DATAFLD = " First. Name"></SPAN></TD> </TR> </TABLE> <INPUT TYPE = "button" VALUE = "Sort By Last Name" ONCLICK = "sort(xml. Sort. Last. Name. XMLDocument ); "> <INPUT TYPE = "button" VALUE = "Sort By First Name" ONCLICK = "sort(xml. Sort. First. Name. XMLDocument ); "> <INPUT TYPE = "button" VALUE = "Revert" ONCLICK = "sort(xml. Revert. Order. XMLDocument ); "> <BR> <INPUT TYPE = "button" VALUE = "Filter for Nieto" ONCLICK = "sort(xml. Filter. Last. Name. XMLDocument ); "> <BR> <INPUT TYPE = "button" VALUE = "|<" ONCLICK=" tbl. first. Page(); "> <INPUT TYPE = "button" VALUE="<" ONCLICK=" tbl. previous. Page(); "> <INPUT TYPE = "button" VALUE = ">" ONCLICK = " tbl. next. Page(); "> <INPUT TYPE = "button" VALUE = ">|" ONCLICK = " tbl. last. Page(); "> </BODY> </HTML>