attachment-0001
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">All,<div><br></div><div>This is Apple's notice of prototyping of the current draft of the IPP Job and Printer Extensions - Set 3 (JPS3) specification as posted here:</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120327.pdf">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v10-20120327.pdf</a></div><div><br></div><div>Apple has prototyped all of the proposed extensions and has shipped many of them since CUPS 1.4. The only implementation issue not directly addressed by the current JPS3 specification is how printers and clients interpret colorant values ("colorantname") in the printer-supply attribute. This issue was identified during the original discussions for printer-supply (vs. the CUPS marker-xxx implementation) and can be addressed by referencing PWG 5101.1 (MSN1) for colorantname values, including the proposed additions from the current MSN2 draft, and finishing the update of 5101.1 (MSN2) to support a full set of reference color names and vendor colors.</div><div><br></div><div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>__________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span>
</div>
<br></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>