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.2800.1491" name=GENERATOR></HEAD> <BODY> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4>Hi Bill,</FONT></SPAN></DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4></FONT></SPAN> </DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4>Umm...actually as chair you ARE supposed to be announcing PWG Last Call on </FONT></SPAN></DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4>the Counter MIB now, for Tokyo review (see the Tokyo schedule).</FONT></SPAN></DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4></FONT></SPAN> </DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4>I published the Last Call ready version ten a week ago on the 19th of March.</FONT></SPAN></DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4></FONT></SPAN> </DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4>Please start this last call soon (SEPARATELY from the note starting the Last</FONT></SPAN></DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4>Call on the Counter abstract spec, because comments must be correlated and</FONT></SPAN></DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4>permanently recorded for each separate document).</FONT></SPAN></DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4></FONT></SPAN> </DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4>Cheers,</FONT></SPAN></DIV> <DIV><SPAN class=181522018-25032005><FONT face=Arial color=#0000ff size=4>- Ira</FONT></SPAN></DIV> <DIV><SPAN class=181522018-25032005></SPAN><SPAN class=181522018-25032005></SPAN> </DIV> <P><FONT size=2>Ira McDonald (Musician / Software Architect)<BR>Blue Roof Music / High North Inc<BR>PO Box 221  Grand Marais, MI  49839<BR>phone: +1-906-494-2434<BR>email: imcdonald@sharplabs.com</FONT> </P> <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> owner-wims@pwg.org [mailto:owner-wims@pwg.org]<B>On Behalf Of </B>wamwagner@comcast.net<BR><B>Sent:</B> Friday, March 25, 2005 12:32 PM<BR><B>To:</B> wims@pwg.org<BR><B>Cc:</B> Peter.Zehler@XeroxLabs.com<BR><B>Subject:</B> WIMS> Last Call Objectives<BR><BR></FONT></DIV> <DIV>Ira is correct that is our intent to offer just Peter's counter spec for last call i early enough to be considered at the Tokyo meeting. The counter spec is a significant document that defines in a structured and consistent way multi-function imaging system parameters for services status and  utilization. At this point, this definition is not bound to any specific management application or protocol, but rather provides conceptual standardization applicable to imaging system monitoring, management and administration using any method. These counter elements address service aspects not covered by the existing printer MIB, or by any other standard. Our objective is to get this document out for review and approval.</DIV> <DIV> </DIV> <DIV>Specific mappings of the counters to MIB and XML Schema context are being worked on, but these are not yet ready for review, and reasonably will not be until the after the more abstract Counter Spec is agreed to.</DIV> <DIV> </DIV> <DIV>Although the counter spec, its schema mapping, and the schema mapping of the Printer MIB elements were predicated by the WIMS working group objectives, the utility of these efforts is not limited to use with the WIMS protocol. Rather, it is expected that initiatives such as DMTF/CIM and WSDM will also wish to use the results of the detailed  management model manifest in the results of these efforts. For this reason, it is particularly desirable that the Counter Spec and the subsequent mapping products of the WIMS working group be considered even by those who may have no interest in the WIMS protocol itself.</DIV> <DIV> </DIV> <DIV>As to the WIMS protocol specification, we believe it is nearing completion although, as Ira points out, PWG procedure requires that a suitable requirements document also be issued. The  The WIMS working group, in conjunction with the PWG officers, will determine how this is best addressed. The current version of the draft specification is available under the "WD" subdirectory in the WIMS section of the PWG FTP site. WIMS specification will not be offered for last call prior to the April PWG meeting. However,  an informative presentation describing the purpose, form and implementation of the WIMS protocol will be presented at the meeting. This is intended both for those who are unfamiliar with this project, and for those who would like an update. The members of the working group believe that the protocol addresses a very real and intensifying set of  requirements, and is interested in  comments from the wider body of printer and multifu! nction device makers, distributors, users and maintainers.</DIV> <DIV> </DIV> <DIV>Bill Wagner, WIMS Chairman</DIV> <DIV> </DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message -------------- <BR><BR>> Hi, <BR>> <BR>> One clarification for these minutes and Harry's announcement <BR>> note below. <BR>> <BR>> We are NOT trying to move the WIMS Protocol spec to 'last <BR>> call' in the immediate future. <BR>> <BR>> There is still some (minor) schema work to be done in the <BR>> Schedule schema (to allow the use of asset tags rather than <BR>> device URI in TargetObjects). <BR>> <BR>> There is also (probably major) work to be done on the WIMS <BR>> Requirements section, which MUST be completed before we can <BR>> 'last call' the WIMS Protocol spec. <BR>> <BR>> Note that the WIMS Counter spec does NOT depend on the WIMS <BR>> Protocol spec, so that the WIMS Counter spec can be moved <BR>> ahead to 'last call' independently. <BR>> <BR>> <BR>> Structure: Having seen WIMS P! rotocol spec with Requirements <BR>> added, I've had second thoughts and think we should separate <BR>> them into two documents. Bill has done recent editorial work <BR>> on WIMS use cases, but otherwise nobody has looked at them in <BR>> two years. The IPPFAX and PSI teams were delayed for between <BR>> four and six months (with running weekly telecons) when we had <BR>> to go back and finish our Requirements specs that were REQUIRED <BR>> by PWG Process/2.0 before a protocol spec could be approved. <BR>> <BR>> Cheers, <BR>> - Ira <BR>> <BR>> <BR>> Ira McDonald (Musician / Software Architect) <BR>> Blue Roof Music / High North Inc <BR>> PO Box 221 Grand Marais, MI 49839 <BR>> phone: +1-906-494-2434 <BR>> email: imcdonald@sharplabs.com <BR>> -----Original Message----- <BR>> From: owner-wims@pwg.org [mailto:owner-wims@pwg.org]On Behalf Of Harry Lewis <BR>> Sent: Friday, March 25, 2005 12:28 AM <BR>> To: wims@pwg.! org <BR>> Cc: Peter.Zehler@XeroxLabs.com; wamwagner@comcast.net <BR>> Subject: WIMS> WIMS minutes posted <BR>> <BR>> <BR>> <BR>> There have been a series of WIMS phone conferences leading up to the Tokyo <BR>> meeting. I have posted a collection of minutes from these meetings. The next <BR>> WIMS conference call is schedule for <BR>> Tuesday March 30, 2005. <BR>> <BR>> (Different) Time: 10am Eastern (8am Pacific) <BR>> Call-in US Toll-free: 1-866-365-4406 <BR>> Call-in International/Toll: 1-303-248-9655 <BR>> Participant Identification number: 2635888# <BR>> ftp://ftp.pwg.org/pub/pwg/wims/minutes/wims_050324.pdf <BR>> <BR>> Please take time to review the latest WIMS Counter spec and WIMS protocol <BR>> drafts as we prepare to go to Last Call. <BR>> ---------------------------------------------- <BR>> Harry Lewis <BR>> IBM STSM <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>> ---------------------------------------------- </BLOCKQUOTE></BODY></HTML>