Smith,
Sorry, I had an action to update the wiki page...
I had originally proposed renaming 'xxx-in-progress' to 'xxxing' to better match existing progress/transitional keywords and removing 'xxx-failed' to further reduce the number of keywords we are adding, not being sure that they provide useful/available/actionable information. Discussions in our last concall had consensus on keeping the 'xxx-failed' keywords along with the recommendation to use "printer-state-message" and "printer-detailed-status-messages" attributes.
Some existing keyword examples:
- 'moving-to-paused' and 'paused' and 'resuming'
- 'stopping' and 'stopped-partly'
- 'subunit-cooling-down' and 'subunit-over-temperature'
- 'subunit-warming-up' and 'subunit-under-temperature'
Alternatives could be:
- 'firmware-update-acquisition-failed'
- 'firmware-update-acquisition-processing'
- 'firmware-update-validation-failed'
- 'firmware-update-validation-processing'
- 'firmware-update-installation-failed'
- 'firmware-update-installation-processing'
- 'firmware-update-activation-failed'
- 'firmware-update-activation-processing'
or:
- 'firmware-update-acquisition'
- 'firmware-update-acquisition-failed'
- 'firmware-update-validation'
- 'firmware-update-validation-failed'
- 'firmware-update-installation'
- 'firmware-update-installation-failed'
- 'firmware-update-activation'
- 'firmware-update-activation-failed'
> On Oct 20, 2026, at 5:26 PM, Smith Kennedy <smitty.standards at gmail.com> wrote:
>> Hi Mike and all,
>> I'm starting to dig into creating the next draft of IPP Firmware Update Extensions v1.0 so that I can have a draft completed for review at the F2F and also hopefully have my prototype updated as well. I was reviewing what we have in the wiki:
>>https://github.com/istopwg/ippsample/wiki/Firmware-Updates#second-revision>> The one thing that bothers me a little is the keyword structures. What has currently been proposed:
>> 'firmware-update-acquiring'
> 'firmware-update-acquisition-failed'
> 'firmware-update-validating'
> 'firmware-update-validation-failed'
> 'firmware-update-installing'
> 'firmware-update-installation-failed'
> 'firmware-update-activating'
> 'firmware-update-activation-failed'
>> We changed from 'firmware-update-<PHASE>-in-progress' to 'firmware-update-<PHASE>ing'. This model seems a bit awkward because the "<PHASE>" substring of "<PHASE>ing" differs from the "<PHASE>" substring in "<PHASE>-failed". At the end of the day I don't actually care that much which one we choose but I want to try to avoid another round of string modifications. So should we have the above? Or should we have this?
>> 'firmware-update-acquisition-failed'
> 'firmware-update-acquisition-in-progress'
> 'firmware-update-validation-failed'
> 'firmware-update-validation-in-progress'
> 'firmware-update-installation-failed'
> 'firmware-update-installation-in-progress'
> 'firmware-update-activation-failed'
> 'firmware-update-activation-in-progress'
>> WDYT?
>> Smith
>>>>> On Oct 8, 2026, at 2:29 PM, Michael Sweet via ipp <ipp at pwg.org> wrote:
>>>> All,
>>>> I have posted the minutes from today's IPP workgroup conference call to:
>>>>https://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20261008.pdf>>>> Our next conference call is on October 24, 2026 at 3pm ET.
>>>> ________________________
>> Michael Sweet
>>>> _______________________________________________
>> ipp mailing list
>>ipp at pwg.org>>https://www.pwg.org/mailman/listinfo/ipp>
________________________
Michael Sweet