attachment-0001
<br><font size=2 face="sans-serif">Bill,</font>
<br>
<br><font size=2 face="sans-serif">I have some more comments/issues with
the document. My appology for not catching these last week.</font>
<br>
<br><font size=2 face="sans-serif">Terminology –</font>
<br><font size=2 face="sans-serif">Should we have a “Terminology” section
which may simply refer to the “Terminology” section of MFD Overall Model
and Semantics?</font>
<br><font size=2 face="sans-serif">If we refer to the Terminologies defined
in MFD Overall Model and Semantics, then let's make sure the terminologies
used consistent with that document throughout and are capitalized.</font>
<br><font size=2 face="sans-serif">Otherwise, I recommend to remove those
capitalized terms.</font>
<br>
<br><font size=2 face="sans-serif">Section 1</font>
<br><font size=2 face="sans-serif">Line 146 – "Mulifunction"
=> missing “t”.</font>
<br>
<br><font size=2 face="sans-serif">Section 2.3.3</font>
<br><font size=2 face="sans-serif">Line 304 – leave a space between “the”
and “commonality”.</font>
<br>
<br><font size=2 face="sans-serif">Section 3.1</font>
<br><font size=2 face="sans-serif">Line 394 – Is this “PWG Semantic Model
(REF)” referring to PWG Semantic Model V2 again? If so, we need to delete
it and revise the sentence.</font>
<br>
<br><font size=2 face="sans-serif">Section 3.1.1.2</font>
<br><font size=2 face="sans-serif">Line 493 – delete “Copy” from
"Copy Template Client". The flow steps apply to Copy/Scan/FaxOut.</font>
<br>
<br><font size=2 face="sans-serif">Section 3.1.1.3</font>
<br><font size=2 face="sans-serif">Line 500 - delete “FaxOut” from "FaxOut
Template Client". </font>
<br>
<br><font size=2 face="sans-serif">Section 4.3.2 Use Case 2</font>
<br><font size=2 face="sans-serif">1) There are actually two separate scenario
examples in this section. However, the first example seemed being used
as the general description of this use case.</font>
<br>
<br><font size=2 face="sans-serif">Suggestion: provide a brief general
description of the use case in the first paragraph, like how it’s done
in Use Case 3. Then give the two use case examples in the following
two subsections.</font>
<br>
<br><font size=2 face="sans-serif">2) In the described scenarios, the user
scans/copies/faxes out <b>multiple hardcopy documents. </b>It provides
detailed flow steps for handling multiple hardcopy documents input to scanner.
But the title specifically says “Handling <b>“a” </b>Hardcopy
Document…”.</font>
<br>
<br><font size=2 face="sans-serif">Suggestion: how about change the title
to “Handling Hardcopy Document Inputs …”</font>
<br>
<br><font size=2 face="sans-serif">3) Line 512: change a “given Subunit”
to a “given Scanner Subunit”. I don’t believe this scenario can
be generalized to any given subunit.</font>
<br><font size=2 face="sans-serif">4) Line 537: change “Document” to
Document(s), or one or more documents.</font>
<br><font size=2 face="sans-serif">5) Line 546: the repeated steps should
be 9 through 13, not 8 through 12.</font>
<br><font size=2 face="sans-serif">6) Line 549: delete the second “notifies”
– redundant.</font>
<br>
<br><font size=2 face="sans-serif">Section 4.3.4.1</font>
<br><font size=2 face="sans-serif">Title- change “Pausing Copy Service”
to “Pausing Scan Service”</font>
<br>
<br><font size=2 face="sans-serif">Section 4.3.4.2</font>
<br><font size=2 face="sans-serif">Title- change “Pausing Print
Service” to “Pausing Copy Service”</font>
<br>
<br><font size=2 face="sans-serif">Section 4.3.4.3</font>
<br><font size=2 face="sans-serif">1) In the processing steps, remove “Scan”
or “Copy” to use a general “Service” or “Job”.</font>
<br><font size=2 face="sans-serif">2) Lines 604-605: Break the sentence
at an appropriate place.</font>
<br>
<br><font size=2 face="sans-serif">Section 5.1</font>
<br><font size=2 face="sans-serif">Line 693 – change “alterate” =>
“alternate”</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">-Nancy<br>
--------------------------------------------------------------------------------<br>
Nancy Chen<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>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"William Wagner"
<wamwagner@comcast.net></b> </font>
<br><font size=1 face="sans-serif">Sent by: mfd-bounces@pwg.org</font>
<p><font size=1 face="sans-serif">05/20/2010 09:29 PM</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] WG Last Call MFD Requirments document</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br>
<br><tt><font size=2>I have posted MS Word and PDF versions of the requirements
document with<br>
changes from the 20 May conference call.<br>
</font></tt>
<br><tt><font size=2>ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdreq10-20100520.pdf<br>
</font></tt>
<br><tt><font size=2>ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdreq10-20100520-rev.pdf
(markup<br>
showing changes)<br>
</font></tt>
<br><tt><font size=2>ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdreq10-20100520.doc<br>
</font></tt>
<br>
<br>
<br><tt><font size=2>(the *doc version can be viewed with or without markups)<br>
</font></tt>
<br>
<br>
<br><tt><font size=2>As decided in the WG conference call, this version
is being presented for<br>
MFD working group last call. The intent is that all remaining working group<br>
comments can be addressed and a stable version presented to the PWG
for PWG<br>
last call overlapping the June Plenary. So please review the document and<br>
send me your comments. Typographical and clarity issues will be dealt with<br>
immediately. Mort substantial questions will be addressed at next week's
MFD<br>
conference call.<br>
</font></tt>
<br>
<br>
<br><tt><font size=2>Many thanks.<br>
</font></tt>
<br>
<br>
<br><tt><font size=2>Bill Wagner<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.<br>
</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.