attachment-0002
Hi Randy,<br><br>Not really (ready to use IPP now in Cloud). <br><br>There's no Register-Client operation. There's <br>no geo-location info (it's coming in JPS3 and<br>IPP Everywhere next year). There's no UUIDs<br>
for Client, Printer, and Job - a necessity.<br><br>There are no extension operations for Printers<br>behind firewalls talking to Cloud Services<br>(Register-Printer, Fetch-Job, Accept-Job,<br>Reject-Job, Notify-Job) - I wrote them up on<br>
slides a year ago - that's it. <br><br>We don't have the IPP operations to make<br>Cloud Print work like any of the current shipping<br>implementations.<br><br>That's the problem.<br><br>The minutes of Cloud WG meetings have recorded<br>
WG reviews of this current draft charter for 5 months<br>and the discussion w/ SC about waiting for MSPS.<br><br>The link on website is to the last *approved* charter.<br>There's no disconnect here. The SC minutes are<br>
also publicly archived with their discussions.<br><br>Cheers,<br>- Ira<br><br>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>
Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a style="color:rgb(51, 51, 255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102, 0, 204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div>
</div><div></div><div></div><div></div><br>
<br><br><div class="gmail_quote">On Wed, Dec 7, 2011 at 6:46 PM, Randy Turner <span dir="ltr"><<a href="mailto:rturner@amalfisystems.com">rturner@amalfisystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div><br></div><div><br></div><div>The charter published on the website is from June 2011 (or at least that's what the link says), which says that we're delivering a prototype IPP binding spec by Q4 2011, last call Q1 2012.</div>
<div>If this is incorrect or outdated, then that's fine. Maybe we should update the website if that's the case.</div><div><br></div><div>The charter you reference in your email shows only a prototype draft for IPP in Q4 / 2012 ? </div>
<div><br></div><div>Which means you may not see implementation of this until sometime mid 2013 maybe.</div><div><br></div><div>If there are multiple vendors shipping products now, by mid 2013, there will be quite a few deployments that will have to support whatever they do now, and whatever the PWG proposes. Or have a way to re-provision their network (on the fly) with something new.</div>
<div><br></div><div>Seems like we could get something out the door quicker than this...something that would nail down how to use just IPP (for now) in a cloud application. </div><span class="HOEnZb"><font color="#888888"><div>
<br></div><div>R.</div></font></span><div><div class="h5"><div><br></div><div><br></div><div><div><div>On Dec 7, 2011, at 3:07 PM, Ira McDonald wrote:</div><br><blockquote type="cite">Hi Randy,<br><br>Ahem - about threats to Q1 2012 schedule.<br>
<br>The current draft charter for the Cloud Imaging WG (from September) <br>moves all work items out a *year* and instead adds the Mapping spec <br>as near-term (depending on Print Job Ticket written in SM WG).<br>
<br><a href="ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20110926.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloud-charter-20110926.pdf</a><br><br>The Steering Committee deferred approval of that charter until we have<br>
resolves the license/copyright/reference text for the MSPS (aka XPS)<br>chapter the Mapping spec.<br><br>Cloud Print is shipping (from lots of people). It's using PPD, XPS, and <br>probably other job tickets now - that's where we see the "low hanging <br>
fruit".<br><br>New protocol work in IPP or SOAP bindings (for Client and Printer <br>registration with Cloud, for Fetch Jobs, NotifyJobs, etc.) is not "low <br>hanging fruit", we think.<br><br>Cheers,<br>- Ira<br>
<br><br clear="all">Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 <a href="tel:734-944-0094" value="+17349440094" target="_blank">734-944-0094</a><br>Summer PO Box 221 Grand Marais, MI 49839 <a href="tel:906-494-2434" value="+19064942434" target="_blank">906-494-2434</a><div style="display:inline">
</div><div style="display:inline"></div><div style="display:inline"></div><div>
</div><div></div><div></div><div></div><br>
<br><br><div class="gmail_quote">On Wed, Dec 7, 2011 at 5:30 PM, Randy Turner <span dir="ltr"><<a href="mailto:rturner@amalfisystems.com" target="_blank">rturner@amalfisystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi Bill,<br>
<br>
I am sensitive to the fact that there was little progress in the last year, and I think this is my point.<br>
<br>
As I said in my most recent message, I'm not calling into question the "work" that is being done, I'm curious as to whether the "sequence" or "priority" of this work with regards to publishing a Cloud Imaging profile could be an issue.<br>
<br>
What I would like to gauge from the working group is whether or not we could declare the job ticket as an optional "package" carried by a cloud printing job...essentially making it an abstraction in the cloud imaging model for now and lock-down/get consensus/publish a model that takes care of all the "low-hanging fruit" ASAP to prevent any potential fragmentation of the cloud imaging space.<br>
<br>
It's possible to publish a Cloud Imaging solution without detailing out job tickets -- I print jobs every day that don't use job tickets. However, as I said before, I'm not calling into question the work that's going...I think it's good work, I'm just looking at this project with my "PM Hat" on..<br>
<br>
If the Cloud Imaging WG feels there's no threat to fragmentation or that there's no risk to the Q1 / 2012 schedule, then that's fine too -<br>
<br>
R.<br>
<div><div><br>
<br>
On Dec 7, 2011, at 2:15 PM, William Wagner wrote:<br>
<br>
> Randy,<br>
><br>
> One of the intentions of the Cloud Imaging group was to advance the use of<br>
> the PWG Semantic Model elements in cloud imaging implementations. A well<br>
> defined PWG Job ticket is a necessary part of the Cloud Printing (and later<br>
> Cloud Imaging) modeling effort and therefore is not bogging down the<br>
> progress of a Cloud Printing solution. However, the workgroup believed that<br>
> correlating the PWG Job Ticket elements with elements of Print Job Tickets<br>
> currently being used (especially PPD and so-called XPS) both would assist in<br>
> encouraging consistent and PWG element coherent use of these other job<br>
> tickets and would prepare the way for use of the PWG Print Job Ticket in<br>
> these extant cloud Printing implementations. Because the mapping effort is<br>
> primarily addressed at existing Cloud Printing applications, it may be<br>
> considered as preempting the work on the PWG Cloud Printing solution.<br>
> However, since we went almost a year without making much progress on the PWG<br>
> Cloud Printing solution, I suggest that the mapping effort is more a<br>
> constructive diversion rather than a blocking (or bogging) effort.<br>
> Bill Wagner<br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a> [mailto:<a href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a>] On Behalf Of<br>
> Zehler, Peter<br>
> Sent: Wednesday, December 07, 2011 1:40 PM<br>
> To: Randy Turner; <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
> Subject: RE: [Cloud] Minutes posted for today's face-to-face meeting<br>
><br>
> Randy,<br>
><br>
> The "PWG Print Job Ticket and Associated Capabilities" specification is<br>
> not bound to Cloud Printing. Cloud Printing is one environment that<br>
> would benefit from an open specification for Print Job Tickets and the<br>
> standardization for the representation of the capabilities and defaults.<br>
> All we are really doing is splitting out the job ticket, capabilities<br>
> and defaults from the PWG semantic model. This, of course, is based on<br>
> IPP and enjoys wide support across the industry. We have an XML schema<br>
> encoding that will be released along with the specification.<br>
><br>
> Pete<br>
><br>
><br>
> Peter Zehler<br>
><br>
> Xerox Research Center Webster<br>
> Email: <a href="mailto:Peter.Zehler@Xerox.com" target="_blank">Peter.Zehler@Xerox.com</a><br>
> Voice: <a href="tel:%28585%29%20265-8755" value="+15852658755" target="_blank">(585) 265-8755</a><br>
> FAX: <a href="tel:%28585%29%20265-7441" value="+15852657441" target="_blank">(585) 265-7441</a><br>
> US Mail: Peter Zehler<br>
> Xerox Corp.<br>
> 800 Phillips Rd.<br>
> M/S 128-25E<br>
> Webster NY, 14580-9701<br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a> [mailto:<a href="mailto:cloud-bounces@pwg.org" target="_blank">cloud-bounces@pwg.org</a>] On Behalf Of<br>
> Randy Turner<br>
> Sent: Wednesday, December 07, 2011 1:24 PM<br>
> To: <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
> Subject: Re: [Cloud] Minutes posted for today's face-to-face meeting<br>
><br>
> Hi Guys,<br>
><br>
> I'm assuming all of this job ticket discussion is reusable outside of<br>
> "Cloud" applications ? Or we only talking about "Cloud-specific"<br>
> attributes of print-job-tickets ?<br>
><br>
> If this discussion is NOT cloud-specific, then I would hope that this<br>
> discussion does not artificially bog down the progress of a Cloud<br>
> Printing solution...<br>
><br>
> R.<br>
><br>
><br>
> On Dec 7, 2011, at 9:56 AM, Michael Sweet wrote:<br>
><br>
>> All,<br>
>><br>
>> I have posted the minutes from today's face-to-face to:<br>
>><br>
>><br>
>> <a href="ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-f2f-minutes-20111207.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-f2f-minutes-20111207.pdf</a><br>
>><br>
>> Action items:<br>
>><br>
>> - Justin to work with Microsoft Legal on the appropriate<br>
> citation/reference to MSPS based on the new license for inclusion with<br>
> the MSPS content in the mapping document, and any process for the PWG to<br>
> make a formal request<br>
>> - Ron or Bill to post a call for wider participation of driver<br>
> developers for the XPS/MSPS stuff<br>
>> - Mike to make "first-index" in JPS3 1-based instead of 0-based<br>
>><br>
>> _________________________________________________________<br>
>> Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
>><br>
>><br>
>> --<br>
>> This message has been scanned for viruses and dangerous content by<br>
>> MailScanner, and is believed to be clean.<br>
>><br>
>> _______________________________________________<br>
>> cloud mailing list<br>
>> <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
>> <a href="https://www.pwg.org/mailman/listinfo/cloud" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br>
>><br>
><br>
><br>
> --<br>
> This message has been scanned for viruses and dangerous content by<br>
> MailScanner, and is believed to be clean.<br>
><br>
> _______________________________________________<br>
> cloud mailing list<br>
> <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
> <a href="https://www.pwg.org/mailman/listinfo/cloud" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br>
><br>
> --<br>
> This message has been scanned for viruses and<br>
> dangerous content by MailScanner, and is<br>
> believed to be clean.<br>
><br>
> _______________________________________________<br>
> cloud mailing list<br>
> <a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
> <a href="https://www.pwg.org/mailman/listinfo/cloud" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br>
><br>
><br>
<br>
<br>
--<br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner, and is<br>
believed to be clean.<br>
<br>
_______________________________________________<br>
cloud mailing list<br>
<a href="mailto:cloud@pwg.org" target="_blank">cloud@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/cloud" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br>
</div></div></blockquote></div><br><div></div>
</blockquote></div><br></div><br>--
<br>This message has been scanned for viruses and
<br>dangerous content by
<a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is
<br>believed to be clean.
</div></div></div>
<br>_______________________________________________<br>
cloud mailing list<br>
<a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/cloud" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br>
<br></blockquote></div><br><div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup"></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.