Ron,
The telecon on Wednesday spent considerable time worrying about the
duplicate ways that IPP/1.1 and [IPP-PROD] have of specifying media types,
since our Media Type names can be used as keyword values of the IPP/1.1
"media" Job Template attribute and as keyword values of the "media-type"
member attribute of the [IPP-PROD] "media-col" Job Template attribute.
[IPP-PROD] REQUIRES that an implementation that supports "media-col" MUST
also support the "media" attribute. Furthermore, which member attributes of
the "media-col" are supported depends on implementation.
So we came up with the following simple way for the Media Type Name values
to be subsetted, so that there was only one way to request media with the
"media" and "media-col" attributes.
The current Appendix A text about [IPP-PROD] is:
The Internet Printing Protocol, Production Printing Attributes [IPP-PROD]
Standard Media Name IPP Production Printing Usage (see notes 2 and 3)
Media Type Name Keyword values of the "media-type"
Media Color Name Keyword values of the "media-color"
Notes:
1. Printer MIB size names do not include the dimensions part. The
dimension are represented by the objects prtInputMediaDimFeedDirDeclared,
prtInputMediaDimXFeedDirDeclared, prtInputMediaDimFeedDirChosen, and
prtInputMediaDimXFeedDirChosen.
2. The Production Printing Attributes referenced are all member
attributes of the "media-col" Job Template attribute.
3. The media sizes are included in the "media-size" member attribute of
the "media-col" Job Template attribute as a pair of numeric values (mm/100).
As an editorial suggestion, I suggest adding the phrase "member attribute"
to the end of both entries in the table.
More importantly, we can clarify the use of the Media Type Names with the
following note added to the first entry:
Keyword values of the "media-type" member attribute (note 4)
4. In order to have a canonical representation for media with the
"media-col" Job Template attribute, implementations that support the
"media-type" member attribute SHOULD subset the Media Type Name keyword
values that are represented by other supported member attributes, even
though these Media Type Name keyword values are supported by the "media" Job
Template attribute. For example, if the implementation supports the
"media-type", "media-front-coating", and "media-back-coating" member
attributes and the 'stationery', 'stationery-glossy', stationery-matte',
'photographic', 'photographic-glossy', and 'photographic-matte' keyword
values for the "media" Job Template attribute, it SHOULD only support the
'stationery' and 'photographic' keyword values for the "media-type" member
attribute and use the 'none', 'glossy', and 'matte' keyword values for the
"media-front-coating" and "media-back-coating" member attributes.
Comments?
Tom