Re: [basex-talk] hof:until qt4cg drops?
I've sent you an e-mail in private.
The Clark notation for QNames with URIs was dropped. Instead, the Expanded
QName syntax (which is also used in XPath and XQuery) is the one that is
supported exclusively in the future:
-Q{URI}name
Andy Bunce schrieb am Sa., 3. Feb. 2024, 16:11:
> Hi Christian,
>
> > Hope this helps
>
> Sounds like a good way forward. Sign me up, please.
>
> Digression:
> I made a tiny change to the wiki recently concerning the "Q" in expanded
> QNames [1] because I thought it was required.
> On reflection, this may be because I was using v9 at the time.
>
> I now think the "Q" is required in BaseX v9, but optional in all V10+.
> Is this correct?
>
> /Andy
>
> [1]
> https://docs.basex.org/index.php?title=Command-Line_Options=146=16921=16694
>
>
>
>
> On Sat, 3 Feb 2024 at 11:15, Christian Grün
> wrote:
>
>> Hi Andy,
>>
>> Thanks for the raised finger. Indeed it’s the specification of XQuery 4
>> that takes much more time than anticipated. The process is highly dynamic,
>> with confirmed features being revised again. Some weeks ago, we have
>> stopped updating the old documentation, and we are working on a new one
>> (completely based on XQuery, with the contents and history stored in
>> databases). It will replace the old one and will be version-based, i.e.,
>> we’ll freeze the documentation of BaseX 11 (12, etc.) once it’s released
>> and maintain the documentation for the upcoming version in parallel.
>>
>> As BaseX 11 won’t be finalized until end of this month as originally
>> planned, here’s a link to the new documentation, which we’re regularly
>> updating:
>>
>> https://help.basex.org/
>>
>> The contents will stay, but the rendering is still work in progress.
>> We’ve converted the contents to a mixture of XML and contemporary Markdown
>> syntax;.editing works similar as before. I invite you (and everyone else)
>> to ask for an account to be able to help us keeping the contents up-to-date
>> and bug free.
>>
>> We know ithe current state is a bit unfortunate. For those who are
>> looking for a reliable version of the BaseX 10 documentation, we point to
>> the archived PDF version:
>>
>> https://docs.basex.org/wiki/Documentation
>>
>> Hope this helps,
>> Christian
>>
>>
>> Andy Bunce schrieb am Fr., 2. Feb. 2024, 19:25:
>>
>>>
>>> I wanted to look up the hof:until[1] syntax in the wiki. It tells me
>>> that it has been replaced with fn:iterate-while. Well, I hope, when the
>>> dust settles, there is something similar to this in the spec, but it looks
>>> like it may not be iterate-while .
>>>
>>> Today a user of the current BaseX release(10.7) is going to struggle to
>>> find what hof:until does and wont find any fn:iterate-while . I think
>>> deprecating functions and moving forward is great. I do like to see what
>>> 4.0 might bring with the BaseX 11 betas but if I catch myself writing
>>> anything substantial I stop. The ground is unstable.
>>>
>>> I think the wiki should center on the functionality of the current
>>> release, with just teasers about the future.
>>> Christian, I think you hinted that the future may hold some
>>> documentation API built into the product, or did I imagine that?
>>>
>>> /Andy
>>>
>>> [1] https://docs.basex.org/wiki/Higher-Order_Functions_Module,
>>>
>>
Re: [basex-talk] hof:until qt4cg drops?
Hi Christian, > Hope this helps Sounds like a good way forward. Sign me up, please. Digression: I made a tiny change to the wiki recently concerning the "Q" in expanded QNames [1] because I thought it was required. On reflection, this may be because I was using v9 at the time. I now think the "Q" is required in BaseX v9, but optional in all V10+. Is this correct? /Andy [1] https://docs.basex.org/index.php?title=Command-Line_Options=146=16921=16694 On Sat, 3 Feb 2024 at 11:15, Christian Grün wrote: > Hi Andy, > > Thanks for the raised finger. Indeed it’s the specification of XQuery 4 > that takes much more time than anticipated. The process is highly dynamic, > with confirmed features being revised again. Some weeks ago, we have > stopped updating the old documentation, and we are working on a new one > (completely based on XQuery, with the contents and history stored in > databases). It will replace the old one and will be version-based, i.e., > we’ll freeze the documentation of BaseX 11 (12, etc.) once it’s released > and maintain the documentation for the upcoming version in parallel. > > As BaseX 11 won’t be finalized until end of this month as originally > planned, here’s a link to the new documentation, which we’re regularly > updating: > > https://help.basex.org/ > > The contents will stay, but the rendering is still work in progress. We’ve > converted the contents to a mixture of XML and contemporary Markdown > syntax;.editing works similar as before. I invite you (and everyone else) > to ask for an account to be able to help us keeping the contents up-to-date > and bug free. > > We know ithe current state is a bit unfortunate. For those who are looking > for a reliable version of the BaseX 10 documentation, we point to the > archived PDF version: > > https://docs.basex.org/wiki/Documentation > > Hope this helps, > Christian > > > Andy Bunce schrieb am Fr., 2. Feb. 2024, 19:25: > >> >> I wanted to look up the hof:until[1] syntax in the wiki. It tells me that >> it has been replaced with fn:iterate-while. Well, I hope, when the dust >> settles, there is something similar to this in the spec, but it looks like >> it may not be iterate-while . >> >> Today a user of the current BaseX release(10.7) is going to struggle to >> find what hof:until does and wont find any fn:iterate-while . I think >> deprecating functions and moving forward is great. I do like to see what >> 4.0 might bring with the BaseX 11 betas but if I catch myself writing >> anything substantial I stop. The ground is unstable. >> >> I think the wiki should center on the functionality of the current >> release, with just teasers about the future. >> Christian, I think you hinted that the future may hold some documentation >> API built into the product, or did I imagine that? >> >> /Andy >> >> [1] https://docs.basex.org/wiki/Higher-Order_Functions_Module, >> >
Re: [basex-talk] hof:until qt4cg drops?
Hi Andy, Thanks for the raised finger. Indeed it’s the specification of XQuery 4 that takes much more time than anticipated. The process is highly dynamic, with confirmed features being revised again. Some weeks ago, we have stopped updating the old documentation, and we are working on a new one (completely based on XQuery, with the contents and history stored in databases). It will replace the old one and will be version-based, i.e., we’ll freeze the documentation of BaseX 11 (12, etc.) once it’s released and maintain the documentation for the upcoming version in parallel. As BaseX 11 won’t be finalized until end of this month as originally planned, here’s a link to the new documentation, which we’re regularly updating: https://help.basex.org/ The contents will stay, but the rendering is still work in progress. We’ve converted the contents to a mixture of XML and contemporary Markdown syntax;.editing works similar as before. I invite you (and everyone else) to ask for an account to be able to help us keeping the contents up-to-date and bug free. We know ithe current state is a bit unfortunate. For those who are looking for a reliable version of the BaseX 10 documentation, we point to the archived PDF version: https://docs.basex.org/wiki/Documentation Hope this helps, Christian Andy Bunce schrieb am Fr., 2. Feb. 2024, 19:25: > > I wanted to look up the hof:until[1] syntax in the wiki. It tells me that > it has been replaced with fn:iterate-while. Well, I hope, when the dust > settles, there is something similar to this in the spec, but it looks like > it may not be iterate-while . > > Today a user of the current BaseX release(10.7) is going to struggle to > find what hof:until does and wont find any fn:iterate-while . I think > deprecating functions and moving forward is great. I do like to see what > 4.0 might bring with the BaseX 11 betas but if I catch myself writing > anything substantial I stop. The ground is unstable. > > I think the wiki should center on the functionality of the current > release, with just teasers about the future. > Christian, I think you hinted that the future may hold some documentation > API built into the product, or did I imagine that? > > /Andy > > [1] https://docs.basex.org/wiki/Higher-Order_Functions_Module, >
