XML Document Recovery via Change Record Rollback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing XML Document Management (XDM) system does not support document recovery to a previous state, limiting user applications as users cannot revert changes made to XML documents.
Innovation Solution
An XML document management method and system that stores change records, determines whether to store them, controls their size, and allows users to recover documents to a previous version by reversing operations sequentially based on stored records, using XCAP or HTTP POST requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If change records are stored for document recovery, then document recovery capability is improved, but system complexity increases
Solution Approach 1:
The system performs preliminary action by storing change records at the time of document modifications. This allows the document recovery function to be implemented without complex real-time analysis, as all necessary information is pre-captured in structured change records that can be directly applied during recovery operations.
Solution Approach 2:
Instead of maintaining multiple full document versions, the system creates simplified copies of only the changed elements (diffs). These change records are lightweight representations that capture the essence of modifications without duplicating entire documents, reducing storage overhead and system complexity.
2Reliability
If all change records are stored, then complete document recovery is improved, but storage space consumption increases
Solution Approach 1:
The system extracts and stores only the essential change information (diffs) rather than complete document states. Each change record contains minimal necessary data to reconstruct the modification, separating the critical recovery information from redundant document content.
Solution Approach 2:
The system transforms change records into a compact parameter-based representation. Instead of storing full document snapshots, it stores parameterized change descriptions that can be efficiently stored and applied, reducing the quantity of stored data while maintaining recovery completeness.
3Quantity of substance
If change record size is controlled, then storage efficiency is improved, but recovery accuracy may deteriorate
Solution Approach 1:
The system creates accurate but compact copies of change information. The change records are simplified representations that retain all essential recovery information while eliminating redundant data, achieving both storage efficiency and recovery accuracy.
Solution Approach 2:
The system uses parameter-based encoding to represent changes efficiently. By storing changes as parameterized operations rather than full document states, it achieves compact storage while maintaining the precision needed for accurate document recovery.
Data Source
AI summary
An extensible markup language document management method includes: receiving a document recovery request from a user; and recovering a version of the document as required by a user from the current version of the document, in accordance with the change records for the document. An extensible markup language document management system includes: a rollback control module, adapted to recover a version of a document as required by a user from the current version of the document, in accordance with change records for the document, upon receiving a document recovery request from the user.