12:47:14 RRSAgent has joined #forms 12:47:15 logging to http://www.w3.org/2016/10/19-forms-irc 12:47:16 RRSAgent, make logs public 12:47:17 Zakim has joined #forms 12:47:19 Zakim, this will be 12:47:19 I don't understand 'this will be', trackbot 12:47:20 Meeting: XForms Users Community Group Teleconference 12:47:20 Date: 19 October 2016 12:51:19 Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0025 12:51:31 Steven has changed the topic to: Agenda: https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0025 12:51:35 Chair: Steven 12:56:18 ebruchez has joined #forms 13:00:18 Present: Steven, Alain, Erik, Philip 13:00:39 pfennell has joined #forms 13:02:03 Topic: header@bind (fixed) 13:02:03 https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0016.html 13:02:16 Steven: I added @bind to header 13:02:43 Topic: + Note 13:02:43 https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0018.html 13:03:24 Steven: So I've cleaned it up, and shortened it 13:03:53 ... but have a question about this note: 13:03:54 When the media type is specified, implementations may handle the output 13:03:54 content as presentation-only or as interactive content, and interactive 13:03:54 content may be isolated from or capable of accessing the enclosing 13:03:54 document that contains the output. Further implementation experience and 13:03:54 user feedback is required. For example, if the output content includes 13:03:54 XForms user interface elements, it may be desirable for them to access a 13:03:56 default XForms model in the output content or from the enclosing document. 13:04:54 Steven: Anybosy do this? 13:05:01 ... what's it mean? How is it possible? 13:05:11 s/bosy/body/ 13:05:43 Alain: I don't support this 13:06:26 Steven: I'm in the mood to delete this note 13:06:51 Erik: might be for video players or some such? 13:06:59 ... I support removing this. 13:07:37 Philip: I agree to get rid of it, on the grounds that only simple content is allowed. 13:08:17 ... it might even be the source of an attack if it were allowed. 13:08:41 ACTION: Steven to remove second note in Output section 13:08:41 Created ACTION-2077 - Remove second note in output section [on Steven Pemberton - due 2016-10-26]. 13:09:26 Topic: @value 13:09:26 https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0010.html 13:10:32 Topic: item@value 13:10:32 https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0022.html 13:12:22 Erik: We talked about this before. 13:12:34 Steven: OK, I need to check old minutes 13:12:42 Erik: In HTML it's the other way round. 13:12:45 13:13:01 ... that's not exactly relevant 13:13:37 ACTION: Steven to search old minutes about value [on Steven Pemberton - due 2016-10-26]. 13:14:36 Topic: item values 13:14:36 https://lists.w3.org/Archives/Public/public-xformsusers/2016Oct/0024.html 13:15:46 Erik: item@ref doesn't give you the value 13:16:20 Steven: The text is not clear on this 13:17:32 8.3.2 The item Element[edit] 13:17:32 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. 13:17:51 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. 13:18:27 Erik: Interesting, I don't know what that is 13:20:22 Steven: Previous version 13:20:22 8.3.3 The value Element[edit] 13:20:22 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: 13:20:22 the value of a node indicated by a Single Item Binding expression, if specified 13:20:22 the result of evaluating an expression appearing in attribute value, if specified 13:20:24 the inline content of the value element (when neither the Single Item Binding nor the value attribute are expressed). 13:20:24 Common Attributes: Common, Single Item Binding (author-optional) 13:20:24 Special Attributes: 13:20:25 value 13:20:25 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. 13:20:27 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. 13:20:58 Erik: I'm pretty sure we don't support a binding 13:21:13 ... to set the value of an item 13:21:42 Alain: No ref or bind in my implementation 13:22:25 Steven: I propose removing @ref and @bind from item and item/value 13:22:59 Erik: I think item/value@ref should eb allowed, it should be like 13:23:06 s/ eb / be / 13:23:26 Steven: But on not? 13:24:01 Erik: It might be OK to allow the binding, but it shouldn't provide the value. 13:24:28 13:25:30 Steven: In other places if you have a ref AND a value, the value gets ignored 13:25:46 Erik: We do actually support it 13:25:47 13:26:16 Erik: It supports relevance etc. 13:26:25 ... we support that, but it is against the spec 13:27:11 ... the rationale is that if you provide context 13:27:22 s/ if // 13:28:43