OASIS Open Document Format for Office Applications (OpenDocument) TC

Greetings, I propose to treat the following issues as approved unless a request is made to discuss a particular issue by our meeting on Monday, 4 June 2018. I summarize the requested changes below. Office-3954 Editorial error in 19.728 table:table-background https://issues.oasis-open.org/browse/OFFICE-3954 19.728 table:table-background : table:show-details -> table:table-background (editorial error) Office-3950 - 3.17 Foreign Elements and Attributes: failure to handle the special case of the ruby element. https://issues.oasis-open.org/browse/OFFICE-3950 Present: OpenDocument schema permits the inclusion of character data for all its ancestors up to the <text:p> or <text:h> element ancestor element, .... Proposed: OpenDocument schema permits the inclusion of character data for all its ancestors up to the <text:p> or <text:h> element ancestor, *or a <text:ruby-base> ancestor element,* Proposed: Plus add <text:ruby-base> to root elements in schema: <rng:define name= office-document >     <rng:element name= office:document >       <rng:ref name= office-document-attrs />       <rng:ref name= office-document-common-attrs />       <rng:ref name= office-meta />       <rng:ref name= office-settings />       <rng:ref name= office-scripts />       <rng:ref name= office-font-face-decls />       <rng:ref name= office-styles />       <rng:ref name= office-automatic-styles />       <rng:ref name= office-master-styles />       <rng:ref name= office-body />     </rng:element>   </rng:define> to: <rng:define name= office-document >     <rng:element name= office:document >       <rng:ref name= office-document-attrs />       <rng:ref name= office-document-common-attrs />       <rng:ref name= office-meta />       <rng:ref name= office-settings />       <rng:ref name= office-scripts />       <rng:ref name= office-font-face-decls />       <rng:ref name= office-styles />       <rng:ref name= office-automatic-styles />       <rng:ref name= office-master-styles />       <rng:ref name= office-body /> *<rng:ref name= text:ruby-base />*     </rng:element>   </rng:define> Yes? Office-3946 19.855 text:relative-tab-stop-position: typo ident https://issues.oasis-open.org/browse/OFFICE-3946 ident -> indent Office-3945 improve description for text:anchor-type https://issues.oasis-open.org/browse/OFFICE-3945 Proposal: A Change first paragraph to: The text:anchor-type attribute specifies how a drawing shape is bound to a text document. The anchor position is the point at which a drawing shape is bound to a text document. B Add to section 19.754: The same attribute is available as graphic property 20.408. If the attribute is given both as element attribute 19.754 and as graphic property 20.408, then the element attribute has precedence over the graphic property. If neither an element attribute nor a graphic property is given or can be found by inheritance, then the attribute text:anchor-type defaults to value paragraph . C Add to section 20.408: The same attribute is available as element attribute 19.754. D Change the column labels in table 17 and table 24 from The drawing shape element appears… to The drawing shape element shall be located in file text… Any objections? Thanks! Hope everyone is having a great week! Patrick -- 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 Attachment: signature.asc Description: OpenPGP digital signature

hi Patrick, On 31/05/18 22:41, Patrick Durusau wrote: Office-3950 - 3.17 Foreign Elements and Attributes: failure to handle the special case of the ruby element. https://issues.oasis-open.org/browse/OFFICE-3950 Present: "OpenDocument schema permits the inclusion of character data for all its ancestors up to the <text:p> or <text:h> element ancestor element, ...." Proposed: "OpenDocument schema permits the inclusion of character data for all its ancestors up to the <text:p> or <text:h> element ancestor, *or a <text:ruby-base> ancestor element,* Proposed: Plus add <text:ruby-base> to root elements in schema: <rng:define name="office-document">     <rng:element name="office:document">       <rng:ref name="office-document-attrs"/>       <rng:ref name="office-document-common-attrs"/>       <rng:ref name="office-meta"/>       <rng:ref name="office-settings"/>       <rng:ref name="office-scripts"/>       <rng:ref name="office-font-face-decls"/>       <rng:ref name="office-styles"/>       <rng:ref name="office-automatic-styles"/>       <rng:ref name="office-master-styles"/>       <rng:ref name="office-body"/>     </rng:element>   </rng:define> to: <rng:define name="office-document">     <rng:element name="office:document">       <rng:ref name="office-document-attrs"/>       <rng:ref name="office-document-common-attrs"/>       <rng:ref name="office-meta"/>       <rng:ref name="office-settings"/>       <rng:ref name="office-scripts"/>       <rng:ref name="office-font-face-decls"/>       <rng:ref name="office-styles"/>       <rng:ref name="office-automatic-styles"/>       <rng:ref name="office-master-styles"/>       <rng:ref name="office-body"/> *<rng:ref name="text:ruby-base"/>*     </rng:element>   </rng:define> Yes? i don't understand what problem that would solve; the ruby element exists only as child of <text:ruby> which only exists inside paragraph elements. the only problem with the current text is that it technically excludes <text:ruby-base> because its parent <text:ruby> does not allow immediate character content children. if we know we're inside <text:ruby-base>, this implies that we're inside one of the paragraph elements as well, hence my proposal. -- Michael Stahl Senior Software-Entwickler LibreOffice ––– CIB software GmbH Geschäftsstelle Hamburg Flachsland 10 22083 Hamburg ––– T +49 (40) / 28 48 42 -296 F +49 (40) / 28 48 42 -100 Michael.Stahl@cib.de www.cib.de ––– Sitz: München Registergericht München, HRB 123286 Geschäftsführer: Dipl.-Ing. Ulrich Brandner

Michael, Glad you wrote because the text I suggest was your proposal. What is it that should be done differently? Thanks! Hope you are looking forward to a great weekend! Patrick On 06/01/2018 04:17 AM, Michael Stahl wrote: > > hi Patrick, > > On 31/05/18 22:41, Patrick Durusau wrote: >> Office-3950 - 3.17 Foreign Elements and Attributes: failure to handle >> the special case of the ruby element. >> >> https://issues.oasis-open.org/browse/OFFICE-3950 >> >> Present: "OpenDocument schema permits the inclusion of character data >> for all its ancestors up to the >> <text:p> or <text:h> element ancestor element, ...." >> >> Proposed: "OpenDocument schema permits the inclusion of character >> data for all its ancestors up to the >> <text:p> or <text:h> element ancestor, *or a <text:ruby-base> >> ancestor element,* >> >> Proposed: Plus add <text:ruby-base> to root elements in schema: >> >> <rng:define name="office-document"> >>     <rng:element name="office:document"> >>       <rng:ref name="office-document-attrs"/> >>       <rng:ref name="office-document-common-attrs"/> >>       <rng:ref name="office-meta"/> >>       <rng:ref name="office-settings"/> >>       <rng:ref name="office-scripts"/> >>       <rng:ref name="office-font-face-decls"/> >>       <rng:ref name="office-styles"/> >>       <rng:ref name="office-automatic-styles"/> >>       <rng:ref name="office-master-styles"/> >>       <rng:ref name="office-body"/> >>     </rng:element> >>   </rng:define> >> >> to: >> >> <rng:define name="office-document"> >>     <rng:element name="office:document"> >>       <rng:ref name="office-document-attrs"/> >>       <rng:ref name="office-document-common-attrs"/> >>       <rng:ref name="office-meta"/> >>       <rng:ref name="office-settings"/> >>       <rng:ref name="office-scripts"/> >>       <rng:ref name="office-font-face-decls"/> >>       <rng:ref name="office-styles"/> >>       <rng:ref name="office-automatic-styles"/> >>       <rng:ref name="office-master-styles"/> >>       <rng:ref name="office-body"/> >> >> *<rng:ref name="text:ruby-base"/>* >> >>     </rng:element> >>   </rng:define> >> >> Yes? >> > > i don't understand what problem that would solve; the ruby element > exists only as child of <text:ruby> which only exists inside paragraph > elements. > > the only problem with the current text is that it technically excludes > <text:ruby-base> because its parent <text:ruby> does not allow > immediate character content children. > > if we know we're inside <text:ruby-base>, this implies that we're > inside one of the paragraph elements as well, hence my proposal. > -- 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 Attachment: signature.asc Description: OpenPGP digital signature

hi Patrick, On 01/06/18 16:48, Patrick Durusau wrote: Michael, Glad you wrote because the text I suggest was your proposal. What is it that should be done differently? i'm sorry, i now realise i was writing something very ambiguous in the proposal: 'the easiest fix is to just add the <text:ruby-base> element to the list of "root" elements:' here i meant the <text:p> and <text:h> as the "root" elements in the context of that sentence, and to add the <text:ruby-base> to the list as another "root" element in that context: On 06/01/2018 04:17 AM, Michael Stahl wrote: On 31/05/18 22:41, Patrick Durusau wrote: Present: "OpenDocument schema permits the inclusion of character data for all its ancestors up to the <text:p> or <text:h> element ancestor element, ...." Proposed: "OpenDocument schema permits the inclusion of character data for all its ancestors up to the <text:p> or <text:h> element ancestor, *or a <text:ruby-base> ancestor element,* ... but now you thought it means i want to add it to the document's root elements, which i don't :) probably i should have written "ancestor element" instead. -- Michael Stahl Senior Software-Entwickler LibreOffice ––– CIB software GmbH Geschäftsstelle Hamburg Flachsland 10 22083 Hamburg ––– T +49 (40) / 28 48 42 -296 F +49 (40) / 28 48 42 -100 Michael.Stahl@cib.de www.cib.de ––– Sitz: München Registergericht München, HRB 123286 Geschäftsführer: Dipl.-Ing. Ulrich Brandner

Michael, Thanks! Hope you are nearing a great weekend! Patrick On 06/01/2018 11:10 AM, Michael Stahl wrote: > hi Patrick, > > On 01/06/18 16:48, Patrick Durusau wrote: >> Michael, >> >> Glad you wrote because the text I suggest was your proposal. >> >> What is it that should be done differently? > i'm sorry, i now realise i was writing something very ambiguous in the > proposal: > > 'the easiest fix is to just add the <text:ruby-base> element to the > list of "root" elements:' > > here i meant the <text:p> and <text:h> as the "root" elements in the > context of that sentence, and to add the <text:ruby-base> to the list > as another "root" element in that context: >> On 06/01/2018 04:17 AM, Michael Stahl wrote: >>> On 31/05/18 22:41, Patrick Durusau wrote: >>>> Present: "OpenDocument schema permits the inclusion of character data >>>> for all its ancestors up to the >>>> <text:p> or <text:h> element ancestor element, ...." >>>> >>>> Proposed: "OpenDocument schema permits the inclusion of character >>>> data for all its ancestors up to the >>>> <text:p> or <text:h> element ancestor, *or a <text:ruby-base> >>>> ancestor element,* > ... but now you thought it means i want to add it to the document's > root elements, which i don't :) > > probably i should have written "ancestor element" instead. > -- 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 Attachment: signature.asc Description: OpenPGP digital signature

Michael, If you have time, please check the following schema mods to make sure I have caught all the cases for adding <text:ruby-base> element: *****  <rng:define name="header-footer-content">     <rng:choice>       <rng:group>         <rng:ref name="text-tracked-changes"/>         <rng:ref name="text-decls"/>         <rng:zeroOrMore>           <rng:choice>             <rng:ref name="text-h"/>             <rng:ref name="text-p"/> to:  <rng:define name="header-footer-content">     <rng:choice>       <rng:group>         <rng:ref name="text-tracked-changes"/>         <rng:ref name="text-decls"/>         <rng:zeroOrMore>           <rng:choice>             <rng:ref name="text-h"/>             <rng:ref name="text-p"/>             <rng:ref name="text:ruby-base/> *******************************  <rng:define name="text-content">     <rng:choice>       <rng:ref name="text-h"/>       <rng:ref name="text-p"/> to:  <rng:define name="text-content">     <rng:choice>       <rng:ref name="text-h"/>       <rng:ref name="text-p"/>       <rng:ref name="text:ruby-base"/> ************************************ <rng:define name="text-list-item-content">     <rng:optional>       <rng:ref name="text-number"/>     </rng:optional>     <rng:zeroOrMore>       <rng:choice>         <rng:ref name="text-p"/>         <rng:ref name="text-h"/> to: <rng:define name="text-list-item-content">     <rng:optional>       <rng:ref name="text-number"/>     </rng:optional>     <rng:zeroOrMore>       <rng:choice>         <rng:ref name="text-p"/>         <rng:ref name="text-h"/>         <rng:ref name="text:ruby-base/> *******************************************  <rng:define name="text-numbered-paragraph">     <rng:element name="text:numbered-paragraph">       <rng:ref name="text-numbered-paragraph-attr"/>       <rng:optional>         <rng:ref name="text-number"/>       </rng:optional>       <rng:choice>         <rng:ref name="text-p"/>         <rng:ref name="text-h"/>       </rng:choice>     </rng:element> to:  <rng:define name="text-numbered-paragraph">     <rng:element name="text:numbered-paragraph">       <rng:ref name="text-numbered-paragraph-attr"/>       <rng:optional>         <rng:ref name="text-number"/>       </rng:optional>       <rng:choice>         <rng:ref name="text-p"/>         <rng:ref name="text-h"/>          <rng:ref name="text:ruby-base"/>       </rng:choice>     </rng:element> I searched for pairs of "text-p" and "text-h" twice so I suspect it to be correct but a second set of eyes never hurts! Hope you are having a great week! Patrick On 06/01/2018 11:40 AM, Patrick Durusau wrote: > Michael, > > Thanks! > > Hope you are nearing a great weekend! > > Patrick > > > On 06/01/2018 11:10 AM, Michael Stahl wrote: >> hi Patrick, >> >> On 01/06/18 16:48, Patrick Durusau wrote: >>> Michael, >>> >>> Glad you wrote because the text I suggest was your proposal. >>> >>> What is it that should be done differently? >> i'm sorry, i now realise i was writing something very ambiguous in the >> proposal: >> >> 'the easiest fix is to just add the <text:ruby-base> element to the >> list of "root" elements:' >> >> here i meant the <text:p> and <text:h> as the "root" elements in the >> context of that sentence, and to add the <text:ruby-base> to the list >> as another "root" element in that context: >>> On 06/01/2018 04:17 AM, Michael Stahl wrote: >>>> On 31/05/18 22:41, Patrick Durusau wrote: >>>>> Present: "OpenDocument schema permits the inclusion of character data >>>>> for all its ancestors up to the >>>>> <text:p> or <text:h> element ancestor element, ...." >>>>> >>>>> Proposed: "OpenDocument schema permits the inclusion of character >>>>> data for all its ancestors up to the >>>>> <text:p> or <text:h> element ancestor, *or a <text:ruby-base> >>>>> ancestor element,* >> ... but now you thought it means i want to add it to the document's >> root elements, which i don't :) >> >> probably i should have written "ancestor element" instead. >> -- 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 Attachment: signature.asc Description: OpenPGP digital signature

hi Patrick, On 06.06.2018 17:27, Patrick Durusau wrote: Michael, If you have time, please check the following schema mods to make sure I have caught all the cases for adding <text:ruby-base> element: no schema changes are needed, all that is necessary is to tweak the sentence in 3.17 Foreign Elements and Attributes so that it handles the existing special case of text:ruby-base in the existing schema, as done in the proposal of the issue. regards,  michael -- Michael Stahl Senior Software-Entwickler LibreOffice ––– CIB software GmbH Geschäftsstelle Hamburg Flachsland 10 22083 Hamburg ––– T +49 (40) / 28 48 42 -296 F +49 (40) / 28 48 42 -100 Michael.Stahl@cib.de www.cib.de ––– Sitz: München Registergericht München, HRB 123286 Geschäftsführer: Dipl.-Ing. Ulrich Brandner