@@ -40,20 +40,20 @@ \section{\module{xml.dom} ---
4040The Document Object Model is being defined by the W3C in stages, or
4141`` levels'' in their terminology. The Python mapping of the API is
4242substantially based on the DOM Level 2 recommendation. Some aspects
43- of the API will only become available in Python 2.1 , or may only be
44- available in particular DOM implementations.
43+ of the API will only become available in future Python releases , or
44+ may only be available in particular DOM implementations.
4545
4646DOM applications typically start by parsing some XML into a DOM. How
4747this is accomplished is not covered at all by DOM Level 1, and Level 2
48- provides only limited improvements. There is a
48+ provides only limited improvements: There is a
4949\class {DOMImplementation} object class which provides access to
50- \class {Document} creation methods, but these methods were only added
51- in DOM Level 2 and were not implemented in time for Python 2.0. There
52- is also no well-defined way to access these methods without an
53- existing \class {Document} object. For Python 2.0, consult the
54- documentation for each particular DOM implementation to determine the
55- bootstrap procedure needed to create and initialize \class {Document}
56- and \class {DocumentType} instances .
50+ \class {Document} creation methods, but no way to access an XML
51+ reader/parser/Document builder in an implementation-independent way.
52+ There is also no well-defined way to access these methods without an
53+ existing \class {Document} object. In Python, each DOM implementation
54+ will provide a function \function {getDOMImplementation}. DOM Level 3
55+ adds a Load/Store specification, which defines an interface to the
56+ reader, but this is not implemented in Python .
5757
5858Once you have a DOM document object, you can access the parts of your
5959XML document through its properties and methods. These properties are
0 commit comments