attachment
<br><font size=2 face="sans-serif">Ira,</font>
<br>
<br><font size=2 face="sans-serif">Thanks for the draft for section 3.1.
Just in case we have time to go over the text provided by you, I
have added it into the last updated Scan Service draft (with date 20070918).
I also did some editorial reformating of the list of processing flow steps
and design requirements, so that the way they are listed are more consistent.
The latest updated Scan Service draft is available as :</font>
<br>
<br><font size=2 face="sans-serif">The version with revision marks:</font>
<br><font size=2 face="sans-serif">ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdscan10-20070921_rev.pdf</font>
<br><font size=2 face="sans-serif">and</font>
<br><font size=2 face="sans-serif">ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdscan10-20070921_rev.doc</font>
<br>
<br><font size=2 face="sans-serif">The version without revision marks:</font>
<br><font size=2 face="sans-serif">ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdscan10-20070921.pdf</font>
<br><font size=2 face="sans-serif">and</font>
<br><font size=2 face="sans-serif">ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdscan10-20070921.doc</font>
<br>
<br><font size=2 face="sans-serif">-Nancy</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"McDonald, Ira"
<imcdonald@sharplabs.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: owner-mfd@pwg.org</font>
<p><font size=1 face="sans-serif">09/20/2007 06:09 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif"><mfd@pwg.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">MFD> Rationale for Scan Service Interface</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Hi,<br>
</tt></font>
<br><font size=2><tt>Nancy - for inclusion as section 3.1 in your next
draft<br>
of SSI after the Montreal meeting (note slightly changed<br>
title of section). Modelled on the PSI and Counter MIB<br>
rationale sections.<br>
</tt></font>
<br><font size=2><tt>Cheers,<br>
- Ira<br>
</tt></font>
<br><font size=2><tt>Ira McDonald (Musician / Software Architect)<br>
Chair - Linux Foundation Open Printing WG<br>
Blue Roof Music / High North Inc<br>
PO Box 221 Grand Marais, MI 49839<br>
phone: +1-906-494-2434<br>
email: imcdonald@sharplabs.com<br>
</tt></font>
<br><font size=2><tt>------------------------------------------------<br>
3.1 Rationale for Scan Service Interface<br>
</tt></font>
<br><font size=2><tt>The PWG Imaging System Counters specification [PWG5106.1]
defines:<br>
</tt></font>
<br><font size=2><tt>(a) A standard set of Imaging Services for Imaging
Systems.<br>
</tt></font>
<br><font size=2><tt>(b) A set of use models for monitoring and billing,
management,<br>
and accounting for these Imaging Services.</tt></font>
<br>
<br><font size=2><tt>(c) A set of abstract counters for these Imaging Services.<br>
requirements.</tt></font>
<br>
<br><font size=2><tt>(d) A set of conformance requirements for implementations
of these<br>
abstract counters in Imaging Systems.</tt></font>
<br>
<br><font size=2><tt>The IPP/1.1 Model and Semantics [RFC2911] and the
PWG Print Service<br>
Interface [PWG5104.2] each define:<br>
</tt></font>
<br><font size=2><tt>(a) Models of Print Services, Print Devices, and Print
Jobs.<br>
</tt></font>
<br><font size=2><tt>(b) Sets of abstract operations and elements for Print
Services.<br>
</tt></font>
<br><font size=2><tt>(c) Sets of abstract operations and elements for Print
Jobs.<br>
</tt></font>
<br><font size=2><tt>(d) Sets of conformance requirements for implementations
of these<br>
abstract operations and elements in Print Services and Print<br>
Jobs.</tt></font>
<br>
<br><font size=2><tt>The IPP/1.1 Encoding and Transport [RFC2910] and the
PWG Print Service<br>
Interface [PWG5104.2] each define:<br>
</tt></font>
<br><font size=2><tt>(a) Concrete protocol stacks for IPP/1.1 (HTTP over
TLS) and PSI/1.0<br>
(SOAP over HTTP).</tt></font>
<br>
<br><font size=2><tt>(b) Concrete mappings of operations and elements for
Print Services.<br>
</tt></font>
<br><font size=2><tt>(c) Concrete mappings of operations and elements for
Print Jobs.<br>
Jobs.</tt></font>
<br>
<br><font size=2><tt>(d) Sets of conformance requirements for implementations
of these<br>
concrete operations and elements in Print Services.</tt></font>
<br>
<br><font size=2><tt>In order to support equivalent functionality for scanning
in network<br>
multifunction devices, there is a clear need to develop a semantic<br>
model and a set of abstract operations and elements for Scan Services<br>
and Scan Jobs.<br>
</tt></font>
<br><font size=2><tt>In order to implement these abstract operations and
elements for Scan<br>
Services and Scan Jobs, there is a clear need to map them onto a<br>
concrete protocol stack to link Scan Clients and Scan Services.<br>
</tt></font>
<br><font size=2><tt>Since the current state-of-the-art Internet network
application protocol<br>
stack is the Web Services stack (i.e., WSDL-defined SOAP over HTTP,<br>
using standard Web Services modules for security, addressing, etc.),<br>
there is a clear need to define a binding of these abstract operations<br>
and elements for Scan Services and Scan Jobs onto concrete SOAP messages<br>
and XML Schema instances.<br>
</tt></font>
<br><font size=2><tt>No virus found in this outgoing message.<br>
Checked by AVG Free Edition.<br>
Version: 7.5.487 / Virus Database: 269.13.27/1020 - Release Date: 9/20/2007
12:07 PM<br>
</tt></font>
<br>
<br>