I have been working on an additional section to the Implementer's Guide
specifically for guidelines around implementation of an Admin client and its
usage. I've come across a couple of issues that either may already have
easy answers or is something that should be discussed.
Issue 1a - Regarding IPP-IIG Section 3.1.2.3.1 (Checking for conflicting Job
Template attribute values), is it allowable for an administrator to define
her own attribute/value conflicts? For instance, a printer object
implementation ALLOWS transparencies to be stapled, but the administrator
would prefer this to be NOT allowed on her particular printer. An
additional admin (Set 2) operation or printer attribute collection may easy
provide the functionality for this.
Issue 1b - If Issue 1a is allowable, would an admin-defined conflict return
the 'client-error-conflicting-attributes' status code, or does another
status code need to be created?
Issue 2 - If an administrator is defining her own type 3 attribute values
according to IPP-MOD Section 6.1, is there a 'private' version-number for
the printer object so that her admin client can know that this attribute
value can be supported? For instance, Xerox creates a private job-sheets
attribute. How does an admin client know that this value can be added to
the 'job-sheets-supported' attribute? Can a third field be added to the
'version-number' for private versioning, or does each organization that
extends IPP create their own mechanism for this (e.g.. invent a new
attribute 'Xerox-version-number')?
Issue 3 - If an administrator added her own attributes according to IPP-MOD
Section 6.2, but they require some conflict checking with other IPP
attributes, how is this accomplished? (Similar to Issue 1a)
Thanks!
Mike
~~~~~~~~~~~~~~~~~~~~~~~~~
Michael D. Shepherd
*8*222-2338 / (716)422-2338
* Location: 0128-51E
Michael.Shepherd at crt.xerox.com <mailto:Michael.Shepherd at crt.xerox.com>
~~~~~~~~~~~~~~~~~~~~~~~~~