Temporal and multi-versioned XML documents: A survey

Faisal, Sidra; Sarwar, Mansoor

doi:10.1016/j.ipm.2013.08.003

Cited by 20 publications

(5 citation statements)

References 48 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the XML field, a bibliography of work about temporal representation and evolution of documents and data on the web has been presented in [31]. A recent survey [7] explores several issues related to evolving XML documents (including change detection between versions of XML documents by using deltas, object references, or relational approaches, versioning support, and trend analysis queries), and studies change management features in some commercial tools.…”

Section: Related Work and Discussionmentioning

confidence: 99%

“…When XML data of different temporal formats can coexist in the same XML repository, we talk about a multitemporal XML repository. Whereas schema versioning is required by several applications using multitemporal XML repositories, both commercial XML tools and DBMSs have no support for that feature (including Altova's XMLSpy, LiquidXML Studio, or OXygen's XML Editor, and Oracle 11g, Tamino, or DB2 v.9, as surveyed in [7] but the same also applies to the latest releases of such systems). Therefore, XML Schema designers and developers use ad hoc methods to manage schema versioning.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

High-Level Operations for Creation and Maintenance of Temporal and Conventional Schema in the tauXSchema Framework

Brahmia

Grandi

Oliboni

et al. 2014

2014 21st International Symposium on Temporal Representation and Reasoning

View full text Add to dashboard Cite

tauXSchema is a framework for constructing and validating time-varying XML documents through the use of a temporal schema. This latter ties together a conventional schema (i.e., a standard XML Schema document) and its corresponding logical and physical annotations, which are stored in an annotation document. Conventional schema and logical and physical annotations undergo changes to respond to changes in user requirements or in the real-world. Consequently, the corresponding temporal schema is also evolving over time. In this paper, we study operations which help designers for changing such schema components. Indeed, we propose three sets of highlevel operations for changing temporal schema, conventional schema, and annotations. These high-level operations are based on the low-level operations proposed in our previous work [11,12,14,15,16]. They are also consistency preserving and more user-friendly than the low-level operations. Besides, we have divided the proposed operations into basic high-level operations (i.e., high-level operations that cannot be defined by using other basic high-level operations) and complex ones.

show abstract

Section: Related Work and Discussionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

High-Level Operations for Creation and Maintenance of Temporal and Conventional Schema in the tauXSchema Framework

Brahmia

Grandi

Oliboni

et al. 2014

2014 21st International Symposium on Temporal Representation and Reasoning

View full text Add to dashboard Cite

show abstract

“…To the best of our knowledge, although retroactive updates are allowed by existing data manipulation languages [e.g., the standard SQL (Kulkarni and Michels, 2012)], the current W3C recommendation for managing XML data: XQuery update facility (W3C, 2011)) and mainstream DBMSs (e.g., Oracle, SQL Server, DB2, Tamino) (Faisal and Sarwar, 2014), there is no automatic support for managing the effects of these updates and repairing inconsistencies which could result from them. Therefore, faced with this lack of appropriate tools, database application developers have to try to solve the problem in an ad hoc manner.…”

Section: Lack Of Practical Support For Managing the Effects Of Retroamentioning

confidence: 99%

A systematic approach to efficiently managing the effects of retroactive updates of time-varying data in multiversion XML databases

Hamrouni

Brahmia

Bouaziz

2018

IJIIDS

View full text Add to dashboard Cite

A retroactive update is an update that changes a past data. It is a common operation in both conventional and temporal databases. However, in temporal databases, a retroactive update is challenging since it could lead to data inconsistencies if the retroactively updated data were used for creating other data (like social contributions and taxes which are calculated based on the salaries of the employees). Such data inconsistencies must be repaired in order to preserve the database consistency. In this paper, we extend our previous approach on detecting and repairing automatically data inconsistencies that result from retroactive updates of multiversion temporal XML databases. The extension consists in: 1) providing an enhanced version of the architecture of our approach and explaining the process of handling a retroactive update; 2) showing how to extract data dependencies and how to use them in order to repair detected inconsistencies; 3) proposing a new log structure ensuring a complete and useful history of the executed transactions; 4) presenting a tool, named Retro-Update-Manager, that we have developed to prove technically our approach.Reference to this paper should be made as follows: Hamrouni, H., Brahmia, Z. and Bouaziz, R. (2018) 'A systematic approach to efficiently managing the effects of retroactive updates of time-varying data in multiversion XML databases', Int.

show abstract

“…The overall evaluation process is an instance of the general two-phase approach described in the previous section, as depicted in Figure 8. Since all algorithms produce deltas in XML, we implemented converters as XSLT transformations 1 . The UniDM deltas have been serialised in a XML format, whose syntactic details are not relevant for our discussion.…”

Section: Applying the Metrics To Xml Diff Algorithmsmentioning

confidence: 99%

“…The outputs of diff algorithms, usually called deltas, diffs or patches, are used for many purposes: programmers review source code diffs to avoid adding bugs and to understand which parts of the code has changed; editors highlight the changes made on drafts and pre-prints; law makers compare proposals during the discussion and approval of a bill; philologists use the differences between documents to recreate the stemma codicum of a text, the history of its development. An exhaustive survey on change detection and versioning tools can be found in [1].…”

Section: Introductionmentioning

confidence: 99%