BusinessTransactionBaseType 

The type related to the abstract superclass associated with Business
Transactions.

Complex Type Information

Model

Documentation{0,1} , RequestingRole , RespondingRole
Children: Documentation, RequestingRole, RespondingRole

Attributes

QName Type Fixed Default Use Inheritable Annotation
isGuaranteedDeliveryRequired xsd:boolean false optional 
Refers to the expectation that the underlying messaging service
used to implement the Business Transaction protocol provides guaranteed
delivery, i.e. reliable messaging.
name xsd:string required 
A designation that may be relevant to a business analyst but is
not intended for referencing.
nameID xsd:ID required 
Used for referencing, for example, for identification of elements
within an ebBP instance.
pattern xsd:anyURI optional 
May point to the pattern on which the Business Transaction is
based. This attribute is used only when the concrete BT
patterns provided are not used. This attribute is retained for backward compatibility. The
concrete Business Transaction patterns are also specified. This attribute is 
not be used if one of the concrete, extensible (Data Exchange) or Legacy
Business Transaction (used for conversion purposes only) patterns are used.
Note: These changes were made in v2.0.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://docs.oasis-open.org/ebxmlbp/ebbp-2.0'

Used By

Elements BusinessTransactionHead, DataExchange, InformationDistribution, LegacyBusinessTransaction, Notification, QueryResponse, RequestConfirm, RequestResponse
Complex Type BusinessTransactionType

Source 

<xsd:complexType name="BusinessTransactionBaseType">
  <xsd:annotation>
    <xsd:documentation>The type related to the abstract superclass associated with Business Transactions.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element ref="Documentation" minOccurs="0"/>
    <xsd:element name="RequestingRole" type="RoleType">
      <xsd:annotation>
        <xsd:documentation>Allows definition of the Requesting declarative role on the Business Transaction. This explicit, yet abstract, role facilitates role mapping. This element was added in v2.0.1.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="RespondingRole" type="RoleType">
      <xsd:annotation>
        <xsd:documentation>Allows definition of the the Responding declarative role on the Business Transaction. This explicit, yet abstract, role facilitates role mapping. This element was added in v2.0.1.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
  <xsd:attributeGroup ref="name"/>
  <xsd:attribute name="pattern" type="xsd:anyURI">
    <xsd:annotation>
      <xsd:documentation>May point to the pattern on which the Business Transaction is based. This attribute is used only when the concrete BT patterns provided are not used. This attribute is retained for backward compatibility. The concrete Business Transaction patterns are also specified. This attribute is not be used if one of the concrete, extensible (Data Exchange) or Legacy Business Transaction (used for conversion purposes only) patterns are used. Note: These changes were made in v2.0.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="isGuaranteedDeliveryRequired" type="xsd:boolean" default="false">
    <xsd:annotation>
      <xsd:documentation>Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:complexType>