2019

e created which closely emulate
the existing end-user- expected functionality of fax." but shorter-winded.

[...]

-Dan Wing

language being returned for the response as a whole. If the natural
language is different for an attribute than the response as a whole,
require the IPP object to return the attribute using the
'nameWithLanguage' or 'textWithLanguage' attribute syntaxes that
explicitly specifies the natural language.

ACTION ITEM (Tom): Send out a request for vote on the mailing list to
remove the job-level natural language override for Get-Jobs.

4.2 Remove the entire Natural Language Override mechanism

Remove the 'textWithoutLanguage' and 'nameWithoutLanguage' attribute
syntaxes altogether. They add complexity to the protocol which may
introduce bugs or interoperability problems. They are only
optimizations of responses. In fact, they are not very good
optimizations, because it requires a response to have more than 5 or 6
text and/or name attribute values (of the same language), before the
number of octets is less than if each attribute used the
'textWithLanguage' representation. This is because the "attributes-
natural-language" operation attribute requires about 37 octets, and each
attribute only requires about 6-9 extra octets per value to represent
the natural language explicitly. This simplification does not reduce
any functionality. It had been suggested by Keith Moore last May as
well.

There was considerable support for this proposal. On the other hand,
implementations of IPP have been announced, so that we need to get real
feedback from the participants on whether to make this simplification.
We also need to see whether the complete spec in the Model document for
Natural Language Override mechanism was actually implemented or not.

ACTION ITEM (Tom): Send out a request for vote on the mailing list to
remove the 'textWithoutLanguage' and 'nameWithoutLanguage' attribute
syntaxes.

2

5 Review of Issues

We reviewed the proposed Answer text in the Issues List posted on Oct 6
in:

ftp://ftp.pwg.org/pub/pwg/ipp/proposed-clarifications/ipp-issues-list-
mod-1.3.pdf

Any issues that have no comments against them at either a telecon or on
the mailing list for two weeks will be considered resolved using the
explicit text in the Answer section.

ACTION ITEM (Tom): Edit those proposed text clarifications into the IPP
Model and Semantics specification starting Oct 21, 1998 that have no
comments.

5.1 Issue 1.10 - Case sensitivity in URLs

There were no c