OpenDocument - Adv Document Collab SC

Hi, In example 6.7.2, pp15, of the generic change tracking proposal the example uses text:outline-level as an example of ac:changeXXX implementation. The bug I see is quite small, but deserves clarification none the less. The example uses text:p to demonstrate the use of text:outline-level. It appears from the draft ODF 1.2 spec that outline-level can only be applied to text:h and not text:p as the example currently shows. For those interested, see 19.844 on pp649 of Committee Specification Draft 07 / Public Review Draft 03 of ODF 1.2 part1. Using OpenOffice 3.2.0 (build 9483) from the Fedora repos, if I create a custom style "test" and give it an outline level (right click style, select modify, outline & numbering tab in dialog, outline level set to 3 for example) then OpenOffice will save text using that style as text:h instead of text:p. When I reset the outline level to "body text" for my custom style, then the paragraph is again saved using text:p. So should the example 6.7.2 from the generic proposal change to text:h instead when the outline level is applied? If so it will also need the markup from 6.13 because the element type is changing. Or should the change an attribute example in the proposal be modified to use a more straight forward attribute which does not need an element change too. It might be less than optimal to add a caveat to example 6.7.2 that the element type should change (text:p -> text:h) without showing the markup because it makes testing implementations against the example less straight forward.

Hi Ben, Thanks for pointing this out. Sorry for any confusion caused. The XML examples in the proposal are more for illustration purposes than anything else. For valid ODF examples, take a look at the use cases and the solutions on the Documents page of the subcommittee members page: Use Cases http://www.oasis-open.org/apps/org/workgroup/office-collab/download.php/40800/use-cases.zip and http://www.oasis-open.org/apps/org/workgroup/office-collab/download.php/41042/additional-use-cases-1.zip Generic Proposal Solutions http://www.oasis-open.org/apps/org/workgroup/office-collab/download.php/41547/generic-ct-use-case-solutions.zip The attribute addition use case (B.1) uses the text:start-value attribute on a list item rather than the example given in the proposal. We have validated all of the use case inputs against ODF 1.2 CD05 (which was the latest version at the time). The syntax in the proposal does not really need updating as it still illustrates how to mark up attribute addition, although the actual example would not be used in practice. Regards, Tristan On 28 Mar 2011, at 08:11, monkeyiq wrote: > Hi, > In example 6.7.2, pp15, of the generic change tracking proposal the > example uses text:outline-level as an example of ac:changeXXX > implementation. > > The bug I see is quite small, but deserves clarification none the > less. The example uses text:p to demonstrate the use of > text:outline-level. It appears from the draft ODF 1.2 spec that > outline-level can only be applied to text:h and not text:p as the > example currently shows. For those interested, see 19.844 on pp649 of > Committee Specification Draft 07 / Public Review Draft 03 of ODF 1.2 > part1. > > Using OpenOffice 3.2.0 (build 9483) from the Fedora repos, if I create > a custom style "test" and give it an outline level (right click style, > select modify, outline & numbering tab in dialog, outline level set to 3 > for example) then OpenOffice will save text using that style as text:h > instead of text:p. When I reset the outline level to "body text" for my > custom style, then the paragraph is again saved using text:p. > > So should the example 6.7.2 from the generic proposal change to text:h > instead when the outline level is applied? If so it will also need the > markup from 6.13 because the element type is changing. Or should the > change an attribute example in the proposal be modified to use a more > straight forward attribute which does not need an element change too. It > might be less than optimal to add a caveat to example 6.7.2 that the > element type should change (text:p -> text:h) without showing the markup > because it makes testing implementations against the example less > straight forward. > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > -- Tristan Mitchell, DeltaXML Ltd "Change control for XML" T: +44 1684 869 035 E: tristan.mitchell@deltaxml.com http://www.deltaxml.com Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK