WBMM> PWGDeviceControl Interface WSDL (Proposal)

WBMM> PWGDeviceControl Interface WSDL (Proposal)

WBMM> PWGDeviceControl Interface WSDL (Proposal)

Wagner,William WWagner at NetSilicon.com
Wed May 28 11:44:43 EDT 2003

Many thanks for this initiative.  It is desirable to get beyond  the data model and into the discussion of the protocol and operations. Although this may be archaic, I would prefer the operations conceptual discussion be in English rather than jumping to WSDL right away. For example, I see 18 messages listed, but it is not clear to me what they do...to say the least. I do  not recognize many of the operations that were identified in the Scope&Start document I sent out in February: the idea of compound operations (get, compare, report);  of scheduling operations (now, then, periodic); the query for instructions, etc. 
Hopefully, we will get beyond the other things on the agenda to start discussion of the operations.
Bill Wagner
(the messages listed are)
<message name="GetAttributesResponse"/>
<message name="GetAttributesRequest"/>
<message name="SetAttributesRequest"/>
<message name="SetAttributesResponse"/>
<message name="GetAttributesAsyncRequest"/>
<message name="GetAttributesAsyncResponse"/>
<message name="SetAttributesAsyncRequest"/>
<message name="ExecuteRequest"/>
<message name="ExecuteResponse"/>
<message name="ExecuteAsyncRequest"/>
<message name="ExecuteAsyncResponse"/>
<message name="GetAllRequest"/>
<message name="GetAllResponse"/>
<message name="RegisterRequest"/>
<message name="RegisterResponse"/>
<message name="SetAttributesAsyncResponse"/>
<message name="UnRegisterRequest"/>
<message name="UnRegisterResponse"/>

-----Original Message-----
From: Harry Lewis [mailto:harryl at us.ibm.com]
Sent: Wednesday, May 28, 2003 1:18 AM
To: wbmm at pwg.org
Subject: WBMM> PWGDeviceControl Interface WSDL (Proposal)

Posted  <ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/> is a WSDL representation of a proposed WBMM Interface, Service and (SOAP) Binding we hope will help merge WBMM process with the successful approach taken by PSI. The interface is simple... containing both synchronous (wait for return) and asynchronous (supply URI for a "listener" for the asych response) versions of 


It also supplies mechanisms for   


for notifications. These can be displaced if we engage a more global notifications PWG working group. 

Examples of Execute commands would be Reset, OpPanelMessage, Off-line, LockOpPanel, DownloadCode 

 <ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlInterface.wsdl> ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlInterface.wsdl 
 <ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlService.wsdl> ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlService.wsdl 
 <ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlBinding.wsdl> ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlBinding.wsdl 

The WSDL was built using IBM's WebSphere Applications Development environment and I haven't had an opportunity to check using XMLSPY... so there could be some incompatibility. 

I hope this will be viewed as a good basis for interface discussion just as Ira's work on translating the Printer MIB has been for data model and Bill/Cathy/Kelli's work is for requirements.   

Perhaps we can spend some time on the agenda tomorrow if there are any comments or questions on the WSDL. 

Harry Lewis 
Chairman - IEEE-ISTO Printer Working Group
IBM Printing Systems 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/wims/attachments/20030528/f88cb311/attachment-0001.html

More information about the Wims mailing list