Scribd
Upload
50 views5 pages

ÞC ÞC ÞC ÞC ÞC ÞC ÞC ÞC ÞC

An XML parser converts an XML document into an XML DOM object that can be manipulated with JavaScript. It shields applications from XML complexities like encoding, resolving references, and validating against DTDs. The parser represents each XML document as a Document object containing other objects that can be searched, queried and updated via methods. This project aims to develop an engine that reads XML files and builds a DOM model accessible to calling programs, allowing manipulation with JavaScript since it contains no browser facilities. The parser will use DOM trees for every XML file and can be combined with any XML-capable application on any platform or network.

Uploaded by

Akanksha Jani
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
50 views5 pages

ÞC ÞC ÞC ÞC ÞC ÞC ÞC ÞC ÞC

An XML parser converts an XML document into an XML DOM object that can be manipulated with JavaScript. It shields applications from XML complexities like encoding, resolving references, and validating against DTDs. The parser represents each XML document as a Document object containing other objects that can be searched, queried and updated via methods. This project aims to develop an engine that reads XML files and builds a DOM model accessible to calling programs, allowing manipulation with JavaScript since it contains no browser facilities. The parser will use DOM trees for every XML file and can be combined with any XML-capable application on any platform or network.

Uploaded by

Akanksha Jani
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

INTRODUCTION

OVERVIEW

An XML parser is a piece of software that converts an XML document into an XML DOM
object - which can then be manipulated with a JavaScript.
To avoid the difficulties inherent in parsing raw XML input, almost all programs that need to
process XML documents rely on an XML parser to actually read the document. The parser is a
software library (in Java, it's a class) that reads the XML document and checks it for well-
formedness. Client applications use method calls defined in the parser API to receive or request
information that the parser retrieves from the XML document.
The parser shields the client application from all of the complex and not particularly relevant
details of XML, including

 Transcoding the document to Unicode

 Assembling the different parts of a document divided into multiple entities

 Resolving character references

 Understanding CDATA sections

 Checking hundreds of well-formedness constraints

 Maintaining a list of the namespaces in scope on each element

 Validating the document against its DTD or schema

 Associating unparsed entities with particular URLs and notations

 Assigning types to attributes

Each XML document is represented as a Document object. Documents are searched, queried, and
updated by invoking methods on this Document object and the objects it contains.
OBJECTIVE AND SCOPE

OBJECTIVE:

The aim of this project is to develop an engine that reads in an xml file and tries to built a
DOM(Document Object Model) from it in a format that is accesible from whatever program
which is calling it which can then be manipulated using a java script.
The direction of this project is to build a XML PARSER which uses DOM TREE for every xml
file it reads, as the java script itself contains no facilities for interacting with the browser ,such
facilities are provided by browser in the form of host object that are stored as properties of java
script global object. The definition of the properties of these object is known as document object
model.

SCOPE:

 It can be combined with any application which is capable of processing XML irrespective
of the platform it is being used on.
 It can be deployed on any network if it is amicable for usage with the application in use.
 If the application can work along with XML, then XML can work on any platform and
has no boundaries.
 It is also vendor independent and system independent. While data is being exchanged
using XML, there will be no loss of data even between systems that use totally different
formats.
 DOM has great advantages, including its simplicity, powerful access to the document,
popularity, and well-defined specification. It also pairs nicely with XSLT and other
document-transformation solutions you may require. DOM implementations are currently
biased towards in-memory storage of the document, but this may change as PDOM
implementations become more popular. Programming DOM code becomes even easier

ORGANIZATION OF REPORT

1. INTRODUCTION:
This is the first chapter of our report. In this we have given a brief overview of our
project, specifying how and what the project is going to work. We have also given the
main purpose i.e. the objective and scope of the project.

2. BACKGROUND AND LITERATURE SURVEY:


In this chapter we mainly focus on the literature survcy and feasibily of the project.We
discuss it under the following heads:
a) SRS: This is the Software Requirement Specification.It describes about the basic
necessities of the project.
b) Feasibility Report: Here we tell about the usefullness of our project.Its
innovativeness, market potential and advantages in the software environment is
concerned deeply.
c) Proposed Model: This describes the virtual shape that the project will take up after
completion.

3. PROCESS MODEL:
This discusses about the software implementation of the project.It includes:
a) SDLC: Software Development Life Cycle describes how the project will work
according to timeline.
b) Proposed Process Model: The proposed process model for our project is the Waterfall
model.
c) Project plan: This is the working criteria of project .
d) Project Schedule: This tells about the proceeding of the project with time.

4. DESIGN IMPLEMENTATION:
This includes all diagrams associated with the project.

5. TECHNICAL DETAILS:
It tells about:
a) Software Specification: The software used in the project is specified.
b) Hardware Specification: The total capacity of h/w required is specified.

6. FUTURE WORKS:
It includes the future scope of the project.

7. REFRENCES;
It provides all the sites referred for the project.

You might also like