OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (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:comment-tabpanel&focusedCommentId=21713#action_21713 ] 

Michael Brauer commented on OFFICE-3383:

A few comments:

1. I'm in favor of keeping <text:p>, even though maybe with restricted content. The simple reason is that it is one of the design pattern of ODF to reuse concept. So, if a change tracking note may consist of several possibly formatted paragraphs, then we should use <text:p> for this. We further should be careful to not break backward compatibility. If we break backward compatibility because we add exciting new features from which users benefit that may be okay. But users don't benefit if we omit the <text:p> elements only because they may not be necessary. So, that's a change I would not make.
2. Is it a defect that <text:p> here seems to support far more than applications support in practice? Well, one may see it either way, but it is certainly some work to figure out what should be permitted inside these <text:p> elements and what should be forbidden. Two examples: 1. <text:p> allows the use fields, and the use of fields for authors or dates may indeed by reasonable in some cases. 2. Change tracking: It may look strange at the first glance if a change tracking note can contain change tracking information itself. But why not? If an application wants to track changes in these notes, why should it not be allowed to do so?

Taking it all together, I think the issue is not serious enough and the resolution not easy enough that I would change anything for ODF 1.2. But it may worth to keep this open for ODF-Next.

> 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]