A template language is the input to a transformation (and the transformation is usually fixed, at least relatively fixed). XSL specifies the transformation, not the input language, so it isn't a template language in my mind, but that's probably largely a matter of semantics. An XSL style sheet could accept an (XML-based) template language as input, but XML-based languages have notoriously poor usability.
As for simplicity, I'm much more familiar with XSL than I'd like to be and you're unlikely to convince me that anything where I have to cross reference multiple independent specifications is "simple." Having said that, as Bob says, we do use XSL and we've got a need for XSL superstars. If you'd like to show off your XSL chops, fix our UML 1.3 to UML 1.4 converter for us. It's an XSL style sheet that was written in a procedural style that matches up poorly with XSLs declarative style and it chokes on large documents. http://argouml.tigris.org/issues/show_bug.cgi?id=4188 http://argouml.tigris.org/source/browse/*checkout*/argouml/trunk/src/argouml-core-model-mdr/src/org/argouml/model/mdr/conversions/uml13touml14.xsl Tom ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1043584 To unsubscribe from this discussion, e-mail: [[email protected]].
