Meeting minutes
ACTION-2315: Report on event handling in web components (Erik)
https://
Erik: Continues
ACTION-2322: Summarise the submit/done/error response-body issues
(Erik)
https://
Erik: Going back to xforms-submit-ready event
… as an alternative to using an echo:... scheme
… the submission does a lot of work normally, so depending on what's coming back, it may convert to xml,
… and storing the result in an instance somewhere
… so simulating an echo is a lot of work
… not a show stopper in itself.
Steven: Aren't we only interested in what we send?
Erik: It depends on what you are trying to do.
Steven: so going back to: https://
Steven: So I see we have three options. 1) an echo: scheme and not registered
… 2) scheme and registered, which is work
… 3) submit-ready
Alain: I think that submit-ready gives us the functionality we want and so much more.
Steven: /\ Can you live with submit-ready Erik?
Erik: Sure
<trackbot> Error finding 'To'. You can review and register nicknames at <https://
ACTION: Alain to write spec text for xforms-submit-ready
<trackbot> Created ACTION-2323 - Write spec text for xforms-submit-ready [on Alain Couthures - due 2022-05-20].
ACTION-2321: Propose text for a <cancel/> action (Steven)
https://
Steven: It was pretty easy.
Erik: Sounds simple
Alain: OK
ACTION: Steven to put cancel action in spec
<trackbot> Created ACTION-2324 - Put cancel action in spec [on Steven Pemberton - due 2022-05-20].
ACTION-2313: Research the alternatives for 'dirty' data, and produce
code in all of them for comparison (Steven)
https://
(Was: Detecting/Ignoring unsaved data
https://
Steven: Continues
AOB
Steven: Both my submissions got accepted for XML Prague
Steven: Declarative.amsterdam is beginning of November, hybrid
… call for papers next week.
Steven: My talk at CHI included XForms, and was positively received.
Steven: No call next week
[ADJOURN]
s;Steven: /\; Steven: ;
<Steven> s/Steven: .\/Steven: /
<Steven> s/Steven: \/.\\/Steven: /
<Steven> s/Steven: \/\\/Steven: /