XForms Users Community Group Teleconference -- 19 Oct 2016

header@bind (fixed)

https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0016.html

Steven: I added @bind to header

<output/> + Note

https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0018.html

Steven: So I've cleaned it up, and shortened it
... but have a question about this note:

When the media type is specified, implementations may handle the output

content as presentation-only or as interactive content, and interactive

content may be isolated from or capable of accessing the enclosing

document that contains the output. Further implementation experience and

user feedback is required. For example, if the output content includes

XForms user interface elements, it may be desirable for them to access a

default XForms model in the output content or from the enclosing document.

Steven: Anybody do this?
... what's it mean? How is it possible?

Alain: I don't support this

Steven: I'm in the mood to delete this note

Erik: might be for video players or some such?
... I support removing this.

Philip: I agree to get rid of it, on the grounds that only simple content is allowed.
... it might even be the source of an attack if it were allowed.

<scribe> ACTION: Steven to remove second note in Output section [recorded in http://www.w3.org/2016/10/19-forms-minutes.html#action01]

<trackbot> Created ACTION-2077 - Remove second note in output section [on Steven Pemberton - due 2016-10-26].

@value

https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0010.html

item@value

https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0022.html

Erik: We talked about this before.

Steven: OK, I need to check old minutes

Erik: In HTML it's the other way round.

<ebruchez> <option value="...">Label</option>

Erik: that's not exactly relevant

<scribe> ACTION: Steven to search old minutes about <item label="...>value</item> [recorded in http://www.w3.org/2016/10/19-forms-minutes.html#action02]

<trackbot> Created ACTION-2078 - Search old minutes about <item label="...>value</item> [on Steven Pemberton - due 2016-10-26].

item values

https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0024.html

Erik: item@ref doesn't give you the value

Steven: The text is not clear on this

8.3.2 The item Element[edit]

This element specifies the storage value and label to represent an item in a list. It is found within elements select1 and select, or grouped in element choices.

Data Binding Restriction: All lexical values must be valid according to the datatype bound to the selection control. If the Single Item Binding attributes are used and indicate a node in a model other than the bound node of the containing selection control, then an xforms-binding-error must occur.

Erik: Interesting, I don't know what that is

Steven: Previous version

8.3.3 The value Element[edit]

This element provides a storage value to be used when an item is selected. The storage value is determined by one of three methods, in order of precedence:

the value of a node indicated by a Single Item Binding expression, if specified

the result of evaluating an expression appearing in attribute value, if specified

the inline content of the value element (when neither the Single Item Binding nor the value attribute are expressed).

Common Attributes: Common, Single Item Binding (author-optional)

Special Attributes:

value

Author-optional. An expression to be evaluated. The string result of the evaluation is used as the storage value of the item when it is selected. If a Single Item Binding is expressed, then this attribute has no effect. The evaluation context is the same as would be applied to the evaluation of the Single Item Binding. An empty string is used if the evaluation fails.

Erik: I'm pretty sure we don't support a binding
... to set the value of an item

Alain: No ref or bind in my implementation

Steven: I propose removing @ref and @bind from item and item/value

Erik: I think item/value@ref should be allowed, it should be like <output/>

Steven: But on <item/> not?

Erik: It might be OK to allow the binding, but it shouldn't provide the value.

Steven: In other places if you have a ref AND a value, the value gets ignored

Erik: We do actually support it

Erik: It supports relevance etc.
... we support that, but it is against the spec
... the rationale is thatyou provide context

<ebruchez> <Itemset ref="my-items"><label>Label<'/label><value ref="value"/></iemset>

<ebruchez> <Itemset ref="my-item"><label>Label<'/label><value ref="value"/></iemset>

<ebruchez> <Itemset ref="my-item[... some condition ...]"><label>Label<'/label><value ref="value"/></iemset>

Erik: this makes items not appear if they are not relevant
... which is maybe an argument for unifying <item> and <itemset>
... I would not be enthusiastic with <item@ref> setting the value of the item

Steven: Your suggestion to allow both ref and value would be a spec change
... we now say if there is ref and value, ignore value
... you are saying evaluate both, use the value, but in the context of the ref

Philip: I'm happy with that

Steven: It's now a small change, now that @value is in Common

Erik: It's fine (it's what we do already)

Steven: It still retains a strange inconsistency with item@ref
... Shall we leave the decision for a week to allow it to sink in?

Erik: I see the consistency problem between item and output.
... each has a label and a value

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

Erik: Still working on it.

AOB

[None]

[Adjourn]

- DRAFT -

XForms Users Community Group Teleconference

19 Oct 2016

Attendees

Contents

header@bind (fixed)

<output/> + Note

@value

item@value

item values

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

AOB

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output