TimeToPerform 2.0 excerpt for discussion at Feb 24 meeting

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

 

8.4.14.10 timeToPerform attribute

The timeToPerform attribute is of type duration [XMLSCHEMA-2]. It specifies the time period, starting from the initiation of the RequestingBusinessActivity, within which the initiator of the transaction MUST have received the response, i.e., the business document associated with the RespondingBusinessActivity.

 

NOTE: The timeToPerform attribute associated with a BinaryCollaboration in BPSS is currently not modeled in this specification. Therefore, it cannot be overridden. In other words, the value specified at the BPSS level MUST be used.

 

When synchronous reply mode is in use (see Section 8.4.23.1), the TimeToPerform value SHOULD be used as the connection timeout.

 

NOTE: See section 10.6 for a description of changes in the CPPA 2.1 schema made to the data type of the timeToPerform attribute to align with Process Specifications conforming to [ebBP].

 

 

Please post modified language for these sections that you would like to see in the 2.1 maintenance release.

 

I think that the above  language should be aligned with the new statement in the Chapter 10 on extensibility that notes (when discussing ebBP 2.0)

 

10.6.5 TimeToPerform

In [ebBP], the @timeToPerform attribute has been replaced by a TimeToPerform element that allows new means of specification of varying performance times for a BusinessTransaction. Therefore, the content model for both MessagingCharacteristics and BusinessTransactionCharacteristics has been generalized to allow extension by other namespace content.

 

[Does this need more elaboration?]