All,
Nancy's comments implemented. Updated documents at:
ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722.pdf and
ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100722-rev.doc
Bill Wagner
From: Nancy.Chen at okidata.com [mailto:Nancy.Chen at okidata.com]
Sent: Thursday, July 22, 2010 9:42 AM
To: William Wagner
Cc: mfd at pwg.org; mfd-bounces at pwg.org
Subject: RE: [MFD] Requirements Document Last Call Comments resolution
Bill,
I am fine with "<service> applied only where Service was part of a term such
as "Service Job
Ticket".
With that, Section 5.3.1.4, Line 433: "the <service>" should be "the
Service" and Line 434: "<service> Capabilities" should be <service> Service
Capabilities which has not been captured in the terminology section either.
Regards,
-Nancy
"William Wagner" <wamwagner at comcast.net>
07/21/2010 09:09 PM
To
<Nancy.Chen at okidata.com>
cc
<mfd at pwg.org>, <mfd-bounces at pwg.org>
Subject
RE: [MFD] Requirements Document Last Call Comments resolution
Hi Nancy,
Thank you for your comments.
All comments have been implemented except:
1. My understanding was that the requested translation from Service to
<service> applied only where Service was part of a term such as "Service Job
Ticket" .that becomes <service> Job Ticket because for, example, there is a
Scan Job Ticket but no Service Job Ticket. However, the term Service is
defined as pertaining to any of the Imaging Services, and a phrase such as
"The Service scans the first sheet." would appear both appropriate and much
easier to read.
2.
Bill Wagner
From: Nancy.Chen at okidata.com [mailto:Nancy.Chen at okidata.com]
Sent: Wednesday, July 21, 2010 5:26 PM
To: William Wagner
Cc: mfd at pwg.org; mfd-bounces at pwg.org
Subject: Re: [MFD] Requirements Document Last Call Comments resolution
Hi Bill,
A few more editorial comments:
Page 2 and beyond - the revision Date (June 20, 2010) at the righ upper
corner of each page is wrong.
Section 5.3.1.4
Line 434: I thought we agreed that all "Service" should be changed to
<service>?
Line 442: "Resource" is mispelled.
Section 5.3.2.2
Lines 473, 479, 481, 484, 485, 489, 490, 494: "Service" should be changed to
<service>?
Section 5.3.3
Line 501: change "PhysicalDocument TicketDocument Ticket" to "Physical
Document Ticket"
Line 502: change "PhysicalJob Ticket" to "Physical Job Ticket "
Line 514: change "PhysicalJob Ticket" to "Physicalb Job Ticket".
Line 515: same change as Line 514.
Line 519: remove duplicated "and" and duplicated "Document Ticket"
Line 524: change "Physical Document TicketDocument Ticket" to "Physical
Document Ticket"
Line 525: remove dulplicated "Document Ticket"
Section 5.3.4.1
Line 541: extra '.' preceeding "Document"
Section 5.3.4.3
Line 551: "local client" should be capitalized
Line 554: "User Client" should be "Local Client"
Line 560: change "Job TicketDefault Job Ticket" to "Default Job Ticket"
Section 9
Lines 684-685: change the color of text to black.
Regards,
-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
Email: Nancy.Chen at okidata.com
"William Wagner" <wamwagner at comcast.net>
Sent by: mfd-bounces at pwg.org
07/20/2010 10:21 AM
To
<mfd at pwg.org>
cc
Subject
[MFD] Requirements Document Last Call Comments resolution
The updated MFD Modeling Requirements document reflecting the comments at
last Thursday's call is at:
The updated document is accessible at:
ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100720.pdfftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100720-rev.doc
I suggest that the un-redlined copy be reviewed.
I will update the text comments resolution later.
Thanks.
Bill Wagner
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
mfd mailing list
mfd at pwg.orghttps://www.pwg.org/mailman/listinfo/mfd
--
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/20100722/6c39bdd4/attachment-0001.html>