<trackbot> Date: 09 October 2013

Announcements

Steven: There is an XForms event in Amsterdam (CWI) Nov 22.

Asynchronous Javascript functions call

http://www.w3.org/community/xformsusers/2013/10/05/asynchronous-javascript-functions-call/

Alain: I was thinking about how to implement some things, and the solution I found is using an event through javascript
... it works nicely in XSLTForms
... maybe we should work out how to dispatch events from Javascript
... and include it in the spec

Erik: Clearly event dispatch is big, so it would be good to standardise. Our implementation is slightly different from XSLTform's.

Nick: We do this on mobile as well.

Steven: Does this mean that all three of you have an API for this?

Nick: Yes.

Steven: Would it be easy to merge them?

Nick: It's just a question of naming.

Erik: Which means it is hard, right? :-)

Steven: Who wants to accept responsibility.

Nick: Interested, but too busy

Steven: Let me ask you all three just to post a message with the details of your event dispatch, so that we have them documented.

ACTION-1868 - Bruchez to summarize problems with error handling and

three options for variable type handling

http://lists.w3.org/Archives/Public/public-forms/2013Oct/0007.html

http://lists.w3.org/Archives/Public/public-forms/2013Oct/0009.html

Erik: [explains Nick's comment, and how to fix it]
... I will specify that.
... 1. With xforms-action-error, we don't need xforms-script-exception and

xforms-script-language-not-supported-exception. I suggest removing these

two events. Possibly, we can add context information to xforms-action-error

to specify that the error is with a script or the script language.

scribe: do we need more specific information about what failed?

Nick: We need some context information

Erik: We need a list of reasonable errors
... I can try to find some

Nick: That would be good.
... Implementors can add more, and we can merge them later.

Erik: OK with removing the two exceptions?

[agreement]

Erik: Since the expression language is in a module, it is better to have a neutral event name for the error
... not with 'xpath' in it.

Steven: 'expression' is fine. Go for it

Erik: "3. I had said that an incorrect instance attribute on xf:submission would

dispatch xforms-submit-error, but XForms 1.1 dispatches

xforms-binding-exception. Unsure which one to pick here. Wouldn't you want

to have xforms-submit-error for any error with the submission?

"

Steven: you mean between "binding-error" or "submit-error"?

Erik: Yes

Nick: Isn't submit-error when you try to send something over the wire?

Erik: That's the next one.
... validation gives a submit-error, so not entirely
... if target-ref fails, it is a submit-error
... so I am leaning to say that for consistency, we should do the same thing for same errors
... it is easier to catch a single event for a submission than try to remember all three

Steven: It sounds like you have answered your own question :-)

Erik: It is doubtful that anyone ever used the -exceptions

Steven: I think we agree on reflection that they were a bad idea

Erik: I will specify submit-errors, if no one objects
... "4. XForms 1.1 is contradictory for xf:send/@submission:

- the action says "If this attribute is given but does not identify a

submission element, then the send action has no effect"

- xforms-binding-exception event says: "a submission attribute that

fails to point to the ID of a submission element"

- I suggest ignoring, as the action says (could also do an action error)

"

Steven: The problem with ignoring errors is that they are hard to track down

Erik: In that case I would suggest an action error

Steven: That makes me feel better

Erik: The dispatch action has a similar situation. I wonder if the spec says anything about that

<ebruchez> "If there is a null search result for the target object and the source object is an XForms action such as dispatch, send, setfocus, setindex or toggle, then the action is terminated with no effect"

Steven: So ignored
... do we then do the same thing for dispatch?

Erik: I don't know why it was designed this way
... it worries me to change it now
... I agree it would be better if actions failed, but I think I'd rather not change it now
... I'll notate this on the wiki
... I have the two events in the spec now
... nothing more to discuss.

Progress to LC

Steven: We need to set ourselves some deadlines.
... Any suggestions for how much more time we need to get to LC?

Erik: I have some actions to complete, the error handling for instance. I may or may not finish by next week. Some writing to do.

Steven: It depends on your agenda Nick.

Nick: I am quite oversubscribed already.
... Erik has something with bind
... I have dialog

Steven: I have the rewriting of the intro

Erik: I did the bind function, so I should close the action
... I need to do multipart
... simple but needs some time allocated

<nvdbleek> ACTION-1946?

<trackbot> ACTION-1946 -- Nick Van Den Bleeken to Adjust schema file to allow one result element for Function element -- due 2013-05-15 -- OPEN

<trackbot> https://www.w3.org/2005/06/tracker/xforms/actions/1946

Nick: I have some other stuff

<nvdbleek> ACTION-1937?

<trackbot> ACTION-1937 -- Nick Van Den Bleeken to Write a proposal for the xforms-action-error event instead of the current script exceptions. -- due 2013-03-13 -- OPEN

<trackbot> https://www.w3.org/2005/06/tracker/xforms/actions/1937

Steven: We can close that

Erik: I see several that I have done but not closed

<nvdbleek> ACTION-1928?

<trackbot> ACTION-1928 -- Steven Pemberton to Review intro to XForms -- due 2013-04-30 -- OPEN

<trackbot> https://www.w3.org/2005/06/tracker/xforms/actions/1928

Steven: Started but not finished

<nvdbleek> ACTION-1923?

<trackbot> ACTION-1923 -- Steven Pemberton to Add text that submission will fail if the XML can't be converted to JSON -- due 2013-02-06 -- OPEN

<trackbot> https://www.w3.org/2005/06/tracker/xforms/actions/1923

Steven: I will have to check that one

<nvdbleek> Steven did you address ACTION-1918?

<nvdbleek> ACTION-1918?

<trackbot> ACTION-1918 -- Steven Pemberton to Have a look at the vCARD example and replace it with a imaginary markup that has no XML notation -- due 2012-12-19 -- OPEN

<trackbot> https://www.w3.org/2005/06/tracker/xforms/actions/1918

Steven: Will do
... So aim for end of this month for complete text?

[concur]

[ADJOURN]

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Wee/We/
Succeeded: s/mop/mo/
Succeeded: s/\//
Succeeded: s/JD/DJ/
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Default Present: Steven, ebruchez, [IPcaller], nvdbleek
Present: Steven ebruchez [IPcaller] nvdbleek alain

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

Regrets: Philip
Agenda: http://lists.w3.org/Archives/Public/public-forms/2013Oct/0011
Found Date: 09 Oct 2013
Guessing minutes URL: http://www.w3.org/2013/10/09-forms-minutes.html
People with action items: