See also: IRC log
<trackbot> Date: 03 December 2014
<pfennell> The UK Government will be using XForms for the Department for Communities and Local Government (DCLG).
Steven: As I was just saying to
Philip, I am chairing a meeting in London hosted by the UK
Cabinet Office
... (a part of govt). The UK govt has decided to use ODF
instead of MS Office
... and I am chairing that meeting (and talking about
XForms)
... I won't be back in time for the call.
http://plugfest.opendocumentformat.org/2014-london/
scribe: Good news all round.
section 3.2 the instance element
http://lists.w3.org/Archives/Public/public-forms/2014Dec/0000.html
(Nick's not here, so there are a number of items we can't handle today)
Erik: [walks through the email]
Steven: So you copy namespace nodes to the root of the instance for contained elements and attributes that have ns bindings, but NOT for namespaces in content?
Erik: Right
Steven: So if we adopted the backward-incompatible way, the only forms that would potential break would be those with namespace prefixes in content.
<ebruchez> Steven it seems the others can still hear me
Erik: Yes, namespaces in content, or for people who needed the namespaces to be in scope.
Steven: Example?
Erik: An instance that inherits a namespace node, that the form ends up using by creating nodes that use them...
Alain: another possibility is when the forms are automatically created.
Steven: Do we have a preference
for backwards-compatibility/incompatibility?
... since the incompatible one is the one that is likely to
occur more often.
Erik: It is a broader
compatibility issue, as raised by Nick.
... We can control that with @version
... I think that the default being the new behaviour is the
better choice
Alain: I prefer the incompatibility route
Philip: Agree
Steven: I can live with that
Erik: I think that's OK
Steven: It means old forms have
to have a textual change if they are affected, but there aren't
many of those
... and let them be more explicit about the namespaces being
used by copying them to the root element of the instance
RESOLUTION: Adopt the "Backwards incompatible" version of namespace usage in instances
<scribe> ACTION: Erik to write text for new instance namespaces processing [recorded in http://www.w3.org/2014/12/03-forms-minutes.html#action01]
<trackbot> Created ACTION-1990 - Write text for new instance namespaces processing [on Erik Bruchez - due 2014-12-10].
https://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#Container_Form_Controls
Steven: Alain sent a message
http://lists.w3.org/Archives/Public/public-forms/2014Dec/0002.html
... A good point.
Erik: Isn't the goal of caseref and indexref to control the behaviour via an instance?
Alain: toggle would not be possible with casevalue
Erik: I see.
... that could work.
Steven: So casevalue would calculate to a string which would select one of the IDs?
Alain: Yes.
Steven: Replacing caseref?
Alain: No because of toggle.
Erik: We already allow ref attributes to point to atomic values.
<ebruchez> @caseref="...compute the selected case..."
Erik: there is nothing that would
prevent us from having a caseref that returns a string.
... so we might not need another attribute
Alain: But then we could deprecate output/@value
Steven: I'd like longer to
consider the ramifications; OK we put it off to next
call?
... I had a couple of comments
... case has label as content, so it should have a label as
attribute as well.
http://www.w3.org/TR/xforms/#ui-switch-module
Erik: I'm not sure what we do with that label...
Steven: case does not have help hint or alert on the other hand. It is not a control.
Erik: It is not unreasonable that
Case have a label (or even help and hint)
... it should either have none or all of them.
Steven: We need to decide, and while we are about it, dialog has the similar problem.
Erik: Dialog should have them all.
Steven: dialog is much more clearly a control than case is
Erik: Exactly.
<scribe> ACTION: Steven to add help hint alert elements to dialog [recorded in http://www.w3.org/2014/12/03-forms-minutes.html#action02]
<trackbot> Created ACTION-1991 - Add help hint alert elements to dialog [on Steven Pemberton - due 2014-12-10].
Steven: Back to
<case>
... do we think of it as a control?
... So you think it is valid that it has a label
Alain: Agree
Steven: So we should add them all?
Alain: Right
<scribe> ACTION: Steven to add help hint alert elements, and attributes to <case> [recorded in http://www.w3.org/2014/12/03-forms-minutes.html#action03]
<trackbot> Created ACTION-1992 - Add help hint alert elements, and attributes to <case> [on Steven Pemberton - due 2014-12-10].
Steven: I moved itemset and copy
as agreed last week. All other comments from me are
editorial.
... I propose we discuss section 10 at the call in two weeks
time.
[None]
Next call in two weeks
[ADJOURN]
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Steven Anyone else hear him?// Succeeded: s/Erik/Alain/ Succeeded: s/ST/St/ Succeeded: s/xx/x/ Succeeded: s/same/similar/ Succeeded: s/N/N]/ Succeeded: s/Net week/Next week/ No ScribeNick specified. Guessing ScribeNick: Steven Inferring Scribes: Steven Default Present: Steven, pfennell, [IPcaller], ebruchez Present: Steven pfennell [IPcaller] ebruchez Regrets: Nick Agenda: http://lists.w3.org/Archives/Public/public-forms/2014Dec/0001 Found Date: 03 Dec 2014 Guessing minutes URL: http://www.w3.org/2014/12/03-forms-minutes.html People with action items: erik steven[End of scribe.perl diagnostic output]