[OASIS Issue Tracker] Commented: (OFFICE-2694) ODF 1.2 draft 3breaks modularity

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

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

Dennis Hamilton commented on OFFICE-2694:
-----------------------------------------

Nowhere in this issue have I proposed processing the parts as separate standards, so I will not address any objections that assumes that is the proposal or even a consequence of the proposal.  When I say  "arrange for approval" I mean arrange for approval of that packaging for a single standard by the OASIS TC Administrator, not approval as separate standards.  Does that help?

I believe my recommendation is very clear.  It depends on spending more time working with the OASIS TC Administrator so that we can accomplish in a straightforwrad way what ECMA and JTC1 manage without difficulty when a *single* standard has multiple parts with their own conformance sections.

It remains my considered opinion that the additional complexification of the additional and pointless document for the purpose of carrying 3 informative pages is a disservice.

I also maintain that the approach is defect-prone but the specific defects I see already will be raised with separate JIRA issues.

> ODF 1.2 draft 3 breaks modularity
> ---------------------------------
>
>                 Key: OFFICE-2694
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2694
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Conformance, General
>    Affects Versions: ODF 1.2 Part 3 CD 2, ODF 1.2 Part 1 CD 5, ODF 1.2 Part 2 CD 3
>         Environment: This issue applies to the restructured parts 1-2-3 and the overview that are balloted for approval as a Committee Draft(s) for Public Review: OpenDocument-v1.2-draft3.odt, OpenDocument-v1.2-part1-cd04-rev08.odt, OpenDocument-v1.2-part2-cd02-rev08.odt, and OpenDocument-v1.2-part3-cd01-rev07.odt.
>            Reporter: Dennis Hamilton
>            Priority: Blocker
>             Fix For: ODF 1.2
>
>
> 1. This new packaging breaks the modularity by which part2 and part3 are independently usable and relatively self-contained.  
>     1.1 The removal of conformance sections from all parts, with the only conformance section being in the OpenDocument-v1.2-draft3.odt causes these parts to be inextricably intertwined.  This strikes me as a question of substance that requires discussion.
>     1.2 This organization also creates unnecessary duplication and burdens readers with the need to consult multiple documents for no useful purpose.
>     1.3 The additional complexity of maintenance of the specifications, potential errata and defect-reconciliation efforts, and the prospect of inconsistency between the parts seems unjustifiable.  (There are already inconsistencies between the new 1.2-draft3 and provisions referenced in the other parts of the specification.)
>  2. It also seems excessive that OpenDocument-v1.2-draft3.odt consists of 
>   * 93 pages of front matter, including duplication of the tables of contents of parts 1-3, 
>    * 3 pages of back matter, and 
>    * only three pages having modest narrative content and creating a list of conformance clauses that makes it indispensible to the other parts.
>  3. Finally, I think this approach is an unwarranted imposition on the time and efforts of those who we wish to embrace this specification, invest in its review, and engage in implementation, testing, and verification of products that support OpenDocument.
> [Note: I am concerned that attempting to remedy this as part of a re-issue in a 15-day secondary public review would be too dificult.  After examining the material and the new sections 2 of Parts 1-3, I am satisfied that correction by elimination of v1.2-draft3 is workable.]

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