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]>
Hi Mike,

> On Jul 6, 2021, at 2:42 PM, Michael Sweet <[email protected]> wrote:
> 
> Smith,
> 
> > On Jul 6, 2021, at 4:07 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <[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.

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

iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAmDkwwAACgkQqskbKLDW
1N2knBAAictd/QO3cqchDWkRtlkPHyy2y1yt48wZaPyvymSSC3EyV461wFTdMYoi
uDDqVCRPaNFz0/Ghj8x8NHUKyo04UwFZz0WD+j/rkvfvRNuQ9OCSKRP0pLdBkjZJ
hkG16DxCaqhSEZ9CmW8scLRtZasosJ5AjBOwv7zrclMYjU17WOHpwGuSC3aTiz20
YITYVPCHZRZzWbfWBP5WKbjNgka8Ml7BCAjh1KkPqQp+Qfh6MxvKBtyOpaZo9b+w
v4pis5DkHcSxPJNM2OZeN0UnNMAe2JjS94fEb/JPd8x2UcI8lNX5lSftySUp9S1u
eTIqyhBx6oO0ccs9REuKyI/ViCb208d483nzD8i+79LhoKABeAj53g3iWvZO3Fvm
JRwdPZgdO603LaRHs+a8C7uTtIYBK638p8cKfz6HO8aEfNyoFuRi5LyfYQZMQ9YK
YETnCHiSLebI+xuPkYSNLfbRWD5kwoab2pIwxghcQpNauL+2dtQ28sHDRPEJI0ta
HHYd9cEdtmvreuH3GR/OJkdidtkYzr3hBWNFonf27aqFUnbmrxUtGkt41oih1Oso
bo4GnGRZP6sXWReraInwRjK4zpRSGv8Z4h4O0YyZHr0x3j9H9cOMM4OBI1GXH8KN
TcshIuL2oNmACFgmLQb4Ffw3ZOKLTmI/SD9XfWvIp3tdGKW33l0=
=Y6/w
-----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.