At 13:39 03/10/97 PST, Robert Herriot wrote:
>>> From hastings at cp10.es.xerox.com Mon Mar 10 12:35:01 1997
>>>> We need to be striving to provide the same functionality to the end-user
>> for both printing paradigms with IPP.
>>>> So I suggest adding a requirement something like:
>>>> IPP shall provide the same functionality to the end-user for print
>> time choices of stored documents as the end-user has for printing
>> directly from an application.
>>>> For example, the user can choose number of copies, two-sided, stapling,
>> number-up, and page ranges, etc. whether printing from the application
>> that has the entire document or printing from a file or document that
>> has been stored on the web or in a document repository.
>>>>I'm not sure if this should be a requirement for V1.0, but we should definitely
>make it be a strong goal of IPP. If it is a requirement, then we need
>to be certain that it is implementable at a reasonable cost for all vendors.
>That is, some vendors have PDL interpreters that access external attributes
>and others don't. For the latter group, production attributes must be
>merged into the PDL data stream. Attributes, such as sides, are reasonably
>easy to merge, but attributes, such as n-up, are considerably more difficult.
I agree that the requirement can't be met with some PDL implementations.
I was proposing a requirement that the IPP protocol meet, not
what implementations will necessarily be able to support for all PDLs.
So we need to add some words to indicate this as a requirement for the
protocol to provide the functionality and a goal for implementation to
support. Perhaps, add some wording that this requirement is "to the extent
possible with today's PDL implementations".