[OASIS Issue Tracker] Updated: (OFFICE-3449) ODF 1.2 CD05 Part 15.5.3 Text Insertion Interoperable Definition Required

[ http://tools.oasis-open.org/issues/browse/OFFICE-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Hamilton updated OFFICE-3449:
------------------------------------

      Component/s:     (was: Needs Discussion)
    Fix Version/s: ODF-Next
                       (was: ODF 1.2 CD 06)
       Resolution: This issue is deferred to ODF-Next absent any offer by the appropriate experts to remedy the defects that prevent independent implementation of this feature with any level of interoperabilty.

> ODF 1.2 CD05 Part 1 5.5.3 Text Insertion Interoperable Definition Required
> --------------------------------------------------------------------------
>
>                 Key: OFFICE-3449
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3449
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Part 1 (Schema), Text
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>            Priority: Blocker
>             Fix For: ODF-Next
>
>
> This is related to ODF-3448 and related issues around tracked changes.
> There is actually no description of what constitutes an insertion and what it takes to reject one.  (Acceptance is easy).
> All we have said is that <text:change-start> and a matching <text:change-end> element bound the insertion and associate it with a <text:insertion> element.
> But the span of markup betweem a <text:change-start> to its corresponding <text:change-end> has all the characteristics of a selection.  And rejecting the insertion is an act of deletion.  Although that deletion is presumably not tracked, a consumer that supports insertion rejection, must know how to heal the removel of the inserted markup similar to ways that markup is healed around the scar of a tracked deletion.

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