See also: IRC log
https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0073.html
https://lists.w3.org/Archives/Public/public-xformsusers/2016Dec/0001.html
Steven: This is the example for the spec, and to show the use case
https://lists.w3.org/Archives/Public/public-xformsusers/2016Dec/0006.html
Steven: I don't understand how this is supposed to work.
Erik: I raised it long ago
... John Boyer says that there is magic happening
... the processor has to do something special
... I need to look what we do
<scribe> ACTION: Erik to report back on how he implements multipart/related with regard to upload/anyURI [recorded in http://www.w3.org/2016/12/07-forms-minutes.html#action01]
<trackbot> Created ACTION-2096 - Report back on how he implements multipart/related with regard to upload/anyuri [on Erik Bruchez - due 2016-12-14].
evaluation of function/result@value fails
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0012.html
https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0093.html
https://lists.w3.org/Archives/Public/public-xformsusers/2016Dec/0026.html
Steven: Thank you.
https://lists.w3.org/Archives/Public/public-xformsusers/2016Dec/0020.html
Steven: Now solved
https://lists.w3.org/Archives/Public/public-xformsusers/2016Dec/0003.html
Erik: I agree that what is in refresh is the same as in initialization
Steven: So you're OK with me adding something to initialize to make them match
Alain: OK with me
https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0075.html
Steven: Maybe it is soluble by removing the word "calculate" in the first sentence quoted in the email
Erik: I'm puzzled.
... Circular dependencies can only happen via calculate.
... but not via constraint for example.
Steven: So all the spec needs is to define circular dependencies as only going via calculates.
<scribe> ACTION: Steven to rephrase circular dependency text [recorded in http://www.w3.org/2016/12/07-forms-minutes.html#action02]
<trackbot> Created ACTION-2097 - Rephrase circular dependency text [on Steven Pemberton - due 2016-12-14].
https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0071.html
Erik: If the indexref is readonly it will cause problems.
Steven: I can see use-cases where the inexref is calculated from something else
Erik: You could override readonly in that case
Steven: We still have the problem
Erik: Either we say "bad stuff wil happen" or say that something else happens if the indexref is readonly
Steven: We can say that when the system updates the index, if it can't update the indexref, it won't
Erik: That's OK
https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0089.html
Steven: Do we do it or not?
Erik: And you could have element
values that are ID type
... you can modify the ID yourself.
... we don't support it.
Steven: Shall we remove this comment
Erik: I'm fine
Steven: I will mention that this is a change in the spec, so that commentators are aware of it
<scribe> ACTION: Steven to remove ID copying comment [recorded in http://www.w3.org/2016/12/07-forms-minutes.html#action03]
<trackbot> Created ACTION-2098 - Remove id copying comment [on Steven Pemberton - due 2016-12-14].
https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0090.html
Steven: We could also demand that both insert and delete demand the index to be in bounds
Erik: You can explicitely say
what to do when it is out of bounds
... It is better to catch errors earlier
... I agree that it is worse with delete
<scribe> ACTION: Steven to change insert and delete to only work when in range [recorded in http://www.w3.org/2016/12/07-forms-minutes.html#action04]
<trackbot> Created ACTION-2099 - Change insert and delete to only work when in range [on Steven Pemberton - due 2016-12-14].
https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0056.html
Steven: I think this has been
covered in the mail and that we keep it.
... I made some adjustments to the text, but it's still
there.
https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0068.html
Steven: Skip this today; I'm not ready to discuss it
https://lists.w3.org/Archives/Public/public-xformsusers/2016Dec/0019.html
Steven: I miss this event in the processing model
Erik: What would you do?
... submission is not multi-threaded
Steven: How do deal with it now?
Erik: You get an event or callback
Steven: So you're saying that there is no use case, and it's just magic?
Erik: The response is atomic from XForms POV. There's no streaming or whatever
Steven: Fair enough
[No link]
Steven: I propose we skip the 28th and 4th.
[ADJOURN]
<scribe> ACTION: Steven to match UI initialization with refresh [recorded in http://www.w3.org/2016/12/07-forms-minutes.html#action05]
<trackbot> Created ACTION-2100 - Match ui initialization with refresh [on Steven Pemberton - due 2016-12-14].
<scribe> ACTION: Steven to update text wrt readonly indexref [recorded in http://www.w3.org/2016/12/07-forms-minutes.html#action06]
<trackbot> Created ACTION-2101 - Update text wrt readonly indexref [on Steven Pemberton - due 2016-12-14].
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Present: Alain Erik Steven Regrets: None Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Dec/0022 Found Date: 07 Dec 2016 Guessing minutes URL: http://www.w3.org/2016/12/07-forms-minutes.html People with action items: erik steven[End of scribe.perl diagnostic output]