XML type checking with macro tree transducers
Proceedings of the twenty-fourth ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems
Taxonomy of XML schema languages using formal language theory
ACM Transactions on Internet Technology (TOIT)
Preserving XML queries during schema evolution
Proceedings of the 16th international conference on World Wide Web
Managing and querying transaction-time databases under schema evolution
Proceedings of the VLDB Endowment
Tree Pattern Rewriting Systems
ATVA '08 Proceedings of the 6th International Symposium on Automated Technology for Verification and Analysis
Semantics, Types and Effects for XML Updates
DBPL '09 Proceedings of the 12th International Symposium on Database Programming Languages
XML schema, tree logic and sheaves automata
RTA'03 Proceedings of the 14th international conference on Rewriting techniques and applications
CODS: evolving data efficiently and scalably in column oriented databases
Proceedings of the VLDB Endowment
Impact of XML Schema Evolution
ACM Transactions on Internet Technology (TOIT)
Updating XML schemas and associated documents through exup
ICDE '11 Proceedings of the 2011 IEEE 27th International Conference on Data Engineering
Computing transitive closures of hedge transformations
VECoS'07 Proceedings of the First international conference on Verification and Evaluation of Computer and Communication Systems
XML schema evolution: incremental validation and efficient document adaptation
XSym'07 Proceedings of the 5th international conference on Database and XML Technologies
| Hi-index | 0.00 |
In this paper we propose a framework for XML data and schema co-evolution that allows to check whether a user-proposed document adaptation (i.e., a sequence of document update operations intended to adapt the documents valid for a schema to a new schema) is guaranteed to produce a document valid for the updated schema. The proposed framework can statically determine, working only with the automata related to the original and modified schema, if the document update operation sequence will re-establish document validity, thus avoiding the very expensive run-time revalidation of the set of involved documents that is usually performed upon schema update.