attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.24"> <TITLE>more comments on requirements doc</TITLE> </HEAD> <BODY> Page : Line     Comment Cover   Based on Section 3.2, I believe the title should be modeled to reflect the developed.   i.e. Title  "Scan Service Model..." -> "Networked Scan Service Semantic Model..." 7 : 230 What is intent or value of this section? 7: 240  Most of consumer MFDs are not networked connected; they are typically USB or directly-host-connected.  By this statement, is the intent to eliminate consumer MFDs.   What if a low end MFD uses a host-based Scan Service to provide the same functionality described for networked MFD's.   Why does the model care where the Scan Service is hosted?  We could then refine the Scan Service to be a Host Scan Service or MFD Scan Service. 7 : 241 Why is "document format" in or out of scope for this model and requirements/ I believe that will should have a list of today's well known image formats but not having an extensible list would restrict the model.  Does the model care what the format is? 7 : 242         More group discussion on what is out-of-scope would be important to understand and defining the requirements. 7 : 245 For this use-case the entity providing the functionality is not the "(host/mfd) scan service" but the "(host/mfd) scan client".  8 : 253 "User Create a template from scan client (PC)" -> "User Creates a Scan Template from Host Scan Client" 8 : 254 Step 1: User request a new template from the Host Scan Client Step 2: The Host Scan Client request scan job description elements and associated default values from the Host or MFD Scan Service. Step 3: The Host Scan Client composes a template with default values. Step 4: The user modifies the template to meet their scan intent. Step 5: The Host Scan Client validates the user modified scan template. Step 6: The user designates the template storage location (i.e. at the Host or MFD Scan Service or a specific Template Repository) Step 7: The Host Scan Client request the Host or MFD Scan Service to store template at the specific storage location. 8: 270          " User Create a template directly with Scan Service"  -> "User Creates a Scan Template from MFD Scan Client" 8 : 271 Step 1: User request a new template from the MFD Scan Client Step 2: The MFD Scan Client request job description elements and associated default value from the Host Scan Service. Step 3: The MFD Scan Client composes a template with default values. Step 4: The user modifies the template to meet their scan intent. Step 5: The MFD Scan Client validates the user modified scan template. Step 6: [Optional] The user designates the template storage location (i.e. at the Host Scan Service or a specific Template Repository) Step 7: The MFD Scan Client request the Host Scan Service to store template at the specific storage location. (Default location is MFD). 9: 281-> 10: 311        this material may change accordingly to reflect changes above. 10 : 313        "Job Template from UI, then"  --> "Job Template from the MFD Client Service, then" 10: 320 Step 1: The User places the hard copy document on scanner platen (flatbed) or in the automatic document feeder. Step 2: From the MFD Scan Client, the user select the scan template to use for their scan job intent Step 3: The user, using the MFD Scan Client, fills out the scan template for their scan job intent Step 4: The MFD Scan Client instantiates the scan template to a scan job ticket Step 5: The MFD Scan Client sends the user's scan job ticket to the MFD Scan Service Step 6: The MFD Scan Service schedules the user scan job Step 7: (When user scan job is reached in the queue) The MFD Scan Service executes the user's scan job. Step 8: The MFD Scan Service stores the digital document at the specific storage location. Step 9: The MFD Scan Service notifies the MFD Scan Client that the scan job is complete. Step10: The MFD Scan Client notifies the user the scan job is complete based on the information in the scan job ticket. 11: 340-> 12: 367       this material may change accordingly to reflect changes above. 12 :368 - > 12:375      I am confused why the pervious use-case did not store the document somewhere; I thought it was an omission.   In the pervious use-case what happens to the electronically generated "image data".  It would appear to fall on the floor.  If we use the pervious use-case with storage added (as shown above) then this case could be dropped or the pervious use-case could be dropped and this use-case used. 14: 422 "Scan from PC..."  --> "Scan from Host......" Step 1: The User places the hard copy document on scanner platen (flatbed) or in the automatic document feeder. Step 2: The user returns to their Host computer. Step 3: From the Host Scan Client, the user select the scan template to use for their scan job intent Step 4: The user, using the Host Scan Client, fills out the scan template for their scan job intent Step 5: The Host Scan Client instantiates the scan template to a scan job ticket Step 6: The Host Scan Client sends the user's scan job ticket to the Host or MFD Scan Service Step 6: The Host or MFD Scan Service schedules the user scan job Step 7: (When user scan job is reached in the queue) The Host or MFD Scan Service executes the user's scan job. Step 8: The Host or MFD Scan Service stores the digital document at the specific storage location. Step 9: The Host or MFD Scan Service notifies the Host Scan Client that the scan job is complete. Step 10: The Host Scan Client notifies the user the scan job is complete based on the information in the scan job ticket. 15: 445 -> 15: 460      this material may change accordingly to reflect changes above. 16:475 Step 1: From the MFD Scan Client, the user select the scan template to use for their scan job intent Step 2: The user, using the MFD Scan Client, fills out the scan template for their scan job intent.  This includes noting there are multiple document with the same or different destinations. Step 3: The MFD Scan Client instantiates the scan template to a scan job ticket Step 4: The MFD Scan Client sends the user's scan job ticket to the MFD Scan Service Step 5: The MFD Scan Service schedules the user scan job Step 6: (When user scan job is reached in the queue) The MFD Scan Service begins execution of the user's scan job. Step 6a: The MFD Scan Service request the user to place the next hard copy document on scanner platen (flatbed) or in the automatic document feeder. Step 6b: The user presses the "Continue" button on the MFD. Step 6b1: The MFD Scan Service scans the individuals of the hard copy document; requesting the user to put in the next page for the case the user is using the MFD platen or the document is larger than the MFD's ADF capacity. Step 6b2: The user presses the "Stop" button when all of the document's pages have been scanned. Step 6c: The MFD Scan Service stores the digital document at the specific storage location. Step 6d: Repeat Step 6a through 6c until last document complete Step 7: The user presses the "Stop" button to indicate that there are no more documents for this scan job Step 8: The MFD Scan Service notifies the MFD Scan Client that the scan job is complete. Step 9: The MFD Scan Client notifies the user the scan job is complete based on the information in the scan job ticket. 16: 445 --> 19:551 this material may change accordingly to reflect changes above. 19: 553 I don't understand this use-case.  How will the (Host or MFD) Scan Service "discover"?   A networked device may have broad network access and there may be many locations the user has right to.   So, after scanning the user has to "fishing" for where the document is at?   <A NAME="_MailAutoSig">R</A>gds, Glen W. Petrie Epson Imaging Technology Center 2580 Orchard Parkway, Suite 200 San Jose, CA, 95131 Voice: 408.576.4131  Fax: 408.474.0511 </BODY> </HTML>