Although I think the schema changes make sense, they do play havoc with the
MFD Overall document, and I suspect that there may be further changes. At
any rate, a few more questions in working with the current schema.
1. The schema appears to show 0..1 instances of each of the Server's
constituent elements. I thought that a Server must have one and no more than
one System. And is an MFD an MFD if it does not include at least one
2. With the absorption of Subunits and Available Resources into the System,
is the "Relationships" Diagram (Fig 3 in the current overall MFD document
but copped from the Scan Service spec) valid? This diagram shows Services
and Subunits on the same level, but does not show the System.
3. Would not each service need a Configuration element? Why do EmailIn,
EmailOut, FaxIn not include it?
4. I do not understand why FaxOut and Scan do not include CapabilitiesReady
while all other services (except Resource) do include it.
5. EmailIn and EmailOut are listed as services in the Schema, but I don't
recall discussing what they are, and they did not appear on Figure 1 - MFD
Services with Primary Interfaces when we first worked up that diagram. What
are these services? We have described them as facsimile services using
email (but not IETF fax, which does use SMTP). And if they are fax services,
calling them email certainly causes confusion. And what is distinctive about
such services so that we cannot collapse them into FaxIn and FaxOut, as we
did will all of the other facsimile services?
I would appreciate some comments and clarifications.
From: Ira McDonald [mailto:blueroofmusic at gmail.com]
Sent: Wednesday, July 15, 2009 4:45 PM
To: Zehler, Peter; Ira McDonald; mfd at pwg.org
Cc: William Wagner
Subject: Re: MFD Schema updated
Hi Pete, Wednesday (15 July 2009)
Here are my comments on 10 July SM/2.0 schema:
(1) I like the generalization of Printer[Status/Description] elements
reflected in PwgDeprecated.xsd
- I agree with Bill that there may yet be more to generalize
- Note this boils down to applying IPP to MFD services - Good Thing
(2) I like the rework of System
(3) I like the rework of NaturalLanguage and Charset
- IETF just approved RFC 4646bis, so a new RFC reference this fall
(4) In SubunitStates please capitalize (for consistency):
coverOpen/Closed, interlockOpen/Closed, and other
(5) In SubunitStatus type definition and numerous other places in schema
- SPY has jumbled XML comments randomly out-of-line
(6) StorageDataEncryption should be StorageDataEncryptionIsEnabled,
since it's a boolean not an enum (w/ default to false)
- see lines 59 to 65 in Subunits.xsd
(7) MediaPathStatus should include SheetsCompleted like
ScanMediaPathStatus (though the property's not in Printer MIB)
- What are the semantics?
- Are these Lifetime or PowerOn counters?
(8) FinisherSupply (from Finisher MIB) and
MarkerSupply (from Printer MIB) should probably be combined into
- in recent MIB walks, many manufacturers list FinisherSupply stuff
in prtMarkerSuppliesTable (where types like 'staple' are defined)
- the advantage of using the common table (among others) is that
Finisher supplies show up in HP WJA and other fleet mgmt tools
(9) I like the current ImagingJob and ImagingJobTicket classes
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic at gmail.com
579 Park Place Saline, MI 48176
PO Box 221 Grand Marais, MI 49839
On Fri, Jul 10, 2009 at 2:13 PM, Zehler, Peter<Peter.Zehler at xerox.com>
> I updated the MFD site with the schema version I last sent to you.
>> Peter Zehler
>> Xerox Research Center Webster
> Email: Peter.Zehler at Xerox.com> Voice: (585) 265-8755
> FAX: (585) 265-7441
> US Mail: Peter Zehler
> Xerox Corp.
> 800 Phillips Rd.
> M/S 128-25E
> Webster NY, 14580-9701
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.