At 2007-02-24 21:58 +0900, MURATA Makoto wrote:
>All differences are caused by two things:
>
>Q1: Is OASIS a "JTC 1 designated maintenance group of the submitter
>in accordance with JTC 1 rules" as shown in 14.4.3.14 of the direcrives?
The JTC 1 version of the submission of the DIS text, the one that was
voted on by JTC 1 membership (not by SC34 membership), has the
explanatory report copied below. This is text excerpted from the
circulated DIS 26300 voting document dated 2005-11-01 with voting
ending 2006-05-01. It would be the actual document your national
body's JTC 1 committee received and voted on. I've copied and pasted
the text of the explanatory report without any edits.
I understand this negotiation was done between JTC 1 and
OASIS. Certainly as SC34 Secretariat I did not see any of this until
it was a done deal. We don't see the comments on the material until
the end of the ballot period.
>Q2: If the answer to Q1 is positive, what does "Its maintenance will
>be handled either by JTC 1 or by JTC 1 designated maintenance group of
>the PAS Submitter in accordance with JTC 1 rules." mean?
>
>You appear to belive that the answer to Q1 is Yes. I do not know when
>and how the decision was made. (Had I new this, I would have tried to
>make Japan vote No to ODF.) Clause 14.4.3.14 clearly says that "Its
>maintenance will be handled either the PAS Submitter in accordance with
>JTC 1 rules." Why is the maintenance not handled by JTC1? I have seen
>no justifications yet.
SC34 is not entitled to demand justification. This was negotiated
between JTC 1 and OASIS.
>Q2 is even more debatable. Does this sentence mean that OASIS will
>create a defect report, draft technical corrigendum, and technical
>corrigendum, as shown in 8.1.5 of the directives? Or, does it mean that
>OASIS can do whatever they would like to do? For example, OASIS
>might want to
>incorporate changes only to future versions of ODF, without revising
>ODF 1.0 of OASIS or ODF 1.0 of ISO/IEC.
OASIS proposed maintenance in the explanatory report attached to its
submission to JTC 1 which was balloted by JTC 1 P-members and accepted.
>Here is the reason that I care so much. Harmonization of ODF and OOXML
>is an important issue.
I am unaware that such harmonization is a current project.
>As I see it, neither OASIS nor ECMA is the right
>place for such harmonization. If SC34 is not even allowed to create
>technical corrigenda, they certainly cannot create addenda to ODF or
>OOXML. Thus, SC34 will become a lame duck, the only thing it can do
>is to say "Yes" or "No" to ODF or OOXML. No attempts for the
>harmonization will happen anywhere in the world.
Again, and I think I'm repeating myself here, the arrangement is
between the submitter and JTC 1. SC34 had no say in the matter. Why
is this subject taking up so much SC34 time when it is a done deal
between JTC 1 and OASIS? The time to have brought this up was when
P-members voted at the JTC 1 level. It is my opinion that now is not
the time to change things. If I am going to be asked to request
changes of JTC 1, then I'm going to need clear direction from *all*
of SC34 to do so, as requesting such changes and reopening already
established agreements is not a trivial matter.
I do not believe I'm raising anything new here ... SC34 is
responsible to JTC 1, JTC 1 negotiates PAS and Fast Track
submissions, JTC 1 then leaves it to the responsible SC to handle
ballot resolution. In the case of ODF JTC 1 has negotiated that
OASIS handle maintenance.
What more has to be said here?
. . . . . . . . . . . . . Ken
EXPLANATORY REPORT
OASIS Submission of OpenDocument v1.0 to ISO/IEC JTC1
This report is provided in Portable Document Format (.PDF), OpenOffice (.SXW)
and HTML (.HTM) formats
OASIS (the Organization for the Advancement of Structured Information
Standards) 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 2004, 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/12572/OpenDocument-v1.0-
os.pdf]
OpenOffice.org XML format at
[http://www.oasis-open.org/committees/download.php/12573/OpenDocument-v1.0-
os.sxw]
Exemplar XML schemas that implement the specification can be found at:
[http://www.oasis-open.org/committees/download.php/12571/OpenDocumentschema-
v1.0-os.rng]
[http://www.oasis-open.org/committees/download.php/12570/OpenDocumentmanifest-
schema-v1.0-os.rng]
[http://www.oasis-open.org/committees/download.php/12569/OpenDocumentstrict-
schema-v1.0-os.rng]
P.A.S. CRITERIA
OASIS and its OpenDocument TC are pleased to offer the following additional
observations relevant 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, and has 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
- SWIFT, ABA, ACORD, AIAG, Asia PKI, BPMI, CEN/ISSS, CNNIC, CommerceNet, EAECA,
ECIF, GGF, GS1-US/RosettaNet, HL7, HR-XML, ICTSB (Europe), IDEAlliance,
IPTC, ISM, KIEC, LISA, LRC, MBAA, NASPO, NIGP, OAGi, OGC, OMA, OMG, PISCES,
PSLX, UPU, VCA, 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 [1]. The proposed form of submission terms applicable to this submission
is attached as exhibit A and complies with the criteria in Section 7.3.1.1 of
JTC1's document N5746. OASIS and its OpenDocument Technical Committee plan 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.
[1] http://www.oasis-open.org/committees/liaison_policy.php
OASIS expects that the submitted document will be adopted and transposed with
substantially the same content as submitted. OASIS requests that any change or
improvement proposals be cycled back through an OASIS technical committee for
inclusion in errata (if the correction of a defect) or a future v2.0
version (if
in the nature of amendment or revision), to be developed by OASIS. If future
major versions (substantive changes) are advisable, OASIS expects to seek to
offer them for re-transposition by JTC1, after OASIS approval under its usual
rules, as it is an OASIS policy goal to ensure convergence and avoid "forked"
specifications. (The typical, but not mandated, period of time for progression
of a new substantive version through the OASIS process is 8 to 24 months.)
Other OASIS Standards developed and approved under the same rules and methods
have been submitted and approved by, for example, ISO, where four OASIS
Standards for ebXML were approved by ISO TC 154 as ISO TS 15000-1
through 15000-
4. The approach proposed here for OpenDocument v1.0 essentially is the same
used successfully for ISO 15000.
OASIS technical committees continue to actively produce XML-based
specifications
that may, over time, provide additional opportunities for convergence, or
feature expansion of this work, towards related domains of activity. OASIS
additionally maintains close working relationships with a number of other
prolific sources of standardized methodologies for localization,
transformation,
presentation, graphics, semantics and XML operation. By liaison or re-use these
sources may also provide additional functional opportunities, over time as
technologies grow, for augmentation of OpenDocument methods. However, as noted
below, v1.0 represents a stable, reliable and complete feature set.
- Characteristics of the Organization (7.3.2)
OASIS is a member-led, international standards consortium, incorporated as a
501(c)6 not-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. As verified during our PAS submitter recognition process, 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 Associate and Individual
members) 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 knows of no claimed patent rights in the submitted specification.
OASIS holds a copyright in the submitted specification. Under the terms of its
liaison policy (link [1] above), OASIS will agree either (a) to have its
copyright notice and associated disclaimers retained on a JTC1 print of the
transposed work, or (b) to have only the ISO/IEC copyright notice appear, so
long as OASIS' retention of its independent copyright is properly memorialized
in the working agreement referenced above. OASIS has no objection to joint or
dual distribution of the transposed standard.
OASIS holds a trademark in its name, but otherwise knows of no
claimed trademark
rights in the normative elements of the submitted specification. OASIS will
grant such permission to refer to its name, if any, as might be necessary for
joint or dual distribution of the transposed standard.
Under the OASIS IPR Policy referenced above, all contributions provided by
members into its technical committees are made with the assurance that they are
freely available for incorporation, derivation and republication into the
committee's output.
- Quality: Completeness (7.4.1.1) and Stability (7.4.1.4)
The submitted specification is a final approved version, after over
32 months of
continuous development and successive drafts demonstrating careful convergence
on a stable set of methods. The specification is perpetually available under
OASIS rules. All necessary elements are specified, and exemplar XML excerpts
are supplied for each instance. Each of these elements may be consumed by any
device that handles XML; it is our expert panel's expectation that this will
result in use of the specification as an exchange format among a broad range of
devices and products.
Also, the OASIS standard approval process requires that multiple OASIS members
publicly acknowledge successful implementation of the specification; in this
case that acknowledgement is 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. These notices applied specifically to the
stable version that was finally approved as an OASIS Standard and is submitted
here.
Our participating member experts have verified that the current v1.0 represents
a stable, reliable and complete feature set, with robust utility. Strong
positive user reactions from multiple public and private domains support this
assessment. The OASIS OpenDocument Technical Committee proposes to stay in
place to perform maintenance, and collect errata, implementation
experience, and
possible feedback towards future improvements.
- Quality: Clarity (7.4.1.2) and Testability (7.4.1.3)
The OpenDocument specification provides over 700 pages of textual description,
explanation and examples. The specification includes unambiguous and detailed
criteria for conformance to the various office document artifact types that can
be created in conformance with its structure and methodology. As a practical
matter, in this context, "conformance" is most likely to arise in the sense of
compliant documents successfully being authored, exchanged, read and revised
among multiple parties, using different compliant client software, without
alteration or misinterpretation of the content and presentation. These are
readily testable functions.
- Quality: Availability (7.4.1.5)
Under the OASIS IPR Policy referenced above, users are unqualifiedly permitted
to implement the submitted OASIS Standard without requiring license, permission
or royalty from OASIS; other parties with claims are permitted to assert those
claims and make any license terms known. No claims requiring a license,
permission or royalty have been made. Distribution of the specification is
unlimited. The progressive versions of the specification have been publicly
available from OASIS's internet portals since the project's inception.
- Consensus (7.4.2)
OpenDocument v1.0 was developed by the OASIS Open Document Format for Office
Application Technical Committee [2]. It was approved by that committee, and
then approved by 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; broad quality review under
a consensual process; and a declared and clear regime for the resolution of any
intellectual property rights claims (although none have been asserted against
this work). These OASIS policies require public transparency of comments to a
proposed standard and acknowledgment of their resolution. As a result, the
course of development in OASIS technical committees always is porous to inpur
from the needs of user communities. The development and approval of this
specification complied with our open process methods and requirements, as
evidenced by the enclosed notices. The successful use statements referenced
above from OASIS member software implementers, and the acute and growing
interest in openly-available document formats from public sector governmental
users, often explicitly citing this specification, evidence strong external
demand for the work.
- Alignment (7.4.3)
As a broadly useful set of formats for the output of general office
application software, the submitted specification is designed for extremely
wide-spread use cases. OpenDocument v1.0 makes use of many widely-used open
specifications, either by complete inclusion or by re-use of relevant concepts,
elements, attribute names and semantics, including the following:
Dublin Core Metadata Element Set
IETF RFC 2048 (MIMEtypes)
ISO 639 Language Codes
ISO 3166 Country Codes
ISO/IEC 10646 (UNICODE)
ISO/IEC 19757-2 (OASIS RELAX NG)
W3C HTML
W3C MathML
W3C SVG
W3C XForms
W3C XML
While all of these specifications cover some aspects of documents created by
office applications, none of them covers all aspects of such
documents, or could
be extended to cover all these aspects. The work is not duplicative of other
standards: we are aware of no other openly-available, vendor-neutral XML
representation method for office documents as a class.
As noted above, OASIS expects its technical committee to remain active and
drive growth of the specification, bringing future major versions back to JTC1
at an appropriate stage ofstability. As described in the attached terms, OASIS
is willing to have the submitted specification re-formatted into JTC1 document
styles as necessary to achieve appropriate transposition.
STRATEGIC CHARACTERISTICS
The proposed transposition also meets the higher-level strategic goals of
JTC1 represented by the Common Strategic Characteristics defined for JTC1's
Technical Directions: interoperability, portability, and cultural and
linguistic
adaptability.
- Interoperability
Office applications, as a class, are among the most prolific generators of
electronic artifacts. Through their widespread use, a great deal of the
knowledge of enterprises and individuals is embedded into electronic file form,
as "documents", "spreadsheets", "presentations" and the like. By employing
standards-based XML methods as its base representations, the OpenDocument v1.0
specification permits and encourages that knowledge to be widely interoperable
with the many other automated systems that consume XML. The design choice
encourages interoperability and information sharing, by exposing the expressed
information to a broad and increasing body of devices and information methods.
- Portability
OpenDocument v1.0 is a standardized, widely available and freely useable
expression method for the many kinds of information noted above, and as such is
available as a vendor-neutral, device-neutral and language-neutral format for
exchange across implementations.
- Cultural and linguistic adaptability
OpenDocument v1.0 uses adaptable and multi-lingual representational logic to
express and consume character set, enumeration, calendar and similar data, and
permits additional extensibility if needed, thus permitting universal utility
across languages and global user communities.
END OF BODY
APPENDIX A
PROPOSED TERMS OF TRANSPOSITION AND MAINTENANCE
OASIS expects that the submitted document will be adopted and transposed in
substantially the same form as submitted. OASIS grants permission to JTC1 to
cause the submitted textual specification to be re-formatted into JTC1 document
styles as necessary to achieve appropriate transposition. OASIS as Submitter
requests that the specification remain otherwise unchanged throughout the
transposition process.
OASIS retains its independent copyright in the submitted specification and any
related OASIS materials, and may contribute to distribute them freely as has
heretofore been the case. Subject to the foregoing, OASIS grants permission to
JTC1 either (a) to have the OASIS copyright notice retained on a JTC1 print of
the transposed work, or (b) to have only the ISO/IEC copyright notice appear.
OASIS has no objection to dual distribution of the standard, and at JTC1's
option also would be pleased to cooperate in the creation of a
jointly-published
single document.
OASIS and its OpenDocument Technical Committee plans to conduct the ongoing
maintenance of the submitted specification, including the collection and
promulgation of errata, implementation experience and possible feedback towards
future improvements. OASIS requests that any corrections of defects or errata
from the JTC1 process be re-presented to the OASIS Technical Committee, for
handling and correction, which the Technical Committee will be pleased to
publish in a manner coordinated with JTC1. OASIS requests that any change or
improvement proposals from the JTC1 process be re-presented to the OASIS
Technical Committee, for inclusion in a future major revision. The OASIS
OpenDocument Technical Committee proposes to remain active and drive growth of
the specification, and to bring any future major versions back to
JTC1 for retransposition
at an appropriate stage of stability.
END OF APPENDIX
END OF EXPLANATORY REPORT
-- G. Ken Holman Crane Softwrights Ltd. ISO/IEC JTC 1/SC 34 Secretariat Standards Council of Canada Committee correspondence: mailto:jtc1sc34@scc.ca Committee website: http://www.jtc1sc34.org Corporate correspondence: mailto:gkholman@CraneSoftwrights.com Corporate website: http://www.CraneSoftwrights.com/a/ -- DSDL members discussion list To unsubscribe, please send a message with the command "unsubscribe" to dsdl-discuss-request@dsdl.org (mailto:dsdl-discuss-request@dsdl.org?Subject=unsubscribe)Received on Sun Feb 25 00:46:29 2007
This archive was generated by hypermail 2.1.8 : Sun Feb 25 2007 - 05:13:02 UTC