Consistency Check between XML Schema and Class Diagram for Document Versioning

A consistency check between design and implementation is usually done in order to check the correctness of the system’ requirements. However, if the requirements are changed over time, then the document versioning occurred within the requirements. For XML Schema, document versioning exists when there is a change in the XML Schema from its previous Schema. In order to detect the versioning of both XML Schemas, consistency rules check need to be performed to both class diagrams produced by both Schemas. The consistency between two XML Schemas is checked based on transformation rules and versioning rules. Transformation rules are used for translating the XML Schema into the class diagram, and versioning rules are used for checking the existing of document changes between two XML Schemas. Once two XML Schemas are different the consistency rules will be used for the consistency check. This paper presents an approach based on transformation rules and versioning rules to check consistency between XML Schema and UML class diagram when document versioning exist. The approach is then used for the case study to show how the consistency is checked in order to detect the versioning of two different XML Schemas. Based on the case study, the approach shows that two XML Schemas can be checked for their consistency when document versioning exist.

Updates on XML Documents and Schemas

In a dynamic and heterogeneous world as the Web, the need often arises to update XML data, as well as their structures, to adhere to new domain requirements. Updates may break compliance of data to schemas, and updates at schema level may in addition require to adapt associated documents to the new schema. Moreover, emerging application contexts in which updates come from different sources, such as collaborative editing, versioning, cloud computing, and disconnected execution, are more and more relevant. The main goals of this thesis are: (i) to support data and schema updates as an integrated process, investigating the mutual implications of updating either data or schema on the other, (ii) to develop a flexible framework for dynamically reasoning on XML updates, applicable in different contexts and (iii) to study provenance in the context of our XML update framework, introducing the possibility of storing and querying each individual update information to trace the data lineage