IFX Mail Archive: IFX> RE: IPP> REG - Proposal for "

IFX Mail Archive: IFX> RE: IPP> REG - Proposal for "

IFX> RE: IPP> REG - Proposal for "job-recipient-name" Job Template att ribute

From: Zehler, Peter (Peter.Zehler@usa.xerox.com)
Date: Fri Sep 08 2000 - 07:41:04 EDT


Tom, Mike,

I too would like to see the "job-recipient-name" attribute have a syntax of
type2 keyword | name(MAX). I would also like to see the
"job-recipient-name" attribute be a job description attribute as opposed to
a job template attribute. I do not see any advantage in the
"job-recipient-name-supported" or "job-recipient-name-default"

"job-recipient-name-supported" is not needed since the length of the name
syntax has already been defined and should not be truncated. (What is
printed on a banner sheet should be left to an implementation.) The
"job-recipient-name-default" would be covered in the specification. Having
the default be equivalent to the keyword 'none' would work for me. As an
implementer I would put both the "job-recipient-name" and the
"job-originating-user-name" on the banner sheet.

Pete

                                Peter Zehler
                                XEROX
                                Xerox Architecture Center
                                Email: Peter.Zehler@usa.xerox.com
                                Voice: (716) 265-8755
                                FAX: (716) 265-8792
                                US Mail: Peter Zehler
                                        Xerox Corp.
                                        800 Phillips Rd.
                                        M/S 139-05A
                                        Webster NY, 14580-9701

-----Original Message-----
From: Michael Sweet [mailto:mike@easysw.com]
Sent: Thursday, September 07, 2000 8:15 PM
To: Hastings, Tom N
Cc: ipp (E-mail); QUALDOCS DL (E-mail)
Subject: Re: IPP> REG - Proposal for "job-recipient-name" Job Template
attribute

"Hastings, Tom N" wrote:
> ...
> If the client omits this attribute in a create request, the printer
> MAY use the "job-recipient-name-default" (name(MAX)) Printer
> attribute value, unless it has not been configured by the
> administrator, or MAY use the "authenticated user" name (see
> [IPP-MOD] section 8.3), depending on implementation.
> ...

What if the default has not been configured? Will the -default
attribute contain an empty string, or will it be passed as a
no-value?

I'm thinking this and the job-recipient-name attribute may need to
be a type2 keyword | name(MAX), with keywords like:

    none
    administrator
    operator

to specify no specific recipient or the current admin/operator for
the device.

> The "job-recipient-name-supported" (integer(0:255) Printer attribute
> indicates the maximum length that the Printer will accept for the
> "job-recipient-name" Job Template attribute without truncation. A
> ...

Since the client will likely not know how to shorten a name so that
it remains unique, and since the recipient name will probably need
to be a valid name on the destination system anyways, having an
attribute that specifies the maximum number of significant characters
isn't all that useful IMHO.

Also, since the -supported attributes usually enumerate the supported
values for an attribute, it might make more sense to name it
"job-reciepient-name-max" instead.

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products                  mike@easysw.com
Printing Software for UNIX                       http://www.easysw.com



This archive was generated by hypermail 2b29 : Fri Sep 08 2000 - 07:49:24 EDT