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=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;}
/* 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";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
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;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle29
{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:2092967940;
mso-list-type:hybrid;
mso-list-template-ids:710306268 -1085219508 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Tahoma","sans-serif";
color:windowtext;}
@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:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Here is an update on the tasks (as of 3/15/2013)</span><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">On 2/25/2013, we captured a list of</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> items
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">that need to be done within the
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">SM WG. Items 8,9,10 were added
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">on 2/27.</span><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="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Reduced (optimal) element set for Print Job Ticket – Glen Petrie worked on this document and submitted it to WG.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">Update: (from Bill Wagner) This has been addressed in the Cloud WG, although the way in which it may be used was not agreed to.<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:"Tahoma","sans-serif""><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">JSON binding that reflects the optimal element set for PJT – Pete indicated that samples (examples in XML and JSON) exist in the present Print Ticket
standard – PJT. These samples may not comprise the fully optimal set noted in item 1 above.<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:"Tahoma","sans-serif""><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Simplified scan and resource job tickets and capabilities spec to correspond to Google Job Ticket Specification.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">Update: (from Bill Wagner) Michael Sweet’s action item to send this to Google, as discussed in the Cloud WG.
<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:"Tahoma","sans-serif""><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Scan Service 2.0 – The Scan Service Spec 1.0 was completed in the MFD WG, before the Semantic Model was created. Hence some work on co-relating Scan
Service 1.0 more to the common model is needed. Also, co-relating to things discovered during the binding work on IPP Scan when IPP WG does the IPP Scan work. Note that since Google is pushing towards Cloud Scan either (Cloud Scan Job Ticket + Capabilities)
or an (Imaging Job Ticket + Capabilities) should be part of the WG.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">Action Item: Daniel to check with Nancy on version 1.0. – done. Update: The Scan Service 2.0 Spec can be easily aligned with the MFD Common SM Spec. Of higher priority is
the IPP Scan Spec which does not use any model element names from the Scan Service Spec. It is better to rewrite IPP Scan Spec to be aligned with the MFD Scan Service Spec. (comment from Bill Wagner) – The Scan Service 1.0 was completed not before the Semantic
Model was created as noted above, but before the Model and Common Semantics Specification was Approved.<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:"Tahoma","sans-serif""><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Resource Service 2.0 - The Resource Service Spec 1.0 was completed in the MFD WG, before the Semantic Model was created. Hence some work on co-relating
Resource Service 1.0 more to the common model is needed. Security on the Resources in a Cloud and Enterprise Environment must be considered. Note that since Google is pushing towards Cloud Resource either (Cloud Resource Job Ticket + Capabilities) should
be part of the WG</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">. – Action Item: Daniel to check with Nancy on version 1.0 – done. Update: The Resource Service 2.0 Spec can be easily aligned with the MFD Common SM Spec.
(comment from Bill Wagner) – The Scan Service 1.0 was completed not before the Semantic Model was created as noted above, but before the Model and Common Semantics Specification was Approved.<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:"Tahoma","sans-serif""><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Print Service 2.0 - (Get a good clean draft of the Print Service Spec 2.0; then update the Common Semantic Model; then get both approved) – No one
yet had agreed to work on the Print Service 2.0 draft. Bill Wagner has volunteered to update the Common Semantic Model.<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:"Tahoma","sans-serif""><span style="mso-list:Ignore">7.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Fax In Service – Ira McDonald to work on the draft. It is still outstanding.
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">– Update</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">:
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">Action Item: Daniel to touch base with Ira about when he will present the draft.<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:"Tahoma","sans-serif""><span style="mso-list:Ignore">8.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Transform Service 1.0 - Decide how to schedule moving Transform Service 1.0 through the PWG SM Workgroup process to get the document finished. The
Transform Service 1.0 needs use case and design requirements sections added. Typically a draft is developed and then everyone attending a bi-weekly teleconference gives input while the sections in question are reviewed page by page. Edits are collected and
then a new draft is published. Once the document seems relatively stable and no further work is deemed appropriate by the SM Working Group a working group last call is issued</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">.
– Update: Discuss the Transform Service 1.0 specification on Monday, 22 Apr. 2013 SM WG meeting (Paul will be at the AFP consortium on 8 Apr. 2013).<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:"Tahoma","sans-serif""><span style="mso-list:Ignore">9.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Cloudmap 1.0 - Decide how to schedule moving Cloudmap 1.0 document through the PWG SM workgroup review process so that it can begin its approval process.
Document is ready for a full review of the Microsoft section in a bi-weekly teleconference.
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">– Update</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">:</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">
Discuss the Cloudmap 1.0 specification on Monday,</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">25 Mar. 2013. (comment from Bill Wagner) – the last WD is dated Aug. 2012. We need an updated version posted if we need a review</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red">.
Action Item: Paul Tykodi.<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:"Tahoma","sans-serif""><span style="mso-list:Ignore">10.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Joint meeting with AFP Consortium - Coordinate with AFP Consortium about a date to review the initial white paper. Paul Tykodi to upload the document
to the White Paper folder in the MFD section of the FTP site. URL will be posted after the document is uploaded. Paul has not received any feedback from the AFP Consortium about reviewing the document since he sent them the idea to discuss on March 11<sup>th</sup>.
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">– Update</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">:</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">The next AFP Consortium meeting will be held Apr 8-11, 2013; Paul Tykodi</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">will be presenting an overview of PWG as well as SM on Apr. 11 (Boulder, CO), and how the SM helps in cloud printing. Paul will be presenting an initial version of the mapping
document (IPDS and MO:DCA-P– PWG PJT).</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#7030A0">(comment from Bill Wagner) – I do not see the referred white paper. I am a little confused by the objective. Harry was chair of the PWG for many years and is fully familiar
with the PWG. He might need some update on where the semantic model has gone, and we may need some help with the AFP protocols. But this does not seem to be a critical path item for the SM group.</span><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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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>