Questions around <http:response/>

[ChristianGruen]

Hi Adam, I noticed that the schema of the <http:response/> element is different to the one proposed in the EXPath HTTP specification:

http://www.expath.org/spec/http-client#d2e491

For example, the message attribute name is called reason in the XMLPrague proposal for RESTXQ. Next, there is no <http:body/> element. Instead, all results are returned as additional items.. which is of course reasonable if we plan to also return non-textual data.

[adamretter]

Hi Christian, terribly sorry. For some reason I completely missed this. Is it still something you need an answer on?

[ChristianGruen]

Hi Adam, I stumbled upon this issue, because @dizzzz changed a little example in our documentation (http://docs.basex.org/index.php?title=RESTXQ&action=historysubmit&diff=13833&oldid=13809 …hi Dannes!).

In the specifications…

• http://expath.org/spec/http-client#d2e491
• http://exquery.github.io/exquery/exquery-restxq-specification/restxq-1.0-specification.html#response-format

…the response attribute is called message, so maybe we should change this back from reason to message?

The current version of the BaseX RESTXQ implementation provides support for both attributes.

[ChristianGruen]

Hi Dannes, hi Adam, do you have any opinion on this? Thanks in advance!

[dizzzz]

I have no strong opinion here, as long it works cross-vendor :)
IMO we need to follow the spec, and if eXist deviates here, we have a bug and need to fix it.

in eXist-db: For compatibility i’d Like to support both attributes..... at least for some time. But the code will be a bit ugly :-)

[dizzzz]

suggested fix in PR #35

[ChristianGruen]

Thanks for your feedback, Dannes!

[dizzzz]

We have to undo the wiki change :)

[ChristianGruen]

Just done ;)