[For discussion during today's WG concall]
All,
One of the decisions at the last 3D concall was to use collections for subunit status information. What follows is a general template for all of these attributes, which we will discuss before I apply it to the various subunit attributes in the current draft.
....
"printer-<subunitname>-col (1setOf collection)"
This CONDITIONALLY REQUIRED Printer Status attribute provides the status of the <subunitname> sub-units that are managed by the Printer. Printers that support <subunitname> sub-units MUST support this attribute.
"<subunitname>-info (text)"
This member attribute provides a human-readable description for the sub-unit.
"<subunitname>-info-uri (uri)"
This member attribute provides a web page for the sub-unit.
"<subunitname>-name (name)"
This member attribute provides a human-readable name for the sub-unit.
"<subunitname>-make-and-model (text)"
This member attribute provides a human-readable make and model for the sub-unit.
"<subunitname>-security (boolean)"
This member attribute indicates whether the sub-unit has some security associated with it.
"<subunitname>-serial-number (text)"
This member attribute provides a human-readable serial number for the sub-unit.
"<subunitname>-state (type1 enum)"
This member attribute provides the current state of the sub-unit. Values are:
'3' ('idle'): The sub-unit is available and either idle or in standby mode.
'4' ('processing'): The sub-unit is available and either active or busy.
'5' ('stopped'): The sub-unit is unavailable.
Additional information concerning the state can be found in the "printer-state-reasons" Printer Status attribute [RFC2911].
"<subunitname>-version (text)"
This member attribute provides a human-readable version for the sub-unit.
_________________________________________________________
Michael Sweet, Senior Printing System Engineer