Effective storage structure for multi-version XML documents

Chang Chih-Chun, Cheng Ming-Shien, Hsu Ping-Yu

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

1 Scopus citations

Abstract

Office applications such as OpenOffice.org and Microsoft office are widely used to do everything you expect from your needs. Because of more and more requirements of information exchange and retrieve, XML becomes a standard in doing this way. With the adoption of using XML in both office application groups, the abilities for efficient storing historical office documents are become a growing issue. This paper introduces an efficient way to process multi-version XML documents. It is not only effective storage space need but also keeping the integral of original documents. It minimizes the change of data values or structures transmutation of historical XML documents. The purpose is to well-managed electronic documents for enterprises and all the messages were involved in should be preserved.

Original languageEnglish
Title of host publicationFuture Generation Information Technology - Second International Conference, FGIT 2010, Proceedings
Pages249-266
Number of pages18
DOIs
StatePublished - 2010
Event2nd International Mega-Conference on Future Generation Information Technology, FGIT 2010 - Jeju Island, Korea, Republic of
Duration: 13 Dec 201015 Dec 2010

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume6485 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

Conference2nd International Mega-Conference on Future Generation Information Technology, FGIT 2010
Country/TerritoryKorea, Republic of
CityJeju Island
Period13/12/1015/12/10

Keywords

  • Historical document
  • OpenOffice.org
  • Storage structure
  • XML

Fingerprint

Dive into the research topics of 'Effective storage structure for multi-version XML documents'. Together they form a unique fingerprint.

Cite this