- From: Reece Dunn <msclrhd@googlemail.com>
- Date: Sat, 20 May 2023 07:36:56 +0100
- To: Dimitre Novatchev <dnovatchev@gmail.com>
- Cc: public-xslt-40@w3.org
- Message-ID: <CAGdtn26++srLk3kzZ3hTATPWBdonfoLLZYFdXmmDb5qmar_t7w@mail.gmail.com>
Hi Dimitre, This -- along with a few other features -- were incorporated into the spec before the standards group was formed. There have been issues added to track these so that they can be reviewed and voted on, like how the records and thin arrow operator have been. It may be useful to have a label to identify these features in the issue list, and to make sure that we continue to review these through the WG. Kind regards, Reece On Fri, 19 May 2023 at 22:04, Dimitre Novatchev <dnovatchev@gmail.com> wrote: > > And in section "2.2.1 Static Context" there is this text: > > "*Note:* > > Item type aliases can be defined in XQuery 4.0 and in XSLT 4.0, but not in > XPath 4.0 itself." > > I clearly remember that we had a heated and unfinished argument whether or > not defining type aliases can be done in XPath and that we didn't arrive at > conclusion, so we accepted that we will see a demonstration how type > aliases can be defined once in XPath and accessed and reused from multiple > XPath expressions. > > Here is an action from one of the minutes (apr. 11): > > * [ ] QT4CG-029-07: NW to open the next discussion of #397 with a > demo from DN > > And the issue for type aliases is with Open status. > > I don't remember us ever voting to include type aliases with this text in > the XPath Spec, because I would clearly remember voting against this. > > Please, let us follow our standard procedures. > > Thanks, > > Dimitre > >
Received on Saturday, 20 May 2023 06:37:12 UTC