[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (OFFICE-3383) ODF 1.2-1 5.5.6<office:change-info> content overkill
[ http://tools.oasis-open.org/issues/browse/OFFICE-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Hamilton updated OFFICE-3383:
------------------------------------
Component/s: Needs Discussion
Part 1 (Schema)
Schema and Datatypes
Fix Version/s: ODF 1.2 CD 06
(was: ODF-Next)
Oliver, I accept your recommendation that limited markup be allowed in such a comment. I don't mind that case, although it will take some schema work. I'm not sure that even a paragraph element is required, unless you seriously intend to allow styles and font choices here. Some sort of simple-text RNG rule with modest formatting should work, based on what OO.o actually allows to be entered, say. without opening up the door through <draw:frame> and <draw:controls> and everything that provides (<draw:object>, etc.)
Furthermore, I claim that allowing general paragraph content is a defect, since it allows change-tracking in change-tracking comments which is seriously strange. It also allows <office:annotation> another wonder.
It also allows serious content by nesting.
SInce no implementation, as far as we know, produces anything like what ODF 1.2 CD05 says is acceptable, we should fix it now.
How come your vote over-rides my vote? I'm changing this back to target ODF 1.2 CD06 and setting needs discussion.
> ODF 1.2-1 5.5.6 <office:change-info> content overkill
> -----------------------------------------------------
>
> Key: OFFICE-3383
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-3383
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: Needs Discussion, Part 1 (Schema), Public Review, Schema and Datatypes
> Affects Versions: ODF 1.2 CD 05
> Reporter: Dennis Hamilton
> Priority: Minor
> Fix For: ODF 1.2 CD 06
>
>
> The <office:change-info> element occurs within each of the three forms of <text:changed-region> element as a source of identifying information concerning the change being tracked. It is not part of the tracked-change material itself.
> In addition to the basic identifying information, there may be one or more <text:p> elements for commentary about the change.
> This is serious overkill. Not only can almost any possible content be introduced this way, but change tracking, index marks, tables of content, etc., are admissible.
> It makes no sense to provide such a general provision for arbitrary text in what is basically a descriptive comment that may not even be implemented by any producers at this time. It is also not something that needs to be subject to the treatment of presentation in the same way as document content, including application of styles, incorporation of dynamic fields, cross-referencing, etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]