PROJ Title of Document
(Acronym)

Status: Initial

Abstract: This document defines something really interesting. Provide an abstract for your document here. Abstracts should be at most one paragraph long. Never call your document a "standard" here, it is a document or specification.

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:

http://ftp.pwg.org/pub/pwg/general/templates/wd-template.dotx

Copyright © YYYY 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: PROJ Title of Document (Acronym)

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: ieee-isto@ieee.org.

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.

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 Group

c/o The IEEE Industry Standards and Technology Organization

445 Hoes Lane

Piscataway, NJ 08854

USA

About the PROJECT NAME Work Group

Description of PROJECT NAME.

For additional information regarding PROJECT NAME visit:

http://www.pwg.org/PROJECT/

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

Table of Contents

1. Introduction	6

2. Terminology	6

2.1 Conformance Terminology	6

2.2 Other Terminology	7

2.3 Acronyms and Organizations	7

3. Requirements	8

3.1 Rationale for Title of Document	8

3.2 Use Cases	8

3.3 Exceptions	8

3.4 Out of Scope	8

3.5 Design Requirements	8

4. First Specification Section	8

5. Conformance Requirements	9

6. Internationalization Considerations	9

7. Security Considerations	9

8. IANA Considerations	9

9. References	9

9.1 Normative References	9

9.2 Informative References	9

10. Authors' Addresses	9

11. Change History	11

11.1 Month, DD, YYYY	11

List of Figures

Figure 1 - An Example Figure	4

List of Tables

Table 1 - An Example Table	4

Introduction

Provide an introduction for the document.

Figure 1 - An Example Figure

Table 1 - An Example Table Using the PWG Table Style

Keyword	Description	Conformance
One	The first keyword	REQUIRED
Two	The second keyword	OPTIONAL

Terminology

Conformance Terminology

Capitalized terms, such as MUST, MUST NOT, RECOMMENDED, REQUIRED, SHOULD, SHOULD NOT, MAY, and OPTIONAL, have special meaning relating to conformance as defined in Key words for use in RFCs to Indicate Requirement Levels [RFC2119]. The term CONDITIONALLY REQUIRED is additionally defined for a conformance requirement that applies to a particular capability or feature.

Printing Terminology

Normative definitions and semantics of printing terms are imported from IETF Printer MIB v2 [RFC3805], IETF Finisher MIB [RFC3806], and IETF Internet Printing Protocol/1.1: Model and Semantics [RFC2911].

Document: An object created and managed by a Printer that contains the description, processing, and status information. A Document object may have attached data and is bound to a single Job.

Job: An object created and managed by a Printer that contains description, processing, and status information. The Job also contains zero or more Document objects.

Logical Device: a print server, software service, or gateway that processes jobs and either forwards or stores the processed job or uses one or more Physical Devices to render output.

Output Device: a single Logical or Physical Device

Physical Device: a hardware implementation of a endpoint device, e.g., a marking engine, a fax modem, etc.

Protocol Role Terminology

This document also defines the following protocol roles in order to specify unambiguous conformance requirements:

Client: Initiator of outgoing connections and sender of outgoing operation requests (Hypertext Transfer Protocol -- HTTP/1.1 [RFC7230] User Agent).

Printer: Listener for incoming connections and receiver of incoming operation requests (Hypertext Transfer Protocol -- HTTP/1.1 [RFC7230] Server) that represents one or more Physical Devices or a Logical Device.

Other Terminology

Capitalized Term In Italics: defininition of the term with any references as appropriate.

Acronyms and Organizations

IANA: Internet Assigned Numbers Authority, http://www.iana.org/

IETF: Internet Engineering Task Force, http://www.ietf.org/

ISO: International Organization for Standardization, http://www.iso.org/

PWG: Printer Working Group, http://www.pwg.org/

Requirements

Rationale for Title of Document

Given the following existing specifications:

Title of First Specification [REFERENCE1]

Title of Second Specification [REFERENCE2]

...

Title of Nth Specification [REFERENCEN]

And given the need for WHAT YOU NEED, the TITLE OF DOCUMENT should:

Provide foo,

Define bar, and

Define bla.

Use Cases

Provide use cases for the document in subsections using the casual use case format.

Exceptions

Provide exceptions for the use cases using the casual use case format.

Out of Scope

The following are considered out of scope for this specification:

Definition of foo

Protocols for bar

Requirements for bla

Design Requirements

The design requirements for this specification are:

Define attributes for foo and bar

Define operations for bla

Register all attributes and operations with IANA

The design recommendations for this specification are:

Support additional "nice to have" use cases

First Specification Section

Provide specification information starting in section 4.

Conformance Requirements

Provide numbered lists of conformance requirements for the document.

Internationalization Considerations

For interoperability and basic support for multiple languages, conforming implementations MUST support:

The Universal Character Set (UCS) Transformation Format -- 8 bit (UTF-8) [STD63] encoding of Unicode [UNICODE] [ISO10646]; and

The Unicode Format for Network Interchange [RFC5198] which requires transmission of well-formed UTF-8 strings and recommends transmission of normalized UTF-8 strings in Normalization Form C (NFC) [UAX15].

Unicode NFC is defined as the result of performing Canonical Decomposition (into base characters and combining marks) followed by Canonical Composition (into canonical composed characters wherever Unicode has assigned them).

WARNING – Performing normalization on UTF-8 strings received from Clients and subsequently storing the results (e.g., in Job objects) could cause false negatives in Client searches and failed access (e.g., to Printers with percent-encoded UTF-8 URIs now 'hidden').

Security Considerations

Provide security considerations for this specification, such as the following.

The IPP extensions defined in this document require the same security considerations as defined in the IPP/1.1: Model and Semantics [RFC2911].

IANA and PWG Considerations

Provide IANA and PWG registration information for this specification.

Attribute Registrations

The attributes defined in this document will be published by IANA according to the procedures in IPP/1.1 Model and Semantics [RFC2911] section 6.2 in the following file:

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

The registry entries will contain the following information:

Document Description attributes:	Reference

--------------------------	---------

name (type)	[REFERENCE]

Document Status attributes:	Reference

--------------------------	---------

name (type)	[REFERENCE]

Document Template attributes:	Reference

--------------------------	---------

name (type)	[REFERENCE]

Job Description attributes:	Reference

--------------------------	---------

name (type)	[REFERENCE]

Job Status attributes:	Reference

--------------------------	---------

name (type)	[REFERENCE]

Job Template attributes:	Reference

--------------------------	---------

name (type)	[REFERENCE]

Operation attributes:	Reference

--------------------	---------

name (type)	[REFERENCE]

Printer Description attributes:	Reference

------------------------------	---------

name (type)	[REFERENCE]

Printer Status attributes:	Reference

------------------------------	---------

name (type)	[REFERENCE]

Subscription Description attributes:	Reference

------------------------------	---------

name (type)	[REFERENCE]

Subscription Status attributes:	Reference

------------------------------	---------

name (type)	[REFERENCE]

Subscription Template attributes:	Reference

------------------------------	---------

name (type)	[REFERENCE]

Attribute Value Registrations

The attributes defined in this document will be published by IANA according to the procedures in IPP/1.1 Model and Semantics [RFC2911] section 6.1 in the following file:

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

The registry entries will contain the following information:

Attributes (attribute syntax)

Keyword Attribute Value	Reference

-----------------------	---------

name (type2 keyword)	[REFERENCE]

value-1	[REFERENCE]

value-2	[REFERENCE]

name-supported (1setOf type2 keyword)	[REFERENCE]

< all name values >	[REFERENCE]

Type2 enum Registrations

The attributes defined in this document will be published by IANA according to the procedures in IPP Model and Semantics [RFC2911] section 6.1 in the following file:

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

The registry entries will contain the following information:

Attributes (attribute syntax)

Enum Value	Enum Symbolic Name	Reference

----------	------------------	---------

name (type2 enum)	[REFERENCE]

3	value-3	[REFERENCE]

4	value-4	[REFERENCE]

operations-supported (1setOf type2 enum)	[RFC2911]

0xXXXX	Operation-Name	[REFERENCE]

Operation Registrations

The attributes defined in this document will be published by IANA according to the procedures in IPP/1.1 Model and Semantics [RFC2911] section 6.4 in the following file:

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

The registry entries will contain the following information:

Operation Name	Reference

--------------	---------

Operation-Name	[REFERENCE]

Exiting-Operation-Name (Extension)	[REFERENCE]

Status Code Registrations

The attributes defined in this document will be published by IANA according to the procedures in IPP/1.1 Model and Semantics [RFC2911] section 6.6 in the following file:

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

The registry entries will contain the following information:

Value Status Code Name	Reference

------ ---------------------------------------------	---------

0x0400:0x04FF - Client Error:

0x04XX	client-error-name	[REFERENCE]

0x0500:0x05FF - Server Error:

0x05XX	server-error-name	[REFERENCE]

Semantic Model Registrations

The extensions defined in this specification and provided in the following file:

http://ftp.pwg.org/pub/pwg/NAME/wd/wd-docname-YYYYMMDD.zip

will be added to the PWG Semantic Model XML schema.

OR

Except as noted below, the IPP attributes, values, and operations defined in this specification and listed in the preceding sections will be added to the PWG Semantic Model XML schema using the method defined in section 21 of [PWG5108.07].

Table 2 lists the attributes that are mapped to alternate element names.

Table 2 - New Semantic Model Element Names

Attribute Name	Element Name
name	AlternateName
name-supported	Capabiltiies/AlternateName

Table 3 lists the values that are mapped to alternate Well-Known Values.

Table 3 - New Semantic Model Well-Known Values

Attribute Name	Value	Well-Known Value
name	value-1	AlternateValue1
name	value-2	AlternateValue2

Table 4 lists the operations that are mapped to alternate operation names.

Table 4 - New Semantic Model Operations

IPP Operation Name	Semantic Model Operation Name
Operation-Get-Name	AlternateGetName
Operation-Set-Name	AlternateSetName

References

Normative References

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

[ISO10646]	"Information technology -- Universal Coded Character Set (UCS)", ISO/IEC 10646:2011

[PWG5108.07]	P. Zehler, "PWG Print Job Ticket and Associated Capabilities Version 1.0", PWG 5108.07-2012, August 2012, http://ftp.pwg.org/pub/pwg/candidates/cs-sm20-pjt10-20120801-5108.07.pdf

[RFC2119]	S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119/BCP 14, March 1997, http://tools.ietf.org/html/rfc2119

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

[RFC5198]	J. Klensin, M. Padlipsky, "Unicode Format for Network Interchange", RFC 5198, March 2008, http://tools.ietf.org/html/rfc5198

[RFC7230]	R. Fielding, J. Reschke, "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", RFC 7230, June 2014, http://tools.ietf.org/html/rfc7230

[STD63]	F. Yergeau, "UTF-8, a transformation format of ISO 10646", RFC 3629/STD 63, November 2003, http://tools.ietf.org/html/rfc3629

[STD66]	T. Berners-Lee, R. Fielding, L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", RFC 3986/STD 66, January 2005, http://tools.ietf.org/html/rfc3986

[UAX15]	M. Davis, M. Duerst, "Unicode Normalization Forms", Unicode Standard Annex 15, March 2008, http://www.unicode.org/reports/tr15/

[UNICODE]	The Unicode Consortium, “The Unicode Standard, Version 6.2.0”, ISBN 978-1-936213-07-8, September 2012, http://www.unicode.org/versions/Unicode6.2.0/

Informative References

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

Authors' Addresses

Primary authors (using Address style):

John Doe

123 Hoppalong Highway

Exampleville, CA 12345

john.doe@exampleville.ca

The authors would also like to thank the following individuals for their contributions to this standard:

Turanga Leela - Planet Express

Zapp Brannigan - Democratic Order of Planets

Change History

Month, DD, YYYY

Initial revision.