attachment-0001
<br><font size=2 face="sans-serif">I had a task to write up a new use case
and flow diagram. I got hung up as you can see below and need some explanation
about the two ways for a client to associate a target device with a job
and specify the document type transform.</font>
<br>
<br><font size=2 face="Courier New">1. Job
is submitted to a printer via IPP or some other “legacy” protocol</font>
<br>
<br><font size=2 face="Courier New"> a.
Job is in some document format the printer
does not support natively</font>
<br>
<br><font size=2 face="Courier New"> b.
Printer will behave as both client and
target device to engage print (transform) service.</font>
<br>
<br><font size=2 face="Courier New"> c.
Printer does not want to poll to know
when the print service has completed the transform and is ready to deliver
the job</font>
<br>
<br><font size=2 face="Courier New">2. Using
the TargetDeviceSupported Interface on the print service, Printer registers
with print service as Target Device</font>
<br>
<br><font size=2 face="Courier New"> a.
targetDeviceSupportInterface</font>
<br><font size=2 face="Courier New">
i. registerTargetDevice</font>
<br><font size=2 face="Courier New">
ii. deliveryMethod –
“push”</font>
<br>
<br><font size=2 face="Courier New">3. Using
the JobControl Interface on the print service, Printer (acting as client)
defines targetDevice, specifies “deliver” and requests a data type to
translate to (of course the Printer will request the correct document format
for itself… the whole point of this exercise).</font>
<br>
<br><font size=2 face="Courier New"> a.
jobControlInterface</font>
<br><font size=2 face="Courier New">
i. createJob</font>
<br><font size=2 face="Courier New">
1. targetDeviceIdentifier</font>
<br><font size=2 face="Courier New">
2. deliverToTargetDevice
= true</font>
<br><font size=2 face="Courier New">
3. requestedTargetDeviceDataType</font>
<br>
<br><font size=2 face="Courier New">OK HERE’S
(ONE PLACE) WHERE I’M LOST</font>
<br>
<br><font size=2 face="Courier New">4. Using
the targetDeviceSupportedInterface on the print service, Printer COULD
associate the target device with the UID acquired during createJob (right?)
and also request the target device data type</font>
<br>
<br><font size=2 face="Courier New"> a.
targetDeviceSupportInterface</font>
<br><font size=2 face="Courier New">
i. associateTargetDevice</font>
<br><font size=2 face="Courier New">
1. jobURI</font>
<br><font size=2 face="Courier New">
2. userID</font>
<br><font size=2 face="Courier New">
3. targetDeviceIdentifier</font>
<br><font size=2 face="Courier New">
4. requestedTargetDeviceDataType</font>
<br>
<br><font size=3 face="Times New Roman">What am I missing? Why do I feel
like (3) and (4) are mostly redundant? Is one supposed to represent a longer
term relationship between client and print service while the other should
be thought of more as a “per job” specification? </font>
<br><font size=2 face="sans-serif">----------------------------------------------
<br>
Harry Lewis <br>
IBM Printing Systems <br>
---------------------------------------------- </font>