Jay,
I would agree that several of these attributes could be multi-valued.
Your example for "printer_service-notifcation-uri" is good. Also, the
"local-notification-uri" could be multi-valued. For example, if you send
a document to a printer at Dataproducts in Simi Valley, you could include
my uri as well as a secretary. If the secretary knows that I am not in the
office today, she will retrieve the document and place it in my mail box.
If I am in, she will just ignore the message. A corresponding
"local-notification-types-requested" should also be included.
Another approach would be to have an "alternate...notification-uri", but
this would always result in some limitations. The multi-valued approach
is much cleaner.
As we develop the scenarios, additional attributes may also be determined
to be multi-valued.
Tomorrows phone conference should be interesting. Unfortunately, I will
not be able to participate.
Ron Bergman
Dataproducts Corp.
On Tue, 10 Feb 1998, Jay Martin wrote:
> Ron,
>> > The model document should include the following attributes to support
> > these requirements.
> >
> > 1. remote-notification-uri (Job Template Attribute) No job
> > completion notification is returned to the remote user if this
> > attribute is not included in the job submission request.
> >
> > 2. local-notification-uri (Job Template Attribute) No job
> > notifications are returned to the local user if this attribute is
> > not included in the job submission request.
> >
> > 3. Local-notification-types-requested (Job Template Attribute) An
> > enum or bit map which defines the types of notifications
> > requested. Includes job completion, job progress, job errors,
> > printer errors, printer warnings, etc.
> >
> > 4. local-notification-types-default (Printer Description Attribute)
> >
> > 5. printer-service-notification-uri (Printer Description Attribute)
> > All printer problems are reported to this URI.
>> Can (should?) the URI attributes be multi-valued?
>> In particular, I'm thinking the "printer-service-notification-uri"
> attribute would greatly benefit from having multiple URI targets,
> so as to support delivery of printer device problems to multiple
> operations personnel.
>> Or is the "printer-service-notification-uri" attribute to be used
> for other reasons?
>> ...jay
>> ----------------------------------------------------------------------
> -- JK Martin | Email: jkm at underscore.com --
> -- Underscore, Inc. | Voice: (603) 889-7000 --
> -- 41C Sagamore Park Road | Fax: (603) 889-2699 --
> -- Hudson, NH 03051-4915 | Web: http://www.underscore.com --
> ----------------------------------------------------------------------
>