Smith,
*If* we were to adopt some notion of client-controlled duration, that would be major new semantics with defined defaults for each action.
However, I thought the purpose of adopting a 'cancel' action was to obviate the need for a duration, which is (currently) implementation specific behavior. And I believe we were planning on adding guidance for Identify-Printer, both for the Client and Printer, to the IIG2.
As for System Control Service, it might be a service that implements Identify-Printer but it shouldn't be the only one.
On Dec 9, 2013, at 5:28 PM, Kennedy, Smith (Wireless Architect) <smith.kennedy at hp.com> wrote:
> IMHO, these look fine. I wonder if the “identify action duration” needs to be covered by something? Does the System Control Service need to concern itself with this domain?
>> Smith
>>>> On 2013-12-09, at 12:53 PM, Michael Sweet <msweet at apple.com> wrote:
>>> All,
>>>> During our last Cloud Imaging Model WG meeting, we discussed having the ability to explicitly cancel a previous Identify-Printer operation. The consensus during that meeting was to add a new "identify-actions" keyword ('cancel') that would cancel any active identification mechanism.
>>>> In addition, a new "printer-state-reasons" keyword ('identifying-printer' was proposed, although given the existing 'identify-printer-requested' value I like adding 'identify-printer-active' instead) would be added to allow a Client to discover whether a printer is currently identifying itself using an action other than 'cancel', which by definition stops any active identification and removes the new keyword from the "printer-state-reasons" attribute...
>>>> The official registration would look like this:
>>>> Attributes (attribute syntax)
>> Keyword Attribute Value Reference
>> ----------------------- ---------
>> identify-actions (1setOf type2 keyword) [PWG5100.13]
>> cancel
>>>> printer-state-reasons (1setOf type2 keyword) [RFC2911]
>> identify-printer-active
>>>> Thoughts?
>>>> (I considered adding this to IPPSIX, but since this has application outside of shared infrastructure/cloud deployments I think we should register it separately...)
>>>> _______________________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>> _______________________________________________
>> ipp mailing list
>>ipp at pwg.org>>https://www.pwg.org/mailman/listinfo/ipp>
_______________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair