W3C

- DRAFT -

XForms

18 Feb 2015

Agenda

See also: IRC log

Attendees

Present
Steven, Alain, Erik
Regrets
Nick, Philip
Chair
Steven
Scribe
Steven

Contents


13: 59 Joining chat room…

Started talking in forms on Wednesday 18/02/15 13:59:07

Started talking in forms on Wednesday 18/02/15 13:59:07

Room topic is: Code is 26631 (CONF1)\

14: 03 -> Zakim has joined forms

Steven zakim, room for 5 at 1400Z?

Zakim ok, Steven; conference Team_(forms)14:00Z scheduled with code 26631 (CONF1) at 14:00Z for 60 minutes until 1500Z

14: 37 -> alain has joined forms

15: 00 -> ebruchez has joined forms
... 01 Zakim Team_(forms)14:00Z has now started

Zakim +ebruchez

15: 02 Zakim +??P11

Steven zakim, I am ?

Zakim +Steven; got it

Zakim +[IPcaller]

alain Zakim, I am [IPcaller]

Zakim ok, alain, I now associate you with [IPcaller]

15: 03 Steven Chair: Steven

Steven Regrets: Philip, Nick

15: 04 Steven Agenda: http://lists.w3.org/Archives/Public/public-forms/2015Feb/0013.html

Steven Topic: Finish off Section 11

Steven http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#XForms_Actions

Zakim +Dimitris

Zakim -Dimitris

15: 05 Steven Steven: I have one more comment in section 11

Steven http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_dispatch_Element

15: 06 Steven "If a run-time element is destroyed, then any delayed events targeted at that element are removed from the delayed event queue. A run-time element may be destroyed for a number of reasons, including shutdown of the form or removal of form controls associated by a repeat with an instance data node that is destroyed."
... 07 Steven Erik: dipatch requires identifying a target

Steven s/dip/disp/

15: 08 Steven Steven: Do we refer to "run-time elements being destroyed" anywhere else?

Steven Erik: 9.4.1

ebruchez "A repeat object is an implicitly generated group element that contains the set of run-time objects generated to represent the repeat template content for a single repeat item of the repeat collection. These run-time objects are form controls, XForms actions and other host language elements that correspond to markup content in the repeat template. If an item of the repeat collection is non-relevant, then the rendering approach used to

signify non-relev[CUT]

ebruchez applied to the user interface controls of the associated repeat object."

15: 09 Steven Steven: All "run-time objects".

Steven Erik: In the repeat section it talks about repeat objects.

15: 10 Steven Steven: What is the intention of this section?

Steven Erik: You can't dispatch to an element that doesn't exist.

15: 11 Steven ... like in a repeat
... 12 Steven Steven: An event is dispatched to the current item in a repeat.
... 13 Steven Erik: The one at the time the action is run, not when it is actually dispatched after a delay.

Steven ... so something might have changed

Steven Steven: In fact there may be no element at all when it comes to be dispatched.

Steven Erik: Yes.

Steven Steven: So you're happy with this wording?

15: 14 Steven Erik: You could change "element" to "object"

Steven Steven: I'm OK if you are with it.

15: 15 Steven Steven: Any more comments on 11?

Steven Erik: I still have to review section 11.

Steven Steven: So there may still be some to come.

Steven Topic: Section 12

Steven http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#Conformance

15: 16 Steven Alain: It only mentions XPath 1.0

Steven Steven: That was one of my comments too.

15: 18 Steven Steven: With a "Model processor" do we need to mention JSON as external format?
... 19 Steven Erik: We don't want to make many features options, right?

Steven Steven: Right.

Steven ... so a must a MUST or a SHOULD

15: 20 Steven Erik: Submission is a SHOULD

Steven Steven: I was surprised by that on reflection

15: 21 Steven ... ODF is a model processor, because it has a different UI module
... 22 Steven Erik: Does it have submission?

Steven Steven: [looks] Yes, it does.

15: 23 Steven Steven: So should we make JSON a MUST.
... 24 Steven Erik: Yes.

Steven Alain: Agree.

Steven ACTION: Steven to add JSON to specification of Model Processor

trackbot is creating a new ACTION.

trackbot Created ACTION-2011 - Add json to specification of model processor [on Steven Pemberton - due 2015-02-25].

Steven Steven: And make submission a MUST as well?

Steven Erik: Right.

15: 25 Steven ACTION: Steven to make submission a MUST in Model Processor

trackbot is creating a new ACTION.

trackbot Created ACTION-2012 - Make submission a must in model processor [on Steven Pemberton - due 2015-02-25].

Steven Erik: And we have a SHOULD for <group> in full. I don't see why.

Steven Steven: I'm in favour of making that a must.

Steven Erik: Agree.

Steven Alain: Me too

15: 26 Steven Erik: Same for toggle and switch

Steven Steven: Agree

15: 27 Steven Alain: Agree

Steven ACTION: Steven to make toggle, switch a MUST

trackbot is creating a new ACTION.

trackbot Created ACTION-2013 - Make toggle, switch a must [on Steven Pemberton - due 2015-02-25].

15: 28 Steven Steven: It says only SHOULD for https.... do we agree?
... 29 Steven Erik: We changed the examples to use https... if anything there is more.

Steven Steven: It's sending the wrong message in a way.

15: 30 Steven Erik: You could imagine very restrictive examples where https is not needed,

Steven ... but for "full" I think we should require it.

15: 31 Steven Erik: It is ahrd to implement file: scheme

Steven s/ahrd/hard/

Steven Alain: We partially implement it, but the user has to allow it via a dialog

Steven ... but it is useful.

15: 32 Steven Erik: Webapps don't normally use the file store

Steven Steven: They use local data

15: 33 Steven Erik: I think https should be a MUST
... 34 Steven Alain: Agree

Steven Erik: file: a MAY

Steven Alain: Agree

Steven ACTION: Steven to make https a MUST, file: a MAY

trackbot is creating a new ACTION.

trackbot Created ACTION-2014 - Make https a must, file: a may [on Steven Pemberton - due 2015-02-25].

15: 36 Steven Topic: AOB

Steven Steven: For next week we should review the rest of the spec, glossary, refs, and examples.

15: 37 Zakim -Steven

Zakim -[IPcaller]

Zakim Team_(forms)14:00Z has ended

Zakim Attendees were ebruchez, Steven, [IPcaller], Dimitris

Steven Steven: You're back home next week Erik?

Steven Erik: Yes

Steven Steven: OK, so call at regular time

Steven [ADJOURN]

Steven rrsagent, make minutes

s/^15: ?? Steven //g

s/15:03 Steven //

s/Steven Regrets/Regrets/

s/15:04 Steven //

s/^Steven //g

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/02/18 15:02:02 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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 Topic:/Topic:/G
FAILED: s/^15: ?? Steven //g
FAILED: s/15:03 Steven //
FAILED: s/Steven Regrets/Regrets/
FAILED: s/15:04 Steven //
FAILED: s/^Steven //g
Succeeded: s/Topic:/Topic:/
Succeeded: s/Topic:/Topic:/
Succeeded: s/Topic:/Topic:/G
Succeeded: s/Topic: Finish off Section 11/Topic: Finish off Section 11/

WARNING: Possible internal error: join/leave lines remaining: 
        <Steven> 14:03            -> Zakim has joined forms
        <Steven> 14:37            -> alain has joined forms
        <Steven> 15:00            -> ebruchez has joined forms


No ScribeNick specified.  Guessing ScribeNick: Steven
Inferring Scribes: Steven

WARNING: No "Topic:" lines found.

Present: Steven Alain Erik
Regrets: Nick Philip
Agenda: http://lists.w3.org/Archives/Public/public-forms/2015Feb/0013.html
Got date from IRC log name: 18 Feb 2015
Guessing minutes URL: http://www.w3.org/2015/02/18-forms-minutes.html
People with action items: 

WARNING: Possible internal error: join/leave lines remaining: 
        <scribe> 14:03            -> Zakim has joined forms
        <scribe> 14:37            -> alain has joined forms
        <scribe> 15:00            -> ebruchez has joined forms



WARNING: Possible internal error: join/leave lines remaining: 
        <scribe> 14:03            -> Zakim has joined forms
        <scribe> 14:37            -> alain has joined forms
        <scribe> 15:00            -> ebruchez has joined forms



WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]