Standard For Internet Printing Protocol '-actual' attributes · Web viewTemplate Repository may be embedded within a device where the Template Manager Service resides or hosted remotely.

March 10April 3, 2008wd-mfdscanmod10-2008 Working Draft

The Printer Working Group

Network Scan ServiceSemantic Model and Service Interface

Status: Interim

Abstract: Network print devices have evolved to support additional multifunction services, in particular Scan Service. When network Scan Devices are installed in local office or enterprise networks, they need remote service, device, and job management capabilities so that administrators, operators, and end users can monitor their health and status. In addition, such network Scan Devices need remote job submission capabilities so that operators and end users can create Scan Jobs without depending entirely on local console interfaces. This document defines a semantic model for service, device, and job management and job submission for these network Scan Devices.

Copyright © 2007-2008, Printer Working Group. All rights reserved.

1231234

5

6

7

8

910

11

121314151617181920

2122232425

2627

28

29

3031

32

4

MFD: Scan Service March 10April 3, 2008

Copyright (C) 2007-2008, The Printer Working Group. All rights reserved. This document may be copied and furnished to others, and derivative works that comment on, or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice, this paragraph and the title of the Document as referenced below are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Printer Working Group, a program of the IEEE-ISTO.

Title: Network Scan Service Semantic Model and Service Interface

The IEEE-ISTO and the Printer Working Group DISCLAIM ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED INCLUDING (WITHOUT LIMITATION) ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

The Printer Working Group, a program of the IEEE-ISTO, reserves the right to make changes to the document without further notice. The document may be updated, replaced or made obsolete by other documents at any time.

The IEEE-ISTO and the Printer Working Group, a program of the IEEE-ISTO take no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights.

The IEEE-ISTO and the Printer Working Group, a program of the IEEE-ISTO invite any interested party to bring to its attention any copyrights, patents, or patent applications, or other proprietary rights, which may cover technology that may be required to implement the contents of this document. The IEEE-ISTO and its programs shall not be responsible for identifying patents for which a license may be required by a document and/or IEEE-ISTO Industry Group Standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Inquiries may be submitted to the IEEE-ISTO by e-mail at:

[email protected]

The Printer Working Group acknowledges that the IEEE-ISTO (acting itself or through its designees) is, and shall at all times, be the sole entity that may authorize the use of certification marks, trademarks, or other special designations to indicate compliance with these materials.

Use of this document is wholly voluntary. The existence of this document does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to its scope.

Copyright © 2007-2008, Printer Working Group. All rights reserved. Page 2 of 85

56

333435363738

39

404142

4344

45464748

495051525354

55

565758

596061

78


About the IEEE-ISTO

The IEEE-ISTO is a not-for-profit corporation offering industry groups an innovative and flexible operational forum and support services. The IEEE Industry Standards and Technology Organization member organizations include printer manufacturers, print server developers, operating system providers, network operating systems providers, network connectivity vendors, and print management application developers. The IEEE-ISTO provides a forum not only to develop standards, but also to facilitate activities that support the implementation and acceptance of standards in the marketplace. The organization is affiliated with the IEEE (http://www.ieee.org/) and the IEEE Standards Association (http://standards.ieee.org/).

For additional information regarding the IEEE-ISTO and its industry programs visit:http://www.ieee-isto.org.

About the Printer Working Group

The Printer Working Group (or PWG) is a Program of the IEEE-ISTO. All references to the PWG in this document implicitly mean “The Printer Working Group, a Program of the IEEE ISTO.” The PWG is chartered to make printers and the applications and operating systems supporting them work together better. In order to meet this objective, the PWG will document the results of their work as open standards that define print related protocols, interfaces, data models, procedures and conventions. Printer manufacturers and vendors of printer related software would benefit from the interoperability provided by voluntary conformance to these standards.

In general, a PWG standard is a specification that is stable, well understood, and is technically competent, has multiple, independent and interoperable implementations with substantial operational experience, and enjoys significant public support.

Contact information:

The Printer Working Groupc/o The IEEE Industry Standards and Technology Organization445 Hoes LanePiscataway, NJ 08854USA

MFD Web Page: http://www.pwg.org/mfd MFD Mailing List: [email protected]

Instructions for subscribing to the MFD mailing list can be found at the following link: http://www.pwg.org/mailhelp.htmlMembers of the PWG and interested parties are encouraged to join the PWG and MFD WG mailing lists in order to participate in discussions, clarifications and review of the WG product.


91062

63646566676869

70717273

747576777879

808182

83

848586878889909192939495

1112

http://www.pwg.org/mailhelp.html

mailto:[email protected]

http://www.ieee-isto.org/

http://standards.ieee.org/)

http://www.ieee.org/


Contents

1 Introduction.................................................................................................................................................. 87

2 Summary..................................................................................................................................................... 87

3 Terminology................................................................................................................................................. 983.1 Conformance Terminology................................................................................................................................. 983.2 Content Specific Terminology.......................................................................................................................... 109

4 Rationale................................................................................................................................................. 13124.1 Rationale for this Scanning Service Specification..........................................................................................13124.2 Out of Scope for Scan Service.......................................................................................................................13124.3 Model mapping conventions........................................................................................................................... 1312

5 Scan Job Ticket Lifecycle........................................................................................................................ 1413

6 Scan Service Model Overview.................................................................................................................15146.1 Relationships.................................................................................................................................................. 16156.2 Job/Document Object and Digital Document Cardinality................................................................................17166.3 Content Coordinate system............................................................................................................................ 1817

6.3.1 Scan Device Coordinates...........................................................................................18176.3.2 Scan Service Coordinates..........................................................................................19186.3.3 Document Format Coordinates..................................................................................20196.3.4 Coordinate Nomenclature..........................................................................................2120

6.4 Scan Service Model Description..................................................................................................................... 21206.4.1 Default Scan Ticket....................................................................................................21206.4.2 Scan Service Capabilities..........................................................................................2221

This element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability...............................................................30296.4.3 Scan Service Configuration........................................................................................30296.4.4 Scan Service Description...........................................................................................41406.4.5 Service Status............................................................................................................4342

6.5 Scan Job Model.............................................................................................................................................. 49486.5.1 Scan Job Receipt.......................................................................................................50496.5.2 Scan Job Status.........................................................................................................50496.5.3 Scan Job Ticket..........................................................................................................5453

6.6 Scan Document Model................................................................................................................................... 64636.6.1 Scan Document Receipt............................................................................................64636.6.2 Scan Document Status..............................................................................................64636.6.3 Scan Document Ticket...............................................................................................6867

7 Scan Service Theory of Operation...........................................................................................................7069

8 Scan Service Interfaces........................................................................................................................... 71708.1 Basic Scan Service Operations...................................................................................................................... 7170

8.1.1 CancelJob..................................................................................................................71708.1.2 CloseScanJob............................................................................................................72718.1.3 CreateScanJob..........................................................................................................72718.1.4 GetActiveJobs............................................................................................................72718.1.5 GetJobHistory............................................................................................................73728.1.6 GetScanJobElements................................................................................................74738.1.7 GetScanDocumentElements......................................................................................74738.1.8 GetScanServiceElements..........................................................................................74738.1.9 ValidateScanTicket....................................................................................................7574

8.2 Administrative Scan Service Operations........................................................................................................7574


131496

97

98

99100101

102103104105

106

107108109110

111112113114115

116117118119120121122123

124125126127

128129130131

132133

134135136137138139140141142143

1516


8.2.1 DisableScanService...................................................................................................75748.2.2 EnableScanService....................................................................................................76758.2.3 HoldJob......................................................................................................................76758.2.4 HoldNewJobs.............................................................................................................77768.2.5 Pause.........................................................................................................................77768.2.6 PauseAfterCurrentJob................................................................................................78778.2.7 PromoteJob................................................................................................................78778.2.8 ReleaseJob................................................................................................................78778.2.9 ReleaseNewJobs.......................................................................................................78778.2.10 ReprocessJob............................................................................................................78778.2.11 RestartJob..................................................................................................................78778.2.12 Resume......................................................................................................................78778.2.13 Shutdown...................................................................................................................78778.2.14 Startup........................................................................................................................7877

8.3 Scan Job Template Manager Operations.......................................................................................................78778.3.1 DeleteTemplate..........................................................................................................78778.3.2 GetTemplate..............................................................................................................79788.3.3 ListTemplates.............................................................................................................80798.3.4 PutTemplate (TemplateName, RequestingUserName, OverwriteFlag).....................80798.3.5 SetTemplateAccessRights (Template).......................................................................80798.3.6 SetTemplateExpiration (Template).............................................................................80798.3.7 ValidateTemplate (Template).....................................................................................8079

9 Conformance Requirements....................................................................................................................8079

10 PWG and IANA Registration Considerations...........................................................................................8079

11 Internalization Considerations................................................................................................................. 8079

12 Security Considerations........................................................................................................................... 818012.1 Storing Scan Documents in a Document Repository......................................................................................818012.2 Protection of End User’s Scan Documents....................................................................................................818012.3 Protection of a “Restricted Use” Scan Job Template......................................................................................818012.4 Restricted Use of Scan Service Features.......................................................................................................818012.5 Preventing DoS Attack Through High Priority Job..........................................................................................828112.6 Security for Service Discovery.......................................................................................................................8281

13 References.............................................................................................................................................. 828113.1 Normative References.................................................................................................................................... 828113.2 Informative References.................................................................................................................................. 8382

14 Author’s Address..................................................................................................................................... 8382

15 Change Log............................................................................................................................................. 8483

Figures


1718

144145146147148149150151152153154155156157158

159160161162163164165166

167

168

169170171172173174175

176177178

179

180181182

183

1920


Figure 1 Scan Job Lifecycle Diagram.................................................................................................................................. 14

Figure 2 High Level Scan Service Schema......................................................................................................................... 15

Figure 3 Object Relationships............................................................................................................................................. 17

Figure 4 Scan Device Coordinates...................................................................................................................................... 19

Figure 5 Scan Service Coordinates..................................................................................................................................... 20

Figure 6 Document Format coordinates.............................................................................................................................. 21

Figure 7 Default Scan Ticket............................................................................................................................................... 22

Figure 8 Scan Service Capabilities...................................................................................................................................... 22

Figure 9 Scan Documents Processing Capabilities.............................................................................................................23

Figure 10 Exposure (Capability).......................................................................................................................................... 24

Figure 11 Scan Job Description Capabilities.......................................................................................................................27

Figure 12 Scan Job Processing Capabilities....................................................................................................................... 29

Figure 13 Scan Service Configuration................................................................................................................................. 31

Figure 14 Console............................................................................................................................................................... 32

Figure 15 Covers................................................................................................................................................................. 33

Figure 16 InputChannel....................................................................................................................................................... 34

Figure 17 Interface.............................................................................................................................................................. 35

Figure 18 Output Channel................................................................................................................................................... 36

Figure 19 Output Tray......................................................................................................................................................... 38

Figure 20 ScanMediaPath................................................................................................................................................... 39

Figure 21 Scanner Subunit.................................................................................................................................................. 40

Figure 22 Scan Service Description.................................................................................................................................... 42

Figure 23 Scan Service Status............................................................................................................................................ 44

Figure 24 Top Level Service State Transition Diagram.......................................................................................................46

Figure 25 Detailed Service Transition Diagram...................................................................................................................48

Figure 26 High Level Scan Job View................................................................................................................................... 50

Figure 27 Scan Job Status.................................................................................................................................................. 51

Figure 28 Job State Transition Diagram.............................................................................................................................. 53

Figure 29 Scan Job Ticket................................................................................................................................................... 54

Figure 30 Scan Documents Processing.............................................................................................................................. 55

Figure 31 Scan Region........................................................................................................................................................ 59

Figure 32 Scan Job Processing........................................................................................................................................... 63

Figure 33 High Level Scan Document View........................................................................................................................ 64

Figure 34 Scan Document Status........................................................................................................................................ 65

Figure 35 Document State Transition Diagram...................................................................................................................67

Figure 36 Scan Document Ticket........................................................................................................................................ 68

Figure 37 Scan Document Description................................................................................................................................ 69


2122

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

2324

MFD: Scan Service February April 253, 2008

1 IntroductionThis document specifies the PWG abstract model for scanning services of a MultiFunctionMultifunction Device (MFD). Included in this document is the content specific terminology, data model, the theory of operation, the scanning service interfaces and the conformance requirements. The MFD scanning service abstract models include the functional models and interfaces of the associated scanning services for a local or enterprise network connected multifunction device.

2 SummaryThe MFD scanning services addressed in this specification are, specifically, the Scan Service and the Scan Template Manager Template Manager Service. The Scan Service responds to queries about its capabilities, configuration and descriptive information. It responds to queries for information about the Scan Jobs and their associated Documents. It manages and processes Scan Jobs with its associated Scan Job Ticket and stores the digital output. The Scan Template Manager Template Manager Service allows clients to store, retrieve and manage Scan Job Templates. A network scanning client application contains a Scan Client and optionally a Scan Template Manager Template Manager Client. A network scanning client application interacts with the end user to obtain the end user’s Scan Intent and uses a Scan Client toClient to communicate with the Scan Service that will execute the end user’s Scan Intent. A network scanning client application may contain a Scan Template Manager Template Manager Client that obtains Scan Templates from the the Scan Template Manager Template Manager Service. Scan Templates contain instructions representing preconfigured scan intent that can be used as is or modified by the end user. Once the end user is satisfied with the Scan Template the network scanning client application passes the Scan Job Template to the Scan Job Client for submission to the Scan Service.

The scanning scenarios addressed in this specification ranges from walk-up scanning using the MFD’s front panel to remote scanning from an end user’s computer to support for document on-ramp scanning using enterprise workflow applications. When shared by a workgroup using different functions of the MFD, the model supports interruption of a large Scan Job to perform other MFD functions including a different Scan Job. For batch job scanning of either single or multiple documents, the model supports automated scanning of a stack of documents separated by an individual Scan Instruction Sheet. The model also supports external security services that protects against unauthorized use of the scanning services and access of scanned digital data.

Copyright © 2007-2008, Printer Working Group. All rights reserved. Page 7 of

2526

222

223224225226227228

229

230231232233234235236237238239240241242243244245246247248249250

27


3 Terminology

3.1 Conformance TerminologyCapitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, MAY, RECOMMENDED and OPTIONAL, have special meaning relating to conformance as defined in RFC 2119 [RFC2119].

MUST This word meanThis word means that the definition is an absolute requirement of the specification.

REQUIRED This word meanThis word means that the definition is an absolute requirement of the specification.

SHALL This word meanThis word means that the definition is an absolute requirement of the specification.

MUST NOT phrase meanThis phrase means that the definition is an absolute prohibition of the specification.

SHALL NOT This phrase meanThis phrase means that the definition is an absolute prohibition of the specification.

SHOULD This word meanThis word means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

SHOULD NOT This phrase mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.

RECOMMENDED This word meanThis word means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

NOT RECOMMENDED This phrase mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.

MAY This word meanThis word means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)

OPTIONAL This word meanThis word means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared


2829

251

252

253254255

30


to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)

3.2 Content Specific Terminology

Term Definition

Active Jobs A Scan Service instance specific queue containing all the Scan Jobs that are waiting to be processed or are currently processing.

ADF Automatic Document Feeder. A mechanism for handling Hard Copy Documents for scanning. The mechanism selects a page from its bin and passes it to the image acquisition subsystem of the Scan Device. After the Scan is complete the ADF transports the Hard copy Document page to its final destination (e.g. output bin, ADF bin)

Attribute Attributes can decorate XML Elements and contains additional information about an Element.

Cross Feed direction This is the direction perpendicular to the movement of the Hard Copy Document or light bar of the scanner. For scanners that use a technology other that a light bar, this is the direction along which the image data is acquired most slowly. (See also Fast Scan direction, X and §6.3.4) This direction is sometimes referred to as XFeed direction.

Default Scan Job Ticket A Scan Job Ticket data object that is bound to an instance of a Scan Service. The values contained in the Default Scan Job Ticket are the values that that will be used by the Scan Service when processing a Scan Job whose Scan Job Ticket does not specify a different value...

Destination URL Alternative term for Scan Destination. (See Scan Destination below)

Digital Document The output of a scan service containing the digitized data resulting from the scanning of Hardcopy Document(s). The images from the scanned Hardcopy Document(s) are encoded in an image or document format and stored at a Scan Destination.

Directory Service A software application or a set of applications that stores and organizes information about a computer network’s users and resources, and that allows network administrators to manage user’s accesses to the resources.

Discovery Client A software application that performs service or resource discovery on a computer network.

Document Repository A local or remote data store where Digital Documents are stored by the Scan Service.

Element Elements are used to convey structure and relationships in XML document instances. An Element can contain both content and Attributes.

Fast Scan direction This is the direction along which the image data is most quickly acquired. If the light bar or media moves, this direction is at a right angle to that movement. (See also Cross Feed direction and X)

Feed direction This is the direction along which the light bar of the scanner moves relative to the Hard Copy Document. For scanners that use a


3132

256

257

258

33


Term Definition

technology other that a light bar this is the direction along which the image data is acquired most slowly. (See also Slow Scan direction, Y and §6.3.4)

Group Element A collection of Elements that constitutes a complex Element.

Hardcopy Document A physical document in the form of paper, transparency, film, …,… etc. that is the input source for a Scan Job. The Hardcopy Document is scanned by the Scan Device and the images transformed by the Scan Service into a Digital Document and stored in at the Scan Destination within a Document RespositoryRepository.

Image A digital (i.e. binary) representation of the information captured by a Scan Device. One Image is produced as a result of a Scan Device scanning a Scan Region.

Job History A Scan Service instance specific queue containing all the Scan Jobs that have reached a terminating state. The terminating states are defined as Completed, Aborted and Canceled. The length of this queue is determined by the implementer. The Scan Jobs SHOULD remain is the Job History for a reasonable period time to permit interested parties to obtain information on completed jobs.

Local Client Alternative term for Local Scan Client. (See Local Scan Client and Scan Client below.)

Local Scan Client The Scan Client application within the MFD. (See Scan Client below.)

Physical Scan Document Ticket

AAn encoded hardcopy Scan Document Ticket, directly marked by the end user, that becomes a Scan Document Ticket data object after being scanned and processed.

Physical Scan Job Ticket An encoded hardcopy Scan Job Ticket, directly marked by the end user, that becomes a Scan Job Ticket data object after being scanned and processed.

Remote Scan Client The Scan Client application external to the MFD. (See Scan Client below.)

Scan Client The local or remote software entity that interfaces with the end user and interacts with a Scan Service.

Scan Destination The end point network address (i.e. URL) of a storage location for the Digital Document of a Scan Job.

Scan Device The MFD subsystem that is responsible for image acquisition and media handling (i.e. the scanner).

Scan Document The data object managed by a Scan Service that contains document level description, processing, status information of a document within a Scan Job.

Scan Document Data This term is used interchangeable with Digital Document throughout this specification. (See Digital Document above)

Scan DocumenyDocument Ticket

A data object that contains document processing and descriptive properties of a Scan Document. Any document processing properties in the Scan Document Ticket will override the values specified in the Scan Job Ticket’s document processing properties. The content of a Scan Job Document Ticket is configured by end user through a Scan Client.

Scan Intent The end user’s preferences for the processing and description


3435

36


Term Definition

properties of a Scan Job.

Scan Job A data object, created and managed by a Scan Service, that contains the description, processing, and status information of a job submitted by a user. The Scan Job can contain one or more document objects. The purpose of a Scan Job is to acquire the digital content (images) of scanned Hardcopy Documents and store them at a specified destination in a specified document format

Scan Job Receipt An element of the Scan Service that contains information on the actual values of processing elements used by the Scan Service for processing a Scan Job. The content of a Scan Job Receipt is populated by the Scan Service when a Scan Job is processed.

Scan Region A rectangular region of the Scan Device’s Platen that has been specified by an Administrator or End User as the bounding area in which a scan will occur.

Scan Job Ticket A data object that contains document processing, job processing and descriptive job properties of a Scan Job. The job elements apply to the entire JScan Job. The document processing elements will be used for all the documents within the Scan Job unless overridden at the document level (See Scan Document Ticket). The content of a Scan Job Ticket is configured by end user through a Scan Client.

Scan Job Template A Scan Job Ticket data object that is not bound to a Scan Service or Scan Job. Scan Job Template can be stored or retrieved from the Scan Template Manager Template Manager Service collocated on the MFD or hosted on a remote system.

Scan Service A software service that accepts and processes requests to create, monitor and manage Scan Jobs. The software service accepts and processes requests to monitor and control the status of the service itself and its associated resources... A Scan Service is hosted either locally or remotely to the MFD,

Sequence An ordered list of elements.

Slow Scan direction This is the direction along which the image data is acquired most slowly. If the light bar or media moves, this direction is parallel to that movement. (See also Feed direction, Y and §6.3.4)

Template Manager Service A software service that provides the Scan Client the interfaces for, storing, retrieving, and maintaining their Scan Job Templates. The Templates associated with a Scan Service is a Scan Job Template.

Template Repository A persistent storage for storing Scan Job Templates. Access to the Template Repository is through the Template Manager Service. Template Repository may be embedded within a device where the Template Manager Service resides or hosted remotely.

X An axis of the coordinate system. This axis is associated with the Fast Scan direction of the Scan Device. If the light bar or Hard Copy Document moves, they do not move in the X direction. They move in the Y direction. (See also Cross Feed direction, Fast Scan direction and §6.3.4)

Y An axis of the coordinate system. This axis is associated with the slow scan direction of the Scan Device. If the light bar or Hard Copy Document moves, they move in Y direction. (See also Feed direction, Slow Scan direction and §6.3.4)


3738

25939


4 Rationale

4.1 Rationale for this Scanning Service Specification

In order to support common functionality for scanning using network multifunction devices, there is a clear need to develop a semantic model and a set of abstract operations and elements for scanning related services. In order to implement an abstract model of the operations and elements for scanning related services, there is need to map them onto implementable applications and communication protocols that support interactions between Scan Clients and Scan Services. There is a clear need to define a binding of the abstract model into Web Service Schema and Web Service protocol stack.

4.2 Out of Scope for Scan ServiceThe basic scanning service model defined in this document is targeted to support enterprise scan applications. However this document does not specify any application specific semantics. The MFD Working Group charter defines the following as out of scope:

1. Semantics of any compound service such as Scan-To-Email, Scan-To-Fax, Scan-To-Mailbox, or Scan-To-Print of which the additional semantics associated with accessing the specific document repositories will be defined in other services, not included in the scanning services.

2. Semantics of any workflow protocol, i.e., sequencing and coordination of scanning jobs across multiple services.

3. Semantics of any scanning service management operations for MFDs that are not network connected.4. Semantics for the creation of new document or file formats.

4.3 Model mapping conventionsThe Scan Service model is described in this document as an XML schema. This is for the sake of convenience and does not require a protocol mapping involving XML. The top level objects such as the Subunits, the Services, and their associated Jobs and Documents can be represented in any number of ways. Abstractly they are objects which contain attributes or properties that express characteristics of the object. For the remainder of this document references to Attribute or Element refer to XML Attributes and XML Elements respectively. Either of these can be abstractly considered to be attributes or properties of abstract objects.


4041

260

261

262263264265266267268269

270271272273274275276277278279280281282

283284285286287288289

42


5 Scan Job Ticket Lifecycle

Figure 1 Scan Job Lifecycle Diagram

A Scan Job Ticket is a data object that contains job descriptions and job and document processing instructions. The Scan Job Ticket life cycle begins when a Scan Client initiates a Scan Job. A Scan Job is initiated when an end user pushes the “start scan” button. The Scan Service creates a Scan Job. A local Scan Job Template is created from a Scan Service’s Default Scan Job Ticket, or a user supplied Scan Job parameters filled in with the End User’s Scan Intents., When the Scan Service binds the local Scan Job Template to the job, the result is a Scan Job Ticket. A Scan Job Template is a Scan Job Ticket, unbound to any Scan Job or Scan Service, pre-created by an end user or someone for other end users, for the convenience or purpose of submitting future Scan Jobs. A Scan Job Template can be created in one of the following ways:

(1) A walk-up end user uses Local application and User Interface to create a Scan Job Template by configuring a set of preferred values for job and document processing and job description. The local Scan Template Repository Client is used to store the Scan Job Template in the Scan JobScan Job Template Repository. The template is uniquely identifiable and stored in a MFD internal repository or a remote system.


4344

290291

292

293

294

295296297298299300301302303304305306307308309310

45


(2) Same as (1) but instead of a walk-up end user, an organization’s designate creates Scan Job Templates for all end users.

(3) Same as (1) but an end user uses a remote application (in a computer) to create Scan Job Templates and a Remote Scan Template Repository Client is used to store the Scan Job Template in the Scan Job Template Repository.

(4) Same as (3) but an organization’s designate uses a remote application (in a computer) to create Scan Job Templates for all end users. A Remote Scan Template Repository Client is used to store the Scan Job Template in the Scan JobScan Job Template Repository.

If an end user did not select a Scan Job Template, a Scan Job Ticket is created from the default Scan Job Ticket, which is an Element of the Scan Service. The default Scan Job Ticket can be administratively modified to control default behaviors for the associated Scan Service.

As a Scan Job Ticket is created, it is bound to the end user’s Scan Job by the Scan Service. Then the Scan Service manages and processes the Scan Job according to the instructions supplied in the Scan Job Ticket, including file format of the output Digital Document and the location for storing the Digital Document, be it an internal or an external Document Repository . If a processing instruction in the Scan Job Ticket can not be supported, the Scan Service either returns an error or substitutes the instruction with another that best matches the user’s intent. The actual values used for processing the job are captured in the Scan Job Receipt of the Job in the Job History queue, which can be queried later.

After a Scan Job is completed, it is moved to the Job History queue. A Scan Job is deleted from the Scan Service when it is deleted from the Job History according to a set of site-specific Job History retention rules.

The Scan Job Ticket lifecycle ends as soon as the job ticket is deleted along with the Scan Job.

6 Scan Service Model OverviewBelow is the top level view of the Scan Service.

Figure 2 High Level Scan Service Schema


4647

311312313314315316317318319320321322323324325326327328329330331332333334335

336

337338

339

340

34148


The PWG semantic model supports zero or more Scan Services. A Scan Service is hosted locally on an MFD or remotely on another computer. The Scan Service model has an Active Job queue, a Job History and a set of Elements which includes Scan Service status, configuration, description, defaults, and processing capabilities.

The ScanServiceStatus Group Element is an extension of the PWG service status class that includes elements such as ID, state, service counters, state messages and state reasons. State messages are localized state reasons. The only Scan Service specific status extensions are the Scan Service specific counters. The details of the Elements in the ScanServiceStatus group are specified in Section §6.4.4.

The ScanServiceDescription Group Element includes descriptive information such as service name and information, and has extension point for vendor specific information. These Description Elements are settable by Administrators. Similar to Scan Service state elements, there are localized description Elements for each supported description Element. The details of the ScanServiceDescription Elements are specified in section §6.4.3.

The ScanServiceCapabilities Group Element represents the allowed values supported by the Scan Service for a Scan Job Ticket. The Element includes two sub Elements: the ScanDocumentCapabilities Group Element has all processing Elements for Scan Documents, and the ScanJobCapabilites Group Element includes all supported processing Elements for Scan Jobs. The details of each processing Element are specified in Section §6.4.2.

The DefaultScanTicket Group Element contains scan description and job and document processing default values. The values contained in the Default ScanJobTicket are the values that that will be used by the Scan Service when processing a Scan Job whose Scan Job Ticket does not specify a different value... The values for this are populated in an implementation specific manner. The details of the DefaultScanTicket are specified in section §6.4.1

The ScanService Configuration provides a Scan Service specific view into the Subunits that are associated with this service instance. Only Subunits that are used by the Scan Service will appear in this element. The details of each subunit are detailed in section §. To see all the subunits for the MFD the System element provides aan all encompassing view.

A Scan Service contains zero or more jobs. Each job has a zero or more Documents which reference a Scan Destination where the Digital Document(s) are stored as files. The Scan Service organizes its Scan Jobs in a minimum of two job queues: (1) ActiveJobs ,ActiveJobs, (2) JobHistory. ActiveJobs is a queue maintaining a list of jobs that are pending or processing. The JobHistory queue maintains a log of Scan Jobs that have completed processing.

6.1 Relationships

The diagram below provides a pictorial view of the relationships between the various objects and data items. As mentioned above a Scan Service can contain multiple Scan Jobs. In practice the Jobs appear in one of two queues. One is for pending and active jobs and the other for completed jobs. Each Scan Job can contain multiple Scan Documents. During Job creation there can be a point in time where a Scan Job does not yet have a Scan Document. It is also possible for a Scan Job to contain multiple Scan Documents. Scan Documents are associated with Digital Documents that contain the data from the scanned Hardcopy Documents. (See section §6.2 for a description of the Job/Document/Digital Document cardinality)The input to the Scan Service is a set of Hardcopy Document. A Scan Region identifies the portion of the Hardcopy Document to be scanned and converted into an image. It is possible to identify multiple Scan Regions on a media sheet side. Each Scan Region has a one to one mapping to a scanned image. The Scan Service uses the Scan Device to scan the Scan Region and converts the aquiredacquired data into an image. The representation of the image at this point is implementation specific. The Scan service accumulates the set of images that represent the input Hardcopy Document. In an implementation specific manner the set of images are encoded into the specified Document Format. Document Formats include image specific formats such as jpeg. The Digital Document which is in the specified Document Format is stored by the Scan Service to the specified Scan Destination. The next section covers the cardinality of the Digital Document.


4950

342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375

376

377378379380381382383384385386387388389390391392393394

51


Figure 3 Object Relationships

6.2 Job/Document Object and Digital Document CardinalityThe relationship between input Hardcopy Documents, the Scan Job, Scan Document and Digital document are described below. The Scan Service semantic model may allow the end user to specify any of the following types of Job, Documents and files(files (i.e. Digital Document) as the final output of scannningscanning Hardcopy Document(s):


5253

395

396

397398399400401

402

54


SDSF (Single Document Single File Job): One document object that contains a reference to one single file. There is one file URL for the single document location. The scan destination is the document URL; i.e. the single file URL.

SDMF (Single Document Multiple File Job): One document object that contains references to multiple files. Each image in the document data is stored in a separate file. There is one file URL per image file which constitutes the document. The scan destination is the directory URL of the files for the document.

MDSF (Multiple Document Single File Job): Job object contains multiple Document objects. Each document can have different set of processing parameters from another. Each file contains a specified number of images for the document. Each such set of images is stored in a separate file. The document object contains one file URL for the image file location.

MDMF (Multiple Document Multiple File Job): Job object contains multiple document objects. Each document can have different set of processing parameters from another. Each image in the document data is stored in a separate file. The document object contains a file URL for each image file location. The scan destination is the directory URL for the document.

Note: A completed Scan Job has 1~n document objects. A Scan Job has a unique ID within a unique Scan Service. The documents are numbered 1 to N within the Job. The scan destination of a multi-document job is a directory for multi-document files. After the document file is stored, the document file URL will be updated in the document object as the document location. Note: In addition to URL, the MIME type of a stored document MUST be specified by the end user to clearly indicate the content type to be used for transporting the stored document.

The Scan Service supports MUST support the type SDSF Job in which the document data for the only document in the job is stored in a single file. The capablilitycapability of a Scan Service to support the various Document/File cardinalities is declared in the DocumentOutputMode in the ScanJobProcessingCapabilities element. The value of the DocumentOutputMode which is set in the Scan Job Ticket allows an End User to request one of the supported values. The detail of scan queues and Scan Document are specified in Section §6.6.

Scan Service MUST supports the interfaces that enable creation of a Scan Job, canceling and listing jobs, obtaining service elements ,elements, obtaining job elements, and validate a scan ticket. A Scan Service MAY support administrative operations for Scan Service startup, shutdown, enable, disable, activate, deactivate, pause, pause after current job, and resume. A Scan Service MAY supportJobsupport Job related administrative operations to hold a job, hold a new job, promote a job, release a job, release a new job.

The ScanTemplate Mmanagement Service MUST support operations for Scan Job Templates to be stored, deleted, retrieved, and listed...

6.3 Content Coordinate systemBelow are descriptions of the coordinate systems and units of measures for the Scan Device and Scan Service. The output of a Scan Service, the Digital Document, is discussed as it relates to the semantic of the layout affecting Document Processing elements. An example would be the rotation of an image that is stored in a document format that has a “bounding box” in which an image can be placed. The document format is discussed to provide a consistent semantics for the placement of an image smaller than the “bounding box” or the cropping of an image larger than the “bounding box”.

6.3.1 Scan Device Coordinates


5556

403404405

406407408409

410411412413414

415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447

448449450451452453454455

456

45757


The diagram below shows the coordinate system that is used for a Scan Device. The content of the media is assumed to be facing the reader. The scan operation begins at the leading edge of the cross feed (i.e. Xfeed) and proceeds down the page. The arrow on the left indicates the movement of the media relative to the scan head. Usually the platen is marked with an arrow that points to the leading edge. The arrow on the platen does not necessarily point to the origin of the coordinate system.

Figure 4 Scan Device Coordinates

6.3.2 Scan Service Coordinates

The diagram below shows the coordinate system that is used for a Scan Service. The content of the media is assumed to be facing the reader. The scan operation begins at the leading edge of the Fast Scan (i.ei.e. X) direction and proceeds down the page in the Slow Scan (i.e. Y) direction. The coordinate system for the Scan Device and Scan Services are linked together. In other words the origin of the Scan Device’s coordinate system is the same as the origin of the Scan Service’s coordinate system. The Scan Region is specified relative to the origin of the coordinate system. It is possible to have multiple overlapping Scan Regions. The result of a Scan Service scanning a Scan Region is an image.


5859

458459460461462463

464

465

466467

468

469470471472473474475476

60


Figure 5 Scan Service Coordinates

6.3.3 Document Format Coordinates

When the output of a Scan Service is stored as an image file, there is no need to discuss the Document Format coordinates. The image file contains the entire scanned image. However when the output of a Scan Service is stored in some Document Formats (e.g. PDF, XPS) the entire image may not be stored. This is due to the fact that some document formats contains a construct that bounds the area where the image can be placed. Below is the diagram for the Document Format. The image box is where the image will be placed. The Media Box delineates the area where the image can appear in the output document. If the X Offset and Y Offset are absent or set to 0 the origin of the coordinate systems for the Image Box and Media Box are aligned.


6162

477

478

479

480

481482483484485486487488489

63


Figure 6 Document Format coordinates

6.3.4 Coordinate NomenclatureThroughout this specification there appears to be some inconsistency in the names associated with coordinate related semantics. The Scan Service Model is actually a subset of a complete Multifunction Device Model. The goal in a comprehensive multifunction device model is that once a semantic element is defined someplace within the model, it is reused throughout the model. The semantics regarding the coordinate system are affected by this reuse. We have scanner specific semantics (e.g. Fast Scan Direction), Media related semantics (e.g. width), as well as general image processing semantics (e.g. X). These terms are related. The terms CrossFeed, XFeed, FastScan, X, and Width are semantically aligned. They refer to the axis which is perpendicular to the movement of the Hard Copy Document or Scanner’s light bar. It is also the axis along which the image data is acquired most quickly. . The terms Feed, SlowScan, Y, and Height are semantically aligned. They refer to the axis which is parallel to the movement of the Hard Copy Document or Scanner’s light bar. It is also the axis along which the image data is acquired most slowly.

6.4 Scan Service Model Description

6.4.1 Default Scan TicketThe DefaultScanTicket provides the values that will be used if the element is omitted in a Scan Job’s Job Ticket. Note that the processing instructions are not bound to the Scan Job until the Scan Job is actually processed. The values from the Default Scan Ticket are not copied to the Job’s Scan Ticket. If the Scan Receipt is supported, the combined elements from the user supplied Scan Ticket and the applied values from the Default Scan Ticket are copied to the Scan Receipt.


6465

490

491

492

493494495496497498499500501502503504

505

506507508509510511

66


Figure 7 Default Scan Ticket

For descriptions of the elements that comprise ScanJobDescription, ScanJobProcessing and ScanDocumentProcessing see section §6.5.3 on ScanJobTicket below.

6.4.2 Scan Service CapabilitiesThe ScanServiceCapabilities provides information about the elements that can be used in Scan Job Tickets. Although the elements have the same name as their ScanJobTicket counterparts the syntax is often different. For example a Scan Job Ticket such as InputSource that is a single keyword is a sequence of keywords in Scan Service Capabilities. The values list the allowed values for the Job Ticket element. Some Scan Job Ticket elements that are an integer are a range of integers in Scan Service Capabilities. Other elements that are simple strings or predefined ranges in the Scan Job Ticket are simply boolean values in Scan Capabilities to represent the Scan Job Ticket element isvalues in Scan Capabilities to represent the Scan Job Ticket element are supported.

Figure 8 Scan Service Capabilities

6.4.2.1 Scan Document Processing CapabilitiesThe ScanDocumentCapabilities provides information about the document processing elements that can be used in Scan Job Tickets. See §6.5.3.1 for details on semantics of the Document Processing elements.Note that ScanDocumentCapabilities consists of two sequences. The first represents elements inherited from the Imaging Service super class and includes elements such as NumberUp and OrientationRequested. The second sequence includes Scan Service specific extensions to the super class such as Exposure and Resolution.


6768

512

513

514

515516517518

519520521522523524525526

527

528

529

530531532533534535536

69


Figure 9 Scan Documents Processing Capabilities

6.4.2.1.1 NumberUpThis is a list of page numbers that indicates whether the ScanDocumentsCapabilitiesScanDocumentCapabilities of a Scan Service supports multiple input pages to be imaged on one impression.

6.4.2.1.2 OrientationRequestedISSUE: Should the Scan Service use rotation in place of this processing instruction?Indicates the types of orientation supported by the Scan Service. (Keywords: Portrait, Landscape, ReverseLandscape, ReversePortrait).


7071

537

538

539

540541542

543544545546

72


6.4.2.1.3 PresentationDirectionNumberUpThis element iIndicates the supported placement order of the page images on a Finished-Page Image with the "NnumberU-up" element. (Keywords: TorightTobottom, TobottomToright, ToleftTobottom, TobottomToleft, TorightTotop, TotopToright, ToleftTotop) for Scan Job Ticket to specify.

6.4.2.1.4 AutoSkewCorrection(boolean) Indicates the Scan Service’s ability to detect and correct small skew orientation error due to ADF loading or placement on the platen by the user

6.4.2.1.5 Compression (list of keywords) Specify the compression algorithms supported by the Scan Service. (Keywords: Compress, Deflate, Gzip, None)

6.4.2.1.6 CompressionFactor (Range of Int) Specifies the range of compression factor supported.

6.4.2.1.7 DocumentFormat(list of keywords) This element iIndicates the output document formats that can be generated by the Scan Service. The document format values are MIME types. (Keywords include: application/octet-stream, application/pdf, application/postscript, application/vnd.pwg-xhtml-print+xml, application/vnd.hp-PCL, image/g3fax, image/jpeg, image/tiff, image/tiff-fx)

6.4.2.1.8 Exposure(complex) This is a group of elements relating to the perceived quality of a scanned image

Figure 10 Exposure (Capability)

6.4.2.1.8.1 AutoExposure(boolean) Indicates whether the Scan Service supports automatic adjustment of Brightness Contrast and/or Sharpness.

6.4.2.1.8.2 Brightness (boolean) Indicates whether increase or decrease brightness is supported by the Scan Service.

6.4.2.1.8.3 Contrast (boolean) Indicates whether increase or decrease contrast is supported by the Scan Service.

6.4.2.1.8.4 Sharpness (boolean) Indicates whether increase or decrease the sharpness of a scanned images is supported.


7374

547548549550551

552553554

555556557

558559

560561562563564

565566567

568

569

570

571572573

574575

576577

578579

75


6.4.2.1.9 InputSource( list(list of keywords) Specifies the source of the scanned document supported. (possible Keywords: Platen, Feeder, FilmReader)

6.4.2.1.10 Magnification(Height, Width Range of Int) This element sSpecifies the supported range of the magnification. for both the slow and fast scan directions. Magnification is isomorphic (i.e. the aspect ratio of the image does not change) A value of ‘100’ specifies that no adjustments are made to the scanned image. Magnification is expressed in 1 percent increments. Values below ‘100’ reduce the magnification and values above increase magnification.

6.4.2.1.11 OriginalType( list of keywords) This element sSpecifies the main characteristics of the original document supported by the Scan Service. (possible Keywords: Auto, Text, Photo, TextAndPhoto, LineArt, Magazine, Halftone, Mixed)

6.4.2.1.12 OutputDocumentColor(complex) This is a group of color related elements for the output of the Scan Service

6.4.2.1.12.1 BitDepth(sequenceSequence of integers) The number of bits used to hold a pixel sample (example values: 1, 4, 8, 16, 24, 32and 32)

6.4.2.1.12.2 ColorEncoding(sequenceSequence of keyword) Type of color encoded in the output document (keywords: Binary, Gray, color)

6.4.2.1.12.3 ColorSpace(sequenceSequence of keyword) The abstract model that describes color representation as tuples of numbers (keyword: RGB, sRGB, scRGB, CMY, CMYK, YCCand YCC)

6.4.2.1.12.4 SamplesPerPixel(Sequence of integers) This element contains the number of components per pixel. (example values: 1,3,4)

6.4.2.1.13 OutputDocumentSize(Height, Width Range of Int) Specifies This element specifies the range of output document size in Height and Width supported.

6.4.2.1.14 Resolution(CrossFeedDirt, FeedDir, Range of Int) This element sSpecifies the supported sequence of resolutions in CrossFeed and X, FeedY direction for image capture.

6.4.2.1.15 Rotation(list of keywords) This element sSpecifies the supported amount of rotation in degrees clockwise for a scanned document. (keywords: 0, 90, 180, 270)

6.4.2.1.16 ScanRegion(Height, Width, XOffset, YOffset, each is Range of Int) This element sSpecifies the supported range of area within the input document boundaries to scan.


7677

580581582583

584585586587588589

590591592

593594

595596597

598599600

601602603

604605606

607608609

610611612

613614615616

617618619620621

78


6.4.2.1.17 SidesTBD (sequenceSequence of keywords) This element sSpecifies the supported ways of a images canto be scanned from the side(s) of the Hardcopy Document. (Keywords: OneSided, TwoSidedLongEdge, TwoSidedShortEdge, TwoSidedLongEdge)

6.4.2.1.18 SinglePageFile(booleanm) This element iIndicates whether the service supports storing each page of the Scanned Hardcopy Document as a separate file.

6.4.2.1.19 VendorExtensionThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability Extension point for vendors

6.4.2.2 Scan Job Description CapabilitiesThe ScanJobDescriptionCapabilities group element provides information about the Job processing elements that can be used in Scan Job Tickets. See §6.5.3.2 for details on semantics of the Job Description elementsNote that ScanJobDescriptionCapabilities consists of two sequences. The first represents elements inherited from the Imaging Service super class and includes elements such as JobName and JobOriginatingUserName. The second sequence includes Scan Service specific extensions to the super class.


7980

622623624625626

627628629

630631632633

634635636637638639640

81


Figure 11 Scan Job Description Capabilities

6.4.2.2.1 ElementsCharset(list of keywords) Indicates the allowed coded character set and encoding method for the elements with a string syntax (example values: utf-8, unicode-1-1, shift-jis)

6.4.2.2.2 ElementsNaturalLanguage(sequence of keywords) Indicates the supported natural languages for the elements with a string syntax (example values: en-us, fr, de, ja)

6.4.2.2.3 JobAccountingId(boolean) Indicates the Scan Service’s support for Job Accounts.


8283

641

642

643

644645646

647648649

650651

84


6.4.2.2.4 JobAccountingUserIdboolean) Indicates the Scan Service’s support for a User supplied Accounting ID User Names associated with the Job Accounts.

6.4.2.2.5 JobMandatoryElements(boolean) This element iIndicates the Scan Service’s support JobMandatoryElements which is an alternative method of encoding MustHonor flagged elements.

6.4.2.2.6 JobMessageFromOperator(boolean) This element iIndicates the Scan Service’s support of operator messages for Jobs.

6.4.2.2.7 JobName(boolean) This element iIndicates the Scan Service’s support of a name for the Job.

6.4.2.2.8 JobOriginatingUserName(boolean) This element iIndicates the Scan Service’s support of the name of the user submitting the Job.

6.4.2.2.9 JobPassword(boolean) Indicates the Scan Service’s support for holding the Job until the correct password is entered.

6.4.2.2.10 JobPassword(list of keywords) This element contains the list of password encryption methods supported by the Scan Service. (keywords: TripleDES, AES, ECC, Md2, Md4, Md5, Sha, None)

6.4.2.2.11 KOctets(boolean) This element iIndicates the Scan Service’s support for storing the size of the Job in integral units of 1024 octets.

6.4.2.2.12 TemplateCreatorUserName(boolean) Indicates the Scan Service’s support for storing the user who created the template on which the Job Ticket was based.

6.4.2.2.13 TemplateId(boolean) Indicates the Scan Service’s support for storing the Id of the template on which the Job Ticket was based.

6.4.2.2.14 TemplateName(boolean) Indicates the Scan Service’s support for storing the user freiendlyfriendly name of the template on which the Job Ticket was based.

6.4.2.2.15 TemplateType(list of keywords) Indicates the Scan Service’s support for storing the type of the template on which the Job Ticket was based. The Scan Service should only support Scan Job Templates (keyword:

6.4.2.2.16 VendorExtensionThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability Extension point for vendorsScan Job Processing CapabilitiesThe ScanJobProcessingCapabilities group element provides information about the Job processing elements that can be used in Scan Job Tickets. See §6.5.3.3 for details on semantics of the Job Processing elementsNote that ScanJobProcessingCapabilities consists of two sequences. The first represents elements inherited from the Imaging Service super class and includes elements such as JobHoldUntil and JobPriority. The second sequence includes Scan Service specific extensions to the super class such as BatchModeScan.


8586

652653654

655656657

658659

660661

662663

664665

666667668

669670671

672673674

675676677

678679680

681682683

684685686687688689690691692693

87


Figure 12 Scan Job Processing Capabilities

6.4.2.2.17 JobHoldUntil(list of keywords) Indicates the named events for releasing the held job (keywords: DayTime, Evening, Indefinite, Night, NoHold, SecondShift, ThirdShift, Weekend)

6.4.2.2.18 JobHoldUntilTime(boolean) Indicates if the Scan Service allows a Scan Job Ticket to specify a Date and Time when a joba job is put on hold will be released.

6.4.2.2.19 JobMessageToOperator(boolean) Indicates if displaying a job message to an operator is supported.

6.4.2.2.20 JobPhoneNumber(boolean) Indicates if storing the contact phone number for the job is supported.

6.4.2.2.21 JobRecipientName(boolean) Indicates if storing the name of the recipient of a job is supported.

6.4.2.2.22 BatchModeScan(boolean) Indicate whether Batch Scan processing mode is supported by the Scan Service.

6.4.2.2.23 DocumentOutputMode(list of keywords) Indicate the number of documents and image storage files combinations supported by the Scan Service. (keywords: SingleDocumentSingleFile, SingleDocumentMultipleFile, MultipleDocumentSingleFile, MultipleDocumentMultipleFile)

6.4.2.2.24 MultipleSetOriginals(boolean) Indicate if the Scan Service supports scanning multiple sets of Hardcopy documents fofor the Job.


8889

694

695

696

697698699

700701702

703704

705706

707708

709710

711712713714

715716

90


6.4.2.2.25 VendorExtensionThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability TBDScan Service ConfigurationThis group element identifies the actual instances of the subunits the service uses. Note that not all subunits are used by the Scan Services. Although the diagram shows all the defined Subunits only the applicable subunits are included below. These elements are based on the Printer MIB [RFC3805]. See the RFC for details on these elements.


9192

717718719720721722723724725

93


Figure 13 Scan Service Configuration


9495

726

727

728729

96


6.4.2.3 ConsolesThis element represents the User Interface Console(s). See [RFC3805] §6 for details.

Figure 14 Console

6.4.2.3.1 ConsoleStatus

6.4.2.3.1.1 ConsoleIdThe unique identifier for the Console instance

6.4.2.3.1.2 ConsoleNaturalLanguageThe current natural language of the text displayed on the Console

6.4.2.3.1.3 ConsoleDisableIndicates if the console is currently active

6.4.2.3.1.4 ConsoleDisplayBufferThe textual contents of the Console’s diplay buffer ConsoleDisplayLightsSequence of Elements representing the Lights on the Console


9798

730731732

733

734

735

736

737738

739740

741742

743744745746

99


ConsoleLightOnTimeSequence of Elements representing the Lights on the Console

ConsoleDescription

ConsoleNumberOfDisplayLinesTBDConsoleNumberOfDisplayCharsTBD

6.4.2.4 CoversThis element represents a device’s cCovers, doors, housings and or interlocks. See [RFC3805] §6 for details.

Figure 15 Covers

6.4.2.4.1 CoverStatus

6.4.2.4.1.1 CoverIdTBDCoverStatesTBDCoverDescription

CoverInfoTBDFinisher

Not applicable to a Scan Service

6.4.2.5 InputChannelThis element represents the source of Scan Job control information (i.e. channel over which Scan Service operations are received). Note that InputChannelDefaultPageDescriptionLanguage does not apply to Scan Service. ISSUE1: What new channel types are needed (e.g. PortSOAP)


100101

747748749750751752753754755

756757758

759760

761

762763764765766767768769770771

772773774775776

102


Figure 16 InputChannel

6.4.2.6 InputTraysPlaten or ADFNot applicable to a Scan Service.


103104

777

778

779

780781782

105


Figure 17 Input Tray

6.4.2.7 InterfacesThis element represents the communication ports and associated protocol stack into and out of the device. The details of the elements contained within this element group are defined in [RFC1213] and [RFC2863]


106107

783

784

785786787

108


Figure 18 Interface

6.4.2.8 InterpretersNot applicable to Scan Service. See Transformer below


109110

788

789

790791

111


6.4.2.9 MarkerNot applicable to Scan Service

6.4.2.10 Interpreters

6.4.2.11 MediaPathsNot applicable to Scan Service

6.4.2.12 Output ChannelThis element represents the destination pathways for Digital Documents. Output Channels are associated with an underlying Interface and are usually bound to a transport protocol or file system.

Figure 19 Output Channel

TBD: Add the details of the Output Channel elements since it is not defined elsewhere.

6.4.2.12.1 OutputChannelDefaultJobControlLanguageThis associated Job Control Language (i.e. Interpreter) defines the syntax used for control functions (e.g. queries, setting document boundaries). See [RFC3805] §6 for additional details. ISSUE2: Is an Interpreter what we really


112113

792793

794

795

796797

798799800801

802

803

804805

806807808

114


mean here? Doesn’t OutputChannelType specify this (i.e. the protocol). The output channel should be independent of the document format just as the interface is independent of the transport protocol.

6.4.2.12.2 OutputChannelIDThis element uniquely identifies an instance of an Output Channel.

6.4.2.12.3 OutputChannelInterfaceThis is the Interface instance associated with this instance of an Output Channel. See [RFC3805] §6 for additional details on Interface.

6.4.2.12.4 OutputChannelIsEnabledThis element indicated whether or not an Output Channel instance is available for use.

6.4.2.12.5 OutputChannelStatesThis element shows the current States of the Output Channel. The States for the Output Channel are taken from the Input Channel (i.e. prtChannel) of the Printer MIB. See [RFC3805] §6 for additional details on prtChannelState.

6.4.2.12.6 OutputChannelAuxInfoThis element provides additional protocol information needed to use the Output Channel’s protocol. The information is protocol specific. ISSUE3: What is this element based on? I don’t see a corollary object in the Printer MIB.

6.4.2.12.7 OutputChannelInfoThis element provides protocol information needed to use the Output Channel’s protocol. The information is protocol specific. See [RFC3805] §6 for additional details on prtChannelInformation.

6.4.2.12.8 OutputChannelProtocolVersionThis element specifies the version of the protocol associated with an Output Channel instance in a protocol specific manner. See [RFC3805] §6 for additional details on prtChannelProtocolVersion.

6.4.2.12.9 OutputChannelTypeThis element specifies the protocol associated with an Output Channel instance. See [RFC3805] §6 for additional details on prtChannelType.

6.4.2.12.10 VendorExtensionThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperabilityISSUE: How does mediapath relate to Platen and ADF.

Figure 20 Media Path

6.4.2.13 OutputTraysThis element represents the general purpose output trays capable of receiving Hard Copy Documents that have been scanned. Note: if the scanner is equipped with an ADF this element may not be applicable. If the ADF is the only destination of the Hard Copy Documents handled by the ADF (i.e. recirculating) then a general purpose Output Tray is not applicable. See ScanMediaPath for additional information. See [RFC3805] §6 for details on the OutputTray elements.TBD


115116

809810

811812

813814815

816817

818819820

821822823824

825826827

828829830

831832833

834835836837838839

840

841842843844845846847

117


Figure 21 Output Tray

6.4.2.14 ScanMediaPathCopyright © 2007-2008, Printer Working Group. All rights reserved. Page 38 of

118119

848

849

850120


This element represents the media handling aspects of a Scan Device.

Figure 22 ScanMediaPath

6.4.2.14.1 ScanMediaPathIdThis element uniquely identifies an instance of a Scan Media Path.

6.4.2.14.2 ScanMediaPathStatesThis element shows the current States of the Scan Media Path. The States for the Scan Media Path are taken from the Media Path (i.e. prtMediaPathStatus) of the Printer MIB. See [RFC3805] §6 for additional details on prtMediaPathStatus.

6.4.2.14.3 RecirculatingThis element is applicable to Scan Media Paths that are capable of feeding Hard Copy Documents. If this element is set to the value ‘true’ then the Scan Media Path is both an input and output for the Hard Copy Documents as they are to the Scan Device (i.e. Scanners subunit). If the element is missing or the value is set to ‘false’ then the Hard Copy Document is delivered to an Output Bin after scanning is complete.

6.4.2.14.4 Scan MediaPathTypeThis element indicates the type of Scan Media Path (e.g. ADF, Platen).

6.4.2.14.5 Scan MediaPathTypeThis element indicates the type of Scan Media Path (e.g. ADF, Platen).


121122

851852853

854

855

856857

858859860861

862863864865866

867868

869870871

123


6.4.2.15 Scanners

6.4.2.16 ScannersThis element represents the image acquisition aspects of a Scan Device.

TBD

Figure 23 Scanner Subunit

6.4.2.16.1 ScannerAddressabilityThis element group contains information on the addressability (i.e. resolution) of the Scanning hardware. See [RFC3805] §6 prtMarkerAddressability objects for additional information

6.4.2.16.1.1 ScannerAddressabilityBasisThis element expresses the confidence level of the addressability information for the Scanning hardware.


124125

872

873874875876

877878

879880881

882883

126


6.4.2.16.2 ScannerCounterLifeThis element records the number of scans performed by the scanning hardware for the life of the device. The units are measured in ScannerCounterUnits. See [RFC3805] §6 prtMarkerLifeCount objects for additional information. ISSUE4: Should subunits use the counting metrics used by the services?

6.4.2.16.3 ScannerCounterPowerOnThis element records the number of scans performed by the scanning hardware since the device was lasted turned on. The units are measured in ScannerCounterUnits. See [RFC3805] §6 prtMarkerPowerOnCount objects for additional information

6.4.2.16.4 ScannerCounterUnitsThis element specifies units for ScannerCounterLife and ScannerCounterPowerOn. See [RFC3805] §6 prtMarkerCounterUnit objects for additional information

6.4.2.16.5 ScannerIdThis element uniquely identifies an instance of a Scan Media Path.

6.4.2.16.6 ScannerStatesThis element shows the current States of the Scanner. The States for the Scanner are taken from the Marker (i.e. prtMarkerStatus) of the Printer MIB. See [RFC3805] §6 for additional details on prtMarkerStatus.

6.4.2.16.7 ScannerMarginThis element group contains information on the Margin of the Scanning hardware. The margins provide a bounding box within which the Scanner hardware is capable of scanning. See [RFC3805] §6 prtMarkerMargin objects for additional information

6.4.2.16.7.1 ScannerMarginBasisThis element expresses the confidence level of the Margin information for the Scanning hardware.

6.4.2.16.8 ScannerBitsPerPixelThis element contains the number of bits per pixel used by the scanner’s image acquisition subsystem.

6.4.2.16.9 ScannerColorPlanesThis element contains the number of color planes used by the scanner’s image acquisition subsystem.

6.4.2.16.10 ScannerInfoThis element contains descriptive information about the scanner’s image acquisition subsystem..

6.4.2.17 TransformerISSUE5: Needs definition. I assume this will look an awful lot like an interpreter except with both an input and output side represented. Should we represent input and output as Language Family/Level/Version or as DocumentFormat/MIME? Should image processing elements from the ScanDocumentProcessing be included somehow to represent the Transformer’s capability or is that the prevue of an actual Transformation Service? Is the Transformer subunit necessary for the Scan Service model?

6.4.2.18 VendorSubunitsVendorExtensionsThis element provides extension points for vendor and implementation specific Subunits while maintaining interoperability.

6.4.3 Scan Service Description


127128

884885886887

888889890891

892893894

895896

897898899

900901902903

904905

906907

908909

910911

912913914915916917

918919920921922

923

924

129


Below is a view of the Description elements for the Scan Service. The Description elements provide Descriptive information for the Scan Service. The elements are administratively set. The element values can be directly or modified indirectly through an operation. Note that ScanServiceDescription consists of two sequences. The first represents elements inherited from the Imaging Service super class and the second sequence includes Scan Service specific extensions.

Figure 24 Scan Service Description

6.4.3.1 OwnerUriThis is the email / HTTP URI by which you can reach the admin or owner who created the service.

6.4.3.2 OwnerVCardThis is the vCard (rfc2426) of the owner of the Scan Service.

6.4.3.3 ResourcesSupportedThis is the object IDsa service specific view of the resources used by the service. ISSUE: Why should we force a client to examine the values in this element and then retrieve all the resources to find the resources of interest? Why not just provide a service specific view of the resources that are used by the Service as has been done with Subunits?.

6.4.3.4 ServiceInfoThis is descriptive information about this Scan Service. (exampleExample: “Out of courtesy for others, please scan only small (1-5 page) jobs at this scanner")


130131

925926927928929930931

932

933

934

935936

937938

939940941942943

944945946

132


6.4.3.5 ServiceNameThis is the end-user friendly name of Scan Service.

6.4.3.6 ServiceURISupportedThis element contains the URLs where the Scan Service is available.

6.4.3.7 ScanJobTimeoutWhen Scan Service is operating in MultipleSetOriginals mode, this element sets the timeout value for awaiting the end user’s next set of document originals. At timeout the Scan Service SHALL close the job inputs and schedule the job for processing. ISSUE6: Is this the desired behavior for timed out jobs?

6.4.3.8 VendorExtensionsAllows This element provides extension points for vendor differentiation and implementation specific extensions vendors to add their own extensions to the model and while maintaining interoperability.

6.4.4 Service Status

Below is a view of the Status elements for the Scan Service. The Status elements provide state information for the Scan Service. The elements are maintained by automata and can not be directly set. The element values can be modified indirectly through an operation. For example Pause operation on the Scan Service may result in the change of the State and StateReasons elements.

Note that ScanServiceStatus consists of two sequences. The first represents elements inherited from the Imaging Service super class and includes elements such as Id and State. The second sequence includes Scan Service specific extensions to the super class such as the Scan Service counters.


133134

947948

949950

951952953954

955956957958

959

960961962963964965966967968969

135


Figure 25 Scan Service Status

6.4.4.1 AccessModesAccess modes based on POSIX (ISO9945) providing Read/Write/Execute permissions for Owner/Group/World. This can be used to specify some group operations under certain privileged level in a specific domain. ISSUE7: How is this used? Where are groups defined? Why not rely on a protocol specific mechanism (e.g. WS-Security)

6.4.4.2 CreateDateDate and Time the Service was created.

6.4.4.3 CurrentTimeThis element indicates the current date and time according the Scan Services internal clock

6.4.4.4 IDA 32 bit Object Identifier for the Scan Service instance. It is unique within a scan server.


136137

970971972

973974975976

977978

979980

981982983

138


6.4.4.5 IsAcceptingJobsThis element indicates whether this Scan Service is currently able to accept jobs. How the Value for this element is configured is implementation-specific, e.g., local console, web page.

6.4.4.6 NaturalLanguageIndicates the local language currently used by the Service. This is the same as the locality method used by theof Printer MIB. ISSUE8: How is this used? Is this the language all system generated strings are in or is this the language of the user supplied strings? How do we intend to handle localization? SNMP approach i.e. set object on server then retrieve values or HTTP approach give a list of acceptable languages or is the desired language part of the request….

6.4.4.7 QueuedJobCountThis element specifies the number of jobs this Scan Service has currently accepted but not yet finished.

6.4.4.8 SerialNumberThis element specifies the serial number of the device hosting the service.

6.4.4.9 StateThis element Identifiesidentifies the current state of scanning service. The state is a unification of the service states from rfc2911 and rfc2790. The state transition diagram represents the rfc2911 view. The state values MUST NOT be extended by an implementation.

Values:From rfc2911:

Idle – The Scan Service is available and can start processing a new job.Processing – The Scan Service is currently processing jobs.Stopped - No jobs can be processed and intervention is needed.

From rfc2790:Unknown– The state of the Scan Service is not known.Testing- The Scan Service is in testing or maintenance mode.

Down- The Scan Service is unavailable for jobs.

6.4.4.9.1 Service State Diagram

(1) Service State Diagram is divided into three phases:- <Init> - Unknown state - immediately after service creation- <Offline> - Down and Testing states - no user jobs are processed- <Online> - Idle, Processing, and Stopped states


139140

984985986

987988989990991992

993994

995996

997998999

1000100110021003100410051006

100710081009

1010

1011

10121013

1014101510161017

141


Figure 26 Top Level Service State Transition Diagram

6.4.4.9.2 Service State Transition Tables

The following notations are used in the two subsequent service state transition tables:

~ = logical NOT (e.g., ~C.paused means "not paused")C = prefix of a condition E = prefix of an event (e.g., E.endJob means "job completed")titlecase = state (e.g., Idle), operation (e.g., Startup), or phaselowercase = action function (in FSM)

The following notes are used in the two service state transition tables:

(2) Startup and Restart - Startup (Unknown/Init) sends E.startup and goes to (Down/Offline)- Startup (Down/Offline) is a synonym for Restart- Restart (Down/Offline) initializes and goes to (Idle/Online)

(3) Shutdown - Shutdown (Testing|Idle|Stopped) goes to (Down/Offline)- Shutdown (Processing) sends E.shutdown and stays in (Processing)

(4) Testing- Testing (Down|Stopped) goes to (Testing/Offline)- Testing (Idle|Processing) is an error

6.4.4.9.2.1 Service State Transition By Operations

SERVICE STATE MACHINE (Operations)Input State


142143

1018

1019

1020

1021

102210231024102510261027102810291030

103110321033

10341035103610371038

1039104010411042

10431044

10451046

144


Down Testing Idle Processing StoppedOperation

(Condition)Action

(new state)Action

(new state)Action

(new state)Action

(new state)Action

(new state)

DisableN/A disable

(~C.IsAcceptingJobs)disable(~C.IsAcceptingJobs)

disable(~C.IsAcceptingJobs)

disable(~C.IsAcceptingJobs)

Enable N/A enable(C.IsAcceptingJobs)

enable(C.IsAcceptingJobs)



PauseN/A pause

(C.Pause)pause(Stopped, C.Pause)

pause(Stopped, C.Pause)

pause(C. Pause)

Resume(C. Pause, C.critical )

N/A resume(~C.Pause)

N/A N/A resume(~C.Pause)

Resume(C. Pause, ~C.critical)

N/A resume N/A N/A resume (Idle, ~C.Pause)

Restart (Note 2)

restart (Idle)

restart (Idle) restart

restart (Idle)

restart (Idle)

Shutdown(Note 3) N/A

shutdown(Down)

shutdown(Down)

shutdown(Down)

shutdown(Down)

Startup (Note 2)

restart (Idle) error error error error

Test(Note 4)

test(Testing) error error error error

6.4.4.9.2.2 Service State Transition By Events

SERVICE STATE MACHINE (Events)

InputState

Down Testing Idle Processing StoppedEvent

(Condition)Action

(new state)Action

(new state)Action

(new state)Action

(new state)Action

(new state)

E.critical N/A criticalcritical(Stopped)

critical(Stopped) critical

E.endCrit(~C.paused) N/A endCritical error error

endCritical(Idle|Processing)

E.endJob(C.shutdown) N/A error error

shutdown(Down) error

E.endJob(C.paused) N/A error error

pause(Stopped) error

E.endJob(~C.paused) N/A E.endJob error

schedule(Idle | Proc) error

E.endTest N/AtestReport(Down) error error error

E.endWarn N/A endWarning endWarning endWarning endWarningE.Startup(Note 2)

restart(Idle) error error error error

E.startJob(C.paused) N/A error error ignore ignoreE.startJob(C.disabled) N/A error error ignore ignore


145146

1047

10481049

147


E.startJob(~C.disabled) N/A error

schedule(Processing) schedule ignore

E.warning N/A warning warning warning warning

6.4.4.9.3 Detailed Service State Transition Diagram

Figure 27 Detailed Service Transition Diagram

6.4.4.10 StateReasonsThis element supplies additional detail about the service's state. The standard keyword values are defined in section §4.4.12 of rfc2911. Values of interest to a Scan Service include:

AttentionRequired ConnectingToDevice CoverOpen Deactivated DoorOpen


148149

1050

1051

1052

1053

105410551056

10571058105910601061106210631064

150


HoldNewJobs InputTrayMissing InterlockOpen MediaJam MovingToPaused None Other OutputAreaAlmostFull OutputAreaFull OutputTrayMissing Paused Scanning Shutdown Stopping TimedOut

6.4.4.11 StateMessagesThis element contains iInformation about the Service State and StateReasons in human readable text. If the Service supports this element, it MUST be able to generate the messages in any of the natural languages supported by the Service.

6.4.4.12 ScanServiceCountersThis element contains the counters for the amount of work performed by the Scan Service, timers covering utilization and monitoring information covering errors, warnings ,warnings, traffic, job counts and configuration changes. See PWG5106.1-2007.

6.4.4.13 VendorExtensionsThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability Allows vendors to add their own extensions to the model and maintain interoperability.

6.5 Scan Job Model Below is the top level view of the Scan Job. Scan Jobs can contain 0 or more documents. Initial implementations will be limited to single document jobs. During job creation it is possible that temporarily there are 0 documents. The state of the job is described in the ScanJobStatus element. ScanJobTicket contains descriptive information about the job and the Job and Document processing instructions. It is possible to override the Document Processing instructions on a document by document basis by supplying a ScanDocument Ticket with the Scan Document. The Job Ticket and Document Ticket represent the End User’s intent while the Job Receipt and Document Receipt represent what the Scan Service actually did.


151152

1065106610671068106910701071107210731074107510761077107810791080

1081108210831084

1085108610871088

108910901091109210931094

109510961097109810991100110111021103

153

Nancy Chen, Oki Data, 01/08/08,

Why limit initial implementation? Or is this just a conformance statement?


Figure 28 High Level Scan Job View

6.5.1 Scan Job ReceiptThis element has exactly the same structure as the Scan Job Ticket. For each processing element of a Scan Job, it records the actual value used by the Scan Service for processing a specificthe Scan Job when MustHonor is false. It contains the elements supplied by the Scan Client, Any substitutions made by the Scan Service and any Default elements applied by the Scan Service. See section §6.5.3 for element descriptions.

6.5.2 Scan Job Status

Below is a view of the Status elements for the Scan Job. The Status elements provide state information for the Scan Job. The elements are maintained by automata and can not be directly set. The element values can be modified indirectly through an operation. For example CancelScanJob operation on the Scan Job may result in the change of the State and StateReasons elementsNote that ScanJobStatus consists of two sequences. The first represents elements inherited from the Imaging Job super class (i.e. ImagingJobStatus) and includes elements such as JobId and JobState. The second sequence includes Scan Service specific extensions to the super class such as the Scan Service counters.


154155

1104

1105

11061107

110811091110111111121113

1114

111511161117111811191120112111221123

156


Figure 29 Scan Job Status

6.5.2.1 DateTimeAtCompletedThis element indicates the date and time at which the Job object completed (or was canceled or aborted).


157158

1124

1125

1126

11271128

159


6.5.2.2 DateTimeAtCreationThis element indicates the date and time at which the Job object completed created.

6.5.2.3 DateTimeAtProcessingThis element indicates the date and time at which the Job object first began processing (i.e. scanned).

6.5.2.4 DetailedStatusMessagesThis element specifies additional detailed and technical information about the job. The Scan Service MAY localize the message(s), since they are intended for use by the system administrator or other experienced technical persons. Localization might obscure the technical meaning of such messages. Clients MUST NOT attempt to parse the value of this attribute.

6.5.2.5 DocumentAccessErrorsThis element provides additional information about each document access error for this job encountered by the Scan Service after it returned a response to scan initiation operation and subsequently attempted to store the image data to the locations supplied in the ScanJobTicket. For errors in the protocol associated with a URI scheme, such as 'http:' or 'ftp:', the error code is returned in parentheses, followed by the URI. For example: (404) http://ftp.pwg.org/pub/pwg/mfd/job1207.png

6.5.2.6 ErrorsCountThe number of errors encountered while scanning the Hardcopy Document and generating and storing the Digital Document.

6.5.2.7 JobIdJobId is an integer value that uniquely identifies the job within the Scan Service. The Scan Service is responsible for implementing a job numbering scheme that will not allow two different jobs to coexist with the same JobId

6.5.2.8 JobStateThis element identifies the current state of Scan Job. The state values MUST NOT be extended by an implementation. Values:

From rfc2911:- Aborted – the job was halted due to an error

- Canceled – the job was halted due to a cancel operation

- Completed – the job has successfully completed operation

- Pending – the job has been accepted by the system and is awaiting system resources before it can start processing

- PendingHeld – the job is not a candidate for processing for any number of reasons and will return to the Pending state when the reasons are no longer present. The Job’s JobStateReason MUST indicate the reason the Job is not a candidate for processing.

- Processing – the job is currently progressing towards completion. The job can be scanning, processing captured data or transferring image data from the Scan Device to the destination location.


160161

11291130

11311132

1133113411351136

1137

113811391140114111421143

114411451146

114711481149

115011511152115311541155

1156

1157

11581159

116011611162

11631164

162

http://ftp.pwg.org/pub/pwg/mfd/job1207.png


- ProcessingStopped – the job has suspended processing and is awaiting resources to become available before processing can continue. Jobs in this state will be either awaiting image processing

resources, internal storage or network availability for transferring images.

Figure 30 Job State Transition Diagram

6.5.2.9 JobStateMessagesThis element provides information about the Job State and StateReasons in human readable text. If the Service supports this element, it MUST be able to generate the messages in any of the natural languages supported by the Service.

6.5.2.10 JobStateReasonsThis element supplies additional detail about the Job state. The standard keyword values are defined in section §4.3.8 of rfc2911. There is a Scan Service specific value of ‘Scanning”.ToDo: Add any new scan specific reasons here.

6.5.2.11 JobUriThe aThis element contains the globally unique identifier for a job.

6.5.2.12 KOctetsProcessedThe total number of octets processed in integral units of 1024 octets so far

6.5.2.13 MoreInfoURI used to obtain information intended for end user consumption about this specific Job

6.5.2.14 NumberOfDocumentsThe number of Documents in this Job


163164

116511661167

1168

1169

1170

1171

1172117311741175

1176117711781179

11801181

11821183

11841185

11861187

165


6.5.2.15 NumberOfInterveningJobsThe number of jobs that are "ahead" of this Job assuming the current scheduled order

6.5.2.16 TimeAtCompletedThe time at which the Job completed in “PrinterUpTimeScannerUpTime” seconds

6.5.2.17 TimeAtCreationThe time at which the Job was created in “PrinterUpTimeScannerUpTime” seconds

6.5.2.18 TimeAtProcessingThe time at which the Job first began processing in “PrinterUpTimeScannerUpTime” seconds

6.5.2.19 WarningsCountThis element contains the total number of warnings that a Scan Service has generated while processing and storing the Job’s Document(s).TBD

6.5.2.20 ScanServiceCountersThis element contains the counters for the amount of work performed for this document by the Scan Service, timers covering utilization and monitoring information covering errors, warnings , traffic, job counts are included. See [PWG5106.1-2007].TBD

6.5.2.21 VendorExtensionThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability TBD

6.5.3 Scan Job TicketThe Scan Job Ticket contains description and processing elements provided by the Scan client diringduring Scan Job creation. This information is used by the Scan Service during the processing of a Scan Job. This information is made available to Scan Clients through the GetScanJobElements operation and a subset is made available through the GetActiveJobs and GetJobsHistory operations.

Figure 31 Scan Job Ticket

6.5.3.1 Scan Document ProcessingThe ScanDocumentProcessing provides the document processing instructions that have been requested by the End User at the job level. Each element has a MustHornorMustHonor attribute to indicate whether documents within the job must be processed according to what user has requested.


166167

11881189

11901191

11921193

11941195

119611971198

1199120012011202

12031204120512061207

120812091210121112121213

1214

1215

1216

1217121812191220

168


Note that ScanDocumentCapabilities consists of two sequences. The first represents elements inherited from the Imaging Service super class and includes elements such as NumberUp and OrientationRequested. The second sequence includes Scan Service specific extensions to the super class such as AutoExposure and Brightness.


169170

122112221223

171


Figure 32 Scan Documents Processing

6.5.3.1.1 NumberUpThis element iIndicates the number of Input pages that the Scanner is to place on one image. See [rfc2911] §4.2.9Copyright © 2007-2008, Printer Working Group. All rights reserved. Page 56 of

172173

1224

122512261227

12281229

174


6.5.3.1.2 OrientationRequestedISSUE: Should rotation be used for scanned images? Orientation implies knowledge of content.The desired orientation for scanned pages for document formats that don’t have a built-in orientation. (Keywords: Portrait, Landscape, ReverseLandscape, ReversePortrait)

6.5.3.1.3 PresentationDirectionNumberUpThis element sSpecifies the placement order of the input page images on a Finished-Page Image with the "number-up" element. (Keywords: TorightTobottom, TobottomToright, ToleftTobottom, TobottomToleft, TorightTotop, TotopToright, ToleftTotop) See [PWG5100.3] §3.17

6.5.3.1.4 AutoSkewCorrection Provide detection and correction of small skew orientation error from the media loading from the ADF or placement on the platen by the user

6.5.3.1.5 CompressionCompression algorithm used on the Document Data, if any. (Keywords: None, Deflate, Gzip, Compress) See [rfc2911] §4.4.32

6.5.3.1.6 CompressionFactorAn This element contains a normalized integer value used by JPEG compression to determine the amount of acceptable image loss. JPEG compression can be lossy, some amount of data is lost (none reproducible) or lossless. The higher the requested compression factor the smaller the resulting file size. The value is normalized as an integer between 0 and 100.

6.5.3.1.7 DestinationIndicates where the output of the job SHALL be stored. The destination is either a directory in which the Digital Document is stored or the URL to the Digital Document file. Destination must be in URI format. Issue9: Does this require a corresponding capabilities element?

6.5.3.1.8 Document FormatThe format used to save Scan Documents. This SHALL be an enumeration of MIME type which is pwg:DocumentFormat type. See [rfc2911] §3.2.1.1 and [PWG5100.5] §9.1.12

6.5.3.1.9 ExposureThis element is a choice of the AutoExposure element or a sequence of four elements: BrighnessBrightness, Contrast, Sharpness, and VendorExtension. This specifies whether the Scan Service will automatically employ image processing techniques to reduce the background of the document to a white image. When set to true automatic background reduction will be performed on the input document

6.5.3.1.9.1 AutoExposureWhen selected automatic background reduction will be performed on the input document.

6.5.3.1.9.2 BrightnessSpecifies the relative amount to enhance or reduce the brightness of the scanned image. Negative values will darken the image and positive values will lighten the image.

6.5.3.1.9.3 ContrastSpecifies the relative amount to enhance or reduce the contrast of the scanned image Negative values will reduce the apparent difference between light and dark pixels in the image. Positive values will increase the apparent difference between light and dark pixels in the image.

6.5.3.1.9.4 Sharpness


175176

1230123112321233

1234123512361237

123812391240

124112421243

12441245124612471248

1249125012511252

1253125412551256

125712581259126012611262

12631264

126512661267

1268126912701271

1272

177


Specifies the relative amount to enhance or reduce object edges within a scanned image. Positive values enhance object edges and negative values reduce object edges. The value is normalized as an integer between -100 and 100.

6.5.3.1.9.5 VendorExtensionThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability

6.5.3.1.10 InputSourceThis element sSpecifies the source of the scanned document . (Keywords: Platen, Feeder, FilmReader)

6.5.3.1.11 MagnificationThis element sSpecifies the magnification for both the slow and fast scan directions. Both values must be specified. Isomorphic magnification to be applied to the scanned image is accomplished by supplying the same values for both height and length. Magnification is isomorphic (i.e. the aspect ratio of the image does not change) A value of ‘100’ specifies that no adjustments are made to the scanned image. Magnification is expressed in 1 percent increments. Values below ‘100’ reduce the magnification and values above increase magnification.The value is normalized as an integer between 0 and 100.

6.5.3.1.12 MediaBoxThis element is only applicable when the document format used to store the Digital Document has a similar construct that controls the placement and bounding of the scanned image on the document format specific page image. Prior to applying this element all other processing elements are assumed to have been applied. Note that origin of the image does not move when an image is rotated for the purposes of MediaBox. In other words the origin of the image before rotation is in the upper left hand corner. After any amount of rotation the origin for the image remains in the upper left hand corner. This is also true for the orientation of the MediaBox.The image is placed within the intersection of the MediaBox and the ImageBox under the control of the ImageCroppingPolicy. (See below)

6.5.3.1.12.1 ImageBoxDescribes the region where the image from the scan of the ScanRegion will be placed

6.5.3.1.12.1.1 HeightThe height of the image box in RegionUnits

6.5.3.1.12.1.2 RegionUnitsThe units used for specifying the region

6.5.3.1.12.1.3 WidthThe width of the image box in RegionUnits

6.5.3.1.12.1.4 XOffsetThe offset, positive or negative, on the X axis from the origin of the MediaBox in RegionUnits

6.5.3.1.12.1.5 YOffsetThe offset, positive or negative, on the X axis from the origin of the MediaBox in RegionUnits

6.5.3.1.12.2 ImageCroppingPolicyThis element controls how to handle mismatches in the size of the image and the intersection of the ImageBox and MediaBox where the image will be placed. Values are ‘Crop’ – Image is not modified, areas outside the intersection are cropped, area that are not filled by the image are left blank; ‘StretchIsomorphicMax’ – The image is stretched maintaining its aspect ration until the both the height and


178179

127312741275

127612771278

1279

12801281

1282128312841285128612871288

128912901291129212931294129512961297

12981299

13001301

13021303

13041305

13061307

13081309

13101311131213131314

180


width are filled, the image outside the intersection is cropped; ‘StretchIsomorphicMin - The image is stretched maintaining its aspect ration until image fills the height and width, no part of the image is cropped; ‘StretchNonIsomorphic’ – The image is stretched in the X direction until the width is filled, The image is stretched in the Y direction until the height is filled, no part of the image is cropped, The aspect ratio is not necessarily maintained

6.5.3.1.12.3 MediaSizeNameThe size of the canvas for a page in the Digital Document expressed as a media size name. . . See [pwg5101.1] §5

6.5.3.1.12.4 OrientationRequestedThe orientation of the MediaBox See [rfc2911] §4.2.10

6.5.3.1.13 OriginalTypeThis element specifies the main characteristics of the original document (Keywords: Auto, Text, Photo, Magazine, Halftone, Mixed)

6.5.3.1.14 OutputDocumentColor

6.5.3.1.14.1 BitDepthThe number of bits used to hold a pixel sample (example values: 1, 4, 8, 16, 24, 32)

6.5.3.1.14.2 ColorEncodingType of color encoded in the output document (keywords: Binary, Gray, color)

6.5.3.1.14.3 ColorSpaceThe abstract model that describes color representation as tuples of numbers (keyword: RGB, sRGB, scRGB, CMY, CMYK, YCC)

6.5.3.1.14.4 SamplesPerPixelThe is the number of components per pixel. (example values: 1,3,4)

6.5.3.1.14.5 VendorExtension

6.5.3.1.15 ResolutionThis specifies the resolution in the Feed and Cross Feed directions at which to capture the image. The Resolution data structure does not limit the values. However, individual devices may limit the range of options to a predefined list or range. This information will be available as part of the ScanServiceCapabilities provided as a result of a GetScannerElements query. Resolution is specified in pixels per inch or pixels per centimeter. See printer-resolution in [RFC2911] §4.2.12

6.5.3.1.16 RotationSpecifies the amount to rotate each image of a scanned document specified in degrees clockwise

6.5.3.1.17 ScanRegionSpecifies the area within the input document boundaries to scan. If ScanRegion is not specified, the device should use 0 as the offsets and the width and height of the InputSize, if given. If ScanRegion is not specified and InputSize is not specified or cannot be determined by the device, the implementation is up to the hardware vendor.


181182

13151316131713181319

132013211322

13231324

132513261327

1328

13291330

13311332

133313341335

13361337

1338

133913401341134213431344

13451346

13471348134913501351

183


Figure 33 Scan Region

Width corresponds to the fast scan direction and Height corresponds to the slow scan direction.

6.5.3.1.17.1.1 HeightThe height of the ScanRegion in RegionUnits

6.5.3.1.17.1.2 RegionUnitsThe units used for specifying the region

6.5.3.1.17.1.3 WidthThe width of the ScanRegion in RegionUnits

6.5.3.1.17.1.4 XOffsetThe offset, positive or negative, on the X axis from the West Margin of the Scan Device in RegionUnits

6.5.3.1.17.1.5 YOffsetCopyright © 2007-2008, Printer Working Group. All rights reserved. Page 60 of

184185

1352

1353

13541355

13561357

13581359

13601361

13621363

1364186


The offset, positive or negative, on the X axis from the West Margin of the Scan Device in RegionUnits

6.5.3.1.18 SidesIndicates how an image is to be scanned from the side(s) of the Hardcopy Document. (Keywords: OneSided, TwoSidedLongEdge, TwoSidedShortEdge, TwoSidedLongEdge) See [rfc2911] §4.2.8

6.5.3.1.19 SinglePageFileThis element iIndicates whether each page of the Scan Document is to be stored as a separate file. If this element’s value is true, the Destination MUST be a DestinationDirectory. ISSUE10: Shouldn’t this be removed in favor of the Job level DocumentOutputMode

6.5.3.1.20 VendorExtensionThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperabilityTBD

6.5.3.2 Scan Job DescriptionTBD Below is a view of the Description elements for the Scan Job. Note that ScanJobDescription consists of two sequences. The first represents elements inherited from the Imaging Job super class (i.e. ImagingJobDescription) and includes elements such as JobName. The second sequence includes Scan Service specific extensions to the super class. Currently the only extension is the extension point for Vendors. These elements are set by the Scan Client during job creation.


187188

13651366

136713681369

1370137113721373

1374137513761377

1378137913801381138213831384

189


Figure 23 Scan Job Description

6.5.3.2.1 ElementsCharsetIndicates the coded character set and encoding method of the elements in this Document object with string syntax that were set by the End User.

6.5.3.2.2 ElementsNaturalLanguageIndicates the natural language of the elements with string syntax that were set by the End User. ElementsCharset and ElementsNaturalLanguage both are character set in language for system generated character strings. For example, the response of a request to Scan Service can be in the language you specified here.

6.5.3.2.3 JobAccountingIDAccount associated with this Job. See [PWG5100.3] §3.6


190191

1385

1386

1387

138813891390

1391139213931394

13951396

192


6.5.3.2.4 JobAccountingUserIDSpecifies the User ID associated with the “JobAccountId”. See [PWG5100.3] §3.7

6.5.3.2.5 JobMandatoryElementsAllows a user to list which Ticket elements the Scanner must honor. The Scan Service rejects the job submission if any of the listed elements are unsupported or contain values that the Scan Service does not support. All of the remaining supplied elements are best effort. See attribute-fidelity [rfc2911] §15.1 and [PWG5100.5] §8.1.1

6.5.3.2.6 JobMessageFromOperatorMessage to the end user indicating the reasons for any management action taken on this Job See [rfc2911] §4.3.16

6.5.3.2.7 JobNameThe Scan Service sets this to the client-supplied end-user friendly name for the Job., When it is not supplied by the client,else the Scan Service must generate a name from other information. [rfc2911] §4.3.5

6.5.3.2.8 JobOriginatingUserNameThe Scan Service sets this element to the most authenticated printable name that it can obtain (example: “John Doe”, \authDomain\John Doe”) See [rfc2911] §4.3.6

6.5.3.2.9 JobPasswordContains a password supplied by the client encrypted according to method specified by the client in the JobPasswordEncryption element. See [prod-print2] §4.1

6.5.3.2.10 JobPasswordEncryptionSpecifies the type of encryption that the client is used for the supplied value of the JobPassword element. (Keywords: None, Md2, Md4, Md5, Sha) See [prod-print2] §4.2

6.5.3.2.11 KOctetsThe total size of this Job’s Document(s) in integral units of 1024 octets. See [rfc2911] §4.3.17.1

6.5.3.2.12 TemplateNameThe name of template used to create the Job Ticket (if any). Note: For a Job Template this is used to hold the Template Repository wide unique Template name.

6.5.3.2.13 TemplateCreatorUserNameThe name of user who created the template used to create the Job Ticket (if any). Note: For a Job Template this is used to hold the most authenticated user name of the Template Creator.

6.5.3.2.14 TemplateIdThe ID of the template used to create the Job Ticket (if any).

6.5.3.2.15 TemplateTypeThe type of the template used to create the Job Ticket (if any). The type of the template MUST match the service which in this case is ‘Scan’.


6.5.3.3 Scan Job ProcessingThe ScanJobProcessing provides the job processing instructions that have been requested by the End User. Each element has a MustHonored attribute. When the value of MustHonored is true, the Scan


193194

13971398

1399140014011402

140314041405

140614071408

140914101411

141214131414

141514161417

14181419

142014211422

142314241425

14261427

142814291430

1431143214331434

143514361437

195


Service does not process the job unless the element is supported, otherwise the Scan Service processes the job with its best effort.

Note that ScanJobProcessing consists of two sequences. The first represents elements inherited from the Imaging Service super class and includes elements such as JobHoldUntil and JobPriority. The second sequence includes Scan Service specific extensions to the super class such as BatchModeScan.

Figure 34 Scan Job Processing

6.5.3.3.1 JobHoldUntilThe duration of time a job is put on hold, i.e. prohibited from being scheduled for processing. Note that if this element is specified JobHoldUntilTime can not. See [rfc2911] §4.2.2

6.5.3.3.2 JobHoldUntilTimeThe absolute date and time a job will be released after being put on hold. This allowThis element allows you to hold a remotely submitted job until a specific time for processing. . Note that if this element is specified JobHoldUntil can not. See [prod-print2] §5.4

6.5.3.3.3 JobMessageToOperatorMessage provided by the Job owner that should be presented to the scanner operator in an implementation specific manner. See [PWG5100.3] §3.10

6.5.3.3.4 JobPhoneNumberTThis element contains the contact phone number for the owner of the Job. This informational element’s value can be used to contact the owner in the event additional information is required *e.g. what to do if the quality of the scan is deemed unacceptable) See [prod-print2] §5.5

6.5.3.3.5 JobRecipientNameThis element contains the name of the recipient for the job. See [prod-print2] §5.6


196197

1438143914401441144214431444

1445

1446

1447

144814491450

14511452145314541455

145614571458

1459146014611462

14631464

198


6.5.3.3.6 BatchModeThis element’s value iIndicates whether the job is to be processed in Batch Scan Mode. Batch mode scanning consists of a set of Hard Copy Documents that are placed in a document feeder. The set of Hard Copy Documents will contain Physical Scan Job Ticket(s) and Physical Scan Document Ticket(s) that will control the processing of the stack of Hard Copy Documents.

6.5.3.3.7 DocumentOutputModeThis element controlsIndicates the number of Documents and output files for the outputgenerated from a Scan Job. See §6.2

6.5.3.3.8 MutipleSetOriginalThis element controls Indicates whether the Scan Service is requireds to intake multiple sets of originals from the selected input source.


6.6 Scan Document Model Below is the top level view of the Scan Document. Scan Documents are associated with one Job. Initial implementations will be limited to single document jobs. The state of the Document is described in the ScanDocumentStatus element. ScanJobTicket contains descriptive information about the job and the Job and Document processing instructions. It is possible to override the Document Processing instructions on a document by document basis by supplying a ScanDocument Ticket with the Scan Document. The Job Ticket and Document Ticket represent the End User’s intent while the Job Receipt and Document Receipt represent what the Scan Service actually did.

Figure 35 High Level Scan Document View

6.6.1 Scan Document ReceiptThis element has exactly the same structure as the Scan Document Ticket. For each processing element of a Scan Document, it records the actual value used by the Scan Service for processing the Scan Document. It contains the elements supplied by the Scan Client, Any substitutions made by the Scan Service and any Default elements applied by the Scan Service.For each processing element of a Scan Document, it records the actual value used by the Scan Service for processing a specific Scan Document when MustHonor is false. See section §6.6.3 for element descriptions.

6.6.2 Scan Document Status


199200

14651466146714681469

147014711472

147314741475

1476147714781479

148014811482148314841485148614871488

1489

1490

1491

1492149314941495149614971498

1499

1500

201


Below is a view of the Status elements for the Scan Job. Note that ScanJobStatus consists of two sequences. The first represents elements inherited from the Imaging Job super class (i.e. ImagingJobStatus) and includes elements such as JobId and JobState. The second sequence includes Scan Service specific extensions to the super class such as the Scan Service counters.ToDo:Add additional descriptive text

Figure 36 Scan Document Status

6.6.2.1 CurrentPageOrderTBD


202203

150115021503150415051506

150715081509

15101511

204


6.6.2.2 DateTimeAtCompletedThis element indicates the date and time at which the Job object completed (or was canceled or aborted). See [rfc2911] §4.3.14.7

6.6.2.3 DateTimeAtCreationThis element indicates the date and time at which the Job object completed created. See [rfc2911] §4.3.14.5

6.6.2.4 DateTimeAtProcessingThis element indicates the date and time at which the Job object first began processing (i.e. scanned). See [rfc2911] §4.3.14.6

6.6.2.5 DetailedStatusMessagesThis element specifies additional detailed and technical information about the job. The Scan Service MAY localize the message(s), since they are intended for use by the system administrator or other experienced technical persons. Localization might obscure the technical meaning of such messages. Clients MUST NOT attempt to parse the value of this attribute. See [rfc2911] §4.3.10

6.6.2.6 DocumentAccessErrorsThis element provides additional information about each document access error for this job encountered by the Scan Service after it returned a response to scan initiation operation and subsequently attempted to store the image data to the locations supplied in the ScanJobTicket. For errors in the protocol associated with a URI scheme, such as 'http:' or 'ftp:', the error code is returned in parentheses, followed by the URI. For example: (404) http://ftp.pwg.org/pub/pwg/mfd/job1207.png See [rfc2911] §4.3.11

6.6.2.7 DocumentNumberTBDThe order of the document within a Job. The first Document is number ‘1’. This element uniquely identifies a Document within a Job. See [PWG5100.4] §9.2, [PWG5100.5] §9.1.23

6.6.2.8 DocumentStateThis element identifies the current state of Scan Document. The state values MUST NOT be extended by an implementation. See [PWG5100.5] §9.1.25Values:

From rfc2911:- Aborted – The Document has been aborted by the system, usually while the Document was in the

'Processing' state and the Scan Service has completed aborting the Document and all Document status elements have reached their final values for the Document. While the Scan Service is aborting the Document, the Document remains in its current state, but the Document’s " DocumentStateReasons” element SHOULD contain the 'ProcessingToStopPoint' and 'AbortedBySystem' values. When the Document moves to the 'Aborted' state, the 'ProcessingToStopPoint' value, if present, MUST be removed, but the 'AbortedBySystem' value, if present, MUST remainthe job was halted due to an error

- Canceled – The Document has been canceled as a result of the Scan Job being cancelled by a CancelJob” operation prior to the document reaching a ‘Completed’ or ‘Aborted’ state. While the Scan Service is canceling the Document, the Document remains in its current state, but the Document’s "DocumentStateReasons” element SHOULD contain the 'ProcessingToStopPoint' value and one of the 'CanceledByUser', 'CanceledByOperator', or 'CanceledAtDevice' values. When the Document moves to the 'canceled' state, the 'ProcessingToStopPoint' value, if present, MUST be removed, but the 'CanceledByXxx', if present, MUST remainthe job was halted due to a cancel operation

- Completed – The Document has completed successfully or with warnings or errors after processing and all of the Document’s Digital Documents have been sent to their Destination and all Document status elements have reached their final values for the Document. The Document’s " DocumentStateReasons” element SHOULD contain one of: 'CompletedSuccessfully', 'CompletedWithWarnings', or 'CompletedWithErrors' values.the job has successfully completed operation


205206

151215131514

15151516

151715181519

1520152115221523

1524

152515261527152815291530

153115321533

1534153515361537153815391540154115421543154415451546

15471548154915501551155215531554

155515561557155815591560

207

PZehler, 01/08/08,

Paused (DW)

http://ftp.pwg.org/pub/pwg/mfd/job1207.png


- Pending – The Document has not started to be processed at allthe job has been accepted by the system and is awaiting system resources before it can start processing

- Processing – The job has begun using, or is attempting to use, one or more purely software processes that are analyzing, creating, or interpreting the Hard Copy Document or Digital Document. The job has begun using, or is attempting to use, one or more hardware devices that are analyzing, creating, or interpreting the Hard Copy Document or Digital Document. The Digital Document is ready for sending to its Destination, but the Output Channel is not yet transferring it, either because the Digital Document hasn't reached the Output Channel or because the Document is queued in the Output Channel or some other spooler, awaiting the Output Channel to transfer it. The ‘processing’ state for the Document indicates that the Document has begun to be processed. Even if the Job stops being processed, the Document remains in the ‘processing’ state until it moves to one of the three terminal states. Implementations MAY include additional values in the document’s ”DocumentStateReasons” element to indicate the progress of the Document, such as adding the ’Scanning’ value to indicate when the Scanner device is actually acquiring the image from the Scan region of the Hard Copy Document the job is currently progressing towards completion. The job can be scanning, processing captured data or transferring image data from the scan device to the destination location.

Figure 37 Document State Transition Diagram

6.6.2.9 DocumentStateMessagesThis element provides information about the Document State and StateReasons in human readable text. If the Service supports this element, it MUST be able to generate the messages in any of the natural languages supported by the Service. See [PWG5100.5] §9.1.26


208209

15611562

156315641565156615671568156915701571157215731574157515761577

1578

1579

1580

1581

1582

1583

1584158515861587

210


6.6.2.10 DocumentStateReasonsThis element supplies additional detail about the Document state. The standard keyword values are defined in section 4.3.8 of rfc2911. The scan specific value of ‘Scanning” has been added See [PWG5100.5] §9.1.27 and {RFC2911] §4.3.8 for standard values.ToDo: Add any new scan specific reasons here.

6.6.2.11 ErrorCountsThe number of errors encountered while processing the document See [PWG5100.5] §9.1.29

6.6.2.12 JobIdJobId is an integer value that identifies the job to which this document belongs. See [PWG5100.5] §9.1.18

6.6.2.13 JobUriThe globally unique ID of the job to which this document belongs See [PWG5100.5] §9.1.19

6.6.2.14 KOctetsProcessedThe total number of octets processed in integral units of 1024 octets so far See [rfc2911] §4.3.17.1

6.6.2.15 MoreInfoURI used to obtain information intended for end user consumption about this specific Job See [rfc2911] §4.3.4

6.6.2.16 TimeAtCompletedThe time at which the document completed in “PrinterUpTime” seconds See [rfc2911] §4.3.14.3

6.6.2.17 TimeAtCreationThe time at which the Document was created in “PrinterUpTime” seconds See [rfc2911] §4.3.14.1

6.6.2.18 TimeAtProcessingThe time at which the Document first began processing in “PrinterUpTime” seconds See [rfc2911] §4.3.14.2

6.6.2.19 WarningsCountThe total number of warnings that a Scan Service has generated while processing and storing the Job’s Document(s). See [PWG5100.4 §6.1

6.6.2.20 ScanServiceCountersThis element contains the counters for the amount of work performed for this document by the Scan Service, timers covering utilization and monitoring information covering errors, warnings , traffic, job counts are included. See [PWG5106.1-2007].

6.6.2.21 VendorExtensionThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperabilityTBD

6.6.3 Scan Document TicketThe Scan Document Ticket contains description and processing elements provided by the Scan client during Scan Document creation. This information is used by the Scan Service during the processing of a Scan Document. This information is made available to Scan Clients through the GetScanDocumentElements operation.TBD


211212

15881589159015911592

15931594

15951596

15971598

15991600

16011602

16031604

16051606

16071608

160916101611

1612161316141615

16161617161816191620

16211622162316241625

213


Figure 38 Scan Document Ticket

6.6.3.1 Scan Document DescriptionBelow is a view of the Description elements for the Scan Job. Note that ScanJobDescription consists of two sequences. The first represents elements inherited from the Imaging Job super class (i.e. ImagingJobDescription) and includes elements such as JobName. The second sequence includes Scan Service specific extensions to the super class. Currently the only extension is the extension point for Vendors. These elements are set by the Scan Client during job creation. TBD

Figure 39 Scan Document Description

6.6.3.1.1 CompressionCompression algorithm to be used on the Digital Document Data, if any TBD

ISSUE:Need to add Description elementsISSUE11: This should be a processing element for scan as opposed to print’s use as a descriptive element

6.6.3.1.2 DocumentCharsetThis element provides a hint about Hard Copy Documents that contain text. This element is not useful for Hard Copy documents that do not contain text or are not intended to undergo Optical Character Recognition (OCR). See [PWG5100.7] §3.2.2 [PWG5100.5] §9.1.10 Copyright © 2007-2008, Printer Working Group. All rights reserved. Page 70 of

214215

1626

1627

1628

1629163016311632163316341635

163616371638

163916401641164216431644

1645164616471648

216


6.6.3.1.3 DocumentDigitalSignatureThe type of digital signature, if any, used in the creation of the Digital Document. (Keywords: dss, none, pgp, smime, xmldsig). See [PWG5100.7] §3.2.3 [PWG5100.5] §9.1.11

6.6.3.1.4 DocumentMessageA message from either (1) the user to the operator about the Document or (2) from the operator, system administrator, or "intelligent" process to indicate to the end user the reasons for modification or other management action taken on the Document. See [PWG5100.5] §9.1.20

6.6.3.1.5 DocumentNameName for this Document to be used in an implementation specific manner. See [rfc2911] §3.2.1.1

6.6.3.1.6 DocumentNaturalLanguageThis element provides a hint about the language used in Hard Copy Documents that contain text. This element is not useful for Hard Copy documents that do not contain text or are not intended to undergo Optical Character Recognition (OCR). See [rfc2911] §3.2.1.1, [PWG5100.5] §9.1.22

6.6.3.1.7 LastDocumentThe value of this element is set to ‘true’ for the last document in the job. Otherwise the value is set to ‘false’ or the element is omitted. See [rfc2911] §3.3.1

6.6.3.1.8 VendorExtensionThis element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability TBD

6.6.3.2 Scan Document ProcessingThis group element has exactly the same structure as the Scan Document Processing element of Scan Job (See 6.5.3.1). It provides the document processing instructions that have been requested by the End User at each document level, overriding the job level document processing instructions.

7 Scan Service Theory of OperationThe Scan Service operates autonomously through three phases: initialization, online, and offline.

At power-up the Scan Service enters its initialization phase that initializes all its service attributes, connected subunits, may perform a self-testing and may also test its Scan Device(s). After the initialization is successful, the Scan Service enters the “Down” state (an offline state) and performs a start-up operation that brings the service online, authenticates and registers its service with a service directory or announces its service to the network domain in which it resides. The Scan Service then enters the “Idle” state and becomes ready for service discovery and accepting service requests from Scan Clients.

The Scan Service accepts new requests as long as it’s not disabled and is in one of the four states: Idle, Processing, Stopped, or Testing. Performing an administrative Disable() operation while in any state will stop the Scan Service from accepting new jobs. Performing an Enable() operation in any state while the Scan Service is disabled will enable new jobs to be accepted again.

A user submits a Scan Job through a local (via MFD UI) or remote (via local network or Internet) Scan Client to a selected target Scan Service that has the desired scan capabilities. While the service is enabled, a Scan Client can request any Scan Service operations specified in Sections 8.1 and 8.1.9.1. A Scan Client uses the CreateScanJob operation to submit a Scan Job on behalf of a user. To facilitate users to input Scan Job processing instructions, a Scan Client may use any of the Template Manager operations specified in Section 11.3 to prepare, store and maintain each user’s job processing instructions as Scan Job Templates in a repository. A user may then select a template that best matches his/her Scan Intent to be passed as a parameter by the Scan Client to the Copyright © 2007-2008, Printer Working Group. All rights reserved. Page 71 of

217218

164916501651

1652165316541655

16561657

1658165916601661

166216631664

1665166616671668

16691670167116721673

1674

167516761677167816791680168116821683168416851686168716881689169016911692169316941695

219


CreateScanJob operation. A Scan Client needs to use the CloseJob() operation to signal the last set of Hardcopy Scan Document input when the scanner’s input capacity is limited and continuous sets of hardcopies need to be fed into the platen or ADF for a large Scan Job. The Scan Service places all submitted jobs in the ActiveJobs queue and schedules jobs for processing immediately or when a StartJob event is signaled based on job priority. A user may specify a JobHoldUntilTime for a remotely submitted job to allow ample time for user to walk up to the scanner for placing his/her Hardcopy originals on the scanner. An administrator can also put a job in the ActiveJobs queue on hold via a HoldJob() operation preventing it being scheduled and a ReleaseJob() operation will release the job for scheduling again.

When a Scan Job is released for scheduling and reached the top of ActiveJobs queue, the Scan Service immediately enters its Processing state. During job processing, the Scan Service can be interrupted by a “Pause()” operation to enter the “Stopped” state. This allows a user to submit and process an urgent Scan Job or a job for another service, and a Resume() operation resumes previous Scan Job processing afterwards.

When there are critical conditions impacting Scan Serviceability during “Idle” or “Processing” state, either a C.Critical event is generated or an Administrative Pause() is performed to bring the service to the Stopped state, from there the condition can be fixed by user’s intervention immediately then either the Scan Service generates a ~C.Critical event or an administrator performs a Resume() operation to bring the Scan Service back to “Idle” or “Processing” state. Otherwise, if the Scan Service needs a Shutdown() operation followed by a restart or Shutdown() for testing, both will require a Startup() operation to bring the service back to “Idle” state then restart job processing again.

At any time all jobs in the ActiveJobs queue, whether being held, pending for scheduling, in processing, or being temporarily stopped from processing, can be canceled via a CancelJob() operation by an authorized user. A canceled job, completed job, or an aborted job due to processing errors can be placed back into ActiveJobs queue and restarted via the administrative RestartJob() operation and be processed along with its Scan Documents again.[TBD]

8 Scan Service InterfacesThe Scan Service provides a set of service interfaces that is the same for a co-located local Scan Client or a Remote Scan Client via a local interface, a local area network, or the Internet. A user makes a Scan Service request by interacting directly with the Scan Service or indirectly through a local Scan Client via the MFD UI or a Remote Scan Client via its software application UI.

8.1 Basic Scan Service Operations

8.1.1 CancelJob This REQUIRED operation allows a client to cancel a Scan Job from the time the job is created up to the time it is completed, canceled, or aborted. Since a Job might already be scanning by the time a Cancel-Job is received, some page images might be stored to the scan destination before the job is actually terminated.

The Scan Service MUST accept or reject the request based on the job's current state and transition the job to the indicated new state as follows:CurrentJobState

New JobState

status Note

Pending Canceled SuccessPendingHeld Canceled SuccessProcessing Canceled SuccessProcessing Processing Success See Note 1Processing Processing Fault See Rule 2Processing Stopped

Canceled Success

Processing Stopped

Processing Stopped

Success See Note 1


220221

169616971698169917001701170217031704170517061707170817091710171117121713171417151716171717181719172017211722

1723

1724172517261727

1728

1729173017311732173317341735

222


Processing Stopped

Processing Stopped

Fault See Rule 2

Completed Completed FaultCanceled Canceled FaultAborted Aborted FaultNote 1: If the implementation requires some measurable time to cancel the job in the ‘Processing’ or ‘ProcessingStopped’ states, the Scan Service MUST add the ProcessingToStopPoint ' value to the job's "JobStateReasons" element and then transition the job to the 'Canceled' state when the processing ceases.Note 2: If the Job already has the 'ProcessingToStopPoint' value in its "JobStateReasons" element, then the Scan Service MUST reject a CancelJob operation.

8.1.1.1 Cancel Job Request

8.1.1.2 Cancel Job ResponseNote: The response is expected to be an empty successful return or a fault. The response below indicates that vendors may extend the response with additional information

8.1.2 CloseScanJobISSUE12: Is this operation required. Other than CreateJob what other operations are needed befor a Job is closed

8.1.3 CreateScanJob This REQUIRED operation allows a Scan Client to create a Scan Job on the Scan Service. Upon completion the Scan Job is available for scheduling unless a Job Processing instruction (e.g. JobHoldUntil) explicitly prevents it.

8.1.3.1 CreateScanJobRequest


223224

17361737173817391740

1741

1742174317441745

174617471748

174917501751

1752

1753

225


8.1.3.2 CreateScanJobRSponse

8.1.4 GetActiveJobsThis REQUIRED operation provides summary information on all Pending and Processing Scan Jobs.

8.1.4.1 GetActiveJobsRequestISSUE13: The parameters need to be defined for this operation

8.1.4.2 GetActiveJobsResponseISSUE14: This operation should return minimal information about a job. This summary information has yet to be defined.

8.1.5 GetJobHistoryThis OPTIONAL operation provides summary information on all Scan Jobs that have reached a terminating state (i.e. Completed, Canceled, Aborted).

8.1.5.1 GetJobHistory RequestISSUE15: The parameters need to be defined for this operation.


226227

1754

17551756

17571758

17591760

1761176217631764

1765176617671768

17691770

1771

228


8.1.5.2 GetJobHistory ResponseISSUE16: This operation should return minimal information about a job. This summary information has yet to be defined.

8.1.6 GetScanJobElements This REQUIRED operation allows a Scan Client to obtain detailed information on the specified Scan Job. The Client can request any element or group of elements contained within the Scan Job.

8.1.6.1 GetScanJobElements Request

8.1.6.2 GetScanJobElements ResponseIssue17: Need a new type so that ststus is not mandatory in response

8.1.7 GetScanDocumentElements This REQUIRED operation allows a Scan Client to obtain detailed information on the specified Scan Document within the specified Scan Job. The Client can request any element or group of elements contained within the Scan Document. The Scan Document Data is not part of the Scan Document and can not be retrieved using this operation. The location of the Scan Document Data is available.ISSUE18: Needs to be added to WSDL/Schema


229230

177217731774

1775177617771778

1779

178017811782

17831784178517861787178817891790

231


8.1.7.1 GetScanDocumentElementsRequest

8.1.7.2 GetScanDocumentElements Response

8.1.8 GetScanServiceElements This REQUIRED operation allows a Scan Client to obtain detailed information on the Scan Service. The Client can request any element or group of elements contained within the Scan Service.

8.1.8.1 GetScanServiceElementsRequest

8.1.8.2 GetScanServiceElementsResponse

8.1.9 ValidateScanTicket

8.1.9.1 ValidateScanTicketRequest

8.1.9.2 ValidateScanTicketResponse

8.2 Administrative Scan Service Operations

8.2.1 DisableScanServiceThis operation prevents the Scan Service from accepting any new Scan Jobs (i.e. CreateScanJob operation). The Scan Service is still able to process other operations.

8.2.1.1 DisableScanServiceRequestNote: The request is not expected to contain any parameters. The request below indicates that vendors may extend the request with additional information


232233

1791

1792

179317941795

1796

17971798

17991800

1801

1802

1803

1804

180518061807

1808180918101811

234


8.2.1.2 DisableScanServiceResponseNote: The response is expected to be an empty successful return or a fault. The response below indicates that vendors may extend the response with additional information

8.2.2 EnableScanServiceThis operation allows a previously disabled Scan Service to accepting new Scan Jobs (i.e. CreateScanJob operation).

8.2.2.1 EnableScanServiceRequestNote: The request is not expected to contain any parameters. The request below indicates that vendors may extend the request with additional information

8.2.2.2 EnableScanServiceResponseNote: The response is expected to be an empty successful return or a fault. The response below indicates that vendors may extend the response with additional information

8.2.3 HoldJob This OPTIONAL operation allows a client to hold a pending job in the queue so that it is not eligible for scheduling. If the HoldJob operation is supported, then the ReleaseJob operation MUST be supported, and vice-versa. The OPTIONAL "JobHoldUntil" or "JobHoldUntilTime" parameter allows a client to specify whether to hold the job until a specified time, indefinitely or until a specified time period, if supported. The Scan Service MUST accept or reject the request based on the job's current state and transition the job to the indicated new state as follows:

Current JobState New JobState StatusPending PendingHeld Success See Note 1Pending Pending Success See Note 2PendingHeld PendingHeld Success See Note 1PendingHeld Pending Success See Note 2Processing Processing FaultProcessingStopped ProcessingStopped FaultCompleted Completed Fault


235236

18121813181418151816

18171818181918201821

182218231824

1825182618271828

18291830

1831183218331834183518361837

237


Current JobState New JobState StatusCanceled Canceled FaultAborted Aborted Fault

Note 1: If the implementation supports multiple reasons for a job to be in the PendingHeld state, the Scan Server MUST add the 'JobHoldUntilSpecified' value to the Job's "JobStateReasons” element.

Note 2: If the Scan Service supports the "JobHoldUntil" and/or the "JobHoldUntilTime" elements, but the specified time period has already started (or is the 'NoHold' value) and there are no other reasons to hold the job, the Scan Service MUST make the job be a candidate for processing immediately by putting the job in the 'Pending' state.

In order to keep the HoldJob operation simple, a request is rejected when the job is in the 'Processing' or 'ProcessingStopped' states.

8.2.3.1 HoldJobRequest

8.2.3.2 HoldJobResponseNote: The response is expected to be an empty successful return or a fault. The response below indicates that vendors may extend the response with additional information

8.2.4 HoldNewJobsThis OPTIONAL operation allows a client to prevent any new jobs from being eligible for scheduling. If the HoldNewJobs operation is supported, then the ReleaseNewJobs operation MUST be supported, and vice-versa. The OPTIONAL "JobHoldUntil" parameter allows a client to specify whether to hold new jobs until a specified time, indefinitely or until a specified time period, if supported. While this operation is in effect all new jobs MUST have the “JobHoldUntil” or the “JobHoldUntilTime” Job Processing element added with the value from the operation. The Scan Server MUST add the 'JobHoldUntilSpecified' value to the Job's "JobStateReasons” element

8.2.4.1 HoldNewJobsRequest


238239

183818391840

184118421843

18441845

1846

18471848184918501851

18521853185418551856185718581859

1860

1861

240


8.2.4.2 HoldNewJobsResponseNote: The response is expected to be an empty successful return or a fault. The response below indicates that vendors may extend the response with additional information

8.2.5 Pause This OPTIONAL operation allows a client to stop the Scan Service from scheduling jobs. Depending on implementation, the Pause operation MAY also stop the Scan Service from processing the current job. Any job that is currently being scanned is either stopped as soon as the implementation permits or is completed, depending on implementation. The Scan Service MUST still accept CreateScanJob operations to create new jobs, but MUST prevent any jobs from entering the 'Processing' state. If the Pause operation is supported, then the Resume operation MUST be supported, and vice-versa.

The Scan Service stops the current job that is in the 'Processing' or 'ProcessingStopped' states as soon as the implementation permits. If the implementation will take appreciable time to stop, the Scan Service adds the ' MovingToPaused ' value to the Scan Service’s "StateReasons" element. When the Scan Service transitions to the 'Stopped' state, it removes the 'MovingToPaused' value, if present, and adds the 'Paused' value to the Scan Service’s "StateReasons" elemet. If the implementation permits the current job to stop in mid processing, the Scan Service transitions the Scan Job to the 'ProcessingStopped' state and adds the 'Stopped' value to the job's "JobStateReasons" element.

For any jobs that are 'pending' or 'pending-held', the ‘Stopped' value of the jobs' "JobStateReasons" element also applies. However, the Scan Service NEED NOT update those jobs' "JobStateReasons" element and only need return the 'Stopped' value when those jobs are queried (so-called "lazy evaluation").

The Scan Service MUST accept the request in any state and transition the Scan Service to the indicated new "State" before returning as follows:

Current State New State StateReason StatusIdle Stopped Paused SuccessProcessing Processing MovingTo Paused Success See Note 1Processing Stopped Paused Success See Note 2Stopped Stopped Paused SuccessNote 1: Implementation that do not pause the current job replace the “State” ‘Processing’ value with ‘Stopped’ and replace the “SateReason” value of ‘MovingToPaused’ with ‘Paused’.Note 2: Implementations that are able to pause the current job.


241242

1862186318641865

18661867186818691870187118721873

1874187518761877187818791880

188118821883

18841885

188618871888

243


8.2.6 PauseAfterCurrentJob

8.2.7 PromoteJob

8.2.8 ReleaseJob

8.2.9 ReleaseNewJobs

8.2.10 ReprocessJob

8.2.11 RestartJob

8.2.12 Resume

8.2.13 Shutdown

8.2.14 Startup

8.3 Scan Job Template Manager Operations

8.3.1 DeleteTemplate This REQUIRED operation permanently removes a Scan Template from the Scan Template Repository

8.3.1.1 DeleteTemplate Request

8.3.1.2 DeleteTemplate ResponseNote: The response is expected to be an empty successful return or a fault. The response below indicates that vendors may extend the response with additional information

8.3.2 GetTemplateThis REQUIRED operation allows a Scan Client to retrieve a copy of a Scan Template. The Scan Template may be modified. The Scan Template may be used in a CreateJob operation.


244245

1889

1890

1891

1892

1893

1894

1895

1896

1897

1898

1899

19001901

1902

19031904190519061907

1908190919101911

246


8.3.2.1 GetTemplateRequest

8.3.2.2 GetTemplateResponseISSUE19: Need schema element for Scn Template. It will be nearly identical to a Scan Ticket except it will mandate some elements such as TemplateId which are optional in a Scan Ticket

8.3.3 ListTemplatesThis REQUIRED operation allows a Scan client to get a list of Scan Template. The Scan Template List returned will provide some summary information on each Scan Template. The Scan Service SHOULD restrict the the list of Scan Templates returned based on the identity of the Scan Client.

8.3.3.1 ListTemplatesRequest

8.3.3.2 ListTemplatesResponse


247248

1912

1913191419151916

19171918191919201921

1922

19231924

19251926

249


8.3.4 PutTemplate (TemplateName, RequestingUserName, OverwriteFlag)

8.3.5 SetTemplateAccessRights (Template)

8.3.6 SetTemplateExpiration (Template)

8.3.7 ValidateTemplate (Template)

9 Conformance Requirements[TBD]

10 PWG and IANA Registration Considerations[TBD]

11 Internalization Considerations[TBD]

12 Security Considerations

12.1 Storing Scan Documents in a Document RepositoryOrganizations with higher security requirements may require end users to store their documents only in the designated Document Repositories for which organizational document access control policies can easily be instrumented. It is the end user’s responsibility to ensure that their target document repositories have been administered to support the Scan Service writes user’s Scan Document Data into the repository as long as the requesting user has been authenticated in the same network domain of the Document Repository.

12.2 Protection of End User’s Scan DocumentsAn end user’s Scan Documents can be protected from disclosure by encrypting the content of the documents and protected from modification by signing the content of the documents when these documents are stored in a repository or being transmitted over a communication link.

Signing or encrypting documents stored in a Document Repository requires secure key management which includes the selection, generation, distribution, and destruction of effective signing or encryption of each end user’s keys. Signing or encrypting document stored in a Document Repository is outside the scope of the Scan Service. It is RECOMMENDED that the end user designates a Document Repository that has their desired level of signing or encryption capabilities if so is required.

For protection of the documents transmitted over the network between a Scan Service and a Document Repository or a Scan Client, the Scan Service SHALL support the secure communication protocols required by the end user’s site policy, which may require signing and/or encryption of the transmitted document. The Scan Service SHALL have security attributes to indicate the signing or encryption support for the end user’s site policy. Different level of security requires different signing or encryption methods to be used. A site policy administrator SHOULD be responsible to manage the site security policy to ensure consistency with the site security requirements. The MFD implementer SHOULD ensure that a signing or encryption method consistent with the user’s site policy is used for transporting user’s Scan Document over a shared communication medium.


250251

1927

1928

1929

1930

1931

1932

1933

1934

1935

1936

1937

193819391940194119421943

19441945194619471948194919501951195219531954195519561957195819591960196119621963

252

Nancy Chen, Oki Data, 01/08/08,

Need to discuss and determine the security attributes requirements here.


12.3 Protection of a “Restricted Use” Scan Job TemplateAn end user could create a template to which access is restricted. A template could be created for publicly unrestricted read access, or for restricted read access by the end users within a specific group, but nobody should be allowed to modify a stored template other than the owner or other authorized user(s) of the template. An end user who has read access to a template is allowed to make a copy of the template then modify the copy subsequently.

In order to restrict the access and use of template(s) stored in the Template Repository to authorized end users, the template has TemplateName and TemplateOriginatingUserName defined that allow a template site policy to be established to specify individual and group membership for accessing a specific, uniquely named template. A template site policy is to be specified by an authorized end user or administrator for association with a Template Management Service. A Template Management Service SHALL authenticate the end user’s access rights to the template(s) for GetTemplate, ListTemplate, or PutTemplate operations. Protection of a “restricted Use” Scan Job Template is outside the scope of a Scan Service.

12.4 Restricted Use of Scan Service FeaturesA company might want to restrict certain group(s) of users to use only part of supported feature(s) of a Scan Service. The “RequestingUserName” element of the Scan Service model specified herein is the end user identifying name that is used to request for processing the submitted Scan Job. This user name can be replaced with the most authenticated name if one available. A Scan Service SHALL authenticate a user’s rights for using the requested Scan Service features based on the “RequestingUserName” against the end user’s site policy, which maybe residing in the end user’s site security framework or locally in the security database associated with the Scan Service. Implementations are free to use a variety of security framework for the user authentication. The management of the site policy for the use of Scan Service features is outside the scope of this specification.

12.5 Preventing DoS Attack Through High Priority JobA malicious user could submit a “non-interruptible job” that runs indefinitely or consumes MFD resources to eventually cause unavailability. The Scan Service SHALL authenticate the user who has submitted a “non-interruptible job” to ensure the user is trustable.

12.6 Security for Service Discovery Security threats to Service discovery include unauthorized access to service endpoint and service interface information resulting in malicious exploitation of security vulnerabilities, eventually lead to disclosure or alteration of sensitive information. Thus security considerations for service discovery SHOULD encompass access control for service discovery and protection of confidentiality and integrity of the discovery request and response information. ,

13 References [TBD]

13.1 Normative References

[prod-print2]

T. Hastings, and D. Fullman, “Internet Printing Protocol (IPP): Production Printing Attributes - Set 2”, August 21, 2002, ftp://ftp.pwg.org/pub/pwg/ipp/new_PPE/pwg-ipp-prod-print-set2-draft-v0_1-020821.pdf ,

[PWG5100.5] PWG 5100.5-2003, "Internet Printing Protocol (IPP): Document Object", October 31, 2003, D. Carney, T.

Hastings, and P. Zehler, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippdocobject10-20031031-5100.5.pdf


253254

196419651966196719681969197019711972197319741975197619771978

1979198019811982198319841985198619871988

1989199019911992

19931994199519961997

1998

1999

2000

2001

200220032004

200520062007

255

ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippdocobject10-20031031-5100.5.pdf

ftp://ftp.pwg.org/pub/pwg/ipp/new_PPE/pwg-ipp-prod-print-set2-draft-v0_1-020821.pdf

ftp://ftp.pwg.org/pub/pwg/ipp/new_PPE/pwg-ipp-prod-print-set2-draft-v0_1-020821.pdf


[PWG5101.1] PWG 5101.1-2002 Media Standardized Names, February 26, 2002

ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-5101.1.pdf

[PWG5100.3] PWG 5100.3-2001, "Internet Printing Protocol (IPP): Production Printing Attributes - Set1", February 12,

2001, K. Ocke, T. Hastings, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippprodprint10-20010212-5100.3.pdf

[PWG5100.5] PWG 5100.5-2003, "Internet Printing Protocol (IPP): Document Object", October 31, 2003, D. Carney, T.

Hastings, and P. Zehler, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippdocobject10-20031031-5100.5.pdf

[PWG5106.1-2007] PWG 5106.1-2007, "The Printer Working Group (PWG) Standardized Imaging System Counters 1.1", April

27, 2007, H. Lewis, I. McDonald, J. Thrasher, W. Wagner, and P. Zehler, ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimscount11-20070427-5106.1.pdf

[RFC2119] S. Bradner, “Key words for use in RFCs to Indicate Requirement Levels”, RFC 2119, March 1997.

[RFC 3712]P. Fleming, I. McDonald, “Lightweight Directory Access Protocol (LDAP): Schema for Printer Services”, RFC 3712, February 2004.

[RFC 2782]A. Gulbrandsen, P. Vixie, L. Esibov, ” A DNS RR for specifying the location of services (DNS SRV)”, RFC 2782, February 2000.

[rfc2911] RFC 2911 “Internet Printing Protocol/1.1 Model and Semantics”, September 2000, T. Hastings, R. Herriot,

R. deBry, S. Isaacson, P. Powell, ftp://ftp.rfc-editor.org/in-notes/rfc2911.txt

[RFC 3805] R. Bergman, H. Lewis, I. McDonald, “Printer MIB v2”, RFC 3805, June 2004.

[Others TBD]

13.2 Informative References[TBD]

14 Author’s AddressNancy ChenSolutions and TechnologyOki Data2000 Bishops Gate Blvd.Mt. Laurel, NJ 08003Phone: 856 222 7006


256257

200820092010

201120122013

2014201520162017

2018201920202021

20222023

202420252026

202720282029

203020312032

20332034

2035

2036

20372038

2039

204020412042204320442045

258

ftp://ftp.rfc-editor.org/in-notes/rfc2911.txt



ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippprodprint10-20010212-5100.3.pdf

ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-5101.1.pdf


Fax: 856 222 5130Email: [email protected]

Peter ZehlerXerox Research Center WebsterEmail: [email protected]: (585) 265-8755FAX: (585) 265-7441US Mail: Peter ZehlerXerox Corp.800 Phillips Rd.M/S 128-25EWebster NY, 14580-9701

Additional contributors: (Still to be updated)Mike Fenelon – MicrosoftAndrey Savov – ToshibaHarry Lewis – IBMIra McDonald – High NorthWalter Filbrich - SamsungGlen Petrie – EpsonKei Sando – Oki DataJerry Thrasher – LexmarkDavid Whitehead - LexmarkCraig Whittle – Sharp

15 Change Log(To be removed in final version)04/03/2008 PZ Update based on teleconferences in preparation for April face to face meeting02/25/2008 PZ partial update based on February face to face meeting01/31/2008 PZ initial version (incomplete) released for February face to face meeting


259260

2046204720482049205020512052205320542055205620572058205920602061206220632064206520662067206820692070207120722073

2074

20752076207720782079

261