Re: Minutes posted from today's meeting
"Kennedy, Smith \(Wireless & IPP Standards\) via ipp" <[email protected]>
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <[email protected]> |
Hi again,
I guess one other way this might be conveyed is to add a "job-max-pages-per-set-supported" member to "finishings-col" and add that as an additional member of "finishings-col-ready: / "finishings-col-database" collections, so that it can be used by all finishings operations?
finishings-col-database=
{
finishing-template='fold-accordion'
media-size-name="iso_a4_210x297mm"
job-max-pages-per-set-supported=1
folding=
{
folding-direction='inward'
folding-location=7425
folding-reference-edge='top'
},
{
folding-direction='inward'
folding-location=22275
folding-reference-edge='top'
},
{
folding-direction='outward'
folding-location=14850
folding-reference-edge='top'
}
}
Smith
> On Aug 3, 2021, at 10:26 AM, Kennedy, Smith (Wireless & IPP Standards) via ipp <[email protected]> wrote:
>
> Hi Mike,
>
>> On Aug 3, 2021, at 8:20 AM, Michael Sweet <[email protected]> wrote:
>>
>> Smith,
>>
>>> On Aug 2, 2021, at 5:53 PM, Kennedy, Smith (Wireless & IPP Standards) <[email protected] <mailto:[email protected]>> wrote:
>>>
>>> Hi Mike,
>>>
>>> You have in these minutes this statement about section 5.2.6 "folding (1setOf collection)":
>>>
>>> ⁃ Add something to talk about folding applying to the set, except as noted (e.g. poster fold is normally done to individual sheets)
>>>
>>> I'm not sure what to do about this because the . Are you saying that the size of the Set or how many Media Sheets should be folded may depend on the type of the fold? So if the Client sends a 4 page document and supplies "finishing" = 'fold-poster', the Printer might fold every Media Sheet, but if the Client instead supplies "finishing" = 'fold-half' the Printer may instead fold all 4 pages together?
>>>
>>> Maybe we need to add a "folding-when"?
>>
>>
>> So the issue here is that some kinds of folds can be applied per-sheet or per-set, but some can *only* be applied per set (fold-double-gate, fold-parallel), others can *only* be applied per sheet (fold-half-z, fold-poster), and the rest can be applied either way depending on the amount of folding done and output bin/tray.
>>
>> Look at figure 1's fold images to get a visual sense of this - folds along both axis need to be applied per-sheet, while overlapping folds need to be applied per-set. So this is definitely implementation/process-specific, but we want folding to only express the intent.
>
> As you know well, we have two needs: describing a folding operation to a Client, and describing a custom folding operation to the Printer.
>
> In both cases, a “folding-when” would be useful. The Client needs to know the range of options it could use (1 or more than 1 option). And if there is the possibility of a choice, the Client needs a member to convey that choice to the Printer.
>
> Expressing this via the current finishings-col is going to be a little bit awkward because folding is expressed as an ordered sequence of folding collections. Maybe a”folding-when” as a member of the first “folding” collection? Or as a separate peer to “folding”?
>
> _______________________________________________
> ipp mailing list
> [email protected]
> https://www.pwg.org/mailman/listinfo/ipp
_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAmEMaK0ACgkQqskbKLDW 1N3qtg/+Iw2PobAhgni9eV7bCPmvr+qpqDkqp046gztPwi7HxDWkuS/wHPGe39vn R1W1dhqoiC2M6RwQ19w52igFJkwOQgZB0zi66q26GFI0WWaMo6FgYx2RhCWY3eqW YNCksBJFt+i7s+tVnR1p5bSVWuYZCHkNQ/ouS5mvHyZOetz3Ay7Lln06oafbzaz+ 7jNhZTF9KmQ+a/dIiONT8ipA/aAOU5Enu7Rf3wOlUgQV6yo76VkcTZ4/Il+cDJoP oFNScEXbNS7O/xfhwZd4Nn0h4aRzwiIt4bv6qcRQb0GfSXlhs+v+3tIceZWrbOBF 4rntzSXttqhMLj/lLl6YzHypBaQgnE1OYIDl1QCXEwRY/ahGsokbJoLQhLe984je Ff/VCNeammlkYmDVJdeoJjTvgucY0h76U9tZA43F1nx7mEwyjuuIkdAzzkkYTPV4 9Jy5LtNXd0ceXqe/nTs+lYVtmlqy4tN0FqtzL/kMprV92vCi9GsRn9Ipq8eoGTT4 vL0PeIAC79Wm8MPc1+yM8v/mizEukUajhpctOh828k4Xy/F5OrCwEomwqbeUeB0o JM/1BKhBWOT6IZnBCsV6GGaio7P+OMvtXKsDpDwNZZtNHyjJBfJy8WP0Xl2le9HL FK0qQ72WkDf/Rcb5wFTu/vI9a1YcqLYaXSCSVhwulI2TnqmO4ZY= =BVG4 -----END PGP SIGNATURE-----