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] Re-focusing on the proposed Charter

Thanks for clarifying Rob - based on your suggestions I have populated the wiki as follows, with the charter document at the top level and separate pages for each sub-section/topic (note the comments form at the bottom of each).

This is world readable now and writeable by anyone with an accout, which you can get by filling out the form I sent earlier and/or harassing me.

On Mon, Jun 9, 2008 at 10:03 PM, <robert_weir@us.ibm.com> wrote:

Sorry, I've been otherwise engaged today.  I'll need to go back and read the traffic from today, but it looks like we may be prematurely solving the interoperability problem, when we really need to first agree on a charter and then form a TC.

Believe me, once we have a TC in place for this, we'll have an OASIS-hosted Wiki.  We'll also have mailing lists, action items trackers, document libraries, etc.  We'll have the ability to create subcommittees.  We'll have conference calls, face-to-face meetings if we want, etc.  We'll have all that infrastructure stuff available.  But the way the OASIS infrastructure is set up, this is all tied to TC membership, and until we have a TC, we can't tap into all that.

I've seen some documents float around that seemed more in the nature of a draft of one of the TC's deliverables, such as a draft or outline of a conformity assessment document.  That isn't a bad thing per se, but it is more in the nature of a possible contribution to this TC, once created.

If we focus on the charter task, we first note the requirements detailed in OASIS TC Process section 2.2 (http://www.oasis-open.org/committees/process.php#formation).  This calls for the submission of a proposed TC charter which can include _only_ the following items:

(1)(a) The name of the TC, such name not to have been previously used for an OASIS TC and not to include any trademarks or service marks not owned by OASIS. The proposed TC name is subject to TC Administrator approval and may not include any misleading or inappropriate names. The proposed name must specify any acronyms or abbreviations of the name that shall be used to refer to the TC.

(1)(b) A statement of purpose, including a definition of the problem to be solved.

(1)(c) The scope of the work of the TC, which must be germane to the mission of OASIS, and which includes a definition of what is and what is not the work of the TC, and how it can be determined when the work of the TC has been completed. The scope may reference a specific contribution of existing work as a starting point, but other contributions may be made by TC Members on or after the first meeting of the TC. Such other contributions shall be considered by the TC Members on an equal basis to improve the original starting point contribution.

(1)(d) A list of deliverables, with projected completion dates.

(1)(e) Specification of the IPR Mode under which the TC will operate.

(1)(f) The anticipated audience or users of the work.

(1)(g) The language in which the TC shall conduct business.

(2) Non-normative information regarding the startup of the TC, which includes:

(2)(a) Identification of similar or applicable work that is being done in other OASIS TCs or by other organizations, why there is a need for another effort in this area and how this proposed TC will be different, and what level of liaison will be pursued with these other organizations.

(2)(b) The date, time, and location of the first meeting, whether it will be held in person or by telephone, and who will sponsor this first meeting. The first meeting of a TC shall occur no less than 30 days after the announcement of its formation in the case of a meeting held exclusively by telephone or other electronic means, and no less than 45 days after the announcement of its formation in the case of a meeting held face-to-face (whether or not a telephone bridge is also available).

(2)(c) The projected on-going meeting schedule for the year following the formation of the TC, or until the projected date of the final deliverable, whichever comes first, and who will be expected to sponsor these meetings.

(2)(d) The names, electronic mail addresses, and membership affiliations of at least Minimum Membership who support this proposal and are committed to the Charter and projected meeting schedule.

(2)(e) The name of the Convener who must be an Eligible Person.

(2)(f) The name of the Member Section with which the TC intends to affiliate, if any.

(2)(g) Optionally, a list of contributions of existing technical work that the proposers anticipate will be made to this TC.

(2)(h) Optionally, a draft Frequently Asked Questions (FAQ) document regarding the planned scope of the TC, for posting on the TC's website.

(2)(i) Optionally, a proposed working title and acronym for the specification(s) to be developed by the TC.

On the scope question, the OASIS members (including me) who proposed this discussion list also proposed a scope statement, which was included in the original Call for Participation that went out last week:  http://lists.oasis-open.org/archives/tc-announce/200806/msg00003.html

There are around 20 individual questions listed above that we can address in our Charter.  Some of them are probably uncontroversial, like what language to conduct the TC in, while others like the scope, might garner more discussion.  Unless there are objections from OASIS staff, I think a Wiki or other collaborative document editing environment would help us work out the answers to the above questions.  But let's try to keep the discussions here on this list.




Rob Weir
Software Architect
Workplace, Portal and Collaboration Software
IBM Software Group

email: robert_weir@us.ibm.com
phone: 1-978-399-7122

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