Dear
all,
OASIS TC
Administration provided among other feedback on the DSS profile for ebXML that
new standards work at OASIS needs a Conformance
section.
http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html
This
is an issue that other profiles will need to deal with too, so it is of interest
beyond the scope of the ebXML profile.
Below
is a proposed conformance section for the ebXML profile. It defines four
conformance clauses for four conformance targets. The idea is that some
implementations will support only client functionality but not server
functionality (or vice versa) and may support one version of ebXML messaging but
not the other.
Comments welcome.
Pim
1
Conformance
Any
implementation of this profile is not conformant with this specification if it
fails to satisfy one or more of the MUST or REQUIRED level requirements defined
in this specification.
An
implementation of this profile provides DSS client functionality, DSS server
functionality, or both DSS client and DSS server functionality.
An
implementation of this profile provides support for either version 2.0 or 3.0 of
the OASIS ebXML Messaging Service specification, or supports
both.
Any
implementation of this profile SHOULD support the DSS security binding described
in section 3.
1.1
Conformance as a DSS Client using ebMS
2.0
An
implementation of this profile conforms to this profile as a DSS Client
using ebMS 2.0 if it meets the following
requirements:
·
Supports sending of
SignRequest signature generation request messages and
VerifyRequest signature verification request messages with syntax
and semantics defined in section 2 of this specification.
·
Supports receiving of
SignResponse signature generation response messages and
VerifyResponse signature verification response message with syntax
and semantics defined in section 2 of this specification.
·
Supports version 2.0 of
the ebXML Messaging Service version 2.0 OASIS Standard [ebMS 2.0].
1.2
Conformance as a DSS Server using ebMS
2.0
An
implementation of this profile conforms to this profile as a DSS Server
using ebMS 2.0 if it meets the following
requirements:
·
Supports receiving of
SignRequest signature generation messages and
VerifyRequest signature verification messages with syntax and
semantics defined in section 2
of this specification.
·
Supports sending of
SignResponse signature generation messages and
VerifyResponse signature verification messages with syntax and
semantics defined in section 2
of this specification.
·
Supports version 2.0 of
the ebXML Messaging Service version 2.0 OASIS Standard [ebMS 2.0].
1.3
Conformance as a DSS Client using ebMS
3.0
The
conformance requirements for a DSS Client
using ebMS 3.0 are the same as for a DSS Client
using ebMS 2.0, except that it support version 3.0 of the ebXML
Messaging Service version 3.0 OASIS Standard [ebMS 3.0]
instead of version 2.0 [ebMS 2.0].
1.4
Conformance as a DSS Server using ebMS
3.0
The
conformance requirements for a DSS Server
using ebMS 3.0 are the same as for a DSS Server
using ebMS 2.0, except that it support version 3.0 of the ebXML
Messaging Service version 3.0 OASIS Standard [ebMS 3.0]
instead of version 2.0 [ebMS 2.0].
