attachment-0001
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think "DestinationUris" is right since the IPP mapping is "destination-uris". If we used "DestinationURIs" the name would map to "destination-u-r-is"... :)<div><br><div><div>On Apr 28, 2011, at 9:05 AM, <a href="mailto:Nancy.Chen@okidata.com">Nancy.Chen@okidata.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<br><font size="2" face="sans-serif">Bill and Pete,</font>
<br>
<br><font size="2" face="sans-serif">While checking the FaxOut Service working
draft's consistency with the MFD Model and Common Semantics spec, I found
that the XML element "DestinationUris" is inconsistently named
as "DestinationURIs" or "DestinationURI" in some places
throughout the MFD Model and Common Semantics document. In the FaxOut
Service working draft, "DestinationURIs" is consistently used
both in draft spec and XML Schema, which I think they should all be "DestinationUris"
according to the MFD Model and Common Semantics. I will address that in
my comments for FaxOut Service spec.</font>
<br>
<br><font size="2" face="sans-serif">I remember in one of the face-to-face
meeting, we discussed whether URIs or Uris should be used, and the consensus
was the latter. I don't mind to change back to URIs, but please make
them all consistently named, referenced, both in specs and XML Schema.</font>
<br>
<br><font size="2" face="sans-serif">Please check and ensure consistencies
globally in the documents and XML Schema.</font>
<br>
<br><font size="2" face="sans-serif">Thanks,</font>
<br><font size="2" face="sans-serif">-Nancy</font>
<br><font size="2" face="sans-serif">--------------------------------------------------------------------------------------------------<br>
Nancy Chen, PWG Vice-Chair<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</font>
<br>
<br>
<br>
<br>
<table width="100%">
<tbody><tr valign="top">
<td width="40%"><font size="1" face="sans-serif"><b>"William Wagner"
<<a href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a>></b> </font>
<br><font size="1" face="sans-serif">Sent by: <a href="mailto:mfd-bounces@pwg.org">mfd-bounces@pwg.org</a></font><p><font size="1" face="sans-serif">04/25/2011 10:05 PM</font>
</p></td><td width="59%">
<table width="100%">
<tbody><tr valign="top">
<td>
<div align="right"><font size="1" face="sans-serif">To</font></div>
</td><td><font size="1" face="sans-serif">"'Zehler, Peter'" <<a href="mailto:Peter.Zehler@xerox.com">Peter.Zehler@xerox.com</a>>,
<<a href="mailto:mfd@pwg.org">mfd@pwg.org</a>></font>
</td></tr><tr valign="top">
<td>
<div align="right"><font size="1" face="sans-serif">cc</font></div>
</td><td>
</td></tr><tr valign="top">
<td>
<div align="right"><font size="1" face="sans-serif">Subject</font></div>
</td><td><font size="1" face="sans-serif">RE: [MFD] MFD Teleconference</font></td></tr></tbody></table>
<br>
<table>
<tbody><tr valign="top">
<td>
</td><td></td></tr></tbody></table>
<br></td></tr></tbody></table>
<br>
<br><tt><font size="2">All,<br>
</font></tt>
<br>
<br>
<br><tt><font size="2">Thank you for your comments. I have modified the Model
and Common Semantics document to reflect editorial and technical issues.
The current version is posted at <a href="ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110426.pdf">ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdmodel10-20110426.pdf</a>.
I have removed line numbers in preparation for release, but have kept the
status as Stable pending agreement that the necessary issues are fix (any
nothing too much else has gone awry).<br>
</font></tt>
<br><tt><font size="2">All except figure and formatting changes are
highlighted in yellow.<br>
</font></tt>
<br><tt><font size="2">Reported comments are below. Issues in light gray
have not been specifically addressed.:<br>
</font></tt>
<br>
<br>
<br><tt><font size="2">1.Change “System Service” to “System Control Service”
(3 places in text)<br>
</font></tt>
<br><tt><font size="2">2. Update Table 52 and Figure 80 to indicate that
NaturalLanguageSupported is multi-valued<br>
</font></tt>
<br><tt><font size="2">3. Fix references for NaturalLanguageSupported
and NaturalLanguageConfigured on Table 52 of MFD Model<br>
</font></tt>
<br><tt><font size="2">4. Add note to Table 52 that NaturalLanguageSupported
corresponds to generated-natural-language-supported in IPP<br>
</font></tt>
<br><tt><font size="2">5. Update Figure 80 of Model to reflect that
CharsetConfigured and CharsetSupported are mandatory as in IPP<br>
</font></tt>
<br><tt><font size="2">6. Update Figure 83 of Model to reflect that QueuedJobCount
is mandatory in IPP<br>
</font></tt>
<br><tt><font size="2">7. Delete Startup<service>Service in Table
79<br>
</font></tt>
<br><tt><font size="2">8. Add “Imaging Client” to the table in section
1.3.2 MFD Services Terminology – same meaning as “Client” – new terminology
used in IDS and Cloud<br>
</font></tt>
<br>
<br>
<br><tt><font size="2">Nancy Chen comments:<br>
</font></tt>
<br><tt><font size="2">1) Line 49 - document link needs update.<br>
2) Page 106, Table 44 - "Cross FeedDir" should be concatenated<br>
3) Page 112, Table 48 - typo: "vraious"<br>
4) Page 123, Figure 80 - need updated Schema diagram for ImagingServiceDescription
(as above)<br>
5) Page 124, Table 52 - fix data type for NaturalLanguageSupported (as
above)<br>
6) Page 141, Line 1986 - 'ever' is at the beginning of a sentence. It should
be "However"?</font></tt>
<br><tt><font size="2">& Line 1902 - need to reformat (apply left justification?)
to remove extra spaces between words. (see comment below)<br>
& Line 1911 - change 'hav' to 'have'.</font></tt>
<br><tt><font size="2">7) Page 144, Table 62 - "Document Format"
should be concatenated<br>
</font></tt>
<br><tt><font size="2">Although I appreciate that the coarse justification
resulting from the long concatenated strings can be disconcerting, I personally
find an occasional coarse justification less objectionable than extremely
ragged right margins. Also, since the body of the text is justified, switching
the style to left aligned may have strange effects affecting pagination.
I have reworded some of the more obvious justification problem areas
to lessen the effect, but I ask your indulgence to leave the rest as it
is. At any rate, with the layout changes, the justification problems are
probably not where they appeared in the previous version.<br>
</font></tt>
<br><tt><font size="2">8) Page 155, Lines 1961 & 1962 - reformat (apply
left justification?) to remove extra spaces between words.<br>
9) Page 160, Lines 2002 to 2004 - reformat (apply left justification?)
to remove extra spaces between words.<br>
10) Page 187, Lines 2424 - 2425 & 2438 - reformat (apply left justification?)
to remove extra spaces between words.<br>
11) Page 200, Line 2906 & 2918 - reformat (apply left justification?)
to remove extra spaces between words.<br>
12) Page 201, Lines 2935, 2951 - reformat (apply left justification?) to
remove extra spaces between words.<br>
13) Page 202, Line 2968 - reformat (apply left justification?) to remove
extra spaces between words.<br>
14) Page 203, Line 2989 - reformat (apply left justification?) to remove
extra spaces between words.<br>
15) Page 204, Line 3009 - reformat (apply left justification?) to remove
extra spaces between words.<br>
16) Page 205, Lines 3046, 3070, 3071, 3079 - reformat (apply left justification?)
to remove extra spaces between words.<br>
17) Page 206, Lines 3080, 3018, 3116 - reformat (apply left justification?)
to remove extra spaces between words.<br>
18) Page 209, Line 3203, 3205, 3218 - reformat (apply left justification?)
to remove extra spaces between words.<br>
19) Page 209, Line 3207 - "Media Used Counters" should be followed
by a ':', not a period.<br>
20) Page 210, Line 3232, subsection 8.1 heading - left justify the words
in the heading.<br>
21) Page 216, Lines 3332, 3334 - reformat (apply left justification?)
to remove extra spaces between words.<br>
</font></tt>
<br>
<br>
<br>
<br>
<br>
<br>
<br><tt><font size="2">From: <a href="mailto:mfd-bounces@pwg.org">mfd-bounces@pwg.org</a> [mailto:mfd-bounces@pwg.org]
On Behalf Of Zehler, Peter<br>
Sent: Wednesday, April 20, 2011 10:32 AM<br>
To: <a href="mailto:mfd@pwg.org">mfd@pwg.org</a><br>
Subject: [MFD] MFD Teleconference<br>
</font></tt>
<br>
<br>
<br><tt><font size="2">All,<br>
</font></tt>
<br>
<br>
<br><tt><font size="2">The Copy Service’s Last Call ends this Friday.
Please send any comments to the MFD list.<br>
</font></tt>
<br>
<br>
<br><tt><font size="2">Given that I have been out for a bit, have a final
MFD schema to publish, need to update the Copy spec for Formal Vote, need
to update the FaxOut spec for PWG Last Call, need to produce a couple of
use cases and need to update the System Service spec, I do not have time
or content for an MFD teleconference this week. I will put out an
agenda for an MFD teleconference to be held on April 28th.<br>
</font></tt>
<br>
<br>
<br><tt><font size="2">Let me know if this is a problem for anyone.<br>
</font></tt>
<br>
<br>
<br><tt><font size="2">Pete<br>
</font></tt>
<br>
<br>
<br>
<br>
<br><tt><font size="2">Peter Zehler<br>
</font></tt>
<br><tt><font size="2">Xerox Research Center Webster<br>
Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</a><br>
Voice: (585) 265-8755<br>
FAX: (585) 265-7441<br>
US Mail: Peter Zehler<br>
Xerox Corp.<br>
800 Phillips Rd.<br>
M/S 128-25E<br>
Webster NY, 14580-9701<br>
</font></tt>
<br>
<br>
<br>
<br><tt><font size="2">--<br>
This message has been scanned for viruses and<br>
dangerous content by <<a href="http://www.mailscanner.info/">http://www.mailscanner.info/</a>> MailScanner,
and is<br>
believed to be clean.<br>
</font></tt>
<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><tt><font size="2">_______________________________________________<br>
mfd mailing list<br>
<a href="mailto:mfd@pwg.org">mfd@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/mfd">https://www.pwg.org/mailman/listinfo/mfd</a></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.
<span><C.htm></span>_______________________________________________<br>mfd mailing list<br><a href="mailto:mfd@pwg.org">mfd@pwg.org</a><br>https://www.pwg.org/mailman/listinfo/mfd<br></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>________________________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span>
</div>
<br></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>