Hi Mike,
Coming back to the registrations, for now HP Inc. would like to register these, with names structured as per your request:
Attributes (attribute syntax)
Keyword Attribute Value Reference
-------------------------------------------------------- --------------
media (type2 keyword | name(MAX)) [RFC8011]
na_arch-e1_32x40in [HP20210302]
oe_photo-10x12_10x12in [HP20210302]
oe_photo-10x15_10x15in [HP20210302]
oe_photo-14x18_14x18in [HP20210302]
oe_photo-16x20_16x20in [HP20210302]
oe_photo-20x24_20x24in [HP20210302]
oe_photo-22x28_22x28in [HP20210302]
oe_photo-24x30_24x30in [HP20210302]
om_photo-300x400_300x400mm [HP20210302]
om_photo-300x450_300x450mm [HP20210302]
om_photo-350x460_350x460mm [HP20210302]
om_photo-400x600_400x600mm [HP20210302]
om_photo-500x760_500x760mm [HP20210302]
om_photo-600x900_600x900mm [HP20210302]
media-supported (1setOf (type2 keyword | name(MAX))) [RFC8011]
< all name values > [RFC8011]
We can perhaps discuss at today's IPP WG meeting if these are acceptable for registration.
Smith
/**
Smith Kennedy
HP Inc.
*/
> On Mar 2, 2021, at 1:13 PM, Michael Sweet <msweet at msweet.org> wrote:
>> Smith,
>> At first blush I see some duplicated sizes from the registry:
>> na_arch-c_18x24in
> na_arch-d_24x36in
>> and the MSN2 spec doesn't allow those...
>> Also, while I appreciate keeping the na_WIDTHxHEIGHT_WIDTHxHEIGHTin form for those dimensional sizes, if they are primarily for photo/art printing I'd like to see a 'photo' prefix in the name portion, e.g.:
>> oe_photo-16x20_16x20in
>> Similarly, the om_photo sizes should include the dimensions if there is no corresponding well-known name:
>> om_photo-300x400_300x400mm
>>> > On Mar 2, 2021, at 12:29 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <ipp at pwg.org> wrote:
> >
> > Greetings,
> >
> > HP Inc. is requesting the registration of additional keywords for the “media” attribute [STD92] for some standard sizes that aren’t yet registered. Here is the registration template and the keywords to be added:
> >
> > Attributes (attribute syntax)
> > Keyword Attribute Value Reference
> > -------------------------------------------------------- --------------
> > media (type2 keyword | name(MAX)) [RFC8011]
> > na_arch-e1_32x40in [HP20210302]
> > na_super-c_18x24in [HP20210302]
> > na_super-d_24x36in [HP20210302]
> > oe_10x12_10x12in [HP20210302]
> > oe_10x15_10x15in [HP20210302]
> > oe_14x18_14x18in [HP20210302]
> > oe_16x20_16x20in [HP20210302]
> > oe_20x24_20x24in [HP20210302]
> > oe_22x28_22x28in [HP20210302]
> > oe_24x30_24x30in [HP20210302]
> > om_photo_300x400mm [HP20210302]
> > om_photo_300x450mm [HP20210302]
> > om_photo_350x460mm [HP20210302]
> > om_photo_400x600mm [HP20210302]
> > om_photo_500x760mm [HP20210302]
> > om_photo_600x900mm [HP20210302]
> > media-supported (1setOf (type2 keyword | name(MAX))) [RFC8011]
> > < all name values > [RFC8011]
> >
> > Let me know if there are any issues.
> >
> > Cheers,
> > Smith
> >
> > /**
> > Smith Kennedy
> > HP Inc.
> > */
> >
> >
> >
> > _______________________________________________
> > ipp mailing list
> > ipp at pwg.org> > https://www.pwg.org/mailman/listinfo/ipp <https://www.pwg.org/mailman/listinfo/ipp>
>> ________________________
> Michael Sweet
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20210311/f609ff3c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://www.pwg.org/pipermail/ipp/attachments/20210311/f609ff3c/attachment.sig>