attachment-0001
Hi,<br><br>I suggest that this new attribute be explicitly named<br>"media-size-name" (rather than the sadly ambiguous<br>"media-name") and constrained to ONLY take size<br>name values from the PWG Standard for Standardized <br>
Media Names (PWG 5101.1-2002) - which is BTW <br>certainly the most circular and meaningless PWG <br>Candidate Standard document title that we've ever <br>come up with...<br><br>Note that our DMTF CIM_PrintInputTray class has the<br>
element "MediaSizeName" which we used to map from<br>the Printer MIB's "prtInputMediaDimFeedDirDeclared"<br>and "prtInputMediaDimFeedDirDeclared" objects.<br><br>Also note that either "job-uri" or "job-id" can be used in<br>
job operations, but either MUST be accompanied by the <br>enclosing "printer-uri" that specifies the over-the-wire <br>protocol target of the IPP over HTTP request.<br><br>Cheers,<br>- Ira<br><br><br clear="all">
Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Co-Chair - TCG Hardcopy WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br>
<a 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>Christmas through April:<br> 579 Park Place Saline, MI 48176<br> 734-944-0094<br>May to Christmas:<br> PO Box 221 Grand Marais, MI 49839<br>
906-494-2434<div style="display: inline;"></div><div style="display: inline;"></div><div style="display: inline;"></div><br>
<br><br><div class="gmail_quote">On Fri, Mar 4, 2011 at 7:59 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Mar 4, 2011, at 3:53 PM, Yousey, Marc wrote:<br>
> One thing that would be nice to add to the media-col is the pwg-standard-name. With rounding going on on both sides of the wire it can be difficult to associate the standard sizes in media-supported to the media-size elements in the media-col-database. If the media-size collection had a pwg-standard-name (or similar) attribute we could be sure which size everyone was talking about rather than trying to guess.<br>
<br>
</div>I have no objection to adding a media-name member attribute that contains the PWG media name that corresponds to the given dimensions and margins. While size matching is not usually an issue for CUPS, margin matching often can be...<br>
<div class="im"><br>
> Also, a few questions:<br>
><br>
> 1) job-uri is just an informational object correct? I.e. it is not a new way to specify which job you are operating on in say a get-job-attributes or cancel-job request.<br>
<br>
</div>I assume you mean job-uuid? In the current definition it is only used as an informational object. The local job-id or job-uri is used to actually specify the job object in job operations. If all you had was a job-uuid, you would need to use the Get-Jobs operation to get a list of all jobs and their job-uuid attributes and then find the job you are interested in.<br>
<div class="im"><br>
> 2) On the new job-state-reasons, is there a corresponding status code to return with job requests? There seems to be a pairing between many but not all of the job-state-reasons and status-codes.<br>
<br>
</div>Currently I have not added any new status-code values, although we can do so if a need is seen. Both document-security-error and document-unprintable-error checking could be done as part of job/document creation, although I think it is more likely that they will be discovered while processing the job.<br>
<br>
Is the existing client-error-document-format-error status code sufficient, or would you prefer to see new status codes for each?<br>
<div><div></div><div class="h5"><br>
________________________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<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>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</div></div></blockquote></div><br><div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup{position: absolute;z-index: 9999;padding: 0px 0px;margin-left: 0px;margin-top: 0px;overflow: hidden;word-wrap: break-word;color: black;font-size: 10px;text-align: left;line-height: 130%;}</style>
<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.