XML namespace: Difference between revisions

The educational technology and digital learning wiki
Jump to navigation Jump to search
 
(38 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Incomplete}}
{{Incomplete}}
{{web technology tutorial|Intermediate}}


This is an ''introductory'' XML namespace tutorial.
== Introduction ==


Note on its production: It's a Framemaker to Word to Mediawiki translation from parts of teaching slides. There are some details that need to be fixed - (20 March 2007)
<div class="tut_goals">
; Learning goals
* Understand why Namespaces are needed
* Learn how to use namespace declarations
* Learn how to create combined XHTML/SVG/MathML/etc documents
; Prerequisites
* Some [[XML]]
; Moving on
* [[DTD tutorial]]
* [[XML Schema tutorial - Basics]]
* [[SVG]] and [[MathML]]
* [[IMS]] e-learning standards
; Level and target population
* Beginners
; Remarks
* This tutorial provides a short overview about XML namespaces. It includes minimal knowledge needed for an XML class. Most parts also can be used in introductory web technologies class. Technical web authors also must understand namespaces, since they are used in XHTML and combined profiles.
</div>


== Definition ==
'''XML namespaces have two purposes:'''
# Clearly identify a markup language and its version. Schema declarations like DTDs or XML Schema are not mandatory in many XML applications
# Allow to mix two or more languages in a single document.


XML Namespaces allow to fully/uniquely qualify XML element and attribute names to prevent from confusing two elements that have the same name but mean different things.
XML Namespaces allow to fully/uniquely qualify XML element and attribute names to prevent confusing two elements that have the same name but mean different things. Various [[XML]] vocabularies (languages/applications) may be mixed. E.g. in a standards compliant web browser like Firefox or Opera you may include [[SVG]] and [[MathML]] code with the same [[XHTML]] page. But then we can run into naming conflicts, i.e. different vocabularies (DTDs) can use the same names for elements ! Namespaces are a W3C standard since Jan 1999. That means that namespaces have been introduced after XML has been invented.


== Purpose and history of XML namespace ==
Since DTDs are not mandatory for most W3C XML languages, the W3C requires namespace definitions within root elements, e.g. XHTML and SVG must include a namespace declaration:


Various XML vocabularies (languages/applications) can be mixed. But then we can run into naming conflicts, i.e. different vocabularies (DTDs) can use the same names for elements !
The following was mandatory in for valide XHMTL 1.x files:


Since DTDs are not mandatory for most W3C languages, the W3C requires namespace definitions within root elements, e.g. XHTML must have one:
&lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;


&lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
Basically this statement says that within the html element all child elements belong to XHTML, unless they are explicitly part of another namespace.


Namespaces are a W3C standard since Jan 1999. That means that namespaces have been introduced after XML has been invented.
The following example shows how to declare SVG files or fragments with an example (this is also valid for inclusion in HTML5)
<svg id="circle" height="200" xmlns="http://www.w3.org/2000/svg">
      <circle id="greencircle" cx="30" cy="30" r="30" fill="green" />
</svg>


== Standards involved ==
== Standards involved ==
Line 33: Line 55:
* http://www.w3.org/2004/CDF/
* http://www.w3.org/2004/CDF/


See also: The [[standard]]s overview article. Most XML-based standards in education (e.g. [[IMS Content Packaging]] make heavy use of namespaces ! In addition, most [[IMS]] and [[SCORM]] standards use [[XML Schema]]s which are associated to XML contents via namespace declarations.
See also: The [[standard]]s overview article. Most XML-based standards in education (e.g. [[IMS Content Packaging]] make heavy use of namespaces ! In addition most [[IMS]] and [[SCORM]] standards use [[XML Schema]] which are associated to XML contents via namespace declarations.


== Namespaces ==
== Namespaces ==
Line 39: Line 61:
=== An example demonstrating the need for namespaces ===
=== An example demonstrating the need for namespaces ===


Here is an XML fragment using '''title''' within a '''bibliography''' element:
Here is an XML fragment using title within a bibliography element:
<source lang="xml">
<book>
<title>A true story</title>
<description>A real cool publication</description>
</book>
</source>


<nowiki>book</nowiki>
A 2nd XML fragment uses title in a employees record:
  <nowiki>title</nowiki>A true story<nowiki>/title</nowiki>
<source lang="xml">
  <nowiki>description</nowiki>A real cool publication<nowiki>/description</nowiki>
<record>
<nowiki>/book</nowiki>
<name>Miller</name>  
<title>Dr. </title>
<publications> ... </publications>
</record>
</source>


A 2nd XML fragment uses '''title''' in a '''employees''' record:
If these two XML fragments were added together, there would be a name conflict because both contain a <title>< element with different meaning. In one case we mean ''book title'' and in the other ''something like "none", PhD, etc.''. A style-sheet would have to render these elements very differently. But we can solve this problem by adding prefixes, like this:
<nowiki>record</nowiki>
  <nowiki>name</nowiki>Miller<nowiki>/name</nowiki>  <nowiki>title</nowiki>Dr. <nowiki>/title</nowiki>
  <nowiki>publications</nowiki> ...  <nowiki>/publications</nowiki>
<nowiki>/record</nowiki>


If these two XML fragments were added together, there would be a name conflict because both contain a <nowiki>title</nowiki> element with different meaning. In one case we mean ''book title'' and in the other ''something link nothing, PhD, etc.''. E.g. a stylesheet would have to render these elements very differently. But we can solve this problem by adding prefixes, like this:
<source lang="xml">
<employees:record>
  <employees:name>Miller</employees:name>
  <employees:title>Dr. </employees:title>
  <employees:publications>
    <biblio:book>
      <biblio:title>A true story</biblio:title>
      <biblio:description>A real cool publication</biblio:description>
    </biblio:book>
  </employees:publications>
</employees:record>
</source>


<nowiki>''employees'':record</nowiki>
=== A real world example ===
<nowiki>''employees'':name</nowiki>Miller<nowiki>/''employees'':name</nowiki>
 
<nowiki>''employees'':title</nowiki>Dr.  <nowiki>/''employees'':title</nowiki>
The ''The Open Packaging Format''. Below is the content of an *.opf file that must be included within [[ePub]] "zip" file (a popular [[e-book]] format. It defines the structure of the book using assets and includes metadata.
<nowiki>''employees'':publications</nowiki>
 
   <nowiki>''biblio'':book</nowiki>
''OPF example copied with minor modifications from [http://en.wikipedia.org/wiki/EPUB#Open_Packaging_Format_2.0 Wikipedia] (nov 30 2010).
  <nowiki>''biblio'':title</nowiki>A true story<nowiki>/biblio:title</nowiki>
<source lang="XML">
  <nowiki>''biblio'':description</nowiki>A real cool publication<nowiki>/biblio:description</nowiki>
<?xml version="1.0"?>
   <nowiki>/''biblio'':book</nowiki>
<package version="2.0"
  <nowiki>/''employees'':publications</nowiki>
        xmlns="http://www.idpf.org/2007/opf"
  <nowiki>/''employees'':record</nowiki>
        unique-identifier="BookId">
  <metadata xmlns:dc="http://purl.org/dc/elements/1.1/"
            xmlns:opf="http://www.idpf.org/2007/opf">
    <dc:title>Pride and Prejudice</dc:title>
    <dc:language>en</dc:language>
    <dc:identifier id="BookId" opf:scheme="ISBN">123456789X</dc:identifier>
    <dc:creator opf:file-as="Austen, Jane" opf:role="aut">Jane Austen</dc:creator>
  </metadata>
   <manifest>
    <item id="chapter1" href="chapter1.xhtml"
          media-type="application/xhtml+xml"/>
    <item id="chapter2" href="chaptertwo.xhtml"
          media-type="application/xhtml+xml"/>
    <item id="stylesheet" href="style.css"
          media-type="text/css"/>
    <item id="ch1-pic" href="ch1-pic.png"
          media-type="image/png"/>
    <item id="myfont" href="css/myfont.otf"
          media-type="application/x-font-opentype"/>
    <item id="ncx" href="book.ncx" media-type="application/x-dtbncx+xml"/>
  </manifest>
  <spine toc="ncx">
    <itemref idref="chapter1" />
    <itemref idref="chapter2" />
   </spine>
   
  <guide>
    <reference type="loi" title="List Of Illustrations"
              href="appendix.html#figures" />
  </guide>
   
</package>
</source>
 
This OPF file includes two namespaces:
* http://www.idpf.org/2007/opf (It is both used as default, but also with a prefix within the Metadata section)
* http://purl.org/dc/elements/1.1/ ([[Dublin Core]] Metadata)


=== Declaring namespaces ===
=== Declaring namespaces ===
Line 72: Line 150:


# Create or identify a namespace identifier you wish to use: An XML namespace is identified by a unique URI reference, usually a URL.
# Create or identify a namespace identifier you wish to use: An XML namespace is identified by a unique URI reference, usually a URL.
# The URL does '''need not point to anything on the Internet'''. It is just used as a unique string, i.e. a name !
# The URL does '''need not point to anything on the Internet'''. It is just used as a unique string, i.e. a name  
# Therefore if some namespace URLs below are broken there is absolutly nothing to worry about. However, most namespace identifiers actually point to a real web page that either provides an explanation or at least informations about the organization/author that created the namespace. This means that if you plan to create your own namespaces, you should use the name of any webpage over which you have control.
# Therefore if some namespace URLs below are broken there is absolutely nothing to worry about. However, most namespace identifiers actually point to a real web page that either provides an explanation or at least information about the organization/author that created the namespace. This means that if you plan to create your own namespaces, you should use the name of any webpage over which you have control.
# Make a namespace declaration within the element that belongs to this namespace, i.e. map a prefix of your choice to a unique URI.
# Make a namespace declaration within the element that belongs to this namespace, i.e. map a prefix of your choice to a unique URI.


There are two major variants to declare namespaces
There are two major variants of namespace use: '''prefixed  '''namespaces and '''default''' ones.


(1) declaring a namespace that will require insertion of prefixes
(1) Namespace declaration for use with a prefix: declaring a namespace that will require use of '''prefixes for each element'''
<source lang="xml">
<prefix:element xmlns:prefix="URI">
</source>
Example:
<source lang="xml">
<html:html xmlns:html="http://www.w3.org/1999/xhtml">
  <html:head> ..... </html:head>
</source>
Each element below html:html that uses prefix "html:" will belong to Xhtml. Any other will not.


<nowiki>prefix:element xmlns:prefix="URI"</nowiki>
(2) Default namespace: declaring a '''default''' namespace for element and its children. I.e. these will not be prefixed.
e.g.
<nowiki>html:html xmlns:html=<nowiki>’</nowiki>http://www.w3.org/1999/xhtml<nowiki>’></nowiki> 
(2) declaring a default namespace for an element plus its children (by default they belong to namespace of the parent). See also below.


  <nowiki>element xmlns="URI"</nowiki>
<source lang="xml">
e.g.
  <element xmlns="URI"><
  <nowiki>html xmlns=<nowiki>’</nowiki>http://www.w3.org/1999/xhtml<nowiki>’></nowiki> .....
</source>
Example:
<source lang="xml">
  <html xmlns="http://www.w3.org/1999/xhtml">
  <head>.....</head>
  <body>.....
</source>


=== Scoping ===
=== Scoping ===
Line 97: Line 187:
;XHMTL fragment example:
;XHMTL fragment example:


<nowiki>?xml version="1.0"?</nowiki>
<source lang="xml">
<nowiki>html:html xmlns:html=<nowiki>’</nowiki>http://www.w3.org/1999/xhtml<nowiki>’></nowiki>
<?xml version="1.0"?>
  <nowiki>html:headhtml:title</nowiki>Frobnostication<nowiki>/html:title/html:head</nowiki>
  <html:html xmlns:html='http://www.w3.org/1999/xhtml'>
   <nowiki>html:bodyhtml:p</nowiki>Moved to
  <html:head>
  <nowiki>html:a href=<nowiki>’</nowiki>http://frob.example.com<nowiki>’></nowiki>here.<nowiki>/html:a/html:p</nowiki>
    <html:title>Frobnostication</html:title>
  <nowiki>/html:body</nowiki>
  </html:head>
<nowiki>/html:html</nowiki>
   <html:body>
    <html:p>
      Moved to<html:a href='http://frob.example.com'>here.</html:a>
    </html:p>
  </html:body>
</html:html>
</source>
The scope of the XHMTL namespace declaration goes from <code><html:html></code> to <code></html:html></code>.


;Example with 2 namespaces (both use URNs instead of URLs)
;Example with 2 namespaces (both use URNs instead of URLs)
 
<source lang="xml">
<nowiki>?xml version="1.0"?</nowiki>
<?xml version="1.0"?>
<nowiki>!-- both namespace prefixes are available throughout --</nowiki>
<!-- both namespace prefixes are available throughout the XML fragment -->
<nowiki>bk:book xmlns:bk=<nowiki>’</nowiki>urn:loc.gov:books<nowiki>’</nowiki> xmlns:isbn=<nowiki>’</nowiki>urn:ISBN:0-395-36341-6<nowiki>’></nowiki>
<bk:book xmlns:bk='urn:loc.gov:books'
  <nowiki>bk:title</nowiki>Cheaper by the Dozen<nowiki>/bk:title</nowiki>
        xmlns:isbn='urn:ISBN:0-395-36341-6'>
  <nowiki>isbn:number</nowiki>1568491379<nowiki>/isbn:number</nowiki>
    <bk:title>Cheaper by the Dozen</bk:title>
<nowiki>/bk:book</nowiki>
    <isbn:number>1568491379</isbn:number>
</bk:book>
</source>


=== Default namespaces ===
=== Default namespaces ===


If most elements in an XML document belonged to the same namespace, it would be ugly to prefix each element name. Instead, define a default namespace that applies to all non-prefixed elements and attributes.
If most elements in an XML document belonged to the same namespace, it would be ugly to prefix each element name. Instead define a default namespace that applies to all non-prefixed elements and attributes.
 
Syntax:
  <nowiki>element xmlns="URI"</nowiki> ....
<source lang="xml">
  <element xmlns="URI"> < ....
</source>


The default namespace applies to the element in which it was defined and all descendants of that element. But if a descendants has another default namespace defined on it, this new namespace definition overrides the previous one and becomes the default for that element and its descendants.
The default namespace applies to the element in which it was defined and all descendants of that element. But if a descendants has another default namespace defined on it, this new namespace definition overrides the previous one and becomes the default for that element and its descendants.
Line 124: Line 225:


;XHTML default namespace example:
;XHTML default namespace example:
 
<source lang="xml">
<nowiki>?xml version="1.0"?</nowiki>
<?xml version="1.0"?>
<nowiki>!-- elements are in the HTML namespace by default --</nowiki>
<!-- elements are in the HTML namespace by default -->
  <nowiki>html xmlns=<nowiki>’</nowiki>http://www.w3.org/1999/xhtml<nowiki>’></nowiki>
<html xmlns='http://www.w3.org/1999/xhtml'>
  <nowiki>headtitle</nowiki>Frobnostication<nowiki>/title/head</nowiki>
  <head>
  <nowiki>bodyp</nowiki>Moved to
      <title>Frobnostication</title>
  <nowiki>a href=<nowiki>’</nowiki>http://frob.example.com<nowiki>’></nowiki>here<nowiki>/a</nowiki>.<nowiki>/p/body</nowiki>
  </head>
<nowiki>/html</nowiki>
  <body>
 
      <p>Moved to <a href='http://frob.example.com'>here</a>.</p>
  </body>
</html>
</source>
Default namespace for a book vocabulary plus a namespace for ISBN example:
Default namespace for a book vocabulary plus a namespace for ISBN example:
<nowiki>?xml version="1.0"?</nowiki>
<source lang="xml">
<nowiki>!-- unprefixed element types are from "books" --</nowiki>
  <!-- unprefixed element types are from "books" -->
  <nowiki>book xmlns=<nowiki>’</nowiki>urn:loc.gov:books<nowiki>’</nowiki>
  <book xmlns='urn:loc.gov:books'
xmlns:isbn=<nowiki>’</nowiki>urn:ISBN:0-395-36341-6<nowiki>’></nowiki>
        xmlns:isbn='urn:ISBN:0-395-36341-6'>
    <nowiki>title</nowiki>Cheaper by the Dozen<nowiki>/title</nowiki>
  <title>Cheaper by the Dozen</title>
    <nowiki>isbn:number</nowiki>1568491379<nowiki>/isbn:number</nowiki>
  <isbn:number>1568491379</isbn:number>
  <nowiki>/book</nowiki>
  </book>
 
</source>
;A larger example of namespace scoping
;A larger example of namespace scoping


It includes some XHTML whose namespace is declared within the "p" element.
It includes some XHTML whose namespace is declared within the "p" element.
 
<source lang="xml">
<nowiki>?xml version="1.0"?</nowiki>
<?xml version="1.0"?>
<nowiki>!-- initially, the default namespace is "books" --</nowiki>
<!-- initially, the default namespace is "books" -->
<nowiki>book xmlns=<nowiki>’</nowiki>urn:loc.gov:books<nowiki>’</nowiki> xmlns:isbn=<nowiki>’</nowiki>urn:ISBN:0-395-36341-6<nowiki>’></nowiki>
<book xmlns='urn:loc.gov:books'
<nowiki>title</nowiki>Cheaper by the Dozen<nowiki>/title</nowiki>
      xmlns:isbn='urn:ISBN:0-395-36341-6'>
<nowiki>isbn:number</nowiki>1568491379<nowiki>/isbn:number</nowiki>
  <title>Cheaper by the Dozen</title>
<nowiki>notes</nowiki>
  <isbn:number>1568491379</isbn:number>
<nowiki>!-- make HTML the default namespace for some commentary --</nowiki>
  <notes>
<nowiki>p xmlns=<nowiki>’</nowiki>http://www.w3.org/1999/xhtml<nowiki>’></nowiki> This is a <nowiki>i</nowiki>funny<nowiki>/i</nowiki> book!
  <!-- make HTML the default namespace for some commentary -->
    <nowiki>/p</nowiki>
      <p xmlns='http://www.w3.org/1999/xhtml'>
  <nowiki>/notes</nowiki>
        This is a <i>funny</i> book!
<nowiki>/book</nowiki>
    </p>
  </notes>
</book>
</source>


; XSLT namespace example
; XSLT namespace example


# XSLT instructions are prefixed with "xsl" here
[[XSLT]] is a transformation language, i.e. programming language that allows to translate an XML content into another content (XML or other). XSLT instructions are prefixed with "xsl" here.
# Output is namespace-less here ...)
Output produced is namespace-less here. See the [[XSLT tutorial]] for an introduction.
<source lang="xml">
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="page">
  .....
  <html> <head> <title> <xsl:value-of select="title"/> </title> </head>
  <body bgcolor="#ffffff"> <xsl:apply-templates/> </body>
  </html>
</xsl:template>


<nowiki>?xml version="1.0"?</nowiki>
<xsl:template match="title">
<nowiki>xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"</nowiki>
   <h1 align="center"> <xsl:apply-templates/> </h1>
<nowiki>xsl:template match="page"</nowiki>
</xsl:template>
.....
<nowiki>html</nowiki> 
  <nowiki>head</nowiki> <nowiki>title</nowiki> <nowiki>xsl:value-of select="title"/</nowiki> <nowiki>/title</nowiki><nowiki>/head</nowiki>
<nowiki>body bgcolor="<nowiki> </nowiki>ffffff"</nowiki> 
  <nowiki>xsl:apply-templates/</nowiki> 
    <nowiki>/body</nowiki>
  <nowiki>/html</nowiki>
<nowiki>/xsl:template</nowiki>
<nowiki>xsl:template match="title"</nowiki>
   <nowiki>h1 align="center"</nowiki>
  <nowiki>xsl:apply-templates/</nowiki>
  <nowiki>/h1</nowiki>
<nowiki>/xsl:template</nowiki>


<nowiki>xsl:template match="content"</nowiki>
<xsl:template match="content">
   <nowiki>p align="center"</nowiki>
   <p align="center"> <xsl:apply-templates/> </p>
  <nowiki>xsl:apply-templates/</nowiki>
</xsl:template>
  <nowiki>/p</nowiki>
<nowiki>/xsl:template</nowiki>


<nowiki>xsl:template match="comment"</nowiki>
<xsl:template match="comment">
   <nowiki>hr /</nowiki>
   <hr /> <xsl:apply-templates/>
  <nowiki>xsl:apply-templates/</nowiki>
   </xsl:template>
   <nowiki>/xsl:template</nowiki>
</xsl:stylesheet>
  <nowiki>/xsl:stylesheet</nowiki>
</source>


=== Validation of composite documents ===
=== Validation of composite documents ===


# Validating documents that contain different namespaces are called composite or compound documents and validation is not always easy since combined DTDs may not exist
Validating documents that contain different namespaces are called composite or compound documents and validation is not always easy since combined DTDs may not exist. A validation standard for composite W3C vocabularies is currently under preparation (but may not happen ...). Usually, combined documents are produced by server-side programs for delivery and they are just well-formed (not attached to DTDs or other schemas)
# A validation standard for composite W3C vocabularies is currently under preparation ...
# Usually, combined documents are produced by server-side programs for delivery and they are just well-formed (not attached to DTDs or other schemas)
# You may write DTDs that validate compound documents.


; A DTD rule with an extra namespace example:
You also may write DTDs that validate your own compound documents as we demonstrate in the following example.


# In this example, the "a" element and the "description" attribute belongs to the default namespace, but the href and type attributes belong to the xlink namespace
; A DTD rule with an extra namespace example
# We declare the namespace in the root element, but also could have done it just for the "el" element...
* [http://tecfa.unige.ch/guides/xml/examples/composites/link_list.dtd link_list.dtd]
* [http://tecfa.unige.ch/guides/xml/examples/composites/link_list.xml link_list.xml]


<nowiki>!ELEMENT link_list (el<nowiki>+</nowiki>)</nowiki>
In this example, the "a" element and the "description" attribute belongs to the default namespace, but the href and type attributes belong to the xlink namespace. We declare the namespace in the root element, but also could have done it just for the "el" element. Note: Xlinks do not work in IE7/8.
<nowiki>!ATTLIST link_list xmlns:xlink CDATA <nowiki> </nowiki>FIXED "http://www.w3.org/1999/xlink"</nowiki>
<nowiki>!ELEMENT el (<nowiki> </nowiki>PCDATA)</nowiki>
<nowiki>!ATTLIST el description CDATA <nowiki> </nowiki>IMPLIED xlink:href CDATA <nowiki> </nowiki>REQUIRED xlink:type CDATA <nowiki> </nowiki>FIXED "simple"</nowiki>


; An XML Example file
<source lang="xml">
<!ELEMENT link_list (el+)>
<!ATTLIST link_list xmlns:xlink CDATA #FIXED "http://www.w3.org/1999/xlink">
<!ELEMENT el (#PCDATA)>
<!ATTLIST el description CDATA #IMPLIED
          xlink:href CDATA #REQUIRED
          xlink:type CDATA #FIXED "simple" >
</source>
See the [[DTD tutorial]] for details.


<nowiki>?xml version="1.0" encoding="ISO-8859-1" ?</nowiki>
; An XML example file
<nowiki>!DOCTYPE link_list SYSTEM "link_list.dtd"</nowiki>
<nowiki>?xml-stylesheet href="link_list.css" type="text/css" ?</nowiki>
<nowiki>link_list xmlns:xlink="http://www.w3.org/1999/xlink"</nowiki>
  <nowiki>el description="verified" xlink:type="simple" xlink:href="http://tecfa.unige.ch/"</nowiki>TECFA<nowiki>/el</nowiki>
  <nowiki>el xlink:href="http://tecfa.unige.ch/" xlink:type="simple"</nowiki>TECFA<nowiki>/el</nowiki>
<nowiki>/link_list</nowiki>


== Client-side XML languages and namespaces overview ==
<source lang="xml">
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE link_list SYSTEM "link_list.dtd">
<?xml-stylesheet href="link_list.css" type="text/css" ?>
<link_list xmlns:xlink="http://www.w3.org/1999/xlink">
    <el description="verified"
        xlink:type="simple"
        xlink:href="http://www.webster.ch/">Webster Geneva</el>
    <el xlink:href="http://www.webster.edu/"
        xlink:type="simple">Webster</el>
</link_list>
</source>
 
== Namespaces for documents ==
 
=== Client-side XML web languages and namespaces overview ===


The W3C defines several Internet languages and for which namespace declarations are mandatory (even if you use them "standalone", i.e. not in composite documents.  
The W3C defines several Internet languages and for which namespace declarations are mandatory (even if you use them "standalone", i.e. not in composite documents.  
Line 230: Line 343:
|align = "center"|Explanation
|align = "center"|Explanation
|-
|-
|XSLT
|[[XSLT]]
|http://www.w3.org/1999/XSL/Transform
|http://www.w3.org/1999/XSL/Transform
|XSL - Transformations
|XSL - Transformations
Line 239: Line 352:
|-
|-
|[[XML Schema]]
|[[XML Schema]]
|http://www.w3.org/2001/XMLSchema<nowiki> </nowiki>
|http://www.w3.org/2001/XMLSchema
|&nbsp;
|XML grammar definition language
|-
|-
|[[SVG]]
|[[SVG]]
Line 247: Line 360:
|-
|-
|[[RDF]]
|[[RDF]]
|http://www.w3.org/1999/02/22-rdf-syntax-ns<nowiki> </nowiki>
|http://www.w3.org/1999/02/22-rdf-syntax-ns
|Resource Description Format
|Resource Description Format
|-
|-
Line 259: Line 372:
|-
|-
|XLink
|XLink
|xmlns:xlink="http://www.w3.org/1999/xlink"
|http://www.w3.org/1999/xlink"
|XML Linking Language
|XML Linking Language
|-
|-
Line 266: Line 379:
|Next generation of HTML forms.
|Next generation of HTML forms.
|-
|-
|XHTML
|[[XHTML]]
|http://www.w3.org/1999/xhtml
|http://www.w3.org/1999/xhtml
|&nbsp;
|XML-based HTML variant
|-
|-
|[[MathML]]
|[[MathML]]
Line 282: Line 395:


See [http://ebiquity.umbc.edu/blogger/100-most-common-rdf-namespaces/ 100 most common RDF namespaces]
See [http://ebiquity.umbc.edu/blogger/100-most-common-rdf-namespaces/ 100 most common RDF namespaces]
=== Other Document standards ===
Each of the following usually packages a document as zip file. Inside the zip, you will find several files using several XML languages.
* [[EPub]] (e-books)
* [[Open Packaging Conventions and Office Open XML]] (Microsoft "docx")
* [[IMS Content Packaging]] (an e-learning format)


== Compound documents ==
== Compound documents ==
Line 289: Line 410:
; Examples of possible Compound Document profiles:
; Examples of possible Compound Document profiles:


* XHTML <nowiki>+</nowiki> SVG <nowiki>+</nowiki> MathML
* XHTML + SVG + MathML
* XHTML <nowiki>+</nowiki> SMIL
* XHTML + SMIL
* XHTML <nowiki>+</nowiki> XForms
* XHTML + XForms
* XHTML <nowiki>+</nowiki> VoiceML
* XHTML + VoiceML


The W3C is working on a generic Compound Document by Reference Framework (CDRF) that defines a language-independent processing model for combining arbitrary document formats ...
The W3C is working on a generic Compound Document by Reference Framework (CDRF) that defines a language-independent processing model for combining arbitrary document formats ...
Line 298: Line 419:
;Web browser caveats:
;Web browser caveats:


* IE doesn't support natively most of these languages, Firefox supports more but not all.
* IE '''doesn't support natively''' most XML W3C "content" languages (e.g. SVG, MathML), but implements a version of [[SMIL]], called "Timed Text". Firefox supports static [[SVG]] and [[MathML]]. Both implement [[RSS]]
Workarounds:
Workarounds:
* Use a browser that is more advanced (e.g. Firefox) or specialized players (e.g. Realplayer for SMIL)
* Use a browser that is more advanced (e.g. Firefox, Opera, Chrome) or specialized players (e.g. Realplayer for SMIL)
* Install plugins for your web browser and use a more indirect method to assemble contents, i.e. <nowiki>object</nowiki> or <nowiki>iframe</nowiki> This will work with most browsers if you have the right plugin (SVG in this case) installed.
* For HTML + SVG + MathML, use [[HTML5]]
<nowiki>iframe src="hello-svg.svg" height="300" width="80%" frameborder="0"</nowiki>
* Call your files *.xml (often helps if you use IE)
* For some formats you may install plugins or extensions in your web browser and then use a more indirect method to assemble contents, i.e. <nowiki><object> or <iframe></nowiki>.  This will work with most browsers if you have the right plugin (SVG in this case) installed.
<source lang="xml">
<iframe src="hello-svg.svg" height="300" width="80%" frameborder="0">
... Sorry you need an SVG plugin ...
... Sorry you need an SVG plugin ...
<nowiki>/iframe</nowiki>
</iframe><
</source>


=== XHTML + other vocabularies ===
=== XHTML + other vocabularies ===


; XHTML / MathML example
; XHTML / MathML example
 
* [http://tecfa.unige.ch/guides/xml/examples/composites/xhtml_mathml.xml xhtml_mathml.xml]
See the [[MathML]] article. It contains some mixed XHTML/MathML code.
<source lang="xml">
<?xml version="1.0" encoding="iso-8859-1"?>
<xhtml:html xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <xhtml:body>
    <xhtml:h1>A Compound Document</xhtml:h1>
    <xhtml:p>A simple formula using MathML in XHTML.</xhtml:p>
    <mathml:math xmlns:mathml="http://www.w3.org/1998/Math/MathML">
      <mathml:mrow>
        <mathml:msqrt> <mathml:mn>49</mathml:mn> </mathml:msqrt>
        <mathml:mo>=</mathml:mo>
        <mathml:mn>7</mathml:mn>
      </mathml:mrow>
    </mathml:math>
  </xhtml:body>
</xhtml:html>
</source>
MathML doesn't natively work with IE 6/7/8. But there are workarounds. See the [[MathML]] article for some more information about MathML and dealing with IE.


;Xlink example
;Xlink example
Line 318: Line 459:


; Example - Story grammar that implements XLink for an A element
; Example - Story grammar that implements XLink for an A element
* Online: [http://tecfa.unige.ch/guides/xml/examples/composites/story-grammar.xml story-grammar.xml]


<nowiki>?xml version="1.0" encoding="ISO-8859-1" ?</nowiki>
<source lang="xml">
<nowiki>STORY xmlns:xlink="http://www.w3.org/1999/xlink"</nowiki>
<?xml version="1.0" encoding="ISO-8859-1" ?>
<nowiki>Title</nowiki>The Webmaster<nowiki>/Title</nowiki>
<STORY xmlns:xlink="http://www.w3.org/1999/xlink">
.....
  <Title>The Webmaster</Title>
  <nowiki>INFOS</nowiki>  
  .....
    <nowiki>Date</nowiki>30 octobre 2003<nowiki>/Date</nowiki>
  <INFOS> <Date>30 octobre 2003 - </Date>
    <nowiki>Author</nowiki>DKS -<nowiki>/Author</nowiki>
  <Author>DKS - </Author>
    <nowiki>A xlink:href=http://jigsaw.w3.org/css-validator/check/referer xlink:type="simple"</nowiki>CSS Validator<nowiki>/A</nowiki>
  <A xlink:href=http://jigsaw.w3.org/css-validator/check/referer
  <nowiki>/INFOS</nowiki>
    xlink:type="simple">CSS Validator</A>
<nowiki>/STORY</nowiki>
  </INFOS>
</STORY>
</source>


;SVG example
;SVG example
* Most browsers (i.e. all major browser except IE8) can handle SVG. However, some only implement SVG 1.0 and most only static SVG. As of, only Opera implemented the so-called SMILE tags.
* Alternatively, use HTML and read the [[using SVG with HTML5 tutorial]]


XHTML with embedded SVG tags (tested with Firefox)
XHTML with embedded SVG tags (tested with Firefox)
* Source: http://tecfa.unige.ch/guides/xml/examples/composites/xhtml_svg.xhtml xhtml_svg.xhtml]
<source lang="xml" enclose="div">
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" >
<html xmlns="http://www.w3.org/1999/xhtml" 
      xmlns:svg="http://www.w3.org/2000/svg">
<head>
  <title>SVG within XHTML Demo</title>
</head>
<body>
  <h1>SVG within XHTML Demo</h1>


<nowiki>?xml version="1.0" encoding="ISO-8859-1" ?</nowiki>
  <p> You can embed SVG into XHTML, provided that your browser
<nowiki>!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" </nowiki>
  natively implements SVG. E.g. Firefox 1.5+ supports most of static
<nowiki>html xmlns="http://www.w3.org/1999/xhtml"
  SVG. </p>
    xmlns:svg="http://www.w3.org/2000/svg"</nowiki>
 
<nowiki>head</nowiki> 
  The SVG part starts below <hr />
<nowiki>title</nowiki>SVG within XHTML Demo<nowiki>/title</nowiki> 
 
  <nowiki>/head</nowiki>
  <svg xmlns="http://www.w3.org/2000/svg" version="1.1"  
<nowiki>body</nowiki>
      width="400" height="300">
.... The SVG part starts below <nowiki>hr /</nowiki>
  <!-- a small rectangle -->
<nowiki>svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="400" height="300"</nowiki>
   <rect x="50" y="50" rx="5" ry="5" width="300" height="100"
<nowiki>!-- a small rectangle --</nowiki>
  style="fill:#CCCCFF;stroke:#000099"/>
   <nowiki>rect x="50" y="50" rx="5" ry="5" width="300" height="100" style="fill:<nowiki> </nowiki>CCCCFF;stroke:#000099"/</nowiki>
 
<nowiki>!-- a text in the same place --</nowiki>
  <!-- a text in the same place -->
   <nowiki>text x="55" y="90" style="stroke:#000099;fill:#000099;font-size:24;"</nowiki>HELLO dear reader <nowiki>/text</nowiki>
   <text x="55" y="90" style="stroke:#000099;fill:#000099;font-size:24;">
   <nowiki>/svg</nowiki>
    HELLO dear reader
<nowiki>hr /</nowiki>
  </text>
The SVG part ended above
 
<nowiki>/body</nowiki>
  </svg>
<nowiki>/html</nowiki>
  <hr />
  The SVG part ended above
</body>
</html>
</source>
 
SVG within HTML5. This also should work with very old browsers (e.g. IE 6 and FF 1) plus the now unavailable SVG plugin from Adobe.
 
<source lang="xml">
<!DOCTYPE html>
<html>
  <head> <title>HELLO SVG with an iframe</title> </head>
   <body>
    <h1>HELLO SVG with an iframe</h1>
        Here is an embeded SVG scene using iframe.
<iframe src="hello-svg.svg" height="200" width="80%" frameborder="0">
</iframe>
    <hr>
  </body>  
</html>
</source>
 
In the following example, the SVG file is a standard stand-alone SVG file
<source lang="xml">
<?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN"
          "http://www.w3.org/TR/2001/PR-SVG-20010719/DTD/svg10.dtd">
<svg xmlns="http://www.w3.org/2000/svg">
  <rect x="50" y="50" rx="5" ry="5" width="300" height="100"
        style="fill:#CCCCFF;stroke:#000099"/>
  <text x="55" y="90" style="stroke:#000099;fill:#000099;font-size:24;">
  HELLO dear reader
  </text>
</svg>
</source>


=== Combining XHTML with your XML ===
=== Combining XHTML with your XML ===
Line 358: Line 552:
It sometimes can be practical to combine your own XML contents with XHTML, because HTML offers easy-to-use functionality like image inclusions or links.
It sometimes can be practical to combine your own XML contents with XHTML, because HTML offers easy-to-use functionality like image inclusions or links.
Note however that in practice this feature is not often used since:
Note however that in practice this feature is not often used since:
* XSLT stylesheets allow transformations of XML data into XHTML (i.e. the stylesheet will contain the extra HTML and the result displayed usually will be all HTML and easier to manage with CSS)
* [[XSLT]] stylesheets allow transformations of XML data into XHTML. The stylesheet will contain the extra HTML and the result displayed usually will be all HTML and will be easier to manage with CSS.
* the way browsers implement this is not really stable
* The way browsers implement this feature is not really stable
* Since HTML5 is now dominant, people cannot remember the potential of XHTML.


;XHTML with some XML included and CSS example
;XHTML with some XML included, using [[CSS]] for styling


# Tested with Firefox 2.x (works) and IE 7 (CSS doesn<nowiki>’</nowiki>t work, I don<nowiki>’</nowiki>t know why ...)
* Tested with Firefox 2.x (works) and IE 7 (CSS doesn't work, I don't know why ...)


Procedure:
Procedure:


# Define a namespace for the included XML content
# Define a namespace for the included XML content
# Attach a CSS stylesheet with an XML processor instruction
# Attach a CSS stylesheet with an XML processor instruction. Else, users will not see the contents of your XML.
# Your file must be understood as "XML", e.g. call it something.xml or something.xhtml but not something.html !
# Your file must be understood as "XML", e.g. call it ''something.xhtml'' or ''something.xht'' or ''something.xml''. If you use IE7/8 it must be something.xml, since IE doesn't support XHTML). Do not call your file ''something.html'' or ''something.htm'' !!
 
XHTML with some cooking XML included (file cooking.xhtml):
* [http://tecfa.unige.ch/guides/xml/examples/composites/cooking.xhtml cooking.xhtml] (XHTML + XML file)
* [http://tecfa.unige.ch/guides/xml/examples/composites/cooking.css cooking.css] (CSS file)
<source lang="xml">
<?xml version="1.0" ?>
<?xml-stylesheet type="text/css" href="cooking.css"?>
 
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:re="http://webster.unige.ch/coap21/dolores">
  <head>
    <title>A Compound XHTML-XML Document</title>
    <!-- this should work with IE but doesn't, maybe IE6 ? -->
    <link href="dolores.css" type="text/css" rel="stylesheet"/>
  </head>


  <body>


XHTML with some cooking XML included (file cooking.xhtml):
    <h1>A Compound XHTML-XML Document</h1>
<nowiki>?xml version="1.0" encoding="iso-8859-1"?</nowiki>
 
<nowiki>?xml-stylesheet type="text/css" href="cooking.css"?</nowiki>
    <p>Contains a cooking recipee written down by R. Dolores for a
<nowiki>html xmlns="http://www.w3.org/1999/xhtml" xmlns:re="http://tecfa.unige.ch/ns/cooking"</nowiki>
    COAP 2180 CSS exercise. Everything below the line is XML styled
<nowiki>head</nowiki>
    with a CSS stylesheet</p> <hr/>
<nowiki>title</nowiki>A Compound XHTML-XML Document<nowiki>/title</nowiki>
 
<nowiki>!-- this should work with IE but doesn<nowiki>’</nowiki>t, maybe IE6 ? --</nowiki>
  <re:recipe>
<nowiki>link href="cooking.css" type="text/css" rel="stylesheet"/</nowiki>
    <re:recipe_head>
<nowiki>/head</nowiki>
      <re:recipe_name>Cold Salmon in Creamy Spiced Sauce</re:recipe_name>
<nowiki>body</nowiki>
      <re:recipe_author>Hilaire Walden</re:recipe_author>
<nowiki>h1</nowiki>A Compound XHTML-XML Document<nowiki>/h1</nowiki>
     
<nowiki>p</nowiki>Contains a cooking recipee written down by R. D. as an exercise.
      <re:meal_type>Fish and Shellfish</re:meal_type>
  Everything below the line is XML styled with a CSS stylesheet<nowiki>/ p</nowiki>
    </re:recipe_head>
<nowiki>hr/</nowiki>
   
<nowiki>re:recipe</nowiki>
    <re:recipe_body>
<nowiki>re:recipe_head</nowiki>
      <re:ingredients>
  <nowiki>re:recipe_name</nowiki>Cold Salmon in Creamy Spiced Sauce<nowiki>/re:recipe_name</nowiki>
<re:ingredient>1/2 teaspoon finely crushed cumin seeds</re:ingredient>
  <nowiki>re:recipe_author</nowiki>H.W.<nowiki>/re:recipe_author</nowiki>
<re:ingredient>1 teaspoon chilli powder</re:ingredient>
  <nowiki>re:meal_type</nowiki>Fish and Shellfish<nowiki>/re:meal_type</nowiki>
<re:ingredient>salt and freshly ground black pepper</re:ingredient>
<nowiki>/re:recipe_head</nowiki>
.....
<re:ingredient>2 tablespoons olive oil</re:ingredient>
<nowiki>/re:recipe</nowiki>
<re:ingredient>2 cloves garlic, crushed</re:ingredient>
<nowiki>/body</nowiki>
<re:ingredient>1.25 cm (1/2 in) fresh ginger root, finely
<nowiki>/html</nowiki>
chopped</re:ingredient>
<re:ingredient>4 pieces salmon fillet, skinned</re:ingredient>
<re:ingredient>125 ml (4 fl oz / 1/2 cup) double (heavy)
cream</re:ingredient>
<re:ingredient>250 ml (8 fl oz / 1 cup) thick plain
yogurt</re:ingredient>
<re:ingredient>large pinch of saffron threads, toasted and
crushed</re:ingredient>
  <re:ingredient>seeds from 6 cardamom pods, toasted and finely
  crushed</re:ingredient>
<re:ingredient>salt</re:ingredient>
  <re:ingredient>coriander (cilantro) to garnish</re:ingredient>
      </re:ingredients>
      <re:directions>
<re:direction>Mix together the cumin seeds, chilli powder and
pepper and rub into the fish.</re:direction>
<re:direction>Heat the oil in a frying pan, add the garlic and
ginger and heat until they sizzle.</re:direction>
<re:direction>Add the salmon fillets and fry until they start
to colour (about 15-20 seconds on each side).</re:direction>
<re:direction>Stir in the cream, yogurt, saffron, cardamom and
salt.</re:direction>
<re:direction>Adjust the heat so that the sauce is just
bubbling and cook, turning the fish once, until the flesh just
flakes when tested with the point of a sharp knife (about 3-4
minutes each side).</re:direction>
<re:direction>Transfer the fish to a shallow dish. Boil the
sauce until it has reduced and thickened, pour over the fish
and leave to cool.</re:direction>
        <re:direction>Cover the dish and chill until 15-20 minutes
        before serving.</re:direction>
<re:direction>Garnish with coriander (cilantro).</re:direction>
</re:directions>
    </re:recipe_body>
 
    <re:recipe_footer>
    <re:serving>4</re:serving>
    <re:preparation_time>15 minutes</re:preparation_time>
    </re:recipe_footer>
 
    <re:document_info>
      <re:document_author>Hilaire Walden</re:document_author>
      <re:date_updated>21/01/07</re:date_updated>
      <re:source>Easy to Cook, Hot &amp; Spicy</re:source>
    </re:document_info>
  </re:recipe>
  </body>
</html>
</source>


=== Combining your XML with XHTML ===
=== Combining your XML with XHTML ===
Line 403: Line 663:
* Btw this is a trick to get around non-implementation of the xlink standard in IE.  
* Btw this is a trick to get around non-implementation of the xlink standard in IE.  


;XML plus XHTML (file xml_plus_xhtml.xml)
;XML plus XHTML
<nowiki>?xml version="1.0" ?</nowiki>
* [http://tecfa.unige.ch/guides/xml/examples/composites/xml_plus_xhtml.xml xml_plus_xhtml.xml]
<nowiki>?xml-stylesheet href="xml_plus_xhtml.css" type="text/css"?</nowiki>
<source lang="xml">
<nowiki>page xmlns:html="http://www.w3.org/1999/xhtml" updated="jan 2007"</nowiki>
<?xml version="1.0" ?>
  <nowiki>title</nowiki>Hello friend<nowiki>/title</nowiki>
<?xml-stylesheet href="xml_plus_xhtml.css" type="text/css"?>
  <nowiki>list</nowiki>
<page xmlns:html="http://www.w3.org/1999/xhtml" updated="jan 2007">
   <nowiki>!-- we use an HTML tag below to include a picture --</nowiki>
  <title>Hello friend</title>
   <nowiki>html:img src="photo.jpg"/</nowiki>
  <list>
   <nowiki>item price="10"</nowiki> White plate <nowiki>/item</nowiki>
   <!-- we use an HTML tag below to include a picture -->
   <nowiki>item price="20"</nowiki> Gold plate <nowiki>/item</nowiki>
   <html:img src="photo.jpg"/>
   <nowiki>item price="15"</nowiki> Silver plate <nowiki>/item</nowiki>
   <item price="10"> White plate </item>  
  <nowiki>/list</nowiki>
   <item price="20"> Gold plate </item>  
  <nowiki>comment</nowiki> Written by <nowiki>html:a href="...."</nowiki>DKS/Tecfa<nowiki>/html:a</nowiki> , feb 2007 <nowiki>/comment</nowiki>
   <item price="15"> Silver plate </item>  
<nowiki>/page</nowiki>
  </list>
 
  <comment> Written by <html:a href="http://tecfa.unige.ch/DKS">DKS/Tecfa</html:a>
, feb 2007 </comment>
</page>
</source>
 
== XSLT transformations of compound documents ==
 
Transforming XML files that include namespace (including just default namespaces that do not use prefixes) requires that you prefix each XPath "component". For more information, see:
* [[XSLT for compound documents tutorial]]
* [[XSLT Tutorial - Basics]]


[[Category: Technologies]]
[[Category: XML]]
[[Category: XML]]
[[Category: Tutorials]]
[[Category:Web technology tutorials]]

Latest revision as of 22:00, 13 September 2015

Introduction

Learning goals
  • Understand why Namespaces are needed
  • Learn how to use namespace declarations
  • Learn how to create combined XHTML/SVG/MathML/etc documents
Prerequisites
Moving on
Level and target population
  • Beginners
Remarks
  • This tutorial provides a short overview about XML namespaces. It includes minimal knowledge needed for an XML class. Most parts also can be used in introductory web technologies class. Technical web authors also must understand namespaces, since they are used in XHTML and combined profiles.

XML namespaces have two purposes:

  1. Clearly identify a markup language and its version. Schema declarations like DTDs or XML Schema are not mandatory in many XML applications
  2. Allow to mix two or more languages in a single document.

XML Namespaces allow to fully/uniquely qualify XML element and attribute names to prevent confusing two elements that have the same name but mean different things. Various XML vocabularies (languages/applications) may be mixed. E.g. in a standards compliant web browser like Firefox or Opera you may include SVG and MathML code with the same XHTML page. But then we can run into naming conflicts, i.e. different vocabularies (DTDs) can use the same names for elements ! Namespaces are a W3C standard since Jan 1999. That means that namespaces have been introduced after XML has been invented.

Since DTDs are not mandatory for most W3C XML languages, the W3C requires namespace definitions within root elements, e.g. XHTML and SVG must include a namespace declaration:

The following was mandatory in for valide XHMTL 1.x files: 

<html xmlns="http://www.w3.org/1999/xhtml">

Basically this statement says that within the html element all child elements belong to XHTML, unless they are explicitly part of another namespace.

The following example shows how to declare SVG files or fragments with an example (this is also valid for inclusion in HTML5) 

<svg id="circle" height="200" xmlns="http://www.w3.org/2000/svg">
      <circle id="greencircle" cx="30" cy="30" r="30" fill="green" />
</svg>

Standards involved

The Namespace standard:

Namespaces are identified with URIs

A URI is either a URL or a URN

Compound W3C documents

See also: The standards overview article. Most XML-based standards in education (e.g. IMS Content Packaging make heavy use of namespaces ! In addition most IMS and SCORM standards use XML Schema which are associated to XML contents via namespace declarations.

Namespaces

An example demonstrating the need for namespaces

Here is an XML fragment using title within a bibliography element: 

<book>
 <title>A true story</title>
 <description>A real cool publication</description>
</book>

A 2nd XML fragment uses title in a employees record: 

<record>
 <name>Miller</name> 
 <title>Dr. </title>
 <publications> ... </publications>
</record>

If these two XML fragments were added together, there would be a name conflict because both contain a <title>< element with different meaning. In one case we mean book title and in the other something like "none", PhD, etc.. A style-sheet would have to render these elements very differently. But we can solve this problem by adding prefixes, like this: 

<employees:record>
  <employees:name>Miller</employees:name>
  <employees:title>Dr. </employees:title>
  <employees:publications>
    <biblio:book>
      <biblio:title>A true story</biblio:title>
      <biblio:description>A real cool publication</biblio:description>
    </biblio:book>
  </employees:publications>
</employees:record>

A real world example

The The Open Packaging Format. Below is the content of an *.opf file that must be included within ePub "zip" file (a popular e-book format. It defines the structure of the book using assets and includes metadata.

OPF example copied with minor modifications from Wikipedia (nov 30 2010). 

<?xml version="1.0"?>
<package version="2.0" 
         xmlns="http://www.idpf.org/2007/opf" 
         unique-identifier="BookId">
 
  <metadata xmlns:dc="http://purl.org/dc/elements/1.1/" 
            xmlns:opf="http://www.idpf.org/2007/opf">
    <dc:title>Pride and Prejudice</dc:title>
    <dc:language>en</dc:language>
    <dc:identifier id="BookId" opf:scheme="ISBN">123456789X</dc:identifier>
    <dc:creator opf:file-as="Austen, Jane" opf:role="aut">Jane Austen</dc:creator>
  </metadata>
 
  <manifest>
    <item id="chapter1" href="chapter1.xhtml" 
          media-type="application/xhtml+xml"/>
    <item id="chapter2" href="chaptertwo.xhtml" 
          media-type="application/xhtml+xml"/>
    <item id="stylesheet" href="style.css" 
          media-type="text/css"/>
    <item id="ch1-pic" href="ch1-pic.png" 
          media-type="image/png"/>
    <item id="myfont" href="css/myfont.otf" 
          media-type="application/x-font-opentype"/>
    <item id="ncx" href="book.ncx" media-type="application/x-dtbncx+xml"/>
  </manifest>
 
  <spine toc="ncx">
    <itemref idref="chapter1" />
    <itemref idref="chapter2" />
  </spine>
 
  <guide>
    <reference type="loi" title="List Of Illustrations" 
               href="appendix.html#figures" />
  </guide>
 
</package>

This OPF file includes two namespaces:

Declaring namespaces

Formally speaking, an XML namespace is simply a collection of names (elements and attributes) of a markup vocabulary that can be uniquely identified

Procedure
  1. Create or identify a namespace identifier you wish to use: An XML namespace is identified by a unique URI reference, usually a URL.
  2. The URL does need not point to anything on the Internet. It is just used as a unique string, i.e. a name
  3. Therefore if some namespace URLs below are broken there is absolutely nothing to worry about. However, most namespace identifiers actually point to a real web page that either provides an explanation or at least information about the organization/author that created the namespace. This means that if you plan to create your own namespaces, you should use the name of any webpage over which you have control.
  4. Make a namespace declaration within the element that belongs to this namespace, i.e. map a prefix of your choice to a unique URI.

There are two major variants of namespace use: prefixed namespaces and default ones.

(1) Namespace declaration for use with a prefix: declaring a namespace that will require use of prefixes for each element 

 <prefix:element xmlns:prefix="URI">

Example: 

 <html:html xmlns:html="http://www.w3.org/1999/xhtml">
   <html:head> ..... </html:head>

Each element below html:html that uses prefix "html:" will belong to Xhtml. Any other will not.

(2) Default namespace: declaring a default namespace for element and its children. I.e. these will not be prefixed. 

 <element xmlns="URI"><

Example: 

 <html xmlns="http://www.w3.org/1999/xhtml">
   <head>.....</head>
   <body>.....

Scoping

"Scoping" means "where does a declaration apply ?

The scope of an XML namespace declaration extends from the beginning of the start-tag in which it appears to the end of the corresponding end-tag, including all children. Most frequently, namespaces are declared in the document root.

XHMTL fragment example
<?xml version="1.0"?>
  <html:html xmlns:html='http://www.w3.org/1999/xhtml'>
  <html:head>
    <html:title>Frobnostication</html:title>
  </html:head>
  <html:body>
    <html:p>
      Moved to<html:a href='http://frob.example.com'>here.</html:a>
    </html:p>
  </html:body>
</html:html>

The scope of the XHMTL namespace declaration goes from <html:html> to </html:html>.

Example with 2 namespaces (both use URNs instead of URLs)
<?xml version="1.0"?>
<!-- both namespace prefixes are available throughout the XML fragment -->
<bk:book xmlns:bk='urn:loc.gov:books'
         xmlns:isbn='urn:ISBN:0-395-36341-6'>
    <bk:title>Cheaper by the Dozen</bk:title>
    <isbn:number>1568491379</isbn:number>
</bk:book>

Default namespaces

If most elements in an XML document belonged to the same namespace, it would be ugly to prefix each element name. Instead define a default namespace that applies to all non-prefixed elements and attributes. Syntax: 

 <element xmlns="URI"> < ....

The default namespace applies to the element in which it was defined and all descendants of that element. But if a descendants has another default namespace defined on it, this new namespace definition overrides the previous one and becomes the default for that element and its descendants. Note that namespaces does not apply to attribute names ! This is a likely source of trouble for XSLT ...

XHTML default namespace example
<?xml version="1.0"?>
<!-- elements are in the HTML namespace by default -->
<html xmlns='http://www.w3.org/1999/xhtml'>
   <head>
      <title>Frobnostication</title>
   </head>
   <body>
      <p>Moved to <a href='http://frob.example.com'>here</a>.</p>
   </body>
</html>

Default namespace for a book vocabulary plus a namespace for ISBN example: 

  <!-- unprefixed element types are from "books" -->
  <book xmlns='urn:loc.gov:books'
        xmlns:isbn='urn:ISBN:0-395-36341-6'>
  <title>Cheaper by the Dozen</title>
  <isbn:number>1568491379</isbn:number>
  </book>
A larger example of namespace scoping

It includes some XHTML whose namespace is declared within the "p" element. 

<?xml version="1.0"?>
<!-- initially, the default namespace is "books" -->
<book xmlns='urn:loc.gov:books'
      xmlns:isbn='urn:ISBN:0-395-36341-6'>
   <title>Cheaper by the Dozen</title>
   <isbn:number>1568491379</isbn:number>
   <notes>
   <!-- make HTML the default namespace for some commentary -->
      <p xmlns='http://www.w3.org/1999/xhtml'>
         This is a <i>funny</i> book!
     </p>
   </notes>
</book>
XSLT namespace example

XSLT is a transformation language, i.e. programming language that allows to translate an XML content into another content (XML or other). XSLT instructions are prefixed with "xsl" here. Output produced is namespace-less here. See the XSLT tutorial for an introduction. 

<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="page">
  .....
  <html> <head> <title> <xsl:value-of select="title"/> </title> </head>
  <body bgcolor="#ffffff"> <xsl:apply-templates/> </body>
  </html>
</xsl:template>

<xsl:template match="title">
  <h1 align="center"> <xsl:apply-templates/> </h1>
</xsl:template>

<xsl:template match="content">
  <p align="center"> <xsl:apply-templates/> </p>
</xsl:template>

<xsl:template match="comment">
  <hr /> <xsl:apply-templates/>
  </xsl:template>
</xsl:stylesheet>

Validation of composite documents

Validating documents that contain different namespaces are called composite or compound documents and validation is not always easy since combined DTDs may not exist. A validation standard for composite W3C vocabularies is currently under preparation (but may not happen ...). Usually, combined documents are produced by server-side programs for delivery and they are just well-formed (not attached to DTDs or other schemas)

You also may write DTDs that validate your own compound documents as we demonstrate in the following example.

A DTD rule with an extra namespace example

In this example, the "a" element and the "description" attribute belongs to the default namespace, but the href and type attributes belong to the xlink namespace. We declare the namespace in the root element, but also could have done it just for the "el" element. Note: Xlinks do not work in IE7/8. 

<!ELEMENT link_list (el+)>
<!ATTLIST link_list xmlns:xlink CDATA #FIXED "http://www.w3.org/1999/xlink">
<!ELEMENT el (#PCDATA)>
<!ATTLIST el description CDATA #IMPLIED
          xlink:href CDATA #REQUIRED
          xlink:type CDATA #FIXED "simple" >

See the DTD tutorial for details.

An XML example file
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE link_list SYSTEM "link_list.dtd">
<?xml-stylesheet href="link_list.css" type="text/css" ?>
 <link_list xmlns:xlink="http://www.w3.org/1999/xlink">
    <el description="verified"
        xlink:type="simple"
        xlink:href="http://www.webster.ch/">Webster Geneva</el>
    <el xlink:href="http://www.webster.edu/"
        xlink:type="simple">Webster</el>
</link_list>

Namespaces for documents

Client-side XML web languages and namespaces overview

The W3C defines several Internet languages and for which namespace declarations are mandatory (even if you use them "standalone", i.e. not in composite documents.

Some W3C languages
Name Namespace URL Explanation
XSLT http://www.w3.org/1999/XSL/Transform XSL - Transformations
XSL-FO http://www.w3.org/1999/XSL/Format XSL - Formatting
XML Schema http://www.w3.org/2001/XMLSchema XML grammar definition language
SVG http://www.w3.org/2000/svg Scalable Vector Graphics
RDF http://www.w3.org/1999/02/22-rdf-syntax-ns Resource Description Format
SMIL 2.0 http://www.w3.org/2001/SMIL20/ Synchronized Multimedia Integration Lang.
VoiceXML 2.0 http://www.w3.org/2001/vxml Synthesized voice
XLink http://www.w3.org/1999/xlink" XML Linking Language
XForms http://www.w3.org/2002/xforms Next generation of HTML forms.
XHTML http://www.w3.org/1999/xhtml XML-based HTML variant
MathML http://www.w3.org/1998/Math/MathML Mathematical markup language


Some of these languages (e.g. SMIL, MathML, SVG, X3D) need special clients for display. Others are transducers or helpers, i.e. are used to define, style, transform and process XML contents

RDF namespace

RDF-based languages are very prolific and add to the complexity of semantic web initiatives

See 100 most common RDF namespaces

Other Document standards

Each of the following usually packages a document as zip file. Inside the zip, you will find several files using several XML languages.

Compound documents

Combining various content delivery formats is the future (also on cell phones). For example, XHTML-formatted content can be augmented by SVG objects or mathematical formula.

Examples of possible Compound Document profiles
  • XHTML + SVG + MathML
  • XHTML + SMIL
  • XHTML + XForms
  • XHTML + VoiceML

The W3C is working on a generic Compound Document by Reference Framework (CDRF) that defines a language-independent processing model for combining arbitrary document formats ...

Web browser caveats
  • IE doesn't support natively most XML W3C "content" languages (e.g. SVG, MathML), but implements a version of SMIL, called "Timed Text". Firefox supports static SVG and MathML. Both implement RSS

Workarounds:

  • Use a browser that is more advanced (e.g. Firefox, Opera, Chrome) or specialized players (e.g. Realplayer for SMIL)
  • For HTML + SVG + MathML, use HTML5
  • Call your files *.xml (often helps if you use IE)
  • For some formats you may install plugins or extensions in your web browser and then use a more indirect method to assemble contents, i.e. <object> or <iframe>. This will work with most browsers if you have the right plugin (SVG in this case) installed.
<iframe src="hello-svg.svg" height="300" width="80%" frameborder="0">
... Sorry you need an SVG plugin ...
</iframe><

XHTML + other vocabularies

XHTML / MathML example
<?xml version="1.0" encoding="iso-8859-1"?>
<xhtml:html xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <xhtml:body>
    <xhtml:h1>A Compound Document</xhtml:h1>
    <xhtml:p>A simple formula using MathML in XHTML.</xhtml:p>
    <mathml:math xmlns:mathml="http://www.w3.org/1998/Math/MathML">
      <mathml:mrow>
         <mathml:msqrt> <mathml:mn>49</mathml:mn> </mathml:msqrt>
         <mathml:mo>=</mathml:mo>
         <mathml:mn>7</mathml:mn>
       </mathml:mrow>
     </mathml:math>
  </xhtml:body>
</xhtml:html>

MathML doesn't natively work with IE 6/7/8. But there are workarounds. See the MathML article for some more information about MathML and dealing with IE.

Xlink example

XLink was supposed to replace all linking constructs in the W3C languages. It is adopted by SVG, X3D, but not by XHTML 2 which introduces its own linking constructs. XML-capable browsers are also supposed to implement this (Firefox, but not IE)

Example - Story grammar that implements XLink for an A element
<?xml version="1.0" encoding="ISO-8859-1" ?>
<STORY xmlns:xlink="http://www.w3.org/1999/xlink">
  <Title>The Webmaster</Title>
  .....
  <INFOS> <Date>30 octobre 2003 - </Date>
  <Author>DKS - </Author>
  <A xlink:href=http://jigsaw.w3.org/css-validator/check/referer
     xlink:type="simple">CSS Validator</A>
   </INFOS>
</STORY>
SVG example
  • Most browsers (i.e. all major browser except IE8) can handle SVG. However, some only implement SVG 1.0 and most only static SVG. As of, only Opera implemented the so-called SMILE tags.
  • Alternatively, use HTML and read the using SVG with HTML5 tutorial

XHTML with embedded SVG tags (tested with Firefox) 

<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" >

<html xmlns="http://www.w3.org/1999/xhtml"  
      xmlns:svg="http://www.w3.org/2000/svg">
 <head>
  <title>SVG within XHTML Demo</title>
 </head>
 <body>
  <h1>SVG within XHTML Demo</h1>

  <p> You can embed SVG into XHTML, provided that your browser
  natively implements SVG. E.g. Firefox 1.5+ supports most of static
  SVG.  </p>

  The SVG part starts below <hr />

  <svg xmlns="http://www.w3.org/2000/svg" version="1.1" 
       width="400" height="300">
   <!-- a small rectangle -->
   <rect x="50" y="50" rx="5" ry="5" width="300" height="100"
   	 style="fill:#CCCCFF;stroke:#000099"/>
   
   <!-- a text in the same place -->
   <text x="55" y="90" style="stroke:#000099;fill:#000099;font-size:24;">
    HELLO dear reader
   </text>

  </svg>
  <hr />
  The SVG part ended above
</body>
</html>

SVG within HTML5. This also should work with very old browsers (e.g. IE 6 and FF 1) plus the now unavailable SVG plugin from Adobe. 

<!DOCTYPE html>
<html>
  <head> <title>HELLO SVG with an iframe</title> </head>
  <body>
     <h1>HELLO SVG with an iframe</h1>
        Here is an embeded SVG scene using iframe. 
	<iframe src="hello-svg.svg" height="200" width="80%" frameborder="0">
	</iframe>
     <hr>
  </body> 
</html>

In the following example, the SVG file is a standard stand-alone SVG file 

<?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN"
          "http://www.w3.org/TR/2001/PR-SVG-20010719/DTD/svg10.dtd">
<svg xmlns="http://www.w3.org/2000/svg">
   <rect x="50" y="50" rx="5" ry="5" width="300" height="100"
         style="fill:#CCCCFF;stroke:#000099"/>
   <text x="55" y="90" style="stroke:#000099;fill:#000099;font-size:24;">
   HELLO dear reader
   </text>
</svg>

Combining XHTML with your XML

It sometimes can be practical to combine your own XML contents with XHTML, because HTML offers easy-to-use functionality like image inclusions or links. Note however that in practice this feature is not often used since:

  • XSLT stylesheets allow transformations of XML data into XHTML. The stylesheet will contain the extra HTML and the result displayed usually will be all HTML and will be easier to manage with CSS.
  • The way browsers implement this feature is not really stable
  • Since HTML5 is now dominant, people cannot remember the potential of XHTML.
XHTML with some XML included, using CSS for styling
  • Tested with Firefox 2.x (works) and IE 7 (CSS doesn't work, I don't know why ...)

Procedure:

  1. Define a namespace for the included XML content
  2. Attach a CSS stylesheet with an XML processor instruction. Else, users will not see the contents of your XML.
  3. Your file must be understood as "XML", e.g. call it something.xhtml or something.xht or something.xml. If you use IE7/8 it must be something.xml, since IE doesn't support XHTML). Do not call your file something.html or something.htm !!

XHTML with some cooking XML included (file cooking.xhtml): 

<?xml version="1.0" ?>
<?xml-stylesheet type="text/css" href="cooking.css"?>

<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:re="http://webster.unige.ch/coap21/dolores">
  <head>
    <title>A Compound XHTML-XML Document</title>
    <!-- this should work with IE but doesn't, maybe IE6 ? -->
    <link href="dolores.css" type="text/css" rel="stylesheet"/>
  </head>

  <body>

    <h1>A Compound XHTML-XML Document</h1>

    <p>Contains a cooking recipee written down by R. Dolores for a
    COAP 2180 CSS exercise. Everything below the line is XML styled
    with a CSS stylesheet</p> <hr/>

  <re:recipe>
    <re:recipe_head>
      <re:recipe_name>Cold Salmon in Creamy Spiced Sauce</re:recipe_name>
      <re:recipe_author>Hilaire Walden</re:recipe_author>
      
      <re:meal_type>Fish and Shellfish</re:meal_type>
    </re:recipe_head>
    
    <re:recipe_body>
      <re:ingredients>
	<re:ingredient>1/2 teaspoon finely crushed cumin seeds</re:ingredient>
	<re:ingredient>1 teaspoon chilli powder</re:ingredient>
	<re:ingredient>salt and freshly ground black pepper</re:ingredient>
	
	<re:ingredient>2 tablespoons olive oil</re:ingredient>
	<re:ingredient>2 cloves garlic, crushed</re:ingredient>
	<re:ingredient>1.25 cm (1/2 in) fresh ginger root, finely
	chopped</re:ingredient>
	<re:ingredient>4 pieces salmon fillet, skinned</re:ingredient>
	<re:ingredient>125 ml (4 fl oz / 1/2 cup) double (heavy)
	cream</re:ingredient>
	<re:ingredient>250 ml (8 fl oz / 1 cup) thick plain
	yogurt</re:ingredient>
	
	<re:ingredient>large pinch of saffron threads, toasted and
	crushed</re:ingredient>
  	<re:ingredient>seeds from 6 cardamom pods, toasted and finely
  	crushed</re:ingredient>
	<re:ingredient>salt</re:ingredient>
  	<re:ingredient>coriander (cilantro) to garnish</re:ingredient>
      </re:ingredients>
      <re:directions>
	<re:direction>Mix together the cumin seeds, chilli powder and
	pepper and rub into the fish.</re:direction>
	<re:direction>Heat the oil in a frying pan, add the garlic and
	ginger and heat until they sizzle.</re:direction>
	<re:direction>Add the salmon fillets and fry until they start
	to colour (about 15-20 seconds on each side).</re:direction>
	<re:direction>Stir in the cream, yogurt, saffron, cardamom and
	salt.</re:direction>
	<re:direction>Adjust the heat so that the sauce is just
	bubbling and cook, turning the fish once, until the flesh just
	flakes when tested with the point of a sharp knife (about 3-4
	minutes each side).</re:direction>
	<re:direction>Transfer the fish to a shallow dish. Boil the
	sauce until it has reduced and thickened, pour over the fish
	and leave to cool.</re:direction>
        <re:direction>Cover the dish and chill until 15-20 minutes
        before serving.</re:direction>
	<re:direction>Garnish with coriander (cilantro).</re:direction>
	</re:directions>
     </re:recipe_body>

     <re:recipe_footer>
     <re:serving>4</re:serving>
     <re:preparation_time>15 minutes</re:preparation_time>
     </re:recipe_footer>

     <re:document_info>
       <re:document_author>Hilaire Walden</re:document_author>
       <re:date_updated>21/01/07</re:date_updated>
       <re:source>Easy to Cook, Hot &amp; Spicy</re:source>
     </re:document_info>
  </re:recipe>
  </body>
</html>

Combining your XML with XHTML

Works with Firefox 1x/2x and IE7 (probably also with IE6).

  • An HTML namespace is declared in the root element and we use it twice (for the img and a tags).
  • Btw this is a trick to get around non-implementation of the xlink standard in IE.
XML plus XHTML
<?xml version="1.0" ?>
<?xml-stylesheet href="xml_plus_xhtml.css" type="text/css"?>
<page xmlns:html="http://www.w3.org/1999/xhtml" updated="jan 2007">
 <title>Hello friend</title>
 <list>
   <!-- we use an HTML tag below to include a picture -->
   <html:img src="photo.jpg"/>
   <item price="10"> White plate </item> 
   <item price="20"> Gold plate </item> 
   <item price="15"> Silver plate </item> 
 </list>

 <comment> Written by <html:a href="http://tecfa.unige.ch/DKS">DKS/Tecfa</html:a>
 , feb 2007 </comment>
</page>

XSLT transformations of compound documents

Transforming XML files that include namespace (including just default namespaces that do not use prefixes) requires that you prefix each XPath "component". For more information, see:

Retrieved from "https://edutechwiki.unige.ch/mediawiki/index.php?title=XML_namespace&oldid=56088"