W3C home > Mailing lists > Public > www-ws-arch@w3.org > March 2002

RE: Web Service Definition [Was "Some Thoughts ..."]

From: Krishna Sankar <ksankar@cisco.com>
Date: Mon, 4 Mar 2002 12:00:24 -0800
To: <www-ws-arch@w3.org>
Message-ID: <NABBJDOPDKGCDCNBNEDOIENNHCAA.ksankar@cisco.com>
Mike,

	I had responded to the message.

	In essence that message defines web services as SOAP interaction described
using WSDL. If we abstract it one more level up, we get the "interfaces and
binding described using standards"  + "interact using internet protocols".

	We can move up or down the levels of abstraction (i.e. be more specific or
be more general). We can even do one of the following i.e. combine the
definitions we have so far:

	"A web service is defined as software which has the following
characteristics:

	1.	Interfaces and bindings defined in a standard way
	2.	Interacts using standard Internet protocols
	3.	The result 1s XML with the vocabulary clearly documented
	4.	The result is XML that matched a specific schema
	5.	The result is SOAP with the payload documented in human-readable form
	6.	The result is SOAP and the payload documented with WSDL
	7.	URI encoded a SOAP invocation message and the result was SOAP with the
payload documented with WSDL.
	8.	Does not *require* human interaction
	9.	Does not *mandate* an object model
	A.	Is programming language and VM independent
	B.	Is distributed
	C.	Is secure
	D.	..."

	Does this make more sense ?

	BTW, I am not that comfortable saying web service needs to talk XML. I
agree on this with James Snell that even though for the most part, in the
foreseeable future we would be using XML, we should not restrict the
*definition* to XML.

	OTOH, may be we could substitute "structured markup language" for XML and
thus be technology neutral.

	i.e. 3. The result 1s structured markup language with the vocabulary
clearly documented
	   4. The result is structured markup language that matched a specific
schema
		.. and so on

cheers

 | -----Original Message-----
 | From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
 | Behalf Of Champion, Mike
 | Sent: Monday, March 04, 2002 11:23 AM
 | To: David Orchard; www-ws-arch@w3.org
 | Subject: RE: Web Service Definition [Was "Some Thoughts ..."]
 |
 |
 |
 |
 | > -----Original Message-----
 | > From: David Orchard [mailto:david.orchard@bea.com]
 | > Sent: Monday, March 04, 2002 1:57 PM
 | > To: www-ws-arch@w3.org
 | > Subject: RE: Web Service Definition [Was "Some Thoughts ..."]
 | >
 | >
 | > I agree with Dietmar.  I see little difference between "web
 | > resources" and
 | > "web services" in Krishna's definition.
 |
 | I didn't see much discussion in response to
 | http://lists.w3.org/Archives/Public/www-ws-arch/2002Mar/0029.html .  This
 | described about 6 gradations between something that is clearly a "web
 | resource" (a stock quote page directed at humans) and indisputably a "web
 | service" (a SOAP message invoking an XML representation of the
 | stock price,
 | all described in WSDL). I'd be very curious to hear where other
 | people would
 | draw the line.  For me, it's where the "contract" between the service
 | provider and the service consumer becomes explicit and detailed enough so
 | that a programmer could invoke the service and use the results,
 | without any
 | "AI" stuff, of course.
 |
 |
Received on Monday, 4 March 2002 15:00:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:24:55 GMT