Hi Mike,
You're right.
I've been following this mailing list since few years now, and IMHO I'm
currently of following opinion.
1) Publishing XSLT 4.0 and XPath 4 specs candidate recommendation (CR)s
asap. Giving community one month after that to provide feedback on CRs.
After closing those feedback items, making those specs normative CRs.
2) Following steps after having normative CRs, to progress with making
those CRs to XSL 4.0 recommendations.
Regards,
Mukul
On Thu, 13 Feb, 2025, 00:12 Michael Kay, <mike@saxonica.com> wrote:
> >
> >> Maybe, if we don't want to have much to do at any cost, then probably
> we shouldn't have joined this CG in the first place?
> >
>
>
> Let me also say that from my point of view, I have some fairly clear ideas
> about the issues I want to spend my time on. My primary focus for 4.0 is to
> make XSLT 4.0 and XQ 4.0 as effective for working with JSON as they are for
> XML. I have no objection to people raising issues that are unrelated to
> that objective - many of the ideas have been great, and some of them are
> easy to do; and if they're not, then I'm prepared to take time to explain
> why I think they need improvement. But I'm not going to put a lot of my
> time into turning other people's good ideas into specifications and tests
> cases unless I think it's a priority use of my time. I'm not going to do
> the legwork in those cases, and unless someone steps up to do it, it will
> forever remain an open issue.
>
> Michael Kay
> Saxonica
>
>
>