• To: Rick Jelliffe <ricko@a...>, XML Dev <xml-dev@l...>
• Subject: Re: Redefining the meaning of common nouns
• From: Paul Prescod <paul@p...>
• Date: Thu, 28 Nov 2002 06:17:53 -0800
• In-reply-to: <1038472726.25572.2766.camel@ibook>
• References: <1038472726.25572.2766.camel@ibook> <015701c296d7$5f573140$4bc8a8c0@A...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021016

Rick Jelliffe wrote:

>
> The point about web services is that they provide some metadata that 
> allows you to find or use them: for example, that they may advertise 
> or have schemas. 

I thought that the point about Web Services(TM) was that they were 
interfaces to services intended to be processed by machines rather than 
presented to human beings. I would posit that less than 1 in 20 
"self-declared Web Services" uses any formal discovery mechanism and 
less than half have a service discovery.

> So that some software can say "I want to find a certain service" or 
> some other software can also say "tell me what format/schema is being

> used."


I strongly disagree that this is the defining characteristic as the term 
is used even in "the industry". XMethods lists many web services with no 
WSDL.

If I just make a SOAP endpoing with no WSDL, what do I call that if not 
a Web Service or XML Web Service?

  Paul Prescod

• Follow-Ups:
  • Re: Redefining the meaning of common nouns
    • From: "Rick Jelliffe" <ricko@a...>

• References:
  • Redefining the meaning of common nouns
    • From: Eric van der Vlist <vdv@d...>
  • Re: Redefining the meaning of common nouns
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: Re: Redefining the meaning of common nouns
• Next by Date: Re: Redefining the meaning of common nouns
• Previous by thread: Re: Redefining the meaning of common nouns
• Next by thread: Re: Redefining the meaning of common nouns
• Index(es):
  • Date
  • Thread