attachment
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div>The idea here was that it is more interoperable to access documents via their http: link than FTP </div><div><br></div><div>The browser that was "so defective" was Chrome on OS X Mountain Lion</div><div><br></div><div>It seems reasonable to use a link with the fewest potential problems for access - what's the downside of using http?</div><div><br></div><div>R.</div><div><br>On Oct 22, 2013, at 2:08 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div><div><div><div><div>Hi Mike,<br><br></div>So is this a new PWG standard practice decision?<br><br></div>Only post all new documents w/ HTTP links? Because someone<br></div>has a browser so defective that it can't access FTP links?<br>
<br></div>Sorry, up all night on calls to TCG meeting sessions in Osaka, Japan,<br></div>so I'm a bit frustrated by this thread.<br><br></div>Cheers,<br></div>- Ira<br><br></div><div class="gmail_extra"><br clear="all">
<div>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<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div>
<div></div><div></div><div></div><div></div></div>
<br><br><div class="gmail_quote">On Mon, Oct 21, 2013 at 11:54 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.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">Ira,<div><br></div><div>You can now use ftp: or http: to reference files on the FTP server, e.g.:</div><div><br></div><div><div> <a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsix10-20130923.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsix10-20130923.pdf</a></div>
</div><div><div> <a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsix10-20130923.pdf" target="_blank">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsix10-20130923.pdf</a></div></div><div><div class="h5"><div><br></div><div>
<br>
</div><div><div><div>On Oct 21, 2013, at 7:46 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><div><div>
<div><div>Hi Mike,<br><br></div>Out of curiosity, since there were a lot of topics in Randy's note, *what* is<br></div>now done?<br><br></div>Cheers,<br></div>- Ira<br><br></div><div class="gmail_extra">
<br clear="all"><div>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><br>
<br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div>
<div></div><div></div><div></div><div></div></div>
<br><br><div class="gmail_quote">On Mon, Oct 21, 2013 at 10:41 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is now done.<br>
<br>
On Oct 21, 2013, at 4:40 PM, Randy Turner <<a href="mailto:rturner@amalfisystems.com" target="_blank">rturner@amalfisystems.com</a>> wrote:<br>
<br>
><br>
> Ok, thanks.<br>
><br>
> This happened again this evening when I tried to access the links that Joe Murdock published earlier today…I was using a laptop that was failing the FTP links.<br>
><br>
> If we could just substitute http for ftp when publishing links then this would be great…<br>
><br>
> R.<br>
><br>
><br>
> On Oct 21, 2013, at 7:15 PM, Michael Sweet <<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>> wrote:<br>
><br>
>> Randy,<br>
>><br>
>> On Oct 21, 2013, at 4:03 PM, Randy Turner <<a href="mailto:rturner@amalfisystems.com" target="_blank">rturner@amalfisystems.com</a>> wrote:<br>
>>><br>
>>> Hi Guys,<br>
>>><br>
>>> I would like to request that hyperlinks to documents (minutes, documents, whatever) be "http:" links instead of "ftp:" links -- on a number of occasions, I and some of my colleagues have been in situations where we are using a browser that has issues with issuing "ftp:" requests.<br>
>>><br>
>>> Whereas using "http:" requests would be more "universal" with regards to be able to access documents in any browser context (even at an internet cafe where we might not have configuration capability with the browser).<br>
>><br>
>> We already have (currently undocumented) aliases on the main <a href="http://pwg.org/" target="_blank">pwg.org</a> web site to the standards directories. It would be trivial to support "<a href="http://ftp.pwg.org/" target="_blank">http://ftp.pwg.org/..</a>." aliases for all "<a href="ftp://ftp.pwg.org/" target="_blank">ftp://ftp.pwg.org/..</a>." links.<br>
>><br>
>>> Also, on another topic, after navigating the PWG website, I can't find any way to subscribe to the "PWG announce" mailing list. I already subscribe -- I'm making this comment because one of my colleagues was trying to subscribe and couldn't find a "subscribe" link for "PWG-announce".<br>
>><br>
>> Anyone that is subscribed to the WG mailing lists automatically should be subscribed to the pwg-announce list, but you can subscribe to just the pwg-announce list at:<br>
>><br>
>> <a href="https://www.pwg.org/mailman/listinfo/pwg-announce" target="_blank">https://www.pwg.org/mailman/listinfo/pwg-announce</a><br>
>><br>
>> _________________________________________________________<br>
>> Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
>><br>
>><br>
><br>
<br>
_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<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>
</blockquote></div><br></div>
</blockquote></div><br><div>
<span style="border-collapse:separate;border-spacing:0px"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;white-space:normal;font-family:'Andale Mono';word-spacing:0px"><div style="word-wrap:break-word">
_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></div></div></div></blockquote></div><br></div>
</div></blockquote></body></html>