Subject: Reporting requirement for XSL From: Francis Norton <francis@xxxxxxxxxxx> Date: Thu, 17 Feb 2000 05:33:35 +0000 |
OK, nobody has challenged the scope of the requirement, and there does seem to be real interest. First, I have stuck the original requirement onto a web-site at http://redrice.com/xml/xslReporting.html Now, I'd be interested in answers to the following questions: [1] should (can?) we use pure XSLT, or should it be XSLT with java extensions? [2] would it be useful or sensible to go for a text or XHTML output before implementing XSL FOs? [3] what is the best way of organising this? I can do basic transformations but someone else would be needed for FO input, and I'm also wondering whether we should go off-list - this doesn't seem to have generated massive buzz. [4] May I also request some advice on implementation architecture - for instance how to fit the data to a reporting library. Francis. RSuiter@xxxxxxxxx wrote: > ... > I cast one more vote for hearing more about this. My own future > requirements > on this are slightly less complex than your problem description, > but I know I'm going to have to go there sooner or later. > > Sorry for the late post. > > Rick Suiter > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Printing XML + XSLT (2nd try), RSuiter | Thread | Re: Printing XML + XSLT (2nd try), Jeff Hamilton |
Re: Storing XSL Documents In Databa, Steve Muench | Date | DocBook...., SeJo |
Month |