|
It's desirable to generate XSLT transformation from some simple specifiction. The difficulty, however, is right with the specifition itself. If the syntax and semantics of the specifiction changes often, the generator has to be changed accordingly and the idea misses its goal. So, what's desired is really a versatile yet simple "conversion specification language", which has to be something very formal and well-defined. If we replace the word "conversion" with "transformation", it becomes a "transformation specification language", and finally "transformation language" in short. So, it ends at XSL Transformation.
You seems to suggest defining a simple syntax specially for one office. That will work, if the office business changes very slowly.
|