Greetings!
Our chat notes from the OASIS teleconference on January 7, 2019.
Hope everyone is having a great week!
Patrick
*********************
Patrick: Alfred - present
Patrick: Andreas - present
Patrick: Michael - present
Patrick: Regina - present
Patrick: Patrick - present
Patrick: agenda approved by consent
Patrick: Michael doesn't know of any ODF applications using these elements, can deprecate
Patrick: Patrick - are these elements used in interchange with MS products?
Patrick: Alfred - not supported in PowerPoint at all - deprecation not a problem
Patrick: attributes enable two distinct texts to be displayed whereas content only allows one text
Patrick: Andreas - consumer who can't evaluate the condition, knows what text to show - by having the content in the element - What was supposed to be shown when the document was saved is shown
Patrick: Don't know if the content shown meets the condition or not but it is what is shown be a consumer that can't evaluate the condition.
Patrick: suggested resolution: close with comment to editors
Michael Stahl: <define name="xforms-model">
<element name="xforms:model">
<ref name="anyAttListOrElements"/>
</element>
</define>
Michael Stahl: ODF 1.1 says "Buttons may be used to trigger an XForms submission by adding an form:xforms-submission attribute. If such a button is triggered, a previously declared XForms submission with the given name is executed."
Patrick: Alfred suggests it may be an ID reference?
Patrick: Looking at 19.904 xmforms:bind, there may be a case to be made for that reading
Patrick: With OpenDocument form buttons, the bind attribute refers to an <xforms:submission>
element with the given ID. Pushing the button causes the appropriate XForms submission action
to be performed.
Patrick: Change log from ODF 1.1: The attribute xforms:submission specified in section 11.3.11 has been renamed to form:xforms-submission.
Patrick: Name refers to the name of the form in form:name and not the XForms submission itself - that is the ODF form is executed
Patrick: Patrick to write up an explanation, that possibly explains this more clearly
--
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau