OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ebBP 4/7/2005: Comment re: isPositiveResponse (wd11-schema 4/1)


In line with Tuesday's decision about isPositiveResponse and related to 
default or fixed values (on this or isPositiveSignal). Here are some 
updates to ensure consistency in tech spec and schema.

Comments welcome on text. Thanks.
===============================================================================================================
Section 4.6.6.3 Business Signals
Change from:
A corresponding isPositiveSignal attribute occurs on each signal, 
consistent with the structure of the Document Envelope.

Change to:
A corresponding isPositiveSignal attribute occurs on each signal. 
Although consistent with the structure of the Document Envelope, this 
attribute on each signal type has a fixed value.

Section 4.8 Runtime Business Transaction semantics
Change from [note we had an open question here]:

    * [next to the last bullet] Validation of the received response and
      identify if it was specified with isPositiveResponse = false or
      isPositiveSignal

Change to:

    * [next to the last bullet] Validation of the received response or
      signal and identify if it was specified with isPositiveResponse =
      false or adherence to the fixed isPositiveSignal value

Section 4.8.2.4 BSI Conformance
Change from:
isPositiveResponse
A parameter that takes the value of TRUE or FALSE.

Change to:
isPositiveResponse
A parameter that MAY take the value of TRUE or FALSE.

Schema:
[on attribute isPositiveResponse on DocumentEnvelopeType and 
DocumentEnvelope]
Change from:
Evaluates to TRUE or FALSE. If TRUE, the DocumentEnvelope is intended as 
a positive response to a request. The value for this parameter is used 
to evaluate a Business Success or Failure of the corresponding Business 
Transaction.

Change to:
May evaluate to TRUE or FALSE. If TRUE, the DocumentEnvelope is intended 
as a positive response to a request. The value for this parameter is 
used to evaluate a Business Success or Failure of the corresponding 
Business Transaction.

Change from:
An annotation exists on ReceiptAcknowledgementType and doesn't require a 
change.

[add annotation on attribute isPositiveSignal on those specified]
ReceiptAcknowledgementExceptionType
- <#> <xsd:attribute name="*isPositiveSignal*" type="*xsd:boolean*" 
fixed="*false*">
- <#> <xsd:annotation>
  <xsd:documentation>Specifies whether positive receipt of a Business 
Signal is not allowed (i.e. the business signal is an 
exception).</xsd:documentation>
  </xsd:annotation>

AcceptanceAcknowledgementType
<xsd:attribute name="*isPositiveSignal*" type="*xsd:boolean*" 
fixed="*true*">
- <#> <xsd:annotation>
  <xsd:documentation>Specifies whether positive acceptance of a Business 
Signal is required (i.e. the business signal is not an 
exception).</xsd:documentation>
  </xsd:annotation>

AcceptanceAcknowledgementExceptionType
<xsd:attribute name="*isPositiveSignal*" type="*xsd:boolean*" 
fixed="*false*">
- <#> <xsd:annotation>
  <xsd:documentation>Specifies whether positive acceptance of a Business 
Signal is not allowed (i.e. the business signal is an 
exception).</xsd:documentation>
  </xsd:annotation>

GeneralExceptionType
<xsd:attribute name="*isPositiveSignal*" type="*xsd:boolean*" 
fixed="*false*">
- <#> <xsd:annotation>
  <xsd:documentation>Specifies whether positive receipt of a Business 
Signal is not allowed (i.e. the business signal is an 
exception).</xsd:documentation>
  </xsd:annotation>









[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]