Lauren Wood et al. Document Object Model (DOM) level 1 speci cation, version 1.0, October 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....and experimental results of our XML processing system developed to prove the feasibility of general techniques to efficiently evaluate XPath queries using LDAP. Besides providing support for network operations and query distribution over a set of nodes, the LDAP model is so close to the DOM model [6], that we are able to process XML based sources without the need to incur in cumbersome transformations, like XML to relational representations. The combination of these features, plus the simplicity of our LDAP based model to efficiently support XPath queries, make it the ideal candidate for an ....

L. Wood et al. Document object model. http: //www.w3.org/TR/REC-DOM-Level-1, 2000.

....to the transformations we just described. We further assume that predicates contain only simple path expressions that Original Axis Augmented Axis child descendent parent ancestor Table 2. Subquery Generalization Strategy test properties and attributes of a node that, following the DOM model [11], are stored as direct descendents of such elements. We could, of course, allow the adaptive search of path expressions in predicates, but then we need to define what it means for a predicate match to happen after a generalization, which could lead to inconsistencies in the result set. For this ....

....discrepancies between information stored as either an element or an attribute node in the XML description of a catalog. The same concept can appear as an element in the global catalog and as an attribute in one of the local catalogs. The main problem by such a configuration is that, by definition [11], attributes have no descendants. Therefore, even if we extended our adaptive algorithm to perform subquery generalization and elimination on attributes, instead of just elements, no further searching of the catalog would stem from attribute nodes. A simple solution to this problem, and one that ....

L. Wood, A. L. Hors, V. Apparao, S. Byrne, M. Champion, S. Isaacs, G. Nicol, J. Robie, R. Sutor, and C. Wilson. Document object model (DOM) level 1 specification (second edition). http://www.w3.org/TR/2000.

.... [6] propElt : propName value propName propName resAttr 5 [7] propName : Qname [8] value : descript string [9] resAttr : resource= URI ref [10] Qname : NSprefix : name [11] URI ref : string [12] IDsymbol : any XML legal symbol) [13] name : any XML legal symbol) 14] NSprefix : any XML namespace prefix) 15] string : any XML data) Using this syntax, we can represent in RDF XML the following assertion about the owner of a particular le: f:Owner Sabin Corneliu Buraga f:Owner In this example, the namespace pre ....

....RDF model can be validated and manipulated by Simple RDF Parser and Compiler (SiRPAC ) 17] a freely available Java servlet based on Megginson s SAX (Simple API for XML) processor. An implementation of our RDF model and proposed XML language can be also based on the Document Object Model (DOM ) [13] speci cation. The RDF description of distributed le systems needs to be enriched by a formal RDF schema and particular (low level) speci cations for Linux and Windows platforms. 15 ....

L. Wood (ed.), Document Object Model (DOM) Level 1 Speci

....the WQFL and WQGL documents it can be used Libxml [28] a SAX (Simple API for XML) library available on Linux systems. Another parsing and further processing solution is given by JDOM (Java Document Object Model) library [27] a Java open source implementation of World Wide Web Consortium s DOM [3, 25] level 1 and level 2 recommendations. To design the graphical user interface we intend to adopt an user centered interface design approach. A solution is given by LUCID (Logical User Centered Interaction Design) 29] For building the user interface it can be considered the existing XUL ....

L. Wood (ed.), Document Object Model (DOM) Level 1 Speci

....this simple model revealed some small ambiguities in [XPath] which we discuss at the end of this section. For simplicity, we will ignore namespaces; although a full treatment of them along similar lines is possible. The model we give is, unsurprisingly, quite similar to the Document Object Model (DOM) a standard interface for accessing and manipulating representations of XML trees, which works with a number of programming languages [DOM] There are a few di#erences from the DOM (which we will note parenthetically) The basic datatype is Node. Each Node is one of six kinds: root, element, ....

....although a full treatment of them along similar lines is possible. The model we give is, unsurprisingly, quite similar to the Document Object Model (DOM) a standard interface for accessing and manipulating representations of XML trees, which works with a number of programming languages [DOM] There are a few di#erences from the DOM (which we will note parenthetically) The basic datatype is Node. Each Node is one of six kinds: root, element, attribute, text, comment, or processing instruction. We indicate this with six boolean functions; for each node, exactly one of these functions ....

[Article contains additional citation context not shown here]

Lauren Wood, editor, Document Object Model (DOM), Version 1.0, W3C Recommendation, 1 October 1998. http://www.w3.org/TR/REC-DOM-Level-1/

....that we extended to our application specific needs. The advantages of using P DOM are the good performance, the ease of extensibility of the metadata schemas, and the possibility of co existence of old and new schemas (DTDs) in our repositories. P DOM is a persistent DOM (Document Object Model) [DOM00]. DOM is a platform and language neutral interface for XML. It provides a standard set of objects for representing XML documents, a standard model of how these objects can be combined, and a standard interface for accessing and manipulating them. Many of the existing implementations of DOM ....

Wood, L., et al: Document Object Model (DOM) Level 1 Specification (Second Edition), Version 1.0. W3C Working Draft, September,

....(extensible markup language, 1] XML is being adopted as an easy to write, easy to parse language to exchange semistructured data in commercial, nancial, medical, scienti c and other applications. With the advent of standardized APIs for semistructured data like the document object model (DOM, [2]) the mere exchange of textual representations with generating at one end and parsing at the other will not be sucient for all applications. Direct access to and manipulation of the documents tree structure and, as a consequence, ecient storage managers for tree structured data will be required. ....

.... LINE Let me see your eyes; LINE LINE Look in my face. LINE SPEECH SPEAKER OTHELLO LINE Let me see your eyes; LINE Look in my face. Figure 2: A fragment of XML with its associated logical tree 2. 2 Logical Model A popular and useful model for XML documents is the tree [2, 9]. General graphs, which are often used to model semistructured data, are represented in XML using special IDREF attributes[1] and XLinks [10] for intra and inter document references, respectively. We use ordered trees in which each non leaf node is labelled with a symbol taken from an alphabet ....

Lauren Wood et al. Document Object Model (DOM) level 1 specication, version 1.0, October

....utility for transferring data between XML documents and relational databases, implemented as a set of Java packages: a data transfer package, a map factory package, and a coordinator package. The utility is based on widely available specifications JDBC for database access, SAX [Megg98] and DOM [DOM98] for XML document access, and DDML [BCML99] for XML schema information so it can be used with products from many vendors, such as di#erent databases, parsers, and DOM implementations. 7.1 XML DBMS Architecture XML DBMS is used by applications that need to transfer data between XML documents ....

L. Wood, et al.: Document Object Model (DOM) Level 1 Specification, Version 1.0, http://www.w3.org/TR/REC-DOM-Level-1/, 1998

....natural support for describing the hierarchical structure in web documents and allows speci c markup to be created for speci c data. It may become as important and as widely used as HTML in the future. The World Wide Web Consortium (W3C) has recently recommended the Document Object Model (DOM) [14] as an application programming interface for HTML and XML documents. DOM de nes the logical structure of documents and the way a document is accessed and manipulated. It represents documents as a hierarchy of various node objects. With DOM, programmers can access, change, delete, add or build HTML ....

L. Wood, A. L. Hors, et al. Document Object Model (DOM) Level 2 Specication. W3C Recommendation. See http://www.w3c.org/TR/2000/CR-DOM-Level2 -20000307, March 2000. 14

....name, property valueg. Properties generalise the attributes of an XML element and most are string valued, but some have values which are lists of other nodes in the internal representation, for example the children and parent properties. As an extension to the standard XML document model [Wood, 1998], DTDs are also represented as objects in the database. The types of nodes and their interrelationships are shown in figure 2. This representation of the database makes it easy for the query language (section 4) to ask general questions about the annotations. Most uses of this data model for ....

Wood L. (ed) (1998). Document Object Model (DOM) Level 1 Specification Version 1.0, World Wide Web Consortium, December 1998. See http://www.w3.org/TR/1998/RECDOM -Level-1.

....client XML parser conforms to the Simple API for XML (SAX) 5] standard, and can be interchanged with other SAX compliant parsers. The motivation for using SAX is its simplicity: the Bluejay parser is small and does not require the complexity of a parser API such as the Document Object Model (DOM) [6] because the other Bluejay classes are the only modules which are directly interacting with the parser. The parser is validating, i.e. the marked up data are checked to ensure content and syntax conformity to the markup language definition. The validation of the content offloads work 144 HIGH ....

Wood, L. et al, eds. Document Object Model (DOM) Level 1 Specification, on-line, available at http://www.w3.org/TR/REC-DOM-Level-1.

....[15] allows for embedded scripts in a document, but it does not provide a standard object model that describes how scripts can manipulate the document content. Unfortunately, the Netscape and Microsoft browsers have incompatible DOM versions. The recently announced DOM Level 1 specification [4] defines a standard API, but it is not yet fully implemented in the standard browsers. In this paper we will therefore concentrate on the object model as implemented by Microsoft s Internet Explorer 4 [6] which in contrast to Navigator makes all objects in a document scriptable, and provides an ....

Lauren Wood et. al. Document Object Model (DOM) Level 1 Specification. http://www.w3.org/TR/REC-DOM-Level-1, October 1998.

....software as the basic infrastructure to provide future growth and easy migration to other new standards. Furthermore, S2M2 utilizes standard multimedia and content technologies such as Java Media Framework (JMF) 8] created by Sun Microsystems, Intel and SGI, and the Document Object Model (DOM) [6] by W3C. Figure 3 shows the S2M2 basic system components and architecture. The following subsections discuss each component in greater detail. FIGURE 3: S2M2 SYSTEM COMPONENT AND ARCHITECTURE SAXDOM SMIL DTD Applet JavaScript JDK Class Library JMF Class Library S2M2 Rendering ....

L. Wood (chair). Document Object Model. http://www.w3.org/TR/WD-DOM.

No context found.

Lauren Wood et al. Document Object Model (DOM) level 1 speci cation, version 1.0, October 1998.

No context found.

Wood L. et al. Document Object Model (DOM) Level 1 Specification (Second Edition).W3C, 2000.

No context found.

Lauren Wood, Arnaud Le Hors et al. Document Object Model (DOM) Level 1 Specification (Second Edition) Version 1. W3C Working Draft, 29 September 2000.

No context found.

L. Wood, V. Apparao, S. Byrne, M. Champion, S. Isaacs, I. Jacobs, A. Le Hors, G. Nicol, J. Robie, R. Sutor, C. Wilson, Document Object Model (DOM) Level 1 Specification,Version 1.0, W3C Recommendation, 1998. (http://www.w3.org/TR/REC-DOM-Level-1/)

No context found.

L. Wood, V. Apparao, S. Byrne, M. Champion, S. Isaacs, I. Jacobs, A. Le Hors, G. Nicol, J. Robie, T. Research, R. Sutor, C. Wilson and L. Wood, Document Object Model (DOM) 1.0, W3C Recommendation, 1 October 1998, http://www.w3.org/TR/RECDOM -Level-1

No context found.

L. Wood, V. Apparao, S. Byrne, M. Champion, S. Isaacs, I. Jacobs, A. Le Hors, G. Nicol, J. Robie, T. Research, R. Sutor, C. Wilson and L. Wood, Document Object Model (DOM) 1.0, W3C Recommendation, 1 October 1998, http://www.w3.org/TR/REC-DOM-Level-1

No context found.

L. Wood, et al.: Document Object Model (DOM) Level 1 Specification, Version 1.0, www.w3.org/TR/REC-DOMLevel -1/, 1998

No context found.

L. Wood, A. L. Hors, V. Apparao, L. Cable, M. Champion, J. Kesselman, P. L. Hegaret, T. Pixley, J. Robie, P. Sharpe, and C. Wilson. Document Object Model (DOM). W3C, 1999. http://www.w3.org/TR/DOM-Level-2/.

No context found.

L. Wood, A. L. Hors, V. Apparao, L. Cable, M. Champion, J. Kesselman, P. L. Hegaret, T. Pixley, J. Robie, P. Sharpe, and C. Wilson, Document Object Model (DOM). W3C, 1999. http://www.w3.org/TR/DOM-Level-2/.

No context found.

Wood, L. et al. (Eds.), 1998. Document Object Model (DOM) Level 1 Specication. W3C Recommendation. Available from [http://www.w3.org/ DOM/]. 28

No context found.

. Document Object Model (DOM) Level 1 Specification. http://www.w3.org/TR/1998/RECDOM -Level-1-19981001. Lauren Wood+. W3, October 1998.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC