[Cloud] Updated Mapping and Model Drafts

[Cloud] Updated Mapping and Model Drafts

[Cloud] Updated Mapping and Model Drafts

Murdock, Joe jmurdock at sharplabs.com
Fri Jun 8 19:21:12 UTC 2012


I don't agree with combine the Cloud Print Provider and the Cloud Print System Service functionality.

There is nothing to prevent, and actually a lot to recommend/require, a Cloud Print Provider from supporting multiple Cloud Print System Services, based on a variety of performance, contractual and legal agreements/reasons.  It is not unusual that a customer's requirement for a cloud service be that the customer's data never reside on or be processed on a service that does not reside in a specified country.  With a multinational Cloud Print Provider, this would necessitate they provide multiple Cloud Print System Services on multiple pieces of physical hardware that resides in multiple countries).  In this scenario, a user/company/printer/other service needs to have a well know endpoint to start with (the Cloud Print Provider), from which it can be redirect as necessary to the appropriate system service, and ultimately the proper print service, based on information associated with a user's account.  If we combine the Cloud Print Provider and the Cloud Print System Service this account-base separation and redirection is no longer possible.

I also don't like the idea of renaming the Cloud Print Provided as the Cloud Print Registry, as registering a printer is only a small portion of it job.  It does not register a user, rather it authenticates a user account that was previously setup via a marketing/sale organization.  It does not register a Cloud Print System Service, rather it creates one or more Cloud Print Systems as dictated by the same marketing/sales organizations (based on customer requirements), with additional input from an IT organization.  It does not even really register a printer, rather it creates a Cloud-based Printer Service to receive and handle jobs for that printer

And yes, of course the term "Printer" in all of these diagrams should really be read as "Imaging".  It may be appropriate to do that now, and just limit the scope of Imaging to be printing for now.


From: cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] On Behalf Of larryupthegrove
Sent: Thursday, June 07, 2012 2:44 PM
To: ptykodi at tykodi.com; 'Petrie, Glen'
Cc: cloud at pwg.org
Subject: RE: [Cloud] Updated Mapping and Model Drafts


Glen raises some interesting points for the next discussion.  The challenge is that the activities in the cloud are provider dependent, so there could be a wide variety of implementations.

I would like to leave client, but possibly add a cloud print client as part of the association.  Long term I could see cloud print provider becomes cloud imaging provider, and "print" gets replaced with "scan", "fax", etc.  Then we can reuse a lot of the diagrams and work.


I updated the sequence drawings, adding a Print sequence and an Enumeration sequence.

ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud%20Print%20sequence%20drawingsupdate20120607.pdf
ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud%20Print%20sequence%20drawingsupdate20120607.vsd


Larry Upthegrove


From: cloud-bounces at pwg.org<mailto:cloud-bounces at pwg.org> [mailto:cloud-bounces at pwg.org]<mailto:[mailto:cloud-bounces at pwg.org]> On Behalf Of Paul Tykodi
Sent: Thursday, June 07, 2012 1:05 PM
To: 'Petrie, Glen'
Cc: cloud at pwg.org<mailto:cloud at pwg.org>
Subject: RE: [Cloud] Updated Mapping and Model Drafts

Hi Glen,

I like your choice of the name registry. I find myself continually getting confused as to the actual tasks undertaken by some of the components that live within the Cloud in our current model.

At least for me, the use of the word registry really helped with the conceptual understanding.

Thanks.

Best Regards,

/Paul
--
Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile:  603-866-0712
E-mail:  ptykodi at tykodi.com<mailto:ptykodi at tykodi.com>
WWW:  http://www.tykodi.com<http://www.tykodi.com/>
From: cloud-bounces at pwgorg [mailto:cloud-bounces at pwg.org]<mailto:[mailto:cloud-bounces at pwg.org]> On Behalf Of Petrie, Glen
Sent: Thursday, June 07, 2012 12:05 PM
To: Petrie, Glen; William A Wagner; cloud at pwg.org<mailto:cloud at pwg.org>
Subject: RE: [Cloud] Updated Mapping and Model Drafts

Bill,

In fact, considering the functions of the Cloud Print System Service, the Cloud Print System Service should be called the Cloud Print Registry.   This is where the User, Print Services, Transforms, etc are registered.  It is the place where User-to-'Print Service' association is done.   It is the place where a lot of the security and access functionality is done (i.e User login, access token, etc.).   Now in the model diagram, the arrow going to the "cloud-boundary" now go the Cloud Print Registry.

[ I believe using system service in the name here will be a big problem later when we define an MFD and have the MFD system service.]

Glen


________________________________
From: Petrie, Glen
Sent: Thursday, June 07, 2012 7:46 AM
To: Petrie, Glen; 'William A Wagner'; 'cloud at pwg.org'
Subject: RE: [Cloud] Updated Mapping and Model Drafts

Bill,

Can the methods of the Cloud Print Provider be moved to the Cloud Print System Service; thus, leaving the Cloud Print Provider as an environment (basically, the collection of all Cloud Print entities in a specific cloud implementation).

Glen


________________________________
From: Petrie, Glen
Sent: Thursday, June 07, 2012 7:42 AM
To: Petrie, Glen; 'William A Wagner'; 'cloud at pwg.org'
Subject: RE: [Cloud] Updated Mapping and Model Drafts

Bill,

Comment on Cloud Print Provider.

In the current definition, the Cloud Print Provider is defined as an environment but then it methods.   If the Cloud Print Provider provides methods and can perform operations then it a software entity and not just an environment.

Glen


________________________________
From: cloud-bounces at pwg.org<mailto:cloud-bounces at pwg.org> [mailto:cloud-bounces at pwg.org]<mailto:[mailto:cloud-bounces at pwg.org]> On Behalf Of Petrie, Glen
Sent: Thursday, June 07, 2012 7:16 AM
To: William A Wagner; cloud at pwg.org<mailto:cloud at pwg.org>
Subject: RE: [Cloud] Updated Mapping and Model Drafts

Bill,

I was reviewing the definition of the Client and I believe the Client does not provide the association function.  It must be a Cloud entity, such as the Cloud Provider or the Cloud Print Provider (i.e. Google Cloud Print), that creates and maintains the association between the User and one or more Printers (Cloud Print Services).  The Client (acting as a proxy for the User) may or may-not actually display the list of User Associated Printer Service (i.e. the Client may be an embedded Client).


The Client is the software component that implements the interface between the User and the Cloud Print Provider to create an Association; and to enumerate available Cloud Print Services. The Client is also implements the interface between the User and the selected Cloud Print Service to submit a Print Job and to query Job and Printer Status.

I would like to suggest the following

The Client is the software proxy implementing an interface between the User and the Cloud Print Provider for selection of a specific Cloud Print Service from an enumeration list of User associated Cloud Print Services .  The Client provides an interface for setting job elements which are communicated with the specific Cloud Print Service  The Client obtains and provided the User with job queries and Printer status.

I would like to also suggest that we name "Client" as "Cloud Print Client" since this is a specific type of generic Client that provides the interface specifically between the User and the Cloud Print solution.

Glen


________________________________
From: cloud-bounces at pwgorg<mailto:cloud-bounces at pwg.org> [mailto:cloud-bounces at pwg.org]<mailto:[mailto:cloud-bounces at pwg.org]> On Behalf Of William A Wagner
Sent: Wednesday, June 06, 2012 7:34 PM
To: cloud at pwg.org<mailto:cloud at pwg.org>
Subject: [Cloud] Updated Mapping and Model Drafts

Interim level, definitely work-in-progress drafts reflecting considerations during the June face-to-face meeting are posted as follows:

ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmap10-20120604.pdf
ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmap10-20120604-rev.pdf
ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmap10-20120604-rev.docx

and
ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120606.pdf
ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120606-rev.pdf
ftp://ftp.pwg.org/pub/pwg/cloud/wd/wd-cloudmodel10-20120606-rev.docx

Note that un-redlined versions of MS Word documents may be obtained from redline versions.

Comments are appreciated.

Thanks,

Bill Wagner

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/cloud/attachments/20120608/13ad29c8/attachment-0002.html>


More information about the cloud mailing list