Meeting minutes
Sorting spec text
https://
Steven: Posted today, take a couple of minutes to have a look
Erik: About nesting of binds
Steven: We allow the same with constraint, so I've just used the same mechanism for sort
Erik: Seems OK, I don't remember why I had an issue before with the context
Erik: Why do you add the note to insert?
Steven: Because the effect will be different inserting into a sorted nodeset
… should we make it a requirement that it is inserted in the right place
RESOLUTION: Make it a requirement that a node gets inserted in the right position in a sorted nodeset
Alain: What about types for @sort?
… does it sort according to the type?
Steven: I use "less than" and "greater than". Would you like it to be more specific.
Erik: What happens if you have a malformed value, or empty. What do you do in that case?
Steven: If you filter on less-than, then it should work like that.
Erik: XPath 2 has this concept, and it is a dynamic error
Steven: items[. > preceding-sibling::*]
Erik: In our implementation where if the node is empty or not an integer when it should be, then we have a dynamic error
… The evaluation will stop in our case
https://
Error Handling
If an error occurs in an XPath function, then an xforms-expression-error EventXF, xforms-binding-error EventXF, or xforms-action-error EventXF is dispatched.
Steven: So it looks like if a comparison is wrong, then we get an expression-error
Erik: So the sort will be interrupted
Steven: No different from a @calculate though?
… "f the evaluation fails, the value content is set to the empty string."
Erik: We could mention what happens, "the sort is not completed or performed"
Steven: So if any of the comparisons fail, the sort stops
ACTION: Steven to add error conditions for sort
Next meeting
Next week
AOB
[None]
Steven: 3 days to ixml symposium submission deadline
[ADJOURN]