The Printer Working Group - ftp.pwg.org · 30/07/2011 · 49 manufacturers, print server...

July 30, 2011 Working Draft

The Printer Working Group

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

Michael Sweet� 3/23/11 8:32 AMDeleted: February 23, 2011

PWG Raster Format

Status: Interim

Abstract: This standard defines a simple raster format for printing, scanning, and facsimile. The format includes support for a set of standard and device color spaces and bit depths, and defines PWG Semantic Model elements and IPP attributes that enable a client to generate or request a supported raster stream.

This document is a PWG Working Draft. For a definition of a "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/ipp/wd/wd-ippraster10-20110730.docx ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippraster10-20110730.pdf

Michael Sweet� 7/30/11 8:16 PMStyle Definition: Numbered List: Font:12pt

Michael Sweet� 7/26/11 11:37 AMDeleted: Draft

Michael Sweet� 7/26/11 11:53 AMDeleted: small

Michael Sweet� 7/26/11 11:52 AMDeleted: Printer description

Michael Sweet� 7/26/11 11:52 AMDeleted: for IPP

Michael Sweet� 7/30/11 8:19 PMDeleted: C

Michael Sweet� 5/28/11 1:48 PMDeleted: 0223

Michael Sweet� 7/22/11 8:38 PMDeleted: .pdf/

Working Draft – PWG Raster Format July 30, 2011

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

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

This document may be copied and furnished to others, and derivative works that comment 2 on, or otherwise explain it or assist in its implementation may be prepared, copied, 3 published and distributed, in whole or in part, without restriction of any kind, provided that 4 the above copyright notice, this paragraph and the title of the Document as referenced 5 below are included on all such copies and derivative works. However, this document itself 6 may not be modified in any way, such as by removing the copyright notice or references 7 to the IEEE-ISTO and the Printer Working Group, a program of the IEEE-ISTO. 8

Title: PWG Raster Format 9

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

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

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

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

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

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

Michael Sweet� 5/28/11 1:49 PMDeleted: .36



About the IEEE-ISTO 37

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

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

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

About the IEEE-ISTO PWG 46

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

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

For additional information regarding the Printer Working Group visit: 61

http://www.pwg.org 62

Contact information: 63

The Printer Working Group 64 c/o The IEEE Industry Standards and Technology Organization 65 445 Hoes Lane 66 Piscataway, NJ 08854 67 USA 68

UnknownField Code ChangedUnknownField Code ChangedUnknownField Code Changed



About the Internet Printing Protocol Work Group 69

The Internet Printing Protocol (IPP) working group has developed a modern, full-featured 70 network printing protocol, which is now the industry standard. IPP allows a print client to 71 query a printer for its supported capabilities, features, and parameters to allow the 72 selection of an appropriate printer for each print job. IPP also provides job information 73 prior to, during, and at the end of job processing. 74

For additional information regarding IPP visit: 75

http://www.pwg.org/ipp/ 76

Implementers of this specification are encouraged to join the IPP mailing list in order to 77 participate in any discussions of the specification. Suggested additions, changes, or 78 clarification to this specification, should be sent to the IPP mailing list for consideration. 79

80



Table of Contents 81 82

1. Introduction ...................................................................................................................... 7 83 2. Terminology ..................................................................................................................... 8 84

2.1 Conformance Terminology ........................................................................................ 8 85 2.2 Other Terminology ..................................................................................................... 8 86 2.3 Representation of Octets in Examples ...................................................................... 8 87

3. Requirements .................................................................................................................. 9 88 3.1 Rationale for the PWG Raster Format ....................................................................... 9 89 3.2 Use Cases ................................................................................................................. 9 90

3.2.1 Mobile Printing to Low Cost InkJet ...................................................................... 9 91 3.2.2 Desktop Printing to Low Cost Workgroup Printer ................................................ 9 92

3.3 Out of Scope .............................................................................................................. 9 93 3.4 Design Requirements .............................................................................................. 10 94

4. PWG Raster Format ...................................................................................................... 10 95 4.1 File Organization ...................................................................................................... 10 96 4.2 Synchronization Word .............................................................................................. 11 97 4.3 Page Header ............................................................................................................ 11 98

4.3.1 Data Types ........................................................................................................ 13 99 4.3.2 Bitmap Fields .................................................................................................... 16 100 4.3.3 Job Ticket Fields ............................................................................................... 18 101

4.4 Page Bitmap ............................................................................................................ 20 102 4.4.1 Sample Gray Bitmap ......................................................................................... 20 103 4.4.2 Sample sRGB Bitmap ....................................................................................... 21 104 4.4.3 Sample DeviceCMYK Bitmap ........................................................................... 22 105

5. Semantic Model Elements ............................................................................................. 23 106 5.1 PwgRasterDocumentBackside ................................................................................ 24 107 5.2 PwgRasterDocumentResolutionSupported ............................................................. 24 108 5.3 PwgRasterDocumentTypeSupported ...................................................................... 25 109

6. Conformance Requirements ......................................................................................... 26 110 6.1 PWG Raster Consumer Requirements .................................................................... 26 111 6.2 PWG Raster Producer Requirements ...................................................................... 26 112 6.3 IPP Printer Conformance Requirements ................................................................. 26 113 6.4 IPP Client Conformance Requirements ................................................................... 27 114

7. Internationalization Considerations ............................................................................... 27 115 8. Security Considerations ................................................................................................ 27 116 9. IANA Considerations ..................................................................................................... 27 117

9.1 MIME Media Type Registration ............................................................................... 27 118 9.2 Attribute Registrations ............................................................................................. 29 119 9.3 Attribute Value Registrations ................................................................................... 29 120

10. IPP Printer Description Attributes ................................................................................ 30 121 10.1 pwg-raster-document-backside (type2 keyword) ................................................... 31 122 10.2 pwg-raster-document-resolution-supported (1setOf resolution) ............................ 31 123 10.3 pwg-raster-document-type-supported (1setOf type2 keyword) ............................. 31 124

11. References .................................................................................................................. 31 125 11.1 Normative References ........................................................................................... 31 126



11.2 Informative References .......................................................................................... 32 127 12. Author's Addresses ..................................................................................................... 32 128 13. Change History ............................................................................................................ 33 129

13.1 July 30, 2011 ......................................................................................................... 33 130 13.2 March 27, 2011 ...................................................................................................... 33 131 13.3 March 26, 2011 ...................................................................................................... 33 132 13.4 February 23, 2011 ................................................................................................. 33 133 13.5 January 26, 2011 ................................................................................................... 34 134 13.6 January 24, 2011 ................................................................................................... 34 135

136 137 138

List of Figures 139 Figure 1 - PWG Raster File Organization .......................................................................... 11 140 Figure 3 - Sample Color Bitmap ........................................................................................ 21 141 Figure 5 - PwgRasterBackside and Sides ......................................................................... 24 142

143 144

List of Tables 145 Table 1 - PWG Raster Page Header ................................................................................. 11 146 Table 2 - ColorOrderEnum Values .................................................................................... 13 147 Table 3 - ColorSpaceEnum Values ................................................................................... 13 148 Table 4 - EdgeEnum Values ............................................................................................. 14 149 Table 5 - MediaPositionEnum Values ............................................................................... 14 150 Table 6 - WhenEnum Values ............................................................................................ 16 151 Table 7 - Supported Duplex and Tumble Values .............................................................. 18 152 Table 8 - New Service Description Elements .................................................................... 23 153 Table 9 - PwgRasterTypesSupported Keyword Values .................................................... 25 154 Table 10 - IPP Printer Description Attributes ..................................................................... 30 155 156 157



1. Introduction 158

Historically, printer manufacturers have used a variety of proprietary or device-specific 159 variants of industry standard page description languages (PDLs) to support printing, 160 leading to the proliferation of so-called "printer driver" software for every supported 161 operating system and/or platform. 162

Two high-level PDLs, Adobe PostScript [POSTSCRIPT] and PDF [ISO32000], are 163 sufficiently generic to be used for basic printing, however they require significant 164 resources in the printer and can be difficult to generate and stream from some 165 environments. Existing standard bitmap image formats have issues as well: 166

• JPEG: Lossy compression, no multi-page support 167 • JPEG 2000: Lossy compression, no multi-page support, resource-intensive 168 • MNG: Resource-intensive and not widely implemented or supported 169 • PNG: No multi-page support, resource-intensive 170 • TIFF: Can be resource-intensive, hard to stream, multiple format variants 171

CUPS Raster [CUPSRASTER] is a simple bitmap container to support printing on all 172 types of printers. It provides the following features: 173

• Support for multiple pages 174 • Support for standard color spaces backed by existing ICC color profiles 175 • Adaptable byte order for encoding and decoding 176 • A single, lossless compression algorithm that is space, memory, and processor 177

efficient 178 • Per-page Job Ticket information based on the Adobe PostScript page device 179

dictionary 180 • An easily streamable encoding 181

CUPS Raster has been used over existing print data transports such as the Internet 182 Printing Protocol (IPP) since 1999. CUPS Raster can also be further reduced in size using 183 HTTP or IPP compression algorithms such as Compress and Flate when supported by the 184 client and printer. 185

This standard defines a proper subset of CUPS Raster. The subset includes support for a 186 set of standard and device Color Spaces and bit depths and also defines PWG Semantic 187 Model elements and IPP attributes that enable a client to generate or request a supported 188 raster stream for a printer. 189

Michael Sweet� 7/26/11 11:29 AMDeleted: or 190 Michael Sweet� 7/30/11 8:16 PMDeleted: P191 Michael Sweet� 7/26/11 11:30 AMDeleted: small 192 Michael Sweet� 7/30/11 9:17 PMDeleted: ,193 Michael Sweet� 7/26/11 11:30 AMDeleted: Printer description 194 Michael Sweet� 7/26/11 11:30 AMDeleted: for IPP195 Michael Sweet� 7/30/11 8:16 PMDeleted: Client 196 Michael Sweet� 7/30/11 8:17 PMDeleted: Printer197



2. Terminology 198

2.1 Conformance Terminology 199

Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, 200 MAY, and OPTIONAL, have special meaning relating to conformance as defined in RFC 201 2119 [RFC2119]. 202

2.2 Other Terminology 203

Color Component; an individual element or channel for a Color Space or Pixel, for 204 example “Red”, “Green” and “Blue” are Color Components of the “RGB” Color Space. 205

Color Order; the order of Color Components within the Page Bitmap. These Color Orders 206 are called “Chunked”, “Banded”, and “Planar” in the CUPS Raster Format specification 207 [CUPSRASTER]. 208

Color Space; the interpretation of Pixel color in a page bitmap, for example “RGB”, 209 “Grayscale”, “CMYK”, and so forth. 210

CUPS Raster; the image file format defined by [CUPSRASTER]. 211

PackBits; a simple run-length encoding algorithm for data compression. Each sequence is 212 encoded as a series of repeated or non-repeated Pixels. 213

Page Bitmap; a rectangular grid of Pixels. 214

Page Header; the binary Job Ticket dictionary of Adobe PostScript and raster key values 215 for a Page Bitmap. 216

Pixel; a set of Color Components representing a single grid point in a Page Bitmap. 217

2.3 Representation of Octets in Examples 218

Throughout this specification, octets are represented using pairs of hexadecimal digits 219 prefixed by the string "0x". Multiple contiguous octets may also be combined into a short 220 form similar to that defined in RFC 2119 [RFC2119] with the "0x" prefix replaced by a 221 period ("."), for example 0x12 and 0x34 may be combined as 0x12.34. The short form is 222 used to group related octets for clarity. 223



3. Requirements 224

3.1 Rationale for the PWG Raster Format 225

IPP Everywhere [IPPEVE] and IPP Scan [IPPSCAN] both require a standard raster format 226 for printing and scanning of multiple-page documents without printer-specific driver 227 software. CUPS Raster provides this but supports many more Color Spaces, Color 228 Orders, bit depths, and byte orders than are needed for a modern printer. Moreover, the 229 Adobe PostScript page device dictionary does not map cleanly to IPP or the PWG 230 Semantic Model, leading to additional complexities that would make interoperability 231 difficult. 232

By defining a proper subset of CUPS Raster, we both enable support for a new class of 233 printer without the use of printer- and platform-specific driver software in the client and 234 greatly reduce the number of variables for interoperability. And by defining which page 235 header fields are mapped to/from PWG Job Ticket elements we also enable a low-cost 236 solution for per-page overrides embedded within a document. 237

3.2 Use Cases 238

3.2.1 Mobile Printing to Low Cost InkJet 239

Jane has a smart phone with Wi-Fi capability and a built-in camera. She prints photos 240 from her phone to a low-cost Wi-Fi inkjet printer. The printer has limited memory and 241 processor resources that support basic raster printing on a variety of media types and 242 sizes. 243

During printing, her client software queries the printer for supported media, resolutions, 244 and raster modes, produces a printer-ready raster representation of the photo for the 245 selected media, and streams it to the printer for output. 246

3.2.2 Desktop Printing to Low Cost Workgroup Printer 247

John has a desktop PC he uses to write whitepapers and other business documents. He 248 prints these documents to a low-cost Ethernet workgroup laser printer with three paper 249 trays and a duplexing accessory. The printer has enough memory to hold a partial image 250 of one side of a sheet. 251

During printing, his client software queries the printer for supported media, resolutions, 252 raster modes, and duplex support, produces printer-ready raster pages of the documents, 253 and streams them to the printer for output. 254

3.3 Out of Scope 255

The following items are considered out of scope for this specification: 256

Michael Sweet� 2/2/11 4:07 PMComment [1]: Add references to IPP Everywhere, IPP Scan

Michael Sweet� 7/30/11 8:17 PMDeleted: Printer257

Michael Sweet� 7/26/11 11:36 AMDeleted: IPP P258

Michael Sweet� 5/28/11 1:51 PMDeleted: Use Models259



1. Definition of a new file format; we want to minimize the proliferation of file formats 260 and reuse existing formats whenever possible. 261

2. Extensions to the CUPS Raster format; we want to minimize the proliferation of 262 file formats and reuse the existing CUPS Raster format by defining a simple, 263 backwards-compatible subset of the format for basic raster printing, scanning, 264 and facsimile. 265

3.4 Design Requirements 266

The use cases in section 3.2 identify several design requirements: 267

3. Since both the client and printer may have limited memory, a raster format for 268 printing, scanning, or facsimile must be streamable to minimize buffering. 269

4. Because the printer may have limited memory, the client must be able to discover 270 the supported raster resolutions and how to provide duplex page images – no 271 flip, X flip, Y flip, or rotation by 180 degrees (both X and Y flip) - so that the printer 272 does not need to perform expensive transformations of the client-supplied 273 images. 274

5. Because the client and printer may not have sophisticated color management 275 capabilities, standard color spaces should be used to foster improved color 276 fidelity. 277

In addition, the following items should be considered when selecting the raster format: 278

1. Some form of data compression should be used to limit network bandwidth 279 usage. Text printing favors lossless compression algorithms to preserve edge 280 detail and resource limitations require simpler compression algorithms. 281

2. A bi-level imaging mode may be useful when printing text and line art. 282 3. The order of multi-octet values should be predefined to limit the complexity of 283

implementations. 284 4. While a printer may have limited space for color tables, it should still be possible 285

to support a managed color workflow when both the client and printer are 286 capable. This generally requires some sort of device color space support. 287

4. PWG Raster Format 288

The CUPS Raster specification [CUPSRASTER] defines three format variants for the 289 MIME media type “application/vnd.cups-raster”. The following subsections define the 290 subset of the CUPS Raster v2 format used for the MIME media type “image/pwg-raster”. 291

4.1 File Organization 292

Figure 1 - PWG Raster File Organization shows the general organization of every PWG 293 Raster file. Each file begins with a 32-bit synchronization word followed by zero or more 294 pages. Each page consists of a header followed by the bitmap image for the page. The 295

Michael Sweet� 7/30/11 8:47 PMFormatted: Numbered List

Michael Sweet� 7/30/11 8:48 PMDeleted: and mapping of PostScript page 296 device dictionary key/value pairs to IPP or 297 the PWG Semantic model are out of scope 298 for this specification because299

Michael Sweet� 7/30/11 8:48 PMDeleted: the goal is300

Michael Sweet� 7/30/11 8:49 PMDeleted: define 301

Michael Sweet� 7/30/11 8:35 PMFormatted: IEEEStds Paragraph




Michael Sweet� 7/30/11 8:35 PMDeleted: <#>Since both the client and IPP 303 Printer may have limited memory, a raster 304 format for printing must be streamable to 305 minimize buffering.306 ... [1]

Michael Sweet� 7/30/11 8:43 PMDeleted: t308



bitmap image is compressed using a PackBits-like algorithm to reduce file size without 309 significant overhead. Integer values larger than 8-bits are specified in network byte order. 310

4.2 Synchronization Word 311

The synchronization word is a 32-bit unsigned integer with the value 0x52.61.53.32 312 (“RaS2”). 313

314

Figure 1 - PWG Raster File Organization 315

4.3 Page Header 316

Table 1 - PWG Raster Page Header describes the 1796-octet page header that appears 317 at the beginning of each page. Most of the fields in the header are derived from the Adobe 318 PostScript page device dictionary [POSTSCRIPT]. All reserved fields MUST be 0. 319

Table 1 - PWG Raster Page Header 320

Bytes Type Name 0-63 Reserved Reserved 64-127 CString MediaColor 128-191 CString MediaType 192-255 CString OutputType 256-267 Reserved Reserved 268-271 WhenEnum CutMedia 272-275 Boolean Duplex 276-283 UnsignedInteger x 2 HWResolution

Synchronization Word

Page 1 (Header + Bitmap)

Page 2 (Header + Bitmap)

...

Page N (Header + Bitmap)

Michael Sweet� 7/22/11 8:48 PMDeleted: The bulk of the page header is 321 intentionally unused.322 Michael Sweet� 7/22/11 8:54 PMDeleted: 275323 Michael Sweet� 7/22/11 8:54 PMDeleted: Reserved324 Michael Sweet� 7/22/11 8:54 PMDeleted: Reserved325 Michael Sweet� 7/22/11 8:57 PMDeleted: 79326 Michael Sweet� 7/22/11 8:56 PMDeleted: HorizontalResolution327



Bytes Type Name 284-299 UnsignedInteger x 4 ImagingBoundingBox 300-303 Boolean InsertSheet 304-307 WhenEnum Jog 308-311 EdgeEnum LeadingEdge 312-319 UnsignedInteger x 2 Margins 320-323 Boolean ManualFeed 324-327 MediaPositionEnum MediaPosition 328-331 UnsignedInteger MediaWeight 332-339 Reserved Reserved 340-343 UnsignedInteger NumCopies 344-347 OrientationEnum Orientation 348-351 Reserved Reserved 352-359 UnsignedInteger x 2 PageSize 360-367 Reserved Reserved 368-371 Boolean Tumble 372-375 UnsignedInteger Width 376-379 UnsignedInteger Height 380-383 Reserved Reserved 384-387 UnsignedInteger BitsPerColor 388-391 UnsignedInteger BitsPerPixel 392-395 UnsignedInteger BytesPerLine 396-399 ColorOrderEnum ColorOrder 400-403 ColorSpaceEnum ColorSpace 404-419 Reserved Reserved 420-423 UnsignedInteger NumColors 424-451 Reserved Reserved 452-455 UnsignedInteger TotalPageCount 456-459 Integer CrossFeedTransform 460-463 Integer FeedTransform 464-467 UnsignedInteger ImageBoxLeft 468-471 UnsignedInteger ImageBoxTop 472-475 UnsignedInteger ImageBoxRight 476-479 UnsignedInteger ImageBoxBottom 480-483 SrgbColor SgrayPrimary 484-507 Reserved Reserved 508-511 UnsignedInteger VendorIdentifier 512-515 UnsignedInteger VendorLength 516-1603 VendorData VendorData 1604-1667 Reserved Reserved 1668-1731 CString RenderingIntent 1732-1795 CString PageSizeName

328 329

Michael Sweet� 7/22/11 8:58 PMDeleted: 280-283330 Michael Sweet� 7/22/11 8:58 PMDeleted: VerticalResolution331 Michael Sweet� 7/22/11 8:59 PMDeleted: 284332 Michael Sweet� 7/22/11 8:59 PMDeleted: Reserved333 Michael Sweet� 7/22/11 8:59 PMDeleted: Reserved334

Michael Sweet� 7/26/11 2:55 PMDeleted: Integer335 Michael Sweet� 7/26/11 2:55 PMDeleted: Integer336 Michael Sweet� 5/28/11 2:16 PMDeleted: 1795337



4.3.1 Data Types 338

The page header utilizes several data types described in the following subsections. 339

4.3.1.1 Boolean 340

Boolean fields are 32-bit unsigned (one's complement) integers with a value of 0 (false) or 341 1 (true). 342

4.3.1.2 CString 343

CString fields are 64-octets in length containing up to 63 US ASCII characters followed by 344 an ASCII NUL (0). 345

4.3.1.3 ColorOrderEnum 346

ColorOrderEnum fields are 32-bit unsigned (one's complement) integers containing one 347 the values listed in Table 2. 348

Table 2 - ColorOrderEnum Values 349

Value Keyword Description 0 Chunky Chunky pixels, e.g. CMYK CMYK

CMYK ... 350

4.3.1.4 ColorSpaceEnum 351

ColorSpaceEnum fields are 32-bit unsigned (one's complement) integers containing one 352 of the values listed in Table 3. 353

Table 3 - ColorSpaceEnum Values 354

Value Keyword Description 3 Black Device black 6 Cmyk Device CMYK (cyan magenta

yellow black) 18 Sgray sRGB grayscale 19 Srgb sRGB color 20 AdobeRgb Adobe RGB color 48 Device1 Device color, 1 colorant 49 Device2 Device color, 2 colorants 50 Device3 Device color, 3 colorants 51 Device4 Device color, 4 colorants 52 Device5 Device color, 5 colorants 53 Device6 Device color, 6 colorants 54 Device7 Device color, 7 colorants 55 Device8 Device color, 8 colorants 56 Device9 Device color, 9 colorants 57 Device10 Device color, 10 colorants



Value Keyword Description 58 Device11 Device color, 11 colorants 59 Device12 Device color, 12 colorants 60 Device13 Device color, 13 colorants 61 Device14 Device color, 14 colorants 62 Device15 Device color, 15 colorants

4.3.1.5 EdgeEnum 355

EdgeEnum fields are 32-bit unsigned (one's complement) integers containing one of the 356 values listed in Table 4. 357

Table 4 - EdgeEnum Values 358

Value Keyword Description 0 ShortEdgeFirst The short edge of the media is first. 1 LongEdgeFirst The long edge of the media is first.

4.3.1.6 Integer 359

Integer fields are 32-bit signed (two's complement) integers. 360

4.3.1.7 MediaPositionEnum 361

MediaPositionEnum fields are 32-bit unsigned (one's complement) integers containing 362 one of the values listed in Table 5. 363

Table 5 - MediaPositionEnum Values 364

Value Keyword Description 0 Auto Default or automatically selected source. 1 Main The primary or main source. 2 Alternate The secondary or alternate source. 3 LargeCapacity The large capacity source. 4 Manual The manual feed source. 5 Disc The CD/DVD/Bluray disc source. 6 Photo The photo media source. 7 Hagaki The Hagaki media source. 8 MainRoll The primary or main roll. 9 AlternateRoll The secondary or alternate roll. 10 Top The topmost source. 11 Middle The middle source. 12 Bottom The bottommost source. 13 Side The side source. 14 Left The leftmost source. 15 Right The rightmost source. 16 Center The center source. 17 Rear The rear source. 20 Tray1 Tray 1. 21 Tray2 Tray 2.



Value Keyword Description 22 Tray3 Tray 3. 23 Tray4 Tray 4. 24 Tray5 Tray 5. 25 Tray6 Tray 6. 26 Tray7 Tray 7. 27 Tray8 Tray 8. 28 Tray9 Tray 9. 29 Tray10 Tray 10. 30 Tray11 Tray 11. 31 Tray12 Tray 12. 32 Tray13 Tray 13. 33 Tray14 Tray 14. 34 Tray15 Tray 15. 35 Tray16 Tray 16. 36 Tray17 Tray 17. 37 Tray18 Tray 18. 38 Tray19 Tray 19. 39 Tray20 Tray 20. 40 Roll1 Roll 1. 41 Roll2 Roll 2. 42 Roll3 Roll 3. 43 Roll4 Roll 4. 44 Roll5 Roll 5. 45 Roll6 Roll 6. 46 Roll7 Roll 7. 47 Roll8 Roll 8. 48 Roll9 Roll 9. 49 Roll10 Roll 10.

4.3.1.8 Reserved 365

Reserved fields are a sequence of octets initialized to the value 0. 366

4.3.1.9 SrgbColor 367

SrgbColor fields are 32-bit integers containing a 24-bit sRGB color value. The upper 8 bits 368 are 0, followed by 8 bits of red, 8 bits of green, and 8 bits of blue. 369

4.3.1.10 UnsignedInteger 370

UnsignedInteger fields are 32-bit unsigned (one's complement) integers. 371

4.3.1.11 VendorData 372

VendorData fields are a sequence of octets containing vendor-specific data. 373 374



4.3.1.12 WhenEnum 375

WhenEnum fields are 32-bit unsigned (one's complement) integers containing one of the 376 values listed in . 377

Table 6 - WhenEnum Values 378

Value Keyword Description 0 Never Never apply feature. 1 AfterDocument Apply feature after current document/file. 2 AfterJob Apply feature after current job. 3 AfterSet Apply feature after current set/copy. 4 AfterPage Apply feature after current page.

4.3.2 Bitmap Fields 379

4.3.2.1 HWResolution 380

The HWResolution field consists of two integers representing the cross-feed and feed 381 resolutions of the page bitmap in pixels (dots) per inch and MUST be initialized to either 382 one of the supported values reported by the "PwgRasterResolutionSupported" element or 383 a compatible lower resolution. A compatible lower resolution is an integral divisor of a 384 "PwgRasterResolutionSupported" value, for example 360x360dpi for a printer that 385 supports 720x720dpi or 300x300dpi for a printer that supports 2400x1200dpi. 386

4.3.2.2 LeadingEdge 387

The LeadingEdge field MUST be initialized to 0 if the "FeedDirection" value for the given 388 media or input tray is 'ShortEdgeFirst' and 1 if the value is 'LongEdgeFirst'. 389

4.3.2.3 Width and Height 390

The Width and Height fields MUST be initialized to the full width and height of the current 391 page in addressable units as defined by the HWResolution field. Thus, each page bitmap 392 provides a "full bleed" page image. 393

4.3.2.4 BitsPerColor, BitsPerPixel, ColorSpace, and NumColors 394

The BitsPerColor, BitsPerPixel, ColorSpace, and NumColors fields MUST be initialized to 395 values corresponding to a “PwgRasterTypesSupported” value, as defined in Table 9 - 396 PwgRasterTypesSupported Keyword Values. 397

4.3.2.5 BytesPerLine 398

The BytesPerLine field MUST be initialized to the number of octets for a single 399 uncompressed line in the page bitmap, as described by the following formula: 400

BytesPerLine = TRUNCATE((BitsPerPixel * Width + 7) / 8) 401

Michael Sweet� 7/22/11 9:11 PMDeleted: HorizontalResolution 402 Michael Sweet� 7/22/11 9:11 PMDeleted: and VerticalResolution403 Michael Sweet� 7/22/11 9:11 PMDeleted: HorizontalResolution and Vertical404 Michael Sweet� 7/22/11 9:11 PMDeleted: s405 Michael Sweet� 7/28/11 3:08 PMDeleted: pwg406 Michael Sweet� 7/28/11 3:08 PMDeleted: -r407 Michael Sweet� 7/28/11 3:08 PMDeleted: -r408 Michael Sweet� 7/28/11 3:08 PMDeleted: -s409 Michael Sweet� 7/28/11 3:08 PMDeleted: attribute 410 Michael Sweet� 7/28/11 3:08 PMDeleted: pwg411 Michael Sweet� 7/28/11 3:08 PMDeleted: -r412 Michael Sweet� 7/28/11 3:08 PMDeleted: -r413 Michael Sweet� 7/28/11 3:09 PMDeleted: -s414 Michael Sweet� 7/29/11 2:40 PMDeleted: HorizontalResolution 415 Michael Sweet� 7/29/11 2:40 PMDeleted: and VerticalResolution 416 Michael Sweet� 7/29/11 2:40 PMDeleted: s417 Michael Sweet� 7/28/11 3:24 PMDeleted: p418 Michael Sweet� 7/28/11 3:23 PMDeleted: -r419 Michael Sweet� 7/28/11 3:23 PMDeleted: -420 Michael Sweet� 7/28/11 3:23 PMDeleted: resolution421 Michael Sweet� 7/28/11 3:23 PMDeleted: -s422



4.3.2.6 TotalPageCount 423

The TotalPageCount field specifies the number of pages in the entire file or 0 if the total 424 number of pages is not known when the file is produced. 425

4.3.2.7 CrossFeedTransform and FeedTransform 426

The CrossFeedTransform and FeedTransform fields specify the orientation of the page 427 bitmap in the CrossFeed and Feed directions, respectively. Values of 1 indicate normal 428 orientation, typically left-to-right for the CrossFeed and top-to-bottom for the Feed 429 directions, while values of -1 indicate reserved orientation, typically right-to-left and 430 bottom-to-top respectively. 431

These fields are used to convey the coordinate system used for the backside image for 432 duplex printing or scanning - page bitmaps MUST always be produced using the printer's 433 "native" coordinate system to minimize resource requirements on the printer. 434

4.3.2.8 ImageBoxLeft, ImageBoxTop, ImageBoxRight, and ImageBoxBottom 435

The ImageBoxLeft, ImageBoxTop, ImageBoxRight, and ImageBoxBottom fields specify 436 the area, in pixels, that contains non-empty content and corresponds directly to the 437 ImageBox element in the PWG Semantic Model. Pixels are measured from the beginning 438 of the page bitmap, so the coordinates reflect the orientation specified by the 439 XFeedTransform and FeedTransform fields. 440

All fields will have the value 0 if the ImageBox is unknown. 441

4.3.2.9 SgrayPrimary 442

The SgrayPrimary field specifies the "white" color to use for grayscale page bitmaps as an 443 sRGB color value. When 0, the sRGB color value 0xFFFFFF (white) is used instead. 444

4.3.2.10 VendorIdentifier, VendorLength, and VendorData 445

The VendorIdentifier, VendorLength, and VendorData fields allow a vendor to embed 446 arbitrary data in a page header. They should be initialized to the value 0 when not used. 447

The VendorIdentifier field contains to the USB vendor identification number for the vendor 448 providing the data. 449

The VendorLength field specifies the number of octets that are used in the VendorData 450 field. 451

The VendorData field contains the vendor octets. 452



4.3.3 Job Ticket Fields 453

4.3.3.1 CutMedia 454

This field indicates whether output should be trimmed (cut) and corresponds to the 'Trim' 455 values in the "JobFinishings" element. 456

4.3.3.2 Duplex and Tumble 457

These fields specify the duplex printing mode for the current page. Table 7 lists the 458 supported combinations. 459

Table 7 - Supported Duplex and Tumble Values 460

Duplex Tumble Sides FALSE (0) FALSE (0) OneSided TRUE (1) FALSE (0) TwoSidedLongEdge TRUE (1) TRUE (1) TwoSidedShortEdge

4.3.3.3 InsertSheet 461

This field specifies whether to insert a single blank sheet prior to the current page, using 462 the media defined by the current page header and corresponds to the Semantic Model 463 element of the same name. 464

4.3.3.4 Jog 465

This field specifies whether to jog (offset) pages in the output bin and corresponds to the 466 'JogOffset' values in the "JobFinishings" element. 467

4.3.3.5 Margins 468

This field specifies the left and bottom media margins in points and corresponds to the 469 "MediaLeftMargin" and "MediaBottomMargin" sub-elements of the "MediaCol" element. 470

4.3.3.6 MediaColor 471

This field specifies the media color name corresponding to the "MediaColor" sub-element 472 of the "MediaCol" element. When the empty string, the default media color is used. 473

4.3.3.7 MediaPosition 474

This field specifies the media input tray or source corresponding to the "MediaSource" 475 sub-element of the "MediaCol" element. Table 5 provides a list of MediaPosition values 476 with their corresponding "MediaSource" values. When 0, the default media type is used. 477



4.3.3.8 MediaType 478

This field specifies the media type name corresponding to the "MediaType" sub-element 479 of the "MediaCol" element. When the empty string, the default media type is used. 480

4.3.3.9 MediaWeight 481

This field specifies the media weight in grams per square meter and corresponds to the 482 "MediaWeight" sub-element of the "MediaCol" element. When 0, the default media weight 483 is used. 484

4.3.3.10 NumCopies 485

This field specifies the number of copies of the current page to produce and corresponds 486 to the "Copies" element. When 0, the default number of copies is used. 487

4.3.3.11 Orientation 488

This field specifies the orientation of the page and corresponds to the 489 "OrientationRequested" element. 490

4.3.3.12 OutputType 491

This field specifies the relative print quality for the page and corresponds to the 492 "PrintQuality" element. Valid values are the empty string for the default print quality, 'Draft' 493 for draft quality, 'Normal' for normal quality, and 'High' for high quality. 494

4.3.3.13 PageSize and PageSizeName 495

The PageSize field specifies the width and length of the current page in points. When the 496 width and length are 0 the default media size is used, typically as defined by the Width, 497 Height, and HWResolution fields for the page bitmap. The PageSize field corresponds to 498 the "MediaSize" sub-element of the "MediaCol" element. 499

The PageSizeName field specifies a named size using a PWG Standardized Media Name 500 [PWG5101.1]. When the empty string, the default media size is used. The PageSizeName 501 field corresponds to the "MediaSizeName" sub-element of the "MediaCol" element. 502

4.3.3.14 RenderingIntent 503

The RenderingIntent field specifies the colorimetric rendering intent for the page and 504 corresponds to the "PrintRenderingIntent" element. When the empty string, the default 505 rendering intent is used. 506



4.4 Page Bitmap 507

The page bitmap is compressed using a PackBits-like algorithm. Pixel color values are 508 packed into an integral number of octets. 8 pixel color values are packed into a single 509 octet for compression when BitsPerPixel is 1. 510

Each line of raster data begins with a repetition count from 1 to 256 that is encoded using 511 a single octet containing "count - 1". 512

After the repetition count, whole color values for that line are run-length encoded using a 513 PackBits-like run-length encoding algorithm: 1 to 128 repeated colors are encoded using 514 an initial octet containing "count - 1" followed by the color value octet(s) while 2 to 128 515 non-repeating colors are encoded using an initial octet containing "257 - count" followed 516 by the color value octet(s). 517

4.4.1 Sample Gray Bitmap 518

The 23x8 1-bit sGray image shown in Figure 2 would be encoded as the following 21 519 octets. 520

0x00 0xFE.8F.78.F7 521 0x00 0xFE.76.77.67 522 0x03 0x02.77 523 0x00 0xFE.8E.38.E3 524 0x00 0x02.FF 525

526

Figure 2 - Sample Gray Bitmap 527

The unused trailing bits (1 bit in this example) can have any value, and in this example we 528 use a value of 1 to improve the compression slightly. 529

The first line (0x00) is a sequence of three octets (0xFE.8F.78.F7). 530

The second line (0x00) is another sequence of three octets (0xFE.76.77.67). 531

The third through sixth lines (0x03) contain a sequence of three repeated octets 532 (0x02.77). 533

Michael Sweet� 7/29/11 4:41 PMDeleted: <#>534

Michael Sweet� 7/30/11 8:51 PMFormatted: Example

Michael Sweet� 7/30/11 8:51 PMFormatted: Caption



The seventh line (0x00) is a sequence of three octets (0xFE.8E.38.E3). 535

The last line (0x00) is a sequence of three repeated octets (0x02.FF). 536

4.4.2 Sample sRGB Bitmap 537

The 8x8 24-bit sRGB image shown in would be encoded as the following 87 octets: 538

0x00 0x00.FF.FF.FF 0x02.FF.FF.00 0x03.FF.FF.FF 539 0x00 0xFE.FF.FF.00.00.00.FF.FF.FF.00 0x02.FF.FF.FF 0xFF.00.FF.00.FF.FF.FF 540 0x00 0x01.FF.FF.00 0x02.FF.FF.FF 0x02.00.FF.00 541 0x00 0x02.FF.FF.00 0x02.FF.FF.FF 0xFF.00.FF.00.FF.FF.FF 542 0x00 0x00.FF.FF.FF 0x02.FF.FF.00 0x03.FF.FF.FF 543 0x00 0x07.FF.FF.FF 544 0x01 0x07.FF.00.00 545

546

547

Figure 3 - Sample Color Bitmap 548

The first line (0x00) contains 1 white pixel (0x00.FF.FF.FF), 3 yellow pixels 549 (0x02.FF.FF.00), and 4 white pixels (0x03.FF.FF.FF). 550

The second line (0x00) contains a sequence of yellow + blue + yellow pixels 551 (0xFE.FF.FF.00.00.00.FF.FF.FF.00), 3 white pixels (0x02.FF.FF.FF), and a sequence of 552 green + white pixels (0xFF.00.FF.00.FF.FF.FF). 553

The third line (0x00) contains 2 yellow pixels (0x01.FF.FF.00), 3 white pixels 554 (0x02.FF.FF.FF), and 3 green pixels (0x02.00.FF.00). 555

The fourth line (0x00) contains 3 yellow pixels (0x02.FF.FF.00), 3 white pixels 556 (0x02.FF.FF.FF), and a sequence of green + white pixels (0xFF.00.FF.00.FF.FF.FF). 557

The fifth line (0x00) contains 1 white pixel (0x00.FF.FF.FF), 3 yellow pixels 558 (0x02.FF.FF.00), and 4 white pixels (0x03.FF.FF.FF). 559

The sixth line (0x00) contains 8 white pixels (0x07.FF.FF.FF). 560

The seventh and eighth lines (0x01) contain 8 red pixels (0x07.FF.00.00). 561

Michael Sweet� 7/30/11 8:52 PMDeleted: Figure - Sample Page Image 624

Michael Sweet� 7/29/11 4:49 PMDeleted: For example, t625

UnknownField Code Changed

Michael Sweet� 7/29/11 5:03 PMDeleted: Figure 2 - Sample Page Image …ould 626 ... [2]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00 %x…x00.FF.FF.FF 627 ... [3]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00 628 ... [4]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00 %x…x01.FF.FF.00 629 ... [5]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00 %x…x02.FF.FF.00 630 ... [6]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00 %x…x00.FF.FF.FF 631 ... [7]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00 %x632 ... [8]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x01 %x633 ... [9]

Michael Sweet� 7/30/11 8:53 PMFormatted: Caption

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00) contains 1 white pixel 634 ... [10]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00) contains a sequence of 635 ... [11]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00) contains 2 yellow pixels 636 ... [12]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00) contains 3 yellow pixels 637 ... [13]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00) contains 1 white pixel 638 ... [14]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x00) contains 8 white pixels (%x639 ... [15]

Michael Sweet� 7/30/11 2:52 PMDeleted: %x…x01) contain 8 red pixels (%x640 ... [16]



4.4.3 Sample DeviceCMYK Bitmap 641

The 8x8 24-bit DeviceCMYK image shown in would be encoded as the following 108 642 octets: 643

0x00 0x00.00.00.00.00 0x02.00.00.FF.00 0x03.00.00.00.00 644 0x00 0xFE.00.00.FF.00.FF.FF.00.00.00.00.FF.00 0x02.00.00.00.00 645

0xFF.FF.00.FF.00.00.00.00.00 646 0x00 0x01.00.00.FF.00 0x02.00.00.00.00 0x02.FF.00.FF.00 647 0x00 0x02.00.00.FF.00 0x02.00.00.00.00 0xFF.FF.00.FF.00.00.00.00.00 648 0x00 0x00.00.00.00.00 0x02.00.00.FF.00 0x03.00.00.00.00 649 0x00 0x07.00.00.00.00 650 0x01 0x07.00.FF.FF.00 651

The first line (0x00) contains 1 white pixel (0x00.00.00.00.00), 3 yellow pixels 652 (0x02.00.00.FF.00), and 4 white pixels (0x03.00.00.00). 653

The second line (0x00) contains a sequence of yellow + blue + yellow pixels 654 (0xFE.00.00.FF.00.FF.FF.00.00.00.00.FF.00), 3 white pixels (0x02.00.00.00.00), and a 655 sequence of green + white pixels (0xFF.FF.00.FF.00.00.00.00.00). 656

The third line (0x00) contains 2 yellow pixels (0x01.00.00.FF.00), 3 white pixels 657 (0x02.00.00.00.00), and 3 green pixels (0x02.FF.00.FF.00). 658

The fourth line (0x00) contains 3 yellow pixels (0x02.00.00.FF.00), 3 white pixels 659 (0x02.00.00.00.00), and a sequence of green + white pixels 660 (0xFF.FF.00.FF.00.00.00.00.00). 661

The fifth line (0x00) contains 1 white pixel (0x00.00.00.00.00), 3 yellow pixels 662 (0x02.00.00.FF.00), and 4 white pixels (0x03.00.00.00.00). 663

The sixth line (0x00) contains 8 white pixels (0x07.00.00.00.00). 664

The seventh and eighth lines (0x01) contain 8 red pixels (0x07.00.FF.FF.00). 665 666

UnknownField Code Changed



5. Semantic Model Elements 667

This specification defines three new <service>ServiceDescription elements. 668

[INSERT SCHEMA DIAGRAM HERE] 669

Figure 4 - New <service>ServiceDescription Elements 670

671

Table 8 - New Service Description Elements 672

Element DataType Description or Keyword PwgRasterDocumentBackside keyword see 5.1;

PwgRasterBacksideWKV PwgRasterDocumentResolutionSupported complex see 5.2 Resolution complex the supported sequence of

resolutions in CrossFeed and Feed direction for PWG Raster files

CrossFeedDir int allowed values for resolutions, in dots per inch, in CrossFeed direction [RFC2911 para 4.1.15]

FeedDir int allowed values for resolutions, in dots per inch, in Feed direction [RFC2911 para 4.1.15]

PwgRasterDocumentTypeSupported list of keywords

see 5.3; PwgRasterTypesWKV

673




5.1 PwgRasterDocumentBackside 675

This REQUIRED element specifies the bitmap coordinate system for the backside of 676 duplex sheets. The following keyword values are defined: 677

'Normal' - the backside has the origin at the top-left corner of the bitmap, 678 'ManualTumble' - the backside has the origin at the top-left corner of the bitmap for 679 'TwoSidedLongEdge' and the bottom-right corner (rotated 180º) of the bitmap for 680 'TwoSidedShortEdge', 681 'Rotated' - the backside image has the origin at the bottom-right corner (rotated 682 180º) of the bitmap for 'TwoSidedLongEdge' and the top-left corner of the bitmap 683 for 'TwoSidedShortEdge', or 684 'Flipped' - the backside image has the origin at the bottom-left corner (X flipped) of 685 the bitmap for 'TwoSidedLongEdge' and the top-right corner (Y flipped) for 686 'TwoSidedShortEdge'. 687

Figure 5 visually shows the effect of each value on the bitmap image. 688

689

Figure 5 - PwgRasterBackside and Sides 690

5.2 PwgRasterDocumentResolutionSupported 691

This REQUIRED element lists the supported page bitmap resolutions in dots per inch. 692 Printers MUST be capable of accepting or producing "image/pwg-raster" streams for the 693 highest reported resolution on the largest supported media. Printers MUST support at 694 least one resolution less than or equal to 360 dots per inch and SHOULD support at least 695 one resolution greater than or equal to 600 dots per inch. 696



5.3 PwgRasterDocumentTypeSupported 697

This REQUIRED element lists the supported page bitmap color configurations. Table 9 698 lists the standard keywords and the corresponding page header field values. 699

Table 9 - PwgRasterTypesSupported Keyword Values 700

Keyword BitsPerColor BitsPerPixel ColorSpace NumColors Black_1 1 1 3 1 Sgray_1 1 1 18 1 Black_8 8 8 3 1 Cmyk_8 8 32 6 4 Sgray_8 8 8 18 1 Srgb_8 8 24 19 3 AdobeRgb_8 8 24 20 3 Device1_8 8 8 48 1 Device2_8 8 16 49 2 Device3_8 8 24 50 3 Device4_8 8 32 51 4 Device5_8 8 40 52 5 Device6_8 8 48 53 6 Device7_8 8 56 54 7 Device8_8 8 64 55 8 Device9_8 8 72 56 9 Device10_8 8 80 57 10 Device11_8 8 88 58 11 Device12_8 8 96 59 12 Device13_8 8 104 60 13 Device14_8 8 112 61 14 Device15_8 8 120 62 15 Black_16 16 16 3 1 Cmyk_16 16 64 6 4 Sgray_16 16 16 18 1 Srgb_16 16 48 19 3 AdobeRgb_16 16 48 20 3 Device1_16 16 16 48 1 Device2_16 16 32 49 2 Device3_16 16 48 50 3 Device4_16 16 64 51 4 Device5_16 16 80 52 5 Device6_16 16 96 53 6 Device7_16 16 112 54 7 Device8_16 16 128 55 8 Device9_16 16 144 56 9 Device10_16 16 160 57 10 Device11_16 16 176 58 11 Device12_16 16 192 59 12 Device13_16 16 208 60 13 Device14_16 16 224 61 14 Device15_16 16 240 62 15

Michael Sweet� 7/30/11 4:35 PMDeleted: <#>Printer Description Attributes701 ... [17]

Michael Sweet� 7/30/11 4:18 PMDeleted: black703 Michael Sweet� 7/30/11 4:18 PMDeleted: -704 Michael Sweet� 7/30/11 4:18 PMDeleted: sgray705 Michael Sweet� 7/30/11 4:18 PMDeleted: -706 Michael Sweet� 7/30/11 4:18 PMDeleted: black707 Michael Sweet� 7/30/11 4:18 PMDeleted: -708 Michael Sweet� 7/30/11 4:18 PMDeleted: cmyk709 Michael Sweet� 7/30/11 4:19 PMDeleted: -710 Michael Sweet� 7/30/11 4:18 PMDeleted: sgray711 Michael Sweet� 7/30/11 4:19 PMDeleted: -712 Michael Sweet� 7/30/11 4:18 PMDeleted: srgb713 Michael Sweet� 7/30/11 4:19 PMDeleted: -714 Michael Sweet� 7/30/11 4:20 PMDeleted: black715 Michael Sweet� 7/30/11 4:20 PMDeleted: -716 Michael Sweet� 7/30/11 4:21 PMDeleted: cmyk717 Michael Sweet� 7/30/11 4:20 PMDeleted: -718 Michael Sweet� 7/30/11 4:21 PMDeleted: sgray719 Michael Sweet� 7/30/11 4:21 PMDeleted: -720 Michael Sweet� 7/30/11 4:21 PMDeleted: srgb721 Michael Sweet� 7/30/11 4:21 PMDeleted: -722 Michael Sweet� 7/30/11 4:21 PMDeleted: a723 Michael Sweet� 7/30/11 4:21 PMDeleted: -r724 Michael Sweet� 7/30/11 4:21 PMDeleted: -725



6. Conformance Requirements 726

6.1 PWG Raster Consumer Requirements 727

To claim conformance to this specification, a PWG Raster consumer MUST: 728

(a) support the "image/pwg-raster" MIME media type as defined in section 4 of this 729 specification and 730 (b) conform to the Security Considerations defined in section 8 of this specification. 731

6.2 PWG Raster Producer Requirements 732

To claim conformance to this specification, a PWG Raster producer MUST: 733

(a) generate document data conforming to the "image/pwg-raster" MIME media 734 type as defined in section 4 of this specification and 735 (b) conform to the Security Considerations defined in section 8 of this specification. 736

6.3 IPP Printer Conformance Requirements 737

To claim conformance to this specification, an IPP Printer implementation MUST: 738

(a) support the PWG Raster Consumer requirements as defined in section 6.1 of 739 this specification, 740 (b) support all IPP attributes defined in section 10 of this specification, 741 (c) support PWG Raster streams at the highest reported resolution reported by the 742 “pwg-raster-resolution-supported” attribute and largest media size reported by the 743 “media-supported” attribute, 744 (d) support PWG Raster streams with all resolutions compatible with the values 745 reported by the “pwg-raster-resolution-supported” attribute as defined in section 5.2 746 of this specification, and 747 (e) support the "feed-orientation" Job Template attribute defined in section 7.1 of 748 PWG 5100.11 [PWG5100.11]. 749

If an IPP Printer supports scanning, it MUST ALSO: 750

(a) support the PWG Raster Producer requirements as defined in section 6.2 of this 751 specification. 752

An IPP Printer SHOULD: 753

(a) support the IPP “compression” attribute with the values “compress”, “deflate”, 754 and/or “gzip” to further reduce the size of PWG Raster documents. 755

Michael Sweet� 7/30/11 8:55 PMFormatted: List Paragraph

Michael Sweet� 7/30/11 8:59 PMDeleted: "image/pwg-raster" MIME media 756 type 757



Michael Sweet� 7/30/11 8:58 PMDeleted: 4.3.1760

Michael Sweet� 7/30/11 9:01 PMDeleted: and761 ... [18]

Michael Sweet� 7/30/11 9:00 PMFormatted: List Paragraph



6.4 IPP Client Conformance Requirements 763

To claim conformance to this specification, an IPP Client MUST: 764

(a) support the PWG Raster Producer requirements as defined in section 6.2 of this 765 specification, 766 (b) explicitly identify the supported values of all IPP attributes defined in section 10 767 of this specification, 768 (c) produce PWG Raster streams at a compatible orientation, resolution, and size 769 as reported by the "feed-orientation", “pwg-raster-resolution-supported”, and 770 “media-supported” attributes and as defined in section 5.2 of this specification, and 771 (d) produce PWG Raster streams using Color Space and bit depth values as 772 defined in section 5.3 of this specification. 773

If an IPP Client supports scanning, it MUST ALSO: 774

(a) support the PWG Raster Consumer requirements as defined in section 6.1 of 775 this specification. 776

An IPP Client SHOULD: 777

(a) support the IPP “compression” attribute with the values “compress”, “deflate”, 778 and/or “gzip” to further reduce the size of PWG Raster documents. 779

7. Internationalization Considerations 780

Because PWG Raster streams contain no localizable text, there are no internationalization 781 considerations for the PWG Raster format. 782

8. Security Considerations 783

The security considerations for IPP are described in Section 8 of RFC 2911 [RFC2911]. 784 Consumers of PWG Raster streams MUST range check all page header and bitmap 785 values to protect against integer and buffer overflows. 786

9. IANA Considerations 787

9.1 MIME Media Type Registration 788

Name : Michael Sweet 789

E-mail : [email protected] 790

MIME media type name : Image 791

Michael Sweet� 7/30/11 9:04 PMDeleted: generate document data 792 conforming to the "image/pwg-raster" MIME 793 media type as defined in section 4 of this 794 specification795


Michael Sweet� 7/30/11 9:02 PMDeleted: generate 797

Michael Sweet� 7/30/11 9:01 PMDeleted: 4.3.1798

Michael Sweet� 7/30/11 9:04 PMDeleted: and799 ... [19]

Michael Sweet� 7/30/11 8:54 PMDeleted: 801 ... [20]



MIME subtype name : Standards Tree – pwg-raster 803

Required parameters : NONE 804

Optional parameters : NONE 805

Encoding considerations : 806

8-bit (raw) binary data. 807

Security considerations : 808

Raster data can be very large, which could fill a filesystem and cause a denial of 809 service or system failure. Raster data contains no executables or macros. 810 Authentication and access control are normally handled by the Internet Printing 811 Protocol and Hyper-Text Transport Protocol. 812

Interoperability considerations : 813

NONE 814

Published specification : 815

ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippraster10-YYYYMMDD-5102.RAS.pdf 816 [Editor's Note: Update this URL prior to publication] 817

Applications which use this media : 818

CUPS 819 IPP Everywhere 820 IPP Scan 821

Additional information : 822

1. Magic number(s) : 823

2. File extension(s) : 824

3. Macintosh file type code : 825

Person to contact for further information : 826

1. Name : Michael Sweet 827

2. E-mail : [email protected] 828

Intended usage : Common 829

Used for printing "raw" image data in formats acceptable to printers. 830



Author/Change controller : 831

The Printer Working Group 832 c/o The IEEE Industry Standards and Technology Organization 833 445 Hoes Lane 834 Piscataway, NJ 08854 835 USA 836

9.2 Attribute Registrations 837

The attributes defined in this document will be published by IANA according to the 838 procedures in RFC 2911 [RFC2911] section 6.2 in the following file: 839

http://www.iana.org/assignments/ipp-registrations 840

The registry entries will contain the following information: 841

Printer Description attributes: Reference 842 ----------------------- --------- 843 pwg-raster-document-backside (type2 keyword) [PWG5102.RAS] 844 pwg-raster-document-resolution-supported (1setOf resolution)845

[PWG5102.RAS] 846 pwg-raster-document-type-supported (1setOf type2 keyword) 847 [PWG5102.RAS] 848

9.3 Attribute Value Registrations 849

The keyword attribute values defined in this document will be published by IANA 850 according to the procedures in RFC 2911 [RFC2911] section 6.1 in the following file: 851

http://www.iana.org/assignments/ipp-registrations 852

The registry entries will contain the following information: 853

Attributes (attribute syntax) 854 Keyword Attribute Value Reference 855 ----------------------- --------- 856 pwg-raster-document-backside (type2 keyword) [PWG5102.RAS] 857 normal [PWG5102.RAS] 858 manual-tumble [PWG5102.RAS] 859 rotated [PWG5102.RAS] 860 flipped [PWG5102.RAS] 861 862 pwg-raster-document-type-supported (1setOf type2 keyword) 863 [PWG5102.RAS] 864 adobe-rgb_16 [PWG5102.RAS] 865 adobe-rgb_8 [PWG5102.RAS] 866 black_1 [PWG5102.RAS] 867 black_16 [PWG5102.RAS] 868 black_8 [PWG5102.RAS] 869



cmyk_16 [PWG5102.RAS] 870 cmyk_8 [PWG5102.RAS] 871 device1_16 [PWG5102.RAS] 872 device1_8 [PWG5102.RAS] 873 device10_16 [PWG5102.RAS] 874 device10_8 [PWG5102.RAS] 875 device11_16 [PWG5102.RAS] 876 device11_8 [PWG5102.RAS] 877 device12_16 [PWG5102.RAS] 878 device12_8 [PWG5102.RAS] 879 device13_16 [PWG5102.RAS] 880 device13_8 [PWG5102.RAS] 881 device14_16 [PWG5102.RAS] 882 device14_8 [PWG5102.RAS] 883 device15_16 [PWG5102.RAS] 884 device15_8 [PWG5102.RAS] 885 device2_16 [PWG5102.RAS] 886 device2_8 [PWG5102.RAS] 887 device3_16 [PWG5102.RAS] 888 device3_8 [PWG5102.RAS] 889 device4_16 [PWG5102.RAS] 890 device4_8 [PWG5102.RAS] 891 device5_16 [PWG5102.RAS] 892 device5_8 [PWG5102.RAS] 893 device6_16 [PWG5102.RAS] 894 device6_8 [PWG5102.RAS] 895 device7_16 [PWG5102.RAS] 896 device7_8 [PWG5102.RAS] 897 device8_16 [PWG5102.RAS] 898 device8_8 [PWG5102.RAS] 899 device9_16 [PWG5102.RAS] 900 device9_8 [PWG5102.RAS] 901 sgray_1 [PWG5102.RAS] 902 sgray_16 [PWG5102.RAS] 903 sgray_8 [PWG5102.RAS] 904 srgb_16 [PWG5102.RAS] 905 srgb_8 [PWG5102.RAS] 906

10. IPP Printer Description Attributes 907

This specification defines three new IPP Printer description attributes. Table 10 lists the 908 attributes. Semantic model keyword values follow the usual conversion from 909 'ExampleKeyword' (TItle Case form) to 'example-keyword' (hyphenated words form). 910

Table 10 - IPP Printer Description Attributes 911

Element Name IPP Attribute Name PwgRasterDocumentBackside pwg-raster-document-backside PwgRasterDocumentResolutionSupported pwg-raster-document-resolution-supported PwgRasterDocumentTypeSupported pwg-raster-document-type-supported

Michael Sweet� 7/30/11 5:07 PMFormatted: Font:Bold



10.1 pwg-raster-document-backside (type2 keyword) 912

This REQUIRED Printer attribute specifies the bitmap coordinate system for the backside 913 of duplex sheets. 914

10.2 pwg-raster-document-resolution-supported (1setOf resolution) 915

This REQUIRED Printer attribute lists the supported page bitmap resolutions in dots per 916 inch. 917

10.3 pwg-raster-document-type-supported (1setOf type2 keyword) 918

This REQUIRED Printer attribute lists the supported Color Space and bit depth 919 combinations. 920

11. References 921

11.1 Normative References 922

[CUPSRASTER] M. Sweet, “CUPS Raster Format”, http://www.cups.org/spec-923 raster.html 924

[ISO32000] "Document management — Portable document format — Part 1: PDF 925 1.7", ISO 32000-2008 926

[POSTSCRIPT] Adobe Systems Incorporated, "PostScript® LANGUAGE 927 REFERENCE, third edition", 1999 928

[PWG5100.11] T. Hastings, D. Fullman, "IPP: Job and Printer Extensions - Set 2 929 (JPS2)", PWG 5100.11, October 2010, 930 ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext10-20101030-931 5100.11.pdf 932

[PWG5100.12] R. Bergman, H. Lewis, I. McDonald, M. Sweet, "Internet Printing 933 Protocol Version 2.0 Second Edition (IPP/2.0 SE)", PWG 5100.12, 934 February 2011, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ipp20-935 20110214-5100.12.pdf 936

[PWG5101.1] R. Bergman, T. Hastings, "Standard for Media Standardized Names", 937 PWG 5101.1, February 2002, 938 ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-939 5101.1.pdf 940





[PWG5108.1] W. Wagner, P. Zehler, "MFD Model and Common Semantics", PWG 941 5108.1, April 2011, ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-942 mfdmodel10-20110415-5108.1.pdf 943

[RFC2911] T. Hastings, R. Herriot, R. deBry, S. Isaacson, P. Powell, "Internet 944 Printing Protocol/1.1: Model and Semantics", RFC 2911, September 945 2000, http://www.ietf.org/rfc/rfc2911.txt 946

[RFC3805] R. Bergman, H. Lewis, I. McDonald, "Printer MIB v2", RFC 3805, 947 June 2004, http://www.ietf.org/rfc/rfc3805.txt 948

11.2 Informative References 949

[SAMPLES] "Sample PWG Raster files", ftp://ftp.pwg.org/pub/pwg/ipp/raster/ 950

12. Author's Addresses 951

Michael Sweet 952 Apple Inc. 953 10431 N. De Anza Blvd. 954 MS 38-4LPT 955 Cupertino CA 95014 956

Send comments to the PWG IPP Mailing List: 957

[email protected] (subscribers only) 958

To subscribe, see the PWG web page: 959

http://www.pwg.org/ 960

Implementers of this specification document are encourages to join the IPP Mailing List in 961 order to participate in any discussions of clarification issues and review of registration 962 proposals for additional attributes and values. 963

The editor would like to especially thank the following individuals who also contributed 964 significantly to the development of this document: 965

Justin Hutchings - Microsoft 966 Ira McDonald - High North 967 Andrew Mitchell - Hewlett Packard 968 Glen Petrie - Epson 969 William Wagner - TIC 970

971

Michael Sweet� 7/30/11 9:13 PMFormatted: PWG Reference



13. Change History 972

[ PWG Secretary: This section must be removed when Document is approved ] 973

13.1 July 30, 2011 974

1. Reworked to define Semantic Model elements with a normative appendix 975 defining IPP attributes. 976

2. Defined mapping from PWG Job Ticket to page header fields, and expanded all 977 applicable page header fields. 978

3. New conformance requirements (split between generic consumer/producer and 979 IPP implementations) 980

4. New TotalPageCount, ImageBox*, SgrayPrimary, and Vendor fields in the page 981 header 982

5. Replaced HorizontalResolution and VerticalResolution with HWResolution 983 (original name from CUPS Raster) and defined its values in terms of cross-feed 984 and feed resolution. 985

6. Added informative reference to PWG Raster samples. 986 7. Added more raster examples. 987 8. Updated the IANA registration information to match new attribute and keyword 988

names. 989

13.2 March 27, 2011 990

1. Restored the "pwg-raster-resolutions-supported" and "pwg-raster-types-991 supported" sections. 992

2. Added the necessary IANA registration templates for the IPP attributes and 993 values. 994

13.3 March 26, 2011 995

1. Clarified the rationale 996 2. Added DeviceN colorspaces. 997 3. Updated sample image encoding to use more efficient end-of-line sequences 998

(two bytes more efficient) 999 4. Added reference to JPS2's feed-orientation attribute 1000 5. Added LeadingEdge field to page header 1001 6. Updated requirements to account for feed orientation/LeadingEdge information 1002

13.4 February 23, 2011 1003

1. Updated MIME media type to image/pwg-raster 1004 2. Updated IPP attributes to be pwg-raster-xxx instead of ipp-raster-xxx 1005 3. Added Out of Scope section 1006



4. Updated introduction and rationale to cover scanning 1007 5. Updated PWG Raster format definition (section 4) to contain a complete 1008

description, including tables and figures, for the CUPS Raster v2 format. 1009 6. Updated pwg-raster-types-supported and pwg-raster-back-side to include figures 1010

and tables 1011 7. Updated conformance section 1012 8. Update IETF registration information 1013

13.5 January 26, 2011 1014

1. Updated document title and filename to use "IPP" as the prefix instead of "PWG". 1015 2. Added normative references to RFC 2911 and RFC 3805 1016 3. Changed "cups-raster" prefix on attributes to "ipp-raster" 1017 4. Added "ipp-raster-resolutions-supported" attribute 1018 5. Added page bitmap section 1019 6. Added conformance requirements 1020 7. Added IANA registration info 1021

13.6 January 24, 2011 1022

Initial draft. 1023

The Printer Working Group - ftp.pwg.org · 30/07/2011 · 49 manufacturers, print server...

Documents

Transcript of The Printer Working Group - ftp.pwg.org · 30/07/2011 · 49 manufacturers, print server...