Here are the answers to your questions preceded by TH>.
Tom, Bob, and Hugo
Could someone please clarify these doubts pertaining to
1>In the Print-job request, does the sequence in which Job
template attributes and Subscription attributes occur matter?
TH> The Subscription Attribute Group MUST come after the Job Attribute
Group, since all operations indicate the order that groups MUST be sent.
2>I have understood the following attributes in Send-Notification
request [indp: delivery method] to be mandatory. Are these correct?
TH> Yes, except as noted.
Group1: Operation attributes: attribute-charset
Group2 to N:Notification attributes:
TH> In order to be consistent with Subscription object names and to not have
duplicate attribute names in two different objects, we agreed to put a
"notify-" prefix on this attribute making it: "notify-printer-uri" for both
the Subscription object and what is sent in the Event Notification content
TH> We agreed to rename this: "notify-trigger-event" so that all Event
Notification content attributes start with "notify-", unless they are copied
from some other object (other than the Subscription object).
TH> The 3 above are only for job events.
TH> And "job-impressions-completed" is MUST for 'job-completed' and
TH> The 3 above are only for printer events.
Kindly let me know if there is any attribute missing/redundant.
TH> If the Subscribing client supplied notify-user-data (octetString(63))
you MUST send: notify-user-data
TH> There are also the following RECOMMENDED and OPTIONAL attributes for the
Notification Source to support in the Send-Notifications content:
printer-current-time REQUIRED if you support
TH> Also if the Printer implementation supports the OPTIONAL
"notify-requested-attributes" Subscription Template attribute, then the
Printer includes the additional Job and Printer attributes that it supports
in Event Notification as well.
This archive was generated by hypermail 2b29 : Mon Jun 19 2000 - 17:51:11 EDT