Proposed Conformance Clauses for RSP1.0

[Jacques Durand <JDurand@us.fujitsu.com>]

 

Proposed Conformance Clauses for RSP1.0:

 

 

 

1.1 Conformance Clauses

This Profile concerns several conformance targets. Conformance targets are identified in requirements as described in Section 2.2.

This Profile is an extension of the Basic Profile (1.2 or 2.0) and therefore conformance to this profile should always be mentioned or claimed in conjunction with a mention or claim about which one of the basic profile (V1.2 or V2.0) is used as foundation, as well as which level of conformance is used for the Basic Profile (CORE or HTTP_TRANSPORT).

 

In addition, to claim conformance to this Profile, a deployed INSTANCE target must support one or more of the WS-ReliableMessaging (WS-RM), WS-SecureConversation (WS-SC), or WS-MakeConnection (WS-MC) protocols, either individually or in some combination thereof, in a manner that conforms to the requirements set forth in this profile.

The four conformance clauses for RSP1.0 reflect the various ways this profile can use the underlying Basic Profile.

1.1.1 Core Conformance based on BP1.2

A conformance target (as defined above) is said to be conforming to this profile over BP1.2 at the “core” conformance level if both conditions below are satisfied:

(a)   this target is conforming with BP1.2 at Core level,

(b)   this target fulfills all the RESP1.0 requirements that are relevant to this target type and also relevant to the combination of WS specifications claimed to be supported (among WS-ReliableMessaging (WS-RM), WS-SecureConversation (WS-SC), and  WS-MakeConnection)

 

Therefore, claims for “Core conformance based on BP1.2” should also mention the subset of WS specifications supported by the INSTANCE involved.

1.1.2 HTTP-transport Conformance based on BP1.2

A conformance target (as defined above) is said to be conforming to this profile over BP1.2 at the “HTTP-transport” conformance level if both conditions below are satisfied:

(a)   this target is conforming with BP1.2 at HTTP-transport level,

(b)   this target fulfills all the RESP1.0 requirements that are relevant to this target type and also relevant to the combination of WS specifications claimed to be supported (among WS-ReliableMessaging (WS-RM), WS-SecureConversation (WS-SC), and  WS-MakeConnection)

 

Therefore, claims for “HTTP-transport conformance based on BP1.2” should also mention the subset of WS specifications supported by the INSTANCE involved.

 

1.1.3 Core Conformance based on BP2.0

A conformance target (as defined above) is said to be conforming to this profile over BP2.0 at the “core” conformance level if both conditions below are satisfied:

(a)   this target is conforming with BP2.0 at Core level,

(b)   this target fulfills all the RESP1.0 requirements that are relevant to this target type and also relevant to the combination of WS specifications claimed to be supported (among WS-ReliableMessaging (WS-RM), WS-SecureConversation (WS-SC), and  WS-MakeConnection)

 

Therefore, claims for “Core conformance based on BP2.0” should also mention the subset of WS specifications supported by the INSTANCE involved.

1.1.4 HTTP-transport Conformance based on BP2.0

A conformance target (as defined above) is said to be conforming to this profile over BP2.0 at the “HTTP-transport” conformance level if both conditions below are satisfied:

(a)   this target is conforming with BP2.0 at HTTP-transport level,

(b)   this target fulfills all the RESP1.0 requirements that are relevant to this target type and also relevant to the combination of WS specifications claimed to be supported (among WS-ReliableMessaging (WS-RM), WS-SecureConversation (WS-SC), and  WS-MakeConnection)

 

Therefore, claims for “HTTP-transport conformance based on BP2.0” should also mention the subset of WS specifications supported by the INSTANCE involved.

 

 

-jacques