<trackbot> Date: 20 February 2013

<scribe> scribe: nvdbleek

ACTION-1931: Propose text for @accept on upload

http://lists.w3.org/Archives/Public/public-forms/2013Feb/0025.html

alain: It is not a problem for me that it is called accept, I even prefer it

nvdbleek: I think we can keep it in the spec
... On the previous call everybody aggreed, and now we have an extra implementer that agrees so we can make a resolution

RESOLUTION: We will change the medatype attribute on upload to accept

<scribe> ACTION: nvdbleek to update the XML and relax-ng schema (change mediatype to accept on upload) [recorded in http://www.w3.org/2013/02/20-forms-minutes.html#action01]

<trackbot> Created ACTION-1934 - Update the XML and relax-ng schema (change mediatype to accept on upload) [on Nick Van Den Bleeken - due 2013-02-27].

The function Element

http://lists.w3.org/Archives/Public/public-forms/2013Jan/0028.html

ebruchez: i've been back and forth on this
... We need this for XPath 1.0 and 2.0 but in XPath 3.0 you can assign functions to a variable but not named functions
... If we would have XPath 3.0+ or XQuery then the function element wasn't needed

<ebruchez> let foo := function0() { …. }

nvdbleek: I think we need it because you can't define named functions in Xpath 3.0 and we don't support to add variables in the model, so you can't refer to the function variables globally

ebruchez: Does Better Forms support adding functions in the form

nvdbleek: They only support adding custom function in java

ebruchez: What about XSLTForms does it supports adding function in javascript

alain: yes

nvdbleek: Are we going to do anything about it

ebruchez: Functions are needed, and XSLT did it already, but now wondering about it because XPath has now native functions
... we can go one way or the other. The feature is not looking forward...

nvdbleek: In Xpath 3.0 you don't have custom named functions

ebruchez: It is a bit strange that they aren't in XPath but are in XQuery
... You want XQuery and XQuery update facility in XForms
... It would be ideal that XForms could say that XForms 2.0 supports XQuery 3.0

nvdbleek: I think that XQuery 3.0 support is currently only feasible for server side implementations

ebruchez: If we support the function element, we want to support variables? because Xpath 3.0 is introducing variables

nvdbleek: I think we should support variables in functions because we only explicitly support XPath 1.0 and 2.0 and you want to use variables to simplify XPath expressions

ebruchez: If prefer a simplified syntax so you don't need elements as children (without variable support)

nvdbleek: So you don't need variables
... do you want to drop variable support, or do you want to different syntaxes

<ebruchez> <function>$i + $j</function>

nvdbleek: What if we support <function>$n <var name="foo" value=".."/> $foo<function>
... typically you won't simply return $foo but do a calculation on it

the result will be the sequence ($n, $foo) in this example

<ebruchez> http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_function_Element

<function> <seq value="$f"/><seq value="$g"/></function>

<function> <seq value="($f, $g)"/></function>

<function> ($f, $g)</function>

<ebruchez> <function><var>$f</function>

<ebruchez> <function><var><seq></function>

<ebruchez> <function><var><result/><function>

nvdbleek: The last sytax looks fine for me, and also support only text content if you don't need variables
... in Xpath 3.0 you don't have to use the var element because they have let

<scribe> ACTION: Erik to send an e-mail proposing a lighter syntax for the function element [recorded in http://www.w3.org/2013/02/20-forms-minutes.html#action02]

<trackbot> Created ACTION-1935 - Send an e-mail proposing a lighter syntax for the function element [on Erik Bruchez - due 2013-02-27].

nvdbleek: if we are only allowing to define functions using XPath do we need the script element

ebruchez: I don't think we need

nvdbleek: As it is written I think you can also use it as an action, and that is already implemented by a lot of implementations

<ebruchez> <action type="xpath">

ebruchez: We can put javascript and xpath expressions in the script element
... We realised that we can use the action element, because it is just switching the language from xforms, to xpath or javascript

nvdbleek: Is it used to call functions with side efects

ebruchez: Yes

<ebruchez> <xf:action type="xpath">

<ebruchez> controlOps:setControlHelp($local/control-name, $local/help),

<ebruchez> controlOps:setControlAlert($local/control-name, $local/alert)

<ebruchez> </xf:action>

ebruchez: The above sample is calling native java functions

<ebruchez> https://gist.github.com/ebruchez/4996935

ebruchez: I don't know if Xpath is a good language for this
... XQuery would be possibly better to be used as a script language
... It is using XPath as scripting language

<ebruchez> http://www.w3.org/TR/xquery-sx-10/

ebruchez: Don't know if they are going to finish XQuery Scripting Extension

trackbot, end meeting

This is scribe.perl Revision: 1.137  of Date: 2012/09/20 20:19:01  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Philip/Phillip/
Succeeded: s/function/function0/
Succeeded: s/It is calling native java functions/The above sample is calling native java functions/
Found Scribe: nvdbleek
Inferring ScribeNick: nvdbleek
Default Present: ebruchez, nvdbleek, [IPcaller]
Present: ebruchez nvdbleek [IPcaller]

WARNING: Replacing previous Regrets list. (Old list: Steven, uli)
Use 'Regrets+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Regrets+ +Phillip

Regrets: +Phillip
Agenda: http://lists.w3.org/Archives/Public/public-forms/2013Feb/0027.html
Found Date: 20 Feb 2013
Guessing minutes URL: http://www.w3.org/2013/02/20-forms-minutes.html
People with action items: erik nvdbleek

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.