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="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)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Peter,<o:p></o:p> <o:p> </o:p> I started reading the Scan Service Specification, but out of time today.  The following are my comments up to page 10.  I am not sure this is the level of feedback you were expecting.<o:p></o:p> <o:p> </o:p> Glen<o:p></o:p> <o:p> </o:p> <o:p> </o:p> My comments<o:p></o:p> <o:p> </o:p> Page 8, Line 250 <o:p></o:p> -- change “sope” to “scope”<o:p></o:p> <o:p> </o:p> Page 10, Line 265<o:p></o:p> -- Active Jobs <o:p></o:p>     - what is the significances of the phrase “instance specific”.  Can the phrase be removed?<o:p></o:p>       It is used in other definitions.<o:p></o:p> <o:p> </o:p> -- ADF<o:p></o:p>     - In OpenPrinting work, specifically the job-ticketing API, the term “tray” referred to input <o:p></o:p>       and the term “bin” referred to output.  Thus, my comments are.<o:p></o:p> <![if !supportLists]>-          <![endif]>Line 3, change “from its bin” to “from its input tray”<o:p></o:p> <![if !supportLists]>-          <![endif]>Line 6, change “ADF bin” to “ADF output bin” <o:p></o:p> <o:p> </o:p> -- Attribute<o:p></o:p>     - I find the definition of a generic word like “Attribute” to be a little strange.<o:p></o:p>     - From the web I found this<o:p></o:p> “is an entity that defines a property of an object, element, or file. An attribute usually consists<o:p></o:p> of a name and a value. Its definition can be extended by a datatype, a representation format, <o:p></o:p> a default value and restrictions.”<o:p></o:p> <o:p> </o:p> -- CrossFeed direction<o:p></o:p>     - Should there be a space in “CrossFeed”, i.e. “Cross Feed”<o:p></o:p>     - Should “direction” be capitalized?  If it is there for clarification should it be in brackets,<o:p></o:p>       i.e. “CrossFeed (direction)”, since direction is not part of the term being define but is only<o:p></o:p>       being used for clarification<o:p></o:p>     - Line 4,  I suggest changing “(See also Fast Scan direction, X and $ 7.14)” to <o:p></o:p>       “(See diagram in $7.14)”<o:p></o:p>     - Line 5, The line should be “The Cross Feed direction is also referred to as the X, X-Feed or<o:p></o:p>                  Fast Scan direction.   I would also move this before the bracketed comment in Line 4.<o:p></o:p> <o:p> </o:p> -- DefaultScanJobTicket<o:p></o:p>     -- Are we defining the term “Default Scan Job Ticket” or the variable “DefaultScanJobTicket”.<o:p></o:p>        I would have assumed it was the term and not the variable. This comment apply to other<o:p></o:p>        “terms” in the definition table.<o:p></o:p>     -- Line 1, the phase “an instance of” implies that the Scan Service is instantiated for each job.<o:p></o:p>        1.) I don’t think this is the intent of the meaning and 2.) it implies an how to implement, which<o:p></o:p>        we should not address.<o:p></o:p>     -- Line 2-5, should the term “values” be elaborated to “Attribute values” (or “attribute values”)?<o:p></o:p> <o:p> </o:p> -- Destination<o:p></o:p>     -- Line 1, The sentence is not a complete sentence, is the phrase “end point” necessary and<o:p></o:p>        is it “URI” or “URL”?<o:p></o:p>       I suggest “A Destination is a network address (i.e. URL) of a storage ……”<o:p></o:p>     -- If the Destination is internal storage, is that really specified by a “network address”?<o:p></o:p> <o:p> </o:p> -- Digital Document<o:p></o:p>    -- Line 1, The sentence is not a complete sentence and “scan service” should be “Scan Service”.<o:p></o:p>       I suggest “A Digital Document is the output of a Scan Service containing the digitized data<o:p></o:p>                      resulting from the scanning of a Hardcopy Document(s).”<o:p></o:p> <o:p> </o:p> All/Most of the remaining definition do not have a complete first sentence.  If the intent is that the <o:p></o:p> word being defined is to be part of the first sentence, then the first word in the “definition” should <o:p></o:p> not be capitalized; otherwise, the noun (the term being defined) needs to be put into the first .  <o:p></o:p> I.e. “Digital Document    is the output”  or “Directory Service     is a”<o:p></o:p> <o:p> </o:p> -- Directory Service<o:p></o:p>     -- This definition is states or implies a lot of implementation specifies; i.e. organizes, administrator <o:p></o:p>        manages, …..   Will the MFD working group create a Directory Service Specification; if not, then<o:p></o:p>        we need to use a common definition<o:p></o:p>     -- Definitions I found on the web:<o:p></o:p>           -- A data source according to ITU specification X.500 that holds data organized in a tree structure<o:p></o:p>           -- A software service that integrates with a user/group directory<o:p></o:p>           -- A service that provides a white pages-like directory of the users and resources located on an <o:p></o:p>              enterprise network<o:p></o:p>           -- A directory service is simply the software system [application] that stores, organizes and <o:p></o:p>              provides access to information in a directory.<o:p></o:p>     ----- I like the last definition <o:p></o:p> <o:p> </o:p> -- Fast Scan direction<o:p></o:p>     - Is there a space between “Fast Scan” or is it “FastScan”.  If there is a space should <o:p></o:p>       “CrossFeed” be “Cross Feed”<o:p></o:p>     - Should “direction” be capitalized?  If it is there for clarification should it be in brackets,<o:p></o:p>       i.e. “Fast Scan (direction)”, since direction is not part of the term being define but is only<o:p></o:p>       being used for clarification<o:p></o:p>     - Line 4,  I suggest making the end of the definition match closer to “Cross Feed”<o:p></o:p>       i.e. This is the direction along which the image data is most quickly acquired. If the light <o:p></o:p>             bar or media moves, this direction is at a right angle to that movement. The Fast Scan<o:p></o:p>             direction is also referred to as the X, X-Feed or Cross Feed direction.  (See diagram $7.14)<o:p></o:p> <o:p> </o:p> -- Feed direction <o:p></o:p>     - Should “direction” be capitalized?  If it is there for clarification should it be in brackets,<o:p></o:p>       i.e. “Feed (direction)”, since direction is not part of the term being define but is only<o:p></o:p>       being used for clarification<o:p></o:p>     - Line 4,  I suggest making the end of the definition match closer to “Cross Feed”<o:p></o:p>       i.e. The Feed direction is also referred to as the Y, Y-Feed or Slow Scan direction.  <o:p></o:p>             (See diagram $7.14)<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>