DOCSLIB.ORG

XML and Related Technologies Certification Prep, Part 3: XML Processing Explore How to Parse and Validate XML Documents Plus How to Use Xquery

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
XML and Related Technologies Certification Prep, Part 3: XML Processing Explore How to Parse and Validate XML Documents Plus How to Use Xquery XML and Related Technologies certification prep, Part 3: XML processing Explore how to parse and validate XML documents plus how to use XQuery Skill Level: Intermediate Mark Lorenz ([email protected]) Senior Application Architect Hatteras Software, Inc. 26 Sep 2006 Parsing and validation represent the core of XML. Knowing how to use these capabilities well is vital to the successful introduction of XML to your project. This tutorial on XML processing teaches you how to parse and validate XML files as well as use XQuery. It is the third tutorial in a series of five tutorials that you can use to help prepare for the IBM certification Test 142, XML and Related Technologies. Section 1. Before you start In this section, you'll find out what to expect from this tutorial and how to get the most out of it. About this series This series of five tutorials helps you prepare to take the IBM certification Test 142, XML and Related Technologies, to attain the IBM Certified Solution Developer - XML and Related Technologies certification. This certification identifies an intermediate-level developer who designs and implements applications that make use of XML and related technologies such as XML Schema, Extensible Stylesheet Language Transformation (XSLT), and XPath. This developer has a strong understanding of XML fundamentals; has knowledge of XML concepts and related technologies; understands how data relates to XML, in particular with issues associated with information modeling, XML processing, XML rendering, and Web XML processing © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 1 of 38 developerWorks® ibm.com/developerWorks services; has a thorough knowledge of core XML-related World Wide Web Consortium (W3C) recommendations; and is familiar with well-known, best practices. Anyone working in software development for the last few years is aware that XML provides cross-platform capabilities for data, just as the Java® programming language does for application logic. This series of tutorials is for anyone who wants to go beyond the basics of using XML technologies. About this tutorial This tutorial is the third in the "XML and Related Technologies certification prep" series that takes you through the key aspects of effectively using XML technologies on Java projects. This third tutorial focuses on XML processing -- that is, how to parse and validate XML documents. It lays the groundwork for Part 4, which focuses on transformation, including the use of XSLT, XPath, and Cascading Style Sheets (CSS). This tutorial is written for Java programmers who have a basic understanding of XML and whose skills and experience are at a beginning to intermediate level. You should have a general familiarity with defining, validating, and reading XML documents, as well as a working knowledge of the Java language. Objectives After completing this tutorial, you will know how to: • Parse XML documents using the Simple API for XML 2 (SAX2) and Document Object Model 2 (DOM2) parsers • Validate XML documents against Document Type Definitions (DTDs) and XML Schemas • Access XML content from databases using XQuery Prerequisites This tutorial is written for developers who have a background in programming and scripting and who have an understanding of basic computer-science models and data structures. You should be familiar with the following XML-related, computer-science concepts: tree traversal, recursion, and reuse of data. You should be familiar with Internet standards and concepts, such as Web browser, client-server, documenting, formatting, e-commerce, and Web applications. Experience designing and implementing Java-based computer applications and working with relational databases is also recommended. XML processing Page 2 of 38 © Copyright IBM Corporation 1994, 2008. All rights reserved. ibm.com/developerWorks developerWorks® System requirements To run the examples in this tutorial, you need a Linux® or Microsoft® Windows® box with at least 50MB of free disk space and administrative access to install software. The tutorial uses, but does not require, the following software: • Java software development kit (JDK) 1.4.2 or later • Eclipse 3.1 or later • XMLBuddy 2.0 or later (Note: Some portions of the series use capabilities of XMLBuddy Pro, which is not free.) See Resources for links to download the above software Section 2. Parsing XML documents You can parse an XML document in multiple ways (see Part 1 of this series, which focuses on architecture), but the SAX parser and the DOM parser constitute the primary ways. Part 1 features a high-level comparison of the two (see Resources). StAX A new API, called Streaming API for XML (StAX), is to be released in late 2006. It is a pull API, as opposed to SAX's push model, so it keeps control with the application rather than the parser. You can also use StAX to modify the document being parsed. Read more in "An Introduction to StAX" (see Resources). XML instance document This tutorial uses a store's catalog of available DVDs for purchase as the document throughout. Conceptually, the catalog contains a collection of DVDs with information about each DVD associated with it. The actual document is a short catalog with only four DVDs in it, but it has enough complexity for you to learn about XML processing, including validation. Listing 1 shows the file. Listing 1. The XML instance document for the DVD catalog <?xml version="1.0"?> <!DOCTYPE catalog SYSTEM "dvd.dtd"> <!-- DVD inventory --> <catalog> <dvd code="_1234567"> <title>Terminator 2</title> <description> A shape-shifting cyborg is sent back from the future XML processing © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 3 of 38 developerWorks® ibm.com/developerWorks to kill the leader of the resistance. </description> <price>19.95</price> <year>1991</year> </dvd> <dvd code="_7654321"> <title>The Matrix</title> <price>12.95</price> <year>1999</year> </dvd> <dvd code="_2255577" genre="Drama"> <title>Life as a House</title> <description> When a man is diagnosed with terminal cancer, he takes custody of his misanthropic teenage son. </description> <price>15.95</price> <year>2001</year> </dvd> <dvd code="_7755522" genre="Action"> <title>Raiders of the Lost Ark</title> <price>14.95</price> <year>1981</year> </dvd> </catalog> Using the SAX parser As Part 1 of this series discussed, the SAX parser is an event-based parser. This means that the parser sends events to callback methods as it parses a document (see Figure 1). For simplicity, Figure 1 doesn't show all the events that would actually occur. Figure 1. SAX parser events XML processing Page 4 of 38 © Copyright IBM Corporation 1994, 2008. All rights reserved. ibm.com/developerWorks developerWorks® These events are pushed out to the application in real time, as the parser moves across the document contents. One benefit of this processing model is that you can handle large documents with relatively little memory. A downside is that you have more work to do to handle all these events. The org.xml.sax package contains a set of interfaces. One of these provides the XMLReader interface to the parser. You can set up for parsing like this: try { XMLReader parser = XMLReaderFactory.createXMLReader(); parser.parse( "myDocument.xml" ); //complete path } catch ( SAXParseException e ) { //document is not well-formed } catch ( SAXException e ) { //could not find an implementation of XMLReader } catch ( IOException e ) { //problem reading document file } Apache Xerces2 parser If you need a parser, you can download the open source Apache Xerces2 parser from The Apache Software Foundation Web site (see Resources). XML processing © Copyright IBM Corporation 1994, 2008. All rights reserved. Page 5 of 38 developerWorks® ibm.com/developerWorks Tip: Reuse the parser instance if possible. Creating a parser is expensive. If you have multiple threads running, you can reuse parser instances from a resource pool. This is all well and good so far, but how does your application get events from the parser? I'm glad you asked. Handling SAX events To receive events from the parser, you implement the ContentHandler interface. This interface has a number of methods that you can implement to process your document. Alternatively, if you only want to handle one or two callbacks, you can subclass DefaultHandler, which implements all the ContentHandler methods (doing nothing) and overrides only the methods you need. Either way, you write logic to do whatever processing you require upon receiving startElement, characters, endDocument, and other callback methods invoked by the SAX parser. You can see all the method calls from a document as they would occur on pages 351-355 of XML in a Nutshell, Third Edition (see Resources). The callback events are the normal events from a document as it's being parsed. You can also handle validity callbacks by implementing an ErrorHandler. I'll discuss this topic after I go over validation, so stay tuned. To learn more about parsing with SAX, check out Chapter 20 of XML in a Nutshell, Third Edition or read "Serial Access with the Simple API for XML (SAX)" (see Resources). SAX parser exception handling By default, the parser ignores errors. To take action upon an invalid or non-well-formed document, you must implement an ErrorHandler (note that DefaultHandler implements this as well as the ContentHandler interface) and define an error() method: public class SAXEcho extends DefaultHandler { ... //Handle validity errors public void error( SAXParseException e ) { echo( e.getMessage() ); echo( "Line " + e.getLineNumber() + " Column " + e.getColumnNumber(); } Then you must turn on the validation feature: parser.setFeature( "http://xml.org/sax/features/validation", true ); Finally, call this code: parser.setErrorHandler( saxEcho ); XML processing Page 6 of 38 © Copyright IBM Corporation 1994, 2008. All rights reserved. ibm.com/developerWorks developerWorks® Remember, parser is an instance of XMLReader. The parser calls the error() method if the document violates a schema (DTD or XML Schema) rule.
Load more

Recommended publications
  • XML Parsers - a Comparative Study with Respect to Adaptability
    XML Parsers - A comparative study with respect to adaptability Bachelor Degree Project in Information Technology Basic level 30 ECTS Spring term 2018 Johan Holm Mats Gustavsson Supervisor: Yacine Atif Examinator: Alan Said Abstract Data migration is common as information needs to be moved and transformed between services and applications. Performance in the context of speed is important and may have a crucial impact on the handling of data. Information can be sent in varying formats and XML is one of the more commonly used. The information that is sent can change in structure from time to time and these changes needs to be handled. The parsers’ ability to handle these changes are described as the property “adaptability”. The transformation of XML files is done with the use of parsing techniques. The parsing techniques have different approaches, for example event-based or memory-based. Each approach has its pros and cons. The aim of this study is to research how three different parsers handle parsing XML documents with varying structures in the context of performance. The chosen parsing techniques are SAX, DOM and VTD. SAX uses an event-based approach while DOM and VTD uses a memory-based. Implementation of the parsers have been made with the purpose to extract information from XML documents an adding it to an ArrayList. The results from this study show that the parsers differ in performance, where DOM overall is the slowest and SAX and VTD perform somewhat equal. Although there are differences in the performance between the parsers depending on what changes are made to the XML document.
    [Show full text]
  • High Performance XML Data Retrieval
    High Performance XML Data Retrieval Mark V. Scardina Jinyu Wang Group Product Manager & XML Evangelist Senior Product Manager Oracle Corporation Oracle Corporation Agenda y Why XPath for Data Retrieval? y Current XML Data Retrieval Strategies and Issues y High Performance XPath Requirements y Design of Extractor for XPath y Extractor Use Cases Why XPath for Data Retrieval? y W3C Standard for XML Document Navigation since 2001 y Support for XML Schema Data Types in 2.0 y Support for Functions and Operators in 2.0 y Underlies XSLT, XQuery, DOM, XForms, XPointer Current Standards-based Data Retrieval Strategies y Document Object Model (DOM) Parsing y Simple API for XML Parsing (SAX) y Java API for XML Parsing (JAXP) y Streaming API for XML Parsing (StAX) Data Retrieval Using DOM Parsing y Advantages – Dynamic random access to entire document – Supports XPath 1.0 y Disadvantages – DOM In-memory footprint up to 10x doc size – No planned support for XPath 2.0 – Redundant node traversals for multiple XPaths DOM-based XPath Data Retrieval A 1 1 2 2 1 /A/B/C 2 /A/B/C/D B F B 1 2 E C C 2 F D Data Retrieval using SAX/StAX Parsing y Advantages – Stream-based processing for managed memory – Broadcast events for multicasting (SAX) – Pull parsing model for ease of programming and control (StAX) y Disadvantages – No maintenance of hierarchical structure – No XPath Support either 1.0 or 2.0 High Performance Requirements y Retrieve XML data with managed memory resources y Support for documents of all sizes y Handle multiple XPaths with minimum node traversals
    [Show full text]
  • Java Parse Xml Document
    Java Parse Xml Document incontrovertibilityPained Swen smarts limites no kindly.grantee Curled invoiced Georges uncommon devocalises after Zollie laughably. mithridatizing snatchily, quite hypotactic. Sicklied Marshall smudges his Once we print and added to access the de facto language that java xml In java dom available and how to apply to have treated as deserializing our web site may sponsor a parser that are frequently by. Processing a large XML file using a SAX parser still requires constant fight But, still the complete hand, parsing complex XML really becomes a mess. Parsing Reading XML file in Java GitHub. The dom4j API download includes a color for parsing XML documents. Thanks for voice clear explanation. JavaxxmlparsersDocumentBuilderparse java code Codota. StringReaderxmlRecords Document doc dbparseis NodeList nodes doc. The DOM has different bindings in different languages. Why you how did you need it, pearson collects your document object consumes a dom. This document describes the Java API for XML Parsing Version 10. For parsing the XML use XPath and for it text file based approach use Java Property Riles Hope that helps a bit Cheers MRB. The first corn is used for documents with possible specific target namespace, the brew for documents without a namespace. Xml allows us learn and written here we create a real time consumption and share data binding, into a good for parsing json. Fast Infoset techniques while man with XML content in Java. Parsing XML using DOM4J Java API BeginnersBookcom. Continued use for building blocks the ui thread however, string in an event in document can update your app to handle to.
    [Show full text]
  • Java API for XML Processing
    4 Java API for XML Processing THE Java API for XML Processing (JAXP) is for processing XML data using applications written in the Java programming language. JAXP leverages the parser standards SAX (Simple API for XML Parsing) and DOM (Document Object Model) so that you can choose to parse your data as a stream of events or to build an object representation of it. JAXP also supports the XSLT (XML Stylesheet Language Transformations) standard, giving you control over the pre- sentation of the data and enabling you to convert the data to other XML docu- ments or to other formats, such as HTML. JAXP also provides namespace support, allowing you to work with DTDs that might otherwise have naming conflicts. Designed to be flexible, JAXP allows you to use any XML-compliant parser from within your application. It does this with what is called a “pluggability layer”, which allows you to plug in an implementation of the SAX or DOM APIs. The pluggability layer also allows you to plug in an XSL processor, letting you control how your XML data is displayed. The JAXP APIs The main JAXP APIs are defined in the javax.xml.parsers package. That package contains two vendor-neutral factory classes: SAXParserFactory and 115 116 JAVA API FOR XML PROCESSING DocumentBuilderFactory that give you a SAXParser and a DocumentBuilder, respectively. The DocumentBuilder, in turn, creates DOM-compliant Document object. The factory APIs give you the ability to plug in an XML implementation offered by another vendor without changing your source code. The implementation you get depends on the setting of the javax.xml.parsers.SAXParserFactory and javax.xml.parsers.DocumentBuilderFactory system properties.
    [Show full text]
  • A Performance Based Comparative Study of Different Apis Used for Reading and Writing XML Files
    A Performance Based Comparative Study of Different APIs Used for Reading and Writing XML Files A Thesis submitted to the Graduate School at the University of Cincinnati In Partial Fulfillment of the requirements for the Degree of MASTER OF SCIENCE In the School of Electronics and Computing Systems of the College of Engineering and Applied Sciences By Neha Gujarathi Bachelor of Engineering (B. E.), 2009 University of Pune, India Committee Chair: Dr. Carla Purdy ABSTRACT Recently, XML (eXtensible Markup Language) files have become of great importance in business enterprises. Information in the XML files can be easily shared across the web. Thus, extracting data from XML documents and creating XML documents become important topics of discussion. There are many APIs (Application Program Interfaces) available which can perform these operations. For beginners in XML processing, selecting an API for a specific project is a difficult task. In this thesis we compare various APIs that are capable of extracting data and / or creating XML files. The comparison is done based on the performance time for different types of inputs which form different cases. The codes for all the different cases are implemented. Two different systems, one with Windows 7 OS and another with Mac OS are used to perform all the experiments. Using the results found we propose a suitable API for a given condition. In addition to the performance, programming ease for these APIs is taken into consideration as another aspect for comparison. To compare the programming ease, aspects such as number of lines of code, complexity of the code and complexity of understanding the coding for the particular API are considered.
    [Show full text]
  • An Empirical Analysis of XML Parsing Using Various Operating Systems
    International Journal of Engineering and Applied Sciences (IJEAS) ISSN: 2394-3661, Volume-2, Issue-2, February 2015 An Empirical Analysis of XML parsing using various operating systems. Amitesh Saxena, Dr. Snehlata Kothari used everywhere in software. An XML Parser is a parser that Abstract— As the use of internet technologies are widely is designed to read XML and create a way for programs to use increasing, the XML markup language attains a remarkable XML. There are different types, and each has its advantages. importance due to its language neutrality and independency in Unless a program simply and blindly copies the whole using data exchange and data transfer through web XML file as a unit, every program must implement or call on environment mechanism. For improving the processing an XML parser. performance of XML parser, it is necessary to find out a mechanism, in which we get minimum processing time while B. DOM (Document Object Model) parsing of XML documents. In this paper, XML documents are being experimentally It supports navigating and modifying XML documents tested using various operating systems to determine, whether an - Hierarchical tree representation of document operating system effect the processing time of XML parsing. - Tree follows standard API - Creating tree is vendor specific Index Terms— XML Parser, DOM Parser, Operating DOM is a language-neutral specification system. - Binding exist for Java, C++, CORBA, JavaScript, C# - can switch to other language. I. INTRODUCTION The Document Object Model (DOM) is In Present world, mega information are sharing and an interface-oriented application programming interface that transmitting, In this XML plays a very significant role as a allows for navigation of the entire document as if it were a tree worldwide design for data interchange.
    [Show full text]
  • Java API for XML Processing (JAXP)
    Java API for XML Processing (JAXP) • API that provides an abstraction layer to XML parser implementations (specifically implementations of DOM and SAX), and applications that process Extensible Stylesheet Language Transformations (XSLT) • JAXP is is a layer above the parser APIs that makes it easier to perform some vendor-specific tasks in a vendor-neutral fashion. JAXP employs the Abstract Factory design pattern to provide a plugability layer, which allows you to plug in an implementation of DOM or SAX, or an application that processes XSLT • The primary classes of the JAXP plugability layer are javax.xml.parsers.DocumentBuilderFactory, javax.xml.parsers.SAXParserFactory, and javax.xml.transform.TransformerFactory. • Classes are abstract so you must ask the specific factory to create an instance of itself, and then use that instance to create a javax.xml.parsers.DocumentBuilder, javax.xml.parsers.SAXParser, or javax.xml.transform.Transformer, respectively. • DocumentBuilder abstracts the underlying DOM parser implementation, SAXParser the SAX parser implementation, and Transformer the underlying XSLT processor. DocumentBuilder, SAXParser, and Transformer are also abstract classes, so instances of them can only be obtained through their respective factory. JAXP Example - 1 import java.io.*; import javax.xml.*; import org.w3c.dom.Document; import org.xml.sax.SAXException; import javawebbook.sax.ContentHandlerExample; public class JAXPTest { public static void main(String[] args) throws Exception { File xmlFile = new File(args[0]); File
    [Show full text]
  • XML Programming in Java Technology, Part 1 Skill Level: Introductory
    XML programming in Java technology, Part 1 Skill Level: Introductory Doug Tidwell ([email protected]) XML Evangelist 13 Jan 2004 This updated tutorial covers the basics of manipulating XML documents using Java technology. Doug Tidwell looks at the common APIs for XML and discusses how to parse, create, manipulate, and transform XML documents. Section 1. Introduction About this tutorial Over the last few years, XML has become a universal data format. In this updated tutorial, I'll show you the most common programming interfaces for working with XML documents in the Java language. The most common XML processing task is parsing an XML document. Parsing involves reading an XML document to determine its structure and contents. One of the pleasures of XML programming is the availability of open-source, no-cost XML parsers that read XML documents for you. This tutorial focuses on creating parser objects, asking those parsers to process XML files, and handling the results. As you might expect, you can do these common tasks in several different ways; I'll examine the standards involved as well as when you should use one approach or another. Programming interfaces A number of programming interfaces have been created to simplify writing Java programs that process XML. These interfaces have been defined by companies, by standards bodies, and by user groups to meet the needs of XML programmers. In this tutorial, I'll cover the following interfaces: • The Document Object Model (DOM), Level 2 • The Simple API for XML (SAX), Version 2.0 XML programming in Java technology, Part 1 © Copyright IBM Corporation 1994, 2005.
    [Show full text]
  • Simple API for XML SAX
    core programming Simple API for XML SAX 1 © 2001-2003 Marty Hall, Larry Brown http://www.corewebprogramming.com Agenda • Introduction to SAX • Installation and setup • Steps for SAX parsing • Defining a content handler • Examples – Printing the Outline of an XML Document – Counting Book Orders • Defining an error handler • Validating a document 2 SAX www.corewebprogramming.com Simple API for XML (SAX) • Parse and process XML documents • Documents are read sequentially and callbacks are made to handlers • Event-driven model for processing XML content • SAX Versions – SAX 1.0 (May 1998) – SAX 2.0 (May 2000) • Namespace addition – Official Website for SAX • http://sax.sourceforge.net/ 3 SAX www.corewebprogramming.com SAX Advantages and Disadvantages • Advantages – Do not need to process and store the entire document (low memory requirement) • Can quickly skip over parts not of interest – Fast processing • Disadvantages – Limited API • Every element is processed through the same event handler • Need to keep track of location in document and, in cases, store temporary data – Only traverse the document once 4 SAX www.corewebprogramming.com Java API for XML Parsing (JAXP) • JAXP provides a vendor-neutral interface to the underlying SAX 1.0/2.0 parser SAXParser XMLReader Parser SAX 2.0 SAX 1.0 5 SAX www.corewebprogramming.com SAX Installation and Setup (JDK 1.4) • All the necessary classes for SAX and JAXP are included with JDK 1.4 • See javax.xml.* packages • For SAX and JAXP with JDK 1.3 see following viewgraphs 6 SAX www.corewebprogramming.com SAX Installation and Setup (JDK 1.3) 1. Download a SAX 2-compliant parser • Java-based XML parsers at http://www.xml.com/pub/rg/Java_Parsers • Recommend Apache Xerces-J parser at http://xml.apache.org/xerces-j/ 2.
    [Show full text]
  • Analyzing XML Parsers Performance for Android Platform
    M V Uttam Tej et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 2 (3) , 2011, 973-976 Analyzing XML Parsers Performance for Android Platform M V Uttam Tej ,Dhanaraj Cheelu, M.Rajasekhara Babu, P Venkata Krishna SCSE, VIT University, Vellore, Tamil Nadu Abstract—As Internet communication technologies are growing up. when an even occurs during the parsing mechanism. XML Text XML are rising up as a popular way for data transfer and for nodes, Element nodes etc are the events which are included in exchange of data across the Internet. Now a day’s choosing the right parser for a task is crucial and critical since improper parser will the SAX Parsing [2] mechanism. lead to degradation and effect in performance and productivity. In 2 DOM Parser:- this paper we have done tedious extensive comparative study on DOM stands for Document Object Model [3] is a standard various xml parsers available for Android Mobile Platform. Keywords-XML Parser; SAX Parser; DOM Parser; PULL Parser; model for parsing the xml document. Generally it is an VTD-XML Parser; Android. application for validating XML Documents. It defines the logical structure of documents and the way a document is I. INTRODUCTION accessed and manipulated. It defines the objects and properties XML stands for eXtensible Markup Language. It is a of all elements in xml and the methods to access them .It set of rules which goals to achieve generality, simplicity represents entire document in tree structure. It treats everything and usability over the Internet. XML is a powerful defacto as a form of node and the real text is present in the form of text standard which is mainly intended to store, data transfer node.
    [Show full text]
  • PDF Output with the FOP Serializer
    Oracle® XML Developer's Kit Programmer©s Guide 12c Release 1 (12.1) E54405-06 December 2016 Provides information to application developers who need to use components of the Oracle XML Developer's Kit (XDK) to generate and store XML data in a database or in a document outside the database. Oracle XML Developer's Kit Programmer's Guide, 12c Release 1 (12.1) E54405-06 Copyright © 2001, 2016, Oracle and/or its affiliates. All rights reserved. Primary Authors: Drew Adams, Lance Ashdown, Janis Greenberg, Sheila Moore, Sue Pelski Contributors: Nipun Agarwal, Geeta Arora, Vikas Arora, Thomas Baby, Janet Blowney, Dan Chiba, Steve Ding, Mark Drake, Beda Hammerschmidt, Bill Han, Roza Leyderman, Dmitry Lychagin, Valarie Moore, Steve Muench, Ravi Murthy, Maxim Orgiyan, Mark Scardina, Helen Slattery, Joshua Spiegel, Asha Tarachandani, Jinyu Wang, Simon Wong, Tim Yu, Kongyi Zhou This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S.
    [Show full text]
  • Important Aspect for Designing an Efficient Xml Parsing Technique: a Review
    International Journal For Technological Research In Engineering ISSN (Online): 2347 - 4718 National Conference on Importance of Inter-disciplinary Studies in Higher Education in the areas of Engineering, Science, Management and Humanities (February – 2018) IMPORTANT ASPECT FOR DESIGNING AN EFFICIENT XML PARSING TECHNIQUE: A REVIEW Swati Gupta1, Prof. Y.P. Singh2 School of Engineering, University of Technology, Jaipur Abstract: Internet has become the main aspect for parsing across few commercial database applications. For a searching and transfer of information. For the same database transaction, the computational cost is increased reason, it requires a language to represent and transfer twice or trice by parsing even a small XML document [9]. In information. XML (eXtensible Markup Language) acts as 2006, Tong, T. et al, gave their reviews about the XML the standard for representing and interchanging data and parser. According to their study, tree-based approach is not information on web. The core operation performed on XML feasible for large size XML documents because it requires document is parsing. Parsing is used to access and memory to store the entire document and for bigger files, it manipulate XML data. But this parsing process is also one can easily run out of memory [4]. In 2009, Lan Xiaoji et. al. of the biggest hindrance in the development of XML. This explains a new parsing model named VTD-XML. It is an paper is a review of different parsing techniques which are open source model, based on the technique called Virtual used to perform the core operation on XML document. Token Descriptor (VTD). Major characteristics of this model Keywords: XML Parsing, DOM, SAX, Data Structure is random access capability, high performance and low Parsing, Database Parsing memory usage [11].
    [Show full text]