0% found this document useful (0 votes)

24 views202 pages

Week 6 XML

XML

Uploaded by

cooperkreates

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

24 views202 pages

Week 6 XML

XML

Uploaded by

cooperkreates

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 202

XML

EXTENSIBLE MARKUP
LANGUAGE
IMPORTANT RESOURCE

W3Schools Tutorials
•XML Tutorial •XML Schema Tutorial
•Recommended parts: •Recommended parts:
•XML Introduction •XSD Introduction
•XML How to Use
•XML Tree
•XSD How To
•XSD <schema>
Optional tutorials that
•XML Syntax
•XML Elements
•XSD Elements
•XSD Attributes
cover XML and XML
•XML Attributes
•XML Namespaces
•XSD Complex Elements
•XSD Elements Only
Schemas.
•XML Display •XSD Text-Only Elements
•XML Validator •XSD Indicators Great resource if you
•XML Schema •XSD String Data Types
•XSD Date and Time Data Types need extra help with XML.
•XSD Numeric Data Types
•XSD Miscellaneous Data Types
3

COMPUTER

To understand at a conceptual Level:

» What is a computer?
» “This instrument can teach, it can illuminate; yes, and even it can inspire,” spoke Murrow. “But
it can do so only to the extent that humans are determined to use it to those ends. Otherwise,
it’s nothing but wires and lights in a box.” - Edward R. Murrow (originally referencing television)
» Still true today when talking about computers.
» It needs software to be anything more than this.
» Software gives the box the “intelligence”.
4

COMPUTER

What does a computer “know”?

» Presence or absences of a charge

COMPUTER

What does a computer “know”?

» Encoded as binary numbers (0s or 1s)

COMPUTER

What does a computer “know”?

COMPUTER

What does a computer “know”?

10100110 →B
» Binary numbers can represent text, images, videos, etc.
8

COMPUTER

Now you want to deliver (transmit) those ones and zeros to all your friends.

How?

Connection.
9

COMPUTER

Now you want to deliver (transmit) those ones and zeros to all your friends.

How?

… internet and the world wide web

MARKUP LANGUAGES

Annotations to text
» instructions on how text is to be displayed/used.
Types:
» Presentational
» Procedural
» Descriptive
⋄ GML/SGML
⋄ HTML/XHTML
⋄ XML
MESSAGE & DATA EXCHANGE
11

TECHNOLOGIES

• Telephone
• Paper (Fax, Postal mail)
• Email
• Electronic Data Interchange (EDI)
• eXtensible Markup Language (XML)
12

XML

So…

• eXtensible Markup Language (XML)

- Data Transport Mechanism

XML

DATA -
From one computer
To another computer
14

XML

DATA -
From one computer
To another computer
15

XML
A method (mechanism) to copy (upload) large amounts
of data into a database.

DATA
16

XML
17

XML: EXAMPLE
Add a list of all of your friends:
- their names, ages and hobby

Database: Steve 21 Skip Rope

Jane 19 Comics
Idra 20 Baseball
18

XML: EXAMPLE
Add a list of all of your friends:
- their names, ages and hobby

Database: Steve 21 Skip Rope

Jane 19 Comics
Idra 20 Baseball

Multiply that by the

Number of students
Enrolled in CS1032
19

XML: EXAMPLE
Add a list of all of your friends:
- their names, ages and hobby

Steve 21 Skip Rope

Database: Jane 19 Comics
Idra 20 Baseball

Way to much
data to enter
by hand!
20

XML

Have each
student send
their list by
Email:
21

XML

Have each
student send
their list by
Email:
22

XML
Each student sends data formatted differently!

Have each
student send
their list by
Email:
23

XML
Each student sends data formatted differently!

Have each
student send
their list by
Email:
No standardized
format used.
Still need to reinput
in database by hand!
24

XML

XML:

Provides a
standardized
format for data.
25

XML

XML:

Computer readable.
Can automate
import!
26

XML

How do we get/write XML???

XML

EASY:

data
- enclosed (encased) by tags

everything in an XML document is one of two things ONLY!

- it either DATA or it is a TAG

XML

EASY:

data
Joe Bloggs
29

XML

EASY:

data
Joe Bloggs

tag ( a label ‘bookended’ by angle brackets )

<tag1>
30

XML

EASY:

data
Joe Bloggs

tag ( a label ‘bookended’ by angle brackets )

<tag1>
XML statement ( combine the data with tags )
<tag1>Joe Bloggs</tag1>
31

XML

EASY: (everything is either data or it is a tag)

XML

Tags - every tag has a START tag

and MUST have a matching END tag
<tag1> START TAGS
<tag2> NOTE: END TAG
<tag3>Hope Ferdebest</tag3> - must match the start tag
<tag4>English</tag4> EXACTLY (including case)
<tag5>2020</tag5>
</tag2> - end tag denoted by the
</tag1>

END TAGS
forward slash/
35

XML

Tags - every tag has a START tag

and MUST have a matching END tag
<tag1>
<tag2> NOTE: TAG RULES
<tag3>Hope Ferdebest</tag3> - no spaces in the labels
<tag4>English</tag4>
<tag5>2020</tag5> - can not start with a number
</tag2> or with the letters “XML”
</tag1>
36

XML

Tags - complex: enclose (encase) other tags

<tag1>
<tag2>
<tag3>Hope Ferdebest</tag3> tag1 and tag2 are
<tag4>English</tag4> complex tags
<tag5>2020</tag5>
</tag2>
</tag1>

COMPLEX TAGS
38

XML
Tags - complex: allows “grouping” of data
<tag1>
<tag2>
<tag3>Hope Ferdebest</tag3>
<tag4>English</tag4> GROUP #1
<tag5>2020</tag5>
</tag2>
<tag2>
<tag3>Isma Braineful</tag3>
<tag4>Math</tag4> GROUP #2
<tag5>2019</tag5>
</tag2>
</tag1>
39

XML
Tags - complex: allows “grouping” of data
<tag1>
<tag2>
<tag3>Hope Ferdebest</tag3>
<tag4>English</tag4> GROUP #1
<tag5>2020</tag5>
</tag2> MAJOR
<tag2> GROUP
<tag3>Isma Braineful</tag3>
<tag4>Math</tag4> GROUP #2
<tag5>2019</tag5>
</tag2>
</tag1>
40

XML
Tags - complex: grouping tags have the same (repeating) labels
<tag1>
<tag2>
<tag3>Hope Ferdebest</tag3>
<tag4>English</tag4> GROUP #1
<tag5>2020</tag5>
</tag2> MAJOR
<tag2> GROUP
<tag3>Isma Braineful</tag3>
<tag4>Math</tag4> GROUP #2
<tag5>2019</tag5>
</tag2>
</tag1>
41

XML
Tags - simple: grouping tags have the same (repeating) labels
<tag1>
<tag2>
<tag3>Hope Ferdebest</tag3>
<tag4>English</tag4> GROUP #1
<tag5>2020</tag5>
</tag2> MAJOR
<tag2> GROUP
<tag3>Isma Braineful</tag3>
<tag4>Math</tag4> GROUP #2
<tag5>2019</tag5>
</tag2>
</tag1>
42

XML
Tags - They should be meaningful to the data context
<course>
<student>
<name>Hope Ferdebest</name>
<major>English</major>
<year>2020</year> Tags should have
</student > descriptive labels
<student > (not just tag1, tag2, etc.)
<name>Isma Braineful</name>
<major>Math</major>
<year>2018</year>
</student >
</course>
43

XML

Tags - BUT: they can be anything*

<foo> *TAG RULES
<bar> - no spaces in the labels
<xyz>Hope Ferdebest</xyz>
<CAT>English</CAT> - can not start with a number
<Duck>2020</Duck> or with the letters “XML”
</bar>
</foo> - Start tag must match end
tag, including capitalization
44

MORE COMPLEX EXAMPLE

List of all of your closest friends, including….

⋄ names(s)
⋄ age(s)
⋄ hobbies(s)
45

MORE COMPLEX EXAMPLE

List of all of your closest friends, including….

⋄ Billy
⋄ 31
DATA
⋄ Avengers
⋄ DandD
46

HOW TO MAKE AN XML DOCUMENT?

How do we turn this into an XML document?

⋄ Create a plain text file (no formatting)

⋄ Use a plain text/flat file editor (notepad++, brackets, etc.)
⋄ File must have the extension of .xml
47

HOW TO MAKE AN XML DOCUMENT?

How do we turn this into an XML document?

⋄ Create a plain text file (no formatting)

⋄ Use a plain text/flat file editor (notepad++, brackets, etc.)
⋄ File must have the extension of .xml

Notepad++ (https://notepad-plus-plus.org/)
48

HOW TO MAKE AN XML DOCUMENT?

DO THE
TAGS LAST!
49
GOAL <?xml version="1.0"?>
<FriendList>
<Friend>
<name>Billy</name>
<age>31</age>
<hobbies>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
<Friend>
Billy 31 Cosplay, Avengers, DandD <name>Idris</name>
<age>27</age>
Idris 27 Dr. Who <hobbies>
<hobby>Dr. Who</hobby>
Jordan 19 Star Wars, My Little Pony </hobbies>
</Friend>
<Friend>
<name>Jordan</name>
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
</FriendList>
50
STEP 1: BREAK IT DOWN

Billy 31 Cosplay, Avengers, DandD

Idris 27 Dr. Who
Jordan 19 Star Wars, My Little Pony
51
STEP 1: BREAK IT DOWN

Billy 31 Cosplay,Avengers, DandD

Idris 27 Dr. Who

Jordan 19 Star Wars, My Little Pony

52
STEP 1: BREAK IT DOWN
Billy
31
cosplay LOGICAL UNITS
Avengers
DandD - Have come commonality

Idris GROUPINGS!
27
Dr. Who
• One data point per line
Jordan
• Break it down into groups
19 separated by spaces
Star Wars • Keep data in group together
My Little Pony
• One piece of data on each line
STEP 2: 53

IDENTIFY
GROUPINGS Billy
31
cosplay
Avengers
DandD

Idris
27
Dr. Who

Jordan
19
Star Wars
My Little Pony
STEP 2: 54

IDENTIFY
GROUPINGS Billy
31
cosplay
Avengers
DandD

Idris
27
LOGICAL UNITS
Dr. Who
- Have come commonality
Jordan
19
Star Wars GROUPINGS!
My Little Pony
STEP 2: 55

IDENTIFY
GROUPINGS Billy
31
cosplay
Avengers
DandD

Idris
27
LOGICAL UNITS
Dr. Who
- Have come commonality
Jordan
19
Star Wars GROUPINGS!
My Little Pony
STEP 2: 56

IDENTIFY
GROUPINGS Billy
31
cosplay
Avengers
DandD

Idris
27
LOGICAL UNITS
Dr. Who
- Have come commonality
Jordan
19
Star Wars GROUPINGS!
My Little Pony
STEP 2: 57

IDENTIFY
GROUPINGS Billy
31
cosplay
Avengers
DandD

Idris
27
LOGICAL UNITS
Dr. Who
- Have come commonality
Jordan
19
Star Wars GROUPINGS!
My Little Pony
STEP 2: 58

IDENTIFY
GROUPINGS Billy
31
cosplay
Avengers
DandD

Idris
27 Give descriptive
Dr. Who
names to the
groupings
Jordan
19
Star Wars
My Little Pony
STEP 2: 59
FriendList
IDENTIFY
GROUPINGS Billy
31
cosplay
Avengers
DandD

Idris
27 Give descriptive
Dr. Who
names to the
groupings
Jordan
19
Star Wars
My Little Pony
STEP 2: 60
FriendList
IDENTIFY
GROUPINGS Billy
31
cosplay
Avengers
DandD Friend

Idris
27 Give descriptive
Dr. Who
names to the
groupings
Jordan
19 Friend
Star Wars
My Little Pony

Friend
STEP 2: 61
FriendList
IDENTIFY
GROUPINGS Billy
31 Hobbies
cosplay
Avengers
DandD Friend

Idris
27 Give descriptive
Dr. Who
Hobbies names to the
groupings
Jordan
19 Friend
Star Wars
My Little Pony

Hobbies

Friend
STEP 3: 62
FriendList
NAME THE
DATA Billy
31 Hobbies
cosplay
Avengers
DandD Friend

Idris
27
Dr. Who

Jordan
Hobbies
Give descriptive
Friend
19
Star Wars names to each
My Little Pony

Hobbies data element

Friend
STEP 3: 63
FriendList
NAME THE
DATA name
Billy
31 Hobbies
cosplay
Avengers
DandD Friend

Idris
27
Dr. Who
name
Hobbies
Jordan
Give descriptive
Friend
19
Star Wars
My Little Pony
names to each
name
Hobbies data element
Friend
STEP 3: 64
FriendList
NAME THE
DATA name
Billy
31 Hobbies
cosplay
Avengers
DandD Friend

Idris
27
Dr. Who
name

Jordan
Hobbies
Give descriptive
Friend
19
Star Wars names to each
My Little Pony
name
Hobbies data element
Friend
STEP 3: 65
FriendList
NAME THE
DATA name
Billy
31 Hobbies
age cosplay
Avengers
DandD Friend

Idris
27
Dr. Who
name
age
Jordan
Hobbies
Give descriptive
Friend
19
Star Wars names to each
My Little Pony
name
age
Hobbies data element
Friend
STEP 3: 66
FriendList
NAME THE
DATA name
Billy
31 Hobbies
age cosplay
hobby Avengers
hobby
DandD Friend
hobby
Idris
27
Dr. Who
name
age
hobby Jordan
Hobbies
Give descriptive
Friend
19
Star Wars names to each
My Little Pony
name
age
Hobbies data element
hobby
hobby Friend
STEP 3: 67
FriendList
NAME THE
DATA name
Billy
31 Hobbies
age cosplay
hobby Avengers
hobby
DandD Friend
hobby

Now we are ready to

Idris
27
Dr. Who
name
age Hobbies make an XML
hobby Jordan
19
Star Wars
Friend
document
My Little Pony
name
age
Hobbies
hobby
hobby Friend
STEP 4: 68

ADD THE XML DOCUMENT FriendList

IDENTIFIER name Billy
31 Hobbies
1st:
age cosplay
hobby
XML Document Identifier
Avengers
hobby
DandD Friend
hobby
Idris
27
Dr. Who
name
age Hobbies
hobby Jordan
19 Friend
Star Wars
My Little Pony
name
age
Hobbies
hobby
hobby Friend
STEP 4: FriendList
69

ADD THE XML DOCUMENT

<?xml version="1.0"?>
IDENTIFIER name Billy
31 Hobbies
age cosplay
hobby Avengers
hobby
DandD Friend
hobby
Idris
27
Dr. Who
name
age Hobbies
hobby Jordan
19 Friend
Star Wars
My Little Pony
name
age
Hobbies
hobby
hobby Friend
STEP 4: FriendList
70

ADD THE XML DOCUMENT

<?xml version="1.0"?>
IDENTIFIER name Billy
31 Hobbies
age cosplay
hobby Avengers
hobby
DandD Friend
hobby
Idris
Tells the computer this
is an XML document.
27
Dr. Who
name
age Hobbies
hobby Jordan
19 Friend
Star Wars
My Little Pony
Every XML file MUST
name
age
Hobbies have this as the FIRST
hobby
hobby Friend line!
STEP 5: FriendList
71

ADD TAGS <?xml version="1.0"?>

AND DATA name

Billy
31 Hobbies
age cosplay
hobby Avengers
hobby
DandD Friend
hobby
Idris
Start adding tags
(groups) and data in
27
Dr. Who
name
age Hobbies
hobby Jordan
Friend
order they appear.
19
Star Wars
My Little Pony
name
age
Hobbies
hobby
hobby Friend
STEP 5: FriendList
72

ADD TAGS <?xml version="1.0"?>

AND DATA Billy

name
age
31
cosplay
Hobbies The RULES:
hobby Avengers
DandD Friend • Everything is either a tag or
hobby
hobby data
Idris
27
• Tags are case sensitive
name
Dr. Who • Start tags MUST have a
age Hobbies
matching end tag
hobby Jordan
19 Friend • Tags can not overlap, must
Star Wars
My Little Pony have proper nesting
name
age
Hobbies • XML Documents can have
hobby one (and only one) Root
hobby Friend
Element
• Tags must obey XML
Naming Conventions
STEP 5: FriendList
73

hobby
Idris
27
Dr. Who
name
age Hobbies
hobby Jordan
19 Friend
Star Wars
My Little Pony
name
age
Hobbies
hobby
hobby Friend
STEP 5: FriendList
79

ADD TAGS <?xml version="1.0"?>

hobby
hobby Friend
STEP 5: FriendList
94

MUST
name have
Dr. Who <Friend>
age Hobbies <name>Idris</name>
a hobby
matching end
Jordan
tag <age>27</age>
<hobbies>
19 Friend <hobby>Dr. Who</hobby>
Star Wars </hobbies>
- tags can not overlap
My Little Pony </Friend>
name
- proper nesting
<Friend>
age
Hobbies <name>Jordan</name>
<age>19</age>
hobby <hobbies>
- XML Documents can
hobby Friend <hobby>Star Wars</hobby>

have one (one only one)

<hobby>My Little Pony</hobby>
</hobbies>
Root Element </Friend>
</FriendList>
103
Raw Data FriendList.xml
<?xml version="1.0"?>
Billy 31 cosplay Avengers DandD
<FriendList>
Idris 27 Dr. Who
<Friend>
Jordan 19 Star Wars My Little Pony
<name>Billy</name>
<age>31</age>
<hobbies>
<hobby>cosplay</hobby>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
<Friend>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</Friend>
<Friend>
<name>Jordan</name>
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
</FriendList>
104
GOAL FriendList
<?xml version="1.0"?>
Complete XML Document <FriendList>
<Friend>
<name>Billy</name>
<age>31</age>

… take raw data … <hobbies>

<hobby>cosplay</hobby>
<hobby>Avengers</hobby>
Billy 31 cosplay, Avengers, DandD <hobby>DandD</hobby>
Idris 27 Dr. Who </hobbies>
Jordan 19 Star Wars, My Little Pony </Friend>
…. <Friend>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</Friend>
<Friend>
<name>Jordan</name>
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
</FriendList>
105
GOAL FriendList
<?xml version="1.0"?>
Complete XML Document <FriendList>
<Friend>
<name>Billy</name>
<age>31</age>

… take raw data … <hobbies>

<hobby>cosplay</hobby>
<hobby>Avengers</hobby>
Billy 31 cosplay <hobby>DandD</hobby>
Idris 27 Dr. Who </hobbies>
Jordan 19 Star Wars </Friend>
Sharmin 28 Comics <Friend>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</Friend>
<Friend>
<name>Jordan</name>
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
… into a computer file … </FriendList>
106
GOAL FriendList
<?xml version="1.0"?>
Complete XML Document <FriendList>
<Friend>
<name>Billy</name>
<age>31</age>

… to import into
<hobbies>
<hobby>cosplay</hobby>

a database…
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
<Friend>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</Friend>
<Friend>
<name>Jordan</name>
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
… into a computer file … </FriendList>
107

REMEMBER!

DO THE
TAGS LAST!
QUICK REVIEW
108
<?xml version="1.0"?>
<FriendList>
<Friend>
<name>Billy</name> Top Level Grouping
<age>31</age>
<hobbies>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
<Friend>
<name>Idris</name> Top Level Grouping
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</Friend>
<Friend>
<name>Jordan</name> Top Level Grouping
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
</FriendList>
QUICK REVIEW
109
<?xml version="1.0"?>
<FriendList>
<Friend>
<name>Billy</name>
<age>31</age>
<hobbies>
<hobby>Avengers</hobby>
Inner Level Grouping
<hobby>DandD</hobby>
</hobbies>
</Friend>
<Friend>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby> Inner Level Grouping
</hobbies>
</Friend>
<Friend>
<name>Jordan</name>
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby> Inner Level Grouping
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
</FriendList>
QUICK REVIEW
110
<?xml version="1.0"?>
<FriendList>
<Friend>
<name>Billy</name>
<age>31</age>
<hobbies>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies> Data ‘Simple’ Groupings
</Friend>
<Friend>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</Friend>
<Friend>
<name>Jordan</name>
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
</FriendList>
111

QUICK REVIEW

<?xml version="1.0"?>

<FriendList> Pre-processor command

<name>Billy</name>
<age>31</age>

<hobbies>
<hobby>cosplay</hobby>
<hobby>D and D</hobby>
</hobbies>

</Friend>

</FriendList>
112

QUICK REVIEW

<?xml version="1.0"?>

<name>Billy</name>
<age>31</age>

<hobbies>
<hobby>cosplay</hobby>
<hobby>D and D</hobby>
</hobbies>

</Friend>

</FriendList>
113

QUICK REVIEW

<?xml version="1.0"?>

<FriendList>
Top Level Grouping
<Friend> … and end tag for grouping

<name>Billy</name>
<age>31</age>

<hobbies>
<hobby>cosplay</hobby>
<hobby>D and D</hobby>
</hobbies>

</Friend>

</FriendList>
114

QUICK REVIEW

<?xml version="1.0"?>

<FriendList> Inner Level Grouping

… and end tag for grouping
<Friend>

<name>Billy</name>
<age>31</age>

<hobbies>
<hobby>cosplay</hobby>
<hobby>D and D</hobby>
</hobbies>

</Friend>

</FriendList>
115

QUICK REVIEW

<?xml version="1.0"?>

<FriendList> Data ‘Simple’ Groupings

<name>Billy</name>
<age>31</age>

<hobbies>
<hobby>cosplay</hobby>
<hobby>D and D</hobby>
</hobbies>

</Friend>

</FriendList>
116

QUICK REVIEW
Pre-processor command
<?xml version="1.0"?>

<FriendList> Root

<name>Billy</name> Data ‘Simple’ Groupings

<hobbies>
<hobby>cosplay</hobby> Inner Level Grouping
<hobby>D and D</hobby>
</hobbies>

</Friend> Top Level Grouping

</FriendList>
XML ELEMENTS
117
<?xml version="1.0"?>
<FriendList>
<Friend> Every Start Tag - End Tag combination
<name>Billy</name> is known as an
<age>31</age> ELEMENT
<hobbies> in an XML Document
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
<Friend>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</Friend>
<Friend>
<name>Jordan</name>
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
</FriendList>
XML ELEMENTS
118
<?xml version="1.0"?>
<FriendList>
<Friend> Every Start Tag - End Tag combination
<name>Billy</name> is known as an
<age>31</age> ELEMENT
<hobbies> in an XML Document
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
<Friend>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</Friend>
<Friend> Hint:
<name>Jordan</name> How many elements are in this XML Document ?
i.e. How many unique start tags can you count?
<age>19</age>
<hobbies>
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
</FriendList>
XML ELEMENTS
119
<?xml version="1.0"?>
<FriendList>
<Friend> Every Start Tag - End Tag combination
<name>Billy</name> is known as an
<age>31</age> ELEMENT
<hobbies> in an XML Document
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
<Friend>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</Friend>
<Friend> Hint:
<name>Jordan</name> How many elements are in this XML Document ?
i.e. How many unique start tags can you count?
<age>19</age>
<hobbies>

6
<hobby>Star Wars</hobby>
<hobby>My Little Pony</hobby>
</hobbies>
</Friend>
</FriendList>
120

TAG ATTRIBUTES
<Friend>
Billy <name>Billy</name>
31 <age>31</age>
cosplay <hobbies>
Avengers <hobby>cosplay</hobby>
DandD <hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
121

TAG ATTRIBUTES
(information about the TAG and NOT about the DATA)

<Friend Order = “1”>

Billy <name>Billy</name>
31 <age>31</age>
cosplay <hobbies>
Avengers <hobby>cosplay</hobby>
DandD <hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>

<Friend GroupType = “human”>

Billy <name>Billy</name>
31 <age>31</age>
cosplay <hobbies>
Avengers <hobby>cosplay</hobby>
DandD <hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
122

TAG ATTRIBUTES
(information about the TAG and NOT about the DATA)

<Friend Order = “1”> {correct}

Billy <name>Billy</name>
31 <age>31</age>
cosplay <hobbies>
Avengers <hobby>cosplay</hobby>
DandD <hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>

<Friend GroupType = “human”> {correct}

Billy <name>Billy</name>
31 <age>31</age>
cosplay <hobbies>
Avengers <hobby>cosplay</hobby>
DandD <hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
123

TAG ATTRIBUTES
(information about the TAG and NOT about the DATA)

<Friend gender = “Male”>

Billy <name>Billy</name>
31 <age>31</age>
cosplay <hobbies>
Avengers <hobby>cosplay</hobby>
DandD <hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>

<Friend>
Billy <name>Billy</name>
31 <age>31</age>
cosplay <gender>Male</gender>
Avengers </hobbies>
DandD <hobby>cosplay</hobby>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
124

TAG ATTRIBUTES
(information about the TAG and NOT about the DATA)

<Friend gender = “Male”> {WRONG!}

Billy <name>Billy</name>
31 <age>31</age>
cosplay <hobbies>
Avengers <hobby>cosplay</hobby>
DandD <hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>

<Friend>
Billy <name>Billy</name>
31 <age>31</age>
cosplay <gender>Male</gender> {correct}
Avengers </hobbies>
DandD <hobby>cosplay</hobby>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
125

ELEMENT COMPONENTS
<city id = “nyc”> New York City </city>
126

ELEMENT COMPONENTS
<city id = “nyc”> New York City </city>

| start tag |
127

ELEMENT COMPONENTS
<city id = “nyc”> New York City </city>
|tag |
|name|

| start tag |
128

| start tag |
129

ELEMENT COMPONENTS
<city id = “nyc”> New York City </city>

|end tag|
130

ELEMENT COMPONENTS
<city id = “nyc”> New York City </city>
|terminator|

|end tag|
131

ELEMENT COMPONENTS
<city id = “nyc”> New York City </city>

| content |
|-data-|
132

ELEMENT COMPONENTS
<city id = “nyc”> <town>York</town> </city>

| content |
|-data-|

- OR -

|- other elements - |
133

ELEMENT COMPONENTS
<city id = “nyc”>
<town>York</town>
</city>
| content |
|-data-|

- OR -

|- other elements- |

Either way - data (simple) or components (complex)

- ‘city’ is still the name of the element
134

ELEMENT COMPONENTS
Empty Elements
<city></city>
| NO content |
|- NO data-|

NOTICE - NO SPACE - {a space is data…}

135

ELEMENT COMPONENTS
Empty Elements
<city></city> - NOTHING between the ‘start’ tag and the ‘end’ tag

| NO content |
|- NO data-|

NOTICE - NO SPACE - {a space is data…}

Alternate – Empty Elements

<city/>
NOTICE – single tag – self terminator AFTER tag name
136

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

XML tag names are case sensitive: <TAG> <Tag> and <tag> are all different

XML Name may NOT begin with a number: <1Tag> is NOT allowed

XML Name may otherwise contain numbers: <Tag1> IS allowed

XML Names MAY contain underscore, hyphens and period characters:

<Tag_Name> <Tag-Name> and <Tag.Name> are allowed

XML Names may NOT contain any other punctuation characters: <Tag%> NO

XML Names can NOT have whitespace: <Tag Name> is NOT allowed

XML Name may NOT begin with XML in any case: <XMLTag> <xmlTag> NO
137

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

XML tag names are case sensitive: <TAG> <Tag> and <tag> are all different

XML Name may NOT begin with a number: <1Tag> is NOT allowed

XML Name may otherwise contain numbers: <Tag1> IS allowed

XML Names MAY contain underscore, hyphens and period characters:

<Tag_Name> <Tag-Name> and <Tag.Name> are allowed

XML Names may NOT contain any other punctuation characters: <Tag%> NO

XML Names can NOT have whitespace: <Tag Name> is NOT allowed

XML Name may NOT begin with XML in any case: <XMLTag> <xmlTag> NO
138

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

XML tag names are case sensitive: <TAG> <Tag> and <tag> are all different

XML Name may NOT begin with a number: <1Tag> is NOT allowed

XML Name may otherwise contain numbers: <Tag1> IS allowed

XML Names MAY contain underscore, hyphens and period characters:

<Tag_Name> <Tag-Name> and <Tag.Name> are allowed

XML Names may NOT contain any other punctuation characters: <Tag%> NO

XML Names can NOT have whitespace: <Tag Name> is NOT allowed

XML Name may NOT begin with XML in any case: <XMLTag> <xmlTag> NO
139

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

XML tag names are case sensitive: <TAG> <Tag> and <tag> are all different

XML Name may NOT begin with a number: <1Tag> is NOT allowed

XML Name may otherwise contain numbers: <Tag1> IS allowed

XML Names MAY contain underscore, hyphens and period characters:

<Tag_Name> <Tag-Name> and <Tag.Name> are allowed

XML Names may NOT contain any other punctuation characters: <Tag%> NO

XML Names can NOT have whitespace: <Tag Name> is NOT allowed

XML Name may NOT begin with XML in any case: <XMLTag> <xmlTag> NO
140

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

XML tag names are case sensitive: <TAG> <Tag> and <tag> are all different

XML Name may NOT begin with a number: <1Tag> is NOT allowed

XML Name may otherwise contain numbers: <Tag1> IS allowed

XML Names MAY contain underscore, hyphens and period characters:

<Tag_Name> <Tag-Name> and <Tag.Name> are allowed

XML Names may NOT contain any other punctuation characters: <Tag%> NO

XML Names can NOT have whitespace: <Tag Name> is NOT allowed

XML Name may NOT begin with XML in any case: <XMLTag> <xmlTag> NO
141

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

XML tag names are case sensitive: <TAG> <Tag> and <tag> are all different

XML Name may NOT begin with a number: <1Tag> is NOT allowed

XML Name may otherwise contain numbers: <Tag1> IS allowed

XML Names MAY contain underscore, hyphens and period characters:

<Tag_Name> <Tag-Name> and <Tag.Name> are allowed

XML Names may NOT contain any other punctuation characters: <Tag%> NO

XML Names can NOT have whitespace: <Tag Name> is NOT allowed

XML Name may NOT begin with XML in any case: <XMLTag> <xmlTag> NO
142

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

XML tag names are case sensitive: <TAG> <Tag> and <tag> are all different

XML Name may NOT begin with a number: <1Tag> is NOT allowed

XML Name may otherwise contain numbers: <Tag1> IS allowed

XML Names MAY contain underscore, hyphens and period characters:

<Tag_Name> <Tag-Name> and <Tag.Name> are allowed

XML Names may NOT contain any other punctuation characters: <Tag%> NO

XML Names can NOT have whitespace: <Tag Name> is NOT allowed

XML Name may NOT begin with XML in any case: <XMLTag> <xmlTag> NO
143

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

Whitespace IS preserved in XML Content (data):

<sData>This is a paragraph. It has a whole whack

of spaces.</sData>

Will be processed as:

This is a paragraph. It has a whole whack

of spaces.
144

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

Whitespace IS preserved in XML Content (data):

<sData>This is a paragraph. It has a whole whack

of spaces.</sData>

Will be processed as:

This is a paragraph. It has a whole whack

of spaces.
145

ELEMENT COMPONENTS
More Rules
<city id = “nyc”> New York City </city>

Whitespace IS preserved in XML Content (data):

<sData>This is a paragraph. It has a whole whack

of spaces.</sData>

Will be processed as:

This is a paragraph. It has a whole whack

of spaces.
146

ELEMENT COMPONENTS
More Rules
<compare>6 <7 & 7> 6 ‘natch’</compare>

Escaping Characters NOT allowed:

- entity reverences are used instead

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

< - the <(less than) character
> - the> (greater than) character
' - the ‘ (apostrophe – single quote) character
" - the “ (double quote) character
147

ELEMENT COMPONENTS
More Rules
<compare>6
W R <7 O &N
7> 6G‘natch’</compare>
! ! ! ! !
Escaping Characters NOT allowed:

- entity reverences are used instead

<compare>6 &lt 7 &amp 7 &gt 6 &aposnatch&apos</compare>

&amp – the & (ampersand) character

&lt - the <(less than) character
&gt - the> (greater than) character
&apos - the ‘ (apostrophe – single quote) character
&quot - the “ (double quote) character
148

ELEMENT COMPONENTS
More Rules
<compare>6 <7 & 7> 6 ‘natch’</compare>

Escaping Characters NOT allowed:

- entity reverences are used instead

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

< - the <(less than) character
> - the> (greater than) character
' - the ‘ (apostrophe – single quote) character
" - the “ (double quote) character
149

ELEMENT COMPONENTS
More Rules
<compare>6 <7 & 7> 6 ‘natch’</compare>

Escaping Characters NOT allowed:

- entity reverences are used instead

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

< - the <(less than) character
> - the> (greater than) character
' - the ‘ (apostrophe – single quote) character
" - the “ (double quote) character
150

ELEMENT COMPONENTS
More Rules
<compare>6 <7 & 7> 6 ‘natch’</compare>

Escaping Characters NOT allowed:

- entity reverences are used instead

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

< - the <(less than) character
> - the> (greater than) character
' - the ‘ (apostrophe – single quote) character
" - the “ (double quote) character
151

ELEMENT COMPONENTS
More Rules
<compare>6 <7 & 7> 6 ‘natch’</compare>

Escaping Characters NOT allowed:

- entity reverences are used instead

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

< - the <(less than) character
> - the> (greater than) character
' - the ‘ (apostrophe – single quote) character
" - the “ (double quote) character
152

ELEMENT COMPONENTS
More Rules
<compare>6 <7 & 7> 6 ‘natch’</compare>

Escaping Characters NOT allowed:

- entity reverences are used instead

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

< - the <(less than) character
> - the> (greater than) character
' - the ‘ (apostrophe – single quote) character
" - the “ (double quote) character
153

ELEMENT COMPONENTS
More Rules
<compare>6 <7 & 7> 6 ‘natch’</compare>

Escaping Characters NOT allowed:

- entity reverences are used instead

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

< - the <(less than) character
> - the> (greater than) character
' - the ‘ (apostrophe – single quote) character
" - the “ (double quote) character
154

ELEMENT ATTRIBUTES
More Rules
<city id = “nyc”> New York City </city>

XML Attributes Values MUST be enclosed with quotes:

- single or double : BUT must match !

“nyc” or ‘nyc’ NOT “nyc’ or ‘nyc”

- can imbed:

“This is Michael’s Bicycle”

‘I can “air quote” for real’

155

ELEMENT ATTRIBUTES
More Rules
<city id = “nyc”> New York City </city>

ALL XML Attributes Values MUST be enclosed with quotes:

- single or double : BUT must match !

“nyc” or ‘nyc’ NOT “nyc’ or ‘nyc”

- can imbed:

“This is Michael’s Bicycle”

‘I can “air quote” for real’

156

ELEMENT ATTRIBUTES
More Rules
<city id = “nyc”> New York City </city>

XML Attributes Values MUST be enclosed with quotes:

- single or double : BUT must match !

“nyc” or ‘nyc’ NOT “nyc’ or ‘nyc”

- can imbed different quotes:

“This is Michael’s Bicycle”

‘I can “air quote” for real’

157

ELEMENT ATTRIBUTES
More Rules
<city id = “nyc”> New York City </city>

XML Attributes can NOT have the same name inside a tag:
158

ELEMENT ATTRIBUTES
More Rules
<city id = “nyc”> New York City </city>

XML Attributes can NOT have the same name inside a tag:

<city id = “1” id = “nyc”>New York City</city> {WRONG!}

159

ELEMENT ATTRIBUTES
More Rules
<city id = “nyc”> New York City </city>

XML Attributes can NOT have the same name inside a tag:

<city id = “1” id = “nyc”>New York City</city> {WRONG!}

<city id = “1”>New York City</city>

<city id = “2”>Chicago</city> {RIGHT!}
160

ELEMENT ATTRIBUTES
More Rules
<city id = “nyc”> New York City </city>

XML Attributes can NOT have the same name inside a tag:

<city id = “1” id = “nyc”> New York City </city> {WRONG!}

<city id = “1”>New York City</city>

<city id = “2”>Chicago</city> {RIGHT!}

XML Attributes can NOT be in the end tag:

<city> New York City </city id = “nyc”> {WRONG!}

161

COMMENTS

Comments are allowed in XML

XML Comments are exactly the same as HTML Comments

Can appear anywhere in the XML Document

- ignored by the computer (XML Processors)
<Friend> 
<name>Billy</name>
<age>31</age>

<hobby>cosplay</hobby>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</Friend>
162

COMMENTS

Comments are allowed in XML

XML Comments are exactly the same as HTML Comments

Can appear anywhere in the XML Document

- ignored by the computer (XML Processors)
<Friend> 
<name>Billy</name>
<age>31</age>

<hobbies>
<hobby>cosplay</hobby>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</Friend>
163

COMMENTS

Comments are allowed in XML

XML Comments are exactly the same as HTML Comments

Can appear anywhere in the XML Document

COMMENTS

Comments are allowed in XML

XML Comments are exactly the same as HTML Comments

Can appear anywhere in the XML Document

XML - EXTENSIBLE MARKUP LANGUAGE

Why is it an EXTENSIBLE markup language
Is user defined
Is extensible (can be easily expanded)

<Friend>
<name>Joe Bloggs</name>
<age>25</age>
</Friend>
Can be easily changed (expanded) to

<Friend>
<name>Joe Bloggs</name>
<age>25</age>
<job>Student</job>
<address>123 Fake St.</address>
<courses>
<course>CS1032</course>
<course>CS2034</course>
</courses>
</Friend>
166

XML - EXTENSIBLE MARKUP LANGUAGE

Why is it an EXTENSIBLE markup language
Is user defined
Is extensible (can be easily expanded)

<Friend>
<name>Joe Bloggs</name>
<age>25</age>
</Friend>
Can be easily changed (expanded) to

<Friend>
<name>Joe Bloggs</name>
<age>25</age>
<job>Student</job>
<address>123 Fake St.</address>
<courses>
<course>CS1032</course>
<course>CS2034</course>
</courses>
</Friend>
167

XML - EXTENSIBLE MARKUP LANGUAGE

Why is it an EXTENSIBLE markup language
Is user defined
Is extensible (can be easily expanded)

<Friend>
<name>Joe Bloggs</name>
<age>25</age>
</Friend>
Can be easily changed (expanded) to

<Friend>
<name>Joe Bloggs</name>
<age>25</age>
<job>Student</job>
<address>123 Fake St.</address>
<courses>
<course>CS1032</course>
<course>CS2034</course>
</courses>
</Friend>
168

XML - EXTENSIBLE MARKUP LANGUAGE

Why is it an EXTENSIBLE markup language
Is user defined
Is extensible (can be easily expanded)

<Friend>
<name>Joe Bloggs</name>
<age>25</age> In most cases the computer
</Friend> will ignore the extra tags (if it
Can be easily changed (expanded) to has not yet been programed
<Friend> to understand them).
<name>Joe Bloggs</name>
<age>25</age>
<job>Student</job> Backwards combability.
<address>123 Fake St.</address>
<courses>
<course>CS1032</course>
<course>CS2034</course>
</courses>
</Friend>
169

XML - EXTENSIBLE MARKUP LANGUAGE

Quick Definitions ….
- Elements : Complex versus Simple Elements

<Friend>
<name>Billy Bob Hillbilly</name>
<age>31</age>
</Friend>

<Friend>
<name>
<first>Billy</first>
<middle>Bob</middle>
<last>Hillbilly</last>
</name>
<age>31</age>
</Friend>
170

XML - EXTENSIBLE MARKUP LANGUAGE

Quick Definitions ….
- Elements : Complex versus Simple Elements

<Friend>
<name>Billy Bob Hillbilly</name>
<age>31</age>
</Friend>

<Friend>
<name>
<first>Billy</first>
<middle>Bob</middle>
<last>Hillbilly</last>
</name>
<age>31</age>
</Friend>
171

XML - EXTENSIBLE MARKUP LANGUAGE

Quick Definitions ….
- Elements : Complex versus Simple Elements

<Friend>

<name>Billy Bob Hillbilly</name> 
<age>31</age> 
</Friend>

<Friend>
<name>
<first>Billy</first>
<middle>Bob</middle>
<last>Hillbilly</last>
</name>
<age>31</age>
</Friend>
172

XML - EXTENSIBLE MARKUP LANGUAGE

Quick Definitions ….
- Elements : Complex versus Simple Elements

<Friend>

<name>Billy Bob Hillbilly</name> 
<age>31</age> 
</Friend>

<Friend>

<name> 
<first>Billy</first> 
<middle>Bob</middle> 
<last>Hillbilly</last> 
</name>
<age>31</age> 
</Friend>
173

XML NAMESPACE

Processing XM Documents:

- may have to combine two or more documents into a single work unit

- remember the rule: tag names must be unique

- how to ensure Doc1 never uses the same tag as Doc2 ???
XML NAMESPACE
174

Conflict Example:
File1.xml: File2.xml:
<?xml version="1.0"?> <?xml version="1.0"?>
<Friends> <Worker>
<person> <person>
<name>Billy</name> <name>
<age>31</age> <first>Frazer</first>
<hobbies> <last>Fur</last>
<hobby>cosplay</hobby> </name>
<hobby>Avengers</hobby> <age>31</age>
<hobby>DandD</hobby> <schedule>
</hobbies> <day>Tuesday</day>
</person> <day>Thursday</day>
</schedule>
<person> </person>
<name>Idris</name> </Worker>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</person>
</Friends>
XML NAMESPACE 175
Combined XML Documents in One File - fCombined.xml
<?xml version="1.0"?> <!– File1.xml →
<Friends>
<person>
<name>Billy</name>
<age>31</age>
<hobbies>
<hobby>cosplay</hobby>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</person>
<person>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</person>
</Friends>

<Worker> <!– File2.xml →

<person>
<name>
<first>Frazer</first>
<last>Fur</last>
</name>
<age>31</age>
<schedule>
<day>Tuesday</day>
<day>Thursday</day>
</schedule>
</person>
</n2:Worker>
XML NAMESPACE
176

Conflict Example:
File1.xml: File2.xml:
<?xml version="1.0"?> <?xml version="1.0"?>
<Friends> <Worker>
<person> <person>
<name>Billy</name> <name>
<age>31</age> <first>Frazer</first>
<hobbies> <last>Fur</last>
<hobby>cosplay</hobby> </name>
<hobby>Avengers</hobby> <age>31</age>
<hobby>DandD</hobby> <schedule>
</hobbies> <day>Tuesday</day>
</person> <day>Thursday</day>
</schedule>
<person> </person>
<name>Idris</name> </Worker>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</person>
</Friends>
XML NAMESPACE 177
Combined XML Documents in One File - fCombined.xml
<?xml version="1.0"?> <!– File1.xml →
<Friends>
<person>
<name>Billy</name>
<age>31</age>
<hobbies>
<hobby>cosplay</hobby>
<hobby>Avengers</hobby>
<hobby>DandD</hobby>
</hobbies>
</person>
<person>
<name>Idris</name>
<age>27</age>
<hobbies>
<hobby>Dr. Who</hobby>
</hobbies>
</person>
</Friends>

<Worker> <!– File2.xml →

<person>
<name>
<first>Frazer</first>
<last>Fur</last>
</name>
<age>31</age>
<schedule>
<day>Tuesday</day>
<day>Thursday</day>
</schedule>
</person>
</n2:Worker>
XML NAMESPACE
178

Conflict Resolution: (how to solve the problem)

- give each document a Namespace.

- fancy way of just saying ‘associate a last name with each document’
- give each a document a ‘last name’ and treat the tag as a ‘first name’

David Smith,David Jones, David Bond, David

Jordan Jones, Jordan Whales, Jordan
Yue Jones, Yue Bond, Yue Xi, Yue
Matthew Smith, Matthew
Cameron Bond, Cameron Maggs, Cameron
Sam Maggs, Sam Jones, Sam
XML NAMESPACE
179

Conflict Resolution: (how to solve the problem)

- give each document a Namespace.

- fancy way of just saying ‘associate a last name with each document’
- give each a document a ‘last name’ and treat the tag as a ‘first name’

David Smith,David Jones, David Bond, David

Jordan Jones, Jordan Whales, Jordan
Yue Jones, Yue Bond, Yue Xi, Yue
Matthew Smith, Matthew
Cameron Bond, Cameron Maggs, Cameron
Sam Maggs, Sam Jones, Sam
XML NAMESPACE
180

Conflict Resolution: (how to solve the problem)

- BUT !!!!

- how to ensure the ‘Last Name’ is unique

XML NAMESPACE
181

Conflict Resolution: (how to solve the problem)

- BUT !!!!

- how to ensure the ‘Last Name’ is unique

Declare a Namespace in XML:

Change Root tag:

To:

<ns1:Friends xmlns:ns1=“http://cs1.ca/cs1032.html">
XML NAMESPACE
182

Conflict Resolution: (how to solve the problem)

- BUT !!!!

- how to ensure the ‘Last Name’ is unique

Declare a Namespace in XML:

Change Root tag:

<Friends> NamespaceURI
Namespace Uniform Resource Identifier
To: root ( usually a URL )

<ns1:Friends xmlns:ns1="http://cs1.ca/cs1032.html">

Namespace Identifier character sequence for namespace

XML NAMESPACE
183

Declare a Namespace in XML: - File1.xml

<ns1:group xmlns:ns1="http://cs1.ca/friends">
<?xml version="1.0"?> <?xml version="1.0"?>
<Friends> <ns1:Friends xmlns:ns1="http://cs1.ca/friends">
<person> <ns1:person>
<name>Billy</name> <ns1:name>Billy</ns1:name>
<age>31</age> <ns1:age>31</ns1:age>
<hobbies> <ns1:hobbies>
<hobby>cosplay</hobby> <ns1:hobby>cosplay</ns1:hobby>
<hobby>Avengers</hobby> <ns1:hobby>Avengers</ns1:hobby>
<hobby>DandD</hobby> <ns1:hobby>DandD</ns1:hobby>
</hobbies> </ns1:hobbies>
</person> </ns1:person>

<person> <ns1:person>
<name>Idris</name> <ns1:name>Idris</ns1:name>
<age>27</age> <ns1:age>27</ns1:age>
<hobbies> <ns1:hobbies>
<hobby>Dr. Who</hobby> <ns1:hobby>Dr. Who</ns1:hobby>
</hobbies> </ns1:hobbies>
</person> </ns1:person>
</Friends> </ns1:Friends>
XML NAMESPACE
184

Declare a Namespace in XML: - File1.xml

Declare a Namespace in XML: - File2.xml

<ns2:group xmlns:ns2=“http://cs1.ca/workers">

<?xml version="1.0"?>
<?xml version="1.0"?>
<ns2:Worker xmlns:ns2="http://cs1.ca/workers">
<Worker>
<ns2:person>
<person>
<ns2:name>
<name>
<ns2:first>Frazer</ns2:first>
<first>Frazer</first>
<ns2:last>Fur</ns2:last>
<last>Fur</last>
</ns2:name>
</name>
<ns2:age>31</ns2:age>
<age>31</age>
<ns2:schedule>
<schedule>
<ns2:day>Tuesday</ns2:day>
<day>Tuesday</day>
<ns2:day>Thursday</ns2:day>
<day>Thursday</day>
</ns2:schedule>
</schedule>
</ns2:person>
</person>
</n2:Worker>
</Worker>
XML NAMESPACE
186

Declare a Namespace in XML: - File2.xml

<ns2:group xmlns:ns2=“http://cs1.ca/workers">

<ns2:Worker xmlns:ns2="http://cs1.ca/workers">
<ns2:person>
<ns2:name>
<ns2:first>Frazer</ns2:first>
<ns2:last>Fur</ns2:last>
</ns2:name>
<ns2:age>31</ns2:age>
<ns2:schedule>
<ns2:day>Tuesday</ns2:day>
<ns2:day>Thursday</ns2:day>
</ns2:schedule>
</ns2:person>
</n2:Worker>
XML NAMESPACE
Combined XML Documents (Files) - fCombined.xml
188

<?xml version="1.0"?>
<ns1:Friends xmlns:ns1="http://cs1.ca/friends">
<ns1:person>
<ns1:name>Billy</ns1:name>
<ns1:age>31</ns1:age>
<ns1:hobbies>
<ns1:hobby>cosplay</ns1:hobby>
<ns1:hobby>Avengers</ns1:hobby>
<ns1:hobby>DandD</ns1:hobby>
</ns1:hobbies>
</ns1:person>
<ns1:person>
<ns1:name>Idris</ns1:name>
<ns1:age>27</ns1:age> Still have an issue.
<ns1:hobbies>
<ns1:hobby>Dr. Who</ns1:hobby>
</ns1:hobbies>
</ns1:person> XML rules say we can
</ns1:Friends>
only have one root
<ns2:Worker xmlns:ns2="http://cs1.ca/workers">
<ns2:person> element!
<ns2:name>
<ns2:first>Frazer</ns2:first>
<ns2:last>Fur</ns2:last>
</ns2:name>
<ns2:age>31</ns2:age>
<ns2:schedule>
<ns2:day>Tuesday</ns2:day>
<ns2:day>Thursday</ns2:day>
</ns2:schedule>
</ns2:person>
</n2:Worker>
XML NAMESPACE
189

Combined XML Documents (Files) - fCombined.xml

Add new root element

<?xml version="1.0"?>
<newRoot>
<ns1:Friends xmlns:ns1="http://cs1.ca/friends">
<ns1:person>
<ns1:name>Billy</ns1:name>
(could have any valid label)
<ns1:age>31</ns1:age>
<ns1:hobbies>
<ns1:hobby>cosplay</ns1:hobby>
<ns1:hobby>Avengers</ns1:hobby>
<ns1:hobby>DandD</ns1:hobby>
</ns1:hobbies>
</ns1:person>
<ns1:person>
<ns1:name>Idris</ns1:name>
<ns1:age>27</ns1:age>
<ns1:hobbies>
<ns1:hobby>Dr. Who</ns1:hobby>
</ns1:hobbies>
</ns1:person>
</ns1:Friends>
<ns2:Worker xmlns:ns2="http://cs1.ca/workers">
<ns2:person>
<ns2:name>
<ns2:first>Frazer</ns2:first>
<ns2:last>Fur</ns2:last>
</ns2:name>
<ns2:age>31</ns2:age>
<ns2:schedule>
<ns2:day>Tuesday</ns2:day>
<ns2:day>Thursday</ns2:day>
</ns2:schedule>
</ns2:person>
</n2:Worker>
</newRoot>
XML NAMESPACE
190

Conflict Resolution: (how to solve the problem)

- BUT !!!!

- Why a web site?????

<ns1:Friends xmlns:ns1=“foobar">

<ns2:Worker xmlns:ns2=“qewrtyuiop">

What happens of the other developer is also uses foobar or mashes the first row of their keyboard?

Using a different web space guarantees uniqueness …

<ns1:Friends xmlns:ns1="http://cs1.ca/cs1032.html">
XML NAMESPACE
191

Conflict Resolution: (how to solve the problem)

- BUT !!!!

- Why a web site?????

<ns1:Friends xmlns:ns1=“foobar">

<ns2:Worker xmlns:ns2=“qewrtyuiop">

What happens of the other developer is also uses foobar or mashes the first row of their keyboard?

Using a different web space guarantees uniqueness …

<ns1:Friends xmlns:ns1="http://cs1.ca/cs1032.html">
XML NAMESPACE
192

Conflict Resolution: (how to solve the problem)

- BUT !!!!

- Why a web site?????

<ns1:Friends xmlns:ns1=“foobar">

<ns2:Worker xmlns:ns2=“qewrtyuiop">

What happens of the other developer is also uses foobar or mashes the first row of their keyboard?

Using a different web space guarantees uniqueness …

<ns1:Friends xmlns:ns1="http://cs1.ca/cs1032.html">
XML NAMESPACE
193

Conflict Resolution: (how to solve the problem)

- BUT !!!!

- Why a web site?????

<ns1:Friends xmlns:ns1=“foobar">

<ns2:Worker xmlns:ns2=“qewrtyuiop">

What happens of the other developer is also uses foobar or mashes the first row of their keyboard?

Using a different web space guarantees uniqueness …

<ns1:Friends xmlns:ns1="http://cs1.ca/cs1032.html">
XML NAMESPACE
194

Conflict Resolution: (how to solve the problem)

- BUT !!!!

- Why a web site?????

<ns1:Friends xmlns:ns1=“foobar">

<ns2:Worker xmlns:ns2=“qewrtyuiop">

What happens of the other developer is also uses foobar or mashes the first row of their keyboard?

Using a different web space guarantees uniqueness …

<ns1:Friends xmlns:ns1="http://cs1.ca/cs1032.html">
XML NAMESPACE
195

Conflict Resolution: (how to solve the problem)

- BUT !!!!

- Why a web site?????

<ns1:Friends xmlns:ns1=“foobar">

<ns2:Worker xmlns:ns2=“qewrtyuiop">

What happens of the other developer is also uses foobar or mashes the first row of their keyboard?

Using a different web space guarantees uniqueness …

Note: Some Namespaces are set
<ns1:Friends xmlns:ns1="http://cs1.ca/cs1032.html"> aside for consistency (see XSDs)
XML NAMESPACE
196

Namespace:
ONLY ONLY ONLY ONLY ONLY ONLY USED …..
XML NAMESPACE
197

Namespace:
ONLY ONLY ONLY ONLY ONLY ONLY USED …..
- 1.) when combing two or more XML documents into a SINGLE
computer file.
XML NAMESPACE
198

Namespace:
ONLY ONLY ONLY ONLY ONLY ONLY USED …..
- 1.) when combing two or more XML documents into a SINGLE
computer file.
- then you MUST use a namespace to differentiate !
XML NAMESPACE
199

Namespace:
ONLY ONLY ONLY ONLY ONLY ONLY USED …..
- 1.) when combing two or more XML documents into a SINGLE
computer file.
- then you MUST use a namespace to differentiate !
- 2.) in an XML Schema
- you ALWAYS use namespace in a schema
(… explanation when we cover Schemas )
XML NAMESPACE
200

XML DOCUMENTS
Scenario:

I need you to send me data in an XML Document (file) so I can import it

into my database.

question 1.) how do I tell you exactly:

- what data I need
- the format of each data item (text, integer, date, etc.)
- the structure of the data (tables)
- the names, usage and position of the tags in the XML (fields)

question 2.) how do I verify your XML is correct:

- well formed
- valid

SOLUTION: XML Schema Document

- ‘blueprint’ of the required XML Data Document
202

XML DOCUMENTS
Scenario:

I need you to send me data in an XML Document (file) so I can import it

into my database.

question 1.) how do I tell you exactly:

- what data I need
- the format of each data item (text, integer, date, etc.)
- the structure of the data (tables)
- the names, usage and position of the tags in the XML (fields)

question 2.) how do I verify your XML is correct:

- well formed
- valid

SOLUTION: XML Schema Document

- ‘blueprint’ of the required XML Data Document

Introduction To XML For Beginners Tutorial
No ratings yet
Introduction To XML For Beginners Tutorial
26 pages
WT Unit 2
No ratings yet
WT Unit 2
20 pages
XML Chap8 Sebesta Web2
No ratings yet
XML Chap8 Sebesta Web2
52 pages
Unit 2 - XML
No ratings yet
Unit 2 - XML
48 pages
Unit 3 - XML
No ratings yet
Unit 3 - XML
44 pages
Introduction To XML
100% (1)
Introduction To XML
35 pages
Extensible Markup Language
No ratings yet
Extensible Markup Language
108 pages
UNIT4pptx 2023 10 27 08 58 28
No ratings yet
UNIT4pptx 2023 10 27 08 58 28
108 pages
Unit 3 - XML
No ratings yet
Unit 3 - XML
44 pages
Sgmlandxml 200806091332
No ratings yet
Sgmlandxml 200806091332
12 pages
Unit-3 The Client Tier
No ratings yet
Unit-3 The Client Tier
57 pages
4020 Week 3
No ratings yet
4020 Week 3
75 pages
Module 2 PDF
No ratings yet
Module 2 PDF
25 pages
XML 2
No ratings yet
XML 2
38 pages
Teacher: CSC 330 E-Commerce
No ratings yet
Teacher: CSC 330 E-Commerce
49 pages
Automation - ch05
No ratings yet
Automation - ch05
35 pages
UNIT 1 Introduction To XML: 1 Prepare By: Dr. A. GNANASEKAR ASP/CSE R.M.D. Engineering College
No ratings yet
UNIT 1 Introduction To XML: 1 Prepare By: Dr. A. GNANASEKAR ASP/CSE R.M.D. Engineering College
28 pages
Chapter 6 XML
No ratings yet
Chapter 6 XML
7 pages
XML Extensible Markup Language
No ratings yet
XML Extensible Markup Language
27 pages
Extensible Markup Language
No ratings yet
Extensible Markup Language
29 pages
XML For Dummies
No ratings yet
XML For Dummies
34 pages
Extensible Markup Language
100% (1)
Extensible Markup Language
89 pages
XML and Applications
No ratings yet
XML and Applications
39 pages
CACS 205: Web Technology XML: Prepared by Krishna Pd. Acharya (Mechi Multiple Campus)
No ratings yet
CACS 205: Web Technology XML: Prepared by Krishna Pd. Acharya (Mechi Multiple Campus)
67 pages
Module 5 XML Notes
No ratings yet
Module 5 XML Notes
36 pages
Unit 3
No ratings yet
Unit 3
50 pages
Unit - 4 XML
No ratings yet
Unit - 4 XML
82 pages
1 - XML 2020 Lab.01 - XML Standard (v3.0) 3
No ratings yet
1 - XML 2020 Lab.01 - XML Standard (v3.0) 3
4 pages
Extensible Markup Language (XML)
No ratings yet
Extensible Markup Language (XML)
20 pages
Itec102 - Midreviewer
No ratings yet
Itec102 - Midreviewer
1 page
CS8651-Internet Programming Department of CSE 2022-2023
No ratings yet
CS8651-Internet Programming Department of CSE 2022-2023
30 pages
Chapter 4
No ratings yet
Chapter 4
22 pages
XML Intro
No ratings yet
XML Intro
37 pages
Exemel
No ratings yet
Exemel
91 pages
XML (BScCSIT 5th Semester)
No ratings yet
XML (BScCSIT 5th Semester)
39 pages
CS549 Distributed Information Systems: Lecture 2: XML and Internet Databases
No ratings yet
CS549 Distributed Information Systems: Lecture 2: XML and Internet Databases
50 pages
E Tensible Arkup Anguage Unit-3: Basic XML DTD XML Schema Dom Vs Sax Presenting XML
No ratings yet
E Tensible Arkup Anguage Unit-3: Basic XML DTD XML Schema Dom Vs Sax Presenting XML
39 pages
Lect7-8 - XML
No ratings yet
Lect7-8 - XML
14 pages
SOA - WS-Topic 2
No ratings yet
SOA - WS-Topic 2
39 pages
XML Basics Extensible Markup Language: Divya Panta 21109
No ratings yet
XML Basics Extensible Markup Language: Divya Panta 21109
17 pages
XML: An Introduction XML: An Introduction: by Chitrakant Banchhor by Chitrakant Banchhor
No ratings yet
XML: An Introduction XML: An Introduction: by Chitrakant Banchhor by Chitrakant Banchhor
49 pages
XML PPT
No ratings yet
XML PPT
37 pages
Problem Solving Through C Programming Assignment Merged
100% (2)
Problem Solving Through C Programming Assignment Merged
45 pages
Introduction To XML Extensible Markup Language: Mr.A Raghuvira Pratap Computer Science Department
No ratings yet
Introduction To XML Extensible Markup Language: Mr.A Raghuvira Pratap Computer Science Department
24 pages
Chap 2 XML
No ratings yet
Chap 2 XML
18 pages
XML Unit III
No ratings yet
XML Unit III
21 pages
SHRM Assignment - Abulrahman Adnan Thekrallah
80% (10)
SHRM Assignment - Abulrahman Adnan Thekrallah
34 pages
Unit 5
No ratings yet
Unit 5
19 pages
XML
No ratings yet
XML
79 pages
XML Quick Guide
No ratings yet
XML Quick Guide
30 pages
Unit II WT Notes
No ratings yet
Unit II WT Notes
32 pages
Sleep and Psychiatric Disorders in Children and Adolescents - 1st Edition Complete Book Download
100% (17)
Sleep and Psychiatric Disorders in Children and Adolescents - 1st Edition Complete Book Download
15 pages
Unit 5
No ratings yet
Unit 5
10 pages
Geodetic Astronomy Part4
100% (1)
Geodetic Astronomy Part4
19 pages
Test Instruments For The Maintenance of Electrical Power Systems
No ratings yet
Test Instruments For The Maintenance of Electrical Power Systems
64 pages
Introduction To XML: A Universal Data Format
No ratings yet
Introduction To XML: A Universal Data Format
41 pages
Web Technology (CSC-353) : (Unit 3: XML)
No ratings yet
Web Technology (CSC-353) : (Unit 3: XML)
50 pages
E Tensible Arkup: Anguage
No ratings yet
E Tensible Arkup: Anguage
26 pages
Pec-Cs801d
No ratings yet
Pec-Cs801d
15 pages
Remidial Measures of Foundation Leakage - Conglomerate
No ratings yet
Remidial Measures of Foundation Leakage - Conglomerate
22 pages
Audience Theories: Hypodermic Needle Model
No ratings yet
Audience Theories: Hypodermic Needle Model
2 pages
XML For Dummies
No ratings yet
XML For Dummies
34 pages
XML Intro
No ratings yet
XML Intro
30 pages
CS Excel
No ratings yet
CS Excel
44 pages
Myers
No ratings yet
Myers
7 pages
Stock Market Analyst Internship Logbook
No ratings yet
Stock Market Analyst Internship Logbook
9 pages
Astm D 2113-14
No ratings yet
Astm D 2113-14
20 pages
XML Syntax Rules of XML Language: © 2008 Mindtree Consulting
No ratings yet
XML Syntax Rules of XML Language: © 2008 Mindtree Consulting
36 pages
Abhishek - Chhatrola Case Study
No ratings yet
Abhishek - Chhatrola Case Study
7 pages
PAG 2 Chemistry Questions
No ratings yet
PAG 2 Chemistry Questions
18 pages
ESCE - 5 - Artificial Intelligence (EN)
No ratings yet
ESCE - 5 - Artificial Intelligence (EN)
45 pages
Curriculum Vitae
No ratings yet
Curriculum Vitae
4 pages
Design & Fashion - June2018
No ratings yet
Design & Fashion - June2018
13 pages
Brutalist Style Technology Pitch Deck by Slidesgo
No ratings yet
Brutalist Style Technology Pitch Deck by Slidesgo
47 pages
Renault Megane-Scenic 1600cc-E3-K4ma7 LPG Eng
0% (1)
Renault Megane-Scenic 1600cc-E3-K4ma7 LPG Eng
4 pages
Week 5 05-Hardware
No ratings yet
Week 5 05-Hardware
37 pages
Week 5 06-Cloud
No ratings yet
Week 5 06-Cloud
23 pages
Week 6 XSD
No ratings yet
Week 6 XSD
219 pages
DSE704 Manual PDF
No ratings yet
DSE704 Manual PDF
15 pages
Cts TDM-PJF Cts Nsqf-5
No ratings yet
Cts TDM-PJF Cts Nsqf-5
68 pages
An Introduction To ASTM Concrete Pipe and Box Culvert Standards
No ratings yet
An Introduction To ASTM Concrete Pipe and Box Culvert Standards
42 pages
Bomba 330C
No ratings yet
Bomba 330C
11 pages
Language and Culture: Chapter 11
No ratings yet
Language and Culture: Chapter 11
25 pages
CRN8062446
No ratings yet
CRN8062446
3 pages
Outline
No ratings yet
Outline
4 pages
Naukri Naveenchandrakandpal (11y 0m)
No ratings yet
Naukri Naveenchandrakandpal (11y 0m)
5 pages
Barriers To Advance in OS
No ratings yet
Barriers To Advance in OS
9 pages
ALLISON TOURIGNY - Resume
No ratings yet
ALLISON TOURIGNY - Resume
2 pages
Iom 2 4PG BW Oct2015
No ratings yet
Iom 2 4PG BW Oct2015
4 pages
Chapter4 RQ1 Quali
No ratings yet
Chapter4 RQ1 Quali
5 pages
Multiple Choice (Pls Choose The Correct One)
No ratings yet
Multiple Choice (Pls Choose The Correct One)
4 pages
Sl. Book Title Author Subject Academic/Student/General/etc
No ratings yet
Sl. Book Title Author Subject Academic/Student/General/etc
7 pages
XML Programming: The Ultimate Guide to Fast, Easy, and Efficient Learning of XML Programming
From Everand
XML Programming: The Ultimate Guide to Fast, Easy, and Efficient Learning of XML Programming
Christopher Right
2.5/5 (2)
XSLT Interview Questions, Answers, and Certification: Your Guide to XSLT Interviews and Certification Review
From Everand
XSLT Interview Questions, Answers, and Certification: Your Guide to XSLT Interviews and Certification Review
equitypress
No ratings yet

Week 6 XML

Uploaded by

Week 6 XML

Uploaded by

XML

To understand at a conceptual Level:

What does a computer “know”?

» Presence or absences of a charge

What does a computer “know”?

» Encoded as binary numbers (0s or 1s)

What does a computer “know”?

What does a computer “know”?

… internet and the world wide web

• eXtensible Markup Language (XML)

- Data Transport Mechanism

Database: Steve 21 Skip Rope

Database: Steve 21 Skip Rope

Multiply that by the

Steve 21 Skip Rope

How do we get/write XML???

everything in an XML document is one of two things ONLY!

- it either DATA or it is a TAG

tag ( a label ‘bookended’ by angle brackets )

tag ( a label ‘bookended’ by angle brackets )

EASY: (everything is either data or it is a tag)

EASY: (everything is either data or it is a tag)

EASY: (everything is either data or it is a tag)

<tag1> NOTE: TAG

Tags - every tag has a START tag

Tags - every tag has a START tag

Tags - simple: only enclose (encase) data

Tags - complex: enclose (encase) other tags

Tags - BUT: they can be anything*

MORE COMPLEX EXAMPLE

List of all of your closest friends, including….

MORE COMPLEX EXAMPLE

List of all of your closest friends, including….

HOW TO MAKE AN XML DOCUMENT?

How do we turn this into an XML document?

⋄ Create a plain text file (no formatting)

HOW TO MAKE AN XML DOCUMENT?

How do we turn this into an XML document?

⋄ Create a plain text file (no formatting)

HOW TO MAKE AN XML DOCUMENT?

Billy 31 Cosplay, Avengers, DandD

Billy 31 Cosplay,Avengers, DandD

Idris 27 Dr. Who

Jordan 19 Star Wars, My Little Pony

Hobbies data element

Now we are ready to

ADD THE XML DOCUMENT FriendList

ADD THE XML DOCUMENT

ADD THE XML DOCUMENT

ADD TAGS <?xml version="1.0"?>

AND DATA name

ADD TAGS <?xml version="1.0"?>

AND DATA Billy

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

ADD TAGS <?xml version="1.0"?>

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character

<compare>6 < 7 & 7 > 6 'natch'</compare>

& – the & (ampersand) character