attachment-0001
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>Comments and Idea for paid printing</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hello<BR>
<BR>
As with the IPP FaxOut, I have unable to review the IPP Paid Printing document until now.<BR>
<BR>
Overall, I was concerned that "Extension for Paid Printing" is being extended through 'finishings" while the concept of "paid-printing" is a business or commerce notion and not a finishing step. While I need to study the document in more detail; how does the current paid-printing model support a print job where a set of differently priced transform service are needed. <BR>
<BR>
Having recently reviewed the PrintTalk specification of JDF; this is an interesting model to explore for PWG (independent of just IPP) "paid-prinitng" for several reason. Instead of modifying/extending JDF, PrintTalk wraps JDF in a business transaction or commerce transaction. With it's relatively simple set API calls it supports very complex set of operations ranging from Quoting, Notations, etc.; again with out modification to the print job JDF. PrintTalk can itemize items and provide a quote for each item. And, finally, PrintTalk is already widely used and deployed. PWG could create a version of PrintTalk, called IppPrintTalk (or PrintTalkIpp or PrintTalkPwg) by simply replacing JDF with PWG (or IPP) in the existing PrintTalk specification. Now IPP stays the same while extending an existing "paid printing" API and implementations which could be applied to any PWG model (Cloud?)<BR>
<BR>
Other comments on the specification itself<BR>
<BR>
The attribute "printer-charge-info-uri" is not defined in this document (perhaps somewhere else). But my concern that a discussion about how a User is associated with a paid (payment) service is out-of-scope.<BR>
<BR>
<BR>
Section 4.2 PIN/Passcode Printing<BR>
Section 4.3 Release Printing<BR>
I believe these sections are out-of-scope for paid-printing since there is not "payment" requirement for these types of printing functionalities.<BR>
<BR>
Section 4.5 Job Review<BR>
I believe this section is out-of-scope for paid-printing. "Job Review" could be applied to any print scenario and not specific relevance to paid-printing. In fact, if a User submits a print job for (100,000 copies) and payment is confirmed; then print the 100,000 copies. <BR>
<BR>
(Mike I assume specification are written to American English notation so 100.000 should be 100,000?)<BR>
<BR>
glen<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
<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>