Meeting minutes
ACTION-2295: Check that his implementation combined @instance and
@targetref correctly
https://
Erik: Pending
ACTION-2297 - Add links to glossary entry for observer
https://
Steven: So I did this, please check that you're OK with the wording.
ACTION-2296: Add text to make it clear where xforms-action-error is
dispatched to.
https://
Erik: The question is, is there anything we can meaningfully do?
… don't we say that the event may not be handlanle?
Steven: I think we say it for submit replace="all"
… for submit-error
Erik: It is in <load/> as well.
… are there any meaning cases where it is possible at all?
Alain: XSLTForms fires resource-error
… so it is similar to how submission works.
Steven: Which is what this is about. You don't need <load/> really, since you could use submit with replace="all".
Erik: You could take the long route, but often it is easiest to just replace the browser's location
Erik: It would make sense to fix the target of the error, and dispatch it in the same way as action-error.
… later we could make it an action-error and dispatch both and deprecate load-error
Steven: The simplests is to leave load error as is, except where it is dispatched to.
All: OK
Sorting
https://
Steven: What do you do for sorting?
Erik: We may have two
<ebruchez_> https://
Erik: there was a function in exforms
… and I think we have another
<ebruchez_> https://
Erik: it is different
… the sort keys used to be a string, and we made it a path...
… but that may not be correct from xpath semantics
… the key should really be a function
… but we can't support that
<ebruchez_> https://
Erik: xpath 3 has sort function
… and the key is a function
Alain: There is no sort function. Easy to add
Erik: It is clearly very useful
Steven: Thanks. I'll study the options.
<Steven> s/TH?Th/
AOB
[None]
[ADJOURN]