Pete,
> On Nov 20, 2014, at 6:58 AM, Zehler, Peter <Peter.Zehler at xerox.com> wrote:
> ...
> The other attribute for specifying media size is “media-size” which is member attribute of “media-col” collection. The associated “media-col-supported” is a set of “media-col”.
Actually, no. "media-col-supported" is a list of "media-col" member attribute names that are supported. "media-col-database" provides the set of "media-col" values that are supported, and "media-col-ready" provides the set of "media-col" values that are ready/loaded.
> The "media-size-supported" is sort of a database of supported media and each unique combination is explicitly enumerated.
"media-size-supported" can also contain rangeOfInteger values, per 5100.3.
And for that matter, rangeOfInteger values are allowed in media-col-database and media-col-ready values, with the latter using it for roll-fed media where the length (y-dimension) provides the minimum and maximum (ideally, the remaining) length.
> For this reason the “media-col-supported’ is specially handled when getting the printer’s attributes. To specify two different supported sizes and example would be {{x-dimension:210, y-dimension:297},{x-dimension:297, y-dimension:420}} to show that it supports two values of "mediasize": A4 (210x297) and A3 (297x420). It does not support other combinations of "x-dimension" and "y-dimension" member attributes, such as 210x420 or 297x297, and it does not support non-enumerated values, such as 420x595.
>> The mistake that has been seen in implementation in the field is that when a supported size range is specified, not all the media sizes within that range are actually supported.
In that case, the printer should not return a min/max range that is not supported...
Are you looking for implementation guidance, a change to the definitions, or ???
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair