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-2796) 5.5.4 text:deletion- second item in list: "If the change mark is inside a heading, proceed asabove, except adapt the end tags to match their new counterparts." ?



    [ http://tools.oasis-open.org/issues/browse/OFFICE-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21643#action_21643 ] 

Dennis Hamilton commented on OFFICE-2796:
-----------------------------------------

The attempt to provide more clarity on what is required so that ODF implementations can provide interoperable implementations over some common definition of tracked changes in the markup is in these two issues: OFFICE-3449 and OFFICE-3448.

If the defect part of this is not resolved in ODF 1.2, then I think we have to say something about implementation-dependency or even implementation-definition.

I do not believe we are talking about how it is implemented but in what it is so that documents that have it can be interpreted interoperably.  If this feature of the document is not one from which it is possible to independently construct interoperable implementations (whether implementers choose to do so and however they choose to do it) without examination of an implementation, then I say the specification of this feature has failed.  

There is no point to providing tracked changes in a way where someone else can't determine how to reject them.  Producers need to know how to produce tracked changes that consumers will know how to reject them.  

I'm certain that hints are not what this specification is about.  We'd be more straightforward making it implementation-dependent.  I can't imagine that being acceptable by those who are counting on this as an open standard for serious office-productivity document interchange that promises standards-assured choice and substitutability of conformant implementations, however.

> 5.5.4 text:deletion - second item in list: "If the change mark is inside a heading, proceed as above, except adapt the end tags to match their new counterparts." ?
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OFFICE-2796
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2796
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Needs Discussion, Text
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Patrick Durusau
>            Assignee: Oliver-Rainer Wittmann
>             Fix For: ODF 1.2 CD 06
>
>
> 5.5.4 text:deletion - second item in list: "If the change mark is inside a heading, proceed as above, except adapt the end tags to match their new counterparts." ?
> The preceding paragraph says: 
> "If the change mark is inside a paragraph, insert the text content of the <text:deletion> element as if the beginning <text:p> and final </text:p> tags were missing."
> Does this mean:
> "If the change mark is inside a heading, insert the text content of the <text:deletion> element as if the beginning <text:p> and final </text:p> tags were missing."
> ? Since deleted text is save in <text:p></text:p>, shouldn't it simply be placed back in the <text:h></text:h> element? 

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