RE: stylesheets for stylesheets (was Re: Swapping table rows and columns)

Subject: RE: stylesheets for stylesheets (was Re: Swapping table rows and columns)
From: "Vun Kannon, David" <dvunkannon@xxxxxxxx>
Date: Wed, 7 Jul 1999 09:29:17 -0400
	There is a UML DTD coming from the OMG, called XMI. Here at KPMG, we
start from the UML, transition the representation to XML and then turn the
stylesheets loose on that. A somewhat fluffy piece talking about our work
was recently published by my colleague in Information Week -
David vun Kannon
Manager, Financial Services Consulting

-----Original Message-----
From: Oren Ben-Kiki [mailto:oren@xxxxxxxxxxxxx]
Sent: Wednesday, July 07, 1999 7:59 AM
To: xsl-list@xxxxxxxxxxxxxxxx
Subject: Re: stylesheets for stylesheets (was Re: Swapping table rows
and columns)

James Tauber <jtauber@xxxxxxxxxxx> wrote:

>I've been thinking about XSL-based literate programming on and off
>for the last year or so. At various times I've considered writing FOP in
>and having a stylesheet produce Java source from that XML.

I've also toyed with similar ideas. What I really like is the ability to
generate multiple documentation views from the same source file(s),
something which current LP systems don't do well (if at all). For example it
would be very interesting to be able to generate UML models (assuming a UML

>There was a mailing list xml-litprog-l[1] that unfortunately seems to have
>gone into hibernation.

>Perhaps not surprisingly, Robin Cover has collected material on the topic


Thanks for the references. I just spent some time going through them, and it
seems that the literate programming people are well aware of XML and its
advantages for them. I'm going to keep an eye on this... I have used noweb
for everything in the previous company I worked in - we even wrote a backend
for generating HTML and for allowing incremental tangling/weaving of large
projects. I miss it sorely today - using JavaDoc just isn't the same.

>I'm not aware of any effort to use XSL for literate programming, although,
>as Ken has pointed out, he has used DSSSL.

The documents in [2] refer to XSLT but seem to underestimate its role
(prehaps due to its state at the time). It might prove possible to implement
a literate programming system using just XSLT, or maybe using just a few
extensions (e.g. using something like SAXON).

Have fun,

    Oren Ben-Kiki

 XSL-List info and archive:
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         

 XSL-List info and archive:

Current Thread