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] Updated: (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:all-tabpanel ]

Oliver-Rainer Wittmann updated OFFICE-2796:
-------------------------------------------


In my opinion it is not the intrinsic scope of the ODF specification to specify how change tracking has to be implemented for an office document. Thus, Dennis' concern <cite>that there is still not enough information to implement this feature from what is provided in the specification alone.</cite> is not an issue for the ODF specification from my point of view.
I agree that hints and notes about what kind of change tracking capabilities can be handled by ODF are useful and as change tracking is on our agenda for "ODF Next" there will be hopefully improvement in the next version of ODF.

I do not think that an ODF supporting application will implement its change tracking capabilities for an office document down on the level of the to be created ODF XML.
The change tracking of ODF represents the _result_ of a performed change tracking to an office document in an application.
For a tracked deletion we included some wording for the reconstruction of the document content. This shall not be interpreted as ODF is defining how rejection of tracked changes have to be implemented.
This wording only covers very simple cases - namely the following:
- Deletions of office document text content which can all be presented in <text:p> elements respectively <text:h> elements
- Deletion of office document content which can be presented by complete ODF elements - e.g., the deletion of a complete table, section, paragraph, list or a mixture of these.
My given proposal to this "reconstruction" text reflects more or less how OpenOffice.org represents more complex deletions - like deletions given in OFFICE-2621.
In simple words spoken it is something like this:
The content whose deletion is tracked can be identified inside the created ODF XML. It is removed for the document content and moved into a <text:deletion> element. If this content does not only cover complete ODF elements the corresponding ODF XML snippet is not valid. Thus, the needed missing start and end tags are added to represent this deletion in ODF. If the left document content is not valid, because the end tags are not matching the left document content is adjusted accordingly. For the reconstruction the addition of tags and the made adjustment have to be undone.
This is what I tried to express with my proposal as an improvement for ODF 1.2.

A possible consumer of an ODF document containing tracked deletions does not need to know more than that the <text:deletion> element contains the deleted content. If the consumer contains change tracking capabilities it will know how to get this deleted content back into the office document. From my point of view it is not the intrinsic scope of ODF to define in detail and complete how this has to be done, because this in general covers office document editing functionality, namely insertion of certain content at a certain position in the office document.

I support the motion to work in the area of change tracking and to include certain hints and notes about what kind of deletions can be handled by ODF. But, I do not think that ODF 1.2 is the right version for it.

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