IPP Mail Archive: Re: IPP> MOD Need Clarification re: Type4 keywords [input fo

Re: IPP> MOD Need Clarification re: Type4 keywords [input fo

Carl Kugler (kugler@us.ibm.com)
Thu, 5 Mar 1998 16:46:00 -0500

Tom-

> Why are there attributes that have both 'type4 keyword' and 'name'
> (and hence 'nameWithLanguage) data types?

I think that this is a new, different question, and a good one. Aren't=
these
the only attributes for which a multi-valued attribute instance may hav=
e a
mixture of its defined attribute syntaxes?

If true, collapsing the redundant '(type4 keyword | name)' to 'name', w=
ould
allow one attribute syntax tag to apply to a whole attribute, even a
multi-valued one. It would also make life easier for implementers tryin=
g to use
strong typing.

-Carl

hastings@cp10.es.xerox.com on 02/09/98 04:46:51 PM
Please respond to hastings@cp10.es.xerox.com @ internet
To: ipp@pwg.org @ internet, Carl Kugler/Boulder/IBM@ibmus
cc:
Subject: Re: IPP> MOD Need Clarification re: Type4 keywords [input fo

At 14:06 02/02/1998 PST, Carl Kugler wrote:
>Attributes with type 4 keywords also allow the 'name' attribute syntax=
for
>administrator defined names. Keywords SHALL be in U.S. English, but
attributes
>that are indicated to have the 'name' attribute syntax also automatica=
lly
have
>the 'nameWithLanguage' attribute syntax.
>
>So in general, attributes with type 4 keywords can use the Language Ov=
erride
>Mechanism?

Correct, but because the 13 attributes that have 'type 4 keyword' data =
type,
also have the 'name' data type:

+-------------------+----------------------+----------------------+
| job-hold-until | job-hold-until- |job-hold-until- |
| (type4 keyword | | default | supported |
| name) | (type4 keyword | |(1setOf |
| | name) | type4 keyword | name)|
+-------------------+----------------------+----------------------+
| job-sheets | job-sheets-default |job-sheets-supported |
| (type4 keyword | | (type4 keyword | |(1setOf |
| name) | name) | type4 keyword | name)|
+-------------------+----------------------+----------------------+

+-------------------+----------------------+----------------------+
| media | media-default | media-supported |
| (type4 keyword | | (type4 keyword | |(1setOf |
| name) | name) | type4 keyword | name)|
| | | |
| | | media-ready |
| | |(1setOf |
| | | type4 keyword | name)|
+-------------------+----------------------+----------------------+

not just because they have the 'type 4 keyword' data type. But we
thought that if an administrator is making up names (which is what
type 4 keywords are), that an implementation may want to be simple
and treat them as names in the language that the administrator is
using or may want to be more complex and allow the administrator to
define keywords that clients can localize into various languages.

Sounds like something for the FAQ:

Why are there attributes that have both 'type4 keyword' and 'name'
(and hence 'nameWithLanguage) data types?

Tom

>
> -Carl
>
>

=