Lines Matching refs:DOM
14 The Document Object Model, or "DOM," is a cross-language API from the World Wide
15 Web Consortium (W3C) for accessing and modifying XML documents. A DOM
20 The DOM is extremely useful for random-access applications. SAX only allows you
30 but the DOM allows you to avoid writing that code. The DOM is a standard tree
35 DOM Level 2 recommendation.
37 .. What if your needs are somewhere between SAX and the DOM? Perhaps
42 features that allow you to find your way around the DOM.
45 DOM applications typically start by parsing some XML into a DOM. How this is
46 accomplished is not covered at all by DOM Level 1, and Level 2 provides only
51 :class:`Document` object. In Python, each DOM implementation will provide a
52 function :func:`getDOMImplementation`. DOM Level 3 adds a Load/Store
56 Once you have a DOM document object, you can access the parts of your XML
58 the DOM specification; this portion of the reference manual describes the
61 The specification provided by the W3C defines the DOM API for Java, ECMAScript,
70 …`Document Object Model (DOM) Level 2 Specification <https://www.w3.org/TR/2000/REC-DOM-Level-2-Cor…
71 The W3C recommendation upon which the Python DOM API is based.
73 `Document Object Model (DOM) Level 1 Specification <https://www.w3.org/TR/REC-DOM-Level-1/>`_
74 The W3C recommendation for the DOM supported by :mod:`xml.dom.minidom`.
97 Return a suitable DOM implementation. The *name* is either well-known, the
98 module name of a DOM implementation, or ``None``. If it is not ``None``, imports
115 DOM. This is typically found as the :attr:`namespaceURI` of a node, or used as
128 Model (DOM) Level 2 Core Specification
129 <https://www.w3.org/TR/DOM-Level-2-Core/core.html>`_ (section 1.1.8).
138 In addition, :mod:`xml.dom` contains a base :class:`Node` class and the DOM
140 implement any of the methods or attributes defined by the DOM specification;
141 concrete DOM implementations must provide those. The :class:`Node` class
144 within the class rather than at the module level to conform with the DOM
152 Objects in the DOM
155 The definitive documentation for the DOM is the DOM specification from the W3C.
157 Note that DOM attributes may also be manipulated as nodes instead of as simple
196 An additional section describes the exceptions defined for working with the DOM
206 determine the availability of particular features in the DOM they are using.
207 DOM Level 2 added the ability to create new :class:`Document` and
219 Return a new :class:`Document` object (the root of the DOM), with a child
222 :meth:`createDocumentType`, or ``None``. In the Python DOM API, the first two
322 This has a different meaning for each node type; see the DOM specification for
331 This has a different meaning for each node type; see the DOM specification for
349 useful for DOM implementations which use any sort of proxy architecture (because
354 This is based on a proposed DOM Level 3 API which is still in the "working
356 from the W3C will not necessarily affect this method in the Python DOM interface
391 :class:`Text` instances. This simplifies processing text from a DOM tree for
407 two ways in the DOM Core recommendation: an :class:`Element` object provides
412 The DOM Level 2 recommendation defines one method and one attribute for these
427 In addition, the Python DOM interface requires that some additional support is
435 If a DOM implementation supports modification of the document, the
733 in is arbitrary but will be consistent for the life of a DOM. Each item is an
763 and DOM implementation support the DOM's XML extension, portions of the text
811 The DOM Level 2 recommendation defines a single exception, :exc:`DOMException`,
816 The Python DOM interface provides the constants, but also expands the set of
818 defined by the DOM. The implementations must raise the appropriate specific
825 Base exception class used for all specific DOM exceptions. This exception class
832 known to be used in the Python DOM implementations, but may be received from DOM
924 The exception codes defined in the DOM recommendation map to the exceptions
968 the Python DOM API, the W3C DOM recommendations, and the OMG IDL mapping for
977 The IDL types used in the DOM specification are mapped to Python types
1015 The Python DOM API, however, *does* require that normal attribute access work.
1017 likely to work, and wrapper objects may be needed on the client if the DOM
1019 consideration for CORBA DOM clients, the implementers with experience using DOM
1021 declared ``readonly`` may not restrict write access in all DOM
1024 In the Python DOM API, accessor functions are not required. If provided, they
1029 The IDL definitions do not fully embody the requirements of the W3C DOM API,
1031 :meth:`getElementsByTagName`, being "live". The Python DOM API does not require