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;}
@font-face
{font-family:OHCJCI+Arial;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</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=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Nancy,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>You are right, I would need a parallel structure by introducing
a <service>ServiceDefaults that would contain the existing Default<service>JobTicket
and a new element for Default<service>DocumentTicket. I am a little
confused by your second paragraph since capabilities should provide all the
allowed values and default provide the single value used when not overridden in
the user request. As for DocumentForma read on.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have been doing some comparisons between the PWG SM v1 and the
current schema. There are some defaults/supported values that are an
issue. This is because these values are associated with Document
Description values or properties of the submitted Digital Document. The
elements in question from the PWG Semantic Model v1 (and IPP) are the
PrinterDescription elements:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:black'>[CompressionDefault]
(Missing in SM v1)<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>CompressionSupported<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>DocumentFormatDefault<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>DocumentFormatSupported<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>DocumetFormatDetailsDefault<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>DocumentFormatDetailsSupported</span><span
style='font-size:16.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>DocumentFormatVersionDefault<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:black'>DocumentFormatVersioSupported<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:16.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The <service>Document Description contains elements for<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Compression<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentFormat<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentFormatDetails<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentFormatVersion<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So by implementing default and capabilities for
<service>DocumentTicket, the defaults/supported above would be covered
there. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Right now the Capabilities and Default for PrintJobDescription
are missing the elements associated with:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>CompressionSupplied<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentCharsetSupplied<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentDigitalSignatureSupplied<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentFormatDetailsSupplied<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentFormatSupplied<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentFormatVersionSupplied<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentMessageSupplied<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>DocumentNameSupplied<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Impressions<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>MediaSheets<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>They will be added. I got to thinking that FaxOut
should have compression and document format, and the others above, as well.
When FaxOut is submitting a document (push or pull) these elements are
applicable. (At least that will be my working group last call comment)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think we should do #1 below and include a similar change to <service>ServiceDefaults.
In IPP the support and default values of compression and the
document format elements are properties of the service description. Should
the elements be replicated there as well?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Comments?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Impact","sans-serif";
color:navy'>Peter Zehler</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
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: </span><a href="mailto:Peter.Zehler@Xerox.com"><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Peter.Zehler@Xerox.com</span></a><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Voice: (585) 265-8755</span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>FAX: (585) 265-7441</span><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>US Mail: Peter Zehler</span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Xerox Corp.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>800 Phillips Rd.</span><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>M/S 128-25E</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Webster NY, 14580-9701</span><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'> </span><span
style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<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"'> Nancy.Chen@okidata.com
[mailto:Nancy.Chen@okidata.com] <br>
<b>Sent:</b> Friday, September 17, 2010 12:34 PM<br>
<b>To:</b> Zehler, Peter<br>
<b>Cc:</b> mfd@pwg.org; mfd-bounces@pwg.org<br>
<b>Subject:</b> Re: [MFD] Issue to resolve before publishing v1.111
<Response Requested><o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi Pete,</span>
<br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Depending on
what we want tp provide for the <service>ServiceCapabilities for Job and
Document, I would say YES to 1), if users only want to know all the
"features" available in a Job and Document Ticket at Service level.
Once we have all the features supported, we also need a corresponding
"default" for each supported feature. I don't think we have a
DedaultDocumentTicket at Service level yet currently.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Would users not
only want to know all those ticket "features" supported, but also
those supported "values" for each supported feature, such as all
supported Document Formats ?</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>DocumentFormat
in a Job or Document Ticket only specifies the Document Format value for a
particular Job or Document. However, at a simple request to a service, I would
think users want to know all DocumentFormat for all jobs and documents that are
supported/configured by a specific service instance before they submit a job to
that service.</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>All,</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>What do you all
think?</span> <br>
<br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>-Nancy</span> <br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
--------------------------------------------------------------------------------------------------<br>
Nancy Chen, PWG Vice-Chair<br>
Principal Engineer<br>
Solutions and Technology<br>
Oki Data<br>
2000 Bishops Gate Blvd.<br>
Mt. Laurel, NJ 08054<br>
Phone: (856)222-7006<br>
Email: <a href="mailto:Nancy.Chen@okidata.com">Nancy.Chen@okidata.com</a></span>
<br>
<br>
<br>
<br>
<o:p></o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td width="40%" valign=top style='width:40.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Zehler,
Peter" <<a href="mailto:Peter.Zehler@xerox.com">Peter.Zehler@xerox.com</a>></span></b><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'> </span><br>
<span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Sent by: <a
href="mailto:mfd-bounces@pwg.org">mfd-bounces@pwg.org</a></span> <o:p></o:p></p>
<p><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>09/17/2010
06:25 AM</span> <o:p></o:p></p>
</td>
<td width="59%" valign=top style='width:59.0%;padding:.75pt .75pt .75pt .75pt'>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>To</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'><<a
href="mailto:mfd@pwg.org">mfd@pwg.org</a>></span> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>cc</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Subject</span><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>[MFD]
Issue to resolve before publishing v1.111 <Response Requested></span><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><o:p> </o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'></td>
</tr>
</table>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>
</td>
</tr>
</table>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
<br>
<tt><span style='font-size:10.0pt'>All,</span></tt><span style='font-size:10.0pt;
font-family:"Courier New"'><br>
</span><br>
<br>
<br>
<tt><span style='font-size:10.0pt'>The issue I found is that <service>DocumentDescriptionCapabilities
is</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt>not represented in the model. The <service>ServiceCapabilities
element</tt><br>
<tt>contains, in effect, the capabilities of a <service>JobTicket.
That</tt><br>
<tt>does not seem to me to be the right place to "stuff" the</tt><br>
<tt><service>DocumentDescriptionCapabilities. I was thinking that
if we add</tt><br>
<tt><service>JobTicketCapabilities and
<service>DocumentTicketCapabilities</tt><br>
<tt>directly under service>ServiceCapabilities we would then have a place</tt><br>
<tt>for <service>DocumentDescriptionCapabilities. This has some
advantages</tt><br>
<tt>such as a clearer mapping to the job or document ticket. The downside</tt><br>
<tt>is that <service>DocumentProcessingCapabilities would be in both</tt><br>
<tt>capabilities. I never thought of document processing as
potentially</tt><br>
<tt>being different at the Job and Document level but I suppose that is</tt><br>
<tt>possible.</tt><br>
</span><br>
<br>
<br>
<tt><span style='font-size:10.0pt'>What is your opinion?</span></tt><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
</span><br>
<tt><span style='font-size:10.0pt'>1) Add
<service>JobTicketCapabilities and</span></tt><span style='font-size:
10.0pt;font-family:"Courier New"'><br>
<tt><service>DocumentTicketCapabilities directly under</tt><br>
<tt><service>ServiceCapabilities. The former contents of</tt><br>
<tt><service>ServiceCapabilities will move to</tt><br>
<tt><service>JobTicketCapabilities.
<service>DocumentTicketCapabilities</tt><br>
<tt>will contain <service>DocumentDescriptionCapabilities,</tt><br>
<tt><service>DocumentProcessingCapabilities and an extension point.</tt><br>
</span><br>
<tt><span style='font-size:10.0pt'>2) Add
<service>DocumentDescriptionCapabilities to</span></tt><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt><service>ServiceCapabilities.</tt><br>
</span><br>
<tt><span style='font-size:10.0pt'>3) Omit
<service>DocumentDescriptionCapabilities</span></tt><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
</span><br>
<tt><span style='font-size:10.0pt'>4) Other (please
specify)</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br>
</span><br>
<br>
<br>
<br>
<br>
<tt><span style='font-size:10.0pt'>Pete</span></tt><span style='font-size:10.0pt;
font-family:"Courier New"'><br>
</span><br>
<br>
<br>
<br>
<br>
<br>
<br>
<tt><span style='font-size:10.0pt'>Peter Zehler</span></tt><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
</span><br>
<tt><span style='font-size:10.0pt'>Xerox Research Center Webster</span></tt><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt>Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</a>
<<a href="mailto:Peter.Zehler@Xerox.com">mailto:Peter.Zehler@Xerox.com</a>></tt><br>
<tt>Voice: (585) 265-8755</tt><br>
<tt>FAX: (585) 265-7441</tt><br>
<tt>US Mail: Peter Zehler</tt><br>
<tt>Xerox Corp.</tt><br>
<tt>800 Phillips Rd.</tt><br>
<tt>M/S 128-25E</tt><br>
<tt>Webster NY, 14580-9701</tt><br>
</span><br>
<br>
<br>
<br>
<tt><span style='font-size:10.0pt'>--</span></tt><span style='font-size:10.0pt;
font-family:"Courier New"'><br>
<tt>This message has been scanned for viruses and</tt><br>
<tt>dangerous content by MailScanner, and is</tt><br>
<tt>believed to be clean.</tt></span> <br>
<br>
<br>
<tt><span style='font-size:10.0pt'>_______________________________________________</span></tt><span
style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt>mfd mailing list</tt><br>
<tt><a href="mailto:mfd@pwg.org">mfd@pwg.org</a></tt><br>
<tt><a href="https://www.pwg.org/mailman/listinfo/mfd">https://www.pwg.org/mailman/listinfo/mfd</a></tt></span>
<o:p></o:p></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>