Sergi,
Scaling and rotation could be applied to Print but at this time they are
not included in any current IPP specification and therefore not included
in the Print Service portion of the MFD specification. Perhaps JPS3
can include them if there is a desire and people willing to work on it.
There are limited controls that cover how an impression is laid out on a
media sheet (e.g., OrientationRequested, Resolution, NumberUp, the
various [X|Y] Image [Shift|Position] elements). If Scaling and
Rotation are included then JPS3 will have to address the interactions of
these IPP job Template attributes
The Transform Service is currently only a place holder. The intent is
for that service to be addressed after the services currently being
actively worked. It is incomplete and can be ignored for now. There is
no intent for simple services (e.g., copy, print, scan) to require a
workflow to produce output. The transformation service was intended
primarily as an "Impedance matcher" between the output of one service
and the input of another. The transform service could also function
independently to extend the capabilities of an MFD.
Pete
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler at Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
From: mfd-bounces at pwg.org [mailto:mfd-bounces at pwg.org] On Behalf Of
Casas, Sergi
Sent: Thursday, June 02, 2011 10:19 AM
To: mfd at pwg.org
Subject: [MFD] Question on print job ticket
Hi there,
I have noticed that in the Semantic Model v2, the job/document
processing ticket only has scaling and rotation elements for image
output services but not for impression output services. This seems to be
inconsistent, since printers are also able to scale and rotate documents
when ripping.
On a related note, rotation and scaling is available in the
TransformService, but this service has no operations defined in
ServicesOperations.xsd. Should rotation & scaling for printing be
ordered by setting a workflow with the TransformService feeding into the
PrintService ? if so, how ? why is this different for the ScanService ?
Thanks,
Sergi Casas
--
This message has been scanned for viruses and
dangerous content by MailScanner <http://www.mailscanner.info/> , and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/mfd/attachments/20110602/a137b707/attachment-0001.html>