RE: Submission of Proposal for new TC formation

["Mary McRae" <mary.mcrae@oasis-open.org>]

Hi Kathryn,

  Glad to see this is moving along! A few bits are missing as noted below. It
should be fairly straightforward to rectify these deficiencies; please feel free
to ping either Jamie or myself should you need assistance.

All the best,

Mary

1(c) Scope. -- It appears this is covered in the Purpose section but needs to be
explicitly identified as such since this is the governing portion of the work of
the Technical Committee.

(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. -- Again, I think this is
covered in the Purpose section and just needs to be explicitly called out here.

(2)(b) The date, time, and location of the first meeting, whether it will be
held in person or by phone, 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 telephone or other electronic meeting, and no less
than 45 days after the announcement of its formation in the case of a
face-to-face meeting.

(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)(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.

> -----Original Message-----
> From: Breininger, Kathryn R [mailto:kathryn.r.breininger@boeing.com]
> Sent: Friday, December 21, 2007 5:11 PM
> To: jamie.clark@oasis-open.org; mary.mcrae@oasis-open.org
> Cc: ebxml-jc@lists.oasis-open.org
> Subject: Submission of Proposal for new TC formation
> 
> Jamie and Mary,
> Below is the JC's submission for proposal for formation of a new OASIS TC.
> I have also attached a Word file document of the proposal. Please let us
> know if you have any questions or comments.
> 
> Charter for the ebXML Core Technical Committee
> 
> Name and abbreviation
> 
> OASIS ebXML Core TC: ebCore
> 
> CORE - Continuity, Outreach, Readiness, Enhancements
> 
> Purpose
> 
> The ebXML Core TC is to be the maintenance group for ebXML TC
> specifications as these specifications are completed or transitioned to the
> ebXML Core TC. TCs eligible for maintenance by the ebXML Core TC are ebXML
> Messaging, ebXML CPPA, ebXML ebBP, ebXML IIC, and ebXML RegRep.
> The ebXML Core TC will provide the means to manage clarifications,
> modifications, and enhancements for the specifications that ebXML TCs have
> either completed and/or turned over as work in progress for completion
> through the OASIS standards process. The ebXML Core TC may issue errata for
> specifications that they maintain and may complete reviews and changes
> required by editor's on committee drafts received by the TC for completion.
> The ebXML Core TC may form subcommittees to provide focus for specific
> specification tasks as they arise. The ebXML Core TC may lead the formation
> of charters for new ebXML TCs for major new versions of specifications. The
> TC may also produce new conformance profiles and adjunct documents
> complementing existing specifications.
> The ebXML Core TC will solicit new end user requirements as well as
> implementation enhancements and change requests. The TC will also explore
> synergies with UN/CEFACT, WS-* specifications and SOA best practices. The
> ebXML Core TC may update schemas, examples, specifications and other
> products of ebXML TC activities.
> The ebXML Core TC will also provide information services for the
> ebXML.xml.org site and for OASIS Webinars and other informational
> activities.
> Explicitly Out-of-scope:
> 
> The ebXML Core TC will not accept work unrelated to the maintenance and
> enhancement of the ebXML specifications or related documents.
> 
> Deliverables
> 
> At the time of formation of the ebXML Core TC, the following work items are
> anticipated:
> 1. ebXML CPPA version 3 drafts for committee and public reviews,
> modifications, and for marshalling through the OASIS standardization
> process. A transition of the ebCPPA TC is expected to be approved upon
> formation of the ebXML Core TC. Projected completion date: July 2009.
> 2. ebXML IIC drafts and working documents will be maintained in a to be
> decided manner upon being made available from the ebXML IIC TC. These
> documents contain material for facilitating adoption of existing ebXML
> standards, such as test suites and deployment profiles. Projected
> completion date: July 2009.
> 3. ebXML ebBP maintenance may result in either errata, a new minor version,
> or a charter for a new major version when change requests based on
> implementation experience, new use cases for the models, or requests for
> enhancements has reached critical thresholds. The precise course of action
> will depend upon uptake by implementers and users of the current version 2
> specification. The ebXML ebBP TC will consider its transition after the
> formation of the ebXML Core TC. Projected completion date: July 2009.
> 4. ebXML ebMS version 3 conformance profiles in addition to those completed
> by the current ebXML ebMS TC may be produced following the transition of
> the ebMS TC to the Core TC. Projected completion date: July 2009.
> 5. ebXML RegRep is continuing major version work on its own, but is
> eligible to transition to maintenance within the Core TC for errata and
> further enhancements after formation of the ebXML Core TC
> 6. Profiles and adjunct documents that complement and enhance existing
> specifications.
> 
> Timeline:
> 
> The TC will remain open until its deliverables are completed.
> 
> 
> IPR Mode
> 
> Royalty-Free on Limited Terms.
> 
> Audience
> 
> The TC is open to any OASIS member with an interest in enhancing ebXML
> specifications and supporting materials used by implementers of or
> participants in collaborative business processes.
> 
> Language
> 
> English
> 
> Proposers
> 
> Ian Jones, ian.c.jones@bt.com British Telecommunications plc
> Jacques Durand, jdurand@us.fujitsu.com, Fujitsu Limited
> Pim van der Eijk, pim.vandereijk@oasis-open.org, Sonnenglanz Consulting
> Dale Moberg, dmoberg@us.axway.com, Axway Software
> Kathryn Breininger, Kathryn.r.breininger@boeing.com, The Boeing Company
> David Webber, david@drrw.info, Individual
> 
> Convener
> 
> Kathryn Breininger, The Boeing Company
> 
>  <<Draft Charter ebXML Core TC.doc>>
> 
> 
> Thanks,
> Kathryn
> 
> Kathryn Breininger
> Manager, Release & Delivery Services
> CIMS - Center for Information Management Services
> 
> MC 62-LC
> 425-965-0182 phone
> 425-237-3491 fax
> kathryn.r.breininger@boeing.com
>