attachment-0002
<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=utf-8"><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:12.0pt;
font-family:"Times New Roman","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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.emailquote, li.emailquote, div.emailquote
{mso-style-name:emailquote;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:1.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:412700278;
mso-list-type:hybrid;
mso-list-template-ids:-1174006494 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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=WordSection1><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks Peter. We will try to consider satisfactory resolution of WG comments during Cloud and we request consideration of </span><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>“JPS3 comment on xxx-preferred”. Issue dirng the special IPP meeting this afternoon.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill Wagner</span><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";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"'> Zehler, Peter [mailto:Peter.Zehler@xerox.com] <br><b>Sent:</b> Monday, January 16, 2012 10:20 AM<br><b>To:</b> William Wagner; cloud@pwg.org<br><b>Cc:</b> Ron Nevo<br><b>Subject:</b> RE: [Cloud] next conference call Monday Dec 19 2011 from 1:00 to 2:00pm EST<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>All,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I will be unable to attend due to a personal commitment. For agenda item #4 I do not track Working Group last call comments the way I track the official Last Call. Below are the comments and the resolutions I could find. I have one roadblock to publishing an updated schema and sending PJT out for PWG Last Call. I sent a note out on it yesterday titled “JPS3 comment on xxx-preferred”. Can we resolve this asap either online or at a meeting this week?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Pete<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>1) Comment: The global search/replace on Printer w/ Print Service also got into the footer and the front matter in Printer Working Group (no Print Service Working Group)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: Fixed<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>2) Comment: Section 6.1.3: Following the other sections; should “ISheetType” be called “InsertSheetType”<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Section 6.1.4: Following the other sections, should “MediaCol” be called “MediaColType”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: These were missed when conventions changed in the schema. The schema and specification have been updated<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>3) Comment: In Section 5 Print Service Description, the section reference for "the definition for the PrintServiceCapabilities container element" is incorrect. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>See the following text in the spec: <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>" <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>368 A container element is needed to carry the subset of PrintServiceDescription elements, <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>369 the PrintJobTicketCapabilities and the PrintDocumentCapabilities in a protocol. Section 0 <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>370 contains the definition for the PrintServiceCapabilities container element. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>" <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: reworked section 5 a bit to update the section reference and clarify the container element mapping<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>4) Comment: The "container element" mentioned above is not defined in the spec. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: reworked section 5 a bit to update the section reference and clarify the container element mapping<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>5) Comment: Table 3 - the element "PWGRasterDocumentBackside" came from PWG Raster Format spec, in Section 5 Semantic Model Elements - Table 9: the "PWGRasterDocumentSheetBack" element. Shouldn't this element use the same name in these two specs????<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: Aligned with specification “PwgRasterDocumentSheetBack”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>6) Comment: I noticed that job accounting sheets has an output-bin; should there be an output-bin element for job error sheet?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: I’m inclined to stick with the IPP definition<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>7) Comment: rfc2911 / 4.2.3 define the two possible JobSheets as ‘none’ and ‘standard’ while the WKV’s for this include job-start-sheet and first-print-stream-page,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Job-start-sheet is, according to rfc2911 on page 221, “create” when auto-sensing has occurred. Also see 4.1.9.1 on page 88.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Was the enum for JobSheets updated in a later document?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I can find no reference to first-print-stream-page (FirstPrintStreamPage)?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: The values are defined in PWG5100.3 §6.2. (Set 1, 2 and 3 have additional values for various elements defined elsewhere.) I have a reference in appendix C to the IANA registry for IPP. <<a href="http://www.iana.org/assignments/ipp-registrations/ipp-registrations.xml">http://www.iana.org/assignments/ipp-registrations/ipp-registrations.xml</a>> The registry is up to date as of December 2011. I was missing the reference entry for [IPPREG] so I fixed that.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>8) Comment: The PJT states the ref is 5100.4 / 5.3; but 5100.4 is obsolete and replaced with 5100.6. 5100.6 states that PagesPerSubset is outside the scope of 5100.6 ………… found it. JPS3 section 5.2.1, can you update the PJT ref.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: Fixed<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>9) 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?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: Added appendix on the rules I used to map IPP to XML<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>10) Comments: In the diagram (page 27) you have JobDelayOutputUntil. On page 46 you have JobDelayUntil. I believe they should match. To go with JobHold, I think it should be JobDelayUntil<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: Corrected name to “JobDelayOutputUntil” and corrected “HoldUntilWKV”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>11) Comment: The TemplateXXX elements are stated to be in PWG 5108.3 sections 1.3.2.12-16; but there is no section nor elements defined for Template in the document. The spec is about resources. I don’t see another spec for template. Can you or someone else point me to the correct spec? Since a Template I believe is a resource; then, is TemplateXXX just an instantiated name for ResourceXXX as in PWG 5108.03 section 7.4.2.4 – 7.4.2.8. I am still a confused about he TemplateType Keyword or is this actually the ResourceType with the only keyword of “PrintJob”.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: The “TemplateXXX” elements are Job Description elements that give information about a template that was used to create a Job. In the PrintJobTicket specification “TemplateType” is limited to ‘PrintJob’. The PWG Semantic model permits other types of templates (i.e., values for every service in both a Job and Document flavor). One of the places from which a template could be available is a Resource Service. The “ResourceCategory” would be ‘Template’ and the “ResourceType” would be one of the values from “TemplateTypeWKV”. Note that that “ResourceType” is a superset of “TemplateType” since resources can be things other than Templates.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The correct TemplateXXX references are:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>TemplateCreatorUserName [PWG5108.2] §8.1.3.2.12<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>TemplateId [PWG5108.2] §8.1.3.2.13<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>TemplateInfo [PWG5108.2] §8.1.3.2.14<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>TemplateName [PWG5108.2] §8.1.3.2.15<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>TemplateType [PWG5108.2] §8.1.3.2.16<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>12) Comment: I have DocumentFormatDetailsSupported as a required element in a table 3 (section 8.2). It occurs nowhere else in the specification and is not currently in the Service Description subset of elements used for document generation in the schema (DocumentGenerationElements). Should DocumentFormatDetailsSupported be a mandatory ServiceDescription element used in the subset of elements used for document generation?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: No<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>13) Comment: Reference for MediaTooth (on page 52) I believe should be [PWG5100.11] $11.5.1. Reference for MediaRecycled I believe is PWG 5100.3 $ 3.13.11 and MediaPrePrinted I believe is PWG 5100.3 $3.13.5<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: Fixed<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>14) Comment: So is “Media” (from page 50 of pwg:pjt) the same as “MediaSizeName” (from page 51 of pwg:pjt)? Actually, the reference for MediaSizeName (pwg 5100.5 $8.1) appears to be wrong. MediaSizeName is also defined in the 5105.1 /pg 35 and has the same references pwg 5100.5 $8.1. Maybe MediaSizeName is defined somewhere else. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: Media is defined in RFC2911 §4.2.11 and MediaSizeName is defined in PWG5108.02 §8.1.3.1.15.3. The semantic difference is that Media is a named medium upon which the impressions will be printed and MediaSizeName is a named size of the canvas for an image. For both elements PWG5101.1 §5 is the reference for the standard values.</span> <span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>add "MediaSizeName" to MediaCol, move MediaSource out of the MediaSize/SizeName/Source choice since source is often used in conjunction with size on non-production printers (i.e. print envelopes from bypass tray). MediaSource is only in MediaCol. Media (top-level element) can have a size or source name registered with IANA or a self-describing name (PWG 5101.1) Add reference to RFC 2911 for Media and MediaType. Make sure IANA registered and 5101.1 names are all in the well-known values list for Media and MediaType.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>15) Comment: For Resolution DataType, there is not reference/definition for Units in this document. I found on page 55 that this Units are stated to be DPI or DPCM. So do we need to explicitly define “Units” as a string type with ‘dpi’ and ‘dpcm’ as values.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Resolution: Resolution is a datatype defined in RFC2911 so I initially treated it as such. To clarify the definition the specification will now treat Resolution as any other complex type. The UnitsWKV will be included.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Impact","sans-serif";color:navy'>Peter Zehler</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br><br></span><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: </span><a href="mailto:Peter.Zehler@Xerox.com"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Peter.Zehler@Xerox.com</span></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Voice: (585) 265-8755</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>FAX: (585) 265-7441</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>US Mail: Peter Zehler</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Xerox Corp.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>800 Phillips Rd.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>M/S 128-25E</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Webster NY, 14580-9701</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";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"'> </span><a href="mailto:cloud-bounces@pwg.org"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>cloud-bounces@pwg.org</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span><a href="mailto:[mailto:cloud-bounces@pwg.org]"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>[mailto:cloud-bounces@pwg.org]</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <b>On Behalf Of </b>William Wagner<br><b>Sent:</b> Saturday, January 14, 2012 1:03 PM<br><b>To:</b> </span><a href="mailto:cloud@pwg.org"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>cloud@pwg.org</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br><b>Cc:</b> 'Ron Nevo'<br><b>Subject:</b> RE: [Cloud] next conference call Monday Dec 19 2011 from 1:00 to 2:00pm EST<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>It is my understanding that there will be a one-hour Cloud Working Group meeting on Monday, January 16 at 1 PM EST.<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br> Call-in toll-free number (US/Canada): 1-866-469-3239<br> Call-in toll number (US/Canada): 1-650-429-3300 (Primary)<br> Call-in toll number (US/Canada): 1-408-856-9570 (Backup)<br><br> Attendee Access Code: *******#<br> Attendee ID Code: # (empty)<br><br>If you need the Attendee Access code, please email me a request.<br><br><br>Agenda:<br><br>(1) PWG IP Policy and Minute Taker<br><br>(2) Approve Cloud Imaging WG minutes from last teleconference<o:p></o:p></span></p></div><div><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20111219.pdf"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20111219.pdf</span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#993366'> </span><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>(3) Action items from last meeting<span style='color:#1F497D'> (updating status and refreshing these may be the primary discussion items).</span><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-size:9.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>Decide next work after mapping document<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-size:9.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>All members to work with Larry to fill out Cloud Printing spreadsheet<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-size:9.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>Start WG last call of Job Ticket document over holiday break (Working Group Last Call for PWG Print Job Ticket and Associated Capabilities specification ended January 8 2012)<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-size:9.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>Submit updated charter for SC approval (PENDING)<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-size:9.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>Continue Mapping of PWG Semantic Model elements into PPD, MSPS, and JDF formats (Best Practices Document)<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-size:9.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>Ira to work with Justin on MSPS mapping (PENDING)<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-size:9.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>Justin to work with Microsoft Legal on the appropriate citation/reference to MSPS based on the new license for inclusion with the MSPS content in the mapping document, and any process for the PWG to make a formal request (ONGOING)<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-size:9.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>Ron or Bill to post a call for wider participation of driver developers for the XPS/MSPS stuff (ONGOING)<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none'><![if !supportLists]><span style='font-size:9.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>Mike to make "first-index" in JPS3 1-based instead of 0-based (ONGOING - part of next update)<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-size:10.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:9.0pt;font-family:"Calibri","sans-serif"'>Mike to prepare new draft of PPD Mapping whitepaper (ONGOING)</span><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Ira to work with Justin on MSPS mapping<o:p></o:p></span></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>(4) Review <span style='color:#003300'>Job Ticket </span><span style='color:#1F497D'>Working Group last call comments (since this has not been done in MFD WG, and assuming that Pete and a reasonable number of commenters are in attendance))</span><o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#003300'>(5) </span><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Next Steps</span><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill Wagner, Cloud WG Vice Chair.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><p class=MsoNormal><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></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>