XML-GL: a graphical language for querying and restructuring XML documents
WWW '99 Proceedings of the eighth international conference on World Wide Web
VXT: a visual approach to XML transformations
DocEng '01 Proceedings of the 2001 ACM Symposium on Document engineering
A Visual Approach to XML Document Design and Transformation
HCC '01 Proceedings of the IEEE 2001 Symposia on Human Centric Computing Languages and Environments (HCC'01)
XMLTrans: a Java-based XML transformation language for structured data
COLING '00 Proceedings of the 18th conference on Computational linguistics - Volume 2
Graph transformation to infer schemata from XML documents
Proceedings of the 2005 ACM symposium on Applied computing
XQBE (XQuery By Example): A visual interface to the standard XML query language
ACM Transactions on Database Systems (TODS)
On the interoperability of model-to-model transformation languages
Science of Computer Programming
A Case for ViewPoints and Documents
Innovations for Requirement Analysis. From Stakeholders' Needs to Formal Designs
Graphical definition of in-place transformations in the eclipse modeling framework
MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
Hi-index | 0.00 |
As XML diffusion keeps increasing, it is today common practice for most developers to deal with XML parsing and transformation. XML is used as format to e.g. render data, query documents, deal with Web services, generate code from a model or perform model transformation. Nowadays XSLT is the most common language for XML transformation. But, although meant to be simple, coding in XSLT can become quite a challenge, if the coding approach does not only depend on the structure of the source document, but the order of template application is also dictated by target document structure. This is the case especially when dealing with transformations between visual models. We propose to use a graph-based approach to simplify the transformation definition process where graphs representing documents are transformed in a rule-based manner, as in XSLT. The differences to XSLT are mainly that rules can be developed visually, are more abstract (since the order of execution does not depend on the target document), IDREFs are dealt with much more naturally, and due to typed transformations, the output document is guaranteed to be valid with respect to the target schema. Moreover, graph-based transformation definitions can be automatically reversed in most cases. This is especially useful in model transformation (e.g. in OMG's MDA approach).