Fwd: OpenDocument submission package draft

[Mary McRae <marypmcrae@gmail.com>]

Hello Michael and OpenDocument TC members:

Below is the text of the draft submission to JTC1. This is an
incomplete, internal draft, and we need everyone to review it and
provide any feedback by Thursday (1 Sept) 10am EDT. At that point
Jamie, Patrick Gannon and myself will combine edits and make the final
submission.

Please provide feedback to this list and cc: mary.mcrae@oasis-open.org

Thank you!

Regards,

Mary




====
DRAFT Explanatory Report

     The Organization for the Advancement of Structured Information
Standards (OASIS) respectfully submits the following OASIS Standard to
ISO/IEC Joint Technical Committee 1, for transposition into an
International Standard under the procedures defined in the current
revision of JTC 1 N 3583 ("The Transposition of Public Available
Specifications into International Standards - A Management Guide"):

     Open Document Format for Office Applications v1.0 Specification
(short name: "OpenDocument v1.0")

The relevant documentation is enclosed (in a ZIP file) with this
communication.  OpenDocument v1.0 is a Publicly Available
Specification under JTC1 rules. OASIS is a Recognized PAS Submitter
under JTC1 rules, having been approved by JTC1 national bodies by
letter ballot (N7458) closed 28 September 28th, and having been
reaffirmed (extended) without revision by the JTC1 chairman on 17 June
2005.

     The OpenDocument specification defines an XML schema for office
applications and its semantics. The schema is suitable for office
documents, including text documents, spreadsheets, charts and
graphical documents like drawings or presentations, but is not
restricted to these kinds of documents.

     The schema provides for high-level information suitable for editing
documents. It defines suitable XML structures for office documents and
is friendly to transformations using XSLT or similar XML-based tools.
OpenDocument was originally based on the open source
community-developed OpenOffice.org XML file format.

     Copies of the relevant notices of approval and public review are
enclosed with this communication, as is the normative copy of the
approved OASIS standard specification.  The OpenDocument v1.0
specification submitted here also is available in two formats at the
following publicly accessible locations:

PDF format at

http://www.oasis-open.org/committees/download.php/12027/office-spec-1.0-cd-3.pdf

OpenOffice.org XML format at

http://www.oasis-open.org/committees/download.php/12028/office-spec-1.0-cd-3.sxw


Specifically, with attention to the JTC1 PAS criteria:

- Cooperative stance (7.3.1),

OASIS as a consortium interoperates and liaises,broadly and
productively, with international de jure standards organizations and
many relevant industry consortia of various types, including formal
working relationships with:
  - ISO, IEC, ITU, UN-ECE MoU for E-Business
  - ISO/IEC JTC1 SC34, ISO TC154 (Cat. A Liaison)
  - ITU-T A.4 and A.5 Recognition
  - IPTC, LISA, SWIFT, UPU, ABA, ACORD, HL7, HR-XML, ISM, MBAA, NASPO,
NIGP, VCA, European ICTSB, CEN/ISSS, EC SEEM, PISCES, LRC, Asia PKI,
CNNIC, EA-ECA, ECIF, KIEC, PSLX, Standards-AU, BPMI, CommerceNet, GGF,
IDEAlliance, OAGi, OGC, OMA, OMG, RosettaNet/UCC, W3C, WfMC, WSCC and
WS-I

OASIS enters into working agreements (as contemplated by JTC1
criteria) with each organization to which it submits OASIS Standards,
pursuant to our Liaison Policy [41.  [The proposed form of agreement
is attached as exhibit ___.]  OASIS and its OpenDocument technical
committee plans to conduct the ongoing maintenance of the submitted
specification, and its current members have indicated that they are
prepared to remain involved in order to support this effort.  OASIS
expects that the submitted document will be adopted and transposed in
substantially the same form as submitted, and would (in the above
agreement) request that any change or improvement proposals would be
cycled back through an OASIS technical committee for
inclusion in a future v2.0 document, which would be developed by OASIS
and then could be re-transposed by JTC1 after OASIS approval.

[1] http://www.oasis-open.org/committees/liaison_policy.php

- Characteristics of the Organization (7.3.2)

OASIS is a member-led, international non-profit standards consortium,
incorporated as a non-for-profit corporation under [Pennsylvania] law,
concentrating on structured information and global e-business
standards, and organized in 1993. As of 2004, approximately 50% of the
over 650 members are technology providers, 35% are technology users
and influencers, and 15% are government and academic entities. OASIS
is one of the largest and most widely recognized open standards
consortia developing XML and e-business data specifications.  All
organizational members of OASIS may vote on OASIS standards (and on
governance issues such as election of the
Board of Directors), and any member (including individuals) may join a
technical committee as a voting member.

- Intellectual Property Rights (7.3.3)

The OASIS IPR policy imposes a clear set of disclosure and
license-notification procedures, somewhat similar to ISO rules, that
ensures predictable detection and resolution of claims from
contributors to OASIS work.  See link [4] below.  OASIS is willing in
its submission to comply with the ISO/IEC patent policy.
OASIS holds a copyright in the submitted specification.  Under the
terms of its liaison policy (link [1] above), OASIS will either permit
its copyright notice to be retained on an JTC1 print of the transposed
work, or to have only the ISO/IEC copyright appear so long as OASIS'
retention of its independent copyright is properly memorialized in the
working agreement referenced above.

- Completeness (7.4.1.1) and Stability (7.4.1.4),

The submitted specification is a final approved version, after over __
months of continuous development, and is perpetually available under
OASIS rules.  The OpenDocument technical committee proposes to stay in
place to collect errata, implementation experience and possible
feedback towards future improvements.  The OASIS standard approval
process requires that multiple OASIS members publicly acknowledge
successful implementation of the specification;  in this case that
acknowledgement as provided by:

          Sun Microsystems
http://lists.oasis-open.org/archives/office/200502/msg00015.html

          Stellent
http://lists.oasis-open.org/archives/office/200503/msg00012.html

          Novell
http://lists.oasis-open.org/archives/office/200503/msg00017.html

          IBM
http://lists.oasis-open.org/archives/office/200503/msg00020.html

as evidenced by the enclosed notices.


- Availability (7.4.1.5)

Under the OASIS policies references above, users are unqualifiedly
permitted to implement the submitted OASIS Standard without requiring
license or permission from OASIS.  Distribution of the specification
is unlimited


- Consensus (7.4.2),

     OpenDocument v1.0 was developed by the OASIS Open Document Format
for Office Application Technical Committee [2] and approved by that
committee and the OASIS membership under the OASIS TC Process [3] and
OASIS IPR Policy [4] as in force during the pendency of the work.

[2] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
[3] http://www.oasis-open.org/committees/process_2003.09.18.php
[4] http://www.oasis-open.org/who/ipr/intellectual_property_2000-1-13.php

    The above rules, as previously confirmed during JTC1's examination
of OASIS' PAS application, assure transparent public feedback and
broad quality review under a consensual process, a declared and clear
regime for the resolution of any intellectual property rights claims
(although none have been asserted against this work).  Other OASIS
Standards developed and approved under the same rules and methods have
been submitted and approved by, for example, ISO (in the case of four
OASIS Standards for ebXML approves bt ISO TC 154 as the ISO TS 15000
series. These OASIS policies require public transparency of comments
to a proposed standard and acknowledgment of their resolution.  The
development and approval of this specification complied with those
requirements, as evidenced by the enclosed notices.

- Alignment (7.4.3)

     As a broadly useful set of formats for the output of general office
application software, the submitted specification is susceptible of and
designed for extremely wide-spread use cases.  OpenDocument v1.0 makes
use of the following standards, either by direct inclusion, or by
adopting some of their concepts, elements and attribute names, or
semantics:

           Dublin Core Metadata Element Set
           W3C (X)HTML
           W3C MathML
           W3C SMIL
           W3C SVG
           W3C XLink
           W3C XForms
           W3C XSL FO

     While all these standards cover some aspects of documents created
by office applications, none of these standards covers all aspects of
such documents, or could be extended to cover all these aspects.

     As noted above, OPASIS expects its technical committee to remain
active and drive growth of the specification, bringing future major
versions back to JTC1 at an appropriate stage of stability.

     As described in the attached form of working agreement, OASIS is
willing to have the submitted specification re-formatted into JTC1
documents styles as necessary to achieve appropriate transposition.

opendoc-jtc1-submit.zip

office-spec-1.0-cd-3.zip