The PWG Finisher MIB meeting took place Friday, 7/10/98, in Monterey, CA. Some final clarifications were reviewed and a few new terms and attributes were introduced. Special thanks to Duplo USA for sending assisting with their Finisher expertise in Monterey. July was the final anticipated full working session for the Finisher MIB project. The MIB is now in PWG "last call" period (expires August 7).
Upon review and participation in the development of the standard Finisher MIB, Duplo has suggested that the PWG form a new working group to address the creation of a standard printer-to-finisher interface and data model, based on their observation that such an interface could easily share the finisher MIB data model. We have requested time during the Tuesday evening MIB session, (August 18, in Toronto) for a BOF.
Ron Bergman - Dataproducts (Editor)
Lee Farrell - Canon
Jennifer Gattis - Duplo USA
Tom Hastings - Xerox
Harry Lewis - IBM (Chair, Secretary)
Ken Oakeson - HP
Kevin Palmer - Duplo USA
Jeff Tsai - Duplo USA
A dilemma was pointed out in that the Attribute Group is mandatory but it might be possible to have no attributes supported. Rather than create a list of cases for this, we simply mandates that one attribute, the name of the device (attribute 3) is mandatory. We did not specify what the default name must be.
Pg-17 - the MIB ARC. We want the Finisher MIB to "live" under the printer MIB ARC as a PWG standard (MIB-243). Ira had changes this to 9999 for the purposes of compiling with the SMIC compiler. We need to develop a compromise version of the MIB that compiles under SMIC, MOSEY , Net+, HP OpenView, NetView and as many compilers as possible, yet still has the proper OID tree. (Ron Bergman action item).
If a compromise MIB cannot be developed then a FAQ will be started indicating the nuances of compiling under various compilers. Anyone finding tit necessary to make minor adjustments to MIBs to accommodate specific compilers should contribute to this FAQ..
FIN supply media input name, description, type etc. Change from display string to octet string. Display string is limited to US ASCII only so it cannot be internationalized but Octet string has the disadvantage that the application developer can't tell, by looking at the string, whether to interpret it as TEXT or just a string of Hex.
Add generic TRIM definition for multisided trimmers which are too flexible to be described by named configuration.
Change existing trim definition to the proper terminology - "Face Trim".
Add device type "Stacker" and create TC's to represent Straight, Offset and CrissCross. Add Stacker specific attributes for stackOffset and stackRotation.
Add the term "Gutter Trim" which is a means of separating adjacent images while eliminating the "gutter" (or white space) between them, resulting in two "full bleed" sheets.
Add device Types "Cover Feed Station" and "Sheet Rotator" with syntax Present/On/Off