[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-jc] FW: [udef.builders] Update on eBusiness Standards Convergence from the auto industr
So, I have modified the charter draft based on these comments.
- section (2) emphasizes the relationship with other orgs.
- added two types of deliverables (see #5 and #6)
Let me know your comments.
At next JC meeting (June 9th) we will try to:
- finalize the posting that Monica has drafted.
- get consensus on the draft charter.
From: Monica J. Martin [mailto:Monica.Martin@sun.com]
Sent: Friday, June 04, 2004 9:59 AM
To: Dale Moberg
Cc: firstname.lastname@example.org; john hardin
Subject: Re: [ebxml-jc] FW: [udef.builders] Update on eBusiness
Standards Convergence from the auto industr
>Moberg: This idea might expand, or maybe just illustrate, Jacques' remarks about
>Monica's draft adding something about interaction with OAG AIAG and so
>It would be good to solicit input from endusers on requirements and it
>might be easier (given how the functionality is spread over several TCs
>at least) to have a central clearinghouse.
mm1: Good suggestion
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ebxml-jc/members/leave_workgroup.php.
**** DRAFT FOR DISCUSSION ONLY **** OASIS ebXML Marketing & Adoption TC Charter NAME The name of this Technical Committee is the ebXML Marketing & Adoption Technical Committee (TC). PURPOSE & SCOPE The purpose of this TC is to provide a forum for collaboration on the facilitation and promotion of ebXML specifications and their adoption, consistent with the principles of the original ebXML project. The TC may develop materials, presentations and events that contribute to this goal, subject to the control OASIS retains over the proper use of the ebXML logo, brand, domain and similar assets. The TC also may serve as a coordinating resource for adoption and promotion efforts of current and future OASIS ebXML technical committees (TCs). The TC will interact with B2B user organizations such as RosettaNet, OAGI, AIAG, for: (1) doing joint marketing and promotional operations, e.g. demonstrations in trade-shows, (2) gathering requirements from these user communities, and feedback on ebXML specifications and products. The TC will communicate feature requirements and feedback data to the ebXML TCs, in order to facilitate the alignment of these TCs with the needs of these communities. The TC will not publish normative public guidance about existing ebXML specifications that contradicts the approved texts. Suggestions for change or extension should be welcome and recorded, but expressed in a manner that does not undermine the approved specifications as the primary source of ebXML technical guidance. No part of this charter grants any right (or changes any present arrangements with respect to such rights) to use the separate brands, logos or work product of any other organization. The TC may elect to submit appropriate work product for approval as Committee Drafts, and in some cases for balloting by OASIS membership for OASIS standard status, pursuant to the OASIS TC Process. List of Deliverables Promotional, explanatory and marketing materials related to the implementation and adoption of ebXML. Among other things, subject to applicable OASIS policies, the TC may elect to produce or assist with: 1. Maintenance of the implementer listing pages on the ebxml.org site. 2. Acting as the clearinghouse for proposals for content of the ebxml.org site and advice to OASIS regarding the look and feel of the site. 3. Solicitation, support and maintenance of a vendor- and industry-neutral ebXML users council (or similar entity) for the balanced promotion of use of ebXML technologies and methodologies. 4. Solicitation and linking to, or mirroring of, relevant original materials authored by third parties to or on current information pages of the ebxml.org site or other appropriate distribution channels. 5. Creation and maintenance of a "requirements and feedback document", based on user input material, and intended to the other ebXML TCs. The process of gathering requirements may be informal (a by-product of other activities) or may involve user surveys. 6. Aggregation and maintenance of a list of current ebXML projects and users. Anticipated Audience All OASIS ebXML TCs, non-OASIS ebXML standards groups and SOA implementers, vendors, eGovernment personnel and users are the primary audience. Language English. The TC may elect to form subcommittees that will produce localized documentation of the TC's work in additional languages. NON-NORMATIVE OTHER WORK As appropriate, the ebXML M&A TC will collaborate with other relevant OASIS TCs, such as the ebXML BP, ebXML CPPA, ebXML MSG, ebXML IIC and ebXML Registry committees, the ebSOA TC and such other SOA and web services TCs as may find ebXML relevant to their work. The ebXML M&A TC will also work to align with relevant efforts of other organizations, such as RosettaNet, the Open Applications Group Inc. (OAGI) and the United Nations Centre for Trade Facilitation and eBusiness (UN/CEFACT) organization. Organizations developing or promoting ebXML methodologies will be invited to participate subject to OASIS rules. Other liaisons may be identified and established by the TC to further its work and purpose. FIRST MEETING The first meeting of the ebXML M&A TC will take place on _______, over the phone, at a number to be provided to prospective participants no later than 5 days before the meeting. That date and time will be the time of record for establishing initial voting membership under the OASIS TC process. SCHEDULE After the initial teleconference meeting the TC shall meet [monthly] over the phone unless another schedule is agreed upon. * * * TC CO-SPONSORS The following persons eligible to participate in OASIS technical committees state that they are committed to the purpose and schedule stated above: * * * CONVENOR The Convenor shall be * * * The proposed chairs are * * *