OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oiic-formation-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [oiic-formation-discuss] Draft Interoperability and Conformance TC formation proposal (0.2)

2008/7/24  <robert_weir@us.ibm.com>:
> As promised, here is a draft of a charter for a proposed new OASIS TC.
> I've based this version on input from this list, in particular from Dave
> Pawson's draft, as well as from conversations with other parties off this
> list.

Duly noted.

  I have been shopping this draft around, attempting to get views and
> comments from a variety of possible participants, and not exclusively from
> this list.

Pity you're not more of a team player Rob.

> It is fair to let you know that I intend to move this forward into a formal
> proposal for a new TC soon, well before the 90 day period of the discussion
> list has expired.

IOW you really didn't need the input from this group at all?

Others please note. Rob has no need of consensus from this group
according to the (lack of ) Oasis process for TC formation.

> TC formation proposal.
> 1a. Name:  OASIS OpenDocument Format Interoperability and Conformance
> Technical Committee (OIC TC)

> 1b. Statement of Purpose
> The OpenDocument Format for Office Applications (OpenDocument) OASIS
> Standard 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.

Unnecessary. Delete.

> There are several commercial and open source applications available based on
> the OpenDocument Format, with more currently under development.  With the
> depth and breadth of functionality specified by ODF, achieving conformance
> and interoperability requires attention to numerous details and diverse
> requirements.

Not a statement of purpose.

> It is the purpose of the OIC TC to produce materials and host events that
> will help implementors create applications which conform the ODF standard
> and which are able to interoperate.

Is IBM hosting these events? Never mentioned on this list.

> 1c. Scope of Work
> In accordance with the OIC TC's purpose, the scope of our work will include
> the following activities:
> Initially and periodically thereafter, to review the current state of
> conformance and interoperability among ODF implementations, and to produce a
> an impartial report that notes areas of accomplishment as well as areas
> needing improvement, and which recommends prioritized activities for
> advancing the state of conformance and interoperability among ODF
> implementations;

Is this a scoping statement?

> To collect the provisions of the ODF standard, and of standards normatively
> referenced by the ODF standard, and to produce a comprehensive conformity
> assessment methodology specification which enumerates all collected
> provisions, as well as specific actions recommended to test each provision,
> including definition of preconditions, expected results, scoring and
> reporting;

A very unclear task. Not scope. Inappropriate in this section.

> To select a corpus of ODF interoperability test documents, such documents to
> be created the OIC TC, or received as member or public contributions;  To
> publish the ODF interoperability test corpus and promote its use in
> interoperability workshops and similar events;

An activity, not a scoping statement.

> To define profiles of ODF which will increase interoperability among
> implementations in the same vertical domain, for example, ODF/A for
> archiving;

An activity, not a scoping statement.
How might a profile (undefined) increase interop?

> To define profiles of ODF which will increase interoperability among
> implementations in the same horizontal domain, for example ODF Mobile for
> pervasive devices, or ODF Web for browser-based editors.

An activity, not a scoping statement.

> To provide feedback, where necessary, to the ODF TC on changes to ODF that
> might improve interoperability;

At last! But still an activity, not a scoping statement.

> To coordinate, in conjunction with the ODF Adoption TC, Interop Workshops
> and OASIS InterOp demos related to ODF;

This from the man who said we shouldn't be writing software. U turn Rob.

Reminder. Scope. The sphere or area over which any activity operates
or is effective; range of application or of subjects embraced; the
reach or tendency of an argument, etc.; the field covered by a branch
of knowledge, an inquiry, concept, etc.

> To liaise on conformance and interoperability topics with other TC's and
> bodies whose work is leveraged in present or future ODF specifications, and
> with committees dealing with conformance and interoperability in general.

An activity. Fresh from the mind of RW?

> The following activities are explicitly not within the Scope of the OIC TC:
> Acting as a rating or certifying authority or agency for conformance of ODF
> implementations;
> Authoring or distributing software that tests the conformance or
> interoperability of ODF implementations;

Despite providing demonstrations? With vapourware perhaps?

> 1d. List of Deliverables
> Initial report on the state of ODF conformance and interoperability (March
> 1st, 2009);
> Report on the best practices on profiles and recommendations on possible
> ODF-related profiles (April 1st, 2009);

I wouldn't take you on for project estimating Rob.

> A conformity assessment methodology specification, detailing how each
> provision and recommendation in the ODF standard may be tested for
> conformance (May 1st, 2009);

Like the spec itself, note the 'may'

> Interoperability test corpus documents,  released in batches, according to
> functional area (several incremental deliverables, Q4 2008 through 2009)

No definition of " Interoperability test corpus documents,"? Who'se supposed
to translate this?

> 1e. IPR Mode
> This TC will operate under the "RF on Limited Terms" mode
> 1f. Audience
> The direct audience of the OIC TC's work will be:
> Implementors -- Commercial and Open Source publishers of ODF native or
> compatible applications and tools.
> Testers -- Third-party testing and certification labs.
> Procurers -- Those who purchase or define requirements for the purchase of
> ODF-related technology.
> Regulators -- Officials who specify the use of document standards.
> Other, indirect users of the TC's work may include:
> Integrators -- Third-party developers and independent software vendors who
> interact with and/or integrate ODF.
> Users -- End Users of ODF applications and tools, including both typical and
> "power" users.
> 1g. Language of the TC
> TC business will be conducted in English.
> 2. Informative information
> 2a. Similar work
> We note the work of Lotzi Bölöni at the University of Central Florida and
> his initial work in defining an ODF "test suite", work now maintained by the
> Open Document Fellowship:
> http://develop.opendocumentfellowship.com/testsuite/
> We also note that the work of the OASIS Test Assertions Guidelines (TAG) TC
> may be of use to us in defining test cases:
> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tag
> Sun Microsystems has has also done some work related to ODF conformance
> testing:
> http://blogs.sun.com/GullFOSS/entry/openoffice_org_odf_validation_service
> We note that the W3C has test suite work efforts pertaining so several of
> the standards which ODF references, including MathML and XForms.  We would
> expect to consult with them on any overlapping topics.
> Finally we observe that the OASIS ODF TC owns the ODF standard, including
> the definition of conformance for ODF.   The OIC TC's work does not overlap,
> since our scope would not including defining conformance for ODF

Pardon. Go read the proposed TC title?
Moving towards farce Rob.

" we observe that "... Which 'we' Rob? You and your employers?
Certainly not the group of people on this list.

, but
> defining test cases (preconditions, specific test actions, expected results)
> that are traceable to the provisions of the ODF standard and referenced
> standards.

Your confusion is showing Rob - how is this not a compliance test?

> 2b. First meeting.
> The initial meeting will be by telephone and will be hosted by IBM.
> [Date to be determined, likely late September/early October, 2008 .  Must be
> no less than 30 days after TC is formed]
> 2c. Meeting schedule
> We anticipate meeting, by teleconference, initially every week as we prepare
> for an interoperability workshop in November, and then reverting to a normal
> alternate week meeting schedule
> 2d. Minimum membership who support this proposal.
> 1. Robert Weir / IBM
> [TBD.  We will need 5 OASIS members, from at least 3 member organizations]
> 2e. Convener
>    Robert Weir/ IBM
> 2f. Member section affiliation. None
> 2g. (optional) Contributions.
> [Is there any work that will be contributed initially?  That's fine if there
> is none.  Members or the public can contribute at any time.]
> 2h (optional) FAQ's:  N/A
> 2i  (optional) Working titles and acronyms for specifications:  None.

From the top of Robs post

" I've based this version on input from this list, in particular from
Dave  Pawson's draft,"

Factually incorrect.

Good luck Rob.

Dave Pawson

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]