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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:st="" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <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="PlaceType"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> There will be an MFD conference call at 3:00 PM EDT (12:00 PM PDT) this Thursday.<o:p></o:p> <o:p> </o:p> Note the NEW Teleconference number and access code are now used.<o:p></o:p> Please contact me if you do not have the new numbers.<o:p></o:p> <o:p> </o:p> Agenda:<o:p></o:p> 1. Identify Minute Taker<o:p></o:p> 2. Approval of minutes from Face to Face meeting<o:p></o:p> <<a href="ftp://ftp.pwg.org/pub/pwg/minutes/pwg-ftf-mfd-minutes-20081022.pdf">ftp://ftp.pwg.org/pub/pwg/minutes/pwg-ftf-mfd-minutes-20081022.pdf</a>>   <o:p></o:p> 3. Discuss Media/MediaCol capabilities issue (See Below).<o:p></o:p> 4. Review updated Resource Service specification.  Please look at the modifications<o:p></o:p> (see –rev version) since these will be specifically discussed.  Feel free to<o:p></o:p> raise any additional comments. <o:p></o:p>  <<a href="ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdresourcemodel10-20081105.pdf">ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdresourcemodel10-20081105.pdf</a>> <o:p></o:p> 5. Next Steps<o:p></o:p> <o:p> </o:p> Click Here to Join Live Meeting <<a href="https://www.livemeeting.com/cc/xerox/join?id=PWG_MFD&role=attend&pw=PQ%25%3EFj5sN" title="blocked::https://www.livemeeting.com/cc/xerox/join?id=PWG_MFD&role=attend&pw=PQ%>Fj5sN">https://www.livemeeting.com/cc/xerox/join?id=PWG_MFD&role=attend&pw=PQ%25%3EFj5sN</a>>  <o:p></o:p> (Note: Live meeting recently released a new version.  To save time before the meeting, check your system at <<a href="http://go.microsoft.com/fwlink/?linkid=52354" title="blocked::http://go.microsoft.com/fwlink/?linkid=52354">http://go.microsoft.com/fwlink/?linkid=52354</a>><o:p></o:p> Media/MediaCol capabilities issue:<o:p></o:p> In internal prototyping efforts we came across a problem.  In higher end printer environments, and even some office environments, the size of the media database can become quite large.  Clearly printers must be able to serve up the allowed media in a capabilities request.  We have found however that it is quite problematic to have to serve up that same database each and every place that media capabilities occur (e.g.  CoverBack, CoverFront, InsertSheet, JobAccountingSheets, ProofPrint).  For the most part these capability elements need only indicate if Media and/or MediaCol are allowed in the associated processing element.  The DocumentProcessing elements Media and MediaCol allow the entire database of media to be retrieved.  Furthermore it is preferable that the media database should be explicitly requested to insure that the client is not inundated with the contents of the media database unless that is what the client desires.<o:p></o:p> Comments?<o:p></o:p> <o:p> </o:p> <o:p> </o:p> 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> <o:p> </o:p> </div> </body> </html>