[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OASIS Call for Participation: ebXML-CORE
To: OASIS members & interested parties A new OASIS technical committee is being formed. The OASIS ebXML Core (ebCore) Technical Committee has been proposed by the members of OASIS listed below. The proposal, below, meets the requirements of the OASIS TC Process [a]. The TC name, statement of purpose, scope, list of deliverables, audience, and language specified in the proposal will constitute the TC's official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC's first meeting. This TC will operate under our 2005 IPR Policy [b]. The eligibility requirements for becoming a participant in the TC at the first meeting (see details below) are that: (a) you must be an employee of an OASIS member organization or an individual member of OASIS; (b) the OASIS member must sign the OASIS membership agreement [c]; (c) you must notify the TC chair of your intent to participate at least 7 days prior to the first meeting, which members may do by using the "Join this TC" button on the TC's public page at [d]; and (d) you must attend the first meeting of the TC, at the time and date fixed below. Of course, participants also may join the TC at a later time. OASIS and the TC welcomes all interested parties. Non-OASIS members who wish to participate may contact us about joining OASIS [c]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC's public home page at [d]. Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your feedback. Regards, Mary --------------------------------------------------- Mary P McRae Manager of TC Administration, OASIS email: email@example.com web: www.oasis-open.org [a] http://www.oasis-open.org/committees/process.php [b] http://www.oasis-open.org/who/intellectualproperty.php [c] See http://www.oasis-open.org/join/ [d] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebcore CALL FOR PARTICIPATION OASIS the ebXML Core (ebCore) TC (1)(a) Name of the TC OASIS ebXML Core (ebCore) TC CORE - Continuity, Outreach, Readiness, Enhancements (1)(b) Statement of 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. 1(c) Scope: 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. 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. (1)(d) 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. 6. Profiles and adjunct documents that complement and enhance existing specifications. The TC will remain open until its deliverables are completed. (1)(e) IPR Mode under which the TC will operate: Royalty-Free on Limited Terms (1)(f) Audience or users of the work: 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. (1)(g) Language in which the TC shall conduct business: English (2)(a) Identification of similar or applicable work that is being done in other OASIS TCs or by other organizations: The ebXML JC is disbanding. The ebXML Core TC will take on the roles and the work of the ebXML JC, and in addition will do maintenance on the standards that have been produced by the ebXML TCs: ebXML Messaging, ebXML CPPA, ebXML ebBP, ebXML IIC, and ebXML RegRep. (2)(b) The date, time, and location of the first meeting: First meeting, Telecon April 4th at 9:00 am - 10:30 am Pacific Time Call will be hosted by The Boeing Company (2)(c) The projected on-going meeting schedule: Every two weeks. (2)(d) Names e-mail addresses and membership affiliations of proposers: Ian Jones, firstname.lastname@example.org British Telecommunications plc Jacques Durand, email@example.com, Fujitsu Limited Pim van der Eijk, firstname.lastname@example.org, Sonnenglanz Consulting Dale Moberg, email@example.com, Axway Software Kathryn Breininger, Kathryn.firstname.lastname@example.org, The Boeing Company David Webber, email@example.com, Individual (2)(e) Convener: Kathryn Breininger, The Boeing Company (2)(f) The name of the Member Section with which the TC intends to affiliate: No Member Section affiliation. (2)(g) Optionally, a list of contributions of existing technical work that the proposers anticipate will be made to this TC. No contributions. (2)(h) Optionally, a draft Frequently Asked Questions (FAQ) document regarding the planned scope of the TC, for posting on the TC's website. No FAQ. (2)(i) Optionally, a proposed working title and acronym for the specification(s) to be developed by the TC. No titles for specs to be developed by the TC.