This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Reporting requirement for XSL
- To: xsl-list at mulberrytech dot com
- Subject: Reporting requirement for XSL
- From: Francis Norton <francis at redrice dot com>
- Date: Thu, 17 Feb 2000 05:33:35 +0000
- References: <OFBBE66A2F.7B81392C-ON86256886.0081E402@cccis.com>
- Reply-To: xsl-list at mulberrytech dot com
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@cccis.com 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