attachment

<html 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"> <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="City"/> <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> All,<o:p></o:p> <o:p> </o:p> We really did not have a quorum for the MFD teleconference.   We started at three and ended up with five before adjourning.  No formal meeting minutes will be posted.   As long as we were on the phone I did capture some comments.  People with specific comments will send them to Nancy and I.   The comments on the Resource service specification that I captured were:  <o:p></o:p> <![if !supportLists]>1)       <![endif]>On page 8 under Resource Service The clause “There is an instance of Resource Service associated with each MFD Service.” should be removed.  The Resource Service is just another service on the network and it is not required to be bound to an instance of an MDF.<o:p></o:p> <![if !supportLists]>2)       <![endif]>On page 9 the Signature definition needs work.<o:p></o:p> <![if !supportLists]>3)       <![endif]>Page 7 Firmware is out of scope.  It was also pointed out that when the Template Service was generalized to a Resource Service there was a collision with the existing Resource element in the MFD model.  The installed resources for an MFD were renamed to ResidentResources.  There needs to be a discussion on the relationship between ResidentResources and the Resources accessible via a Resource Service.  This will be added to the Face to Face agenda.<o:p></o:p> <![if !supportLists]>4)       <![endif]> There is no required Resource creation function.  The PutResource operation should be mandatory.<o:p></o:p> <o:p> </o:p> I will be putting out an agenda for the upcoming face to face.  Anyone wishing to address specific items during the MFD session should send them to me.<o:p></o:p> <o:p> </o:p> The MFD Schema and WSDL files will not be modified until after the Face to Face.  The Scan Service specification will also remain unchanged until after the Face to Face.  I will leave it to <st1:place w:st="on"><st1:City w:st="on">Nancy</st1:City></st1:place> to determine if she will put out an updated document based on the comments above and those submitted via email by MFD members.<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> Pete<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>