attachment-0001
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2722.900" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=722265914-28052003><FONT face=Arial color=#0000ff
size=2>Harry,</FONT></SPAN></DIV>
<DIV><SPAN class=722265914-28052003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=722265914-28052003><FONT face=Arial color=#0000ff size=2>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. </FONT></SPAN></DIV>
<DIV><SPAN class=722265914-28052003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=722265914-28052003><FONT face=Arial color=#0000ff
size=2>Hopefully, we will get beyond the other things on the agenda to start
discussion of the operations.</FONT></SPAN></DIV>
<DIV><SPAN class=722265914-28052003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=722265914-28052003><FONT face=Arial color=#0000ff size=2>Bill
Wagner</FONT></SPAN></DIV>
<DIV><SPAN class=722265914-28052003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=722265914-28052003></SPAN><SPAN
class=722265914-28052003></SPAN><SPAN class=722265914-28052003><FONT face=Arial
color=#0000ff size=2>(the messages listed are)</FONT></SPAN></DIV>
<DIV><SPAN class=722265914-28052003><FONT face=Arial color=#0000ff
size=2><message name="GetAttributesResponse"/><BR><message
name="GetAttributesRequest"/><BR><message
name="SetAttributesRequest"/><BR><message
name="SetAttributesResponse"/><BR><message
name="GetAttributesAsyncRequest"/><BR><message
name="GetAttributesAsyncResponse"/><BR><message
name="SetAttributesAsyncRequest"/><BR><message
name="ExecuteRequest"/><BR><message
name="ExecuteResponse"/><BR><message
name="ExecuteAsyncRequest"/><BR><message
name="ExecuteAsyncResponse"/><BR><message
name="GetAllRequest"/><BR><message
name="GetAllResponse"/><BR><message
name="RegisterRequest"/><BR><message
name="RegisterResponse"/><BR><message
name="SetAttributesAsyncResponse"/><BR><message
name="UnRegisterRequest"/><BR><message
name="UnRegisterResponse"/></FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Harry Lewis
[mailto:harryl@us.ibm.com]<BR><B>Sent:</B> Wednesday, May 28, 2003 1:18
AM<BR><B>To:</B> wbmm@pwg.org<BR><B>Subject:</B> WBMM> PWGDeviceControl
Interface WSDL (Proposal)<BR><BR></FONT></DIV><BR><FONT face=sans-serif
size=2>Posted</FONT><A href="ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/"></A><FONT
face=sans-serif size=2> 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</FONT> <BR><BR><FONT face=sans-serif
size=2>GetAttributes</FONT> <BR><FONT face=sans-serif
size=2>SetAttributes</FONT> <BR><FONT face=sans-serif
size=2>ExecuteCommand</FONT> <BR><FONT face=sans-serif size=2>GetAll</FONT>
<BR><BR><FONT face=sans-serif size=2>It also supplies mechanisms for
</FONT> <BR><BR><FONT face=sans-serif size=2>Register</FONT> <BR><FONT
face=sans-serif size=2>Unregister</FONT> <BR><BR><FONT face=sans-serif
size=2>for notifications. These can be displaced if we engage a more global
notifications PWG working group.</FONT> <BR><BR><FONT face=sans-serif
size=2>Examples of Execute commands would be Reset, OpPanelMessage, Off-line,
LockOpPanel, DownloadCode</FONT> <BR><BR><A
href="ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlInterface.wsdl"><FONT
face=sans-serif color=blue
size=2>ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlInterface.wsdl</FONT></A>
<BR><A
href="ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlService.wsdl"><FONT
face=sans-serif color=blue
size=2>ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlService.wsdl</FONT></A>
<BR><A
href="ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlBinding.wsdl"><FONT
face=sans-serif color=blue
size=2>ftp://ftp.pwg.org/pub/pwg/wbmm/WDSL/PWGDeviceControlBinding.wsdl</FONT></A>
<BR><BR><FONT face=sans-serif size=2>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. </FONT><BR><BR><FONT
face=sans-serif size=2>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.
</FONT>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD colSpan=3><FONT size=2><BR></FONT><FONT face=sans-serif
size=2>Perhaps we can spend some time on the agenda tomorrow if there
are any comments or questions on the WSDL.</FONT>
<BR></TR></TBODY></TABLE><BR><FONT face=sans-serif
size=2>---------------------------------------------- <BR>Harry Lewis
<BR>Chairman - IEEE-ISTO Printer Working Group<BR>http://www.pwg.org<BR>IBM
Printing Systems
<BR>http://www.ibm.com/printers<BR>303-924-5337<BR>----------------------------------------------
</FONT></BLOCKQUOTE></BODY></HTML>