Re: Printers using "media-size-name" instead of "media-size"

"Kennedy, Smith \(Wireless & IPP Standards\) via ipp" <[email protected]>
Newsgroups gmane.ietf.ipp
Message-ID <[email protected]>

> On Jul 6, 2021, at 2:54 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <[email protected]> wrote:
> 
> Signed PGP part
> Hi Mike,
> 
>> On Jul 6, 2021, at 2:42 PM, Michael Sweet <[email protected] <mailto:[email protected]>> wrote:
>> 
>> Smith,
>> 
>> > On Jul 6, 2021, at 4:07 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <[email protected] <mailto:[email protected]>> wrote:
>> >
>> > Signed PGP part
>> > Hi there,
>> >
>> > PWG 5100.7 5.3.1.15 <http://5.3.1.15/> and 5.3.1.16 <http://5.3.1.16/> define the "media-size" and "media-size-name" members of "media-col" thus:
>> >
>> > <PastedGraphic-1.png>
>> >
>> > What isn't clear to me is whether a Printer will be running a risk if it decides to implement "media-size-name" instead of "media-size", since Clients aren't required to support it?
>> 
>> "media-size" is REQUIRED while "media-size-name" is RECOMMENDED.
>> 
>> > If that is the case, then I'm not sure how a Printer could go about supporting "media-size-name" without risking interoperability issues with Clients.
>> 
>> The way we defined them allows a Printer to support both attributes, the Client can discover what the Printer supports, and the Client can use whichever supported attribute is best. The only issue with the current wording is that a Printer can't report both member attributes in a media-col-database or media-col-ready collection.
> 
> Yep, that's my exact point - we need to change that language so that a Printer can report both.

I'll file an erratum for this in a few minutes.

> 
> 
>

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAmDkw70ACgkQqskbKLDW
1N2eMg/8CaPYHBq2QfVksNHXh0flKKfAUG4GWvDjZGFg7Y4ZZbbRTANt+1v9WrBH
DWCCDt+cym8PTl6KMd/4tU388D9Sa9cHWSL78l/Xq6ogwu3SIUXTYt9ZbTyCsPlC
EGKCqsW5tDkkdvClVpn3R8+ryasMeLWm2noXnmyLy6qaHWrv447d+P06/EQ4EiZo
dz/6VB6c3X7H5gtR+ia6yo0lYMTK6RWXmDl3ZP8AbDwyniwDabmUgkdG9eOnqYnb
dtSV48YNEG3ReXaZhfUmN876vw4LGHSCA0Hp5+D0sjcp/oBiGRUWPMaG5/+nvPPk
aAsa1hSffa5O7kIClQtIt7e4EyTlxXmeiAsRKQHmFVPORiWnXAIHleyahyM8KKdo
05C4kZhSjUsTr/e393vtnQ9HsaNeftM09kxEh8E844C9rRDABQ6EF/yU8hhbRb/Y
YIOhW80qEOLRnrQy0bVWzpOTCqZ8Uw2ByzUY2mSKtpk63bIXfkBbjGdzamE0eedd
/RP3EcTL01xV3NlqlOcW7Y3EfwO+B8LwwwVBSOQTc8dhgYIAgRgAM/0rH1iOQNR2
CEBObvSV2ytUXaWRhFOiJIpTf6C1zlfH5K3HmJ1fUccWCQLuwNGIQDQttAbv7SLw
WTnheGJuwdPH5t/qb3VkTJPwrxIKJ9RKybfdBJSp3degwRP5IhA=
=6zM/
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.