attachment-0001
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Impact;
panose-1:2 11 8 6 3 9 2 5 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
text-indent:-.25in;
mso-list:l0 level1 lfo2;
font-size:10.0pt;
font-family:"Arial","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:926157213;
mso-list-type:hybrid;
mso-list-template-ids:347914760 -2026857294 -27771788 -1873506346 1925994646 -924546762 -2098694348 1736204798 -1433788734 1730052778;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-style-link:"List Paragraph";
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>My comments are inline below.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-family:"Impact","sans-serif";color:navy'>Peter
Zehler</span><span style='color:#1F497D'><br>
<br>
</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:navy'>Xerox Research Center Webster<br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Email: Peter.Zehler@Xerox.com</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Voice: (585) 265-8755</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>FAX: (585) 265-7441</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>US Mail: Peter Zehler</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Xerox Corp.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>800 Phillips Rd.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>M/S 128-25E</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Webster NY, 14580-9701</span><span style='color:#1F497D'> </span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> mfd-bounces@pwg.org
[mailto:mfd-bounces@pwg.org] <b>On Behalf Of </b>William Wagner<br>
<b>Sent:</b> Tuesday, July 07, 2009 12:31 PM<br>
<b>To:</b> mfd@pwg.org<br>
<b>Subject:</b> [MFD] MFD Schema questions<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>I am confused
by what appears to be a lack of parallelism in the schema, although with the
implications it has in the specification documents.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>We have been,
most reasonably, identifying the operations specific to each service. However, I
do not see these operations identified in the Schema for any service other than
Print. (perhaps I am just missing them)<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><PZ>The WSDL identifies
the operations defined for each service (e.g. PwgPrint.wsdl). The
messages for the operations are defined in an associated schema (e.g.
PwgPrintOpMsg.xsd). The operation messages schema are really part of the
Web Service Definition but are broken out due to personal preferences.
The elements in the operation parameters are drawn from the PWG’s MFD data
model which are all the other schema in the directory.</PZ><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>For the Print
Service, the PrintServiceDescription includes the general ServiceDescription
elements, and then some 40+ additional elements among which are
OperationsSupported.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>However, the
other Services include just the general ServiceDescription elements and an
“any”, without any additional service-specific description
elements.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'>Perhaps at
least the OperationsSupported element should be among the general
ServiceDescription elements? Although one would expect that there would
be Service-specific service description elements for each service.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><PZ>The reason
OperationsSupported was included in Print is that it is the mechanism used by
IPP to determine which mandatory and optional operations are available in the
implementation. It seems to me that an element listing all the supported
operations would be useful in all the services. It should be included in
the ServicesDescription base class. There may be other Printer
description elements such as the “three sisters” attributes from
IPP (i.e. PrinterUriSupported, UriAuthenticationSupported, UriSecuritySupported).
There are some elements that make sense to be generalized to System as opposed
to the base class for the Services. Examples include DeviceId, PrinterInfo,
PrinterLocation, PrinterMakeAndModel, PrinterMoreInfo, PrinterMoreInfoManufacturer
and PrinterName. These are useful for the MFD as a whole.</PZ><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt'>Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt'>Bill Wagner<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><br>
-- <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>,
and is <br>
believed to be clean. <o:p></o:p></span></p>
</div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>
</html>