Joe Wicentowski

@wsalesky Remove the `serialize` function and declare the output method in the prolog: ```xquery xquery version "3.1"; declare namespace output="http://www.w3.org/2010/xslt-xquery-serialization"; declare option output:method "text"; let $prefix := "@prefix rdf: ....

Still a problem, for sure, is the double escaping of CDATA blocks saved (PUT) to eXist over REST, WebDAV, and XML-RPC: https://github.com/eXist-db/exist/issues/2081#issuecomment-409664770. Still a mystery to me!

Got it - makes sense! Somehow I never paid attention to `fn:idref()` - probably saw it but never understood its possible applications. In TEI, we often point to elements by...

Also, will `@xml:id` automatically be recognized as an ID for use with `fn:id()` as before, or should people now use **both** an ID on `@xml:id` (for `fn:id()` lookups) **and** a...

Sounds great! Thanks so much.

In the 2018-05-07 call, @duncdrum noted: > Disable Legacy Range Index: might still be too soon, sad but true. We should wait for functional updates to indexing to get back...

@adamretter You asked about the status of this issue in Slack. In https://github.com/eXist-db/exist/issues/581#issuecomment-91004571, @wolfgangmm wrote: > There are still some functions which could not be ported to the new range...

Could one workaround be to allow the use of `fn:matches` to be served by the Lucene-based range index in cases when `$pattern` is explicitly anchored (i.e., starts with `^` and...

@wolfgangmm In last week's community call you said you would check to make sure that xml:id attributes were being automatically indexed; once we're sure this is so, if @adamretter can...

@wolfgangmm By chance, have you been able to check whether `@xml:id` attributes are being automatically indexed now in eXist 5? The last time we discussed removing the legacy range index,...