Adam Retter

So yes it does allow some complexity... if you want it. But you don't have to use these new bits! For most people's use-cases the defaults are sane enough to...

@ChristianGruen Let me first make some small corrections to your examples. It's better I do so in a separate comment rather than editing yours, so that we can see the...

So to clarify, my approach was two pronged: 1) allow the user flexibility but only if and when they want it 2) not force (the majority?) of users to have...

To address some of @ChristianGruen's [comments](https://github.com/expath/expath-cg/pull/125#issuecomment-430608433): > To summarize my feeling: I am not sure if we really need all the flexibility, and if we don’t lose our users here?...

Awesome :-)

@ChristianGruen Welcome back! I am also back (but on actual Holiday - but working). So AFAIK the main thing for me to do is look at the Response processing stuff...

So just a note to myself that when I implement, I will likely use the Apache HTTP Client. When doing so, I need to use the Asynchronous Client to workaround...

I also interpret the EXPath Binary spec to mean that the result should be 18 446 744 073 709 551 615. I note that BaseX (8.6.7) returns `-1`. In Java...

Hmm... So you are proposing to add the [XSLT and XQuery Serialization 3.1](https://www.w3.org/TR/xslt-xquery-serialization-31/#json-output) to the `$options` as a `serialization` option as opposed to adding another arity function signature? If so...

I think we could just have a `serialization` option in `$options` that takes the same as `fn:serialize`. We should not reproduce XSER 3.1 in our spec or list all the...