[MFD] Re: MFD Schema updated [keep Email services]

[MFD] Re: MFD Schema updated [keep Email services]

[MFD] Re: MFD Schema updated [keep Email services]

Zehler, Peter Peter.Zehler at xerox.com
Mon Jul 20 18:08:13 UTC 2009


Ira,
I will add them back in before posting the updated schema to the MFD site.
Pete

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 


-----Original Message-----
From: mfd-bounces at pwg.org [mailto:mfd-bounces at pwg.org] On Behalf Of Ira McDonald
Sent: Monday, July 20, 2009 2:00 PM
To: Zehler, Peter; Ira McDonald
Cc: mfd at pwg.org
Subject: [MFD] Re: MFD Schema updated [keep Email services]

Hi Pete,

The services Email<In/Out> in the PWG Job Monitoring MIB
(RFC 2707) were for first class Email services - NOT for the
separate Fax service (SMTP transport or otherwise).

The Samsung prototype of Counter MIB had an EmailOut
service used by the composed services ScanToEmail and
TransformToEmail - it supported *all*  document formats
- NOT just image formats like Fax.

Samsung intends to use EmailOut (and probably EmailIn)
in PWG Counter MIB implementations.

Samsung would to keep Email<In/Out> as distinct basic
MFD services in the XML schema and model, please.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic at gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434



On Mon, Jul 20, 2009 at 1:27 PM, Zehler, Peter<Peter.Zehler at xerox.com> wrote:
> My comments are inline below.
>
> Peter Zehler
>
>
> -----Original Message-----
> From: William Wagner [mailto:wamwagner at comcast.net]
> Sent: Thursday, July 16, 2009 4:48 PM
> Subject: RE: MFD Schema updated
>
> ...snip...
>
> 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?
> <PZ>My assumption is that these have been collapsed into the Fax
> services and are simply vestigial code.  I will remove them in the next
> version of the schema.  We can add them back in if there is a need for
> them I am overlooking.</PZ>
>
> I would appreciate some comments and clarifications.
>
> Thanks,
>
> Bill Wagner
>
>
> -----Original Message-----
> 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
>    ImagingSupply
>    - 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
>
> Cheers,
> - Ira
>
> Ira McDonald (Musician / Software Architect)
> Chair - Linux Foundation Open Printing WG
> Blue Roof Music/High North Inc
> email: blueroofmusic at gmail.com
> winter:
>  579 Park Place  Saline, MI  48176
>  734-944-0094
> summer:
>  PO Box 221  Grand Marais, MI 49839
>  906-494-2434
>
>
>
> On Fri, Jul 10, 2009 at 2:13 PM, Zehler, Peter<Peter.Zehler at xerox.com>
> wrote:
>> 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.

_______________________________________________
mfd mailing list
mfd at pwg.org
https://www.pwg.org/mailman/listinfo/mfd

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.




More information about the mfd mailing list