[OASIS Issue Tracker] Created: (OFFICE-3553) ODF 1.1 Errata ZipReference Bind

ODF 1.1 Errata Zip Reference Bind
---------------------------------

                 Key: OFFICE-3553
                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3553
             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
          Issue Type: Sub-task
          Components: Packaging
    Affects Versions: ODF 1.1, ODF 1.0 (second edition), ODF 1.0 Errata 02
         Environment: This issue straddles the differences between ODF 1.0 and IS 26300 and ODF 1.1.  ODF 1.0 Errata 02 gets into the act.
            Reporter: Dennis Hamilton
            Assignee: Dennis Hamilton
             Fix For: ODF 1.1 Errata 01


See OFFICE-2205:

 - ODF 1.2 will reference the PKWare APPNote, the same that ODF 1.0 originally referenced. 
 - The Errata 02 change provides a resolvable link to a different specification that is the one in IS 26300. 
 - IS 26300 COR2 will make that change too. 
 - Unless we make the same change via ODF 1.1 Errata 01, alignment with ODF 1.1 will change it back to an unresolvable info-zip one, and keep ODF 1.1 incompatible with ODF 1.2 in this respect. 
 - When we do the ODF 1.1 Errata, it would be a very good time to go back to the PKWare Appnote. If we make ODF 1.1 align with the fix here, it will let the COR2 change to IS 26300 stand
 - Unfortuantely, ODF 1.2 will be a breaking change that we can't avoid making, and now it breaks with respect to all versions of ODF 1.0/1.1 everywhere.   

This note is so that this situation is watched for during creation of ODF 1.1 Errata 01 and the alignment that goes through the IS 26300/AMD1 process.

I suppose there is no harm to simoly making the IS 26300/AMD1 use the resolvable info-zip reference, unless the ITTF sheriff notices. 



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