attachment
<div dir="ltr"><div><div><div>Hi Smith,<br><br></div>A precedent for use of "_" (underscore) to separate base and<br></div>extension names is section 3.4 Derived Media Type Names of<br></div>MSN2 (PWG5101.1-2013) [1], which begins with the following:<br><br>"Media Type Names MAY be locally extended from existing standard, <br>vendor, or custom media names by prefixing the names with the string <br>"derived-" and appending the existing name with a leading underscore, <br>e.g., "derived-xyz-photo_photographic-glossy". The format is defined <br>by the following ABNF [STD68]:<br><br> <span style="font-family:monospace,monospace">derived-type-name = "derived-" base-name "_"<br> ( base-name / vendor-type-name /<br> custom-type-name )</span><br><div class="gmail_extra"><br></div><div class="gmail_extra">Cheers,<br></div><div class="gmail_extra">- Ira<br>[1] <a href="ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn20-20130328-5101.1.pdf">ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn20-20130328-5101.1.pdf</a><br clear="all"></div><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><br><br>Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Jul 12, 2016 at 3:12 PM, Kennedy, Smith (Wireless Architect) <span dir="ltr"><<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Greetings,<br>
<br>
I'm going to echo back the plan we discussed today in the IPP WG. From what I took to understand, the plan was like so:<br>
<br>
- No new enum value 'punch-triohalning-top' etc. to be defined for "finishings"<br>
- Define a keyword / name "variant extension convention" for "finishing-template" names to allow variants to be created for defined keywords<br>
<br>
Thus, to support Swedish Trio Binder (Triohålning) punch pattern, the Printer would list an entry in "finishings-col-database" and possibly "finishings-col-ready" where "finishing-template" would be set to something like 'punch-quad-left_trio-binder', with an appropriate localized string corresponding to that, and with all the "finishings-col" member attributes describing the appropriate punch locations. Below is an example of how the Trio Binder and European 4 ring patterns would be represented in discrete "finishings-col-ready" listings:<br>
<br>
finishings-col-ready=<br>
{<br>
finishing-template=punch-quad-left_trio-binder<br>
media-size-name=iso_a4_210x297mm<br>
media-size={x-dimension=21000 y-dimension=29700}<br>
punching=<br>
{<br>
punching-reference-edge=left,<br>
punching-offset=1200<br>
punching-locations=9250,11350,14850,16950<br>
}<br>
},<br>
{<br>
finishing-template=punch-quad-left_a4-european-4-ring<br>
media-size-name=iso_a4_210x297mm<br>
media-size={x-dimension=21000 y-dimension=29700}<br>
punching=<br>
{<br>
punching-reference-edge=left,<br>
punching-offset=1200<br>
punching-locations=2850,10850,18850,26850<br>
}<br>
},<br>
<br>
<br>
The naming convention proposed is to separate the "keyword" or "base name" from the "subtype name" with an underscore. Reading even the latest revision of 2911 (<a href="https://tools.ietf.org/html/draft-sweet-rfc2911bis-09" rel="noreferrer" target="_blank">https://tools.ietf.org/html/draft-sweet-rfc2911bis-09</a>), it isn't clear to me that there is precedent for this convention. If such conventions are used in other contexts, please share so that I can leverage that / those conventions in my updates to Finishings 2.1.<br>
<span class="im"><br>
Cheers,<br>
<br>
Smith<br>
<br>
/**<br>
Smith Kennedy<br>
Wireless Architect - Client Software - IPG-PPS<br>
Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF<br>
Chair, IEEE ISTO Printer Working Group<br>
HP Inc.<br>
*/<br>
<br>
<br>
<br>
</span><div class=""><div class="h5">> On 2016-07-11, at 9:56 AM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com">smith.kennedy@hp.com</a>> wrote:<br>
><br>
><br>
>> On 2016-07-07, at 7:27 AM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:<br>
>><br>
>> Smith,<br>
>><br>
>>> On Jul 6, 2016, at 1:11 PM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com">smith.kennedy@hp.com</a>> wrote:<br>
>>><br>
>>> Greetings,<br>
>>><br>
>>> HP Inc. requests the addition of 4 "finishings" keywords to support the Swedish "Triohålning" de-facto hole punch standard, as described here:<br>
>>><br>
>>> <a href="https://en.wikipedia.org/wiki/Hole_punch#Sweden" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Hole_punch#Sweden</a> <<a href="https://en.wikipedia.org/wiki/Hole_punch#Sweden" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Hole_punch#Sweden</a>><br>
>>> <a href="https://sv.wikipedia.org/wiki/H%C3%A5lslagsapparat#Svensk_trioh.C3.A5lning" rel="noreferrer" target="_blank">https://sv.wikipedia.org/wiki/Hålslagsapparat#Svensk_trioh.C3.A5lning</a> <<a href="https://sv.wikipedia.org/wiki/H%C3%A5lslagsapparat#Svensk_trioh.C3.A5lning" rel="noreferrer" target="_blank">https://sv.wikipedia.org/wiki/H%C3%A5lslagsapparat#Svensk_trioh.C3.A5lning</a>><br>
>>><br>
>>> We propose the addition of 4 keywords:<br>
>>><br>
>>> "punch-triohalning-top"<br>
>>> "punch-triohalning-left"<br>
>>> "punch-triohalning-right"<br>
>>> "punch-triohalning-bottom"<br>
>>><br>
>>> Even though the "-top" and "-bottom" are likely not necessary for standard letter-type (i.e. A4) media sizes, it is conceivable that a user might want this punch pattern on the short edge of an A3 or larger media size, so that is why I'm suggesting we define these 4.<br>
>><br>
>> I have a few comments about this:<br>
>><br>
>> 1. "finishings" is an enum attribute, "finishing-template" is a keyword (or name) attribute. I assume you want both registered?<br>
><br>
> That is correct - apologies for not being precise. (And if we don't have anything in place currently to make sure that the set of enum values and keywords match, we probably ought to, since they are strongly related.)<br>
><br>
>><br>
>> 2. Keywords are supposed to be US English; looks like "trio binder" is the English equivalent of triohålning.<br>
>><br>
>> 3. We already have punch-quad-{bottom,left,right,top}, and there are numerous 4-hole punch patterns (four specifically listed on the linked page). In the past we have opted for the enum/keyword to specify an implementation-defined hole pattern, with "finishings-col" providing the explicit control, so I am not super happy about going down this road (I count 15 different hole patterns for 2-7 hole punching on the wikipedia page alone).<br>
><br>
> Let me preface by saying I would have preferred to only pursue a solution that uses finishings-col, but unfortunately there seem to be quite a few laggards in this space that still depend on "finishings". When "finishings-col" is employed, you can give the "finishings-template" value any value you want, because it becomes simply an identifier to be used to look up a string out of the strings catalog.<br>
><br>
>><br>
>> 4. From a practical standpoint, will finishers needing this support arbitrary 4-hole punch patterns, or will this be specific to a finisher that is sold/marketed solely in Sweden and nearby countries? If the latter, it seems like keeping the current (generic) punch-quad-xxx is sufficient for "finishings", with "finishings-col" providing explicit intent.<br>
><br>
> I understand and sympathize with your worry about needless enum / keyword definitions. But it struck me that the current keywords definitions ("punch-quad-left") are really ambiguous as far as intent. Is that not a concern?<br>
><br>
><br>
</div></div><div class=""><div class="h5">> _______________________________________________<br>
> ipp mailing list<br>
> <a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
> <a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br>
</div></div><br>_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br></blockquote></div><br></div></div>