Hi Scott,
   Its really nice to see your reply. Please see my comments to your
points, below

On Mon, May 28, 2018 at 9:20 PM, Scott Boag <[email protected]> wrote:
>
>
> > xslt20 & xslt20-compiled
> >
> > Any thoughts, what is the functionality currently contained in above
> folders?
>
> I think those were *very* early attempts to do XSLT 2.0 on Xalan?  Would
> be interesting to get dates on these.
>

At this link, http://svn.apache.org/viewvc/xalan/java/branches/ its
mentioned these folders had previous edits 14 yrs ago.


> > Is there any possibility of IBM donating in some way its XSLT 2.0
> processor technology to Xalan? If it can be done, people will flock to the
> IBM derived Xalan's XSLT 2.0 processor.
>
> I think it could be a possibility.  Not sure it's wise or not... have to
> think about it a bit. But let me discuss with some folks in IBM to explore
> the options.
>

Thanks. IBM donated its XML Parsing & API technology earlier to apache
(Xerces. The Java one I guess). I feel, same could be done with XSLT 2.0.
It would be just great, and beneficial both to community and of course IBM.

> Can we use Saxon's latest home edition XSLT 2.0 processor (its open
> source), and convert to to Xalan's XSLT 2.0 processor?
>
> Hmm, seems on the surface to be a non-starter to me, just given it does
> not feel right.
>

I quite agree with you.


> I was writing some XSLT the other day, and was reminded what a cool and
> interesting language it is
>

I agree.


> despite it's somewhat tarnished reputation.
>

To my opinion, XSLT is a great language in a particular niche (i.e XML
transformation). Its not a general purpose language, but yet its Turing
complete I believe.


> To justify the work for a new processor, really there should be a core
> idea that makes it potentially unique and valuable, above the current state
> of the art.
>

I guess, if you could jump into new XSLT development (2.0 & 3.0) at Xalan,
we'll gain a lot from your leadership.


> For myself, I'd love to see a 3.0 processor implemented in Typescript for
> client use
>

Targeting Xalan to have XSLT 3.0 instead of 2.0 is a good idea. I'm not
much aware of Typescript, so can't comment on that. I guess, implementing
Xalan's XSLT 3.0 in Java would be just great.



> Still, given the ability to do JSON transformations, and mix
> XML/JSON/XHTML, and throwing in the ability to do XQuery 3.0, it could be
> really exciting, from a functional viewpoint.
>

I agree.



-- 
Regards,
Mukul Gandhi

Reply via email to