[OASIS Issue Tracker] Issue Comment Edited: (OFFICE-3312)NEEDS-DISCUSSION: Public Comment: Proposal to improve change tracking inODF

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Dennis Hamilton edited comment on OFFICE-3312 at 8/17/10 12:49 PM:
-------------------------------------------------------------------

Complications from the XML Unique ID requirement

In Guiding Principle Subcase 3.3, it is important to appreciate that however the case of ID-valued attributes in deletions is handled, the requirement that ID-valued attributes be unique across the entire XML document containing the attributes continues to hold.  Whatever happens, the result of tracking the deletion cannot lead to two different attribute instances with the same ID value in the XML document (e.g., content.xml).  

It is also the case that ID-valued attributes may serve as anchors for references into the XML document via IRI references (including local-document ones) that use the ID value as a fragment identifier.

[Note: although non-validating processors of various kinds are not required to check this and are not permitted to treat duplications as fatal, uniqueness of all ID-value instands is still a condition on the document and an application implementation (e.g., an OpenDocument Consumer) might have to treat the condition as fatal, depending on the circumstances.]

      was (Author: orcmid):
    Complications from the XML Unique ID requirement

In Guiding Principle Subcase 3.3, it is important to appreciate that however the case of ID-valued attributes in deletions is handled, the requirement that ID-valued attributes be unique across the entire XML document containing the attributes continues to hold.  Whatever happens, the result of tracking the deletion cannot lead to two different attribute instances with the same ID value in the XML document (e.g., content.xml).  

[Note: although non-validating processors of various kinds are not required to check this and are not permitted to treat duplications as fatal, uniqueness of all ID-value instands is still a condition on the document and an application implementation (e.g., an OpenDocument Consumer) might have to treat the condition as fatal, depending on the circumstances.]
  
> NEEDS-DISCUSSION: Public Comment: Proposal to improve change tracking in ODF
> ----------------------------------------------------------------------------
>
>                 Key: OFFICE-3312
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3312
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Lists, Part 1 (Schema), Schema and Datatypes, Styles, Table, Text
>    Affects Versions: ODF 1.2 CD 05
>         Environment: This proposal addresses issues around change-tracking as it has existed since ODF 1.0.  It is evidently offered in the context of ODF 1.2.
>            Reporter: Dennis Hamilton
>            Priority: Blocker
>             Fix For: ODF 1.2 CD 06
>
>
> Copied from office-comment list
> Original author: Robin LaFontaine <robin.lafontaine@deltaxml.com>
> Original dates: 2010-07-30-09:33Z to 2010-07-31-09:52Z
> Original URLs: 
>    http://lists.oasis-open.org/archives/office-comment/201007/msg00009.html
>    http://lists.oasis-open.org/archives/office-comment/201007/msg00010.html   
>    http://lists.oasis-open.org/archives/office-comment/201007/msg00011.html
> [Note: the office-comment issue scraper may have run but these came through at a time when the JIRA engine may have been blocked in some way.  I have created this issue as a placeholder until such time as the automated forwarder catches up.]

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