IPP Mail Archive: Re: IPP> MOD - NLO 3 of 4: Vote to simplify Get-Jobs

IPP Mail Archive: Re: IPP> MOD - NLO 3 of 4: Vote to simplify Get-Jobs

Re: IPP> MOD - NLO 3 of 4: Vote to simplify Get-Jobs

Robert Herriot (robert.herriot@Eng.Sun.COM)
Wed, 21 Oct 1998 12:26:01 -0700

I vote YES on this change because the current rule requires SPECIAL CODE for attributes-natural-language for the one case of a Get-Jobs response while providing little or NO BENEFIT. The language override is more simply handled at the attribute level, as is the case for all other operation requests and responses.

In my server implementation I didn't implement this feature because I had remembered it as optional, based on IPP discussions.

If this feature retains its mandatory nature, then it raises several issues that we will need to resolve.

1) Suppose the client requests attributes-natural-language as one of the requested-attributes. If a job's natural language differs from the one in operation-attributes can the attributes-natural-language appear twice in the group, once in the first position to meet the rule under vote and a second time as a normal requested attribute. Otherwise, a printer must have special code to avoid sending attributes-natural-language twice.

2) Is attributes-natural-language really required to appear at the beginning of a job attribute group if the group does not contain job-attributes of type name or text.

Bob Herriot

At 08:52 AM 10/21/98 , you wrote:
>Summary: This mail message proposes a change in the specification of
>Get-Jobs to remove an extra level of Natural Language Override at the job
>level. With this change Get-Jobs would be handled the same as any other
>operation with respect to the Natural Language Override mechanism at the
>attribute level.
>* The proposal to vote on is to delete the indicated paragraph
>* below from Section Get-Jobs Response.
>* Please indicate your acceptance or rejection of this proposal
>* on the mailing list by Monday, Nov 2.
>This change will affect implementations that correctly implement the June
>1998 Mode and Semantics specification. However, we suspect that many
>implementations may have ignored this feature, so that deleting this
>paragraph will have no impact on them. Implementers, is this suspicion
>Currently, Section Get-Jobs Response contains the following
> For any job submitted in a different natural language than
>the natural language that the Printer object is returning in the
>"attributes-natural-language" operation attribute in the Get-Jobs response,
>the Printer MUST indicate the submitted natural language by returning the
>Job object's "attributes-natural-language" as the first Job object
>attribute, which overrides the "attributes-natural-language" operation
>attribute value being returned by the Printer object. If any returned
>'text' or 'name' attribute includes a Natural Language Override as described
>in the sections and, the Natural Language Override overrides
>the Job object's "attributes-natural-language" value and/or the
>"attributes-natural-language" operation attribute value.
>Tom Hastings
>(310) 333-6413