RequestResponse 

A concrete Business Transaction Pattern where there is typically no
residual obligation between the parties. The Request-Response Business Transaction
Pattern can be used when an initiating party requests information the Responding
party already has. This pattern is used when a complex set of interrelated results
are required; otherwise use Query-Response. Typically no residual obligation between
parties applies. For example, a request for price and availability. Note: This
concrete pattern was added in v2.0.

Element Information

Model

Documentation{0,1} , RequestingRole , RespondingRole , RequestingBusinessActivity , RespondingBusinessActivity
Children: Documentation, RequestingBusinessActivity, RequestingRole, RespondingBusinessActivity, 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'

Source 

<xsd:element name="RequestResponse" substitutionGroup="BusinessTransactionHead">
  <xsd:annotation>
    <xsd:documentation>A concrete Business Transaction Pattern where there is typically no residual obligation between the parties. The Request-Response Business Transaction Pattern can be used when an initiating party requests information the Responding party already has. This pattern is used when a complex set of interrelated results are required; otherwise use Query-Response. Typically no residual obligation between parties applies. For example, a request for price and availability. Note: This concrete pattern was added in v2.0.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="BusinessTransactionBaseType">
        <xsd:sequence>
          <xsd:element name="RequestingBusinessActivity">
            <xsd:complexType>
              <xsd:complexContent>
                <xsd:restriction base="RequestingBusinessActivityType">
                  <xsd:sequence>
                    <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
                    <xsd:element ref="DocumentEnvelope"/>
                    <xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>
                    <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>
                    <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>
                    <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>
                  </xsd:sequence>
                  <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>
                  <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>
                  <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>
                  <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>
                  <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>
                  <xsd:attribute name="retryCount" type="xsd:int"/>
                </xsd:restriction>
              </xsd:complexContent>
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="RespondingBusinessActivity">
            <xsd:complexType>
              <xsd:complexContent>
                <xsd:restriction base="RespondingBusinessActivityType">
                  <xsd:sequence>
                    <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
                    <xsd:element ref="DocumentEnvelope" maxOccurs="unbounded"/>
                    <xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>
                    <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>
                    <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>
                    <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>
                  </xsd:sequence>
                  <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>
                  <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>
                  <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>
                  <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>
                  <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>
                </xsd:restriction>
              </xsd:complexContent>
            </xsd:complexType>
          </xsd:element>
        </xsd:sequence>
      </xsd:extension>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>

Sample