attachment-0001
<br><font size=2 face="sans-serif">I'm fine with "chosen" vs.
"actual"... not as concerned about the name as the concept. In
this case, actual might differ from requested due to something like a PDL
override (so "chosen" seems to fit) or it COULD differ due to
some circumstance (like the job was aborted prior to all copies completing)
in which case "actual" seems more apropos. </font>
<br><font size=2 face="sans-serif">----------------------------------------------
<br>
Harry Lewis <br>
IBM Printing Systems <br>
---------------------------------------------- </font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"McDonald, Ira" <imcdonald@sharplabs.com></b></font>
<p><font size=1 face="sans-serif">10/02/2002 07:30 PM</font>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
Harry Lewis/Boulder/IBM@IBMUS, sm@pwg.org</font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
RE: SM> Job "Actual" attributes</font>
<br>
<br><font size=1 face="Arial"> </font></table>
<br>
<br><font size=2><tt>Hi Harry,<br>
<br>
For what it's worth...<br>
<br>
Printer MIB used (from DPA I think...) the terminology of<br>
'Declared' or 'Requested' (for the input) and 'Chosen'<br>
(for what you're calling 'Actual' below).<br>
<br>
Cheers,<br>
- Ira McDonald<br>
<br>
-----Original Message-----<br>
From: Harry Lewis [mailto:harryl@us.ibm.com]<br>
Sent: Wednesday, October 02, 2002 5:56 PM<br>
To: sm@pwg.org<br>
Subject: SM> Job "Actual" attributes<br>
<br>
<br>
<br>
In IPP, PWG Semantic Model and PSI we have Job Template attributes with<br>
"sister" (supported, default and ready) Printer Description attributes.
When<br>
discussing the purpose of a "Job Ticket" in the semantic model,
we often<br>
refer to Job Template attributes as the "job ticket" as these
carry<br>
production intent. By definition, when queried, Job Template attributes
must<br>
return the value associated with each attribute during submission. Thus,<br>
there is no way to query a job (or document) and learn WHAT ACTUALLY<br>
HAPPENED w.r.t. any particular attributed (ex. copies). This is covered
by<br>
the JDF job ticket but we have said JDF is too workflow oriented for<br>
(initial) inclusion into the PWG Semantic Model. <br>
<br>
I would like to propose a solution - the addition of a group of Job<br>
Description attributes referred to as "-actual". These could
be extensions<br>
to the group of Job Progress attributes or a separate grouping of Job Actual<br>
(or "Job Completion") attributes. I know, in IPP proper, we don't
have the<br>
notion of job "history" (the job "disappears" as soon
as it has completed)<br>
so "actuals" would not be very useful. But in the semantic model
and PSI<br>
we're trying to overcome this. To the extent that we are reluctant to<br>
embrace a full fledged job ticket, the addition of "-actual"
attributes<br>
should go a long way toward providing much of the essential JT functionality<br>
that was previously missing for non-produciton environments. <br>
<br>
For example: <br>
<br>
+===================+======================+<br>
| Job Template |Job Description:Actual|<br>
| Attribute | Value Attribute
|<br>
+===================+======================+<br>
| copies | copies-actual
|<br>
| (integer (1:MAX)) | (integer (1:MAX)) |<br>
+-------------------+----------------------+<br>
| finishings | finishings-actual |<br>
|(1setOf type2 enum)|(1setOf type2 enum) |<br>
+-------------------+----------------------+<br>
| sides | sides-actual
|<br>
| (type2 keyword) | (type2 keyword) |<br>
+-------------------+----------------------+<br>
| number-up | number-up-actual
|<br>
| (integer (1:MAX)) | (integer (1:MAX)) |<br>
+-------------------+----------------------+<br>
| orientation- |orientation-requested-|<br>
| requested | actual
|<br>
| (type2 enum) | (type2 enum)
|<br>
+-------------------+----------------------+<br>
| media | media-actual
|<br>
| (type3 keyword | | (type3 keyword | |<br>
| name) | name)
|<br>
+-------------------+----------------------+<br>
| printer-resolution| printer-resolution- |<br>
| (resolution) | actual
|<br>
| | (resolution)
|<br>
+-------------------+----------------------+<br>
| print-quality | print-quality-actual |<br>
| (type2 enum) | (type2 enum)
|<br>
+-------------------+----------------------+<br>
<br>
---------------------------------------------- <br>
Harry Lewis <br>
IBM Printing Systems <br>
---------------------------------------------- <br>
</tt></font>
<br>