XForms Users Community Group Teleconference -- 13 Feb 2019

Report back from XML Prague

http://www.xmlprague.cz/

Steven: XForms demo won the demo prize. I got asked to do an XForms tutorial at MarkupUK; there will be a Dutch event in October with XForms parts.

ACTION-2215: Implement collapse="open/closed"

https://lists.w3.org/Archives/Public/public-xformsusers/2019Feb/0008

Steven: Done.
... I'm not 100% happy yet; need to think a bit more. Please take a look.

Erik: When you say "activate toggles between the two states".
... does that mean you can send a DOMActivate

Steven: Yes; activate is always done with a click, and that is always the same as a DOMActivate event

Erik: OK

ACTION-2216: Review part 2 of

https://www.w3.org/2019/01/16-forms-minutes#item03

https://lists.w3.org/Archives/Public/public-xformsusers/2019Feb/0000.html

[which is a sub-part of ACTION-2211: Redefine terms via xdm instead of xpath[1, 2]]

Steven: Thanks for your review. I replied with a proposed new text: https://lists.w3.org/Archives/Public/public-xformsusers/2019Feb/0001.html

Erik: Probably good enough
... XPath can query for typed value; the data() function returns a typed value
... atomization does the same
... I think we can keep the examples

<scribe> ACTION: Steven to update the typed values text

<trackbot> Created ACTION-2223 - Update the typed values text [on Steven Pemberton - due 2019-02-20].

Result of evaluation error for calculate MIP

https://lists.w3.org/Archives/Public/public-xformsusers/2019Feb/0002

Steven: Can we make this expression language independent?

Erik: Good question
... we use "empty sequence" in many places

Steven: Oh...
... maybe we should solve this at a higher level...

Erik: The idea is to clear the node in the calculate case
... we could fix this case with the empty string.

<scribe> ACTION: Steven to summarise the use of "empty sequence"

<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

Result of evaluation error for boolean MIPs

https://lists.w3.org/Archives/Public/public-xformsusers/2019Feb/0003

13.4.1 Error Recovery Outside Actions

https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Error_Recovery_Outside_Actions

6.2 Typed Values

https://www.w3.org/community/xformsusers/wiki/XForms_2.0#Typed_Values

Erik: Section 13.4.1 contradicts 6.2
... In our implementation we pick the opposite of the default
... readonly, required, nonrelevant if the expression fails.

Steven: I like that
... let's adopt.

<scribe> ACTION: Steven to implement evaluation error for MIP as opposite of the default value.

<trackbot> Created ACTION-2225 - Implement evaluation error for mip as opposite of the default value. [on Steven Pemberton - due 2019-02-20].

Suggested update for `replace="text"`

https://lists.w3.org/Archives/Public/public-xformsusers/2019Feb/0004

Steven: I replied saying that we should do it not only for JSON, but for all types we accept

Erik: Yes, of course.

<scribe> ACTION: Steven to update replace="text"

<trackbot> Created ACTION-2226 - Update replace="text" [on Steven Pemberton - due 2019-02-20].

ACTION-2217: Spec up file/read and write (and provide links)

https://lists.w3.org/Archives/Public/public-xformsusers/2019Jan/0031

Steven: In progress

dispatch@targetid default

https://lists.w3.org/Archives/Public/public-xformsusers/2019Feb/0006

Steven: All I am asking for is a default of the parent element for targetid

Erik: I had some reservations, although we have a special notation in our implementation
... I'm not entirely against it.
... it makes sense
... I can live with it.

<scribe> ACTION: Steven to implement targetid default

<trackbot> Created ACTION-2227 - Implement targetid default [on Steven Pemberton - due 2019-02-20].

AOB

[None]

[ADJOURN]

- DRAFT -

XForms Users Community Group Teleconference

13 Feb 2019

Attendees

Contents