attachment-0002
Hi,<br><br>I agree - adding the explicit mapping rules (IPP to XML)<br>would be helpful for most readers.<br><br>Cheers,<br>- Ira<br><br clear="all">Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - TCG Embedded Systems Hardcopy SG<br>IETF Designated Expert - IPP & Printer MIB<br>
Blue Roof Music/High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>
mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<div style="display:inline">
</div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div><br>
<br><br><div class="gmail_quote">On Wed, Jan 11, 2012 at 9:05 AM, Petrie, Glen <span dir="ltr"><<a href="mailto:glen.petrie@eitc.epson.com">glen.petrie@eitc.epson.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<u></u>
<u></u>
<u></u>
<u></u>
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue">I would recommend adding the section
below.<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="blue" face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria;color:blue"><u></u> <u></u></span></font></p>
<div>
<div class="MsoNormal" style="text-align:center" align="center"><font face="Times New Roman" size="3"><span style="font-size:12.0pt">
<hr size="2" width="100%" align="center">
</span></font></div>
<p class="MsoNormal"><b><font face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</span></font></b><font face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma"> Zehler, Peter
[mailto:<a href="mailto:Peter.Zehler@xerox.com" target="_blank">Peter.Zehler@xerox.com</a>] <br>
<b><span style="font-weight:bold">Sent:</span></b> Wednesday, January 11, 2012
5:31 AM<br>
<b><span style="font-weight:bold">To:</span></b> Petrie, Glen; <a href="mailto:mfd@pwg.org" target="_blank">mfd@pwg.org</a><br>
<b><span style="font-weight:bold">Subject:</span></b> RE: [MFD]
JobMandatoryElements</span></font><u></u><u></u></p>
</div><div><div class="h5">
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d">Glen,<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d">There are some rules
I used to map IPP to XML. Changing “Attribute” to
“Element” was one of them. Below is a summary of the IPP
mapping. Please let me know if this should be included in the PJT
spec. I have already added it to the PWG SM v2 specification that is
being worked in the background.<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d">Pete<u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><u></u> <u></u></span></font></p>
<div>
<p class="MsoNormal"><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><u></u> <u></u></span></font></p>
<div style="border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><font color="navy" face="Impact"><span style="font-size:11.0pt;font-family:Impact;color:navy">Peter Zehler</span></font><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><br>
<br>
</span></font><u></u><u></u><font color="navy" face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma;color:navy">Xerox</span></font><u></u><font color="navy" face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma;color:navy"> <u></u>Research<u></u> <u></u>Center<u></u></span></font><u></u><font color="navy" face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma;color:navy"> Webster<br>
</span></font><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">Email: <a href="mailto:Peter.Zehler@Xerox.com" target="_blank">Peter.Zehler@Xerox.com</a></span></font><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><br>
</span></font><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">Voice: <a href="tel:%28585%29%20265-8755" value="+15852658755" target="_blank">(585) 265-8755</a></span></font><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><br>
</span></font><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">FAX: <a href="tel:%28585%29%20265-7441" value="+15852657441" target="_blank">(585) 265-7441</a></span></font><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><br>
</span></font><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">US Mail: Peter Zehler</span></font><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><br>
</span></font><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">Xerox Corp.</span></font><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><br>
</span></font><u></u><u></u><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">800 Phillips Rd.</span></font><u></u><u></u><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><br>
</span></font><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">M/S 128-25E</span></font><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><br>
</span></font><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">Webster NY, 14580-9701</span></font><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"> <u></u><u></u></span></font></p>
</div>
<p style="margin-left:0in;text-indent:0in"><a name="134cd178fffdb80a__Toc71343196"></a><a name="134cd178fffdb80a__Ref58132335"></a><a name="134cd178fffdb80a__Toc58200673"></a><u></u><b><font color="black" face="Arial" size="5"><span style="font-size:16.0pt"><span>1. </span></span></font></b><u></u>Appendix D
– IPP Mapping<u></u><u></u></p>
<p style="margin-left:0in;text-indent:0in"><u></u><b><font color="black" face="Arial" size="4"><span style="font-size:14.0pt"><span>1.1 </span></span></font></b><u></u> <a name="134cd178fffdb80a__Toc71343197"></a><a name="134cd178fffdb80a__Toc58200674"></a>Changes to remove some IPP
specific aspects<u></u><u></u></p>
<p><font face="Arial"><span style="font-size:10.0pt">This
section lists some changes to remove some IPP specific aspects from the PWG
Semantic Model. <u></u><u></u></span></font></p>
<p><u></u><font face="Arial"><span style="font-size:10.0pt"><span>1.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>IPP enumerations use their
well-known string name instead of the integer enumeration. This applies
not only to IPP attributes but also to IPP Operations.<u></u><u></u></p>
<p><u></u><font face="Arial"><span style="font-size:10.0pt"><span>1.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>Any IPP attribute name containing
“ipp” has had the “ipp” removed. <u></u><u></u></p>
<p><u></u><font face="Arial"><span style="font-size:10.0pt"><span>2.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>All IPP attribute and operation keywords
have the substring “attribute” replaced with “element”.<u></u><u></u></p>
<p><u></u><font face="Arial"><span style="font-size:10.0pt"><span>3.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>All IPP operation, status codes,
attribute, and attribute value keyword names have had the first letter
capitalized and the ‘-‘ character removed and the character
following the ‘-‘ has been capitalized. (All mixed case PWG
Semantic Model keywords can be interpreted without regard to case.)<u></u><u></u></p>
<p><u></u><font face="Arial"><span style="font-size:10.0pt"><span>4.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>Certain elements prefixed with
“Job” that apply to either Jobs or Documents has had the
“Job” prefix removed. (This mapping clarified by the value in
the “Group” cell of the PWG SMv2 Element Summary table in appendix
A)<u></u><u></u></p>
<p><u></u><font face="Arial"><span style="font-size:10.0pt"><span>5.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>The IPP attribute value keywords
defined in other registries remain unchanged. Note that the PWG defined
media keyword values for the Semantic Elements MediaType, MediaColor,
MediaSizeName and Media use the values as specified in PWG 5101.1.<u></u><u></u></p>
<p><u></u><font face="Arial"><span style="font-size:10.0pt"><span>6.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>XML datatypes are used that map as
closely as possible to the IPP specification. <u></u><u></u></p>
<p style="margin-left:1.5in"><u></u><font face="Arial"><span style="font-size:10.0pt"><span>a.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>The IPP datatypes
NameWithoutLanguage, NameWithLanguage, TextWithoutLanguage and TextWithLanguage
are mapped to the XML datatype String. Localization is handled globally by the
ElementsNaturalLanguage element. <u></u><u></u></p>
<p style="margin-left:1.5in"><u></u><font face="Arial"><span style="font-size:10.0pt"><span>b.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>The IPP datatype Enum is mapped to
the XML datatype NMToken. See #1 above.<u></u><u></u></p>
<p style="margin-left:1.5in"><u></u><font face="Arial"><span style="font-size:10.0pt"><span>c.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>The IPP collection datatype is
represented as an XML sequence. Although sequence is used the set of
elements is unordered unless order is explicitly specified in the element
definition.<u></u><u></u></p>
<p style="margin-left:1.5in"><u></u><font face="Arial"><span style="font-size:10.0pt"><span>d.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>The “1setOf X” types
are represented as the base type and the “Multivalued” field in the
tables set to “Yes”. <u></u><u></u></p>
<p><u></u><font face="Arial"><span style="font-size:10.0pt"><span>7.<font face="Times New Roman" size="1"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><u></u>Any constraints placed on
attribute values has been noted in the tables and whenever possible expressed
in the XML schema.<u></u><u></u></p>
<p><font face="Arial"><span style="font-size:10.0pt">The
term “keyword” continues to be used for string values enumerated as
part of the PWG Model. The term “object” is sometimes changed
to “data class”. The term “operation” has been
changed to “action” to use the term more frequently used with XML.<u></u><u></u></span></font></p>
<p><font face="Arial"><span style="font-size:10.0pt">The
following IPP attributes are not included: operation-id, attributes-charset,
request-id.<u></u><u></u></span></font></p>
<p style="margin-left:0in;text-indent:0in"><u></u><b><font color="black" face="Arial" size="4"><span style="font-size:14.0pt"><span>1.2 </span></span></font></b><u></u> <a name="134cd178fffdb80a__Toc71343198"></a><a name="134cd178fffdb80a__Toc58200675"></a>Attribute Group Mapping<u></u><u></u></p>
<p><font face="Arial"><span style="font-size:10.0pt">IPP
Actions may contain a number of parameters. The first parameter is always
the Operation Attributes for the Action. The IPP Operation Attributes
have been mapped to the Printer and Job Description Element Groups.<u></u><u></u></span></font></p>
<p><font face="Arial"><span style="font-size:10.0pt">The
IPP Printer Description Attributes map to the PWG Printer Status Elements and
Printer Description Elements. The IPP Job Description Attributes map to
the PWG Job Status Elements and Job Description Elements. The PWG Model
differentiates elements that can be directly set (i.e., Description) versus
those that are maintained by automata and can only be changed through first
class operations (i.e., Status)<u></u><u></u></span></font></p>
<p><font face="Arial"><span style="font-size:10.0pt">The
IPP Job Template Attributes map to the PWG Job Processing Elements and Document
Processing Elements. <u></u><u></u></span></font></p>
<div style="border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
</div>
<p class="MsoNormal"><font color="#1f497d" face="Times New Roman" size="3"><span style="font-size:12.0pt;color:#1f497d"><u></u> <u></u></span></font></p>
</div>
<p class="MsoNormal"><font color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:Calibri;color:#1f497d"><u></u> <u></u></span></font></p>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><font face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</span></font></b><font face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma">
<a href="mailto:mfd-bounces@pwg.org" target="_blank">mfd-bounces@pwg.org</a> [mailto:<a href="mailto:mfd-bounces@pwg.org" target="_blank">mfd-bounces@pwg.org</a>] <b><span style="font-weight:bold">On Behalf Of </span></b>Petrie, Glen<br>
<b><span style="font-weight:bold">Sent:</span></b> Tuesday, January 10, 2012
5:57 PM<br>
<b><span style="font-weight:bold">To:</span></b> <a href="mailto:mfd@pwg.org" target="_blank">mfd@pwg.org</a><br>
<b><span style="font-weight:bold">Subject:</span></b> [MFD]
JobMandatoryElements<u></u><u></u></span></font></p>
</div>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria">Pete,<u></u><u></u></span></font></p>
<p class="MsoNormal"><font face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria">In PWG 5100.7 $ 3.1.2 (not section 3.12) the variable is
called job-mandatory-attributes but you call it JobMandatoryElements.
Should the name be changed (JobMandatoryAttributes) in the PJT to align?<u></u><u></u></span></font></p>
<p class="MsoNormal"><font face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria">Glen<u></u><u></u></span></font></p>
<p class="MsoNormal"><font face="Cambria" size="3"><span style="font-size:12.0pt;font-family:Cambria"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span style="font-size:12.0pt"><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b><span style="font-weight:bold">MailScanner</span></b></a>, and is <br>
believed to be clean. <u></u><u></u></span></font></p>
</div></div></div><div><div class="h5">
<br>--
<br>This message has been scanned for viruses and
<br>dangerous content by
<a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is
<br>believed to be clean.
</div></div></div>
<br>_______________________________________________<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" target="_blank">https://www.pwg.org/mailman/listinfo/mfd</a><br>
<br></blockquote></div><br><div style id="avg_ls_inline_popup"></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.