Hi Bill,
Of course, I meant to replace just the preface (that is,
the actual text labelled section 4), not 4.1 to 4.x.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
-----Original Message-----
From: William A Wagner [mailto:wamwagner@comcast.net]
Sent: Monday, March 21, 2005 8:45 PM
To: 'McDonald, Ira'; wims@pwg.org
Subject: RE: WIMS> Edits for WIMS Counter spec
Ira,
I question whether you mean to replace all of section 4, which includes the
tables defining the counters, of just the preface that I recently added.
Bill Wagner
-----Original Message-----
From: owner-wims@pwg.org [mailto:owner-wims@pwg.org] On Behalf Of McDonald,
Ira
Sent: Monday, March 21, 2005 5:51 PM
To: 'wims@pwg.org'
Subject: WIMS> Edits for WIMS Counter spec
Hi Bill and Harry, Monday (21 March 2005)
Per our review of the WIMS Imaging System Counter spec today, here are
some suggested edits:
(1) In section 3.1, Figure 1, "Printer" should get a footnote:
The PWG SM/1.0 term "Printer" above is a legacy term from IPP/1.1.
The preferred term for this Imaging Service is "Print Service" (see
section 3.2 and Figure 2 below).
[Rationale: WIMS Type schema and Counter MIB currently use "Print".
We agreed to change "Copier" to "Copy" for the service function and
should do the same for "Printer" (and change throughout the spec).
Don't add this text to the Counter spec.]
(2) In section 3.2, Figure 2 and section 3.3, Figure 3, change the term
"Printer" to "Print".
[See above for rationale - don't add this text to the Counter spec.]
(3) Entirely replace existing section 4 with:
This section identifies all of the standard Counter elements, each of
which is is hierarchically named as follows:
C1. Object: This first level identifies the object (System or Service -
see Figure 3) that the contains each Counter element (see 'Simplified
Notation' below). Each System Totals counter is contained in a System
object and is at the same logical level as the corresponding specific
Service counters. Each System Totals counter aggregates across all the
corresponding specific Service counters (see Figure 2).
C2. Application: This second level identifies the application purpose
(Monitoring, Availability, Media Used, or Job - see Figure 4) for each
Counter element. Job counters are further partitioned into DataStream,
Auxiliary, Maintenance, Waste, and Unknown (a virtual counter).
C3. Unit: This third level identfies the unit (e.g., Impressions or
Images) for each Counter element and may be further qualified (e.g.,
BlankImpressions or FullColorImages).
Simplified Notation: This specification uses a short notation. For
example, 'Copy.Job.Impressions' is short for the XML schema qualified
name 'CopyService.CopyStatus.CopyCounters.Job.Impressions' or else
'Service.ServiceStatus.ServiceCounters.Job.Impressions' (depending on
the structure used when adding Imaging Services to [PWG-SM]). Although
the first XML schema structure appears to be simpler, it would lead to a
vastly larger XML schema set and would be error-prone during XML schema
maintenance.
Persistence: Counter elements may persist as follows:
P1. Lifetime - since installation of imaging system or service
(see 'prtMarkerLifeCount' in IETF Printer MIB v2 [RFC3805]).
P2. PowerOn - since last power cycle of imaging system or service
(see 'prtMarkerPowerOnCount' in IETF Printer MIB v2 [RFC3805]).
P3. Reset - since last administrative reset of imaging counter
(e.g., a software reset by an accounting application).
Conformance: Conforming Imaging Systems MUST implement System Totals
counters with Lifetime persistence. Conforming Imaging Systems SHOULD
implement specific Service counters with Lifetime persistence.
Comments?
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
This archive was generated by hypermail 2b29 : Tue Mar 22 2005 - 07:56:03 EST