attachment-0001
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Impact;
panose-1:2 11 8 6 3 9 2 5 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:10.0pt'>At the face to face, it was
indentified that the MFD “Overall” document needed “
Requirements” section.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'>The PWG process document says
“Prior to completion of the first Working Draft, a clear statement
of requirements for the standard to be produced is required. A requirements
statement documents the best effort collection of known requirements on a
particular protocol, interface, procedure or convention. The requirements
statement is important as it leads to a clear, common understanding of the
goals, provides a guide for developing the standard, and can be used as a final
test to measure the completeness of the resulting specification. …”<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'>In practice, the Requirements
document has reverted to being a section in the spec draft. And one such section
exists in the Scan and Resource standards. However, I suggest that, in place of
including a rather minimal Requirements section in each Service spec, the Overall
Spec and the System spec, we do a separate but meaningful Requirements document
for the set of MFD Service and supporting documents.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'>I think a separate single Requirements
document would not only be more efficient, but it would help readers understand
why we are taking a much implemented device type and Services that have been
around for many years and creating new and very involved model descriptions. I
think a meaningful requirements document would indeed allow a “common
understanding of the goals, provide a guide for developing the standard, and [a
reference] to measure the completeness of the resulting specification.”<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'>I call the existing
Requirements sections minimal since they consist of Rationale, Out of
Scope, and Model Mapping Conventions. The ‘ Rationale’
section takes the form “ There is clear need to do this”,
which appears rather circular. ‘Out of Scope’ is useful in
providing bounds, but does not really help understanding what is in scope. “
Model Mapping Conventions” does not really appear to be a main aspect of
requirements.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'>The process document is
unclear on whether “Requirements” should be “
Requirements for” (i.e. why it is needed, Rational, Use Cases) or “
Requirements of” (operational requirements, what must be addressed, constraints,
need for conformity with, and out of scope). In the case of the MFD
Service documents, the requirements should not necessarily relate to the requirements
for or of the Service but rather the requirements for and of a model of the service
consistent with an overall structure (I think… but I too need some help
in clearly stating why the modeling is necessary.)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'>So, I propose a separate Requirements
document and would like some help to really define the need for a consistent
modeling of MFD services. So far, the best I can find is in the charter “</span>Currently
service, device, and job management and job submission protocols for these
network MFDs are fragmented and proprietary. “ <span style='font-size:
10.0pt'>Along with this would be some requirements of the models (be
representable in XML? be consistent with IPP? Be compatible with
existing products?)…Pete and Ira seem to have a handle on this but I suspect
that having a clear written statement may have limited the continuous evolution
that we have been experiencing.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'> Of course, if no one is
interested, I can just copy the standard stuff we have in the other specs and
get this puppy rolling.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'>Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'>Bill Wagner</span><span
style='font-size:14.0pt;color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> mfd-bounces@pwg.org
[mailto:mfd-bounces@pwg.org] <b>On Behalf Of </b>Zehler, Peter<br>
<b>Sent:</b> Tuesday, October 27, 2009 7:18 AM<br>
<b>To:</b> mfd@pwg.org<br>
<b>Subject:</b> [MFD] MFD teleconference Thursday10/29 at 3:00 PM EDT (12:00 PM
PDT)<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>As agreed at the recent face to face meeting there will be an MFD
conference call at 3:00 PM EDT (12:00 PM PDT) Thursday October 29. The focus
of this meeting is the Copy specification that was not covered at the meeting.</span>
The same document will be used.<b><span style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:black'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:black'>The meeting is held in accord with the PWG Intellectual Property
Policy.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Note the NEW
Teleconference number and access code are now used.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Please
contact me if you do not have the new number and pass code.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Call-in
toll-free number (US/Canada): 1-866-469-3239 <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Call-in
toll number (US/Canada): 1-650-429-3300 <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Call-in
toll number (US/Canada): 1-408-856-9570 <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Attendee
access code: (by request only, please contact me if you do not have it)<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Agenda:<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>1.
Identify Minute Taker<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>2.
Approval of minutes from last meeting<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> <<a
href="ftp://ftp.pwg.org/pub/pwg/mfd/minutes/pwg-ftf-mfd-minutes-20091013-14.pdf">ftp://ftp.pwg.org/pub/pwg/mfd/minutes/pwg-ftf-mfd-minutes-20091013-14.pdf</a></span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>><span
style='color:black'> <o:p></o:p></span></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>3. Agenda
bashing <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>4.
Resolve PrinterResolution representation (PrintServiceCapabilities)<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>5.
Discuss Media, MediaType and MediaCol representation in <service>DocumentProcessing
and IPP/WS-Print mapping<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>6.
Discuss Copy Service Semantic Model and Service Interface- Interim Draft.</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'> <o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-.75in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><<span
style='color:#1F497D'><a
href="ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdcopymodel10-20091007.pdf">ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdcopymodel10-20091007.pdf</a></span>><span
style='color:#1F497D'> <o:p></o:p></span></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-.75in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>(also
available is the “-rev” version as well as the “.doc”
format for both versions)<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>7. Next
steps<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:1.25in;text-indent:-1.25in'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:
12.0pt;margin-left:0in'><span style='color:black'><br>
</span><span lang=EN style='color:black'>Click Here to Join Live Meeting </span><span
lang=EN style='font-size:12.0pt;font-family:"Times New Roman","serif";
color:black'><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:
12.0pt;margin-left:0in'><span lang=EN style='color:black'><</span><span
style='font-family:"Arial","sans-serif"'><a
href="https://www.livemeeting.com/cc/xerox/join?id=PWG_MFD&role=attend&pw=PQ%25%3EFj5sN"
title="blocked::https://www.livemeeting.com/cc/xerox/join?id=PWG_MFD&role=attend&pw=PQ%>Fj5sN">https://www.livemeeting.com/cc/xerox/join?id=PWG_MFD&role=attend&pw=PQ%25%3EFj5sN</a>></span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-family:"Impact","sans-serif";color:navy'>Peter
Zehler</span><br>
<br>
<span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy'>Xerox
Research Center Webster<br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</a></span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Voice:
(585) 265-8755</span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>FAX:
(585) 265-7441</span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>US
Mail: Peter Zehler</span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Xerox
Corp.</span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>800
Phillips Rd.</span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>M/S
128-25E</span><br>
<span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Webster
NY, 14580-9701</span> <span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><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. <o:p></o:p></span></p>
</div>
<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.
</body>
</html>