See also: IRC log
[No link]
Steven: Fixed it all.
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Move_Elements_Up_and_Down_in_a_List
Steven: Please review
https://lists.w3.org/Archives/Public/public-xformsusers/2016Jun/0030.html
Steven: Added the two extra
columns
... found 4 missing events
... note that submit-error isn't fatal
Erik: nor output-error
Steven: Oh! Mistake
<scribe> ACTION: Steven to mark output-error as Notification in overview table [recorded in http://www.w3.org/2016/06/29-forms-minutes.html#action01]
<trackbot> Created ACTION-2068 - Mark output-error as notification in overview table [on Steven Pemberton - due 2016-07-06].
Erik: We could go back to
*-exception
... the split was previously between errors and exceptions, and
exceptions were not cancellable.
... there is some kind of inconsistency
... "exception" is a long name.
... In Java the "error"s are more serious than the
"exceptions".
Steven: Let's think about it for
a week. Let it sink in.
... interesting that DOMActivate is a Notification, and yet
cancellable.
Erik: DOMActivate in DOM is deprecated
<ebruchez> spec for DOMActivate: https://www.w3.org/TR/DOM-Level-3-Events/#event-type-DOMActivate
Steven: HTML5 wanted to go back to "click"
<ebruchez> https://www.w3.org/TR/DOM-Level-3-Events/#event-type-click
Erik: Probably only <submit> reacts natively to a DOMActivate
Steven: Leave DOMActivate as-is?
Erik: I think that's ok
... IN HTML5 they call it a post-click activation step
... if click isn't cancelled.
... Ideally I would describe submit as working in terms of a
DOMActivatet, which if not cancelled would do the submit.
Steven: Which means that DOMActivate has a default action
Erik: We could say 'varies', even though it's only in this one case.
Steven: Let's think about it.
clash
https://lists.w3.org/Archives/Public/public-xformsusers/2016Jun/0025.html
Erik: Conflict with XPath2 and
XForms
... function is present for backwards-compatibility
https://lists.w3.org/Archives/Public/public-xformsusers/2016Jun/0027.html
Steven: What did you mean by "Some implementations allow access to non-instances"?
Erik: These are actions that
technically operate on XML 'documents'.
... in XML there is a notion of XML document
... and DOM implementations of Document node
... it's the term used commonly to describe the thing
containing nodes
... there's no reason for them to work only with instances
<ebruchez> <xf:var name="foo" value="doc('test.xml')"/>
Erik: Here I have an XML document that is not an instance
<ebruchez> <xf:delete ref="$foo//bar'/>
Erik: however you could do a delete on it. There's no reason to disallow it.
Steven: SO we use 'document' in several different ways
Erik: Maybe we need to qualify it always
Steven: Now I understand the problem better, I'll look again, and see if I can find a solution.
Erik: It's a very general term
Erik: I'll be in Europe the next
three or four weeks.
... I can be at the call next week, not sure after that.
... Not the 20th and 27th.
Steven: OK< I can make the 3rd Aug but then I will be on holiday
Alain: I won't be around two last weeks of July and two first weeks of Aug.
Steven: OK, so our last call before the summer will be 13th July, and then nothing until 31 Aug.
[ADJOURN]
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/ST/St/ Succeeded: s/dept/ept/ Succeeded: s/sob/sub/ No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Present: Steven Alain Erik Regrets: Philip Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Jun/0029 Found Date: 29 Jun 2016 Guessing minutes URL: http://www.w3.org/2016/06/29-forms-minutes.html People with action items: steven[End of scribe.perl diagnostic output]