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

 


Help: OASIS Mailing Lists Help | MarkMail Help

odf-adoption message

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


Subject: Moving ahead with the ODF Implementation, Interoperability and Conformance(IIC) TC



I'd like to move forward on the idea for the new TC dedicated to ODF interop.  The OASIS rules allow us to start off with a new discussion list where prospective members can take up to 90 days to hash out a consensus charter.  To get this first step started, we need 4 things, as defined in the TC policy here:  http://www.oasis-open.org/committees/process.php#formation

The core requirement is a preliminary "statement of scope", and the names of three or more OASIS members as co-proposers.

Here's my attempt at answering these questions.  Please suggest changes.  If you are willing to add your name, please do.  Note that the "statement of scope" does not need to be perfect at this point.  That's the purpose of the new discussion list, to broaden the discussion with more more participants and try to reach a consensus on the scope and other elements of the TC charter.  Of course, if there is something that is clearly wrong or missing, then let's fix it now.

Here are the four questions and my proposed answers:

(1) The name of the discussion list, which shall not be the same as the name of the list in which the TC itself shall operate if formed.

The proposed discussed list name is "odf-iic-formation".

(2) A preliminary statement of scope for the TC whose formation the list is intended to discuss.

It is the intent of the ODF IIC TC to provide a means for software vendors to create applications which adhere to the ODF specification and are able to interoperate. As such, the purpose of the IIC TC includes the following:

  1. To publish test suites of ODF for applications of ODF to check their conformance with the Standard and to confirm their interoperability;
  2. To provide feedback, where necessary, to the ODF TC on ways in which the standard could improve interoperability;
  3. To produce a set of reference implementation guidelines;
  4. To define interoperability with related markup standards by the creation of profiles or technical reports;
  5. To help coordinate OASIS InterOp demos related to ODF;
 
The IIC TC may also liaise with other standard bodies whose work is leveraged in present or future ODF specifications. These include, but are not limited to, the W3C and ISO/IEC JTC1/SC34.

(3) The names, electronic mail addresses, and OASIS Organizational or Individual Membership affiliations of the three or more Eligible Persons proposing to create the discussion list.

Rob Weir, robert_weir@us.ibm.com, IBM

XXXXXX

XXXXXX

XXXXXX

XXXXXX

(4) The name of the discussion list leader.

Rob Weir



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