Subject:XSL Relationship Export Author:Michael Shephard Date:17 Mar 2005 07:38 PM
We are building a sizeable number of XSL transforms as a part of an
integration project. Being a large organisation with lots of bureaucracy
we need to be able to produce an output of our mappings for sign-off
I am wondering if there is any way to export the "relationships" exhibited
in an XSL to other formats (csv, html, whatever!).
Christian Menapace posted a question similar to this on the 15th Feb 2005
but the response described the documentation of a schema. What we are after
and I think what Christian was after is a method of documenting an XSL.
>We have to communicate with
>many end users the description
>of out mapping infomation.
>Is it possible to publish the
>mapping information on a
>intranet web site ?
>Could we export the
>description in HTML or wiki
The visual mapping views in mapper essentially have everything we
need (source, target, relationship) but there is no way to export
Subject:Re: XSL Relationship Export Author:Minollo I. Date:17 Mar 2005 08:19 PM
other than capturing the Stylus Studio window, today we don't have ways
to document mappings; but we are very interested in understanding your
requirements better so that we can come up with a useful solution in the
Are you interested in a "graphical" documentation of the XSLT-based
mapping? For example, would you like to be able to attach labels to the
various links/blocks for documentation purposes, and then have a way to
export the whole graphical mapping representation in SVG or some other
Or are you interested in general in a way to document the XSLT source code
itself? If this is the case, at what level would like the documentation? At
the template level? And then you would expect some kind of JavaDoc-like
documentation generated automatically?
>Are you interested in a "graphical" documentation of the XSLT-based
>mapping? For example, would you like to be able to attach labels to the
>various links/blocks for documentation purposes, and then have a way to
>export the whole graphical mapping representation in SVG or some other
This would be close to the perfect solution for a "stand alone" tranformation
description and would definitely satisfy the immediate requirements.
As we are essentially performing an end to end data mapping across a
number of systems we eventually would like to be able to track
data elements across a number of transformations. An output as
described above but in a database friendly format would also be a very
desirable thing. What we would do in this case is load each transformation
data file to the database so that you could then track the same
data element across all systems it touches (very desirable for obvious
system and interface maintenance reasons).
We would ideally want to be able to regenerate periodically with version
changes from the sources and reload to the database to keep the
"documentation" up to date.