RE: IFX> Re: IPP> REG - Proposal for "job-recipient-name" Job Tem plate attribute

• Previous message: Michael Sweet: "IFX> Re: IPP> ATT - Updated "job-recipient-name" spec from the 9/13 IPP WG meeting and an ISSUE"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Michael,

Sold - I like your clarifications.

Cheers,
- Ira

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

"McDonald, Ira" wrote:
>
> Hi Mike,
>
> Here's a way to have our cake and eat it.
>
> The attribute 'job-recipient-name' is specified to be
> a person's full name, network user name, or whatever
> name's descriptive to humans (but NOT meant to be
> parsed by automated software).
>
> A different attribute 'job-recipient-role' could hold
> 'none', 'operator', 'admin', 'technician', etc. for
> jobs that need to reach someone who fills a particular
> role in the local network environment. If the attribute
> type was (keyword | name) then we could also let users
> specify roles like 'accounting', 'payroll', etc.

Now *that's* a good idea! :)

I'd only ammend this to add an empty job-recipient-name attribute
means that the actual recipient is unknown, and a member of the
job-recipient-role attribute should be used instead.

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

• Next message: pmoore@peerless.com: "IFX> Thoughts after first meeting"
• Previous message: Michael Sweet: "IFX> Re: IPP> ATT - Updated "job-recipient-name" spec from the 9/13 IPP WG meeting and an ISSUE"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Sep 21 2000 - 15:28:44 EDT