See also: IRC log
https://lists.w3.org/Archives/Public/public-xformsusers/2017Jun/0038
https://lists.w3.org/Archives/Public/public-xformsusers/2017Jun/0040
Steven: We agreed to adopt this,
but we didn't agree on names.
... We have two types now, ascii email and international.
Erik: We should keep 'email' as the name for the ascii one (backwards compatibility)
Steven: iemal?
... iemail?
... any better suggestions?
... I'll use iemail for now.
<scribe> ACTION: Steven to add the two email types to the spec [recorded in http://www.w3.org/2017/09/06-forms-minutes.html#action01]
<trackbot> Created ACTION-2134 - Add the two email types to the spec [on Steven Pemberton - due 2017-09-13].
https://lists.w3.org/Archives/Public/public-xformsusers/2017Jun/0041
Steven: in progress; done by next week.
https://lists.w3.org/Archives/Public/public-xformsusers/2017Jul/0000
Steven: This is about all actions
that have an ID attribute.
... Currently if the ID fails to identify anything, the action
does nothing.
https://lists.w3.org/Archives/Public/public-xformsusers/2017Jul/0025.html
Steven: Backwards compatibility problems?
Erik: In a group of actions, if one fails, the rest don't get run I think
<ebruchez> https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_xforms-action-error_Event
Erik: xforms-action-error is a
fatal error
... Do we care?
Steven: I can live with the change
RESOLUTION: All actions that have an ID attribute that fails to identify a suitable element will dispatch an action-error.
<scribe> ACTION: Steven to implement resolution making actions dispatch an action-error for id attributes [recorded in http://www.w3.org/2017/09/06-forms-minutes.html#action02]
<trackbot> Created ACTION-2135 - Implement resolution making actions dispatch an action-error for id attributes [on Steven Pemberton - due 2017-09-13].
https://lists.w3.org/Archives/Public/public-xformsusers/2017Jun/0042
Steven: It occurred to me that we could use mode="echo"
Erik: I'm not opposed to
something else than the URL.
... Mode is a bit funny though
Steven: It's not completely unreasonable; it is a sort of mode of sending.
Erik: In a series of actions, synchronous or not could have an effect on how it works.
Steven: On you implementation where you use resource="echo:", does @mode have any effect?
Erik: Good question; I would have to check.
Steven: Let's think on.
<ebruchez> mode="synchronous echo"
Erik: You could use tokens.
Steven: That could work.
https://lists.w3.org/Archives/Public/public-xformsusers/2017Jun/0032
Steven: This is still pending.
https://lists.w3.org/Archives/Public/public-xformsusers/2017Mar/0012
[Awaiting an example]
Steven: Waiting for an example from you Erik.
Erik: Ack.
https://lists.w3.org/Archives/Public/public-xformsusers/2017Jun/0014
Steven: Are we interested in
going ahead with this?
... It seems to have support on the list.
Erik: We don't implement this, though we do something similar, linking alerts to the individual constraints.
<scribe> ACTION: Steven spec up alert MIP for further discussion. [recorded in http://www.w3.org/2017/09/06-forms-minutes.html#action03]
<trackbot> Created ACTION-2136 - Spec up alert mip for further discussion. [on Steven Pemberton - due 2017-09-13].
[None]
[ADJOURN]
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/TH/Th/ Present: Alain Erik Philip Steven No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2017Sep/0001 Found Date: 06 Sep 2017 Guessing minutes URL: http://www.w3.org/2017/09/06-forms-minutes.html People with action items: steven[End of scribe.perl diagnostic output]