Hi,
To clarify a little...
PSI conformance print services and target devices MUST publish
URLs for the WSDL for each of their supported interfaces (see
my revised conformance requirements message earlier today).
Tools exist that convert WSDL to appropriate SOAP messages.
A "SOAP binding" is a definition of SOAP message _transport_
over HTTP, SMTP, BEEP, or whatever (those three are currently
standardized).
For interoperability, clients and servers need to be able to
consume and validate published WSDL definitions of other PSI
servers.
For interoperability, all PSI/1.0 clients and servers MUST
support the HTTP/1.1 transport binding of SOAP/1.1.
Separately, PSI/1.0 doesn't (yet) require support for UDDI
based discovery. I question the desirability of adding a
UDDI infrastructure dependence to all PSI/1.0 implementations.
Cheers,
- Ira McDonald
High North Inc
-----Original Message-----
From: Harry Lewis [mailto:harryl at us.ibm.com]
Sent: Tuesday, September 09, 2003 12:43 PM
To: ps at pwg.org
Subject: PS> Mandatory binding
During today's conference call the topic of a mandatory binding came up.
We would prefer to publish the interface and binding WSDL separately and
define a discovery method. We're not sure if UDDI is too coarse a discovery
method for this purpose.
----------------------------------------------
Harry Lewis
Chairman - IEEE-ISTO Printer Working Group
http://www.pwg.org
IBM Printing Systems
http://www.ibm.com/printers
303-924-5337
----------------------------------------------