Summertime

[Reminder: next week back to regular time in Europe]

Dynamic dependencies

https://lists.w3.org/Archives/Public/public-xformsusers/2017Mar/0012.html

Erik: I don't know if it helps. It might help to have an example of where a rebuild is necessry

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

Steven: We could either include an actual example, or just warn of the situations where it might arise.

Erik: It was too long before, now it is too short.
... I could add an example.

Steven: That would be great

<scribe> ACTION: Erik to supply an example for why a <rebuild/> would be needed [recorded in http://www.w3.org/2017/03/22-forms-minutes.html#action01]

<trackbot> Created ACTION-2113 - Supply an example for why a <rebuild/> would be needed [on Erik Bruchez - due 2017-03-29].

ACTION-2049 - Look into making soap non-normative, and use as a

usage example with <header> instead

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

https://lists.w3.org/Archives/Public/public-xformsusers/2017Mar/0016.html

Steven: I studied this section
... I can find no part that can't be done with vanilla XForms

Erik: The current definition adds the SOAPAction header

Steven: Do you do that?

Erik: Yes.

Steven: The point is that you can do this very simply with standard XForms; the header element is there for it.
... the only win in making it a normative part is that you don't have to add the one header.

Erik: It ensures little things, like the charset parameter
... it's not doing nothing.
... We could deprecate it. But we lose backwards compatibility.
... I don't feel strongly about it.
... You can still achieve the same effect.

Alain: It's implemented in XSLTForms.

Steven: So you're suggesting leaving as is?

Erik: We could deprecate it.
... I'm not sure how used it is.

Steven: Funnily enough, I'm writing a SOAP app in XForms now: most wireless routers contain a SOAP server.

PROPSAL: Deprecate, and point out that it will still be possible with existing facilities of XForms.

Erik: OK

Alain: OK

<scribe> ACTION: Steven to deprecate SOAP processing in the processor [recorded in http://www.w3.org/2017/03/22-forms-minutes.html#action02]

<trackbot> Created ACTION-2114 - Deprecate soap processing in the processor [on Steven Pemberton - due 2017-03-29].

Serialization as multipart/related

https://lists.w3.org/Archives/Public/public-xformsusers/2017Feb/0022.html

Steven: Do we have anything to say on this yet?

[Silence]

Erik: I know you don't like the magic in this

Steven: I don't like that you don't have any control.

Erik: A <part/> element could be the solution
... it made sense originally to tie it to <upload/>
... but that is clearly limited
... you don't know how the submission knows about the things.
... Clearly the full mechanism would give you control.
... but I don't know if we can fix the current system.
... it relies on 'secret' information that some parts have been populated from a certain control.
... and that may change dynamically during the workings of the form
... the implementor has to keep some information around, like a MIP
... we have custom MIPs in our implementation

Steven: OK, let's think about it more...

AOB

[None]

[ADJOURN]

RESOLUTION: Deprecate SOAP as a built-in

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/\Erik/Erik/
Succeeded: s/uu/u/
Succeeded: s/gives/would give/
Present: Alain Erik Steven
Regrets: Philip
No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven
Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2017Mar/0014
Found Date: 22 Mar 2017
Guessing minutes URL: http://www.w3.org/2017/03/22-forms-minutes.html
People with action items: erik steven