|
DOM
The Document Object Model is a platform- and language-neutral interface that will allow programs and scripts to dynamically access and update the content, structure and style of documents. The document can be further processed and the results of that processing can be incorporated back into the presented page. This is an overview of DOM-related materials here at W3C and around the web.
|
|
DOM Introduction
The W3C Document Object Model is a "platform- and language-neutral interface that will allow programs and scripts to dynamically access and update the content, structure and style of documents. The document can be further processed and the results of that processing can be incorporated back into the presented page."
|
|
Let your DOM do the walking
The Document Object Model (DOM) offers useful modules to extend its core functionality in advanced ways. This article examines the DOM Traversal module in depth, showing how to find out if this module is supported in your parser and how to use it to walk either sets of selected nodes or the entire DOM tree. You'll come away from this article with a thorough understanding of DOM Traversal, and a powerful new tool in your Java and XML programming kit. Eight sample code listings demonstrate the techniques.
|
|
Just over the horizon ... a new DOM
This article previews the W3C's XML Document Object Model Level 3, due to be released toward the end of 2001 or early in 2002. Java developer and author Brett McLaughlin gives an overview of key features in the forthcoming version of the DOM, which will offer better access to pieces of information in an XML document, better comparisons, and a much-needed bootstrapping process. Six short code samples demonstrate some new methods.
|
|
W3C DOM Compatibility Table
This page notes the new methods and properties that Version 5 browsers should support and the (in)compatibilities of Netscape 6 and Explorer 5, who (surprise!) don't support everything as well as theory says they should.
|
|
Netscape 6, Part IV: DOM Differences and Commonalities with IE5.x
This column is the fourth part of our series on Netscape 6. In this column we'll start looking at the differences between Netscape 6's Document Object Model (DOM) and Internet Explorer 5.x's DOM. The DOM gives scripters a standardized way to access various elements of an HTML page, and should greatly simplify writing cross-browser scripts in the long run.
|
|
Total DOMination
Without question, the DOM is well documented in the W3C specification, in the documentation of various parser tools, and in the growing collection of XML books on the market. To that effect, the DOM is probably the best-documented component of XML (outside of XML itself), largely because the specification is stable and it's been available for roughly two years.
|
|
Dynamic Navigation with DOM
When the World Wide Web Consortium (W3C) introduced their working draft specification for the Document Object Model (DOM), it detailed how Web browsers should deal with HTML, CSS (Cascading Style Sheets), and XML documents. In particular, the specification describes how all document objects should be accessible programmatically.
|
|
Java XML DOM APIs benchmarked
The DOM implementations tested were Apache Crimson (originally Sun's XML parser) and Apache Xerces (derived from IBM's XML parser.)
|