The issue I found is that <service>DocumentDescriptionCapabilities is
not represented in the model. The <service>ServiceCapabilities element
contains, in effect, the capabilities of a <service>JobTicket. That
does not seem to me to be the right place to "stuff" the
<service>DocumentDescriptionCapabilities. I was thinking that if we add
<service>JobTicketCapabilities and <service>DocumentTicketCapabilities
directly under service>ServiceCapabilities we would then have a place
for <service>DocumentDescriptionCapabilities. This has some advantages
such as a clearer mapping to the job or document ticket. The downside
is that <service>DocumentProcessingCapabilities would be in both
capabilities. I never thought of document processing as potentially
being different at the Job and Document level but I suppose that is
What is your opinion?
1) Add <service>JobTicketCapabilities and
<service>DocumentTicketCapabilities directly under
<service>ServiceCapabilities. The former contents of
<service>ServiceCapabilities will move to
will contain <service>DocumentDescriptionCapabilities,
<service>DocumentProcessingCapabilities and an extension point.
2) Add <service>DocumentDescriptionCapabilities to
3) Omit <service>DocumentDescriptionCapabilities
4) Other (please specify)
Xerox Research Center Webster
Email: Peter.Zehler at Xerox.com <mailto:Peter.Zehler at Xerox.com>
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
800 Phillips Rd.
Webster NY, 14580-9701
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...