Hi all,
with the forthcoming W3C recommendation for XSLT 2.0 and XQuery 1.0 serialization, it'd be great whether we can provide a separate implementation from the xslt processing. I think it should not be so hard and long to cut dependencies with Xalan in the org.apache.xalan.serialize package. What do you think? Should we also provide an other package name, like org.apache.xquery.serialization (xquery because the serialization may belong to the data model of xpath/xquery and xslt relies on this datamodel) ?
Thanks!
Lionel Villard
IBM Research
- Re: XSLT/XQuery serialization: toward a separate implemen... Lionel Villard
- Re: XSLT/XQuery serialization: toward a separate imp... Joseph Kesselman
- Re: XSLT/XQuery serialization: toward a separate... scott_boag
- Re: XSLT/XQuery serialization: toward a separate... Lionel Villard
- Re: XSLT/XQuery serialization: toward a separate imp... scott_boag
- Re: XSLT/XQuery serialization: toward a separate imp... david_marston
- Re: XSLT/XQuery serialization: toward a separate imp... Joseph Kesselman
- XSLT/XQuery serialization: toward a separate impleme... Brian Minchau
- Re: XSLT/XQuery serialization: toward a separate... Lionel Villard
