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] Commented: (OFFICE-3024) ODF 1.1 AlignmentCollisions with ODF 1.0 Errata 01



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

Dennis Hamilton commented on OFFICE-3024:
-----------------------------------------

Here are the messages from March, 2010, that reflected the analysis summarized in the Description.

-----Original Message-----
From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org] 
<http://lists.oasis-open.org/archives/office/201003/msg00432.html>
Sent: Tuesday, March 30, 2010 18:23
To: robert_weir@us.ibm.com
Cc: 'Michael Brauer'; 'ODF TC List'; 'Patrick Durusau'; Svante.Schubert@Sun.COM
Subject: RE: [office] Re: OFFICE-2608 and Errata CD04 Defects

I checked the comparison of the COR1/Errata01 changes made to ODF 1.1 and
the diff that Patrick prepared between 1.1 and IS 26300.

There are only 4 collisions that have to be watched for.  I think we might
as well do (A) for now and adjust manually for (B).  These are the
(potential) collisions to watch out for:

 1. Section 9.3.11 sub-section Common Image Map Attributes and Elements.
There is an Errata01/COR1 change *nearby* but an amendment done as change
marking can be structured to miss that.

 2. Section 15.27.22 Errata01/COR1 change to style:wrap-dynamic-threshold
(not -treshold) in the schema fragment has already been changed in 1.1 and
it looks like a delta from IS 26300:2006.

 3. Section 16.1 Datatypes under custom data types has an errata change to
-length and there are different changes (in other parts of the same text)
made in 1.1 in contrast to IS 26300:2006.

 4. Appendix B Errata01/COR1 change to [DOMEvents] appears to be clobbered
by [DOMEvents2] and [DOMEvents3] in ODF 1.1.

 - Dennis

PS: If there is to be a full-up amended IS 26300 document produced, I think
it should not be until the very end when the amendment and the two
Corrigenda are applied, with 1.1 and IS 26300:2006/fixed-up all assured to
be in synch.

-----Original Message-----
From: robert_weir@us.ibm.com [mailto:robert_weir@us.ibm.com] 
<http://lists.oasis-open.org/archives/office/201003/msg00431.html>
Sent: Tuesday, March 30, 2010 16:39
To: dennis.hamilton@acm.org
Cc: 'Michael Brauer'; 'ODF TC List'; 'Patrick Durusau';
Svante.Schubert@Sun.COM
Subject: RE: [office] Re: OFFICE-2608 and Errata CD04 Defects

[ ... ]

I think we have a choice of 3 initial texts we could do the initial diff 
from:

A) ISO/IEC 26300
B) ISO/IEC 26300 + COR 1
C) ISO/IEC 26300 + COR 2

I don't think we want to wait for C to happen, since the DCOR ballot has 
not yet started, and we still need to make some more changes on the OASIS 
side and have another 15 day review.  So COR 2 is at least 4 months away. 

We could wait for COR 1 and option B) if we wanted, since the ballot for 
that has ended and we know what those corrections are.

Or we could do option A.  I think that is what Patrick's initial diff was.

I don't have a strong opinion on A versus B. 

-Rob

[ ... ] 


> ODF 1.1 Alignment Collisions with ODF 1.0 Errata 01
> ---------------------------------------------------
>
>                 Key: OFFICE-3024
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3024
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: General
>    Affects Versions: ODF 1.1, ODF 1.1 Errata 01
>         Environment: This issue applies for the reconciliation of ODF 1.0 Errata 01 with the ODF 1.1 base text as part of creating ODF 1.1 Errata 01 and ensuring correct transposition in the IS 26300:2006 transposition to ODF 1.1.
>            Reporter: Dennis Hamilton
>            Priority: Minor
>             Fix For: ODF 1.0 Errata 01
>
>
> There are four items in the ODF 1.0 Errata 01 (that is, part 1) where the change is already reflected in the text of ODF 1.1 or else there is another difference in ODF 1.1:
>  1. Section 9.3.11 sub-section Common Image Map Attributes and Elements.
> There is an Errata01 change *nearby* a place where ODF 1.1 is different.  The errata instructions should be such that the area of change is not touched.
>  2. Section 15.27.22 Errata01 change to style:wrap-dynamic-threshold
> (not -treshold) in the schema fragment has already been changed in 1.1 and
> it will already be handled in the IS 26300 alignment by COR1 and/or the FPDAM.  This last should be confirmed, however.
>  3. Section 16.1 Datatypes under custom data types has an errata change to
> -length and there are different changes (in other parts of the same text)
> made in 1.1 in contrast to IS 26300:2006.  This collision will need to be resolved carefully.
>  4. Appendix B Errata01 change to [DOMEvents] appears to be obsoleted by the replacement of [DOMEvents] with 
> [DOMEvents2] and [DOMEvents3] in ODF 1.1.  Here, the FPDAM may effectively cancel this change if it is made by COR1.

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