[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (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:comment-tabpanel&focusedCommentId=22532#action_22532 ]
Dennis Hamilton commented on OFFICE-3449:
-----------------------------------------
My main concern is that we have a major defect that has been there since ODF 1.0 and that is preventing independent interoperable implementation.
That there are interoperable implementations in the wild is an additional issue, since they use these elements and the ODF namespaces, but the only way to interoperate is to reverse engineer what other implementations are seen to do or (worse yet) consult any available code. This does give us a family of legacy documents the preservation of which we have no way to assure other than the preservation of the software that created those documents. That is not what I thought the promise of ODF was all about.
With regard to the DeltaXML proposal being tried, I am also concerned with what namespaces those trial implementations will be using and how any harmonization might then occur, especially if the effect is to not use the current definitions (forgiveable, I suppose) but to pepper ODF documents with foreign elements that are someones experimental attempt at the DeltaXML proposal.
> 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: Needs Discussion, Part 1 (Schema), Text
> Affects Versions: ODF 1.2 CD 05
> Reporter: Dennis Hamilton
> Priority: Blocker
> Fix For: ODF 1.2 CD 06
>
>
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]