I see the set of MFD specification enhancing the development of workflow
solutions. The MFD specification clarifies the common semantics used by
the various user perceived MFD functions. I expect an orchestration
service/application would oversee the execution of complex jobs and
handle task sequencing and task status rollup and processing. The
orchestration service/application can leverage industry standards (e.g.
WSCI, BPEL4WS, JDF), be market or vendor specific or, perhaps,
eventually select one of those and create MFD orchestration service in
its own right.
Xerox Research Center Webster
Email: Peter.Zehler at Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
800 Phillips Rd.
Webster NY, 14580-9701
From: Petrie, Glen [mailto:glen.petrie at eitc.epson.com]
Sent: Friday, November 14, 2008 10:35 AM
To: Zehler, Peter
Cc: mfd at pwg.org
Subject: Workflow Question for MFD Specification
I understand your approach to having a set of MFD specifications that do
not require or is based on a workflow model/architecture. Since, you
are currently the most knowledgeable about the MFD specification/schema,
do you see anything that would impede the development of a workflow
-------------- next part --------------
An HTML attachment was scrubbed...