| xercesc::DOMAttr | The DOMAttr class refers to an attribute of an XML element |
| xercesc::DOMBuilder | DOMBuilder provides an API for parsing XML documents and building the corresponding DOM document tree |
| xercesc::DOMCDATASection | CDATA sections are used to escape blocks of text containing characters that would otherwise be regarded as markup |
| xercesc::DOMCharacterData | The DOMCharacterData interface extends DOMNode with a set of attributes and methods for accessing character data in the DOM |
| xercesc::DOMComment | This interface inherits from CharacterData and represents the content of a comment, i.e., all the characters between the starting ' <!--' and ending '-->' |
| xercesc::DOMConfiguration | The DOMConfiguration interface represents the configuration of a document and maintains a table of recognized parameters |
| xercesc::DOMDocument | The DOMDocument interface represents the entire XML document |
| xercesc::DOMDocumentFragment | DOMDocumentFragment is a "lightweight" or "minimal" DOMDocument object |
| xercesc::DOMDocumentRange | |
| xercesc::DOMDocumentTraversal | DOMDocumentTraversal contains methods that create DOMNodeIterators and DOMTreeWalkers to traverse a node and its children in document order (depth first, pre-order traversal, which is equivalent to the order in which the start tags occur in the text representation of the document) |
| xercesc::DOMDocumentType | Each DOMDocument has a doctype attribute whose value is either null or a DOMDocumentType object |
| xercesc::DOMElement | By far the vast majority of objects (apart from text) that authors encounter when traversing a document are DOMElement nodes |
| xercesc::DOMEntity | This interface represents an entity, either parsed or unparsed, in an XML document |
| xercesc::DOMEntityReference | DOMEntityReference objects may be inserted into the structure model when an entity reference is in the source document, or when the user wishes to insert an entity reference |
| xercesc::DOMEntityResolver | DOMEntityResolver provides a way for applications to redirect references to external entities |
| xercesc::DOMError | DOMError is an interface that describes an error |
| xercesc::DOMErrorHandler | Basic interface for DOM error handlers |
| xercesc::DOMException | |
| xercesc::DOMImplementation | The DOMImplementation interface provides a number of methods for performing operations that are independent of any particular instance of the document object model |
| xercesc::DOMImplementationLS | |
| xercesc::DOMImplementationRegistry | |
| xercesc::DOMImplementationSource | |
| xercesc::DOMInputSource | This interface represents a single input source for an XML entity |
| xercesc::DOMLocator | DOMLocator is an interface that describes a location |
| xercesc::DOMNamedNodeMap | DOMNamedNodeMaps are used to represent collections of nodes that can be accessed by name |
| xercesc::DOMNode | The DOMNode interface is the primary datatype for the entire Document Object Model |
| xercesc::DOMNodeFilter | Filters are objects that know how to "filter out" nodes |
| xercesc::DOMNodeIterator | DOMNodeIterators are used to step through a set of nodes, e.g |
| xercesc::DOMNodeList | The DOMNodeList interface provides the abstraction of an ordered collection of nodes |
| xercesc::DOMNotation | This interface represents a notation declared in the DTD |
| xercesc::DOMProcessingInstruction | The DOMProcessingInstruction interface represents a "processing instruction", used in XML as a way to keep processor-specific information in the text of the document |
| xercesc::DOMPSVITypeInfo | The DOMPSVITypeInfo interface represent the PSVI info used by DOMElement or DOMAttr nodes, specified in the schemas associated with the document |
| xercesc::DOMRange | |
| xercesc::DOMRangeException | Range operations may throw a DOMRangeException as specified in their method descriptions |
| xercesc::DOMText | The DOMText interface inherits from DOMCharacterData and represents the textual content (termed character data in XML) of an DOMElement or DOMAttr |
| xercesc::DOMTreeWalker | DOMTreeWalker objects are used to navigate a document tree or subtree using the view of the document defined by their whatToShow flags and filter (if any) |
| xercesc::DOMTypeInfo | The DOMTypeInfo interface represent a type used by DOMElement or DOMAttr nodes, specified in the schemas associated with the document |
| xercesc::DOMUserDataHandler | When associating an object to a key on a node using setUserData the application can provide a handler that gets called when the node the object is associated to is being cloned or imported |
| xercesc::DOMWriter | |
| xercesc::DOMWriterFilter | |
| xercesc::DOMXPathEvaluator | The evaluation of XPath expressions is provided by DOMXPathEvaluator |
| xercesc::DOMXPathException | |
| xercesc::DOMXPathExpression | The DOMXPathExpression interface represents a parsed and resolved XPath expression |
| xercesc::DOMXPathNamespace | The DOMXPathNamespace interface is returned by DOMXPathResult interfaces to represent the XPath namespace node type that DOM lacks |
| xercesc::DOMXPathNSResolver | The DOMXPathNSResolver interface permit prefix strings in the expression to be properly bound to namespaceURI strings |
| xercesc::DOMXPathResult | The DOMXPathResult interface represents the result of the evaluation of an XPath 1.0 expression within the context of a particular node |
| xercesc::MemoryManager | Configurable memory manager |
| xercesc::StDOMNode< T > | |
| xercesc::XMLDeleter | |
| xercesc::XMLPlatformUtils | Utilities that must be implemented in a platform-specific way |
| XPath2Result | The XPathResult2 interface represents the result of the evaluation of an XPath 2.0 expression within the context of a particular node |
| XQillaExpression | The XQillaExpression interface extends the DOMXPathExpression interface, providing the ability to release the object |
| XQillaNSResolver | The XQillaNSResolver interface extends the DOMXPathNSResolver providing the ability to add additional namespace bindings |
| XQillaPlatformUtils | Static utility methods for initializing and terminating the XQilla and Xerces environments |
