W3C home > Mailing lists > Public > public-xformsusers@w3.org > June 2013

Re: ACTION-1947 - Import the XPath 3.0 serialize() function to XForms 2.0

From: Erik Bruchez <erik@bruchez.org>
Date: Wed, 5 Jun 2013 00:37:24 -0700
Message-ID: <CAAc0PEXh4mwJMs9yNPsj+gDV9AQygKa8B8=0s6u6uJwqa=zQ9g@mail.gmail.com>
To: "<public-forms@w3.org>" <public-forms@w3.org>
Cc: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>, "public-xformsusers@w3.org" <public-xformsusers@w3.org>
All,

I have implemented the changes discussed during the last call. Here
are the diffs:

http://www.w3.org/MarkUp/Forms/wiki/index.php?title=XForms_2.0&diff=3802&oldid=3799

http://www.w3.org/MarkUp/Forms/wiki/index.php?title=XPath_Expressions_Module&diff=3804&oldid=3800

-Erik

On Wed, May 29, 2013 at 6:21 AM, Nick Van den Bleeken
<Nick.Van.den.Bleeken@inventivegroup.com> wrote:
>
> Overall this looks good. But I have the following comments:
>
> * Shouldn't the default value for xforms:relevant be true (currently specified value is false)
> * How can you validate non relevant nodes? I would expect that non-relevant nodes are considered valid when doing validation on serialisation.
> * What is the default value of the xforms:validate serialisation parameter
> * Could we rephrase 'When <code>true</code>, nodes marked as invalid in the input sequence are checked (after pruning if pruning is enabled with <code>xforms:relevant</code>). If there is any invalid node, the function raises a dynamic error. No revalidation takes place during this process.'
>       *Proposal*: When <code>true</code>, the function raises a dynamic error if there are any nodes marked as invalid in the input sequence (after pruning if pruning is enabled with <code>xforms:relevant</code>). No revalidation takes place during this process.
>
> Kind regards,
>
> Nick Van den Bleeken
> R&D Manager
>
> Phone: +32 3 425 41 02
> Office fax: +32 3 821 01 71
> nick.van.den.bleeken@inventivegroup.com
> www.inventivedesigners.com
>
>
>
> On 29 May 2013, at 03:31, Erik Bruchez <erik@bruchez.org> wrote:
>
> All,
>
> As per this action item, I imported the function into XForms. I did so:
>
> - by referring to the external specifications
> - and using XSLT and XQuery Serialization 3.0's ability to add
> submission methods and parameters to specify behavior which is
> specific to XForms.
>
> Here is the diff:
>
> http://www.w3.org/MarkUp/Forms/wiki/index.php?title=XPath_Expressions_Module&diff=3800&oldid=3750
>
> This means some changes compared with the previous text, including:
>
> - the function signatures have changed
> - the way to specify parameters (including the serialization method) has changed
>
> I have a few open questions/comments:
>
> - Most standard boolean serialization parameters are "yes" and "no".
> Should we use that too, or "true" and "false"? Or accept both?
> - There are 2 editorial notes related to linking.
> - I chose to raise a dynamic error if JSON serialization fails. It can
> fail, right?
> - Is it unexpected to users that, by default, non-relevant nodes are
> pruned? This is consistent with xforms:submission
> - I made xxforms:validate throw a dynamic error. It seems better than
> returning a blank string.
>
> Comments welcome.
>
> -Erik
>
>
>
>
>
> ________________________________
>
> Inventive Designers' Email Disclaimer:
> http://www.inventivedesigners.com/email-disclaimer
Received on Wednesday, 5 June 2013 07:38:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:48:24 UTC