Lines Matching refs:DOM
13 The Document Object Model, or "DOM," is a cross-language API from the World Wide
14 Web Consortium (W3C) for accessing and modifying XML documents. A DOM
19 The DOM is extremely useful for random-access applications. SAX only allows you
29 but the DOM allows you to avoid writing that code. The DOM is a standard tree
34 DOM Level 2 recommendation.
41 with that package for information on the current state of DOM Level 3 support.
43 .. What if your needs are somewhere between SAX and the DOM? Perhaps
48 features that allow you to find your way around the DOM.
51 DOM applications typically start by parsing some XML into a DOM. How this is
52 accomplished is not covered at all by DOM Level 1, and Level 2 provides only
57 :class:`Document` object. In Python, each DOM implementation will provide a
58 function :func:`getDOMImplementation`. DOM Level 3 adds a Load/Store
62 Once you have a DOM document object, you can access the parts of your XML
64 the DOM specification; this portion of the reference manual describes the
67 The specification provided by the W3C defines the DOM API for Java, ECMAScript,
76 `Document Object Model (DOM) Level 2 Specification <https://www.w3.org/TR/DOM-Level-2-Core/>`_
77 The W3C recommendation upon which the Python DOM API is based.
79 `Document Object Model (DOM) Level 1 Specification <https://www.w3.org/TR/REC-DOM-Level-1/>`_
80 The W3C recommendation for the DOM supported by :mod:`xml.dom.minidom`.
103 Return a suitable DOM implementation. The *name* is either well-known, the
104 module name of a DOM implementation, or ``None``. If it is not ``None``, imports
121 DOM. This is typically found as the :attr:`namespaceURI` of a node, or used as
138 Model (DOM) Level 2 Core Specification
139 <https://www.w3.org/TR/DOM-Level-2-Core/core.html>`_ (section 1.1.8).
151 In addition, :mod:`xml.dom` contains a base :class:`Node` class and the DOM
153 implement any of the methods or attributes defined by the DOM specification;
154 concrete DOM implementations must provide those. The :class:`Node` class
157 within the class rather than at the module level to conform with the DOM
165 Objects in the DOM
168 The definitive documentation for the DOM is the DOM specification from the W3C.
170 Note that DOM attributes may also be manipulated as nodes instead of as simple
209 An additional section describes the exceptions defined for working with the DOM
219 determine the availability of particular features in the DOM they are using.
220 DOM Level 2 added the ability to create new :class:`Document` and
232 Return a new :class:`Document` object (the root of the DOM), with a child
235 :meth:`createDocumentType`, or ``None``. In the Python DOM API, the first two
335 This has a different meaning for each node type; see the DOM specification for
344 This has a different meaning for each node type; see the DOM specification for
362 useful for DOM implementations which use any sort of proxy architecture (because
367 This is based on a proposed DOM Level 3 API which is still in the "working
369 from the W3C will not necessarily affect this method in the Python DOM interface
404 :class:`Text` instances. This simplifies processing text from a DOM tree for
422 two ways in the DOM Core recommendation: an :class:`Element` object provides
427 The DOM Level 2 recommendation defines one method and one attribute for these
442 In addition, the Python DOM interface requires that some additional support is
450 If a DOM implementation supports modification of the document, the
748 in is arbitrary but will be consistent for the life of a DOM. Each item is an
778 and DOM implementation support the DOM's XML extension, portions of the text
828 The DOM Level 2 recommendation defines a single exception, :exc:`DOMException`,
833 The Python DOM interface provides the constants, but also expands the set of
835 defined by the DOM. The implementations must raise the appropriate specific
842 Base exception class used for all specific DOM exceptions. This exception class
849 known to be used in the Python DOM implementations, but may be received from DOM
941 The exception codes defined in the DOM recommendation map to the exceptions
985 the Python DOM API, the W3C DOM recommendations, and the OMG IDL mapping for
994 The primitive IDL types used in the DOM specification are mapped to Python types
1012 Unicode whenever a string is returned from the DOM.
1037 The Python DOM API, however, *does* require that normal attribute access work.
1039 likely to work, and wrapper objects may be needed on the client if the DOM
1041 consideration for CORBA DOM clients, the implementers with experience using DOM
1043 declared ``readonly`` may not restrict write access in all DOM
1046 In the Python DOM API, accessor functions are not required. If provided, they
1051 The IDL definitions do not fully embody the requirements of the W3C DOM API,
1053 :meth:`getElementsByTagName`, being "live". The Python DOM API does not require