At the Bake Off 3 we have discussed the following resolution. Please send
comments.
Thanks,
Tom
Problem: [ipp-ntfy] doesn't specify the attribute syntax for the
"notify-status-code" that is returned in each Subscription Attributes group
in a Subscription Creation response.
Suggested solution: [ipp-indp] defines the attribute syntax for the
"notification-status-code" (which should be spelled "notify-status-code")
attribute returned in each Notification Attributes group as 'type2 enum'.
[ipp-mod] defines the attribute syntax of the "status-code" parameter as
'type2 enum'. The 'type2 enum' attribute syntax, rather than 'integer' is
intended to be used when the specification defines specific meanings for
each value. Therefore, [ipp-ntfy] should define the "notify-status-code" to
have the 'type2 enum' attribute syntax. Change name in [ipp-indp] from
"notification-status-code" to "notify-status-code" for consistency of
attribute names.
Suggested text:
Add to [ipp-ntfy] section 11.1.1.2 Create-Job Response:
"notify-status-code" (type2 enum):
Indicates the status of this subscription (see section 17 for the status
code definitions). This attribute MUST be returned in each Subscription
Attributes Group.
Change [ipp-indp] section 8.1.2 Send-Notifications Response from
"notification-status-code" to "notify-status-code".
-----Original Message-----
From: Carl Kugler/Boulder/IBM [mailto:kugler@us.ibm.com]
Sent: Tuesday, October 10, 2000 14:57
To: ipp@pwg.org
Subject: IPP> NOT> "notify-status-code" is undefined
ipp-not-spec-000830 fails to specify the attribute syntax for
"notify-status-code" (returned in the Subscription Attributes Groups of
responses).
It's not really obvious how to encode it, either. The operation attribute
group's "status-code" is a SIGNED-SHORT in a special location. There is no
attribute tag for a SIGNED-SHORT. "Integer" and "enum" are SIGNED-INTEGER.
I'm guessing it should be (integer(0x00000001:0x00000415))?
-Carl
This archive was generated by hypermail 2b29 : Fri Oct 20 2000 - 22:02:01 EDT