PS> Revised PSI conformance requirements draft (9 Sept)

PS> Revised PSI conformance requirements draft (9 Sept)

McDonald, Ira imcdonald at sharplabs.com
Tue Sep 9 14:11:38 EDT 2003


Hi folks,                                     Tuesday (9 September 2003)

Below is a second draft of section 10 "Conformance" for the PSI Spec,
revised after our partial review at today's PSI telecon.

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 7 October.

Changes to section 10.1 from first draft (26 August):
(1) Added new sentence to first paragraph (about documentation);
(2) Moved the first two requirements (documentation) in section 10.1
    to a new paragraph for product literature recommendations;
(3) Added new requirements and recommendations for XML and WSDL;
(4) Added three new 'Rationale' paragraphs to section 10.1
    (explaining the choices of requirement versus recommandation);
(5) Rewrote several requirements and recommendations for clarity.

Comments?

Cheers,
- Ira McDonald
  High North Inc

-----------------------------------------------

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

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 (publish URLs for) 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.


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 [WSDL1.2] or later WSDL versions;

(3) SHOULD support [SOAP1.2] or later SOAP versions;

(4) SHOULD support non-HTTP bindings of [SOAP1.1] or later SOAP
    versions;

(5) SHOULD support device discovery via the PSI Service Root URL
    as defined in section 5.1;

(6) SHOULD support device discovery for specific supported environments,
    for example using [SLP2.0];

(7) SHOULD support secure sessions over [TLS1.0] or later TLS versions,
    as defined in section 5.2;

(8) SHOULD support the ipp URL scheme for Target Devices,
    as defined in section 8.2.5;

(9) 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.


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

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 QueryEndPointsInterface,
    for access to PSI/1.0 Print Services and PSI/1.0 Target Devices,
    as defined in section 5.3;

(2) MUST 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) 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.3  PSI/1.0 Print Service Conformance

The following conformance REQUIREMENTS apply to a PSI/1.0 Print Service.
Every PSI/1.0 Print Service implementation:

(1) MUST 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) MUST 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) 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;

(4) 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;

(5) 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;

(6) 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;

(7) MUST support the server role in the TargetDeviceSupportInterface,
    for access from PSI/1.0 Target Devices,
    as defined in section 5.6.


10.4  PSI/1.0 Target Device Conformance

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 ServiceCapabilitesInterface,
    for access to PSI/1.0 Print Services,
    as defined in section 5.4;

(3) MUST support the client role in the JobControlInterface,
    for access to PSI/1.0 Print Services,
    as defined in section 5.5;

(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 the client role in the TargetDeviceSupportInterface,
    for access to PSI/1.0 Print Services,
    as defined in section 5.6.



More information about the Ps mailing list