namespaces.html revision 595978c978070456dac57acff4dcfd9039af0ce4
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
2<html>
3<head>
4<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
5<link rel="SHORTCUT ICON" href="/favicon.ico">
6<style type="text/css"><!--
7TD {font-family: Verdana,Arial,Helvetica}
8BODY {font-family: Verdana,Arial,Helvetica; margin-top: 2em; margin-left: 0em; margin-right: 0em}
9H1 {font-family: Verdana,Arial,Helvetica}
10H2 {font-family: Verdana,Arial,Helvetica}
11H3 {font-family: Verdana,Arial,Helvetica}
12A:link, A:visited, A:active { text-decoration: underline }
13--></style>
14<title>Namespaces</title>
15</head>
16<body bgcolor="#8b7765" text="#000000" link="#000000" vlink="#000000">
17<table border="0" width="100%" cellpadding="5" cellspacing="0" align="center"><tr>
18<td width="180">
19<a href="http://www.gnome.org/"><img src="gnome2.png" alt="Gnome2 Logo"></a><a href="http://www.w3.org/Status"><img src="w3c.png" alt="W3C Logo"></a><a href="http://www.redhat.com/"><img src="redhat.gif" alt="Red Hat Logo"></a><div align="left"><a href="http://xmlsoft.org/"><img src="Libxml2-Logo-180x168.gif" alt="Made with Libxml2 Logo"></a></div>
20</td>
21<td><table border="0" width="90%" cellpadding="2" cellspacing="0" align="center" bgcolor="#000000"><tr><td><table width="100%" border="0" cellspacing="1" cellpadding="3" bgcolor="#fffacd"><tr><td align="center">
22<h1>The XML C library for Gnome</h1>
23<h2>Namespaces</h2>
24</td></tr></table></td></tr></table></td>
25</tr></table>
26<table border="0" cellpadding="4" cellspacing="0" width="100%" align="center"><tr><td bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="2" width="100%"><tr>
27<td valign="top" width="200" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td>
28<table width="100%" border="0" cellspacing="1" cellpadding="3">
29<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Main Menu</b></center></td></tr>
30<tr><td bgcolor="#fffacd"><ul>
31<li><a href="index.html">Home</a></li>
32<li><a href="intro.html">Introduction</a></li>
33<li><a href="FAQ.html">FAQ</a></li>
34<li><a href="docs.html">Documentation</a></li>
35<li><a href="bugs.html">Reporting bugs and getting help</a></li>
36<li><a href="help.html">How to help</a></li>
37<li><a href="downloads.html">Downloads</a></li>
38<li><a href="news.html">News</a></li>
39<li><a href="XMLinfo.html">XML</a></li>
40<li><a href="XSLT.html">XSLT</a></li>
41<li><a href="python.html">Python and bindings</a></li>
42<li><a href="architecture.html">libxml architecture</a></li>
43<li><a href="tree.html">The tree output</a></li>
44<li><a href="interface.html">The SAX interface</a></li>
45<li><a href="xmldtd.html">Validation &amp; DTDs</a></li>
46<li><a href="xmlmem.html">Memory Management</a></li>
47<li><a href="encoding.html">Encodings support</a></li>
48<li><a href="xmlio.html">I/O Interfaces</a></li>
49<li><a href="catalog.html">Catalog support</a></li>
50<li><a href="library.html">The parser interfaces</a></li>
51<li><a href="entities.html">Entities or no entities</a></li>
52<li><a href="namespaces.html">Namespaces</a></li>
53<li><a href="upgrade.html">Upgrading 1.x code</a></li>
54<li><a href="threads.html">Thread safety</a></li>
55<li><a href="DOM.html">DOM Principles</a></li>
56<li><a href="example.html">A real example</a></li>
57<li><a href="contribs.html">Contributions</a></li>
58<li><a href="tutorial/index.html">Tutorial</a></li>
59<li>
60<a href="xml.html">flat page</a>, <a href="site.xsl">stylesheet</a>
61</li>
62</ul></td></tr>
63</table>
64<table width="100%" border="0" cellspacing="1" cellpadding="3">
65<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>API Indexes</b></center></td></tr>
66<tr><td bgcolor="#fffacd">
67<form action="search.php" enctype="application/x-www-form-urlencoded" method="GET">
68<input name="query" type="TEXT" size="20" value=""><input name="submit" type="submit" value="Search ...">
69</form>
70<ul>
71<li><a href="APIchunk0.html">Alphabetic</a></li>
72<li><a href="APIconstructors.html">Constructors</a></li>
73<li><a href="APIfunctions.html">Functions/Types</a></li>
74<li><a href="APIfiles.html">Modules</a></li>
75<li><a href="APIsymbols.html">Symbols</a></li>
76</ul>
77</td></tr>
78</table>
79<table width="100%" border="0" cellspacing="1" cellpadding="3">
80<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Related links</b></center></td></tr>
81<tr><td bgcolor="#fffacd"><ul>
82<li><a href="http://mail.gnome.org/archives/xml/">Mail archive</a></li>
83<li><a href="http://xmlsoft.org/XSLT/">XSLT libxslt</a></li>
84<li><a href="http://phd.cs.unibo.it/gdome2/">DOM gdome2</a></li>
85<li><a href="http://www.aleksey.com/xmlsec/">XML-DSig xmlsec</a></li>
86<li><a href="ftp://xmlsoft.org/">FTP</a></li>
87<li><a href="http://www.fh-frankfurt.de/~igor/projects/libxml/">Windows binaries</a></li>
88<li><a href="http://garypennington.net/libxml2/">Solaris binaries</a></li>
89<li><a href="http://www.zveno.com/open_source/libxml2xslt.html">MacOsX binaries</a></li>
90<li><a href="http://sourceforge.net/projects/libxml2-pas/">Pascal bindings</a></li>
91<li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml&product=libxml2">Bug Tracker</a></li>
92</ul></td></tr>
93</table>
94</td></tr></table></td>
95<td valign="top" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%"><tr><td><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table border="0" cellpadding="3" cellspacing="1" width="100%"><tr><td bgcolor="#fffacd">
96<p>The libxml library implements <a href="http://www.w3.org/TR/REC-xml-names/">XML namespaces</a> support by
97recognizing namespace constructs in the input, and does namespace lookup
98automatically when building the DOM tree. A namespace declaration is
99associated with an in-memory structure and all elements or attributes within
100that namespace point to it. Hence testing the namespace is a simple and fast
101equality operation at the user level.</p>
102<p>I suggest that people using libxml use a namespace, and declare it in the
103root element of their document as the default namespace. Then they don't need
104to use the prefix in the content but we will have a basis for future semantic
105refinement and  merging of data from different sources. This doesn't increase
106the size of the XML output significantly, but significantly increases its
107value in the long-term. Example:</p>
108<pre>&lt;mydoc xmlns=&quot;http://mydoc.example.org/schemas/">;
109   &lt;elem1&gt;...&lt;/elem1&gt;
110   &lt;elem2&gt;...&lt;/elem2&gt;
111&lt;/mydoc&gt;</pre>
112<p>The namespace value has to be an absolute URL, but the URL doesn't have to
113point to any existing resource on the Web. It will bind all the element and
114attributes with that URL. I suggest to use an URL within a domain you
115control, and that the URL should contain some kind of version information if
116possible. For example, <code>&quot;http://www.gnome.org/gnumeric/1.0/";</code> is a
117good namespace scheme.</p>
118<p>Then when you load a file, make sure that a namespace carrying the
119version-independent prefix is installed on the root element of your document,
120and if the version information don't match something you know, warn the user
121and be liberal in what you accept as the input. Also do *not* try to base
122namespace checking on the prefix value. &lt;foo:text&gt; may be exactly the
123same as &lt;bar:text&gt; in another document. What really matters is the URI
124associated with the element or the attribute, not the prefix string (which is
125just a shortcut for the full URI). In libxml, element and attributes have an
126<code>ns</code> field pointing to an xmlNs structure detailing the namespace
127prefix and its URI.</p>
128<p>@@Interfaces@@</p>
129<p>@@Examples@@</p>
130<p>Usually people object to using namespaces together with validity checking.
131I will try to make sure that using namespaces won't break validity checking,
132so even if you plan to use or currently are using validation I strongly
133suggest adding namespaces to your document. A default namespace scheme
134<code>xmlns=&quot;http://....";</code> should not break validity even on less
135flexible parsers. Using namespaces to mix and differentiate content coming
136from multiple DTDs will certainly break current validation schemes. I will
137try to provide ways to do this, but this may not be portable or
138standardized.</p>
139<p><a href="bugs.html">Daniel Veillard</a></p>
140</td></tr></table></td></tr></table></td></tr></table></td>
141</tr></table></td></tr></table>
142</body>
143</html>
144