1
2
November 9, 2010
wd-mfdcopymodel10-2010 Working Draft
3
The Printer Working Group
4
5
6
7
8
Copy Service
Semantic Model and Service Interface
9
10
11
12
13
14
15
16
17
18
19
20
Status: Stable
Abstract: Network print devices have evolved to support additional multifunction services, in particular Copy Service.
When Copy Devices are installed in local office or enterprise networks, they need remote service, device, and job
management capabilities so that administrators, operators, and users can monitor their health and status. In addition,
such Copy Devices need remote job submission capabilities so that operators and users can create CopyJobs without
depending entirely on local console interfaces. This document defines a semantic model for service, device, and job
management and job submission for these Copy Devices.
21
22
23
24
25
26
27
28
29
30
31
32
33
Copyright © 2010, Printer Working Group. All rights reserved.
November 9, 2010
MFD: Copy Service
34
35
36
37
38
39
Copyright (C) 2010, 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.
40
Title: Network Copy Service Semantic Model and Service Interface
41
42
43
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.
44
45
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.
46
47
48
49
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.
50
51
52
53
54
55
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:
56
[email protected]
57
58
59
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.
60
61
62
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.
63
Copyright © 2010, Printer Working Group. All rights reserved.
Page 2 of 31
November 9, 2010
MFD: Copy Service
64
About the IEEE-ISTO
65
66
67
68
69
70
71
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/).
72
73
74
75
For additional information regarding the IEEE-ISTO and its industry programs visit:
http://www.ieee-isto.org.
76
77
78
79
80
81
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.
82
83
84
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.
85
Contact information:
86
87
88
89
90
91
92
93
94
95
96
97
The Printer Working Group
c/o The IEEE Industry Standards and Technology Organization
445 Hoes Lane
Piscataway, NJ 08854
USA
About the Printer Working Group
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.html
Members 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.
98
Copyright © 2010, Printer Working Group. All rights reserved.
Page 3 of 31
MFD: Copy Service
99
November 9, 2010
Contents
100
1
Introduction ..................................................................................................................................................... 6
101
2
Summary......................................................................................................................................................... 6
102
103
104
105
106
3
107
108
109
4
110
5
111
112
113
114
115
116
117
6
118
119
120
121
122
123
124
7
125
8
CopyService Theory of Operation ................................................................................................................ 27
126
9
CopyService Interfaces ................................................................................................................................. 27
127
128
129
130
131
132
133
10
134
11
PWG and IANA Registration Considerations................................................................................................ 30
135
12
Internalization Considerations ...................................................................................................................... 30
136
13
Security Considerations ................................................................................................................................ 30
137
138
139
14
140
141
15
3.1
3.2
3.3
3.4
Terminology .................................................................................................................................................... 7
Conformance Terminology .................................................................................................................................... 7
Content Specific Terminology ................................................................................................................................ 7
Model mapping conventions .................................................................................................................................. 7
Naming conventions for Overall specification and this specification ..................................................................... 7
4.1
4.2
Rationale ......................................................................................................................................................... 7
Rationale for this CopyService Specification ......................................................................................................... 7
Out of Scope for CopyService ............................................................................................................................... 7
MFD Model Overview ..................................................................................................................................... 9
6.1
6.2
6.3
6.4
6.5
6.6
CopyService Model Overview ......................................................................................................................... 9
CopyServiceCapabilities ...................................................................................................................................... 10
CopyServiceCapabilitiesReady ........................................................................................................................... 12
CopyServiceConfiguration ................................................................................................................................... 12
CopyServiceDescription ...................................................................................................................................... 14
CopyServiceStatus .............................................................................................................................................. 15
Default CopyJobTicket......................................................................................................................................... 16
CopyJob Model ............................................................................................................................................. 18
7.1
CopyJobReceipt................................................................................................................................................... 19
7.2
CopyJobStatus..................................................................................................................................................... 19
7.3
CopyJobTicket ..................................................................................................................................................... 21
7.3.1
CopyDocumentProcessing ......................................................................................................................... 21
7.3.2
CopyJobDescription .................................................................................................................................... 24
7.3.3
CopyJobProcessing .................................................................................................................................... 25
Conformance Requirements ......................................................................................................................... 29
10.1 Client Conformance Requirements...................................................................................................................... 29
10.2 Copy Service Conformance Requirements ......................................................................................................... 29
10.2.1
Objects ........................................................................................................................................................ 29
10.2.2
Operations ................................................................................................................................................... 29
10.3 Copy Service Elements ....................................................................................................................................... 30
10.4 Extensions ........................................................................................................................................................... 30
14.1
14.2
References .................................................................................................................................................... 30
Normative References ......................................................................................................................................... 30
Informative References ........................................................................................................................................ 31
Author’s Address ........................................................................................................................................... 31
Copyright © 2010, Printer Working Group. All rights reserved.
Page 4 of 31
MFD: Copy Service
November 9, 2010
142
143
144
Figures
Figure 1 High Level CopyService Schema ............................................................................. Error! Bookmark not defined.
145
Figure 2 CopyServiceCapabilities ........................................................................................... Error! Bookmark not defined.
146
Figure 3 CopyServiceConfiguration ........................................................................................ Error! Bookmark not defined.
147
Figure 4 CopyServiceDescription............................................................................................ Error! Bookmark not defined.
148
Figure 5 CopyServiceStatus ................................................................................................... Error! Bookmark not defined.
149
Figure 6 DefaultCopyJobTicket ............................................................................................................................................. 17
150
Figure 7 JobTable ................................................................................................................................................................. 18
151
Figure 8 High Level CopyJob View ....................................................................................................................................... 19
152
Figure 9 CopyJobStatus .......................................................................................................... Error! Bookmark not defined.
153
Figure 10 CopyJobTicket ...................................................................................................................................................... 21
154
Figure 11 CopyDocumentProcessing (Input) ........................................................................................................................ 22
155
Figure 12 CopyDocumentProcessing (Output) ..................................................................................................................... 23
156
Figure 13 CopyJobDescription .............................................................................................................................................. 24
157
Figure 14 CopyJobProcessing .............................................................................................................................................. 26
158
159
160
161
Tables
Table 1 CopyServiceCapabilities .......................................................................................................................................... 11
162
Table 2 Mandatory User Operations ..................................................................................................................................... 27
163
Table 3 Optional User Operations......................................................................................................................................... 28
164
Table 4 Administrative Operations ........................................................................................................................................ 28
165
166
Copyright © 2010, Printer Working Group. All rights reserved.
Page 5 of 31
MFD: Copy Service
November 9, 2010
167
1 Introduction
168
169
170
171
172
This document specifies the PWG abstract model for Copy Services of a Multifunction Device (MFD). Included in
this document is the content specific terminology, data model, the theory of operation, the CopyService interfaces
and the conformance requirements. The MFD Copy Service abstract models include the functional models and
interfaces of the associated Copy Services for a local network or enterprise-connected multifunction device.
173
2 Summary
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
The MFD service addressed in this specification is the CopyService. The CopyService responds to queries about
its capabilities, configuration and descriptive information. It responds to queries for information about CopyJobs. It
manages and processes CopyJobs with its associated CopyJobTicket.
The CopyService, by definition, takes an input Hardcopy Document and produces an output Hardcopy Document.
Although the CopyService usually has some internal representation for the digital form of the document that is
being copied, the internal representation is not visible to the user. The result of this is that a CopyService contains
zero or more Jobs and the Jobs do not contain any documents.
Each CopyJob can contain a CopyJobTicket which provides descriptive information (i.e., CopyJobDescription) as
well as CopyJobProcessing and CopyDocumentProcessing instructions. CopyJobProcessing instructions apply to
the Job as a whole. CopyDocumentProcessing instructions specify processing instructions applied to either the
input or output Hardcopy Document. The input processing semantics are based on Scan Service Semantics [WSSCAN, PWG5108.2] while the output processing semantics are based on Print Service Semantics [RFC2911,
PWG5105.1].
A client application interacting with the CopyService contains a Copy Client. A Copy Client interacts with the End
User to obtain the End User’s Intent and uses the Copy Client to communicate with the CopyService that will
execute the CopyJob according to the End User Intent.
CopyJobTemplates contain instructions representing preconfigured Copy intent that can be used as is or modified
by the End User. Once the End User is satisfied with the CopyJobTemplate the Copy Client uses the
CopyJobTemplate as the CopyJobTicket in the job submission to the CopyService. CopyJobTemplates may be
obtained in a number of ways. Those methods are outside the scope of this specification.
The Copy scenarios addressed in this specification range from walk-up users that use MFD’s front panel to initiate
a CopyJob to remote users that use their computers to initiate a CopyJob. The assumption is that it is possible to
implement a Network Connected Copy Client that is accessible via the device’s front panel. The model also
supports external security services that protects against unauthorized use of the CopyServices and access of Copy
digital data.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 6 of 31
MFD: Copy Service
November 9, 2010
204
3 Terminology
205
3.1
Conformance Terminology
206
See
[RFC2119]for conformance terminology used. There are no Copy specific conformance terms.
207
3.2
Content Specific Terminology
208
209
210
211
212
213
214
215
216
See [MFD] for common MFD terminology used. For this service the “<service>” in the MFD Terminology section is
replaced with “Copy”. The terms used in this document are: ActiveJobs, CopyDevice, Copy Intent,
CopyJob, CopyJobReceipt, CopyJobTemplate, CopyJobTicket, Attribute, Client, CrossFeed
direction, DefaultCopyJobTicket, Digital Document, Element, Feed direction, Group
Element,
Hardcopy
Document,
Job
History,
Job
Ticket,
Local
Client,
PhysicalCopyJobTicket, Remote Client, Scan Device, Scan Region, Sequence, Service,
Slow Scan Direction, Software, Template, Users, X, Y.
217
3.3
218
219
220
221
222
223
The CopyService 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 SystemConfiguration, Services,
and their associated Jobs 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.
224
3.4
225
226
227
228
229
230
231
232
The MFD Overall specification [MFD] describes common concepts and terms used for all of the services hosted on
a multifunction device. That includes the objects and their attributes in the multifunction device data model. The
MFD Overall specification [MFD] uses abstract names for the semantic elements (e.g. Job State). This document
describes a specific service and uses an XML schema to represent the objects and attributes. XML elements
cannot have names with an embedded whitespace. The names for objects and their attributes used by this
specification are the names from the XML Schema (e.g. JobState). The names can be easily mapped between the
two specifications by inserting or removing the whitespace in the name (e.g. Job State ≡ JobState).
233
4 Rationale
234
4.1
235
236
237
238
239
240
241
In order to support common functionality for copying using multifunction devices, there is a need to develop a
semantic model and a set of abstract operations and elements for Copy related services. In order to implement an
abstract model of the operations and elements for Copy related services, there is need to map them onto
implementable applications and communication protocols that support interactions between Copy Clients and
CopyServices. There is a need to define a binding of the abstract model into Web Service Schema and Web
Service protocol stack.
242
4.2
243
244
245
246
247
The basic CopyService model defined in this document is targeted to support enterprise Copy applications.
However this document does not specify any application specific semantics. The MFD Working Group charter
[CHAR] defines the following as out of scope:
There is no Copy specific terminology.
Model mapping conventions
Naming conventions for Overall specification and this specification
Rationale for this CopyService Specification
Out of Scope for CopyService
1. Semantics of any compound service such as Copy-And-Email.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 7 of 31
MFD: Copy Service
248
249
250
251
252
November 9, 2010
2. Semantics of any workflow protocol, i.e., sequencing and coordination of CopyJobs across multiple
services.
3. Semantics of any CopyService management operations for MFDs that are not network connected.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 8 of 31
November 9, 2010
MFD: Copy Service
253
254
5 MFD Model Overview
255
256
257
See [MFD] for the overall MFD model. CopyService fits within the MFD model as one of a number of services that
can be hosted on a multifunction device (i.e., System). The critical MFD container object with regard to describing
CopyService is Services.
258
259
One of the MFD’s services is CopyService. There can be multiple instances of a CopyService hosted, each with its
own set of defaults and capabilities (e.g., separate Job queues).
260
261
262
The System has a SystemConfiguration object that contains all the subunits that comprise the MFD. Each
CopyService instance contains a service specific view of the subunits used by that service instance. The
CopyService element CopyServiceConfiguration contains the service specific view of the associated Subunits.
263
264
6 CopyService Model Overview
265
266
Below is the top level view of the CopyService schema.
267
268
269
270
271
272
273
274
275
276
277
278
Figure 1 High Level CopyService Schema
The MFD System supports zero or more CopyServices. A CopyService is hosted locally on an MFD or remotely on
another computer. The CopyService model has an Active Job queue, a Job History and a set of elements which
includes CopyService status, configuration, description, defaults, and processing capabilities.
The CopyServiceCapabilities group element contains the CopyJobTicketCapabilities. The CopyJobTicketCapabilities
represents the allowed values supported by the CopyService for a CopyJobTicket. The CopyJobTicketCapabilities
includes three sub elements. The CopyJobDescriptionCapabilities element indicates what job description elements are
supported by the service instance. The CopyDocumentProcessingCapabilities group element has all processing
elements for scanning the input Hardcopy Document and printing the output Hardcopy Document. The
Copyright © 2010, Printer Working Group. All rights reserved.
Page 9 of 31
MFD: Copy Service
November 9, 2010
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
CopyJobProcessingCapabilites group element includes all supported processing elements for CopyJobs. The details of
each processing element are specified in §6.1.
319
6.1
320
321
322
323
324
325
326
The CopyServiceCapabilities is a container element containing CopyJobTicketCapabilities that provides information
about the elements that can be used in CopyJobTickets. The values of the elements in CopyJobTicketCapabilities
indicate all the supported values for a CopyJobTicket submitted to the CopyService instance (e.g., all the media
loaded in the InputTrays or available in nearby storage locations). The names of the elements within the
CopyJobTicketCapabilities are the same as those in the DefaultCopyJobTicket. See §7.3 for the names of
theCopyDocumentProcessingCapabilities ( In and Out), CopyJobDescriptionCapabilities, and
CopyJobProcessingCapabilities elements.
327
328
329
330
331
332
333
Although most of the elements have the same name as their CopyJobTicket counterparts the syntax is often
different. For example an element such as InputSource that is a single keyword in CopyJobTicket, it is a sequence
of keywords in CopyServiceCapabilities. The values list the allowed values for the CopyJobTicket element. Some
elements that are of the data type integer in a CopyJobTicket are a range of integers in CopyJobTicketCapabilities.
Other elements that are simple strings or predefined ranges in the CopyJobTicket are simply boolean values in
CopyJobTicketCapabilities, indicating support for the associated CopyJobTicket elements. See [MFD] for details on
the syntax.
The CopyServiceCapabilitiesReady group element represents the allowed values for a CopyJobTicket that do not
require operator intervention (e.g., the media that is actually loaded in an input tray). The details are specified in §6.2
CopyServiceConfiguration provides a CopyService specific view into the Subunits that are associated with this service
instance. Only Subunits that are used by the CopyService will appear in this element. The details of each subunit are
detailed in §6.3. To see all the subunits for the MFD the System element provides an all encompassing view.
The CopyServiceDescription 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. The
details of the CopyServiceDescription elements are specified in §6.5.
The CopyServiceDefaults group element contains the DefaultCopyJobTicket. The DefaultCopyJobTicket contains the
CopyDescription, CopyJobProcessing and CopyDocumentProcessing default values. The values contained in
DefaultCopyJobTicket are the values that will be used by the CopyService when processing a CopyJobTicket which
does not specify a different value. The values for this are populated in an implementation specific manner. The details
of the DefaultCopyJobTicket are specified in §6.7.
The CopyServiceStatus 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
CopyService specific status extensions are the CopyService specific counters. The details of the elements in the
CopyServiceStatus group are specified in §6.6.
A CopyService contains zero or more jobs. Since the input and output of a CopyService is a Hardcopy Document, there
is no document object to represent an implementation specific internal Digital Document. The CopyService does not
expose any Digital Document associated with a CopyJob. Therefore, each job has exactly zero documents. The
CopyService organizes its CopyJobs in a minimum of two job queues: (1) ActiveJobs, (2) JobHistory. ActiveJobs is a
queue maintaining a list of jobs that are pending or processing. The JobHistory queue maintains a log of CopyJobs that
have reached a terminating state (i.e., Completed, Aborted, and Canceled). The retention period for jobs in the
JobHistory list is implementation specific but MUST NOT be less than 300 seconds. Each CopyJob can contain a
CopyJobTicket which provides descriptive information as well as job processing and document processing instructions.
CopyJobProcessing instructions apply to the Job as a whole while CopyDocumentProcessing instructions specify
processing instructions applied to either the input or output Hardcopy Documents. The input processing semantics are
based on Scan Service Semantics while the output processing semantics are based on Print Service Semantics.
CopyServiceCapabilities
334
Copyright © 2010, Printer Working Group. All rights reserved.
Page 10 of 31
November 9, 2010
MFD: Copy Service
335
336
337
338
Figure 2 CopyServiceCapabilities
339
340
341
Table 1 CopyServiceCapabilities
Group
CopyDocumentProcessingCapabilities
(In)
CopyDocumentProcessingCapabilities
(Out)
Elements described in [MFD]
NumberUp, PresentationDirectionNumberUp, AutoSkewCorrection,
ColorEntry, ContentType, Exposure, FilmScanMode, ImagesToTransfer,
InputSource, Resolutions1, Rotation, Scaling, DocumentSizeAutoDetect,
ScanRegions, Sides
NumberUp, PresentationDirectionNumberUp, Copies, CoverBack,
CoverFront, FinishingsCol, ForceFrontSide, ImpositionTemplate,
InsertSheet, Media, MediaType, MediaColSupported2,
MediaInputTrayCheck, OrientationRequested, OutputBin, OutputDevice,
Overrides, PageDelivery, PageRanges, PagesPerSubset,
PrintContentOptimized, Quality, Resolutions1, SeparatorSheets,
SheetCollate, Sides, XImagePosition, XImageShift, XSide1ImageShift,
XSide2ImageShift,, YImagePosition, YImageShift, YSide1ImageShift,
YSide2ImageShift,
CopyJobDescriptionCapabilities
ElementsNaturalLanguage, JobAccountingID, JobAccountingUserID,
JobInformation, JobMandatoryElements, JobMessageFromOperator,
JobMessageToOperator, JobName, JobOriginatingUserName,
JobOriginatingUserUri, JobPassword, JobPasswordEncryption, KOctets,
TemplateCreatorName, TemplateId, TemplateInfo, TemplateName,
TemplateType
CopyJobProcessingCapabilities
JobDelayOutputUntil, JobDelayOutputUntilTime, JobHoldUntil,
JobHoldUntilTime, JobMandatoryElements, JobPhoneNumber,
JobPriority, JobRecipientName, BatchMode, JobAccountingSheets,
JobCopies, JobCoverBack, JobCoverFront, JobErrorSheet,
JobFinishings, JobFinishingsCol, JobSaveDisposition,
Copyright © 2010, Printer Working Group. All rights reserved.
Page 11 of 31
November 9, 2010
MFD: Copy Service
JobSheetMessage, JobSheets, JobSheetsCol, MultipleSetOriginal,
OutputBin, Overrides
Resolution in the CopyJobTicket’s CopyDocumentProcessing is a single instance of Resolution from the
sequence of Resolutions elements in CopyDocumentProcessingCapabilities. This applies to both In and
Out.
2 MediaCol in the CopyJobTicket is a sequence (i.e. MediaColSupported) of MediaCol elements in
CopyDocumentProcessingCapabilities
1
342
343
344
345
346
347
.
348
6.2
349
350
351
352
353
354
355
CopyServiceCapabilitiesReady is a container element containing CopyJobTicketCapabilities that provides
information about the elements that can be used in CopyJobTickets. The values of the elements in
CopyJobTicketCapabilities indicate all the values for a CopyJobTicket that can be submitted to the CopyServer
instance and applied without operator intervention. .(i.e., the Media currently loaded in the InputTrays) . The names
of the elements within CopyServiceCapabilitiesReady are the same as those in CopyServiceCapabilities. See §6.1
for the names of theCopyDocumentProcessingCapabilities ( In and Out), CopyJobDescriptionCapabilities, and
CopyJobProcessingCapabilities elements.
CopyServiceCapabilitiesReady
356
357
6.3
CopyServiceConfiguration
358
359
360
361
362
363
The types of Subunits defined in the MFD Model and Overall Semantics specification [MFD] that are applicable to a
CopyService are Console, Cover, Finisher, InputChannel, InputTray, Interface, Interpreter, Marker, MediaPath,
OutputChannel, OutputTray, Processor, ScanMediaPath, Scanner, Storage and optionally VendorSubunits. There
are no standard subunits unique to the CopyService
Copyright © 2010, Printer Working Group. All rights reserved.
Page 12 of 31
November 9, 2010
MFD: Copy Service
364
365
Figure 3 CopyServiceConfiguration
366
367
368
369
6.4
CopyServiceDefault
370
371
372
373
374
375
376
The CopyServiceDefaults is a containter element. It contains the DefaultCopyJobTicket that provides the values
that will be used if the element is omitted in a CopyJob’s CopyJobTicket. Note that the processing instructions are
not bound to the CopyJob until the CopyJob is actually processed. The values from DefaultCopyJobTicket are not
copied to the Job’s CopyJobTicket. If CopyJobReceipt (See §7.1) is supported, the combined elements from the
user supplied CopyJobTicket and the applied values from the DefaultCopyJobTicket are copied to
CopyJobReceipt.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 13 of 31
November 9, 2010
MFD: Copy Service
377
378
379
380
381
382
383
Figure 4 CopyServiceDefaults
For descriptions of the elements that comprise CopyJobDescription, CopyJobProcessing and
CopyDocumentProcessing see §7.3 on CopyJobTicket below.
384
6.5
CopyServiceDescription
385
386
387
388
Below is a view of the CopyService’s CopyServiceDescription . CopyServiceDescription provide Descriptive
information for the CopyService. The element values are administratively set. The element values can be directly
or modified indirectly through an operation.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 14 of 31
November 9, 2010
MFD: Copy Service
389
390
Figure 5 CopyServiceDescription
391
392
393
394
395
The elements common to all <service>ServiceDescriptions are described in the MFD Model and Overall Semantics
specification [MFD]. Those elements are identified in the above diagram as being included in the yellow box.
There are no elements specific to the CopyServiceDescription except the usual extension point (i.e., Any).
396
6.6
397
398
399
400
401
402
403
CopyServiceStatus
Below is a view of the CopyService’s CopyServiceStatus. CopyServiceStatus provide state information for the
CopyService. The elements values are maintained by automata and cannot be directly set. The element values
can be modified indirectly through an operation. For example PauseCopyService operation on the CopyService
may result in the change of the State and StateReasons elements.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 15 of 31
November 9, 2010
MFD: Copy Service
404
405
406
407
408
409
410
411
412
413
414
Figure 6 CopyServiceStatus
The elements common to all <service>ServiceStatus are described in the MFD Model and Overall Semantics
specification [MFD]. Those elements are identified in the above diagram as being included in the yellow box. The
remaining elements are taken from <service> ServiceStatus. These elements are described in the MFD Model and
Overall Semantics specification [MFD].
6.7
415
416
Copyright © 2010, Printer Working Group. All rights reserved.
Page 16 of 31
MFD: Copy Service
November 9, 2010
417
418
419
420
421
Copyright © 2010, Printer Working Group. All rights reserved.
Page 17 of 31
November 9, 2010
MFD: Copy Service
422
7 CopyJob Model
423
424
425
426
Below is the top level view of CopyJob. The jobs appear in one of two lists. Pending and active jobs appear in
ActiveJobs. Jobs that have reached a terminal state (i.e., Completed, Aborted, and Canceled) appear in
JobHistory. The amount of time a Job is retained in the JobHistory is implementation specific but MUST NOT be
less than 300 seconds.
427
428
Figure 7 JobTable
429
430
431
432
433
434
435
436
437
438
As indicated below CopyJobs MUST contain zero documents. This is because the CopyService takes as input a
Hardcopy Document and produces a Hardcopy Document as output. Any internal digital document representation
is not visible to the User and is handled in an implementation specific manner. The state of the job is described in
CopyJobStatus. CopyJobTicket contains descriptive information about the Job (i.e., CopyJobDescription) and
processing instructions for the Job (i.e., CopyJobProcessing). CopyJobTicket also contains document processing
instructions (i.e., CopyDocumentProcessing). CopyDocumentProcessing are broken into two sets. The Input set
applies to image acquisition (i.e., scanning) and the Output set applies to the production of the output Hardcopy
Document (i.e., printing). CopyJobTicket represent the End User’s intent while CopyJobReceipt represent what the
CopyService actually did.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 18 of 31
November 9, 2010
MFD: Copy Service
439
440
Figure 8 High Level CopyJob View
441
442
443
7.1
CopyJobReceipt
444
445
446
447
448
This element has exactly the same structure as CopyJobTicket. For each processing element of a CopyJob, it
records the actual value used by the CopyService for processing the CopyJob. It contains the elements supplied
by the Copy Client and applied to the job, any element or values substitutions made by the CopyService and any
default elements or values applied by the CopyService. See §7.3 for element descriptions.
449
7.2
450
451
452
Below is a view of the CopyJob’s CopyJobStatus. CopyJobStatus provides state information for the CopyJob. The
elements are maintained by automata and cannot be directly set. The element values can be modified indirectly
CopyJobStatus
Copyright © 2010, Printer Working Group. All rights reserved.
Page 19 of 31
November 9, 2010
MFD: Copy Service
453
454
455
through an operation. For example, CancelCopyJob operation on the CopyJob may result in the change of the
State and StateReasons elements.
456
457
458
459
460
461
Figure 9 CopyJobStatus
The elements common to all <service>JobStatus are described in the MFD Model and Overall Semantics
specification [MFD]. Those elements are identified in the above diagram as being included in the yellow box. The
Copyright © 2010, Printer Working Group. All rights reserved.
Page 20 of 31
November 9, 2010
MFD: Copy Service
462
463
464
465
remaining elements are taken from <service>JobProcessing. These elements are described in the MFD Model and
Overall Semantics specification [MFD].
466
7.3
467
468
469
470
CopyJobTicket contains description and processing elements provided by the Copy client during CopyJob creation.
This information is used by the CopyService during the processing of a CopyJob. This information is made
available to Copy Clients through the GetCopyJobElements operation.
CopyJobTicket
471
472
Figure 10 CopyJobTicket
473
474
7.3.1 CopyDocumentProcessing
475
476
477
478
479
480
CopyDocumentProcessing provides the document processing instructions that have been requested by the Copy
Client at the job level. Each element has a MustHonor attribute to indicate whether documents within the job must
be processed according to what the user has requested. The CopyDocumentProcessing instructions are broken
into two sets. The Input set applies to image acquisition (i.e., scanning) and the Output set applies to the
production of the output Hardcopy Document (i.e., printing).
Copyright © 2010, Printer Working Group. All rights reserved.
Page 21 of 31
November 9, 2010
MFD: Copy Service
481
482
483
Figure 11 CopyDocumentProcessing (Input)
484
485
The elements in the Input set are a subset of the ScanDocumentProcessing element in the Scan Service and are
described in the MFD Model and Overall Semantics specification [MFD].
Copyright © 2010, Printer Working Group. All rights reserved.
Page 22 of 31
November 9, 2010
MFD: Copy Service
486
487
488
489
490
491
492
Figure 12 CopyDocumentProcessing (Output)
The elements in the Output set are a subset of the PrintDocumentProcessing element in the Print Service and are
described in the MFD Model and Overall Semantics specification [MFD].
Copyright © 2010, Printer Working Group. All rights reserved.
Page 23 of 31
November 9, 2010
MFD: Copy Service
493
494
7.3.2 CopyJobDescription
495
496
497
Below is a view of the CopyJob’s CopyJobDescription . These elements are set by the Copy Client during job
creation.
498
499
Figure 13 CopyJobDescription
500
Copyright © 2010, Printer Working Group. All rights reserved.
Page 24 of 31
MFD: Copy Service
November 9, 2010
501
502
503
504
505
The elements common to all <service>JobDescriptions are described in the MFD Model and Overall Semantics
specification [MFD]. Those elements are identified in the above diagram as being included in the yellow box.
There are no elements specific to the CopyJobDescription except the usual extension point (i.e., Any).
506
7.3.3 CopyJobProcessing
507
508
509
510
511
CopyJobProcessing provides the job processing instructions that have been requested by the Copy Client.
Each element has a MustHonor attribute. When the value of MustHonor is true, the CopyService does not
process the job unless the element is supported; otherwise the CopyService processes the job with its best
effort.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 25 of 31
November 9, 2010
MFD: Copy Service
512
513
514
515
516
517
518
Figure 14 CopyJobProcessing
The elements common to all <service>JobProcessing are described in the MFD specifications [MFD]. Those
elements are identified in the above diagram as being included in the yellow box. The remaining elements are
taken from PrintJobProcessing. These elements are described in the MFD Model and Overall Semantics
specification [MFD].
Copyright © 2010, Printer Working Group. All rights reserved.
Page 26 of 31
November 9, 2010
MFD: Copy Service
519
520
521
522
8 CopyService Theory of Operation
523
524
The CopyService follows the behaviors and state transitions defined in the MFD Model and Overall Semantics
specification [MFD].
525
9 CopyService Interfaces
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
The CopyService provides a set of service interfaces that is the same for a co-located local Copy Client or a
Remote Copy Client via a local interface, a local area network, or the Internet. A user makes a CopyService
request by interacting directly with the CopyService or indirectly through a local Copy Client via the MFD UI or a
Remote Copy Client via its software application UI.
The requests below that are expected to have parameters are defined as containing an extension point indicating
that vendors may extend the request with additional information. Responses to operations that fail are expected to
return a fault. Responses that are expected to have no parameters are defined as containing an extension point
indicating that vendors may extend the request with additional information.
The semantics for these operations are the same as the operations specified in the MFD Model and Overall
Semantics specification [MFD]. The exception is that since the CopyService does not expose a document no
operations(e.g., SetCopyDocumentElements) or elements (e.g., CopyDocumentProcessing) associated with a
document object are applicable to this service. In the table below required parameters are in bold and option
operations and parameters are in italic font.
542
Table 2 Mandatory User Operations
User
Operation Name
CancelCopyJob
CreateCopyJob
GetActiveCopyJobs
GetCopyJobElements
GetCopyJobHistory
GetCopyServiceElements
SetCopyJobElements
ValidateCopyJobTicket
Input Parameters
ElementsNaturalLanguage, JobId,
Message, RequestingUserName
CopyJobTicket, ElementsNaturalLanguage,
RequestingUserName
ElementsNaturalLanguageRequested, limit,,
RequestingUserName
ElementsNaturalLanguageRequested,
JobId, RequestedElements,
RequestingUserName
ElementsNaturalLanguageRequested, limit,,
RequestingUserName
ElementsNaturalLanguageRequested,
RequestedElements,
RequestingUserName
CopyJobTicket, JobId,,
ElementsNaturalLanguage, Message,
RequestingUserName
CopyJobTicket, ElementsNaturalLanguage,
RequestingUserName
Copyright © 2010, Printer Working Group. All rights reserved.
Output Parameters
JobId, UnsupportedElements
ActiveJobs,
ElementsNaturalLanguage
CopyJobElements,
ElementsNaturalLanguage
JobHistory,
ElementsNaturalLanguage
CopyServiceElements,
ElementsNaturalLanguage
UnsupportedElements
UnsupportedElements
Page 27 of 31
November 9, 2010
MFD: Copy Service
543
Table 3 Optional User Operations
User
Operation Name
CancelCurrentCopyJob
CancelMyCopyJobs
HoldCopyJob
ReleaseCopyJob
ResubmitCopyJob
ResumeCopyJob
SuspendCurrentCopyJob
544
Input Parameters
ElementsNaturalLanguage, JobIds,
Message, RequestingUserName
ElementsNaturalLanguage, JobId,
Message, RequestingUserName
ElementsNaturalLanguage JobId,
JobHoldUntil | JobHoldUntilTime,
Message, RequestingUserName
ElementsNaturalLanguage JobId,
Message, RequestingUserName
CopyJobTicket, ElementsNaturalLanguage,
JobId, RequestingUserName
ElementsNaturalLanguage JobId,
Message, RequestingUserName
ElementsNaturalLanguage JobId, Message,
RequestingUserName
Output Parameters
JobIds
JobId, UnsupportedElements
Table 4 Administrative Operations
Administrative
Operation Name
CancelCopyJobs
DisableCopyService
EnableCopyService
HoldNewCopyJobs
PauseCopyService
PauseCopyServiceAfterCurrentJob
PromoteCopyJob
ReleaseNewCopyJobs
RestartCopyService
ResumeCopyService
SetCopyServiceElements
ShutdownCopyService
StartupCopyService
Input Parameters
ElementsNaturalLanguage, JobIds,
Message, RequestingUserName
ElementsNaturalLanguage, Message,
RequestingUserName
ElementsNaturalLanguage, Message,
RequestingUserName
ElementsNaturalLanguage JobHoldUntil |
JobHoldUntilTime, Message,
RequestingUserName
ElementsNaturalLanguage Message,
RequestingUserName
ElementsNaturalLanguage Message,
RequestingUserName
ElementsNaturalLanguage JobId,
Message, PredecessorJobId,
RequestingUserName
ElementsNaturalLanguage, Message,
RequestingUserName
ElementsNaturalLanguage, Id,
IsAcceptingJobs, Message,
RequestingUserName, ServiceType,
StartServicePaused
ElementsNaturalLanguage, Message,
RequestingUserName
CopyServiceElements,
ElementsNaturalLanguage, Message,
RequestingUserName
ElementsNaturalLanguage, Id, Message,
RequestingUserName, ServiceType
ElementsNaturalLanguage, Id,
IsAcceptingJobs, Message,
RequestingUserName, ServiceType,
StartServicePaused
Copyright © 2010, Printer Working Group. All rights reserved.
Output Parameters
JobIds
UnsupportedElements
Page 28 of 31
November 9, 2010
MFD: Copy Service
545
546
547
10 Conformance Requirements
548
549
550
This section describes conformance issues and requirements. This document introduces model entities such as
objects, operations, elements, element syntaxes, and element values. These conformance sections describe the
conformance requirements which apply to these model entities.
551
10.1 Client Conformance Requirements
552
553
554
555
A conforming client MUST support all REQUIRED operations as defined in this document. For each parameter
included in an operation request, a conforming client MUST supply a value whose type and value syntax conforms
to the requirements of the Model document as specified in Section 9. A conforming client MAY supply any
extensions in an operation request, as long as they meet the requirements in Section 10.4.
556
557
When sending a request, a conforming client NEED NOT supply any parameters that are indicated as
OPTIONALLY supplied by the client.
558
559
A client MUST be able to accept any of the elements defined in the model, including their full range that may be
returned to it in a response from a Copy Service
560
561
562
563
An operation response may contain elements and/or values that the client does not expect. Therefore, a client
implementation MUST gracefully handle such responses and not refuse to inter-operate with a conforming Copy
Service that is returning extended elements and/or values that conform to Section 10.4 . Clients may choose to
ignore any parameters, elements, or values that they do not understand.
564
10.2 Copy Service Conformance Requirements
565
566
This section specifies the conformance requirements for conforming implementations with respect to objects,
operations, and attributes.
567
568
10.2.1 Objects
569
570
571
Conforming implementations MUST implement all of the model objects and the mandatory elements they
contain as defined in this specification in the indicated sections:
572
573
Section 6 - CopyService
Section 7 - CopyJob
574
10.2.2 Operations
575
576
Conforming Copy Service implementations MUST implement all of the REQUIRED model operations, including
REQUIRED responses, as defined in this specification in section 9:
CancelCopyJob
CreateCopyJob
ValidateCopyJobTicket
577
578
579
580
581
582
GetActiveCopyJobs
GetCopyJobHistory
GetCopyServiceElements
GetCopyJobElements
Conforming Copy Service MUST support all REQUIRED operation elements and all values of such elements if so
indicated in the description. Conforming Copy Service MUST ignore all unsupported or unknown operation
elements received in a request, but MUST reject a CreateCopyJob request that contains an unknown element that
contains the MustHonor attribute with a value of ‘true’.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 29 of 31
MFD: Copy Service
November 9, 2010
583
10.3 Copy Service Elements
584
Conforming Copy Service MUST support all of the REQUIRED object elements, as defined in this specification.
585
586
587
If an object supports an element, it MUST support only those values specified in this document or through the
extension mechanism described in section 10.4. It MAY support any non-empty subset of these values. That is, it
MUST support at least one of the specified values and at most all of them.
588
10.4 Extensions
589
590
591
592
593
Conforming Copy Service MAY support extensions. To extend the model the extensions MUST be fully qualified.
The qualified name MUST NOT be in the PWG target namespace. When extending the model with new elements
the new elements MUST be added at the extension points at the end of the associated sequence of elements.
Extended values for elements MUST conform to the extension patterns defined in the element schema.
Implementers are free to add vendor specific operations to the service.
594
11 PWG and IANA Registration Considerations
595
596
This specification abides by the guidelines set forth in the” MFD Model and Overall Semantics” specification
(section 10).
597
12 Internalization Considerations
598
599
This specification abides by the guidelines set forth in the” MFD Model and Overall Semantics” specification
(section 11).
600
13 Security Considerations
601
602
This specification abides by the guidelines set forth in the” MFD Model and Overall Semantics” specification
(section 12).
603
14 References
604
14.1 Normative References
605
606
607
[MFD]
608
609
610
[PWG5105.1]
<AddPWGDocumnentNumberHere/> MFD Model and Overall Semantics version 1, <AddDateHere/>, W.
Wagner, <AddDocumentsUrlHere/>
PWG 5105.1-2004 Printer Working Group (PWG) Semantic Model version 1, January 20, 2004, P. Zehler,
T.Hastings, S. Albright, ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm10-20040120-5105.1.pdf
611
612
613
[PWG5108.2]
614
615
[RFC2119]
PWG 5108.2-2009 Network Scan Service Semantic Model and Service Interface version 1, April 10, 2009,
N. Chen, P. Zehler, ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-scan10-20090410-5108.02.pdf
RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels”, S. Bradner , March 1997.
Copyright © 2010, Printer Working Group. All rights reserved.
Page 30 of 31
MFD: Copy Service
616
617
618
[RFC2911]
619
620
621
[WS-SCAN]
November 9, 2010
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
“CopyService DefinitionVersion 1.0 For Web Services on Devices”, November 2006, Microsoft, M Fenelon,
http://www.microsoft.com/whdc/connect/rally/wsdspecs.mspx
622
623
14.2 Informative References
624
625
626
[CHAR]
“Charter of the PWG Multifunction Device (MFD) Working Group”, May 4, 2007, P. Zehler, I. McDonald,
ftp://ftp.pwg.org/pub/pwg/mfd/charter/ch-mfd-20070504.pdf
627
15 Author’s Address
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
Peter Zehler
Xerox Research Center Webster
Email: [email protected]
Voice: (585) 265-8755
Fax: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
Additional contributors:
Nancy Chen – OkiData
Lee Farrell – Cannon
Ira McDonald – High North
Bill Wagner – TIC
Copyright © 2010, Printer Working Group. All rights reserved.
Page 31 of 31