Hi!
I am not an active participant of this forum and I have limited experience
in printing domain. However, I would like to express my views in this list.
>>we could also encourage greater interoperability and thereby make more
devices available to users
>>I would therefore cast this outline as a review of these aspects in extant
or imminent Cloud Printing implementations rather than giving the impression
that we intend to specify these things
I agree with the first statement. We have seen the difficulties of having
multitude of printer drivers in use today. If someone does not act now, the
same is going to happen with cloud. Right now Google has a cloud proxy and
it has its own protocol. Every other guy who enters this field is going to
float his own protocol, proxy/client apps (like our drivers) and other
specs. I feel PWG is the only forum which is in a position to do something
to prevent this from happening. However, if PWG just stops at reviewing what
is being used right now, it will not help us achieve the first aim. For
this, it is essential that PWG makes some specification, even though it
might be difficult to convince people like Google who are already in market.
But, I feel PWG should give it a try and while doing that they should review
the existing standards. However, this revision should be aimed at finding
and specifying the lowest common denominator that can be extended in future
with the cooperation of all the stake holders.
Regards,
Sarin
On Thu, Jan 20, 2011 at 10:32 PM, William Wagner <wamwagner at comcast.net>wrote:
> Michael,
>>>> Although this is a great outline, it may give the impression that the PWG
> were intending to develop a Cloud Printing specification; from recent
> comments, it is not clear that we are or can. Indeed, there are already
> various Cloud Printing implementations deployed. I think that we are agreed
> that the PWG would like the basic printing semantics to be consistent with
> the PWG model, regardless of the implementation; this would not only provide
> a more consistent print capability for users, it would facilitate making the
> actual printers compatible with the various implementations. Hopefully, we
> could also encourage greater interoperability and thereby make more devices
> available to users (thereby increasing printer use).
>>>> We have already stated what we consider to be the basic characteristics of
> Cloud Printing. I think the next steps are to better understand the various
> implementations and consider, from the printer perspective, to what extent
> the semantics are or can be made consistent with the PWG model, and perhaps
> what must be added to the model. I would therefore cast this outline as a
> review of these aspects in extant or imminent Cloud Printing implementations
> rather than giving the impression that we intend to specify these things.
> Certainly, after we understand what has/is being done, we can consider from
> a printing viewpoint, to what extent they are compatible with the PWG model,
> what other solutions we might consider more compatible for interoperability,
> and indeed where our model may need to be improved.
>>>> Thanks,
>> Bill Wagner
>> *From:* cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] *On Behalf Of
> *Michael Sweet
> *Sent:* Wednesday, January 19, 2011 11:42 PM
> *To:* cloud at pwg.org> *Subject:* [Cloud] Draft agenda/slide outline for February Cloud Printing
> BOF
>>>> All,
>>>> In the interests of making the next Cloud Printing BOF as productive and
> useful as possible, here is a draft agenda/slide outline for the February
> face-to-face. Please provide feedback no later than January 27, 2011 so we
> have time to finalize the slides.
>>>> Thank you!
>>>> Agenda/slide outline:
>>>> 1. Summary of functional model
>>> - Client
> - Cloud Print Provider
> - Cloud Print Manager
> - Printer
>>> 1. Requirements
>>> - Registration/discovery/selection
> - Job tickets
> - Document data/formats
> - Fidelity/late transforms
> - Event notification
> - Encryption for privacy/security
> - Logging/accounting
> - Firewall/router/network traversal
>>> 1. Attributes
>>> - Geolocation information
> - Job, printer, and subscription UUIDs
> - Various types of credentials
>>> 1. Document formats
>>> - CUPS Raster
> - HTML/XHTML
> - JPEG
> - PDF
>>> 1. Protocols
>>> - HTTP
> - IPP
> - JSON
> - REST
> - SMTP
> - SOAP
> - WSDL
> - XMPP
>>> 1. Next steps
>>> - Do we have more to talk about?
>>> - If so, more BOFs or is there sufficient interest and participation
> for a dedicated Cloud Printing WG?
>>> - Are we going to write any standards or recommendations?
>>> - If so, what working group(s)?
>>>> ________________________________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>> --
> 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.
>> _______________________________________________
> cloud mailing list
>cloud at pwg.org>https://www.pwg.org/mailman/listinfo/cloud>>
--
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/20110121/45b18028/attachment-0001.html>