- From: Christian Grün <cg@basex.org>
- Date: Tue, 27 Feb 2024 17:36:12 +0000
- To: "public-xslt-40@w3.org" <public-xslt-40@w3.org>
If there’s time next week, it would be great if we could tidy up a little: 1. CURRENT DRAFTS: We should look at the features that have already been added to the spec, but have not officially been confirmed by the group. Two issues I get in mind are: https://github.com/qt4cg/qtspecs/issues/283 https://github.com/qt4cg/qtspecs/issues/397 I guess there are various other pending features (such as fn:slice), but I’m not sure if we are aware of all of them? Or should we simply regard the current state of the draft as „officially accepted“? 2. CURRENT TESTS: It would be very helpful if we could get the test suite into a cleaner state. It contains numerous test cases that deviate from the current state of the specification (examples: fn:parts, fn:xdm-to-json, fn:parse-uri/fn:build-uri, …). Chances are currently high to get completely lost while trying to catch up. I’m not sure what’s the best way to achieve this. Maybe we should drop everything that has no counterpart in the spec, and re-add it just in case (by taking advantage from the git history)? Looking forward to everyone’s suggestions. Thanks all, Christian
Received on Tuesday, 27 February 2024 17:36:19 UTC