Re: Proposed text for section 1.6.2 and 1.6.3

That's a good point: "open" is not the antithesis of "uniform".

"Custom" might be appropriate language in this case.

Remember for desktop systems when an application didn't use
the pre-defined "safe" interface?  That was call "ill-behaved", as I
recall...

On second thought, that last idea lacks marketing savvy.  How
about "bespoke"?

--Walden

----- Original Message -----
From: "Hao He" <Hao.He@thomson.com.au>
To: "'Champion, Mike'" <Mike.Champion@SoftwareAG-USA.com>;
<www-ws-arch@w3.org>
Sent: Thursday, May 08, 2003 10:57 PM
Subject: RE: Proposed text for section 1.6.2 and 1.6.3


> I was at the call and I got very confused, especially by the "open
interface
> services".  Since so many things are "open" nowadays, it can be very
> misleading.
>
> Hao
>
> -----Original Message-----
> From: Champion, Mike [mailto:Mike.Champion@SoftwareAG-USA.com]
> Sent: Friday, May 09, 2003 12:50 PM
> To: www-ws-arch@w3.org
> Subject: RE: Proposed text for section 1.6.2 and 1.6.3
>
>
>
>
>
> > -----Original Message-----
> > From: Hao He [mailto:Hao.He@thomson.com.au]
> > Sent: Thursday, May 08, 2003 10:23 PM
> > To: 'David Orchard'; 'Champion, Mike'; www-ws-arch@w3.org
> > Subject: RE: Proposed text for section 1.6.2 and 1.6.3
> >
> >
> > Would you be happy with RPC SOA?
>
> We sortof, tentatively decided today to at least temporarily :-) talk
about
> "services" rather than "SOA" in this section, and the make the distinction
> between "uniform interface services" (AKA "RESTful thingies") and "open
> interface services" (AKA what everyone outside the W3C calls "Web
> services.")
>

Received on Thursday, 8 May 2003 23:14:08 UTC