XForms Users Community Group Teleconference -- 30 Nov 2016

It's not letting me in.

ANyone else already in?

<ebruchez> The Connect to Audio button is garyed out for me

<alain1> For me too...

damn

Let me try something else

just a moment

<ebruchez> calling in it says the access code is not coirrect

For me too

liam?

I can't join the meeting until the host joins, but I AM the host...

<ebruchez> how does WebEx know you are the host?

Usually there is a button to claim the host role

but I'm using the mobile app, and it doesn't have that button

before today I could just phone in

<ebruchez> I see a Reclaim Host Role menu in the desktop app

<ebruchez> it requires a Host key

it's 192124

<ebruchez> ok if I claim that it seems I can join the audio

Great. I'll try diallin in again

Still not valid.

Anyone else in?

<ebruchez> Phlip

<ebruchez> Philip is in

Rewrite

https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0054

Steven: Please take a look, and send comments as necessary.

ACTION-2076: Propose text for what value is used when the

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

Erik: It's simple, because in XPath errors propagate
... I've treated both var and function results.

Steven: So in other words, we don 't produce a value, we just give an error

Erik: Yes
... We're doing the same as XPath basically
... Another problem
... what happens if the syntax of the function signature is

incorrect.

Erik: I am suggesting we do something similar to how we treat missing functions in the @functions attribute on model
... I'll add the error paragraph for @value, and I'll suggest text for the signature

<message/>

https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0106.html

Steven: Are we ok with @value on message?

[general agreement]

JSON: characters below \u0020

https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0112.html

Steven: Which would you prefer?

Erik: Be specific

<scribe> ACTION: Steven to tighten description of equivalent XML charactors for JSON serialisation [recorded in http://www.w3.org/2016/11/30-forms-minutes.html#action01]

<trackbot> Created ACTION-2092 - Tighten description of equivalent xml charactors for json serialisation [on Steven Pemberton - due 2016-12-07].

The constraint Property

https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0111

Erik: So where would you like to see the error?
... we can't set an alert on a repeat.
... so we set the constraint on the wish element
... so it shows up on the input for the wish
... but it wouldn't show up with minimum number of wishes
... I guess there's a bigger story.
... you could provide a 'dummy' control

Steven: Do we do alert on output?

Erik: WE do!
... let's check the spec
... yes output inludes help hint and alert

<scribe> ACTION: Steven to update constrain note, and change it to an example. [recorded in http://www.w3.org/2016/11/30-forms-minutes.html#action02]

<trackbot> Created ACTION-2093 - Update constrain note, and change it to an example. [on Steven Pemberton - due 2016-12-07].

Focus on container controls

https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0047.html

Erik: Focus can be tricky.
... but I think what you suggest is fine
... there is a recursive aspect

Alain: Looks OK for me.
... I'm not sure what we do now, but it's OK

xforms-next/previous

https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0073.html

Steven: In other words xforms-next would work in a similar way to setfocus

Erik: We don't implement this event

Steven: It would typically be bound to the tab key

Erik: THere's no example in the spec, I don't see the use case.

<scribe> ACTION: Produce example for xforms-next [recorded in http://www.w3.org/2016/11/30-forms-minutes.html#action03]

<trackbot> Error finding 'Produce'. You can review and register nicknames at <https://www.w3.org/2005/06/tracker/xforms/users>.

<scribe> ACTION: Steven to Produce example for xforms-next [recorded in http://www.w3.org/2016/11/30-forms-minutes.html#action04]

<trackbot> Created ACTION-2094 - Produce example for xforms-next [on Steven Pemberton - due 2016-12-07].

Erik: My problem is not why you need a nav order, just when would you use this event.

Steven: I'll try and produce some use cases

The xforms-rebuild Event

https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0057.html

Steven: I think that "Any child bind elements are recursively processed as described in the

three points of this list."

is redundant

scribe: since the inner bind is already covered by the rules

<ebruchez> https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0061.html

https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0070.html

Steven: If you think it's fine as it is, then we leave it as is.

Alain: I agree with Erik

Steven: FIne, I was wrong.

xforms-refresh

https://lists.w3.org/Archives/Public/public-xformsusers/2016Nov/0067.html

Steven: It seems wasteful. I don;t know why we require this

Erik: We don't do it.

Alain: I don't know what we do

Steven: How about "events that change MUST be sent, others MAY be sent"

Erik: I think we should be explicit about what may and may not be sent
... if the control should change state it should be dispatched only in that case,

Alain: I'd agree with that.

Philip: Me too

<scribe> ACTION: Steven to tighten definition of which events get sent on value changed [recorded in http://www.w3.org/2016/11/30-forms-minutes.html#action05]

<trackbot> Created ACTION-2095 - Tighten definition of which events get sent on value changed [on Steven Pemberton - due 2016-12-07].

Erik: What happens when the control becomes relevant?

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

[ADJOURN]

- DRAFT -

XForms Users Community Group Teleconference

30 Nov 2016

Attendees

Contents