[IPP] media-ready (1setOf (type2 keyword | name))

[IPP] media-ready (1setOf (type2 keyword | name))

Rizzo, Christopher christopher.rizzo at xerox.com
Thu Oct 24 16:27:26 UTC 2024


Just checking my understanding…

Given the following RFC 8011 definition for 1setOf X attributes:

5.1.18. ’1setOf X’
The ’1setOf X’ attribute syntax is one or more values of attribute
syntax type X. This syntax type is used for multi-valued attributes.
The syntax type is called ’1setOf’ rather than just ’setOf’ as a
reminder that the set of values MUST NOT be empty (i.e., a set of
size 0). Sets are normally unordered; however, each attribute
description of this type can specify that the values MUST be in a
certain order for that attribute.

From 5.2.11:
"media-ready", which differs from "media-supported" in that legal values only
include the subset of "media-supported" values that are physically
loaded and ready for printing with no Operator intervention required.

If there is no media present in any trays of a printer, and media-ready attribute is not allowed to have 0 values, how is media-ready supposed to be show that there is no media ready in a Get-Printer-Attributes response? Should the Tag Value (0x13) ‘no-value’ be used instead of (0x44) keyword? This somewhat implies a modification of the data type of media-ready from 1SetOf X to no-value?  If this is so, then I also presume that for any out of band values, there is no value-length or value appended to the encoding of Attribute-with-one-value (RFC 8010 Section 3.1.4).

===========================

Also – another question I’ve always wondered but would like to verify:

The data type “1setOf (type2 keyword | name(MAX))” seems to imply that any attributes of this type can either be


  1.  1setOf(type2 keyword) only or
  2.  2setOf(name(MAX)) only

And the set cannot have keyword and name values intermixed.  Is that correct?  The encoding document RFC 8010 Section 3.1.5 shows each additional value (after the 1st value) all have value-tags, so theoretically, an encoding can have intermixed data types.
Thanks,
Chris


Christopher Rizzo
Engineer II, Software Engineering
Design & Development Engineering

[signature_2423998234]<http://www.xerox.com/>

Xerox Corporation
Virtual Office Employee
26600 SW Parkway Ave
Wilsonville, OR 97070

[signature_2720245950]<https://www.linkedin.com/company/xerox/>   [signature_3277838456] <https://www.youtube.com/user/XeroxCorp>    [signature_2339567144] <https://twitter.com/Xerox>    [signature_4153322723] <https://www.instagram.com/xerox/>    [signature_344421844] <https://www.facebook.com/XeroxCorp>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20241024/0b6e5e9a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9065 bytes
Desc: image001.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20241024/0b6e5e9a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1409 bytes
Desc: image002.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20241024/0b6e5e9a/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1427 bytes
Desc: image003.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20241024/0b6e5e9a/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1528 bytes
Desc: image004.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20241024/0b6e5e9a/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1648 bytes
Desc: image005.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20241024/0b6e5e9a/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1456 bytes
Desc: image006.png
URL: <http://www.pwg.org/pipermail/ipp/attachments/20241024/0b6e5e9a/attachment-0005.png>


More information about the ipp mailing list