1 / 27

XML Language Family Detailed Examples

XML Language Family Detailed Examples. Most information contained in these slide comes from: h ttp://www.w3.org, http://www.zvon.org/ These slides are intended to be used as a tutorial on XML and related technologies Slide author: Jürgen Mangler (juergen.mangler@univie.ac.at)

zagiri
Download Presentation

XML Language Family Detailed Examples

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XML Language FamilyDetailed Examples • Most information contained in these slide comes from: http://www.w3.org, http://www.zvon.org/ • These slides are intended to be used as a tutorial on XML and related technologies • Slide author:Jürgen Mangler (juergen.mangler@univie.ac.at) • This section contains examples on: XML Schema

  2. The purpose of XML Schema is to deploy a standard mechanism to describe and evaluate the datatype of the content of an element. XML examples: <myElement type="integer">12</myElement> correct<myElement type="integer">eT</myElement> also correct The XML Parser can not distiguish the content of an Element. This is where XML Schema comes in: <name xsi:noNamespaceSchemaLocation="correct_0.xsd" xmlns="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> Jürgen Mangler </name>

  3. If we use the attribute "noNamespaceSchemaLocation", we tell the document that the schema belongs to an element from the null namespace. Valid document: <namexsi:noNamespaceSchemaLocation="correct_0.xsd" xmlns="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> Jürgen Mangler </name> correct_0.xsd: <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" > <xsd:element name="name" type="xsd:string"/> </xsd:schema>

  4. If we use the attribute "schemaLocation", we tell the document that the schema belongs to an element from some particular namespace. In the schema definition, you have to use the "targetNamespace" attribute, which defines the element's namespace. Valid document: <f:anElementxsi:schemaLocation="http://foo correct_0.xsd" xmlns:f="http://foo" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> This Element contains some cdata. </f:anElement> correct_0.xsd: <xsd:schema targetNamespace="http://foo" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="anElement" type="xsd:string"/> </xsd:schema>

  5. Valid document: <AAA> xxx yyy </AAA> If we want the root element to be named "AAA", from null namespace and containing text only. correct_0.xsd: <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="AAA" type="xsd:string"/> </xsd:schema>

  6. If we want the root element to be named "AAA", from null namespace, containing text and an element "BBB", we will need to set the attribute "mixed" to "true" - to allow mixed content. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >   <xsd:element name="AAA">     <xsd:complexType mixed="true">       <xsd:sequence minOccurs="1">         <xsd:element name="BBB" type="xsd:string"/>       </xsd:sequence>     </xsd:complexType>   </xsd:element> </xsd:schema> <AAA> xxx yyy   <BBB>ZZZ</BBB>aaa </AAA>

  7. We want the root element to be named "AAA", from null namespace, containing one "BBB" and one "CCC" element. Their order is not important. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >   <xsd:element name="AAA">     <xsd:complexType mixed="false">       <xsd:all minOccurs="1" maxOccurs="1">         <xsd:element name="BBB" type="xsd:string"/>         <xsd:element name="CCC" type="xsd:string"/>       </xsd:all>     </xsd:complexType>   </xsd:element> </xsd:schema> <AAA>   <CCC/>   <BBB/> </AAA>

  8. We want the root element to be named "AAA", from null namespace, containing a mixture of any number (even zero), of "BBB" and "CCC" elements. We need to use the 'trick' below - we use a "sequence" element with "minOccurs" attribute set to 0 and "maxOccurs" set to "unbounded". The attribute "minOccurs" of the "element" elements has to be 0 too. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >   <xsd:element name="AAA">     <xsd:complexType mixed="false">       <xsd:sequence minOccurs="0" maxOccurs="unbounded">         <xsd:element name="BBB" type="xsd:string" minOccurs="0"/>         <xsd:element name="CCC" type="xsd:string" minOccurs="0"/>       </xsd:sequence>     </xsd:complexType>   </xsd:element> </xsd:schema> Give a valid document!

  9. We want the root element to be named "AAA", from null namespace, containing a mixture of any number (even zero) of "BBB" and "CCC" elements. You need to use the trick below - use "sequence" element with "minOccurs" attribute set to 0 and "maxOccurs" set to "unbounded", and the attribute "minOccurs" of the "element" elements must be set to 0 too. <AAA>   <BBB>111</BBB>   <CCC>YYY</CCC>   <BBB>222</BBB>   <BBB>333</BBB>   <CCC>ZZZ</CCC> </AAA> A valid solution!

  10. We want the root element to be named "AAA", from null namespace, containing either "BBB" or "CCC" elements (but not both) - the "choice" element. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >   <xsd:element name="AAA">     <xsd:complexType mixed="false">       <xsd:choice minOccurs="1" maxOccurs="1">         <xsd:element name="BBB" type="xsd:string"/>         <xsd:element name="CCC" type="xsd:string"/>       </xsd:choice>     </xsd:complexType>   </xsd:element> </xsd:schema> <AAA>   <CCC>aaa</CCC></AAA> Other valid solutions?

  11. In XML Schema, the datatype is referenced by the QName. The namespace must be mapped to the prefix. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >   <xsd:element name="root" type="xsd:integer"/> </xsd:schema> <root> 25 </root>

  12. Restricting simpleType is relatively easy. Here we will require the value of the element "root" to be integer and less than 25. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >   <xsd:element name="root">     <xsd:simpleType>       <xsd:restriction base="xsd:integer">         <xsd:maxExclusive value="25"/>       </xsd:restriction>     </xsd:simpleType>   </xsd:element> </xsd:schema> <root> 25 </root> Valid? Use <xsd:minInclusive value="0"/> to force element > 0. You can also combine min/max in <xsd:restriction>!

  13. If we want the element "root" to be either a string "N/A" or a string "#REF!", we will use <xsd:enumeration> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">  <xsd:element name="root">     <xsd:simpleType>       <xsd:restriction base="xsd:string">         <xsd:enumeration value="N/A"/>         <xsd:enumeration value="#REF!"/>       </xsd:restriction>     </xsd:simpleType>   </xsd:element> </xsd:schema> <root> N/A </root> Other solutions?

  14. If we want the element "root" to be either an integer or a string "N/A", we will make a union from an "integer" type and "string" type. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">  <xsd:element name="root">     <xsd:simpleType>       <xsd:union>         <xsd:simpleType>           <xsd:restriction base="xsd:integer"/>         </xsd:simpleType>         <xsd:simpleType>           <xsd:restriction base="xsd:string">             <xsd:enumeration value="N/A"/>           </xsd:restriction>         </xsd:simpleType>       </xsd:union>     </xsd:simpleType>   </xsd:element> </xsd:schema>

  15. Below we define a group of common attributes, which will be reused. The root element is named "root", it must contain the "aaa" element, and this element must have attributes "x" and "y".   <xsd:element name="root">     <xsd:complexType>       <xsd:sequence>         <xsd:element name="aaa" minOccurs="1" maxOccurs="1">           <xsd:complexType>             <xsd:attributeGroup ref="myAttrs"/>           </xsd:complexType>         </xsd:element>       </xsd:sequence>     </xsd:complexType>   </xsd:element> <xsd:attributeGroup name="myAttrs">     <xsd:attribute name="x" type="xsd:integer" use="required"/>     <xsd:attribute name="y" type="xsd:integer" use="required"/>   </xsd:attributeGroup> Give a valid document!

  16. Below we define a group of common attributes, which will be reused. The root element is named "root", it must contain the "aaa" and "bbb" elements, and these elements must have attributes "x" and "y". <root>   <aaa x="1" y="2"/> </root> Valid document from the previous Schema!

  17. We want the "root" element to have an attribute "xyz", which contains a list of three integers. We will define a general list (element "list") of integers and then restrict it (element "restriction") to have a length (element "length") of exactly three items. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >   <xsd:element name="root">     <xsd:complexType>       <xsd:attribute name="xyz" use="required">         <xsd:simpleType>           <xsd:restriction base="myList">             <xsd:length value="3"/>           </xsd:restriction>         </xsd:simpleType>       </xsd:attribute>     </xsd:complexType>   </xsd:element> <xsd:simpleType name="myList">     <xsd:list itemType="xsd:integer"/>   </xsd:simpleType> </xsd:schema> Documents on next page …

  18. We want the "root" element to have an attribute "xyz", which contains a list of three integers. We will define a general list (element "list") of integers and then restrict it (element "restriction") to have a length (element "length") of exactly three items. Valid!<root xyz="0 0 1"/> Not valid! Why?<root xyz="0 0 1 1"/> Use the same method for lists in the content of elem.

  19. The element "A" has to contain a string which is exactly three characters long. We will define our custom type for the string named "myString" and will require the element "A" to be of that type. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >  <xsd:element name="A" type="myString"/>  <xsd:simpleType name="myString">     <xsd:restriction base="xsd:string">       <xsd:length value="3"/>     </xsd:restriction>   </xsd:simpleType> </xsd:schema> <buchstaben> abc </buchstaben>

  20. The element "A" must contain an email address. We will define our custom type, which will at least approximately check the validity of the address. We will use the "pattern" element, to restrict the string using regular expressions. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >   <xsd:element name="email" type="myString"/>   <xsd:simpleType name="myString">     <xsd:restriction base="xsd:string">       <xsd:pattern value="[^@]+@[^.]+\..+"/>     </xsd:restriction> </xsd:simpleType> </xsd:schema> <email> kung@foo.org </email>

  21. Regular Expressions - the meaning of: [^@]+@[^.]+\..+ [abc] … Characters Class (character can be a, b or c) [^abc] … Negative Character Class (everything except a,b,c) * … Match 0 or more times + … Match 1 or more times ? … Match 1 or 0 times {n} … Match exactly n times {n,} … Match at least n times {n,m} … Match at least n but not more than m times . … match any character \w … Match a "word" character (alphanumeric plus "_") \W … Match a non-word character \d … Match a digit character \D … Match a non-digit character \. … Escape a character with a special Meaning (., +, *, ?, …) [^@]+ … match any character that is not a @ 1 or more times @ … match exactly a @ [^.]+ … match any character that is not a . 1 or more times \. … match exactly a . .+ … match any character 1 or more times

  22. One of the big problems of XML ist the type ID. An attribute of type ID must be unique for the whole file. XML Schema solves this problem: ID's can be vaild for a certain child axis only. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >  <xsd:element name="root" type="myList">     <xsd:unique name="myId">       <xsd:selector xpath="./a"/>       <xsd:field xpath="@id"/>     </xsd:unique>   </xsd:element>  <xsd:complexType name="myList">     <xsd:sequence minOccurs="1">       <xsd:element name="a" minOccurs="1" maxOccurs="unbounded">         <xsd:complexType>           <xsd:attribute name="id" type="xsd:NCName"/>         </xsd:complexType>       </xsd:element>     </xsd:sequence>   </xsd:complexType> </xsd:schema> Document on next page …

  23. One of the big problems of XML ist the type ID. An attribute of type ID must be unique for the whole file. XML Schema solves this problem: ID's can be vaild for a certain child axis only. <root>   <aid="x"/>   <aid="y"/>   <aid="z"/> </root>

  24. The "keyref" lets you specify, that an attribute/element refers to some node (which must be defined as "key" or "unique"). The "key" element requires the elements "a" under the "root" element to contain the existing and unique value of an "id" attribute. Replace <xsd:unique> with: <xsd:key name="myId">     <xsd:selector xpath="./a"/>     <xsd:field xpath="@id"/> </xsd:key> <xsd:keyref name="myIdref" refer="myId">   <xsd:selector xpath="./b"/>     <xsd:field xpath="@ref"/> </xsd:keyref> Add to <xsd:sequence> in myList:   <xsd:element name="b" minOccurs="0" maxOccurs="1">     <xsd:complexType>       <xsd:attribute name="ref" type="xsd:NCName" use="required"/>     </xsd:complexType>   </xsd:element> Document on next page …

  25. The "keyref" lets you specify, that an attribute/element refers to some node (which must be defined as "key" or "unique"). The "key" element requires the elements "a" under the "root" element to contain the existing and unique value of an "id" attribute. <root>   <a id="x"/>   <a id="y"/>   <b idref="x"/> </root>

  26. To define attributes AND childs for a certain element you have to use simpleContent. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xsd:element name="mixit">     <xsd:complexType>       <xsd:simpleContent>        <xsd:extension base="xsd:string">           <xsd:attribute name="times" type="xsd:string" use="required"/>         </xsd:extension>       </xsd:simpleContent>     </xsd:complexType>   </xsd:element> </xsd:schema> <mixit times="7" > shake </mixit>

  27. Wann nehm ich simple-, wann complexType • simpleType: • Wenn ich den Inhalt eines Elements als xsd:string, xsd:integer, xsd:double, ... definieren will • complexType • Wenn ich Attribute definieren will • Wenn ich andere Elemente als Inhalt definieren will (mit sequence, choice, all) • Wenn ich Attribute und Elemente mischen will (xsd:attribute unterhalt von sequence, choice, all • simpleContent innerhalb von complexType • Wenn ich den Inhalt eines Elements als Datentyp definieren und zusätzlich Attribute haben will

More Related