IPP Mail Archive: RE: IPP> PRO Section 9.7 vs. MOD section 4.3: need clarifica

IPP Mail Archive: RE: IPP> PRO Section 9.7 vs. MOD section 4.3: need clarifica

RE: IPP> PRO Section 9.7 vs. MOD section 4.3: need clarifica

Turner, Randy (rturner@sharplabs.com)
Tue, 7 Apr 1998 00:16:48 -0700

Perhaps Bob's clarification text should actually be put into the std
document, that is, since it apparently was not clear to Carl.

Randy

-----Original Message-----
From: Carl Kugler [SMTP:kugler@us.ibm.com]
Sent: Monday, April 06, 1998 2:28 PM
To: robert.herriot@Eng.Sun.COM
Cc: ipp@pwg.org
Subject: Re: IPP> PRO Section 9.7 vs. MOD section 4.3:
need clarifica

Thanks, Bob, I think I get it now.

Maybe your answer also provides a clue to my next question:

If attributes-charset and attributes-natural-language Job
Description
Attributes are MANDATORY according to MOD/4.3, why aren't they
shown as
MANDATORY in "Group 3: Job Object Attributes" under

Print-Job Response:
Print-URI Response:
Create-Job Response:
Send-Document Response:
Send-URI Response:
Get-Job-Attributes Response:
Get-Jobs Response:

in MOD/15.3.4.3 "Validate the presence of a single occurrence of
required
Operation attributes"?

Could it be that the word MANDATORY has different meanings in
these two
sections?

4.3: MANDATORY ... attribute[s] MUST be supported by Printer
objects.
If it is not indicated as MANDATORY, then it is OPTIONAL

15.3.4.3: MANDATORY attributes [are those] that an IPP object
MUST
support and that a client MUST supply

It's still not clear to me.

-Carl

robert.herriot@Eng.Sun.COM on 04/06/98 01:48:31 PM
Please respond to robert.herriot@Eng.Sun.COM
To: ipp@pwg.org, Carl Kugler/Boulder/IBM@ibmus
cc:
Subject: Re: IPP> PRO Section 9.7 vs. MOD section 4.3: need
clarifica

If I understand your question correctly, I think that you have
having the same
confusion
that many other people have had about the word "MANDATORY". It
means that
the "Printer" must support the attribute. It does NOT mean that
the attribute
must
be included in each request/response.

In this particular case, attributes-charset is MANDATORY, i.e.
the printer
must

support the attribute, but in the get-jobs reponse it MUST be in
the operation
attributes
group and it is only in each job attribute group if the client
requested the
attribute via the
requested-attributes attribute in the request. Note, even if it
is present
in a
job attributes
group it does not affect the charset of those attributes. All
attributes in
the entire
response are in the charset specified by attributes-charset in
the operations
attribute
group, which I still believe must be first in that group (a
change we need to
make
to the model document).

Note that in the example attributes-natural-language is in one
of the job
attribute
groups in order to override the natural-language in the
operation attributes.
As I
have been implementing IPP, I have come to believe that this was
a bad idea.
It again
requires a special ordering, i.e. attributes-natural-language
must precede all
other
attributes if processing is to be simple.

Bob Herriot

At 03:34 PM 4/3/98 , Carl Kugler wrote:
>Looking at example 9.7, Get-Jobs Response, I don't see an
attributes-charset
>attribute in any of the three job attributes groups.* But
section 4.3 of the
>Model document, "Job Description Attributes", says that
attributes-charset is
>MANDATORY in the "job-description" attribute group.* This is
causing me
>cognitive dissonance.
>