W3C home > Mailing lists > Public > www-ws-desc@w3.org > November 2003

RE: What WSDL defines - the diagram!

From: <paul.downey@bt.com>
Date: Wed, 5 Nov 2003 00:41:37 -0000
Message-ID: <2B7789AAED12954AAD214AEAC13ACCEF0FFF1D35@i2km02-ukbr.domain1.systemhost.net>
To: <distobj@acm.org>
Cc: <www-ws-desc@w3.org>
AIUI WSDL 2.0 will be able to describe services which work in this way, and more. 
Is it the *more* that is your concern ?

	-----Original Message----- 
	From: Mark Baker [mailto:distobj@acm.org] 
	Sent: Tue 04/11/2003 20:03 
	To: Downey,PS,Paul,XSJ67A C 
	Cc: www-ws-desc@w3.org 
	Subject: Re: What WSDL defines - the diagram!

	On Tue, Nov 04, 2003 at 06:50:43PM -0000, paul.downey@bt.com wrote:
	> ah, but the pipe is the transport.
	A Unix pipe can be used for transport or transfer.  In this case it's
	used for transfer, as there's no operation in what is exchanged (i.e.
	it's state), nor more importantly, any expectation that anything
	occur beyond simply processing the data.
	> try:  ls | zcat | sort
	Sure, schemas and content encodings have to match up.  Unix pipes
	aren't particularly self-descriptive.  Had they been, the shell would
	be able to detect the mismatch and possibly re-route the data flow to
	correct it.
	Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca


Received on Tuesday, 4 November 2003 19:41:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:45 UTC