Hi Mike,
The MFD Model and Common Semantics does not define Output Device (it should)
and some may take it to mean something like a dumb printer. I believe that
SM assiduously avoids any reference to the interface between the Service and
the Output Device. Rather, it deals with the Client-<service>Service
interface, and that can be extended to a Service-Service interface in the
case of a superior (pr Primary) Service feeding other <service>Services (as
you indicate). I would suggest that Multifunction Device (MFD), which is
defined as "A hardware entity that supports one or more Imaging Services,
including the System." Be used in place of Output Device. I also question
the first sentence. I suggest:,
The MFD Model and Common Semantics [PWG5108.01] defines the semantics of the
interface between a Client and an Imaging Service, including one contained
in a Multifunction Device (MFD) such as a Printer. When a primary Service,
acting as a Client to the service within an MFD, has network accessibly to
the MFD, the existing Semantic Model interface applies. However, when the
MFD is not network accessible to a primary Service, a new interface is
required that allows the MFD to retrieve and update Jobs and Documents, as
well as provide current status and configuration of the MFD to the Service.
This specification defines a new printing interface between a Semantic Model
MFD and a Service to support situations where the MFD is not network
accessible to the Service. While the focus of this specification is on
Cloud-based Services, the same interface can be used in any situation where
the MFD is not network accessible to the Service, as is common in many
secure and multi-homed network environments. For example, a gateway Service
might use the printing interface defined by this specification to provide
guest printing from an open Wi-Fi network to a secure corporate LAN.
Thanks,
Bill Wagner
From: cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] On Behalf Of
Michael Sweet
Sent: Sunday, March 17, 2013 4:17 PM
To: cloud at pwg.org
Subject: [Cloud] Proposed introduction text for Cloud Print Requirements and
Model
All,
Here is my proposed introductory text for the Cloud Print Requirements and
Model. I chose to stick with Semantic Model terminology for the
introduction since the corresponding Cloud Print terms are not yet
introduced...
The PWG Semantic Model supports Output Devices that operate separately from
the corresponding Service. The MFD Model and Common Semantics [PWG5108.01]
defines the outward-facing semantics of this interface to ensure conformance
to the model. However, it does not define the interface between the Service
and the Output Device. When the Output Device is network accessible to the
Service, the existing Semantic Model interface can be used with the primary
Service acting as a Client to the Output Device's Service. However, when the
Output Device is not network accessible to the Service, a new interface is
required that allows the Output Device to retrieve and update Jobs and
Documents, as well as provide current status and configuration of the Output
Device to the Service.
This specification defines a new printing interface between a Semantic Model
Output Device and Service to support situations where the Output Device is
not network accessible to the Service. While the focus of this specification
is on Cloud-based Services, the same interface can be used in any situation
where the Output Device is not network accessible to the Service, as is
common in many secure and multi-homed network environments. For example, a
gateway Service might use the printing interface defined by this
specification to provide guest printing from an open Wi-Fi network to a
secure corporate LAN.
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
This message has been scanned for viruses and
dangerous content by <http://www.mailscanner.info/> MailScanner, 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/20130318/4c364c52/attachment-0002.html>