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)"><base href="x-msg://27/"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:Consolas;
panose-1:2 11 6 9 2 2 4 3 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.apple-converted-space
{mso-style-name:apple-converted-space;}
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-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:1466000810;
mso-list-type:hybrid;
mso-list-template-ids:-211648214 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
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'>Hi Randy,<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 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><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'>Since it was decided that a Cloud Imaging Service could be associated with more than one device, we had to model a way to register a Device service with a pre-existing Cloud Service. There seemed no advantage in also modeling a mode where registering a device created the Cloud imaging service.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><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'>It was maintained that a device owner may not want to register all capabilities of a device. He may want to restrict registration to specific services or even elements of specific services. Therefore, the model should (and does) accommodate this. <o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>a.<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'>If a device owner wishes to register all parts of all services of a device with the corresponding services of a Cloud Imaging System, all he need do is inform the Proxy of the local device (if the proxy handles more than one) and the Cloud Imaging System. The Update System Elements and Update Service Elements operations are ones the Proxy needs to exercised once registration is complete anyway and, if the Proxy/Device interface is semantic model compatible (e.g. IPP), the Proxy easily obtains the information in these operations (as well as the List Services) by existing interface operations. I doubt that from the Owners viewpoint that it could be simpler.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>b.<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'> If the Owner wishes to limit what Device and/or Service elements he is registering, the registering application would list the Device and Service elements to allow the Owner to flag what should not be made accessible to the Cloud System.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><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'>Outlining a UI is out of scope for the spec, but I could envision something like the following:<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>a.<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'>Owner connects to the Proxy. Proxy returns identification of devices it supports and requests desired action. User indicates Registration with Cloud Imaging System<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>b.<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'>Proxy requests address of Cloud Imaging System and the ID of the Devices to be registered. User provides this (plus security access info if needed)<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>c.<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'>Proxy contacts Cloud Imaging System and (if successful) returns to User the basic characteristics of the Cloud Imaging System, including supported Cloud Imaging Services. It also lists the Services in each of the devices to be registered and asks that the Owner identify which device services are to be associated with which Cloud Imaging Services. There is a ‘default’ choice which, in a simple case, merely associates each device service with each corresponding Cloud Imaging Service. Alternately, the Owner may show an A-A, B-B, D-D relation, omitting Device Services that are not to be made accessible. <o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>d.<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'>Proxy then asks if there are Service elements that are not to be made accessible (reasonably listing typical elements for each service that may reasonable be limited) . Owner can answer NO, or he can mark what is not to be made accessible. He is done.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>e.<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'>Between this interchange and its communication with the device, Proxy has all it needs to complete the registration.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><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'>Indeed, we fully intend to pass the registration sequence, the normal Proxy/Cloud Service communication, the User /Cloud Service Communication, the access by reference operations, and various administrative interactions to IDS for security issue consideration.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><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'>I would expect the </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Transaction-Based Printing Extensions (previously Paid Printing) to reflect back into the Network Printing interface of the Semantic Model, and therefore into the Client/Service interaction of Cloud Imaging. The User submits a Job request to the Cloud Service. That service will need to consider the Users authorization (based on who they are, where they connect from, how good their credit is, whatever) to use both the Cloud Service and the desired features of the end device. The end device (through the Proxy) needs to report on the work done in conjunction with the resulting job, and we will need to consider what additional elements need to be included in the Cloud Service/Proxy interface. But I expect that the device does not get into authorization beyond what is necessary to obtain local user identification information (e.g., PIN, biometric data, etc) and send it to the Cloud Service.</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'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill Wagner<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><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>Randy Turner<br><b>Sent:</b> Friday, July 19, 2013 10:05 PM<br><b>To:</b> <cloud@pwg.org><br><b>Subject:</b> Re: [Cloud] Minutes posted from today's Cloud Imaging WG conference call<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Hi Bill,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>RE: Item #1 below, starting with "The Device Owner…" , it seems like a complicated interface and sequence of steps that the owner will have to take to register his device for cloud access. If I'm doing one imaging device, it might seem tractable. If I'm doing 20 or 30 heterogeneous devices, it seems excessive. Have we modeled how this might look for an administrator, like what would the UI look like, or what the admin experience would be?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>From Note 1b, I thought registration "caused" a corresponding cloud imaging service to be created? The device registers with some generic (non-specific) imaging cloud service, correct? and then once registered, the "corresponding" service is created. Or at least that's what I thought we were talking about at the last face-to-face.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>Also, from your "Note #2 below", It seems reasonable that the "Authorization" part of the cloud service is probably out of scope for the Cloud WG…but you've highlighted some examples of potential predicates for an authorization decision -- if anyone has any ideas regarding the types of authorization decisions that a service might want to make, I would urge the group to pass those along to the IDS team, especially whoever has the ball on a XACML dialect for imaging authorization.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I know that Mike has published the "Paid Extensions" stuff from IPP that uses some type of authorization ticket that says "I've paid for what I'm asking for", but I would hope that this type of authorization would be just another predicate check by a larger, overall authorization engine, and that there would be one (and only one) "Ok, we'll allow this operation" ticket or token that takes into account all authorization decisions (predicates, conditions, etc.)<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>R.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Jul 19, 2013, at 4:29 PM, William A Wagner <<a href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>As I generate a Registration section for the Cloud Imaging Model, I would like to verify my understanding of the decisions made at Monday's meeting.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div style='margin-left:.5in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>1.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>The Device Owner, operating through the Cloud Imaging Device Proxy that provides the cloud interface for the device, registers the device and the device services he wishes to make available to the Cloud Imaging System. He may desire to block access to specific Device elements and Service elements. In response to information provided by the Device owner to the Proxy:<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>a.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>The proxy provides Device registration information with an initial Update System Elements message to the Cloud System Control Service. This message provides information on all System Elements of the Device that are to be made known to the Cloud Imaging System. It corresponds to a response to a current Get System Elements message with all elements identified.<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>b.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>The Proxy identifies the Device Services that are to be accessible to the Cloud Imaging System by sending an Identify Services message to the Cloud System Control Service. This corresponds to a response to a current List Services operation.<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>c.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>The proxy identifies the elements of each Device Imaging Service that are to be made available to the corresponding Cloud Imaging Service by sending an initial Update Service Elements to an Owner-identified corresponding imaging service of the target Cloud Imaging System. This corresponds to a response to a current Get Service Elements operation.<o:p></o:p></span></p></div><div style='margin-left:.5in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>2.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Once Device and Service registrations are complete, the Proxy will maintain contact with the Cloud System Control Service and the registered Imaging services, updating System and Service Elements and checking Cloud Imaging Services for jobs.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>Note:<o:p></o:p></span></p></div><div style='margin-left:.5in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>1.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>It was decided that:<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>a.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Devices and Service are registered, not subunits<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>b.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Device Services can only be registered with corresponding Cloud Imaging Services<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>c.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Therefore: a Device subunit cannot be made accessible to a Cloud Imaging Service unless that subunit is configured as part of a Device Imaging Service that is registered with the Cloud Imaging Service. For example, a Cloud FaxIn Service can not use a marking engine in a Print Device unless that marking engine is also configured as part of a FaxIn service that is registered with the Cloud FaxIn Service. (This seems an unfortunate limitation to me.)<o:p></o:p></span></p></div><div style='margin-left:.5in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>2.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>It was agreed that the Owner will want to place restrictions on:<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>a.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Who can use the device, with respect to one or more of the following:<o:p></o:p></span></p></div><div style='margin-left:1.5in'><p class=MsoNormal style='text-indent:-1.5in'><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>i.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>User ID, possibly including results of authentication<o:p></o:p></span></p></div><div style='margin-left:1.5in'><p class=MsoNormal style='text-indent:-1.5in'><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>ii.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Geographical or network typological origin of the user<o:p></o:p></span></p></div><div style='margin-left:1.5in'><p class=MsoNormal style='text-indent:-1.5in'><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>iii.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Payment or credit<o:p></o:p></span></p></div><div style='margin-left:1.5in'><p class=MsoNormal style='text-indent:-1.5in'><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>iv.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Any one of various other conditions<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>b.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>What services a user can use<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>c.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>When each user can use what services (e.g., Print and Hardcopy Fax and Email only during working hours; FaxIn, EmailIn to storage all the time)<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>d.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Degree of use (e.g., max number of copies)for each particular user and Service<o:p></o:p></span></p></div><div style='margin-left:1.0in'><p class=MsoNormal style='text-indent:-.25in'><span style='font-size:10.5pt;font-family:Consolas'>e.</span><span style='font-size:7.0pt'> <span class=apple-converted-space> </span></span><span style='font-size:10.5pt;font-family:Consolas'>Probably other conditions<o:p></o:p></span></p></div><div style='margin-left:.5in'><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>The owner will communicate with the Cloud Imaging System with an “access list” to identify these User rights and restrictions. This process is out of scope for the Cloud Imaging Model.<o:p></o:p></span></p></div><div style='margin-left:.75in'><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>I would appreciate confirmation or correction of this understanding.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>Thanks,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>Bill Wagner<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>-----Original Message-----<br>From:<span class=apple-converted-space> </span><a href="mailto:cloud-bounces@pwg.org"><span style='color:purple'>cloud-bounces@pwg.org</span></a><span class=apple-converted-space> </span>[mailto:cloud-<a href="mailto:bounces@pwg.org"><span style='color:purple'>bounces@pwg.org</span></a>] On Behalf Of Michael Sweet<br>Sent: Monday, July 15, 2013 4:25 PM<br>To:<span class=apple-converted-space> </span><a href="mailto:cloud@pwg.org"><span style='color:purple'>cloud@pwg.org</span></a><br>Subject: [Cloud] Minutes posted from today's Cloud Imaging WG conference call<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>All,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>I have posted the minutes to today's Cloud Imaging WG conference call to:<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <span class=apple-converted-space> </span><a href="ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20130715.pdf"><span style='color:windowtext;text-decoration:none'>ftp://ftp.pwg.org/pub/pwg/cloud/minutes/cloud-concall-minutes-20130715.pdf</span></a><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>Our next conference call will be on July 29, 2013 at 3pm ET.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>_________________________________________________________<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>--<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>_______________________________________________<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'>cloud mailing list<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'><a href="mailto:cloud@pwg.org"><span style='color:windowtext;text-decoration:none'>cloud@pwg.org</span></a><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas'><a href="https://www.pwg.org/mailman/listinfo/cloud"><span style='color:windowtext;text-decoration:none'>https://www.pwg.org/mailman/listinfo/cloud</span></a><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'><br>--<span class=apple-converted-space> </span><br>This message has been scanned for viruses and<span class=apple-converted-space> </span><br>dangerous content by<span class=apple-converted-space> </span><a href="http://www.mailscanner.info/"><b><span style='color:purple'>MailScanner</span></b></a>, and is<span class=apple-converted-space> </span><br>believed to be clean. _______________________________________________<br>cloud mailing list<br><a href="mailto:cloud@pwg.org"><span style='color:purple'>cloud@pwg.org</span></a><br><a href="https://www.pwg.org/mailman/listinfo/cloud"><span style='color:purple'>https://www.pwg.org/mailman/listinfo/cloud</span></a><o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p></div></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>