RE: [ebxml-jc] JC Thursday December 20 3 PM Eastern conference call.

["Karl F. Best" <karl.best@oasis-open.org>]

Late agenda item: OASIS has been invited by EDIFICE to provide some
presentations on ebXML for their meeting in Dublin in February. We
talked about a series of "ebXML Roadshows" in a JC call a month or two
ago; the Dublin meeting could be the first of these. We need to decide
if this is the right thing to do, and who will do it. I've asked Carol
Geyer (OASIS PR) to dial in to the meeting so we can discuss this.

</karl>
=================================================================
Karl F. Best
OASIS - Director, Technical Operations
978.667.5115 x206
karl.best@oasis-open.org  http://www.oasis-open.org


> -----Original Message-----
> From: Dale Moberg [mailto:dmoberg@cyclonecommerce.com]
> Sent: Wednesday, December 12, 2001 8:55 AM
> To: ebxml-jc@lists.oasis-open.org
> Subject: [ebxml-jc] JC Thursday December 20 3 PM Eastern conference
> call.
>
>
> The call information:
>
> 877 204 8750
> Conference code is 4806272648.
>
> (International callers can use) 706 679 5113
>
>
> Agenda So Far: (Please add proposed topics
> by posting to list)
>
> Administrative
>
> When should December's second meeting be scheduled?
>
> Old Issues
>
> 1. Form consensus on how to rotate chair task.
> Could someone propose a quarterly rotation to begin
> January 2002, for example?
>
> 2. Patent IPR issues updates from Karl? RF and RAND?
> How and who to contact concerning any claims.
> Especially on SOAP.
>
> From notes:
>
> Should there be some information about how to contact parties
> making IPR claims concerning protocols and specifications
> underlying OASIS specifications?
>
>
>
>
> New Issues
>
>  1. (KB) As you are probably aware, the Vienna ebXML MoU between OASIS
> and
> UN/CEFACT specified that each side would have three voting
> reps and two
> non-voting technical rep to a joint management group. OASIS'
> three reps
> are Patrick Gannon (OASIS CEO), Simon Nicholson, and Norbert
> Mikula, all
> from the OASIS Board of Directors. I am one of the non-voting
> technical
> reps, and we are in need of a second. The OASIS Board would
> like the JC
> to nominate a person to fill that role; the Board would
> then make the final decision.
>
> Responsibilities of the rep are to attend meetings of the joint
> management team to represent OASIS technical activities.
> Meetings are
> bi-weekly phone calls, and possible occasional f2f meetings
> that would
> likely be scheduled to coincide with other meetings (I don't
> think we'd
> ever schedule a stand-alone meeting; we want to keep this
> light-weight.)
>
> 2. (KB) You're probably aware that the Vienna agreement also
> stated that
>  there would be a joint architecture team to design the next
>  phase of the
>  ebXML specs. ebTWG has gone ahead and formed an architecture team on
>  their side, and are waiting for OASIS to do the same. The two teams
>  would then comprise the joint team, or perhaps send reps to
>  be members of the joint team.
>
>  The OASIS Board would like to hear recommendations from the
>  JC on how to
>  form the architecture team and how it should operate. For
>  example, does
>  the JC itself want to be the OASIS architecture team? Or
>  should it be a
>  separate TC or JC? Should it be restricted to ebXML only,
>  or would it
>  define an architecture for all OASIS e-business technical work?
>
> 3. (DM) How should references to not yet approved
> standards be handled? For example, the BPSS
> version 1.1 will probably lag CPPA. CPPA
> will probably lag Messaging.
>
> 4. (DM) We have an early draft specification that
> straddles groups (normative spec on
> how to populate Message fields with
> values from a CPA.) Is there a joint
> TC approval process? Can a spec be
> jointly issued? If a spec must be
> issued by one TC, how can another
> TC be given a voice in its discussion?
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>