I guess the email I sent yesterday with the attached Excel Spreadsheet may have been a bit of overkill, given the succinctness of this IPP Accounting spec (referring to section 4.3). d:o)
Not sure my email had much influence then... Also not sure where to go from here or if more input is requested of me. I do think it's fair that one could say section 4.3 (which I agree is very well written) mainly covers what was in the spreadsheet I sent.
IPP Accounting spec does not mention legacy client issues you asked about however? Is that as planned or overlooked?
Thanks,
Chris
Christopher Rizzo
Xerox Corporation
GDG/Discovery/Advance Technology
26600 SW Parkway Ave.
Wilsonville, OR 97070-9251
Phone: (585) 314-6936
Email: Christopher.Rizzo at xerox.com
"The realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs."
-Maurice Wilkes, Memoirs of a Computer Pioneer
From: ipp <ipp-bounces at pwg.org> on behalf of PWG Workgroup <ipp at pwg.org>
Reply-To: Michael Sweet <msweet at msweet.org>
Date: Wednesday, January 29, 2020 at 12:49 PM
To: PWG Workgroup <ipp at pwg.org>
Subject: [IPP] Updated draft of Job Accounting best practice posted
All,
I have posted an updated interim draft of the Job Accounting with IPP v1.0 best practice document to:
https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippaccounting10-20200129.docxhttps://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippaccounting10-20200129.pdfhttps://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippaccounting10-20200129-rev.pdf
________________________
Michael Sweet
_______________________________________________
ipp mailing list
ipp at pwg.org<mailto:ipp at pwg.org>
https://www.pwg.org/mailman/listinfo/ipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20200129/e9d21aa4/attachment.html>
Our website uses cookies on your device to give you the best user experience. By using our website, you agree to the placement of these cookies. To learn more, read our privacy policy. Read Privacy Policy