[Cloud] Updated Mapping and Model Drafts

[Cloud] Updated Mapping and Model Drafts

Petrie, Glen glen.petrie at eitc.epson.com
Thu Jun 7 18:34:25 UTC 2012


Bill,

 

Attached is my version of the model.

 

Glen

 

 

________________________________

From: Petrie, Glen 
Sent: Thursday, June 07, 2012 9:05 AM
To: Petrie, Glen; 'William A Wagner'; '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] On Behalf Of
Petrie, Glen
Sent: Thursday, June 07, 2012 7:16 AM
To: William A Wagner; 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 pwg.org [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
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, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/cloud/attachments/20120607/76d2c6de/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: just model.zip
Type: application/x-zip-compressed
Size: 166880 bytes
Desc: just model.zip
URL: <http://www.pwg.org/pipermail/cloud/attachments/20120607/76d2c6de/attachment.bin>


More information about the cloud mailing list