attachment

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40" xmlns:ns0="http://schemas.microsoft.com/office/2004/12/omml"> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"/>  <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Bill,<o:p></o:p> I have only had a chance to give a quick look at the document and definitely do not consider it a waste of time.� I found it quite useful and have linked it into the MFD page.� I would like to spend a little time at the face to face to work through the confusion around the Job Ticket lifecycle.� Having a top level document framing the work of modeling MFD services probably should have been the first step in the MFD group.� I was already actively working print and scan in a number of forums.� As we move forward with services, at least partially, built with the semantic definitions established in print and scan this overall view paper will be useful.<o:p></o:p> Pete<o:p></o:p> <o:p> </o:p> <div> Peter Zehler <st1:place w:st="on"><st1:PlaceName w:st="on">Xerox</st1:PlaceName> <st1:PlaceName w:st="on">Research</st1:PlaceName> <st1:PlaceType w:st="on">Center</st1:PlaceType></st1:place> Webster Email: Peter.Zehler@Xerox.com Voice: (585) 265-8755 FAX: (585) 265-7441 US Mail: Peter Zehler Xerox Corp. <st1:Street w:st="on"><st1:address w:st="on">800 Phillips Rd.</st1:address></st1:Street> M/S 128-25E Webster NY, 14580-9701 <o:p></o:p> </div> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: owner-mfd@pwg.org [mailto:owner-mfd@pwg.org] On Behalf Of William A Wagner Sent: Thursday, November 20, 2008 8:44 PM To: mfd@pwg.org Subject: MFD> overall MFD considerations<o:p></o:p> </div> <o:p> </o:p> Greetings,<o:p></o:p> <o:p> </o:p> At the October face-to-face, we had what I believe was a useful overview discussion of the interfaces to the various MFD services.  I think that, although modeling a conceptual MFD service by service is a practical way to approach this task, there is the possibility of losing  or distorting (or never having) an overall perspective.  I have redrawn the interfaces diagram,  provided some text, attempted a generalization of the terminology, and  taken a cut at a generalized ticket life diagram. These are posted at <a href="ftp://ftp.pwg.org/pub/pwg/mfd/white/MFD_Outline_Nov_00.doc">ftp://ftp.pwg.org/pub/pwg/mfd/white/MFD_Outline_Nov_00.doc</a>.<o:p></o:p> <o:p> </o:p> I have noticed some roughness in the Scan Service Terminology (I think Glen mentioned it) and a typeo:<o:p></o:p> “CrossFeed direction This is the direction perpendicular to the movement of the Hard Copy<o:p></o:p> Document or light bar of the scanner. For scanners that use a<o:p></o:p> technology other that a light bar, this is the direction along which the<o:p></o:p> image data is acquired most slowly. (See also Fast Scan direction, X<o:p></o:p> and �7.1.4) This direction is sometimes referred to as XFeed<o:p></o:p> direction.”<o:p></o:p> <o:p> </o:p> I expect  the cross-feed is the direction along which the image data is acquired most rapidly.<o:p></o:p> <o:p> </o:p> Also, although I thought I understood the ScanJobTicket Lifecycle diagram (Fig 5 in the Scan Service Spec), when Pete explained it, I admit that I found it confusing when I tried to extrapolate a generalized JobTicket diagram, particularly when also looking at earlier versions and at the Multifunction Device Overview diagram  (fig 1) in the current spec. If this looks OK to everyone else, I will figure it out.<o:p></o:p> <o:p> </o:p> I would appreciate comments on the MFD Outline white paper…whether “it’s a waste of time” or “ it’s a useful document” or whatever is appropriate in between. <o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> Bill Wagner<o:p></o:p> </div> </body> </html>