The way this is done in most XML and Web Services related standards is that
both groups work together and produce a "shared" module. This module in
turn is part of both the WSRP and WSIA deliverables.
Best regards,
Angel
Angel Luis Diaz, Ph.D
Senior Manager, Next Generation eXperience Frameworks
IBM T. J. Watson Research Center
aldiaz@us.ibm.com
(914) 784-7388 / (914) 441-7594
Greg Giles <ggiles@cisco.com> on 03/13/2002 08:38:23 PM
To: Eilon Reshef <eilon.reshef@webcollage.com>, Wsia
<wsia@lists.oasis-open.org>
cc:
Subject: RE: [wsia] Questions around Relationship between WSIA and WSRP
Eilon, great update, thanks.�Your note about ownership�of the common
'base' concerns me, since with such passionate groups of people involved
it may be difficult to resolve. With that in mind I thought it would be
useful to explore some less attractive options beyond the obvious, so that
any negotiations don't simply end in stalemate. Here are a couple that
jumped out at me:
- set up a third committee that has ownership of the 'base' services
-- pros
--- clear ownership, agenda and scope
-- cons
--- dependency will slow down other efforts
-�have a core set of people spanning both committees and having the base
divided between them, each dual member would lead a team within a single
committee to deliver
-- pros
--- everyone feels heard
--- good cross-pollination of concepts
-- cons
--- assumes a rigorous execution process
--- heavy time commitment
Regards
Greg