Documentation for ebXML Electronic Business using eXtensible Markup Language
Definition Type: Element
Name: RequestResponse
Namespace: http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
Type: nsB:BusinessTransactionBaseType
Containing Schema: ebbp-2.0.4.xsd
Abstract
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.
Collapse XSD Schema Diagram:
Drilldown into RespondingBusinessActivity in schema ebbp-2_0_4_xsd Drilldown into RequestingBusinessActivity in schema ebbp-2_0_4_xsd Drilldown into RespondingRole in schema ebbp-2_0_4_xsd Drilldown into RequestingRole in schema ebbp-2_0_4_xsd Drilldown into Documentation in schema ebbp-2_0_4_xsd Drilldown into isGuaranteedDeliveryRequired in schema ebbp-2_0_4_xsd Drilldown into pattern in schema ebbp-2_0_4_xsd Drilldown into nameID in schema ebbp-2_0_4_xsd Drilldown into name in schema ebbp-2_0_4_xsd Drilldown into name in schema ebbp-2_0_4_xsd Drilldown into BusinessTransactionBaseType in schema ebbp-2_0_4_xsdXSD Diagram of RequestResponse in schema ebbp-2_0_4_xsd (ebXML Electronic Business using eXtensible Markup Language)
Collapse XSD Schema Code: 
<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>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
Documentation nsB:Documentation 0 (1)
RequestingRole nsB:RequestingRole (1) (1)
RespondingRole nsB:RespondingRole (1) (1)
RequestingBusinessActivity nsB:RequestingBusinessActivity (1) (1)
RespondingBusinessActivity nsB:RespondingBusinessActivity (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
name nsB:name Required
nameID nsB:nameID Required
pattern nsB:pattern (Optional)
isGuaranteedDeliveryRequired nsB:isGuaranteedDeliveryRequired false (Optional)
<anyAttribute> Allowed namespace: '##other'
Collapse Derivation Tree:
Collapse References:
nsB:BusinessTransactionHead
Documentation for ebXML Electronic Business using eXtensible Markup Language

Generated using Liquid Studio - Developer Bundle 21.0.0.0