W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > April 2007

XSLT non-XML output (was: standard components edits)

From: Innovimax SARL <innovimax@gmail.com>
Date: Tue, 17 Apr 2007 10:55:25 +0200
Message-ID: <546c6c1c0704170155y5f7aa8e5q8d6322dbe5272a59@mail.gmail.com>
To: "Jeni Tennison" <jeni@jenitennison.com>
Cc: public-xml-processing-model-wg@w3.org

Hi Jeni,

On 4/17/07, Jeni Tennison <jeni@jenitennison.com> wrote:
> Hi Mohamed,
> > Ok so the output of an XSLT transformation of type text or html should
> > be outputted to a parameter, is it ?
> IMO, the result of an XSLT transformation is always a (sequence of)
> documents (node trees). It's only when they're serialised (a separate
> step, with no output) that you might get a text or HTML document.

That's interesting ! And I share part of your concern

But are we going to tell to people that already have crafted their
foo2csv or foo2html xslt stylesheet, that if they want to put it into
XProc, they won't be able to do that ?

I'm not telling I want all and everything in XProc because people
would ask it, but if we want  XProc to ignit fast, we have to take at
least care of one transformation : XSLT !!

So, lots of people won't see any added value, if they need to rebuild
their stylesheet (even personnaly, I'm pleased to refactor my
stylesheet, but I want to be able to use XProc before needing to do

Am I the only to feel something is missing here ?

Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 8 72 475787
Fax : +33 1 4356 1746
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Tuesday, 17 April 2007 08:55:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:42 UTC