PROJ Title of Specification (Acronym)ftp.pwg.org/.../wd/wd-commonusecases10-20110731.docx · Web...

May 17, 2023Working Draft

The Printer Working Group

Common Use Cases

Status: Interim

Abstract: This Best Practices document provides a repository of well-defined use cases, design requirements, internationalization considerations, security considerations, and references for use for PWG standards-track documents.

This is a PWG Best Practices document. For a definition of a "PWG Best Practices Document", see: ftp://ftp.pwg.org/pub/pwg/general/pwg-process30.pdf

This document is available electronically at:

ftp://ftp.pwg.org/pub/pwg/general/wd/wd-commonusecases10-20110731.docx and ftp://ftp.pwg.org/pub/pwg/general/wd/wd-commonusecases10-20110731.pdf

Copyright © 2011 The Printer Working Group. All rights reserved.

12345678910

11

12

13

14

151617

1819

20

2122

Working Draft – PWG Common Use Cases May 17, 2023

Copyright © 2011 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 IEEE-ISTO and the Printer Working Group, a program of the IEEE-ISTO.

Title: PWG Common Use Cases

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

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

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

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

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

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

of 18 Copyright © 2011 The Printer Working Group. All rights reserved.

12

23

24252627282930

31

32333435

363738

3940414243

44454647484950

51525354

55565758

34


About the IEEE-ISTO

The IEEE-ISTO is a not-for-profit corporation offering industry groups an innovative and flexible operational forum and support services. The IEEE-ISTO provides a forum not only to develop standards, but also to facilitate activities that support the implementation and acceptance of standards in the marketplace. The organization is affiliated with the IEEE (http://www.ieee.org/) and the IEEE Standards Association (http://standards.ieee.org/).

For additional information regarding the IEEE-ISTO and its industry programs visit:

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

About the IEEE-ISTO PWG

The Printer Working Group (or PWG) is a Program of the IEEE Industry Standards and Technology Organization (ISTO) with member organizations including printer manufacturers, print server developers, operating system providers, network operating systems providers, network connectivity vendors, and print management application developers. The group is chartered to make printers and the applications and operating systems supporting them work together better. All references to the PWG in this document implicitly mean “The Printer Working Group, a Program of the IEEE ISTO.” In order to meet this objective, the PWG will document the results of their work as open standards that define print related protocols, interfaces, procedures and conventions. Printer manufacturers and vendors of printer related software will benefit from the interoperability provided by voluntary conformance to these standards.

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

For additional information regarding the Printer Working Group visit:

http://www.pwg.org

Contact information:

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


56

59

606162636465

66

67

68

6970717273747576777879

808182

83

84

85

868788899091

78

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

http://standards.ieee.org/)

http://www.ieee.org/


Table of Contents1. Introduction......................................................................................................................62. Terminology.....................................................................................................................6

2.1 Precondition Terminology..........................................................................................73. Use Cases.......................................................................................................................8

3.1 Select Device.............................................................................................................83.1.1 Select the Last Used Device...............................................................................83.1.2 Select Device Using Name or Address...............................................................83.1.3 Select Device Using URI.....................................................................................8 Select Device Using a Directory Service.....................................................................93.1.4............................................................................................................................. 93.1.5 Select Device Using a Cloud Service..................................................................93.1.6 Select Device Using a Discovery Protocol..........................................................93.1.7 Select Device Using Proximity.............................................................................93.1.8 Select Device Using Identifying Technology.......................................................93.1.9 Select Device Using Criteria..............................................................................10

3.2 Print..........................................................................................................................103.2.1 Print a Document...............................................................................................103.2.2 Print a Document by Reference........................................................................103.2.3 Print a Photo......................................................................................................113.2.4 Print a Secure Form..........................................................................................113.2.5 Print with Special Formatting.............................................................................123.2.6 Print and Select at Device.................................................................................123.2.7 Print to a Service...............................................................................................123.2.8 Print to a Recipient............................................................................................133.2.9 Print with a Proof Copy......................................................................................13

3.3 Scan.........................................................................................................................133.3.1 Scan a Document..............................................................................................133.3.2 Scan a Photo.....................................................................................................133.3.3 Scan with Presets..............................................................................................133.3.4 Scan Using a Cloud Service..............................................................................133.3.5 Scan and Select at Device................................................................................13

3.4 Facsimile..................................................................................................................143.4.1 Fax a Document................................................................................................143.4.2 Fax a Photo.......................................................................................................143.4.3 Fax with Presets................................................................................................143.4.4 Fax Using a Cloud Service................................................................................143.4.5 Fax and Select at Device...................................................................................14

3.5 Transforms...............................................................................................................143.6 Status Monitoring.....................................................................................................143.7 Device Control.........................................................................................................14

3.7.1 Release Job for Printing....................................................................................143.7.2 Reprint Job........................................................................................................14

3.8 Exceptions...............................................................................................................14


910

9293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135

1112


3.8.1 Select Device Canceled....................................................................................143.8.2 Not Authorized...................................................................................................143.8.3 Not Authenticated..............................................................................................143.8.4 Document Format Not Supported......................................................................143.8.5 Document Processing Failed.............................................................................143.8.6 Out of Paper......................................................................................................153.8.7 Low Toner.........................................................................................................153.8.8 Billing Error........................................................................................................15

3.9 Access Control.........................................................................................................153.9.1 Authenticated Guest Access.............................................................................15

3.10 Auditing..................................................................................................................163.11 Accounting.............................................................................................................16

Collect Detailed Job/Document Metrics.....................................................................163.11.1......................................................................................................................... 163.11.2 Query Device for Accounting Information Before Print....................................16

3.12 Regulatory Compliance..........................................................................................163.12.1 Copyright.........................................................................................................163.12.2 Privacy.............................................................................................................163.12.3 Identification....................................................................................................16

4. Design Requirements....................................................................................................165. Security Considerations.................................................................................................166. Internationalization Considerations................................................................................167. References....................................................................................................................17

7.1 Normative References.............................................................................................177.2 Informative References............................................................................................17

8. Authors' Addresses........................................................................................................179. Change History..............................................................................................................18

9.1 July 31, 2011............................................................................................................189.2 May 24, 2011...........................................................................................................18


1314136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166

1516


1. IntroductionThis document provides a common repository of casual use cases, design requirements, internationalization considerations, security considerations, and references for PWG standards-track documents. It has been developed to consolidate the overlapping use cases and design requirements of the Cloud Imaging, Imaging Device Security, Internet Printing Protocol, and Multifunction Device working groups so that a coherent view of Devices and Services can be adopted and appropriate (and necessary) standards written to address the common use cases

This use cases are organized into subsections for setup, administration and configuration, selection, printing, scanning, facsimile, transforms, status monitoring, exception handling, access control, auditing, and accounting use cases. Each subsection contains a named use case with a casual use case definition.

2. TerminologyThe following terms are used throughout this document:

Billing; Remuneration for processing of a job

BOOTP; Network address auto-configuration using the Boot Protocol [RFC????].

Cellular Network; A restricted-access voice and data network connected using a combination of radio frequency signal "cells" with optical or electrical cabling.

Cellular Network Settings; .....

Client

Cloud

Cloud Service

Device; IPP definition; also see Logical Device and Physical Device

DHCP; Network address auto-configuration using the Dynamic Host Configuration Protocol [RFC2131].

Directory Service; A service providing query and enumeration of information using names or other identifiers.

DNS; Network address and name resolution using the Domain Name Service [RFC1034????].


1718

167

168169170171172173174

175176177178

179

180

181

182

183184

185

186

187

188

189

190191

192193

194195

1920


DNS-SD; Service discovery using DNS-Based Service Discovery [DNS-SD].

Imaging Device

Logical Device

Physical Device

Device

Scanner

Service; Software providing access to physical, logical, or virtual resources.

User; A person or automata using a Service.

User Interface; A human interface to the Device provided through Client software, embedded web server, or the Device control panel, console, or touch screen.

Wired Network; A traditional computer network connected using electrical or optical cabling.

Wired Network Settings; The IPv4 and/or IPv6 network addresses, network masks, and default router addresses combined with a host name. May also include domain, DNS server addresses, Directory Service name, address, and authentication information, Cloud Service name, address, and authentication information, and Syslog host addresses.

Wireless Network; A traditional computer network connected using antennae and radio frequency signals.

Wireless Network Settings; The IPv4 and/or IPv6 network addresses, network masks, and default router addresses combined with a network name and host name. May also include a network password, domain, DNS server addresses, Directory Service name, address, and authentication information, Cloud Service name, address, and authentication information, and Syslog host addresses.

ZeroConf; Automatic network address assignment using Dynamic Configuration of IPv4 Link-Local Addresses [RFC3927] and IPv6 Link Local addressing.

2.1 Precondition Terminology

The following terms are used as preconditions for the scenarios and use cases in this document:

Connected Network; An IP network to which a Client or Device has access.


2122196

197

198

199

200

201

202

203

204205

206207

208209210211

212213

214215216217218

219220

221

222223

224

2324


Directory Device; A printer selected by query or enumeration of a directory such as LDAP.

Discovered Device; A printer selected through an ad-hoc discovery protocol such as DNS-SD, SNMP broadcast, and UPNP.

Service Device; A printer selected by query or enumeration of a service such as an enterprise print server or Cloud Imaging service.

Static Device; A printer selected using its IP address, URI, other other static identifier.

Visible/Visibility; Refers to the ability of one device to communicate directly with another, for example a Client is able to connect to a Device, query for supported attributes, submit print jobs, and so forth.

3. Use Cases

3.1 Select Device

Device selection is part of most service use cases - the User selects a Device, implicitly or explicitly, and the remainder of the use case applies to the selected device. A Device can be a Logical Device such as a Scan Service or a Physical Device such as a Printer.

Note: For all of the following use cases, the Device must be Visible to the Client to be selected, either directly or through an intermediate Service.

3.1.1 Select the Last Used Device

The Client User Interface displays the last used Device as a selection. The User then confirms the selection of the last used Device.

The last used Device may be automatically selected by the Client User Interface and may be affected by the current network topology or geo-location, for example the last used Device may be tracked on a per-network or per-location basis.

3.1.2 Select Device Using Name or Address

The Client User Interface asks the User for a name or address for the Device. The User then provides a Device name or address through the Client User Interface. Finally, the Client User Interface queries the Device for valid service URIs.

3.1.3 Select Device Using URI

The Client User Interface asks the User for a service URI for the Device. The User then provides a URI through the Client User Interface or cancels selection.


2526225

226227

228229

230

231232233

234

235

236237238

239240

241

242243

244245246

247

248249250

251

252253

2728

Michael Sweet, 07/11/11,

Change requests to asks for in all use cases


3.1.4 Select Device Using a Directory Service

One or more Devices are listed in a Directory Service and that Directory Service is Visible to the Client.

The Client obtains a list of Devices on behalf of the User from the Directory Service and validates that each Device supports one or more Client-supported service protocols. The Client User Interface then asks the User to select one of the supported Devices. Finally, the User selects a Device.

3.1.5 Select Device Using a Cloud Service

The Client and one or more Devices are registered with a Cloud Service, and that Cloud Service is Visible to both the Client and Devices. The Client and Devices may be registered with multiple Cloud Services and maintain multiple identities.

The Client obtains a list of Devices on behalf of the User from the Cloud Service(s). The Client User Interface then asks the User to select one or the Devices. Finally, the User selects a Device.

3.1.6 Select Device Using a Discovery Protocol

The Device is Visible to the Client and supports a common Discovery Protocol.

The Client initiates discovery and maintains a list of Visible Devices during selection. The Client User Interface asks the user to select one of the Visible Devices, updating those Devices as they come and go. Finally, the User selects a Device and the Client discontinues discovery.

3.1.7 Select Device Using Proximity

Both the Client and Device have access to location information to allow for proximity detection. The location information may be implied by the network topology.

The Client initiates a proximity detection of nearby Devices using Services and/or discovery protocols, hiding duplicate Devices that are reported by multiple Service and/or discovery procotols. The Client User Interface asks the User to select one of the nearby Devices. Finally, the User selects a nearby Device.

3.1.8 Select Device Using Identifying Technology

The Device and Client support a common identifying technology such as near-field communications, QRCodes, or bar codes.

The User asks the Client User Interface to identify the Device. The Client initiates identification to obtain a service URI and descriptive information. The Client User Interface


2930254

255256

257258259260

261

262263264

265266267

268

269

270271272273

274

275276

277278279280

281

282283

284285

3132

Michael Sweet, 07/11/11,

Reword this to make it clear that we filter the list of printers based on the supported service protocols


then asks the User to confirm the selection of the identified Device. Finally, the User confirms the selection.

3.1.9 Select Device Using Criteria

A User selects a Device using criteria such as protocol, limits such as the number of pages allowed, job ticket capabilities such as duplex printing support, printer description elements such as location, speed, and color support, and job size. The criteria may be provided by a combination of User input, policy, and/or software heuristic.

The User asks the Client User Interface to select using criteria. The Client obtains a list of Devices for the User that meet the given Job Ticket (media, duplex capabilities, pages/job size, etc.) and Device Description (location, speed, color support, etc.) criteria provided by the Client software, policy, and/or User and validates that each Device supports one or more Client-supported service protocols. The Client User Interface then asks the User to select one of the supported Devices. Finally, the User selects a Device.

3.2 Print

Printing is a common (perhaps the most common) use case for Printer Devices. Each of the use cases in this section begin by selecting a Device which refers to any of the Select Device use cases in section 3.1.

Note: For all of the following use cases, the Device must be Visible to the Client to be selected, either directly or through an intermediate Service. Also, the document to be printed must be Visible to the Device and in a format suitable for the Device or converted by the Client (or Service) into a suitable format.

3.2.1 Print a Document

User has a phone connected to the Wi-Fi network in her business and has a document to print prior to a meeting that is stored on her phone.

User initiates a print from the phone using the Client User Interface and selects a Device. The Client queries the Device for capabilities and status information. The Client User Interface shows the status information, as needed, and asks the user to select Job Ticket settings for the print job. The User selects Job Ticket settings and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and local document. The Device validates the Job Ticket and document data and then prints the document. Finally, the User collects the printout from the Device.


3334286287

288

289290291292

293294295296297298

299

300301302

303304305306

307

308309

310311312313314315316

3536


3.2.2 Print a Document by Reference

User has a phone connected to the Wi-Fi network in her business and is viewing a document on a server that she would like to print.

User initiates a print from the phone using the Client User Interface and selects a Device. The Client queries the Device for capabilities and status information. The Client User Interface shows the status information, as needed, and asks the user to select Job Ticket settings for the print job. The User selects Job Ticket settings and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and remote document URI. The Device validates the Job Ticket and document URI and then prints the document. Finally, the User collects the printout from the Device.

3.2.3 Print a Photo

User is viewing a photo and would like to print the photo on the largest borderless photographic media available on her Device.

User initiates a print from the phone using the Client User Interface and selects a Device. The Client queries the Device for capabilities and status information. The Client User Interface shows the status information, as needed, automatically selects the largest borderless photographic media available and the highest print quality, and asks the user to select additional Job Ticket settings for the print job. The User selects Job Ticket settings and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and local photo. The Device validates the Job Ticket and document data and then prints the photo. Finally, the User collects the printout from the Device.

3.2.4 Print a Secure Form

The treasurer of a small training company that is holding a meeting and seminar at a resort needs to print out 20 checks for training personnel. He uses an accounting program to enter the hours worked, bonuses, reimbursable expenses, and so forth and prints the checks on a printer provided by the resort using check blanks he brought to the meeting.

The User loads check blanks into the Device and configured the loaded media as necessary at the Device. User initiates a print from his accounting program and selects checks to be printed using the Client User Interface. The Client User Interface displays a preview of the printed checks and the User confirms that checks amounts, payees and signature are correct. User selects a Device for printing and the Client queries the Device for capabilities and status information. The Client User Interface shows the status information, as needed, automatically selects the check blank media, and asks the user to select additional Job Ticket settings for the print job. The User selects Job Ticket settings and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and document data containing the checks, correctly oriented for the check of 18 Copyright © 2011 The Printer Working Group. All rights reserved.

3738317

318319

320321322323324325326

327

328329

330331332333334335336337

338

339340341342343

344345346347348349350351352353

3940


blank media. The User waits for the checks to be printed and removes any excess media from the Device.

3.2.5 Print with Special Formatting

At a seminar located at a country resort, a factotum and general gofer has been asked to provide 80 sets of ten keywords/phrases, clearly printed on 2-inch by 1-inch paper slips for use in a get acquainted exercise. Costs are to be minimized. Gofer has a laptop with a word processer program. Resort has a Wi-Fi network available to users and a networked MFD at the business center. Attendant at business center will charge for any printed sheets removed from premises.

User initiates a print from his word processor using the Client User Interface and selects a Device. The Client queries the Device for capabilities and status information. The Client User Interface shows the status information, as needed, and asks the user to select additional Job Ticket settings for the print job. The User selects Job Ticket settings and confirms the print action. The Client produces document data using the media information (size and margins) in the Job Ticket so that 2-inch by 1-inch slips are spread evenly over each page and sends a print job request to the Device with the Job Ticket and document. The Device validates the Job Ticket and document data and then prints the document. Finally, the User collects the printout from the Device.

3.2.6 Print and Select at Device

One or more Devices are integrated with a Service to provide "follow me" printing. The User may release a job at a given Device by providing a PIN and/or other unique identification/authorization information such as a username and password or ID card.

User initiates a print using the Client User Interface and selects a Service. The Client queries the Service for capabilities and status information. The Client User Interface shows the status information, as needed, and asks the user to select Job Ticket settings for the print job and possibly a PIN. The User selects Job Ticket settings and PIN and confirms the print action. The Client sends a print job request to the Service with the Job Ticket and local document. The Service validates the Job Ticket and document data and then holds the document until released by the User at the Device. Finally, the User collects the printout from the Device.

3.2.7 Print to a Service

John is flying to New York for a presentation and doesn't want to carry the presentations. John arrives in New York and goes online from his mobile phone. He selects a local print provider after reviewing the provider web pages and submits his document for printing. He specifies that he needs 10 color copies, printed duplex and stapled on the left side. He also specifies the covers to be 80lb. stock, and the internal pages to be 24lb. stock. John


4142346347

348

349350351352353354

355356357358359360361362363

364

365366367

368369370371372373374375

376

377378379380381

4344


arrives at the provider and picks up his presentations, paying with his corporate credit card.

3.2.8 Print to a Recipient

The recipient may release a job at a given Device by providing a PIN and/or other unique identification/authorization information such as a username and password or ID card.

User initiates a print using the Client User Interface and selects a Device. The Client queries the Device for capabilities and status information. The Client User Interface shows the status information, as needed, and asks the user to select Job Ticket settings for the print job and the recipient of the job. The User selects Job Ticket settings and a recipient and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and local document. The Device validates the Job Ticket and document data and then holds the document until released by the recipient. Finally, the recipient collects the printout from the Device.

3.2.9 Print with a Proof Copy

User initiates a print using the Client User Interface and selects a Device. The Client queries the Device for capabilities and status information. The Client User Interface shows the status information, as needed, and asks the user to select Job Ticket settings for the print job. The User selects Job Ticket settings, requests a proof print, and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and local document. The Device validates the Job Ticket and document data and then prints a proof copy of the document. The User collects the proof printout from the Device and verifies correct output. The User then initiates a full print of the document from the Client User Interface or Device to produce the final printout.

3.3 Scan

3.3.1 Scan a Document

3.3.2 Scan a Photo

3.3.3 Scan with Presets

3.3.4 Scan Using a Cloud Service

3.3.5 Scan and Select at Device

"Follow me" scanning use case.


4546382383

384

385386

387388389390391392393394

395

396397398399400401402403404

405

406

407

408

409

410

411

4748


3.4 Facsimile

3.4.1 Fax a Document

3.4.2 Fax a Photo

3.4.3 Fax with Presets

3.4.4 Fax Using a Cloud Service

3.4.5 Fax and Select at Device

"Follow me" fax use case.

3.5 Transforms

TBD

3.6 Status Monitoring

TBD

3.7 Device Control

For general Operator use cases.

3.7.1 Release Job for Printing

3.7.2 Reprint Job

3.8 Exceptions

3.8.1 Select Device Canceled

3.8.2 Not Authorized

3.8.3 Not Authenticated

3.8.4 Document Format Not Supported

and any other job creation errors due to the document or Job Ticket.


4950

412

413

414

415

416

417

418

419

420

421

422

423

424

425

426

427

428

429

430

431

432

5152


3.8.5 Document Processing Failed

and any other job processing errors that are reported to the User or Operator.

3.8.6 Out of Paper

and any other "something has happened that requires your attention" errors at the Device. Reported to User and/or Operator depending on use case.

3.8.7 Low Toner

and any other advisory messages from the Device. Reported to User and/or Operator depending on use case.

3.8.8 Billing Error

Credit card denied and other failure to pay for services?

3.9 Access Control

3.9.1 Authenticated Guest Access

John and Steve both have cloud repositories accounts. Steve has at least one cloud print account and has some administrative privileges

John, a high-school student, rushes out of the house on his way to his friend’s (Steve) house and, then, to school. In less than 5 minutes he arrives at Steve house. Steve waves his history report at John to show him it is done and printed. John reaches in his backpack to realize he has forgotten his printed copy. John tells Steve he has a copy of his report on his cloud and could he print it at his house. Steve agrees. Steve ask John for his cloud user name and adds John as a ‘friend’ to his cloud aware printer. John promptly logs into his cloud account and finds his history report. Invoking a print request, John sees that Steve’s printer has been added to this printer list. Selecting Steve’s printer, John prints his report and they are both off to school.

Optional: Steve’s system administrator (dad) does not want the ‘friend’s’ list for the printer to be to long; so, Steve removes John from the ‘friend’s’ list and John see the printer disappear from this printer list.

Steve logs in to his cloud account and adds John to the ‘friend’s’ list for his home printer. The cloud system updates the ‘friend’ access list and adds Steve’s home printer to John’s printer list.

John logs in to his cloud account and selects his document and request a print. John selects Steve’s home printer from his printer list. The cloud system presents a print dialog of 18 Copyright © 2011 The Printer Working Group. All rights reserved.

5354433

434

435

436437

438

439440

441

442

443

444

445446

447448449450451452453454455

456457458

459460461

462463

5556


using the capabilities for Steve’s home printer. John sets his print options and presses the print button. The print dialog generates a Print-Job-Ticket and records the URI for Steve’s document in the Print-Job-Ticket. The print dialog passes the print request to the cloud repository print client manager. The cloud repository print client manager checks the status of Steve’s printer. The cloud repository print client manager sends the print job to Steve’s printer. The cloud repository print client manager receive a print-complete. The cloud repository print client manager updates John’s print status. The cloud repository print client manager removes the job from its queue.

3.10 Auditing

3.10.1 TBD

3.11 Accounting

3.11.1 Collect Detailed Job/Document Metrics

including pages/sheets, color usage, media, finishing, job receipt, date/time info, owner

3.11.2 Query Device for Accounting Information Before Print

including charge info URI and summary/info text

3.12 Regulatory Compliance

3.12.1 Copyright

3.12.2 Privacy

3.12.3 Identification

4. Design RequirementsThe Device must have a reusable, persistent, and unique identifier such as a URI.

5. Security ConsiderationsDevices should provide access control through authentication or other accepted methods.

6. Internationalization Considerations


5758464465466467468469470471

472

473

474

475

476

477

478

479

480

481

482

483

484

485

486

487

488

5960


7. References

7.1 Normative References

[REFERENCE] F. Last author list or standards body, "Title of referenced document", Document Number, Month YYYY, URL (if any)

7.2 Informative References

[REFERENCE] F. Last author list or standards body, "Title of referenced document", Document Number, Month YYYY, URL (if any)

8. Authors' AddressesMichael SweetApple Inc.10431 N. De Anza Blvd.MS 38-$LPTCupertino, CA 95014 USA

Justin HutchinsMicrosoft Corporation

Glen PetrieEpson

Craig ShifmanKonica Minolta

Larry UpthegroveEnd-User

William WagnerTechnical Information Consulting


6162

489

490

491492

493

494495

496

497498499500501502503504505506507508509510511512513514515516

6364


9. Change History

9.1 July 31, 2011

1. Major revision to casual use case format, break out selection and exceptions from use cases, and drop scenarios.

2. Incorporated new use cases from Larry Upthegrove.

9.2 May 24, 2011

Initial revision.


6566

517

518

519520521

522

523

6768

PROJ Title of Specification (Acronym)ftp.pwg.org/.../wd/wd-commonusecases10-20110731.docx · Web...

Documents

Transcript of PROJ Title of Specification (Acronym)ftp.pwg.org/.../wd/wd-commonusecases10-20110731.docx · Web...