Re: Can someone recap the differences between @serviceGroup vs. definitions-targetNamespace ?

Hahahahaha .. I missed the "not" too ;-)! I imagine it was
Freudian slip .. but if not it was damned good ;-).

+1 for "not"!!!

;-)

Sanjiva.

----- Original Message -----
From: "Amy Lewis" <alewis@tibco.com>
To: "Jim Webber" <jim.webber@arjuna.com>
Cc: <www-ws-desc@w3.org>
Sent: Wednesday, July 16, 2003 9:15 PM
Subject: Re: Can someone recap the differences between @serviceGroup vs.
definitions-targetNamespace ?


>
> Hmm, it appears that I misread this, and now I'm not sure what was
> intended.  Jim?
>
> On Wed, 16 Jul 2003 12:38:25 +0100
> "Jim Webber" <jim.webber@arjuna.com> wrote:
> > Can we just not go back to allowing mulitiple interfaces per service
> > and declare victory?
>
> My eyes somehow edited out the word "not".  It made sense to me, and
> seemed to be what you have argued earlier.  With the word "not" in there
> ... where do we put the flag to proclaim victory?  In targetResource?
> In serviceGroup?  Somewhere else?  Mind, I'm opposed to most all of
> that, 'cause I still think that it's just cleaner to define service with
> multiple interfaces; I'd like us to 'just go back to allowing multiple
> interfaces per service and declare victory'.  Sorry to have
> misinterpreted; could you clarify a bit where you want to stand while
> declaring victory, since it's apparently not there in multiple
> interfaces?
>
> Amy!
> --
> Amelia A. Lewis
> Architect, TIBCO/Extensibility, Inc.
> alewis@tibco.com

Received on Wednesday, 16 July 2003 11:48:04 UTC