W3C

- DRAFT -

XForms Users Community Group Teleconference

12 Oct 2016

Agenda

See also: IRC log

Attendees

Present
Steven, Alain, Erik, Philip
Regrets
Chair
Steven
Scribe
Steven

Contents


https://www.kadaster.nl/web/english/About-Kadaster.htm

Advance warning, call with be at 14:00 in Europe on 2 Nov

http://www.timeanddate.com/worldclock/fixedtime.html?msg=XForms+Call&iso=20161102T09&p1=43&ah=1

Steven: Only one week this year.
... one hour earlier in Europe

Section 9

https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0009.html

Steven: I'm assuming Section 9 is now done.

@value

https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0010.html

Steven: Surprising amount of work. Many differences are just difference in text, which I can put right. But I still have questions.
... Deprecate submission/header/name, submission/header/value?
... I realise now that you can generate several headers with one name using several values.
... So that is reason enough to keep header/value

Erik: Header/name /value look like item/name /value
... I have no strong feelings about deprecating

Steven: Fine. I thought it was worth mentioning.
... What happens if the evaluation of @value that has type ANY fails?

Erik: Hmm, good question
... for bindings we fall back, and dispatch an error
... for actions we have xforms-action-error
... we don't want actions to silently fail
... one solution would be to dispatch an event
... maybe we already do this already at a general level

<ebruchez> 10.5.2 Error Recovery Inside Actions

"Any error taking place during action processing stops the outermost action handler. Errors include:

expression errors

binding errors with the bind or model attribute

binding errors with complex or readonly content

missing mandatory attributes or unsupported attribute values on action elements

The xforms-action-error event is dispatched to the observer of the action. Observers include: controls and the model, instance, and submission elements.

Note:

Some actions silently ignore error conditions and are not subject to the processing above, including:

setvalue pointing to the empty sequence or to an atomic item (such as a string) instead of a node

delete with the empty sequence or an empty overridden context

insert with an empty or non-element insert context, an empty overridden context, or an empty origin

actions with AVTs evaluating to the empty sequence

dispatch, send, setfocus, setindex, and toggle when the target element is not found"

https://www.w3.org/community/xformsusers/wiki/index.php?title=XForms_2.0#Error_Recovery_Inside_Actions

Steven: So that covers action/param, and dispatch/property. What about function/result

?

Erik: ... Right now it is implementation dependent for when the function elements are processed.
... there can be preprocessing, that spots errors, or a dynamic error

Steven: There are lots of places where preprocessing could occur already, and we don't say what to do in those cases.
... We say that a string @value returns the empty string if evaluation fails
... what should we say for other types?

Erik: There is no good default value

Steven: Then just say "it is undefined"?

<scribe> ACTION: Erik to propose text for what value is used when the evaluation of function/result@value fails [recorded in http://www.w3.org/2016/10/12-forms-minutes.html#action01]

<trackbot> Created ACTION-2076 - Propose text for what value is used when the evaluation of function/result@value fails [on Erik Bruchez - due 2016-10-19].

Steven: I think we can make @value a Common attribute
... along these lines:

Generalise more?:

* Returns a string or any type as specified

* Evaluated in in-scope context, unless there is a binding, and then it

uses that context.

* If the element can have PCDATA content, then @value overrides it

* If evaluation fails, for strings the empty string is used; for ANY ???

(decision)

Steven: Then I can put the description of @value in one central place, and all the places where it is used, they use that Common attribute

Erik: Fine to do that.
... I would prefer it if section 10.5.2 supercedes "returning the empty string".

Steven: That's fine.

AOB

[None]

[ADJOURN]

Summary of Action Items

[NEW] ACTION: Erik to propose text for what value is used when the evaluation of function/result@value fails [recorded in http://www.w3.org/2016/10/12-forms-minutes.html#action01]
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2016/10/12 13:51:50 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/param/result/
Succeeded: s/I propose that we use the same processing as bind errors//
Succeeded: s/Finer/Fine/
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Present: Steven Alain Erik Philip
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0011
Found Date: 12 Oct 2016
Guessing minutes URL: http://www.w3.org/2016/10/12-forms-minutes.html
People with action items: erik

[End of scribe.perl diagnostic output]