XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » XSL Relationship Export
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Error in Stylus Studio - canno... (2)
-> + Saxon Assign (2)
-> - License Authentication Failed (1)
-> + Stylus Studio 2007 Download (2)
-> + EDI to XML validation (2)
-> + Reports: can't remove "undead"... (3)
-> + Document Wizard Incomplete (6)
-> + Opening xml converter (4)
-> + Node depth limit with MySQL? (5)
-> + Basics (2)
-> - Node depth limit with MySQL? (1)
-> + Creating an XML Schema from a ... (4)
-> - Issue with XSD (1)
-> + XSL-FO and Apache FOP (2)
-> + How Come Stylus Studio Fails T... (6)
-> + no suitable driver (8)
-> + 211,19: no declaration found f... (6)
-> - Validate HEX (1)
-> + Crashing when connected to dat... (3)
-> - Interface with quickbooks (1)
-> - CDATA control (1)
-> + [resolved] Namespace (and pref... (5)
-> - Hiding and Revealing Child Nod... (1)
-> + Cannot see values in Watch whe... (4)
-> - Help with CSV to XML and Regio... (1)
-> + How do I verify "opt=yes" URI ... (4)
-> - Stylus Studio claims xsd is in... (1)
-> + Can a generated XSD be used in... (4)
-> + I am not a developer I'm just ... (2)
-> + Stylus crash when deleting dat... (6)
-> - Preserving Structure (1)
-> - Preserving Structure (1)
-> - HL7 ORU group tags (1)
-> + Fixed Length Record Layout to ... (2)
-> + WebService Connect (6)
-> - WebService conection problems (1)
-> + Could not detect EDI dialect a... (3)
-> + I am a bookkeeper not a progra... (2)
-> + fatal error (4)
-> - Saxon linebreak (1)
-> + task scheduler (2)
-> - Number of Elements in Grid vie... (1)
-> + Compile Java (2)
-> + What happened to the EDI Wizar... (15)
-> + setting Transformer for java b... (3)
-> + XML Schema Documentation Gener... (3)
-> + EANCOM xsd-files (4)
-> + Failure of CDATA converting pr... (4)
-> + XML File created from text fil... (3)
-> + After purchase AND activation ... (2)
-> + XQuery Format of XML code snip... (4)
-> + Error during conversion (9)
-> - testing for empty nodes (1)
-> + edi converter - java fails (10)
-> + ddtek:serialize (3)
-> - File explorer view (1)
-> - Java Extension Functions (1)
-> + err:FODC0004 (18)
-> - Removing Attributes when Null (1)
-> + CDATA preservation (6)
-> + Help converting xml report to ... (2)
-> + Converting text to XML issue (3)
-> - example not working (1)
-> + XML Editing (2)
-> + Multiple EDI messages within s... (5)
-> + Mapping RDBMS and XML Schema t... (2)
-> + MySQL Database importing (2)
-> + XSD validation using XSV fails... (3)
-> + Is this really well-formed? (3)
-> + HL7 EDI to XML problems -'ORU_... (11)
-> + How do I modify the Xquery to ... (2)
-> + XML mapping difficulty (3)
-> + XLST Conversion (2)
-> + HTML TO XSL Conversion (2)
-> - Convert an EBCDIC file to XML (1)
-> + License Manager still indicate... (4)
-> + Still sometimes getting beat b... (2)
-> + What versions of MySQL are sup... (5)
-> - External XSLT processor proble... (1)
-> + DDEE0082 Erro Internal system ... (6)
-> + Calling function from .NET C# (2)
-> + Stylus studio projects bound t... (3)
-> + Report Designer mistakenly gen... (3)
-> + Choose Nodes in pipelines (3)
-> + Custom external processor and ... (2)
-> + predefined (4)
-> + translate function in java (2)
-> + XMLPipeline trouble in Linux (7)
-> + Converting Custom EDI Message ... (2)
-> + tab delimetered file with vari... (2)
-> + XML validation with XSD (2)
-> + Missing documentation: SSL_Cer... (2)
-> + Parse Xcel input file which is... (2)
-> + XML Publisher post processors (2)
-> + Alignment of table items in XM... (2)
-> + XML to PDF using XML Publisher (2)
-> + Blurry Background image / Vect... (4)
-> + URIResolver error on command l... (2)
-> + stylus studio - the (3)
-> + problem with omit from output ... (3)
-- Previous [481-500] [501-520] [521-540] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Michael ShephardSubject: XSL Relationship Export
Author: Michael Shephard
Date: 17 Mar 2005 07:38 PM
Hi,
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
purposes.

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
>text ?

The visual mapping views in mapper essentially have everything we
need (source, target, relationship) but there is no way to export
this view...

Any ideas welcome.

Thanks for your help.
Michael
Postnext
Minollo I.Subject: Re: XSL Relationship Export
Author: Minollo I.
Date: 17 Mar 2005 08:19 PM
Michael,
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
near future.

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
exportable format?

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?

Thanks for your feedback,
Minollo
Posttop
Michael ShephardSubject: Re: XSL Relationship Export
Author: Michael Shephard
Date: 17 Mar 2005 08:59 PM
Hi Minollo,
thanks for you prompt reply.

>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
>exportable format?

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.

Michael
   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.