I'm not convinced that retrofitting 4.0 features into an essentially 2.0 processor is the best way to progress toward 4.0. I'd need to look at the spec to see whether, as in 3.0, some basic changes to the data model and processing were introduced. As your experience playing with a 3.0 subset has shown, that isn't always simple, or even possible, without breaking 2.0 semantics.
Would working from the Xalan codebase, with its legacy warts, really be easier than building a new processor based on what we learned in Xalan? I don't currently have a strong opinion. Do we really have the resources to tackle this? If we still had the kind of man-hours that built Xalan originally I'd say it was worth trying to lead the pack again, but... -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Mukul Gandhi <muk...@apache.org> Sent: Wednesday, March 13, 2024 12:58:14 PM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: xsl 4.0 draft specs, and xalan implementation Hi all, As we know, we've done little implementation work within XalanJ's xslt 3.0 dev branch. These days, there's an XSL 4.0 specs development work going on, within QT4 community group (ref, https://qt4cg.org/). These days, within the XSL 4.0 set of QT4 specs, specs related to XSLT 4.0 and related languages are getting specified. At the bottom of page https://qt4cg.org/, links to latest drafts of XSLT 4.0 and related specs are available. Can we, create an codebase dev branch on XalanJ dev repos for XSLT 4.0 implementation work, and try to implement few useful features from latest drafts of the XSLT 4.0 and related specs? Any thoughts please? -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
