attachment-0001
<br><font size=2 face="sans-serif">Hi Pete,</font>
<br>
<br><font size=2 face="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.</font>
<br>
<br><font size=2 face="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 ?</font>
<br>
<br><font size=2 face="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.</font>
<br>
<br><font size=2 face="sans-serif">All,</font>
<br><font size=2 face="sans-serif">What do you all think?</font>
<br>
<br><font size=2 face="sans-serif">-Nancy</font>
<br><font size=2 face="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: Nancy.Chen@okidata.com</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Zehler, Peter"
<Peter.Zehler@xerox.com></b> </font>
<br><font size=1 face="sans-serif">Sent by: mfd-bounces@pwg.org</font>
<p><font size=1 face="sans-serif">09/17/2010 06:25 AM</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] Issue to resolve before publishing
v1.111 <Response Requested></font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br><tt><font size=2>All,<br>
</font></tt>
<br>
<br>
<br><tt><font size=2>The issue I found is that <service>DocumentDescriptionCapabilities
is<br>
not represented in the model. The <service>ServiceCapabilities
element<br>
contains, in effect, the capabilities of a <service>JobTicket. That<br>
does not seem to me to be the right place to "stuff" the<br>
<service>DocumentDescriptionCapabilities. I was thinking that
if we add<br>
<service>JobTicketCapabilities and <service>DocumentTicketCapabilities<br>
directly under service>ServiceCapabilities we would then have a place<br>
for <service>DocumentDescriptionCapabilities. This has some
advantages<br>
such as a clearer mapping to the job or document ticket. The downside<br>
is that <service>DocumentProcessingCapabilities would be in both<br>
capabilities. I never thought of document processing as potentially<br>
being different at the Job and Document level but I suppose that is<br>
possible.<br>
</font></tt>
<br>
<br>
<br><tt><font size=2>What is your opinion?<br>
</font></tt>
<br><tt><font size=2>1) Add <service>JobTicketCapabilities
and<br>
<service>DocumentTicketCapabilities directly under<br>
<service>ServiceCapabilities. The former contents of<br>
<service>ServiceCapabilities will move to<br>
<service>JobTicketCapabilities. <service>DocumentTicketCapabilities<br>
will contain <service>DocumentDescriptionCapabilities,<br>
<service>DocumentProcessingCapabilities and an extension point.<br>
</font></tt>
<br><tt><font size=2>2) Add <service>DocumentDescriptionCapabilities
to<br>
<service>ServiceCapabilities.<br>
</font></tt>
<br><tt><font size=2>3) Omit <service>DocumentDescriptionCapabilities<br>
</font></tt>
<br><tt><font size=2>4) Other (please specify)<br>
</font></tt>
<br>
<br>
<br>
<br>
<br><tt><font size=2>Pete<br>
</font></tt>
<br>
<br>
<br>
<br>
<br>
<br>
<br><tt><font size=2>Peter Zehler<br>
</font></tt>
<br><tt><font size=2>Xerox Research Center Webster<br>
Email: Peter.Zehler@Xerox.com <mailto:Peter.Zehler@Xerox.com><br>
Voice: (585) 265-8755<br>
FAX: (585) 265-7441<br>
US Mail: Peter Zehler<br>
Xerox Corp.<br>
800 Phillips Rd.<br>
M/S 128-25E<br>
Webster NY, 14580-9701<br>
</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>--<br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner, and is<br>
believed to be clean.</font></tt>
<br>
<br>
<br><tt><font size=2>_______________________________________________<br>
mfd mailing list<br>
mfd@pwg.org<br>
https://www.pwg.org/mailman/listinfo/mfd</font></tt>
<br>
<br><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.