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 5.50.4922.900" name=GENERATOR></HEAD> <BODY> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>Thanks for the start Harry.  I would also like to add some ideas regarding the XML and MIB points you mention.</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>1.  The new model should be structured around how the data is consumed by applications as opposed to how a device is physically built.</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>2.  It should take advantage of XML's ability to describe (and enforce) structure</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>3.  It should be extensible so that vendors can add their own extensions.  We should provide a defined path for vendors to provide updates to the model as needed.  (Maintenance?)</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>4.  It should be organized in a manner that a group of related data can be accessed all at once.</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>5.  It should take into account other efforts that are happening in other standards areas to leverage learnings in these areas where beneficial and to not cause conflict in overlapping areas whenever possible.</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2> I also think we should address the access protocol.  </FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>1.  Use SOAP</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>    -  SOAP supports both an RPC and document based model.</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>    -  Currently, use SOAP over HTTP but it is not limited to this</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>    -  WSDL exists to describe SOAP services</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>    -  Directory and discovery services exist to support the SOAP protocol (for example UDDI)</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003>    <FONT face=Arial color=#0000ff size=2>-  SOAP is also usable by the wide variety of applications that Harry mentions below.</FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=218093300-31012003><FONT face=Arial color=#0000ff size=2>  </FONT></SPAN></DIV> <DIV><SPAN class=218093300-31012003></DIV> <DIV></SPAN><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Harry Lewis [mailto:harryl@us.ibm.com]<BR><B>Sent:</B> Thursday, January 30, 2003 5:25 PM<BR><B>To:</B> wbmm@pwg.org<BR><B>Subject:</B> WBMM> WBMM Requiements<BR><BR></DIV></FONT> <BLOCKQUOTE><BR><FONT face=sans-serif size=2>The PWG process (diagram) acknowlesd Brainstorming, Charter development and Requirments gathering as valid actiities at the origin of a new program. I'd like to begin a requirements thread. Here are requirements of WBMM that I would like to see addressed</FONT> <BR><BR><FONT face=sans-serif size=2>1. More expressive than the Printer MIB</FONT> <BR><FONT face=sans-serif size=2>  - While the Printer MIB is an EXCELLENT standard from the point of view of adoption and functionality... there is room for improvment</FONT> <BR><FONT face=sans-serif size=2>  - Specifically, we could be more expressive and clearer regarding State, Status and Error reaaons.</FONT> <BR><FONT face=sans-serif size=2>    - You who are smiling know what I'm talking about (i.e. nix the decoder ring...)</FONT> <BR><FONT face=sans-serif size=2>2. Expressed in XML</FONT> <BR><FONT face=sans-serif size=2>  - More than a clique, XML will aid developers in designing and implementing compliant applicatins with modern tools</FONT> <BR><FONT face=sans-serif size=2>3  Usable by a wide variety of applications</FONT> <BR><FONT face=sans-serif size=2>  - Experience with the Printer MIB has demonstrated that the range of interested applications includes</FONT> <BR><FONT face=sans-serif size=2>     - Device Management</FONT> <BR><FONT face=sans-serif size=2>     - Accounting</FONT> <BR><FONT face=sans-serif size=2>     - Enterprise Managemtn</FONT> <BR><FONT face=sans-serif size=2>     - Remote Serviceing and Help Desk</FONT> <BR><FONT face=sans-serif size=2>     - Self configuring Drivers</FONT> <BR><FONT face=sans-serif size=2>4. Optomized for interoperatility</FONT> <BR><FONT face=sans-serif size=2>  - Care should be given to the use of mandatory and optional</FONT> <BR><FONT face=sans-serif size=2>  - Min/Max access to settable attributes should not be a mystery</FONT> <BR><FONT face=sans-serif size=2>  -  Consider a self describing data model vs.  embedding definitions in the protocol</FONT> <BR><FONT face=sans-serif size=2>5. More... I'm sure. Please join in...</FONT> <BR><FONT face=sans-serif size=2>---------------------------------------------- <BR>Harry Lewis <BR>IBM Printing Systems <BR>---------------------------------------------- </FONT></BLOCKQUOTE></BODY></HTML>