Hi folks, Monday (22 September 2003)
Below is a third draft of section 10 "Conformance", revised per our
review at today's PSI telecon, to be folded into the PSI Spec.
Dave Hall now plans to get a completed draft of the PSI spec out by 26
September, for review at the PWG face-to-face in New York on Tuesday
(7 October). We plan to have _all_day_ dial-in to the PSI face-to-face.
Dave - the issues are labelled 'ISSUE[01/02/03]' - please fixup numbers.
Dave - MOST conformance requirements/recommendations in all other spec
sections (like 5.x) should probably be DELETED - so that the conformance
is specified in accurate detail in sections 10.x only.
Comments?
Cheers,
- Ira McDonald
High North Inc
-----------------------------------------------
Changes for third draft (22 Sept) from second draft (9 Sept):
(1) Divided section 10.1 into 10.1.1, 10.1.2, 10.1.3, for clarity;
(2) Added two issues to section 10.1.1 about pwg-psixx and http URLs;
(3) Removed reference to WSDL/1.2 from section 10.1.2 item(2), per Jerry
Thrasher comment that the next WSDL version may in fact be 2.0;
(4) Moved former section 10.1.2 item (5) (PSI Service Root URL) and
divided into sections 10.2, 10.3, 10.4, per PSI telecon concensus;
(5) Reworded current section 10.1.2 item (5) (specific device discovery)
to replace reference to SLP/2.0 with "Windows, Netware...".
(6) Divided section 10.2 into 10.2.1 and 10.2.2, for clarity;
(7) Moved former section 10.2 items (1) and (2) to section 10.2.2,
per PSI telecon concensus;
(8) Added one issue to section 10.2.2 about QueryEndpointsInterface;
(9) Divided section 10.3 into 10.3.1 and 10.3.2, for clarity;
(10) Moved former section 10.3 items (1), (2), (3) to section 10.3.2,
per PSI telecon concensus;
(11) Divided section 10.4 into 10.4.1 and 10.4.2, for clarity;
(12) Moved former section 10.4 item (2) to section 10.4.2,
per PSI telecon concensus.
-----------------------------------------------
10. Conformance
This section specifies the conformance requirements (necessary for basic
interoperability) and conformance recommendations (useful for improved
interoperability) for all implementations of the PSI/1.0 protocol. This
section also specifies the conformance recommentations for PSI product
literature (useful for informed customer purchasing decisions).
10.1 PSI/1.0 Common Conformance
10.1.1 PSI/1.0 Common Implementation Requirements
The following common conformance REQUIREMENTS apply to every PSI/1.0
implementation (Client, Print Service, or Target Device). Every PSI/1.0
implementation:
(1) MUST support (produce and consume) valid [XML1.0] documents;
(2) MUST support (produce and/or consume) valid [WSDL1.1] interfaces;
(3) MUST support (produce and consume) valid [SOAP1.1] messages;
(4) MUST support the [HTTP/1.1] binding of [SOAP/1.1];
(5) MUST support the Printer Object and all mandatory elements,
as defined in section 7.1;
(6) MUST support the Job Object and all mandatory elements,
as defined in section 7.2;
(7) MUST support the Document Object and all mandatory elements,
as defined in section 7.3;
(8) MUST support pwg-psips and pwg-psitd URL schemes for Target Devices,
as defined in section 8.2.4;
(9) MUST support the http URL scheme for References,
as defined in section 8.3.1.
Rationale: Customers should be able to purchase PSI-based products
with basic interoperability guaranteed for those PSI products.
ISSUE 01: Should item (8) above (pwg-psips/td target device URL
support) be changed to SHOULD (recommendation), because the first PSI
Print Services will only talk to Target Devices (printers) via existing
print protocols (IPP, LPR, etc.).
ISSUE 02: Should item (9) above (http reference URL support) be changed
to SHOULD (recommendation), at least for PSI Clients (so that reference
printing need not be implemented by clients).
10.1.2 PSI/1.0 Common Implementation Recommendations
The following common conformance RECOMMENDATIONS apply to every PSI/1.0
implementation (Client, Print Service, or Target Device). Every PSI/1.0
implementation:
(1) SHOULD support [XML1.1] or later XML versions;
(2) SHOULD support later WSDL versions;
(3) SHOULD support [SOAP1.2] or later SOAP versions;
(4) SHOULD support non-HTTP bindings (SMTP, BEEP, etc.) of [SOAP1.1] or
later SOAP versions;
(5) SHOULD support native device discovery for the implementation's
supported environments (Windows, NetWare, UNIX, Linux, etc.);
(6) SHOULD support secure sessions over [TLS1.0] or later TLS versions,
as defined in section 5.2;
(7) SHOULD support the ipp URL scheme for Target Devices,
as defined in section 8.2.5;
(8) SHOULD support the ftp URL scheme for References,
as defined in section 8.3.2.
Rationale: Customers should be able to purchase PSI-based products
with improved interoperability probable for those PSI products.
10.1.3 PSI/1.0 Common Literature Recommendations
The following common conformance RECOMMENDATIONS apply to product
literature. All products that claim PSI/1.0 conformance:
(1) SHOULD publish the role-independent checklist of conformance claims,
as defined in applicable paragraphs of this section 10.1 above,
in installation, packaging, or other literature (e.g., Web pages);
(2) SHOULD publish the role-specific checklist of conformance claims,
as defined in applicable sections 10.2, 10.3, and/or 10.4 below,
in installation, packaging, or other literature (e.g., Web pages).
Rationale: Customers should be able to purchase PSI-based products
with specific interoperability verified for those PSI products.
10.2 PSI/1.0 Client Conformance
10.2.1 PSI/1.0 Client Requirements
The following conformance REQUIREMENTS apply to a PSI/1.0 Client.
Every PSI/1.0 Client implementation:
(1) MUST support the client role in the JobControlInterface,
for access to PSI/1.0 Print Services and PSI/1.0 Target Devices,
as defined in section 5.5.
10.2.2 PSI/1.0 Client Recommendations
The following conformance RECOMMENDATIONS apply to a PSI/1.0 Client.
Every PSI/1.0 Client implementation:
(1) SHOULD support the client role in the QueryEndPointsInterface,
for access to PSI/1.0 Print Services and PSI/1.0 Target Devices,
as defined in section 5.3;
(2) SHOULD support the client role in the ServiceCapabilitesInterface,
for access to PSI/1.0 Print Services and PSI/1.0 Target Devices,
as defined in section 5.4;
(3) SHOULD support device discovery via the PSI Service Root URL
as defined in section 5.1.
ISSUE 03: Should item (1) above (QueryEndPointsInterface) be changed
to MUST (requirement), because dynamic discovery of JobControlInterface
may not be easy without this additional step
10.3 PSI/1.0 Print Service Conformance
10.3.1 PSI/1.0 Print Service Requirements
The following conformance REQUIREMENTS apply to a PSI/1.0 Print Service.
Every PSI/1.0 Print Service implementation:
(1) MUST support the server role in the QueryEndPointsInterface,
for access from PSI/1.0 Clients and PSI/1.0 Target Devices,
as defined in section 5.3;
(2) MUST support the server role in the ServiceCapabilitesInterface,
for access from PSI/1.0 Clients and PSI/1.0 Target Devices,
as defined in section 5.4;
(3) MUST support the server role in the JobControlInterface,
for access from PSI/1.0 Clients and PSI/1.0 Target Devices,
as defined in section 5.5;
(4) MUST support the server role in the TargetDeviceSupportInterface,
for access from PSI/1.0 Target Devices,
as defined in section 5.6;
(5) MUST support device discovery via the PSI Service Root URL
as defined in section 5.1.
10.3.2 PSI/1.0 Print Service Recommendations
The following conformance RECOMMENDATIONS apply to a PSI/1.0 Print
Service. Every PSI/1.0 Print Service implementation:
(1) SHOULD support the client role in the QueryEndPointsInterface,
for access to PSI/1.0 Print Services and PSI/1.0 Target Devices,
as defined in section 5.3;
(2) SHOULD support the client role in the ServiceCapabilitesInterface,
for access to PSI/1.0 Print Services and PSI/1.0 Target Devices,
as defined in section 5.4;
(3) SHOULD support the client role in the JobControlInterface,
for access to PSI/1.0 Print Services and PSI/1.0 Target Devices,
as defined in section 5.5.
10.4 PSI/1.0 Target Device Conformance
10.4.1 PSI/1.0 Target Device Requirements
The following conformance REQUIREMENTS apply to a PSI/1.0 Target Device.
Every PSI/1.0 Target Device implementation:
(1) MUST support the client role in the QueryEndPointsInterface,
for access to PSI/1.0 Print Services,
as defined in section 5.3;
(2) MUST support the client role in the JobControlInterface,
for access to PSI/1.0 Print Services,
as defined in section 5.5;
(3) MUST support the client role in the TargetDeviceSupportInterface,
for access to PSI/1.0 Print Services,
as defined in section 5.6;
(4) MUST support the server role in the QueryEndPointsInterface,
for access from PSI/1.0 Clients and PSI/1.0 Print Services,
as defined in section 5.3;
(5) MUST support the server role in the ServiceCapabilitesInterface,
for access from PSI/1.0 Clients and PSI/1.0 Print Services,
as defined in section 5.4;
(6) MUST support the server role in the JobControlInterface,
for access from PSI/1.0 Clients and PSI/1.0 Print Services,
as defined in section 5.5;
(7) MUST support device discovery via the PSI Service Root URL
as defined in section 5.1.
10.4.2 PSI/1.0 Target Device Recommendations
The following conformance RECOMMENDATIONS apply to a PSI/1.0 Target
Device. Every PSI/1.0 Target Device implementation:
(1) SHOULD support the client role in the ServiceCapabilitesInterface,
for access to PSI/1.0 Print Services,
as defined in section 5.4.
This archive was generated by hypermail 2b29 : Mon Sep 22 2003 - 15:09:12 EDT