XForms Users Community Group Teleconference -- 11 Sep 2019

Erik: We need to say what happens because of the merging of text nodes due to the data model.
... it can happen in insert, replace and delete
... What does it mean to refer us to the newly inserted nodes?
... I'm not sure what the answer is.
... You can imagine an implementation just caring about the result.
... So in my email, I suggest three possibilities.

Steven: Tricky
... what are the use cases?

Erik: The event is for detecting that there has been a mutation.

Steven: Yes I use that for marking that the instance data has been changed and needs saving.

Erik: You might want to synchronise two instances.
... and in that case you would want to know what has been changed.

Steven: So which solution would support that best?

Erik: That would exclude solution 1.

Steven: Solution 2 might not let you distinguish between something that had been merged, and something that had been inserted.
... that may mean we use solution 3, and supply the inserted things, without referring to the result.

Erik: We might be able to supply even more information so that you know the result of merges.
... the first step would be to say that text nodes that been inserted and merged are not included in the context information

Steven: Can I give you an action item to suggest some text?

Erik: Sure

<scribe> ACTION: Erik to propose text for the merged textnodes case of insert and replace.

<trackbot> Created ACTION-2264 - Propose text for the merged textnodes case of insert and replace. [on Erik Bruchez - due 2019-09-18].

ACTION-2259: Propose text for mips on controls [Steven]

https://lists.w3.org/Archives/Public/public-xformsusers/2019Jun/0014

Steven: In progress

XForms and Web sockets

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

Steven: I read it. I found that there was not enough information about the <ws/> element
... it does look very similar to <submit/>
... And the name ws is badly chosen because it refers to the implementation and not the purpose.
... but there is clearly a use case.
... I wish I knew how our Danish colleagues did their IRC application using XForms, because clearly they could do this stuff already, apparently without a websocket interface.
... What I'll do is contact them to see if they can remember how they did, and maybe even get the source.
... Any other comments.

Erik: I didn't get a chance to read it yet.

Philip: Nor did I.

Steven: I'll add it to next week's discussion again.

<scribe> ACTION: Steven to contact the Danes about IRC

<trackbot> Created ACTION-2265 - Contact the danes about irc [on Steven Pemberton - due 2019-09-18].

AOB

[None]

[ADJOURN]

- DRAFT -

XForms Users Community Group Teleconference

11 Sep 2019

Attendees

Contents

ACTION-2254: Revise <replace/>

ACTION-2260: Change inserted-items to inserted-nodes in

Patterns for data mutations

ACTION-2262: Make insert/delete/replace text consistent with

ACTION-2263: Update dom text for readonly

ACTION-2261: Clarify what to do with merged text nodes in

ACTION-2259: Propose text for mips on controls [Steven]

XForms and Web sockets

AOB

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output