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=21722#action_21722 ] 

Dennis Hamilton commented on OFFICE-3383:


If there is a way to define a <text:p> with reduced content, that could deal with it.  I'm not sure if RNG permits different occurrences of the same element to have different patterns though.  We know it works for attributes, I am unsure about the element case.  [XML1.0] might have something to say about that also.  Another way might be to allow choice between that and something far simpler, deprecating (but not banning) the <text:p> alternative.

i tend to favor re-use and generality.  But when making heavy-weight features out of ones having lightweight purposes, I have doubts, especially when we are not making something that is not defined to contribute to the "text of the document."   In my experience, the desirable generalizations are ones that simplify the work of consumers because there can be simplification of implementations.  Here, I think all the freedom goes to producers and consumers have to second-guess.  That seems unfortunate.

I have similar reservations about some other places where arbitrary element-content and paragraph-content patterns are allowed.  Among those, having <text:p>  for <office:changed-info>, which is just meta-information, perhaps accessibility information, seems too extreme.  

Although it had not struck me before, this is also an invitation for hiding covert content and also raises concerns with regard to the application of digital signatures to the markup as a whole.  

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