OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Note from XSL WG on Extension Concerns

[ Lists Home | Date Index | Thread Index ]
  • From: Eric van der Vlist <vdv@dyomedea.com>
  • To: xml-dev@xml.org
  • Date: Fri, 07 Apr 2000 14:55:38 +0200


I'd like to second Leigh's voice about the standardization of the Java
API which is the second most important blocker (after the "pure" XLST
extensions themselves) for the portability of XLST based applications
but also to plead the case of SAX like interfaces as implemented by XT.

In fact, the best solution would be to allow the 3 levels of
representation of a node set or result tree fragment (string, SAX events
and DOM), each of them having its set of usage.

The SAX level is very convenient to use for mapping java objects to and
from node sets and I think we should definitely keep it as an option.

The other thing I'd like to add is that these interfaces should be
defined on a consistent way for the 3 "places" where you can us them in
a XSLT transformation :

  - As an input for a XML or XSLT document.
  - As parameters (call & return) for java methods.
  - As an output to implement output methods.

My 0,02 Euros.

Eric van der Vlist       Dyomedea                    http://dyomedea.com
creator                  http://xmlfr.org            http://ducotede.com
editor                   http://xmlhack.com              http://dmoz.org

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS