Re: [ebxml-cppa] Draft recharter document (reformatted) for 18moremonths...

[Keith Babo <keith.babo@sun.com>]

Hi Dale,

We may want to refer to this process as charter clarification instead of
"rechartering".  An associate of mine here at Sun pointed me to the
following clause in the OASIS Technical Committe Guidelines:

Clarify the TC Charter

The TC's statement of purpose, scope, and deliverables - which together
are commonly referred to as the TC charter - were defined by the
proposers of the TC and announced in the Call For Participation. The TC
Process allows these to be clarified, but not changed. A TC cannot
change its purpose or the direction of the TC - that would require
disbanding the TC then starting a new TC. The clarification must be made
by vote of the TC, and the results must be minuted and posted to the TC
mail list and web page, and communicated to the TC Administrator who
will make an announcement to the members of OASIS.


I'm new to the process, so I'm not sure this matters.  Just thought I
would point it out as an FYI.  :-)  See you next meeting!

cheers,
keith

Dale Moberg wrote:

> Apparently the formatting of the draft of the
>
> rechartering document is unreadable in some mailers.
>
> I hope this works better.
>
> Thanks,
>
> Dale Moberg
>
> PS: also including as attachment.
>
> ===============================================================
>
> OASISebXML Collaboration Protocol Profile  and Agreement TC
>
>
> Statement of Purpose: The committee will address the following
> matters:
>
>
> 1.      Maintenance of version 2.0 of the ebXML Collaboration-Protocol
> Profile and Agreement Specification (the CPP/CPA Specification, for
> short) including solicitation and collection of feedback on that
> specification, as well as possible development of minor follow-on
> versions to provide clarifications and/or minor technical
> corrections.
>
> 2.      Production of other documents, e.g., technical reports, white
> papers, implementation guidelines, and discussion of "best practices"
> to foster adoption of the specification.
>
> 3.      Gather requirements and produce specification documenting
> extension mechanisms and best practices for an updated schema for
> the ebXML Collaboration-Protocol Profile and Agreement Specification.
>
> 4.      Produce concrete example illustrating use of extension
> framework, possibly with Business Transaction support (BTP) and/or
> other functionality.
>
> 5.      Finish work (both version 1 and next) on Negotiation Protocol
> to be used for CPA Negotiation.
> 6.      Coordination within OASIS and UN/CEFACT to ensure consistency
> with related committees. In particular, the committee will work with
> the ebXML coordination committees that are created.
>
> 7.      Coordination with other OASIS and W3C technical committees
> concerned with interoperable configurability of collaboration
> capabilities.
>
> List of Deliverables and Dates:
> 2nd Quarter, 2003
> Review of Negotiation Protocol
> 3rd Quarter, 2003
> Possible maintenance release of the CPP/CPA specification. Assemble
> requirements for extension framework and list of deliverables (schema
> modifications and documentation).
>
> 4th Quarter, 2003
> Review of extension framework and any examples illustrating its use.
> 2nd Quarter, 2004
> Technical Committee reconsiders its charter and scope after 18 month
> renewal.
> Language for TC Discussion: English
> Meeting Schedule: Weekly teleconferences and face to face meetings as
> scheduled and agreed upon by participants.
> Chair:Dale Moberg, Cyclone Commerce, dmoberg@cyclonecommerce.com
> Submitters of this TC Proposal:
> Dale W. Moberg
> Cyclone Commerce
> 8388 E. Hartford Drive
> Scottsdale, AZ 85255
> USA
> Phone: 480-627-1800
> email: dmoberg@cylonecommerce.com
>
>
>