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: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 WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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='color:#1F497D'>Many thanks for these suggestions and the discussion. I think, considering Glen’s argument, that it might be better to start with considering what actors are responsible for these actions rather than defining new actors. For example:<o:p></o:p></span></p><p class=MsoNormal>User access to device and features: Joe suggests that we have already considered this as out of scope for the print model, with questions of user identification and authorization implemented by other aspects of the Cloud Environment. Presumably, by the PWG Cloud Imaging model, the client connection with the Cloud Service establishes what Cloud Print Servers the user can access, and what end services he can use. Therefore, although it may be any one of several actors that is responsible for defining access rights, none of the components of the PWG Model should be defined as responsible for enforcing them; rather it becomes part of the Cloud Environment requirements (functional requirements) and must be clearly stated in those requirements. If this is agreed to, the question to be considered here is conditional access rights…access limited to certain functions, quantities, or times.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I would say that authorization or selection of:<o:p></o:p></p><p class=MsoNormal style='text-indent:.5in'>cloud services or connections <o:p></o:p></p><p class=MsoNormal style='text-indent:.5in'>Administrator access to device, logs, and other user controls <o:p></o:p></p><p class=MsoNormal style='text-indent:.5in'>Accounting functions <o:p></o:p></p><p class=MsoNormal>Are probably appropriate actions for the administrator of the Print Manager…or maybe someone else. But I don’t think that these are part of the Cloud Printing model. These too are part of the environment and should be included in Functional requirements but I don’t think that we need to define the actor.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For the Cloud Service administrator, again I suggest that these configuration operation are all out of scope for the model, although they should be identified in the Function requirements section. And as such, it is not necessary to identify a Cloud Service Administrator actor<span style='color:#1F497D'> .<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Having indicated that I do not think that these actors need be identified, I would ask Larry if he added them since he needed them for the sequence diagrams or other parts of section 4.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bill W.<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"'> cloud-bounces@pwg.org [mailto:cloud-bounces@pwg.org] <b>On Behalf Of </b>larryupthegrove<br><b>Sent:</b> Wednesday, February 06, 2013 12:46 PM<br><b>To:</b> cloud@pwg.org<br><b>Subject:</b> [Cloud] new actors summary<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/New Actors.pdf">ftp://ftp.pwg.org/pub/pwg/cloud/white/New Actors.pdf</a><o:p></o:p></p><p class=MsoNormal><a href="ftp://ftp.pwg.org/pub/pwg/cloud/white/New Actors.docx">ftp://ftp.pwg.org/pub/pwg/cloud/white/New Actors.docx</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>New Actors<o:p></o:p></p><p class=MsoNormal>Device Owner – the person(s) or entity responsible for the authorization or selection of:<o:p></o:p></p><p class=MsoNormal>1. Any cloud services or connections (apply to IPP)<o:p></o:p></p><p class=MsoNormal>2. User access to device and features<o:p></o:p></p><p class=MsoNormal>3. Administrator access to device, logs, and other user controls<o:p></o:p></p><p class=MsoNormal>4. Accounting functions<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cloud Service Administrator – on behalf of the Device Owner, performs operations to:<o:p></o:p></p><p class=MsoNormal>1. Configures device access controls for use by Cloud Service – should be with<o:p></o:p></p><p class=MsoNormal>2. Configures device for Cloud Print Service access<o:p></o:p></p><p class=MsoNormal>3. Can start, stop , or modify all queues at the cloud service<o:p></o:p></p><p class=MsoNormal>4. Can retrieve any logs from the cloud service<o:p></o:p></p><p class=MsoNormal>5. Accounting configurations<o:p></o:p></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>