Adding Temporal Constraints to XML Schema

NANO SCIENTIFIC RESEARCH CENTRE PVT.LTD.,  AMEERPET, HYD

WWW.NSRCNANO.COM, 09640648777, 09652926926

JAVA PROJECTS LIST--2013

JAVA 2013 IEEE PAPERS

Adding Temporal Constraints to XML Schema

Abstract

            If past versions of XML documents are retained, what of the various integrity constraints defined in XML Schema on those documents? This paper describes how to interpret such constraints as sequenced constraints, applicable at each point in time. We also consider how to add new variants that apply across time, so-called non-sequenced constraints. Our approach supports temporal documents that vary over both valid and transaction time, whose schema can vary over transaction time. We do this by replacing the schema with a (possibly time-varying) temporal schema and replacing the document with a temporal document, both of which are upward compatible with conventional XML and with conventional tools like XMLLINT, which we have extended to support the temporal constraints introduced here.

Existing System:

            AS with prose documents, spreadsheets, presentations, and data in a database, XML documents also are changed over time. Also, as with these other kinds of documents and as with data in a database, users often would like to retain past versions of XML documents, for several reasons. One, those past versions may contain useful historical information. Second, various laws such as the Sarbanes-Oxley Act [1] require that for data that appear in financial reports drawn from prior versions, that those versions be retained for a stated period of time. Third, retaining past versions allows previously written reports using that data to remain consistent, even if new versions are subsequently added. With XML becoming more prevalent as both a transmission encoding and a document encoding format, it thus becomes important to retain prior versions of an XML document. And indeed, a rich literature on this subject has emerged [2]. Given the existence of such prior versions, one then can ask, what of the various integrity constraints defined on that document? How can such constraints be generalized to apply not just to the current version, but across the entire history of the XML document? And how can new, explicitly temporal constraints be defined? Finally, how can all this be managed effectively over schema changes, which are a fact of life in complex enterprises?

Proposed System:

            Our design of an upward-compatible extension of XML Schema, τXSchema [4] addresses the first two concerns emphasized in the previous paragraph. τXSchema supports temporal documents that vary over both valid and transaction time [5], [6], [7], whose schema can vary over transaction time [8], and for which validation is a simple process (to the user) of checking a time-varying document over a schema, which itself is a time-varying document [9], [10]. Related work has formalized language primitives required for managing schema versioning with τXSchema [11].

Software Requirement Specification

Software Specification

Operating System       :           Windows XP

Technology                 :           JAVA 1.6, JMF

Hardware Specification

Processor                     :           Pentium IV

RAM                           :           512 MB

Hard Disk                   :           80GB

Modules:

• Squash

            Squash can render a temporal document consistent with the logical and physical annotations. Hence, the time stamps are spread out across the document, associated with versions of the elements. This removes a great deal of redundancy found in the non-temporal data, which represents each slice as a separate document.

• UnSquash

            UnSquash can divides the records in temporal Squashed Document into several Slices according Time.

� b e g �� �-� ont-family:"Times New Roman","serif"'> 

Modules:

·         Client

·         Router

·         Server

·         Hash Calculation

Trapdoor Hash Verification