attachment-0001
Hi Bill,<br><br>My replies are inline below.<br><br>Cheers,<br>- Ira<br><br><br><div class="gmail_quote">On Tue, Jan 5, 2010 at 4:35 PM, William Wagner <span dir="ltr"><<a href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size: 14pt; color: rgb(31, 73, 125);">Hi Ira,</span></p>
<p class="MsoNormal"><span style="font-size: 14pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 14pt; color: rgb(31, 73, 125);">Quite so. But I had not entered these questions as answered
since the responses did not appear to resolve my questions.</span></p>
<p class="MsoNormal"><span style="font-size: 14pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 14pt; color: rgb(31, 73, 125);"><span>1.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
</span></span></span><span style="font-size: 14pt; color: rgb(31, 73, 125);">Since from your response, a document may contain zero or one document
ticket, and a job can contain zero or more documents, I do not see the error in
saying that a job can contain zero or more document tickets. At any rate, for
those who have not internalized the model, it does answer the question of how
the document tickets get into the service.</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 14pt; color: rgb(31, 73, 125);">I may misunderstand, but I think
it would be misleading to say in the general document description that a document
may contain zero or one document ticket since documents can exist exclusive of
jobs, but I assume that it is only when a document is part of a job that it may
contain a document ticket.</span></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 14pt; color: rgb(31, 73, 125);"></span></p></div></div></blockquote><div><ira><br>When using the correctly capitalized terms for <br>the SM *objects*, a Document object can only<br>
be created *after* a Job object has been created<br>and the DocumentTicket object is optional (and <br>rarely used) to override the JobTicket object in <br>the Job object. <br><br>There is no such thing as a *lowercase* document <br>
ticket in the Semantic Model.<br></ira> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div link="blue" vlink="purple" lang="EN-US">
<div><p class="MsoNormal" style="margin-left: 0.5in;"><span style="font-size: 14pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 14pt; color: rgb(31, 73, 125);"><span>2.<span style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">
</span></span></span><span style="font-size: 14pt; color: rgb(31, 73, 125);">Your response with </span><span style="font-size: 14pt; color: rgb(31, 73, 125);">regard to </span><span style="font-size: 14pt;">StorageMakeAndModel,
although it appears to confirm my observation, does not address the question of
what the reference should be. We originally had two separate elements but there
appeared to be consensus that a single MakeAndModel element was reference-able.
I do not recall who maintained that, but if that is so, I would like the
reference.</span></p></div></div></blockquote><div><ira><br>There is no possible public MIB general reference <br>for MakeAndModel (which was inherited from IPP <br>in SM/1.0 and was for whole Printers only). <br>
<br>IETF Host Resources MIB only supports ASN.1<br>OIDs in the ProductID textual convention used<br>in hrDeviceID (and elsewhere) for manufacturer<br>and model - these OIDs cannot be meaningfully<br>converted to human-readable values for make<br>
and model.<br><br>By very loose implementation convention, most<br>imaging device manufacturers use sysDescr<br>and/or hrDeviceDescr (for hrDevicePrinter) to<br>include human-readable make and model - this<br>information cannot be parsed reliably - I have<br>
had a long thread with HP WJA developers on <br>this issue.<br><br>An IEEE 1284 Device ID does include make<br>and model, but a separate string (at least for<br>the whole network device) is redundant. <br><br>For *only* two of the subunits (InputTray and <br>
OutputTray), Printer MIB v2 includes make <br>and model. So there's no public MIB source <br>for make and model of any other subunits.<br><br>The SM/2.0 MakeAndModel element is synthetic <br>and does *not* have any public MIB reference.<br>
Whether this element is a good idea is really<br>questionable, IMHO.<br></ira> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div><p><span style="font-size: 14pt; color: rgb(31, 73, 125);"></span></p>
<p class="MsoNormal"><span style="font-size: 14pt; color: rgb(31, 73, 125);">Thanks,</span></p>
<p class="MsoNormal"><span style="font-size: 14pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 14pt; color: rgb(31, 73, 125);">Bill Wagner</span></p>
</div></div></blockquote></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.