[Python-checkins] python/dist/src/Doc/lib xmldom.tex,1.19,1.19.6.1
fdrake@users.sourceforge.net
fdrake@users.sourceforge.net
Wed, 11 Sep 2002 15:04:53 -0700
Update of /cvsroot/python/python/dist/src/Doc/lib
In directory usw-pr-cvs1:/tmp/cvs-serv31709
Modified Files:
Tag: release22-maint
xmldom.tex
Log Message:
Revise text about the level of DOM support, and provide pointers to
the work of the XML-SIG in the main body of the text. Incorporates
changes made by Martin von Löwis in revision 1.20 on the trunk.
Modify the markup in a few places to avoid wrapping lines in bad
places, and just general cleanliness.
Index: xmldom.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/xmldom.tex,v
retrieving revision 1.19
retrieving revision 1.19.6.1
diff -C2 -d -r1.19 -r1.19.6.1
*** xmldom.tex 30 Nov 2001 16:58:15 -0000 1.19
--- xmldom.tex 11 Sep 2002 22:04:51 -0000 1.19.6.1
***************
*** 40,58 ****
The Document Object Model is being defined by the W3C in stages, or
``levels'' in their terminology. The Python mapping of the API is
! substantially based on the DOM Level 2 recommendation. Some aspects
! of the API will only become available in Python 2.1, or may only be
! available in particular DOM implementations.
DOM applications typically start by parsing some XML into a DOM. How
! this is accomplished is not covered at all by DOM Level 1, and Level 2
! provides only limited improvements. There is a
\class{DOMImplementation} object class which provides access to
! \class{Document} creation methods, but these methods were only added
! in DOM Level 2 and were not implemented in time for Python 2.0. There
! is also no well-defined way to access these methods without an
! existing \class{Document} object. For Python 2.0, consult the
! documentation for each particular DOM implementation to determine the
! bootstrap procedure needed to create and initialize \class{Document}
! and \class{DocumentType} instances.
Once you have a DOM document object, you can access the parts of your
--- 40,62 ----
The Document Object Model is being defined by the W3C in stages, or
``levels'' in their terminology. The Python mapping of the API is
! substantially based on the DOM Level~2 recommendation. The mapping of
! the Level~3 specification, currently only available in draft form, is
! being developed by the \ulink{Python XML Special Interest
! Group}{http://www.python.org/sigs/xml-sig/} as part of the
! \ulink{PyXML package}{http://pyxml.sourceforge.net/}. Refer to the
! documentation bundled with that package for information on the current
! state of DOM Level~3 support.
DOM applications typically start by parsing some XML into a DOM. How
! this is accomplished is not covered at all by DOM Level~1, and Level~2
! provides only limited improvements: There is a
\class{DOMImplementation} object class which provides access to
! \class{Document} creation methods, but no way to access an XML
! reader/parser/Document builder in an implementation-independent way.
! There is also no well-defined way to access these methods without an
! existing \class{Document} object. In Python, each DOM implementation
! will provide a function \function{getDOMImplementation()}. DOM Level~3
! adds a Load/Store specification, which defines an interface to the
! reader, but this is not yet available in the Python standard library.
Once you have a DOM document object, you can access the parts of your
***************
*** 71,79 ****
\begin{seealso}
\seetitle[http://www.w3.org/TR/DOM-Level-2-Core/]{Document Object
! Model (DOM) Level 2 Specification}
{The W3C recommendation upon which the Python DOM API is
based.}
\seetitle[http://www.w3.org/TR/REC-DOM-Level-1/]{Document Object
! Model (DOM) Level 1 Specification}
{The W3C recommendation for the
DOM supported by \module{xml.dom.minidom}.}
--- 75,83 ----
\begin{seealso}
\seetitle[http://www.w3.org/TR/DOM-Level-2-Core/]{Document Object
! Model (DOM) Level~2 Specification}
{The W3C recommendation upon which the Python DOM API is
based.}
\seetitle[http://www.w3.org/TR/REC-DOM-Level-1/]{Document Object
! Model (DOM) Level~1 Specification}
{The W3C recommendation for the
DOM supported by \module{xml.dom.minidom}.}
***************
*** 138,142 ****
The namespace URI for namespace declarations, as defined by
\citetitle[http://www.w3.org/TR/DOM-Level-2-Core/core.html]{Document
! Object Model (DOM) Level 2 Core Specification} (section~1.1.8).
\versionadded{2.2}
\end{datadesc}
--- 142,146 ----
The namespace URI for namespace declarations, as defined by
\citetitle[http://www.w3.org/TR/DOM-Level-2-Core/core.html]{Document
! Object Model (DOM) Level~2 Core Specification} (section~1.1.8).
\versionadded{2.2}
\end{datadesc}
***************
*** 205,209 ****
The \class{DOMImplementation} interface provides a way for
applications to determine the availability of particular features in
! the DOM they are using. DOM Level 2 added the ability to create new
\class{Document} and \class{DocumentType} objects using the
\class{DOMImplementation} as well.
--- 209,213 ----
The \class{DOMImplementation} interface provides a way for
applications to determine the availability of particular features in
! the DOM they are using. DOM Level~2 added the ability to create new
\class{Document} and \class{DocumentType} objects using the
\class{DOMImplementation} as well.
***************
*** 320,328 ****
same node).
! \note{This is based on a proposed DOM Level 3 API which is
! still in the ``working draft'' stage, but this particular interface
! appears uncontroversial. Changes from the W3C will not necessarily
! affect this method in the Python DOM interface (though any new W3C
! API for this would also be supported).}
\end{methoddesc}
--- 324,334 ----
same node).
! \begin{notice}
! This is based on a proposed DOM Level~3 API which is still in the
! ``working draft'' stage, but this particular interface appears
! uncontroversial. Changes from the W3C will not necessarily affect
! this method in the Python DOM interface (though any new W3C API for
! this would also be supported).
! \end{notice}
\end{methoddesc}
***************
*** 373,377 ****
objects with this interface to represent query results.
! The DOM Level 2 recommendation defines one method and one attribute
for these objects:
--- 379,383 ----
objects with this interface to represent query results.
! The DOM Level~2 recommendation defines one method and one attribute
for these objects:
***************
*** 668,677 ****
\end{memberdesc}
! \note{The use of a \class{CDATASection} node does not
! indicate that the node represents a complete CDATA marked section,
! only that the content of the node was part of a CDATA section. A
! single CDATA section may be represented by more than one node in the
! document tree. There is no way to determine whether two adjacent
! \class{CDATASection} nodes represent different CDATA marked sections.}
--- 674,686 ----
\end{memberdesc}
! \begin{notice}
! The use of a \class{CDATASection} node does not indicate that the
! node represents a complete CDATA marked section, only that the
! content of the node was part of a CDATA section. A single CDATA
! section may be represented by more than one node in the document
! tree. There is no way to determine whether two adjacent
! \class{CDATASection} nodes represent different CDATA marked
! sections.
! \end{notice}
***************
*** 696,700 ****
\versionadded{2.1}
! The DOM Level 2 recommendation defines a single exception,
\exception{DOMException}, and a number of constants that allow
applications to determine what sort of error occurred.
--- 705,709 ----
\versionadded{2.1}
! The DOM Level~2 recommendation defines a single exception,
\exception{DOMException}, and a number of constants that allow
applications to determine what sort of error occurred.