Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / libxml2 / af43f63aaabf0dc4b4a070773875d0927da3d8a2 / . / doc / python.html
blob: f440b2db2d22a71e608fcec92420dc9d8c3d993e [file] [log] [blame]
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]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 content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
5<style type="text/css"><!--
Daniel Veillard373a4752002-02-21 14:46:29 +0000[diff] [blame]6TD {font-family: Verdana,Arial,Helvetica}
7BODY {font-family: Verdana,Arial,Helvetica; margin-top: 2em; margin-left: 0em; margin-right: 0em}
8H1 {font-family: Verdana,Arial,Helvetica}
9H2 {font-family: Verdana,Arial,Helvetica}
10H3 {font-family: Verdana,Arial,Helvetica}
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]11A:link, A:visited, A:active { text-decoration: underline }
12--></style>
13<title>Python and bindings</title>
14</head>
15<body bgcolor="#8b7765" text="#000000" link="#000000" vlink="#000000">
16<table border="0" width="100%" cellpadding="5" cellspacing="0" align="center"><tr>
17<td width="180">
18<a href="http://www.gnome.org/"><img src="smallfootonly.gif" alt="Gnome 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>
19</td>
20<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">
21<h1>The XML C library for Gnome</h1>
22<h2>Python and bindings</h2>
23</td></tr></table></td></tr></table></td>
24</tr></table>
25<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>
26<td valign="top" width="200" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td>
27<table width="100%" border="0" cellspacing="1" cellpadding="3">
28<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Main Menu</b></center></td></tr>
29<tr><td bgcolor="#fffacd"><ul>
30<li><a href="index.html">Home</a></li>
31<li><a href="intro.html">Introduction</a></li>
32<li><a href="FAQ.html">FAQ</a></li>
33<li><a href="docs.html">Documentation</a></li>
34<li><a href="bugs.html">Reporting bugs and getting help</a></li>
35<li><a href="help.html">How to help</a></li>
36<li><a href="downloads.html">Downloads</a></li>
37<li><a href="news.html">News</a></li>
38<li><a href="XMLinfo.html">XML</a></li>
39<li><a href="XSLT.html">XSLT</a></li>
40<li><a href="python.html">Python and bindings</a></li>
41<li><a href="architecture.html">libxml architecture</a></li>
42<li><a href="tree.html">The tree output</a></li>
43<li><a href="interface.html">The SAX interface</a></li>
44<li><a href="xmldtd.html">Validation &amp; DTDs</a></li>
45<li><a href="xmlmem.html">Memory Management</a></li>
46<li><a href="encoding.html">Encodings support</a></li>
47<li><a href="xmlio.html">I/O Interfaces</a></li>
48<li><a href="catalog.html">Catalog support</a></li>
49<li><a href="library.html">The parser interfaces</a></li>
50<li><a href="entities.html">Entities or no entities</a></li>
51<li><a href="namespaces.html">Namespaces</a></li>
52<li><a href="upgrade.html">Upgrading 1.x code</a></li>
53<li><a href="threads.html">Thread safety</a></li>
54<li><a href="DOM.html">DOM Principles</a></li>
55<li><a href="example.html">A real example</a></li>
56<li><a href="contribs.html">Contributions</a></li>
57<li>
58<a href="xml.html">flat page</a>, <a href="site.xsl">stylesheet</a>
59</li>
60</ul></td></tr>
61</table>
62<table width="100%" border="0" cellspacing="1" cellpadding="3">
63<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>API Indexes</b></center></td></tr>
64<tr><td bgcolor="#fffacd"><ul>
65<li><a href="APIchunk0.html">Alphabetic</a></li>
66<li><a href="APIconstructors.html">Constructors</a></li>
67<li><a href="APIfunctions.html">Functions/Types</a></li>
68<li><a href="APIfiles.html">Modules</a></li>
69<li><a href="APIsymbols.html">Symbols</a></li>
70</ul></td></tr>
71</table>
72<table width="100%" border="0" cellspacing="1" cellpadding="3">
73<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Related links</b></center></td></tr>
74<tr><td bgcolor="#fffacd"><ul>
75<li><a href="http://mail.gnome.org/archives/xml/">Mail archive</a></li>
76<li><a href="http://xmlsoft.org/XSLT/">XSLT libxslt</a></li>
77<li><a href="http://phd.cs.unibo.it/gdome2/">DOM gdome2</a></li>
78<li><a href="ftp://xmlsoft.org/">FTP</a></li>
79<li><a href="http://www.fh-frankfurt.de/~igor/projects/libxml/">Windows binaries</a></li>
80<li><a href="http://garypennington.net/libxml2/">Solaris binaries</a></li>
81<li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml">Bug Tracker</a></li>
82</ul></td></tr>
83</table>
84</td></tr></table></td>
85<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">
86<p>There is a number of language bindings and wrappers available for libxml2,
87the list below is not exhaustive. Please contact the <a href="http://mail.gnome.org/mailman/listinfo/xml-bindings">xml-bindings@gnome.org</a>
88(<a href="http://mail.gnome.org/archives/xml-bindings/">archives</a>) in
89order to get updates to this list or to discuss the specific topic of libxml2
90or libxslt wrappers or bindings:</p>
91<ul>
92<li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]93<a href="mailto:ari@lusis.org">Ari Johnson</a> provides a C++ wrapper
94 for libxml:<br>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]95 Website: <a href="http://lusis.org/~ari/xml++/">http://lusis.org/~ari/xml++/</a><br>
96 Download: <a href="http://lusis.org/~ari/xml++/libxml++.tar.gz">http://lusis.org/~ari/xml++/libxml++.tar.gz</a>
97</li>
98<li>There is another <a href="http://libgdome-cpp.berlios.de/">C++ wrapper
99 based on the gdome2 </a>bindings maintained by Tobias Peters.</li>
100<li>
101<a href="http://mail.gnome.org/archives/xml/2001-March/msg00014.html">Matt
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]102 Sergeant</a> developped <a href="http://axkit.org/download/">XML::LibXSLT</a>, a perl wrapper for
103 libxml2/libxslt as part of the <a href="http://axkit.com/">AxKit XML
104 application server</a>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]105</li>
106<li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]107<a href="mailto:dkuhlman@cutter.rexx.com">Dave Kuhlman</a> provides and
108 earlier version of the libxml/libxslt <a href="http://www.rexx.com/~dkuhlman">wrappers for Python</a>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]109</li>
110<li>Petr Kozelka provides <a href="http://sourceforge.net/projects/libxml2-pas">Pascal units to glue
111 libxml2</a> with Kylix, Delphi and other Pascal compilers</li>
112<li>Wai-Sun &quot;Squidster&quot; Chia provides <a href="http://www.rubycolor.org/arc/redist/">bindings for Ruby</a> and
113 libxml2 bindings are also available in Ruby through the <a href="http://libgdome-ruby.berlios.de/">libgdome-ruby</a> module
114 maintained by Tobias Peters.</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]115<li>Steve Ball and contributors maintains <a href="http://tclxml.sourceforge.net/">libxml2 and libxslt bindings for
Daniel Veillardb9e469a2002-02-21 12:08:42 +0000[diff] [blame]116 Tcl</a>
117</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]118<li>There is support for libxml2 in the DOM module of PHP.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]119</ul>
120<p>The distribution includes a set of Python bindings, which are garanteed to
121be maintained as part of the library in the future, though the Python
Daniel Veillard0b79dfe2002-02-23 13:02:31 +0000[diff] [blame]122interface have not yet reached the maturity of the C API.</p>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]123<p>To install the Python bindings there are 2 options:</p>
Daniel Veillard0b79dfe2002-02-23 13:02:31 +0000[diff] [blame]124<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]125<li>If you use an RPM based distribution, simply install the <a href="http://rpmfind.net/linux/rpm2html/search.php?query=libxml2-python">libxml2-python
126 RPM</a> (and if needed the <a href="http://rpmfind.net/linux/rpm2html/search.php?query=libxslt-python">libxslt-python
127 RPM</a>).</li>
128<li>Otherwise use the <a href="ftp://xmlsoft.org/python/">libxml2-python
129 module distribution</a> corresponding to your installed version of
130 libxml2 and libxslt. Note that to install it you will need both libxml2
131 and libxslt installed and run &quot;python setup.py build install&quot; in the
132 module tree.</li>
Daniel Veillard0b79dfe2002-02-23 13:02:31 +0000[diff] [blame]133</ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]134<p>The distribution includes a set of examples and regression tests for the
135python bindings in the <code>python/tests</code> directory. Here are some
136excepts from those tests:</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]137<h3>tst.py:</h3>
138<p>This is a basic test of the file interface and DOM navigation:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]139<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]140
141doc = libxml2.parseFile(&quot;tst.xml&quot;)
142if doc.name != &quot;tst.xml&quot;:
143 print &quot;doc.name failed&quot;
144 sys.exit(1)
145root = doc.children
146if root.name != &quot;doc&quot;:
147 print &quot;root.name failed&quot;
148 sys.exit(1)
149child = root.children
150if child.name != &quot;foo&quot;:
151 print &quot;child.name failed&quot;
152 sys.exit(1)
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]153doc.freeDoc()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]154<p>The Python module is called libxml2, parseFile is the equivalent of
155xmlParseFile (most of the bindings are automatically generated, and the xml
156prefix is removed and the casing convention are kept). All node seen at the
157binding level share the same subset of accesors:</p>
158<ul>
159<li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]160<code>name</code> : returns the node name</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]161<li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]162<code>type</code> : returns a string indicating the node
163 typ<code>e</code>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]164</li>
165<li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]166<code>content</code> : returns the content of the node, it is based on
167 xmlNodeGetContent() and hence is recursive.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]168<li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]169<code>parent</code> , <code>children</code>, <code>last</code>,
170 <code>next</code>, <code>prev</code>, <code>doc</code>,
171 <code>properties</code>: pointing to the associated element in the tree,
172 those may return None in case no such link exists.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]173</ul>
174<p>Also note the need to explicitely deallocate documents with freeDoc() .
175Reference counting for libxml2 trees would need quite a lot of work to
176function properly, and rather than risk memory leaks if not implemented
177correctly it sounds safer to have an explicit function to free a tree. The
178wrapper python objects like doc, root or child are them automatically garbage
179collected.</p>
180<h3>validate.py:</h3>
181<p>This test check the validation interfaces and redirection of error
182messages:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]183<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]184
185#desactivate error messages from the validation
186def noerr(ctx, str):
187 pass
188
189libxml2.registerErrorHandler(noerr, None)
190
191ctxt = libxml2.createFileParserCtxt(&quot;invalid.xml&quot;)
192ctxt.validate(1)
193ctxt.parseDocument()
194doc = ctxt.doc()
195valid = ctxt.isValid()
196doc.freeDoc()
197if valid != 0:
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]198 print &quot;validity chec failed&quot;</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]199<p>The first thing to notice is the call to registerErrorHandler(), it
200defines a new error handler global to the library. It is used to avoid seeing
201the error messages when trying to validate the invalid document.</p>
202<p>The main interest of that test is the creation of a parser context with
203createFileParserCtxt() and how the behaviour can be changed before calling
204parseDocument() . Similary the informations resulting from the parsing phase
205are also available using context methods.</p>
206<p>Contexts like nodes are defined as class and the libxml2 wrappers maps the
207C function interfaces in terms of objects method as much as possible. The
208best to get a complete view of what methods are supported is to look at the
209libxml2.py module containing all the wrappers.</p>
210<h3>push.py:</h3>
211<p>This test show how to activate the push parser interface:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]212<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]213
214ctxt = libxml2.createPushParser(None, &quot;&lt;foo&quot;, 4, &quot;test.xml&quot;)
215ctxt.parseChunk(&quot;/&gt;&quot;, 2, 1)
216doc = ctxt.doc()
217
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]218doc.freeDoc()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]219<p>The context is created with a speciall call based on the
220xmlCreatePushParser() from the C library. The first argument is an optional
221SAX callback object, then the initial set of data, the lenght and the name of
222the resource in case URI-References need to be computed by the parser.</p>
223<p>Then the data are pushed using the parseChunk() method, the last call
224setting the thrird argument terminate to 1.</p>
225<h3>pushSAX.py:</h3>
226<p>this test show the use of the event based parsing interfaces. In this case
227the parser does not build a document, but provides callback information as
228the parser makes progresses analyzing the data being provided:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]229<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]230log = &quot;&quot;
231
232class callback:
233 def startDocument(self):
234 global log
235 log = log + &quot;startDocument:&quot;
236
237 def endDocument(self):
238 global log
239 log = log + &quot;endDocument:&quot;
240
241 def startElement(self, tag, attrs):
242 global log
243 log = log + &quot;startElement %s %s:&quot; % (tag, attrs)
244
245 def endElement(self, tag):
246 global log
247 log = log + &quot;endElement %s:&quot; % (tag)
248
249 def characters(self, data):
250 global log
251 log = log + &quot;characters: %s:&quot; % (data)
252
253 def warning(self, msg):
254 global log
255 log = log + &quot;warning: %s:&quot; % (msg)
256
257 def error(self, msg):
258 global log
259 log = log + &quot;error: %s:&quot; % (msg)
260
261 def fatalError(self, msg):
262 global log
263 log = log + &quot;fatalError: %s:&quot; % (msg)
264
265handler = callback()
266
267ctxt = libxml2.createPushParser(handler, &quot;&lt;foo&quot;, 4, &quot;test.xml&quot;)
268chunk = &quot; url='tst'&gt;b&quot;
269ctxt.parseChunk(chunk, len(chunk), 0)
270chunk = &quot;ar&lt;/foo&gt;&quot;
271ctxt.parseChunk(chunk, len(chunk), 1)
272
Daniel Veillardfcbfa2d2002-02-21 17:54:27 +0000[diff] [blame]273reference = &quot;startDocument:startElement foo {'url': 'tst'}:&quot; + \
274 &quot;characters: bar:endElement foo:endDocument:&quot;
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]275if log != reference:
276 print &quot;Error got: %s&quot; % log
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]277 print &quot;Exprected: %s&quot; % reference</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]278<p>The key object in that test is the handler, it provides a number of entry
279points which can be called by the parser as it makes progresses to indicate
280the information set obtained. The full set of callback is larger than what
281the callback class in that specific example implements (see the SAX
282definition for a complete list). The wrapper will only call those supplied by
283the object when activated. The startElement receives the names of the element
284and a dictionnary containing the attributes carried by this element.</p>
285<p>Also note that the reference string generated from the callback shows a
286single character call even though the string &quot;bar&quot; is passed to the parser
287from 2 different call to parseChunk()</p>
288<h3>xpath.py:</h3>
289<p>This is a basic test of XPath warppers support</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]290<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]291
292doc = libxml2.parseFile(&quot;tst.xml&quot;)
293ctxt = doc.xpathNewContext()
294res = ctxt.xpathEval(&quot;//*&quot;)
295if len(res) != 2:
296 print &quot;xpath query: wrong node set size&quot;
297 sys.exit(1)
298if res[0].name != &quot;doc&quot; or res[1].name != &quot;foo&quot;:
299 print &quot;xpath query: wrong node set value&quot;
300 sys.exit(1)
301doc.freeDoc()
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]302ctxt.xpathFreeContext()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]303<p>This test parses a file, then create an XPath context to evaluate XPath
304expression on it. The xpathEval() method execute an XPath query and returns
305the result mapped in a Python way. String and numbers are natively converted,
306and node sets are returned as a tuple of libxml2 Python nodes wrappers. Like
307the document, the XPath context need to be freed explicitely, also not that
308the result of the XPath query may point back to the document tree and hence
309the document must be freed after the result of the query is used.</p>
310<h3>xpathext.py:</h3>
311<p>This test shows how to extend the XPath engine with functions written in
312python:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]313<pre>import libxml2
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]314
315def foo(ctx, x):
316 return x + 1
317
318doc = libxml2.parseFile(&quot;tst.xml&quot;)
319ctxt = doc.xpathNewContext()
320libxml2.registerXPathFunction(ctxt._o, &quot;foo&quot;, None, foo)
321res = ctxt.xpathEval(&quot;foo(1)&quot;)
322if res != 2:
323 print &quot;xpath extension failure&quot;
324doc.freeDoc()
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]325ctxt.xpathFreeContext()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]326<p>Note how the extension function is registered with the context (but that
327part is not yet finalized, ths may change slightly in the future).</p>
328<h3>tstxpath.py:</h3>
329<p>This test is similar to the previousone but shows how the extension
330function can access the XPath evaluation context:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]331<pre>def foo(ctx, x):
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]332 global called
333
334 #
335 # test that access to the XPath evaluation contexts
336 #
337 pctxt = libxml2.xpathParserContext(_obj=ctx)
338 ctxt = pctxt.context()
339 called = ctxt.function()
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]340 return x + 1</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]341<p>All the interfaces around the XPath parser(or rather evaluation) context
342are not finalized, but it should be sufficient to do contextual work at the
343evaluation point.</p>
344<h3>Memory debugging:</h3>
345<p>last but not least, all tests starts with the following prologue:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]346<pre>#memory debug specific
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame^]347libxml2.debugMemory(1)</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]348<p>and ends with the following epilogue:</p>
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]349<pre>#memory debug specific
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]350libxml2.cleanupParser()
351if libxml2.debugMemory(1) == 0:
352 print &quot;OK&quot;
353else:
354 print &quot;Memory leak %d bytes&quot; % (libxml2.debugMemory(1))
Daniel Veillard9eb146b2002-02-21 16:04:51 +0000[diff] [blame]355 libxml2.dumpMemory()</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]356<p>Those activate the memory debugging interface of libxml2 where all
357alloacted block in the library are tracked. The prologue then cleans up the
358library state and checks that all allocated memory has been freed. If not it
359calls dumpMemory() which saves that list in a <code>.memdump</code> file.</p>
360<p><a href="bugs.html">Daniel Veillard</a></p>
361</td></tr></table></td></tr></table></td></tr></table></td>
362</tr></table></td></tr></table>
363</body>
364</html>