1
May 13, 2011
2
Working Draft
3
The Printer Working Group
4
5
6
7
8
MFD System Object and
System Control Service
Semantics
9
10
Status: Interim
11
12
13
14
15
16
17
18
19
20
21
22
Abstract: Network print devices have evolved to support additional functions. The Multifunction Devices (MFD) includes
additional services such as scan, copy and facsimile. The MFD Model and Common Semantics [PWG51008.1] extends
the original PWG Semantic Model v1 [PWG5105.1] from printing to all of the services that typically may be performed by a
Multifunction Device (MFD). The extension required a root element to represent the MFD and to move the print service to
be one of the hosted document related services. The root of the data model is the System Object. The System Object
represents the MFD. The System Object contains the elements that represent the MFD status, description and services.
The extension of the model included bringing in elements that until now were primarily accessed via SNMP. This includes
the configuration (i.e., Subunits) and conditions that are represented in the Printer MIB[RFC3805] as entries in the Alert
Table. The System Object’s elements contain information that is not visible to any individual service. For example the
MFD wide usage counters, all the conditions, and every Subunits.
23
24
25
26
The MFD hosts a number of services. Many of these services are document related such as print, scan and copy. This
specification defines the SystemControlService. The SystemControlService is needed to start services that have been
shutdown. It is desirable to be able to monitor and manage an MFD as a whole or all the document related services at
once. The MFD’s SystemControlService provides this functionality. .
27
28
29
30
31
32
33
34
35
36
This document is a PWG Working Draft. For a definition of "PWG
Working Draft", see:
ftp://ftp.pwg.org/pub/pwg/general/pwg-process30.pdf
This document is available electronically at:
ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdsystemcontrolservicemodel10-20110513.pdf
37
Copyright © 2011, Printer Working Group. All rights reserved.
MFD System Object and System Control Service Semantics
May 13, 2011
38
Copyright (C) 2011, The Printer Working Group. All rights reserved.
39
40
41
42
43
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.
44
Title: MFD System Object and System Control Service Semantics
45
46
47
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.
48
49
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.
50
51
52
53
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.
54
55
56
57
58
59
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:
60
info@ieee-isto.org
61
62
63
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.
64
65
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.
66
67
Copyright © 2010-2011, Printer Working Group. All rights reserved.
Page 2 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
68
About the IEEE-ISTO
69
70
71
72
73
74
75
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/).
76
77
78
79
For additional information regarding the IEEE-ISTO and its industry programs visit:
http://www.ieee-isto.org.
80
81
82
83
84
85
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.
86
87
88
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.
89
Contact information:
90
91
92
93
94
95
96
97
98
99
100
101
About the Printer Working Group
The Printer Working Group
c/o The IEEE Industry Standards and Technology Organization
445 Hoes Lane
Piscataway, NJ 08854
USA
MFD Web Page: http://www.pwg.org/mfd
MFD Mailing List: mfd@pwg.org
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.
102
Copyright © 2010-2011, Printer Working Group. All rights reserved.
Page 3 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
103
Contents
104
1
Introduction ..................................................................................................................................................... 6
105
2
Summary......................................................................................................................................................... 6
106
107
108
3
109
110
111
112
4
113
5
114
115
116
117
6
118
119
120
121
122
7
123
124
125
126
127
128
8
129
9
PWG Registration Considerations ................................................................................................................ 17
130
10
Internalization Considerations ...................................................................................................................... 17
131
11
Security Considerations ................................................................................................................................ 17
132
133
134
12
135
136
13
3.1
3.2
Terminology .................................................................................................................................................... 7
Conformance Terminology .................................................................................................................................... 7
Content Specific Terminology ................................................................................................................................ 7
4.1
4.2
4.3
Rationale ......................................................................................................................................................... 7
Rationale for this Specification .............................................................................................................................. 7
Out of Scope for this Specification......................................................................................................................... 7
Conventions for Mapping the Model to XML Schema .......................................................................................... 7
MFD Model Overview ..................................................................................................................................... 8
6.1
6.2
6.3
System Object................................................................................................................................................. 8
SystemConfiguration ............................................................................................................................................. 9
SystemDescription ................................................................................................................................................. 9
SystemStatus ....................................................................................................................................................... 10
7.1
7.2
7.3
7.4
SystemControlService .................................................................................................................................. 12
SystemControlService Theory of Operation ........................................................................................................ 12
SystemControlServiceDescription ....................................................................................................................... 12
SystemControlServiceStatus ............................................................................................................................... 13
SystemControlService Interfaces ........................................................................................................................ 14
Conformance Requirements ......................................................................................................................... 16
8.1
Client Conformance Requirements...................................................................................................................... 16
8.2
SystemControlService Conformance Requirements .......................................................................................... 16
8.2.1
Objects ........................................................................................................................................................ 17
8.2.2
Operations ................................................................................................................................................... 17
8.3
Extensions ........................................................................................................................................................... 17
12.1
12.2
References .................................................................................................................................................... 17
Normative References ......................................................................................................................................... 17
Informative References ........................................................................................................................................ 19
Author’s Address ........................................................................................................................................... 19
Copyright © 2010-2011, Printer Working Group. All rights reserved.
Page 4 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
137
138
Figures
139
Figure 1 System Object ........................................................................................................................................................... 8
140
Figure 2 SystemConfiguration................................................................................................................................................. 9
141
Figure 3 SystemDescription .................................................................................................................................................. 10
142
Figure 4 SystemStatus .......................................................................................................................................................... 11
143
Figure 5 SystemControlService ............................................................................................................................................ 12
144
Figure 6 SystemControlServiceDescription .......................................................................................................................... 13
145
Figure 7 SystemControlServiceStatus .................................................................................................................................. 14
146
147
148
Tables
149
Table 1 Mandatory System Operations ................................................................................................................................ 15
150
Table 2 OptionalSystem Operations ..................................................................................................................................... 16
151
Copyright © 2010-2011, Printer Working Group. All rights reserved.
Page 5 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
152
1 Introduction
153
154
155
This document specifies the PWG abstract model for the System object and the SystemControlService of a
Multifunction Device (MFD). Included in this document is the content specific terminology, data model, the theory
of operation, the SystemControlService interfaces and the conformance requirements.
156
2 Summary
157
158
159
The MFD service addressed in this specification is the SystemControlService. The SystemControlService
responds to queries about the System Object’s capabilities, configuration, status and descriptive information. The
SystemControlService acts upon requests to modify System Object’s data.
160
161
162
A client application interacting with the SystemControlService contains a System Client. A System Client interacts
with the End User to obtain the End User’s directives and uses the System Client to communicate with the
SystemControlService that will execute the directive.
163
164
165
166
167
The System scenarios addressed in this specification include walk-up users that use MFD’s front panel to initiate
requests, and remote users that use their computers to initiate requests. The assumption is that it is possible to
implement a Network Connected System Client that is accessible via the device’s front panel. The model also
supports external security services that protects against unauthorized use of the SystemControlService and access
of System Object’s data.
168
Copyright © 2011, Printer Working Group. All rights reserved.
Page 6 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
169
3 Terminology
170
3.1
171
172
See [PWG5108.1] for conformance terminology used. There are no SystemControlService specific conformance
terms.
173
3.2
174
175
See [PWG5108.1] for common MFD terminology used. For this service the “<service>” in the MFD Terminology
section is replaced with “System”. There is no SystemControlService specific terminology.
176
4 Rationale
177
4.1
178
179
180
181
182
183
184
In order to support common functionality for managing and monitoring multifunction devices, there is a need to
develop a semantic model and a set of abstract operations and elements for System related services. In order to
implement an abstract model of the operations and elements for the MFD System, there is need to map them onto
implementable applications and communication protocols that support interactions between System Clients and
SystemControlService. Associated with this specification is a binding of the abstract model into XML Schema.
Associated with the SystemControlService’s operations is a Web Services Definition Language (WSDL)
representation.
185
4.2
186
187
188
The basic SystemControlService model defined in this document is targeted to support enterprise
SystemControlService applications. However this document does not specify any application specific semantics.
The MFD Working Group charter [CHAR] defines the following as out of scope:
Conformance Terminology
Content Specific Terminology
Rationale for this Specification
Out of Scope for this Specification
189
1. Semantics of any compound service such as Copy-And-Email.
190
2. Semantics of any workflow protocol, i.e., sequencing and coordination of Jobs across multiple services.
191
4.3
Conventions for Mapping the Model to XML Schema
192
193
194
195
196
197
The SystemControlService 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, SystemStatus, and Services 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.
Copyright © 2011, Printer Working Group. All rights reserved.
Page 7 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
198
199
5 MFD Model Overview
200
201
202
203
204
There is both a SystemControlService and a System Object in the MFD Model. The distinction between them is
that the System Object represents the MFD as a whole and is the root container for all the MFD attributes,
components and services. The SystemControlService acts upon the System object on behalf of
SystemControlService Clients to query the state of the System object and to affect the System object state through
a well-defined set of operations
205
206
207
208
209
210
The SystemControlService fits within the MFD model as one of a number of services that can be hosted on a
multifunction device (i.e., System or System object). One difference between the SystemControlService and other
hosted services is that there is only a single instance. Another difference is that that since this service is not job
oriented there are no jobs coming in or output produced and no subordinate DefaultJobTicket or Capabilities. Since
the SystemControlService provides a management interface for the entire system, the mandatory
SystemControlService is always active while the MFD is available. . (See [PWG5108.1])
211
Figure 1 and §6 define the System Object schema which represents the MFD.
212
213
214
Figure 1 System Object
215
216
6 System Object
217
218
219
220
The System Object elements SystemConfiguration, SystemDescription and SystemStatus are defined in §6.1, §6.2
and §6.3 respectively. The Services element contains all the hosted services. See §7 below for the description of
the SystemControlService. The other services outside the scope of this specification are covered in their own
specification. See [PWG5106.2-2006] for descriptions of the optional Managers, Agents and Devices elements.
Copyright © 2011, Printer Working Group. All rights reserved.
Page 8 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
221
6.1
SystemConfiguration
222
223
224
225
The System object has a SystemConfiguration element that contains all the subunits that comprise the MFD. Note
that each service instance contains a service specific view of the subunits used by that service instance. For
example a PrintService has a Marker subunit but ScanService does not. The MFD Model and Common
Semantics specification [PWG5108.1] defines all the Subunits.
226
227
228
Figure 2 SystemConfiguration
229
230
6.2
SystemDescription
231
232
233
234
235
Figure 3 is a view of the MFD’s SystemDescription. SystemDescription provide descriptive information for the entire
MFD. The element values are administratively set. The element values can be modified directly or modified indirectly
through an operation. The SystemDescription group element includes descriptive information such as system name
and location, and has extension point for vendor specific information. The MFD Model and Common Semantics
specification [PWG5108.1] defines the elements that are used in the SystemDescription element.
236
Copyright © 2011, Printer Working Group. All rights reserved.
Page 9 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
237
238
Figure 3 SystemDescription
239
240
241
6.3
SystemStatus
242
243
244
Figure 4 is a view of the MFDS’s SystemStatus. SystemStatus provides an optimistic roll-up of state information for
the hosted services. What is meant by that is if any service is ‘Processing’, the SystemStatus State element will be
‘Processing’. This is the case even if one or more of the services are in the ‘Stopped’ state.
245
246
The elements values are maintained by automata and cannot be directly set. The element values can be modified
indirectly through an operation. For example the PauseAllSystemServices operation on the SystemControlService
Copyright © 2011, Printer Working Group. All rights reserved.
Page 10 of 19
MFD System Object and System Control Service Semantics
247
248
May 13, 2011
may result in the change of the State and StateReasons elements. The MFD Model and Common Semantics
specification [PWG5108.1] defines the elements that are used in the SystemStatus element.
249
250
251
Figure 4 SystemStatus
252
Copyright © 2011, Printer Working Group. All rights reserved.
Page 11 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
253
7 SystemControlService
254
7.1
255
256
257
The MFD System supports exactly one SystemControlService. A SystemControlService is hosted locally on an MFD or
remotely on another computer. The SystemControlService model a set of elements for SystemControlService status,
and description.
258
259
260
While the SystemControlService provides operations to obtain an MFD wide view of the Subunits that comprise the
MFD, they are not subordinate to the SystemControlService. The Subunits (i.e., SystemConfiguration) appear at the
root of the model and are defined in §6.1.
261
262
263
The SystemControlServiceDescription 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 SystemControlServiceDescription elements are specified in §7.2.
264
265
266
The SystemControlServiceStatus group element is an extension of SystemServiceStatus class that includes elements
such as ID, state, state messages and state reasons. State messages are localized state reasons. The details of the
elements in the SystemControlServiceStatus group are specified in §7.3.
SystemControlService Theory of Operation
267
268
Figure 5 SystemControlService
269
7.2
SystemControlServiceDescription
270
271
272
273
274
275
Figure 6 is a view of the SystemControlServiceDescription. SystemControlServiceDescription provide Descriptive
information for the SystemControlService. The element values are administratively set. The element values can be
modified directly or modified indirectly through an operation. The SystemControlServiceDescription group element
includes descriptive information such as service name and information, and has extension point for vendor specific
information. The MFD Model and Common Semantics specification [PWG5108.1] defines the
SystemControlServiceDescription elements.
276
Copyright © 2011, Printer Working Group. All rights reserved.
Page 12 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
277
278
Figure 6 SystemControlServiceDescription
279
280
281
282
The elements common to all <service>ServiceDescriptions are defined in the MFD Model and Common Semantics
specification [PWG5108.01]. Those elements are identified in the above diagram by being included in the yellow
box. The remaining elements also are taken from <service> ServiceDescription. These elements are defined in
the MFD Model and Common Semantics specification [PWG5108.01].
283
7.3
284
285
286
287
288
Figure 7 is a view of the SystemControlService’s SystemControlServiceStatus. SystemControlServiceStatus
provide state information for the SystemControlService. The elements values are maintained by automata and
cannot be directly set. The element values can be modified indirectly through an operation. For example
PauseAllServices operation on the SystemControlService may result in the change of the State and StateReasons
elements.
SystemControlServiceStatus
Copyright © 2011, Printer Working Group. All rights reserved.
Page 13 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
289
290
291
292
293
294
Figure 7 SystemControlServiceStatus
The elements common to all <service>ServiceStatus are defined in the MFD Model and Common Semantics
specification [PWG5108.01]. Those elements are identified in the above diagram by being included in the yellow
box. There are no elements specific to the SystemControlServiceStatus except the usual extension point (i.e.,
Any).
295
296
7.4
SystemControlService Interfaces
297
298
299
300
The SystemControlService provides a set of service interfaces that is the same for a co-located local System Client
or a Remote System Client via a local interface, a local area network, or the Internet. A user makes a
SystemControlService request by interacting directly with the SystemControlService or indirectly through a local
System Client via the MFD UI or a Remote System Client via its software application UI.
Copyright © 2011, Printer Working Group. All rights reserved.
Page 14 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
301
302
Table 1 and Table 2 lists the input and output parameters for the defined operations.
that fail are expected to return a fault.
Responses to operations
303
304
305
306
The semantics for these operations are similar to the operations specified in the MFD Model and Common
Semantics specification [PWG5108.1]. One difference is that many of the operations affect all the hosted
document related services instead of an individual service. In the tables below the required parameters are in bold
and optional parameters are in normal font.
307
Table 1 Mandatory System Operations
User
Operation Name
Input Parameters
Output Parameters
DeleteService
ElementsNaturalLanguage, Id,
Message, RequestingUserName,
ServiceType
DisableAllServices
ElementsNaturalLanguage, Message,
RequestingUserName
EnableAllServices
ElementsNaturalLanguage, Message,
RequestingUserName
GetSystemElements
ElementsNaturalLanguageRequested,
RequestedElements,
RequestingUserName
ElementsNaturalLanguage,
System Elements,
ListServices
ElementsNaturalLanguageRequested,
, RequestingUserName
ElementsNaturalLanguage,
List of service summary,
PauseAllServices
ElementsNaturalLanguage, Message,
RequestingUserName
Power
TBD
RestartAllServices
ElementsNaturalLanguage,
IsAcceptingJobs, Message,
RequestingUserName,
StartsServicePaused
RestartService
ElementsNaturalLanguage, Id,
IsAcceptingJobs, Message,
RequestingUserName, ServiceType,
StartServicePaused
RestartSystemControlService
ElementsNaturalLanguage,
Message, RequestingUserName
ResumeAllServices
ElementsNaturalLanguage, Message,
RequestingUserName
ShutdownAllServices
ElementsNaturalLanguage, Message,
RequestingUserName
ShutdownService
ElementsNaturalLanguage, Id,
Message, RequestingUserName
ServiceType
StartupAllServices
ElementsNaturalLanguage,
IsAcceptingJobs, Message,
RequestingUserName,
StartSystemPaused
Copyright © 2011, Printer Working Group. All rights reserved.
TBD
Page 15 of 19
MFD System Object and System Control Service Semantics
User
Operation Name
Input Parameters
May 13, 2011
Output Parameters
ElementsNaturalLanguage, Id,
IsAcceptingJobs, Message,
RequestingUserName ServiceType,
StartServicePaused
StartupService
308
Table 2 OptionalSystem Operations
Administrative
Operation Name
Input Parameters
DeleteService
Id, ElementsNaturalLanguage,
Message, RequestingUserName,
ServiceType
PauseAllServicesAfterCurrentJob
ElementsNaturalLanguage,
Message, RequestingUserName
SetSystemElements
ElementsNaturalLanguage,
Message, RequestingUserName
SystemElements
Output Parameters
UnsupportedElements
309
310
311
8 Conformance Requirements
312
313
314
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.
315
8.1
316
317
318
319
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 7.4. A conforming client MAY supply any
extensions in an operation request, as long as they meet the requirements in Section 8.3.
320
321
When sending a request, a conforming client NEED NOT supply any parameters that are indicated as
OPTIONALLY supplied by the client.
322
323
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 SystemControlService
324
325
326
327
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
SystemControlService that is returning extended elements and/or values that conform to Section 8.3. Clients may
choose to ignore any parameters, elements, or values that they do not understand.
328
8.2
329
330
This section specifies the conformance requirements for conforming implementations with respect to objects,
operations, and attributes.
Client Conformance Requirements
SystemControlService Conformance Requirements
Copyright © 2011, Printer Working Group. All rights reserved.
Page 16 of 19
MFD System Object and System Control Service Semantics
May 13, 2011
331
8.2.1 Objects
332
333
Conforming implementations MUST implement all of the model objects and the mandatory elements they
contain as defined in this specification in the indicated sections:
Section 6 – System Object
334
335
336
337
If an object supports an element, it MUST support only those values specified in this document or through the
extension mechanism defined in section 8.3. 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 including extensions.
338
8.2.2 Operations
339
340
Conforming SystemControlService implementations MUST implement all of the REQUIRED SystemControlService
operations, including REQUIRED requests and responses, as defined in this specification in Table 1:
341
342
343
Conforming SystemControlService MUST support all REQUIRED operation elements and all values of such
elements if so indicated in the description. Conforming SystemControlService MUST ignore all unsupported or
unknown operation elements received in a request.
344
8.3
345
346
347
348
349
Conforming SystemControlService 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.
350
9 PWG Registration Considerations
351
352
This specification abides by the guidelines set forth in the MFD Model and Common Semantics specification
[PWG5108.01] (section 10).
353
10 Internalization Considerations
354
355
This specification abides by the guidelines set forth in the MFD Model and Common Semantics specification
[PWG5108.01] (section 11).
356
11 Security Considerations
357
358
This specification abides by the guidelines set forth in the MFD Model and Common Semantics specification
[PWG5108.01] (section 12).
359
12 References
360
12.1 Normative References
361
[PWG5108.01]
362
363
Extensions
PWG 5108.1-2011 MFD Model and Common Semantics version 1, April 15, 2011, W. Wagner, P. Zehler
ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-mfdmodel10-20110415-5108.1.pdf
Copyright © 2011, Printer Working Group. All rights reserved.
Page 17 of 19
MFD System Object and System Control Service Semantics
364
[PWG5105.1]
365
366
367
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
[PWG5108.2]
368
369
370
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
[PWG5101.1]
371
372
373
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]
374
375
376
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
[PWG5106.1-2007]
377
378
379
380
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
[PWG5106.2-2006]
381
382
383
384
PWG 5106.2-2006, "The Printer Working Group (PWG) Web-based Imaging Management Service v1.0",
April 21, 2006, L Farrell, R. Landau, H. Lewis, I. McDonald, J. Thrasher, W. Wagner, and P. Zehler,
ftp://ftp.pwg.org/pub/pwg/candidates/cs-wims10-20060421-5106.2.pdf
[RFC2119]
S. Bradner, “Key words for use in RFCs to Indicate Requirement Levels”, RFC 2119, March 1997.
385
386
[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
387
388
389
[RFC 3805]
R. Bergman, H. Lewis, I. McDonald, “Printer MIB v2”, RFC 3805, June 2004.
390
391
[rfc3066]
RFC 3066 “Tags for the Identification of Languages”, January 2001, H. Alvestrand,
http://www.ietf.org/rfc/rfc3066.txt
392
393
394
[RFC4395]
RFC 4395 “Guidelines and Registration Procedures for New URI Schemes”, February 2006, T. Hansen, T.
Hardie, L. Masinter, http://www.rfc-editor.org/rfc/rfc4395.txt
395
396
397
[WS-SCAN]
“SystemControlService DefinitionVersion 1.0 For Web Services on Devices”, November 2006, Microsoft, M
Fenelon, http://www.microsoft.com/whdc/connect/rally/wsdspecs.mspx
398
399
400
May 13, 2011
[CHAR]
Copyright © 2011, Printer Working Group. All rights reserved.
Page 18 of 19
MFD System Object and System Control Service Semantics
401
402
403
404
405
406
P. Zehler, and I. McDonald, “Charter of the PWG Multifunction Device (MFD) Working Group (WG)”, May 4,
2007, ftp://ftp.pwg.org/pub/pwg/mfd/charter/ch-mfd-20070504.pdf
[PWG 5100.11-2010]
PWG 5100.11-2010, Internet Printing Protocol (IPP): Job and Printer Extensions – Set 2 (JPS2), T. Hastings,
and D. Fullman, October 30, 2010, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext1020101030-5100.11.pdf
407
12.2 Informative References
408
13 Author’s Address
409
410
411
412
413
414
415
416
417
May 13, 2011
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265-8755
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
418
419
420
421
William Wagner
TIC
Email: wamwagner@comcast.net
422
423
424
425
426
427
428
429
430
Additional contributors:
Michael Sweet – Apple
Lee Farrell – Canon
Glen Petrie - Epson
Ira McDonald – High North
Jerry Thrasher - Lexmark
Nancy Chen – OkiData
Copyright © 2011, Printer Working Group. All rights reserved.
Page 19 of 19