...has the default value of yes, as noted at http://docs.basex.org/wiki/Serialization, the XQuery Serialization does not appear to recommend/enforce a default (http://www.w3.org/TR/xslt-xquery-serialization-30/#XML_OMIT-XML-DECLARATION), but the XForms spec does (http://www.w3.org/TR/xforms11/#submit) and the recommendation in XForms spec is the default value of false (=no), which is different from the default value of yes(=true) used by BaseX.
While it (the way things are) is not a major (or minor) headache (for me), if it is a minor change and can be factored in in some future release, that would be useful (it would mean I have to set one less query param if I want the default behaviour of XForms).
Thanks.
Should've added this to the previous email: ...and it would be nice if BaseX/Jax-rx allowed true and false to be used in addition to yes and no (wherever it currently allows yes and no as the values)
---------- Forwarded message ---------- From: software developer computer.software.developer@gmail.com Date: Thu, Feb 17, 2011 at 8:27 AM Subject: jax-rx outout parameter, omit-xml-declaration key... To: basex-talk@mailman.uni-konstanz.de
...has the default value of yes, as noted at http://docs.basex.org/wiki/Serialization, the XQuery Serialization does not appear to recommend/enforce a default (http://www.w3.org/TR/xslt-xquery-serialization-30/#XML_OMIT-XML-DECLARATION), but the XForms spec does (http://www.w3.org/TR/xforms11/#submit) and the recommendation in XForms spec is the default value of false (=no), which is different from the default value of yes(=true) used by BaseX.
While it (the way things are) is not a major (or minor) headache (for me), if it is a minor change and can be factored in in some future release, that would be useful (it would mean I have to set one less query param if I want the default behaviour of XForms).
Thanks.
...has the default value of yes, as noted at http://docs.basex.org/wiki/Serialization, the XQuery Serialization does not appear to recommend/enforce a default (http://www.w3.org/TR/xslt-xquery-serialization-30/#XML_OMIT-XML-DECLARATION), but the XForms spec does (http://www.w3.org/TR/xforms11/#submit) and the recommendation in XForms spec is the default value of false (=no), which is different from the default value of yes(=true) used by BaseX.
We decided to omit the xml declaration in BaseX by default, as we observed it's the preferred choice by many users (esp. if XQuery is used to produce results other than XML nodes). An alternative default setting could be used for JAX-RX, but this would currently be the only exception in the existing framework.
...and it would be nice if BaseX/Jax-rx allowed true and false to be used in addition to yes and no (wherever it currently allows yes and no as the values)
We'll think about that (I frequently mix up the allowed values by myself; however, an extension to "true" and "false" would conflict with the specs and, thus, might break some tests).
Thanks for your suggestions, Christian
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
software developer