Hey All..
I would like to review the following two things at tomorrows conference
call. We missed reviewing them on Friday...
Thanks!
Dave
Section 6.1 TargetDeviceIdentifier
- Change the introductory paragraph to be:
The Target Device Identifier allows for Clients to specify legacy Target
Devices as well as new PSI capable Target Devices. It is up to the Print
Service to provide the proxy support for that legacy device if it so
chooses.
The TargetDeviceIdentifier is specified by a URL. The client is allowed to
specify any existing, or yet to be defined URL schemes that refer to a
potential Target Device. Below is a list of existing URL schemes that
should be taken into consideration when implementing a Print Service.
A Print Service must support the PSI Service Root URL Target Device
Identifier. <-- do we need a statement to this effect?
Section 6.1.4:
Should be named psiServiceRootURL
Examples:
pwg-psips://MyPsiServiceTarget.mydomain.com:psi-port/psi/<version>
pwg-psitd://MyPsiTargetDeviceTarget.mydomain.com:psi-port/psi/<version>
Notes:
(1) REQUIRED 'host' or 'ip-addr' MUST be specified
(2) REQUIRED 'port' MUST default to PWG PSI IANA-assigned value
(example assumes port 'psi-port')
If a Print Services whishes to expose a proxy PSI TargetDevice for a legacy
Target Device, it may do so by adding appropriate query parameters to the
psiServiceRootURL which would allow the Print Service to identify that the
client has discovered, and is wishing to utilize the legacy Target Device.
This query parameter is:
* LegacyTargetDeviceID
Example:
pwg-psitd://mypsitarget.mydomain.com:psi-port/psi/<version>?LegacyTargetDevi
ceID=132452523