W3C home > Mailing lists > Public > public-forms@w3.org > November 2012

Re: Concerns about format token parameter on serialize() and parse() functions

From: Steven Pemberton <Steven.Pemberton@cwi.nl>
Date: Wed, 28 Nov 2012 18:27:40 +0100
To: "Public Forms" <public-forms@w3.org>, "Nick Van den Bleeken" <Nick.Van.den.Bleeken@inventivegroup.com>
Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Message-ID: <op.wohur7ohsmjzpq@steven-ux21a>
We discussed this at the call today.

Simple example of the use of the serialize function:

	<bind ref="text1" calculate="xf:serialize(../node)"/>

More advanced uses:

	<bind ref="text2" calculate="xf:serialize(../node, json)"/>
	<bind ref="text3" calculate="xf:serialize(../node, xml validate  
relevant)"/>

The point here is to mirror the parts of the <submission/> element that  
are needed to serialize a value.

However, Nick's worry is that a simple list of format tokens as in the  
second and third examples is not future-proof should there ever be  
non-boolean parameters.

The idea that arose in the call was just to use a <submission/> element to  
supply the paramers, since we already have that mechanism, and authors  
will already know it:

	<submission id="fmt1" serialization="application/json"/>
	<submission id="fmt2" serialization="application/xml" version="1.1"  
separator=";" validate="true"/>
...
	<bind ref="text1" calculate="xf:serialize(../node)"/>
	<bind ref="text2" calculate="xf:serialize(../node, fmt1)"/>
	<bind ref="text3" calculate="xf:serialize(../node, fmt2)"/>

Comments?

Steven

On Wed, 21 Nov 2012 09:54:03 +0100, Nick Van den Bleeken  
<Nick.Van.den.Bleeken@inventivegroup.com> wrote:

> All,
>
> I'm a bit concerned about the format parameter on serialize() [1] and  
> parse()[2] functions, because I think that the format token only allows  
> boolean properties. And on the submission element and xslt output  
> options you have properties that take other type of values. For example  
> version, cdata-section-elements and includenamespaceprefixes.
>
> We could decide that the serialize() and parse() functions are only for  
> the simple things and that we will depend on the serialise()[3],  
> parse-xml()[4], parse-xml-fragment()[5] functions in 'XPath and XQuery  
> Functions and Operators 3.0' for the more advanced stuff.
>
> What is your opinion about this?
>
> 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
>
>
> 1:  
> http://www.w3.org/MarkUp/Forms/wiki/XPath_Expressions_Module#The_serialize.28.29_Function
> 2:  
> http://www.w3.org/MarkUp/Forms/wiki/XPath_Expressions_Module#The_parse.28.29_Function
> 3: http://www.w3.org/TR/xpath-functions-30/#func-serialize
> 4: http://www.w3.org/TR/xpath-functions-30/#func-parse-xml
> 5: http://www.w3.org/TR/xpath-functions-30/#func-parse-xml-fragment
>
> ________________________________
>
> Inventive Designers' Email Disclaimer:
> http://www.inventivedesigners.com/email-disclaimer
Received on Wednesday, 28 November 2012 17:35:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:58 UTC