Re: [wsbpel] Liaison Activity - WAS: [wsbpel] CEFACT Liaison Review

[Diane Jordan <drj@us.ibm.com>]

The term  observer doesn't apply
in this context.  Anyone acting as liaison for our TC must be a member
of our TC and should also be a member of the other group.  

Any liaison must be approved (or rejected)
by the full TC.   So far we have approved liaisons with W3C Choreography
and CEFACT BPWG and discussed several others as possibilities.   Members
of the TC who believe liaisons with other groups are appropriate should
bring those suggestions to the TC for consideration.  The TC will
decide whether they are appropriate.  There is no definition of "normative"
that I've seen.  I trust we will all use good sense and only suggest
liaisons with relevant groups. 

The liaison relationships that have
been established are expressly to ensure communications between the groups.
  Any further action that the liaison wishes to see occur with a group
must be brought to the full TC for consideration.  This would include
many of those activities you describe.   

As I indicated in my note yesterday,
the TC was made aware of  the CEFACT BCF work both via email and in
discussion at the meeting prior to the vote which resulted in establishing
a liaison.  
You might be interested in reviewing
the Oasis process for liaisons: (Sorry, can't seem to find a link to it.)

Regards, Diane
IBM  Dynamic e-business Technologies
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123

Sid Askary <saskary@nuperus.com> 09/22/2003 09:25 PM

To:        "Frank Leymann" <LEY1@de.ibm.com>, David RR Webber - XML ebusiness <Gnosis_@compuserve.com>, "Martin Chapman" <martin.chapman@oracle.com>         cc:        "'BPEL OASIS'" <wsbpel@lists.oasis-open.org>         Subject:        [wsbpel] Liaison Activity - WAS: [wsbpel] CEFACT Liaison Review

As of today, there are 2 other general-purpose business process 
definition/choreography
languages under consideration in a standards body:  BPSS in OASIS
and WSCI 
in W3C.  For
the near term, these and the associated underlying standards on which each
is dependant
should be part of the liaison activity.  Everything else is non-normative
and perhaps
out of scope for this group.

As for the difference between Liaison and Observer, I would say that in
the 
former,
there is a great deal more cross-pollination and active engagement (in
the 
form of
normative bi-directional presentations and mutual consideration, specific
approaches,
etc.).  The purpose of this activity, in many cases, is the avoidance
of 
the invention
of the perennial wheel.

While in the later, there is, at best, a one-way channel for allowing 
information
gathering by one party.  No feedback mechanism is deemed necessary.

My 0.02$

Sid Askary

At 10:30 AM 9/22/2003, David RR Webber - XML ebusiness wrote:
>Martin,
>
>CEFACT has launched a completely new direction, and
>made press releases, and made decision vis their
>relationship with OASIS  - since we made our decision.
>They have also had a Plenary meeting in Seoul, and
>more changes and items occurred there as well.  The
>bases have been moved.
>
>I think if we had known about these at the time - we would
>have deferred our decision until we had a better
>understanding.
>
>Essentially we made our decision in the dark - and we
>now need to re-visit in the light of these events over the
>last few weeks.
>
>Thanks, DW.
>======================================================
>Message text written by "Martin Chapman"
> >
>David,
>
>For those of us not closely connected with CEFACT, could you tell us
what
>these unforeseen events are?
>Otherwise I'm not sure I have enough information at hand to decide
>accordingly.
>
>Cheers,
>  Martin.<
>
>
>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/wsbpel/members/leave_workgroup.php.



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/wsbpel/members/leave_workgroup.php.

LiaisonPolicy-20030619.doc