Global: The header text of each page has a much larger font than the
footer!
Lines 194-195:
FaxOut are used repeatedly as an English verb, or as a function name, etc.
Reads funny. Notice that FaxOut is a special term defined in MFD Semantics
as the name of the specific MFD service.
2. Section 5 - MFD Model Overview
Do we need a MFD Model Overview for an individual service spec? Why not
move the content of this section to the beginning of Section 6, I like it
as a concise prelude before the FaxOut Service Model Overview?
3. Line 282: extra "that".
4. Figure 13 FaxOutJobProcessing Schema diagram is out of date?
The "DestinationURIs" is "DestinationUris" in MFD Model and Common
Semantics spec and XML Schema.
5. Section 7.3.3.1, Line 495 -
DestinationURI is fully described in 5.2.3.1 of MFD Model and common
Semantics. Is this section different than that? Why not just reference it
instead of providing only part of description?
6. Extension Points in Schema: I remember that in one of the
face-to-face meeting we decided that any complex element type will include
an attribute extension point and an element extension point. Many of the
datatypes in FaxOut Service model have one of the extension point missing.
Shouldn't these be all consistent? However, if the existing MFD Schema
is mostly not consistent this way, it might require a lot of changes
throughout.
7. GetActiveFaxOutJobs has the list of JobSummaries as a mandatary
response element returned, that is optional in the MFD Model. Is this a
FAxOutService-specific requirement?
9. RestartFaxoutService has some service-specific request paramenters?
Some are not listed in the MFD Model spec. Also in the last face-to-face,
I thought we have a consensus that a service can not restart itself, must
be restarted by the SystemControlService.
-Nancy
--------------------------------------------------------------------------------------------------
Nancy Chen, PWG Vice-Chair
Principal Engineer
Solutions and Technology
Oki Data
2000 Bishops Gate Blvd.
Mt. Laurel, NJ 08054
Phone: (856)222-7006
--
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...
URL: <http://www.pwg.org/pipermail/mfd/attachments/20110428/01dfe261/attachment-0001.html>