Schema ebbp-2.0.4.xsd

schema location:	http://docs.oasis-open.org/ebxml-bp/2.0.4/ebbp-2.0.4.xsd
attribute form default:	unqualified
element form default:	qualified
targetNamespace:	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0

Elements	Groups	Complex types	Simple types	Attr. groups
Attachment	collaborationGroup	AcceptanceAcknowledgementExceptionType	BusinessDocumentValueList	documentSecurity
AttributeSubstitution		AcceptanceAcknowledgementType	ConditionGuardValue	map
BinaryCollaboration		AttributeSubstitutionType	ConditionGuardValueList	name
BusinessAction		BinaryCollaborationType	DocumentSpecificationType	optname
BusinessCollaboration		BusinessActionType	ExpressionLanguageType	quality
BusinessDocument		BusinessActivityType	StepType
BusinessTransaction		BusinessCollaborationType	TimeToPerformType
BusinessTransactionActivity		BusinessDocumentType
BusinessTransactionHead		BusinessStateLinkType
CollaborationActivity		BusinessTransactionActivityType
CommercialTransaction		BusinessTransactionBaseType
ComplexBusinessTransactionActivity		BusinessTransactionType
ConditionExpression		CollaborationActivityType
DataExchange		CompletionType
Decision		ConditionExpressionType
Documentation		DecisionType
DocumentEnvelope		DocumentationType
ExternalRoles		DocumentEnvelopeType
Failure		ExternalRolesType
Fork		ForkType
FromLink		GeneralExceptionType
InformationDistribution		JoinType
Join		MultiPartyCollaborationType
LegacyBusinessTransaction		OperationMappingType
MultiPartyCollaboration		PackageType
Notification		PerformsType
OperationMapping		ProcessSpecificationType
Package		ReceiptAcknowledgementExceptionType
Performs		ReceiptAcknowledgementType
ProcessSpecification		RequestingBusinessActivityType
QueryResponse		RespondingBusinessActivityType
RequestConfirm		RoleType
RequestingBusinessActivity		SignalEnvelopeType
RequestResponse		SignalType
RespondingBusinessActivity		StartType
Signal		TransitionType
Specification
Start
StatusVisibility
Success
TimeToPerform
ToLink
Transition
Variable

schema location:	http://www.w3.org/2001/xml.xsd
attribute form default:
element form default:
targetNamespace:	http://www.w3.org/XML/1998/namespace

Attributes	Attr. groups
base	specialAttrs
id
lang
space

element Attachment

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
properties	content  complex
children	Documentation Specification
used by	complexType  DocumentEnvelopeType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthenticated derived by: xsd:NMTOKEN          documentation The communications channel used to transport the Message provides transient authentication. The specific method will be determined by the communications protocol used. Persistent authentication means the Business Document signer’s identity is verified at the receiving application level. Authentication assists in verification of role identity of a participating party. isConfidential derived by: xsd:NMTOKEN          documentation Transient confidentiality is provided by a secure network protocol, such as SSL as the document is transferred between two adjacent ebXML Messaging Service or other transport messaging nodes. Persistent confidentiality is intended to preserve the confidentiality of the message such that only the intended party (application) can see it. isTamperDetectable derived by: xsd:NMTOKEN          documentation Transient isTamperDetectable is the ability to detect if the information has been tampered with during transfer between two adjacent Message Service Handler nodes. Persistent isTamperDetectable is the ability to detect if the information has been tampered with after it has been received by messaging node, between the messaging node and the application. Tamper detection assists in verification of content integrity between and within a participating party. businessDocumentRef xsd:IDREF required         documentation Indicates the nameID reference to the logical business document. mimeType xsd:string optional         documentation Defines the valid MIME (Multipurpose Internet Mail Extensions) type of this Attachment. Example: 'application/pdf'. minOccurs xsd:integer optional         documentation Defines the minimum occurrences of an Attachment. Note: This attribute was added in v2.0. maxOccurs xsd:integer optional         documentation Defines the maximum occurrences of an Attachment. Note: This attribute was added in v2.0.
identity constraints	Name   Refer   Selector   Field(s)   unique   Attachment-ID      .   nameID
annotation	documentation An optional unstructured document associated with a Business Document.
source	<xsd:element name="Attachment">   <xsd:annotation>     <xsd:documentation>An optional unstructured document associated with a Business Document.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:sequence>       <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="Specification" maxOccurs="unbounded"/>     </xsd:sequence>     <xsd:attributeGroup ref="name"/>     <xsd:attributeGroup ref="documentSecurity"/>     <xsd:attribute name="businessDocumentRef" type="xsd:IDREF" use="required">       <xsd:annotation>         <xsd:documentation>Indicates the nameID reference to the logical business document.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>     <xsd:attribute name="mimeType" type="xsd:string" use="optional">       <xsd:annotation>         <xsd:documentation>Defines the valid MIME (Multipurpose Internet Mail Extensions) type of this Attachment. Example: 'application/pdf'.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>     <xsd:attribute name="minOccurs" type="xsd:integer" use="optional">       <xsd:annotation>         <xsd:documentation>Defines the minimum occurrences of an Attachment. Note: This attribute was added in v2.0.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>     <xsd:attribute name="maxOccurs" type="xsd:integer" use="optional">       <xsd:annotation>         <xsd:documentation>Defines the maximum occurrences of an Attachment. Note: This attribute was added in v2.0.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>   </xsd:complexType>   <xsd:unique name="Attachment-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

attribute Attachment/@businessDocumentRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation Indicates the nameID reference to the logical business document.
source	<xsd:attribute name="businessDocumentRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>Indicates the nameID reference to the logical business document.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute Attachment/@mimeType

type	xsd:string
properties	isRef  0 use  optional
annotation	documentation Defines the valid MIME (Multipurpose Internet Mail Extensions) type of this Attachment. Example: 'application/pdf'.
source	<xsd:attribute name="mimeType" type="xsd:string" use="optional">   <xsd:annotation>     <xsd:documentation>Defines the valid MIME (Multipurpose Internet Mail Extensions) type of this Attachment. Example: 'application/pdf'.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute Attachment/@minOccurs

type	xsd:integer
properties	isRef  0 use  optional
annotation	documentation Defines the minimum occurrences of an Attachment. Note: This attribute was added in v2.0.
source	<xsd:attribute name="minOccurs" type="xsd:integer" use="optional">   <xsd:annotation>     <xsd:documentation>Defines the minimum occurrences of an Attachment. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute Attachment/@maxOccurs

type	xsd:integer
properties	isRef  0 use  optional
annotation	documentation Defines the maximum occurrences of an Attachment. Note: This attribute was added in v2.0.
source	<xsd:attribute name="maxOccurs" type="xsd:integer" use="optional">   <xsd:annotation>     <xsd:documentation>Defines the maximum occurrences of an Attachment. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element AttributeSubstitution

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of AttributeSubstitutionType
properties	content  complex
children	Documentation
used by	complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation nameIDRef xsd:IDREF required         documentation Is the nameID reference to the Documentation related to a particular element. attributeName xsd:NMTOKEN required         documentation Is the name of an attribute of any element within the scope of the substitution set. value xsd:string required         documentation Is the value, which shall replace the current value of the attribute.
annotation	documentation Attribute or document value should be used in place of some value in an existing Process Specification. Attribute substitution could be used for document substitution. These substititution changes were made in v2.0.
source	<xsd:element name="AttributeSubstitution">   <xsd:annotation>     <xsd:documentation>Attribute or document value should be used in place of some value in an existing Process Specification. Attribute substitution could be used for document substitution. These substititution changes were made in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="AttributeSubstitutionType"/>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

element BinaryCollaboration

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	BinaryCollaborationType
properties	content  complex
children	Documentation Role TimeToPerform Start BeginsWhen PreCondition PostCondition EndsWhen BusinessTransactionActivity CollaborationActivity ComplexBusinessTransactionActivity Success Failure Transition Fork Join Decision
used by	complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          documentation May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided. isInnerCollaboration xsd:boolean    false      documentation Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.
identity constraints	Name   Refer   Selector   Field(s)   unique   BinaryCollaboration-ID      .   nameID   unique   BinaryCollaborationRole-ID      .//Role   nameID
annotation	documentation Two roles - Defines the interaction between two top-level or abstract partner roles. Binary Collaboration is a choreographed state of two Business Collaboration roles. This Business Collaboration is being deprecated.
source	<xsd:element name="BinaryCollaboration" type="BinaryCollaborationType">   <xsd:annotation>     <xsd:documentation>Two roles - Defines the interaction between two top-level or abstract partner roles. Binary Collaboration is a choreographed state of two Business Collaboration roles. This Business Collaboration is being deprecated.</xsd:documentation>   </xsd:annotation>   <xsd:unique name="BinaryCollaboration-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique>   <xsd:unique name="BinaryCollaborationRole-ID">     <xsd:selector xpath=".//Role"/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

element BusinessAction

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	BusinessActionType
properties	content  complex abstract  true
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          documentation When a party uses isAuthorizationRequired on a Requesting and/or a Responding activity accordingly, the result that [the activity] will only be processed as valid if the party interpreting it successfully matches the stated identity of the activity's [Role] to a list of allowed values previously supplied by that party. Authorization typically relates to a signed business document and the association to the role identity of the party expected for that activity. isIntelligibleCheckRequired xsd:boolean          documentation Allows partners to agree that a message is confirmed by a Receipt Acknowledgement only if it is also legible. Legible means that it has passed structure/schema validity check. The content of the receipt and the legibility of a business message (if required) are reviewed prior to the processing of the Business Document or the evaluation of Condition Expressions in the business message's Business Documents or Document Envelope. isNonRepudiationRequired xsd:boolean          documentation If non-repudiation of origin and content is required, then the Business Activity stores the business document in its original form for the duration mutually agreed to in an agreement. isNonRepudiationReceiptRequired xsd:boolean          documentation Both parties agree to mutually verify receipt of a Requesting Business Document and that the receipt is non-repudiable. timeToAcknowledgeReceipt xsd:duration          documentation The time a Responding or Requesting role has to acknowledge receipt of a Business Document. timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
annotation	documentation An abstract superclass that holds the attributes common to the Requesting and Responding Business Activity.
source	<xsd:element name="BusinessAction" type="BusinessActionType" abstract="true">   <xsd:annotation>     <xsd:documentation>An abstract superclass that holds the attributes common to the Requesting and Responding Business Activity.</xsd:documentation>   </xsd:annotation> </xsd:element>

element BusinessCollaboration

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	BusinessCollaborationType
properties	content  complex
children	Documentation Role TimeToPerform Start BeginsWhen PreCondition PostCondition EndsWhen BusinessTransactionActivity CollaborationActivity ComplexBusinessTransactionActivity Success Failure Transition Fork Join Decision
used by	complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          documentation May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided. isInnerCollaboration xsd:boolean    false      documentation Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.
annotation	documentation Two or more roles - Two or more roles - Defines the interaction between two or more top-level or abstract partner roles. Binary Collaboration is a choreographed state of two or more Business Collaboration roles. This element will replace Binary and MultiParty Collaboration elements in a future version.
source	<xsd:element name="BusinessCollaboration" type="BusinessCollaborationType">   <xsd:annotation>     <xsd:documentation>Two or more roles - Two or more roles - Defines the interaction between two or more top-level or abstract partner roles. Binary Collaboration is a choreographed state of two or more Business Collaboration roles. This element will replace Binary and MultiParty Collaboration elements in a future version.</xsd:documentation>   </xsd:annotation> </xsd:element>

element BusinessDocument

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	BusinessDocumentType
properties	content  complex
children	Documentation ConditionExpression Specification
used by	complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation A generic name of a document. A Business Document may have 0..n Condition Expressions.
source	<xsd:element name="BusinessDocument" type="BusinessDocumentType">   <xsd:annotation>     <xsd:documentation>A generic name of a document. A Business Document may have 0..n Condition Expressions.</xsd:documentation>   </xsd:annotation> </xsd:element>

element BusinessTransaction

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	BusinessTransactionType
properties	content  complex substGrp  BusinessTransactionHead
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation The Business Transaction of type BusinessTransactionType is based on the Commercial Transaction pattern. This pattern (and the two elements that map to it) is typically a formal obligation between parties. Historically, the Commercial Transaction (as one of the defined patterns) has been colloquially known as the Business Transaction. Note: This element that maps to the Commercial Transaction pattern (i.e. the complex type BusinessTransactionType) was added in v2.0.
source	<xsd:element name="BusinessTransaction" type="BusinessTransactionType" substitutionGroup="BusinessTransactionHead">   <xsd:annotation>     <xsd:documentation>The Business Transaction of type BusinessTransactionType is based on the Commercial Transaction pattern. This pattern (and the two elements that map to it) is typically a formal obligation between parties. Historically, the Commercial Transaction (as one of the defined patterns) has been colloquially known as the Business Transaction. Note: This element that maps to the Commercial Transaction pattern (i.e. the complex type BusinessTransactionType) was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:element>

element BusinessTransactionActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionActivityType
properties	content  complex
children	Documentation TimeToPerform Performs BeginsWhen PreCondition PostCondition EndsWhen
used by	element  ComplexBusinessTransactionActivity group  collaborationGroup
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. businessTransactionRef xsd:IDREF required         documentation The nameID reference for the Business Transaction. This attribute is used to reference the Business Transaction reused by the BusinessTransactionActivityType. hasLegalIntent xsd:boolean    false      documentation Indicates that a particular activity that could represent a statement or commitment between trading partners, and their shared intent. Note: This attribute was renamed to hasLegalIntent from isLegallyBinding in v2.0. isConcurrent xsd:boolean    true      documentation A parameter that governs the flow of transactions. Unlike the security and timing parameters it does not govern the internal flow of a transaction, rather it determines whether at run-time multiple instances of that Business Transaction Activity can be ‘open’ at the same time within any Business Collaboration instance performed between any two partners. isConcurrent limits the ability to execute multiple BTA of the same BT across Business Collaboration instances (with the same party), or within the same Business Collaboration if multiple paths are open. As a result, when isConcurrent is set to false, the BSIs of each party are responsible for serializing these Business Transaction activities.
annotation	documentation Defines a Business Transaction Activity within a Business Collaboration. A Business Transaction Activity is a business activity that executes a Business Transaction. Note in v2.0, isLegallyBinding was replaced by hasLegalIntent.
source	<xsd:element name="BusinessTransactionActivity">   <xsd:annotation>     <xsd:documentation>Defines a Business Transaction Activity within a Business Collaboration. A Business Transaction Activity is a business activity that executes a Business Transaction. Note in v2.0, isLegallyBinding was replaced by hasLegalIntent.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="BusinessTransactionActivityType"/>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

element BusinessTransactionHead

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	BusinessTransactionBaseType
properties	content  complex abstract  true
children	Documentation RequestingRole RespondingRole
used by	complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation The abstract superclass associated with the concrete set of defined Business Transaction patterns. A Business Transaction is a set of business information and Business Signal exchanges amongst business partners that occurs in an agreed upon format and sequence (as supported by the patterns). Through the Business Transaction Head, the concrete set of BT patterns and the Data Exchange element (which allows pattern specialization) enable business exchange through a defined pattern. The Business Transaction Head in essence is a placeholder where the concrete pattern is substituted (i.e. a Request-Confirm is substituted and used). Note: The Business Transaction Head replaced the Business Transaction element in v2.0.
source	<xsd:element name="BusinessTransactionHead" type="BusinessTransactionBaseType" abstract="true">   <xsd:annotation>     <xsd:documentation>The abstract superclass associated with the concrete set of defined Business Transaction patterns. A Business Transaction is a set of business information and Business Signal exchanges amongst business partners that occurs in an agreed upon format and sequence (as supported by the patterns). Through the Business Transaction Head, the concrete set of BT patterns and the Data Exchange element (which allows pattern specialization) enable business exchange through a defined pattern. The Business Transaction Head in essence is a placeholder where the concrete pattern is substituted (i.e. a Request-Confirm is substituted and used). Note: The Business Transaction Head replaced the Business Transaction element in v2.0. </xsd:documentation>   </xsd:annotation> </xsd:element>

element CollaborationActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	CollaborationActivityType
properties	content  complex
children	Documentation Performs
used by	group  collaborationGroup
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. collaborationRef xsd:IDREF required         documentation The nameID reference for the Business Collaboration performed by the Collaboration Activity.
annotation	documentation The activity of performing a Business Collaboration within another Business Collaboration.
source	<xsd:element name="CollaborationActivity" type="CollaborationActivityType">   <xsd:annotation>     <xsd:documentation>The activity of performing a Business Collaboration within another Business Collaboration.</xsd:documentation>   </xsd:annotation> </xsd:element>

element CommercialTransaction

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	BusinessTransactionType
properties	content  complex substGrp  BusinessTransactionHead
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation The Commercial Transaction is based on the Commercial Transaction pattern. This pattern (and the two elements that map to it) is typically a formal obligation between parties. Historically, the Commercial Transaction (as one of the defined patterns) has been colloquially known as the Business Transaction. Note: This element that maps to the Commercial Transaction pattern (i.e. the complex type BusinessTransactionType) was added in v2.0.
source	<xsd:element name="CommercialTransaction" type="BusinessTransactionType" substitutionGroup="BusinessTransactionHead">   <xsd:annotation>     <xsd:documentation>The Commercial Transaction is based on the Commercial Transaction pattern. This pattern (and the two elements that map to it) is typically a formal obligation between parties. Historically, the Commercial Transaction (as one of the defined patterns) has been colloquially known as the Business Transaction. Note: This element that maps to the Commercial Transaction pattern (i.e. the complex type BusinessTransactionType) was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:element>

element ComplexBusinessTransactionActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionActivityType
properties	content  complex
children	Documentation TimeToPerform Performs BeginsWhen PreCondition PostCondition EndsWhen ComplexBusinessTransactionActivity StatusVisibility BusinessTransactionActivity
used by	element  ComplexBusinessTransactionActivity group  collaborationGroup
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. businessTransactionRef xsd:IDREF required         documentation The nameID reference for the Business Transaction. This attribute is used to reference the Business Transaction reused by the BusinessTransactionActivityType. hasLegalIntent xsd:boolean    false      documentation Indicates that a particular activity that could represent a statement or commitment between trading partners, and their shared intent. Note: This attribute was renamed to hasLegalIntent from isLegallyBinding in v2.0. isConcurrent xsd:boolean    true      documentation A parameter that governs the flow of transactions. Unlike the security and timing parameters it does not govern the internal flow of a transaction, rather it determines whether at run-time multiple instances of that Business Transaction Activity can be ‘open’ at the same time within any Business Collaboration instance performed between any two partners. isConcurrent limits the ability to execute multiple BTA of the same BT across Business Collaboration instances (with the same party), or within the same Business Collaboration if multiple paths are open. As a result, when isConcurrent is set to false, the BSIs of each party are responsible for serializing these Business Transaction activities.
annotation	documentation Defines a new descriptive element that holds an embedded activity that allows recursive embedded activities. This construct is restricted to 'black box' visibility (i.e. the embedded activity is used for visibility only not for a Multiparty Collaboration). The subparties in the ComplexBTA are auxiliary partners (not constrained by the Business Collaboration). Note: The ComplexBTA and other linking constructs replaced the onInitiation flag in v2.0.
source	<xsd:element name="ComplexBusinessTransactionActivity">   <xsd:annotation>     <xsd:documentation>Defines a new descriptive element that holds an embedded activity that allows recursive embedded activities. This construct is restricted to 'black box' visibility (i.e. the embedded activity is used for visibility only not for a Multiparty Collaboration). The subparties in the ComplexBTA are auxiliary partners (not constrained by the Business Collaboration). Note: The ComplexBTA and other linking constructs replaced the onInitiation flag in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="BusinessTransactionActivityType">         <xsd:choice minOccurs="0" maxOccurs="unbounded">           <xsd:sequence>             <xsd:element ref="ComplexBusinessTransactionActivity"/>             <xsd:element ref="StatusVisibility"/>           </xsd:sequence>           <xsd:sequence>             <xsd:element ref="BusinessTransactionActivity"/>             <xsd:element ref="StatusVisibility"/>           </xsd:sequence>         </xsd:choice>       </xsd:extension>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

element ConditionExpression

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of ConditionExpressionType
properties	content  complex
children	Documentation
used by	element  Variable complexTypes  BusinessDocumentType BusinessStateLinkType SignalType
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
annotation	documentation An expression element that can be evaluated and provide a TRUE or FALSE. Multiple Condition Expression languages and expressions can be used. Note: The capability whereby multiple Condition Expression languages and expressions can be used was expanded (as well as its use with variables) in v2.0.
source	<xsd:element name="ConditionExpression">   <xsd:annotation>     <xsd:documentation>An expression element that can be evaluated and provide a TRUE or FALSE. Multiple Condition Expression languages and expressions can be used. Note: The capability whereby multiple Condition Expression languages and expressions can be used was expanded (as well as its use with variables) in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="ConditionExpressionType"/>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

element DataExchange

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionBaseType
properties	content  complex substGrp  BusinessTransactionHead
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation The element is open and allows definition of other patterns unspecified in the concrete set of Business Transaction patterns. The DataExchange element was not constrained to support state alignment. The semantics related to DataExchange are partner-specific and therefore left unspecified. Note: This element was added in v2.0.
source	<xsd:element name="DataExchange" substitutionGroup="BusinessTransactionHead">   <xsd:annotation>     <xsd:documentation>The element is open and allows definition of other patterns unspecified in the concrete set of Business Transaction patterns. The DataExchange element was not constrained to support state alignment. The semantics related to DataExchange are partner-specific and therefore left unspecified. Note: This element was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="BusinessTransactionBaseType">         <xsd:choice minOccurs="0" maxOccurs="2">           <xsd:element name="RequestingBusinessActivity" minOccurs="0">             <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:sequence>                   <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>                   <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>                   <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>                   <xsd:attribute name="retryCount" type="xsd:int"/>                 </xsd:restriction>               </xsd:complexContent>             </xsd:complexType>           </xsd:element>           <xsd:element name="RespondingBusinessActivity" minOccurs="0">             <xsd:complexType>               <xsd:complexContent>                 <xsd:restriction base="RespondingBusinessActivityType">                   <xsd:sequence>                     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>                     <xsd:element ref="DocumentEnvelope" minOccurs="0" maxOccurs="unbounded"/>                     <xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>                     <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>                   </xsd:sequence>                   <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>                   <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>                   <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>                   <xsd:attribute name="retryCount" type="xsd:int"/>                 </xsd:restriction>               </xsd:complexContent>             </xsd:complexType>           </xsd:element>         </xsd:choice>       </xsd:extension>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

element DataExchange/RequestingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RequestingBusinessActivityType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          retryCount xsd:int
source	<xsd:element name="RequestingBusinessActivity" minOccurs="0">   <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:sequence>         <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>         <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>         <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>         <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>         <xsd:attribute name="retryCount" type="xsd:int"/>       </xsd:restriction>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute DataExchange/RequestingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute DataExchange/RequestingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute DataExchange/RequestingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute DataExchange/RequestingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute DataExchange/RequestingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute DataExchange/RequestingBusinessActivity/@timeToAcknowledgeAcceptance

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>

attribute DataExchange/RequestingBusinessActivity/@retryCount

type	xsd:int
properties	isRef  0
source	<xsd:attribute name="retryCount" type="xsd:int"/>

element DataExchange/RequestingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>

element DataExchange/RequestingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>

element DataExchange/RespondingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RespondingBusinessActivityType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          retryCount xsd:int
source	<xsd:element name="RespondingBusinessActivity" minOccurs="0">   <xsd:complexType>     <xsd:complexContent>       <xsd:restriction base="RespondingBusinessActivityType">         <xsd:sequence>           <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>           <xsd:element ref="DocumentEnvelope" minOccurs="0" maxOccurs="unbounded"/>           <xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>         </xsd:sequence>         <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>         <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>         <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>         <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>         <xsd:attribute name="retryCount" type="xsd:int"/>       </xsd:restriction>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute DataExchange/RespondingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute DataExchange/RespondingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute DataExchange/RespondingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute DataExchange/RespondingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute DataExchange/RespondingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute DataExchange/RespondingBusinessActivity/@timeToAcknowledgeAcceptance

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>

attribute DataExchange/RespondingBusinessActivity/@retryCount

type	xsd:int
properties	isRef  0
source	<xsd:attribute name="retryCount" type="xsd:int"/>

element DataExchange/RespondingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>

element DataExchange/RespondingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>

element Decision

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	DecisionType
properties	content  complex
children	Documentation FromLink ToLink
used by	group  collaborationGroup
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
identity constraints	Name   Refer   Selector   Field(s)   unique   Decision-ID      .   nameID
annotation	documentation A particular pattern of transition between business states. For example, a choice. This is similar to a Decision in a UML activity diagram, although precise semantics differ. One incoming link and many outgoing links, only one of which is taken.
source	<xsd:element name="Decision" type="DecisionType">   <xsd:annotation>     <xsd:documentation>A particular pattern of transition between business states. For example, a choice. This is similar to a Decision in a UML activity diagram, although precise semantics differ. One incoming link and many outgoing links, only one of which is taken.</xsd:documentation>   </xsd:annotation>   <xsd:unique name="Decision-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

element Documentation

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	DocumentationType
properties	content  complex
used by	elements  Attachment ExternalRolesType/BusinessPartnerRole BusinessTransactionType/RequestingBusinessActivity LegacyBusinessTransaction/RequestingBusinessActivity DataExchange/RequestingBusinessActivity Notification/RequestingBusinessActivity InformationDistribution/RequestingBusinessActivity QueryResponse/RequestingBusinessActivity RequestResponse/RequestingBusinessActivity RequestConfirm/RequestingBusinessActivity QueryResponse/RespondingBusinessActivity InformationDistribution/RespondingBusinessActivity Notification/RespondingBusinessActivity RequestResponse/RespondingBusinessActivity DataExchange/RespondingBusinessActivity LegacyBusinessTransaction/RespondingBusinessActivity RequestConfirm/RespondingBusinessActivity BusinessTransactionType/RespondingBusinessActivity complexTypes  AttributeSubstitutionType BinaryCollaborationType BusinessActionType BusinessCollaborationType BusinessDocumentType BusinessStateLinkType BusinessTransactionActivityType BusinessTransactionBaseType CollaborationActivityType CompletionType ConditionExpressionType DecisionType DocumentEnvelopeType ForkType JoinType MultiPartyCollaborationType PackageType PerformsType ProcessSpecificationType RoleType SignalEnvelopeType SignalType StartType
attributes	Name   Type   Use   Default   Fixed   Annotation uri xsd:anyURI          documentation Defines the address of the Documentation object. A URL can be a URI. xml:lang          documentation Attempting to install the relevant ISO 2- and 3-letter          codes as the enumerated possible values is probably never          going to be a realistic possibility.  See          RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry          at http://www.iana.org/assignments/lang-tag-apps.htm for          further information.          The union allows for the 'un-declaration' of xml:lang with          the empty string.
annotation	documentation Defines user documentation for any element. Must be the first element of its container. Note: The xml:lang was added in v2.0.
source	<xsd:element name="Documentation" type="DocumentationType">   <xsd:annotation>     <xsd:documentation>Defines user documentation for any element. Must be the first element of its container. Note: The xml:lang was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:element>

element DocumentEnvelope

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	DocumentEnvelopeType
properties	content  complex
children	Documentation Attachment
used by	elements  RequestConfirm/RequestingBusinessActivity RequestResponse/RequestingBusinessActivity QueryResponse/RequestingBusinessActivity InformationDistribution/RequestingBusinessActivity Notification/RequestingBusinessActivity DataExchange/RequestingBusinessActivity LegacyBusinessTransaction/RequestingBusinessActivity BusinessTransactionType/RequestingBusinessActivity RequestConfirm/RespondingBusinessActivity RequestResponse/RespondingBusinessActivity QueryResponse/RespondingBusinessActivity InformationDistribution/RespondingBusinessActivity Notification/RespondingBusinessActivity DataExchange/RespondingBusinessActivity LegacyBusinessTransaction/RespondingBusinessActivity BusinessTransactionType/RespondingBusinessActivity complexType  BusinessActionType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. businessDocumentRef xsd:IDREF required         documentation Indicates the nameID reference to the logical business document. isPositiveResponse xsd:boolean          documentation 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. isAuthenticated derived by: xsd:NMTOKEN          documentation The communications channel used to transport the Message provides transient authentication. The specific method will be determined by the communications protocol used. Persistent authentication means the Business Document signer’s identity is verified at the receiving application level. Authentication assists in verification of role identity of a participating party. isConfidential derived by: xsd:NMTOKEN          documentation Transient confidentiality is provided by a secure network protocol, such as SSL as the document is transferred between two adjacent ebXML Messaging Service or other transport messaging nodes. Persistent confidentiality is intended to preserve the confidentiality of the message such that only the intended party (application) can see it. isTamperDetectable derived by: xsd:NMTOKEN          documentation Transient isTamperDetectable is the ability to detect if the information has been tampered with during transfer between two adjacent Message Service Handler nodes. Persistent isTamperDetectable is the ability to detect if the information has been tampered with after it has been received by messaging node, between the messaging node and the application. Tamper detection assists in verification of content integrity between and within a participating party.
annotation	documentation Conveys business information between two roles in a business transaction. One document envelope conveys the request from the Requesting to the Responding role and another the response from the Responding role back to the Requesting one (where applicable).
source	<xsd:element name="DocumentEnvelope" type="DocumentEnvelopeType">   <xsd:annotation>     <xsd:documentation>Conveys business information between two roles in a business transaction. One document envelope conveys the request from the Requesting to the Responding role and another the response from the Responding role back to the Requesting one (where applicable).</xsd:documentation>   </xsd:annotation> </xsd:element>

element ExternalRoles

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ExternalRolesType
properties	content  complex
children	BusinessPartnerRole
used by	complexTypes  PackageType ProcessSpecificationType
annotation	documentation External role element maps to the actual roles used in a Business Collaboration (for example, an external role maps to a Business Collaboration). Note: This element was added in v2.0.
source	<xsd:element name="ExternalRoles" type="ExternalRolesType">   <xsd:annotation>     <xsd:documentation>External role element maps to the actual roles used in a Business Collaboration (for example, an external role maps to a Business Collaboration). Note: This element was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:element>

element Failure

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	CompletionType
properties	content  complex
children	Documentation FromLink
used by	group  collaborationGroup
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
identity constraints	Name   Refer   Selector   Field(s)   unique   Failure-ID      .   nameID
annotation	documentation Defines a failure completion of a Business Collaboration as a transition from an activity.
source	<xsd:element name="Failure" type="CompletionType">   <xsd:annotation>     <xsd:documentation>Defines a failure completion of a Business Collaboration as a transition from an activity.</xsd:documentation>   </xsd:annotation>   <xsd:unique name="Failure-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

element Fork

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ForkType
properties	content  complex
children	Documentation TimeToPerform FromLink ToLink
used by	group  collaborationGroup
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID          type derived by: xsd:NMTOKEN optional   OR      documentation Defines the type of Fork. OR: An OR value will mean that any business activity pointed to by a transition coming from the fork might be initiated. All activities may run in parallel. XOR: Only one of the possible activities will run.
identity constraints	Name   Refer   Selector   Field(s)   unique   Fork-ID      .   nameID
annotation	documentation A choreography construct with one incoming transition and many outgoing transitions. All outgoing transitions are considered to happen either in parallel or, when indicated, an exclusive OR is operative.
source	<xsd:element name="Fork" type="ForkType">   <xsd:annotation>     <xsd:documentation>A choreography construct with one incoming transition and many outgoing transitions. All outgoing transitions are considered to happen either in parallel or, when indicated, an exclusive OR is operative.</xsd:documentation>   </xsd:annotation>   <xsd:unique name="Fork-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

element FromLink

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessStateLinkType
properties	content  complex
children	Documentation ConditionExpression
used by	complexTypes  CompletionType DecisionType ForkType JoinType TransitionType
attributes	Name   Type   Use   Default   Fixed   Annotation fromBusinessStateRef xsd:IDREF required         documentation The nameID reference of the Business State of the link transitioned from. conditionGuard ConditionGuardValue optional         documentation The condition that guards the transition from a Business State.
annotation	documentation A linking construct that indicates a state that can be transitioned from in the current context (containing element). The FromLink/@fromBusinessStateRef attribute references the state that is transitioned from by its ID value. FromLinks can have 0..n Condition Expressions associated with them. The conditionGuard attribute can contain status values obtained from the state pointed to by the FromLink; matching the value governs whether a transition is made at run time. Note: This element was added in v2.0.
source	<xsd:element name="FromLink">   <xsd:annotation>     <xsd:documentation>A linking construct that indicates a state that can be transitioned from in the current context (containing element). The FromLink/@fromBusinessStateRef attribute references the state that is transitioned from by its ID value. FromLinks can have 0..n Condition Expressions associated with them. The conditionGuard attribute can contain status values obtained from the state pointed to by the FromLink; matching the value governs whether a transition is made at run time. Note: This element was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="BusinessStateLinkType">         <xsd:attribute name="fromBusinessStateRef" type="xsd:IDREF" use="required">           <xsd:annotation>             <xsd:documentation>The nameID reference of the Business State of the link transitioned from.</xsd:documentation>           </xsd:annotation>         </xsd:attribute>         <xsd:attribute name="conditionGuard" type="ConditionGuardValue" use="optional">           <xsd:annotation>             <xsd:documentation>The condition that guards the transition from a Business State.</xsd:documentation>           </xsd:annotation>         </xsd:attribute>       </xsd:extension>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute FromLink/@fromBusinessStateRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation The nameID reference of the Business State of the link transitioned from.
source	<xsd:attribute name="fromBusinessStateRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>The nameID reference of the Business State of the link transitioned from.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute FromLink/@conditionGuard

type	ConditionGuardValue
properties	isRef  0 use  optional
facets	enumeration  ProtocolSuccess enumeration  AnyProtocolFailure enumeration  RequestReceiptFailure enumeration  RequestAcceptanceFailure enumeration  ResponseReceiptFailure enumeration  ResponseAcceptanceFailure enumeration  SignalTimeout enumeration  ResponseTimeout enumeration  BusinessSuccess enumeration  BusinessFailure enumeration  Success enumeration  Failure
annotation	documentation The condition that guards the transition from a Business State.
source	<xsd:attribute name="conditionGuard" type="ConditionGuardValue" use="optional">   <xsd:annotation>     <xsd:documentation>The condition that guards the transition from a Business State.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element InformationDistribution

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionBaseType
properties	content  complex substGrp  BusinessTransactionHead
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation A concrete Business Transaction Pattern where an informal exchange occurs between parties. Typically no residual obligation between parties applies. No Responding Business Document (response) applies.  It is important to note that in this pattern there is a Responding Business Activity and corresponding Responding Role irrespective of the fact there is not a Responding Business Document.  That Responding role receives and processes (in an abstract sense) the Request. The Responding Business Activity binds the associate role to the business action.  Each activity, Requesting or Responding, has roles bound and linked to it. Note: This concrete pattern was added in v2.0.
source	<xsd:element name="InformationDistribution" substitutionGroup="BusinessTransactionHead">   <xsd:annotation>     <xsd:documentation>A concrete Business Transaction Pattern where an informal exchange occurs between parties. Typically no residual obligation between parties applies. No Responding Business Document (response) applies.  It is important to note that in this pattern there is a Responding Business Activity and corresponding Responding Role irrespective of the fact there is not a Responding Business Document.  That Responding role receives and processes (in an abstract sense) the Request. The Responding Business Activity binds the associate role to the business action.  Each activity, Requesting or Responding, has roles bound and linked to it. 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="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" minOccurs="0" maxOccurs="0"/>                     <xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0" maxOccurs="0"/>                     <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0" maxOccurs="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>

element InformationDistribution/RequestingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RequestingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          documentation If non-repudiation of origin and content is required, then the Business Activity stores the business document in its original form for the duration mutually agreed to in an agreement. isNonRepudiationReceiptRequired xsd:boolean          documentation Both parties agree to mutually verify receipt of a Requesting Business Document and that the receipt is non-repudiable. timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int
source	<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="retryCount" type="xsd:int"/>       </xsd:restriction>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute InformationDistribution/RequestingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute InformationDistribution/RequestingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute InformationDistribution/RequestingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute InformationDistribution/RequestingBusinessActivity/@retryCount

type	xsd:int
properties	isRef  0
source	<xsd:attribute name="retryCount" type="xsd:int"/>

element InformationDistribution/RequestingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>

element InformationDistribution/RequestingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>

element InformationDistribution/RequestingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element InformationDistribution/RequestingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element InformationDistribution/RespondingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RespondingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
source	<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" minOccurs="0" maxOccurs="0"/>           <xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0" maxOccurs="0"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0" maxOccurs="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>

attribute InformationDistribution/RespondingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute InformationDistribution/RespondingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute InformationDistribution/RespondingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute InformationDistribution/RespondingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute InformationDistribution/RespondingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

element InformationDistribution/RespondingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element InformationDistribution/RespondingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element InformationDistribution/RespondingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element InformationDistribution/RespondingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element Join

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	JoinType
properties	content  complex
children	Documentation FromLink ToLink
used by	group  collaborationGroup
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID          waitForAll xsd:boolean    true      documentation Indicates that all transitions coming into the Join are executed in order for the Business Collaboration to reach the Join state (AND-join). By default, the Join is an AND-join.
identity constraints	Name   Refer   Selector   Field(s)   unique   Join-ID      .   nameID
annotation	documentation A choreography construct that defines the point where one or more forked activities join. Can define that the completion of all state occur.
source	<xsd:element name="Join" type="JoinType">   <xsd:annotation>     <xsd:documentation>A choreography construct that defines the point where one or more forked activities join. Can define that the completion of all state occur. </xsd:documentation>   </xsd:annotation>   <xsd:unique name="Join-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

element LegacyBusinessTransaction

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionBaseType
properties	content  complex substGrp  BusinessTransactionHead
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation The previous Business Transaction (now called LegacyBusinessTransaction) was retained for conversions only. The previous Business Transaction element is being replaced by the Business Transaction Head abstract superclass, BusinessTransactionBaseType and the concrete set of Business Transaction Patterns. Note: The Business Transaction (LegacyBusinessTransaction) will be deprecated in a future version. This element was retained in v2.0.x versions.
source	<xsd:element name="LegacyBusinessTransaction" substitutionGroup="BusinessTransactionHead">   <xsd:annotation>     <xsd:documentation>The previous Business Transaction (now called LegacyBusinessTransaction) was retained for conversions only. The previous Business Transaction element is being replaced by the Business Transaction Head abstract superclass, BusinessTransactionBaseType and the concrete set of Business Transaction Patterns. Note: The Business Transaction (LegacyBusinessTransaction) will be deprecated in a future version. This element was retained in v2.0.x versions.</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"/>                     <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>                     <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>                     <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>                   </xsd:sequence>                   <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>                   <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>                   <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>                   <xsd:attribute name="retryCount" type="xsd:int"/>                 </xsd:restriction>               </xsd:complexContent>             </xsd:complexType>           </xsd:element>           <xsd:element name="RespondingBusinessActivity" minOccurs="0">             <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"/>                     <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>                     <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>                     <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>                   </xsd:sequence>                   <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>                   <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>                   <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>                 </xsd:restriction>               </xsd:complexContent>             </xsd:complexType>           </xsd:element>         </xsd:sequence>       </xsd:extension>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

element LegacyBusinessTransaction/RequestingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RequestingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          retryCount xsd:int
source	<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"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>           <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>           <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>         </xsd:sequence>         <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>         <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>         <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>         <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>         <xsd:attribute name="retryCount" type="xsd:int"/>       </xsd:restriction>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute LegacyBusinessTransaction/RequestingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute LegacyBusinessTransaction/RequestingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute LegacyBusinessTransaction/RequestingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute LegacyBusinessTransaction/RequestingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute LegacyBusinessTransaction/RequestingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute LegacyBusinessTransaction/RequestingBusinessActivity/@timeToAcknowledgeAcceptance

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>

attribute LegacyBusinessTransaction/RequestingBusinessActivity/@retryCount

type	xsd:int
properties	isRef  0
source	<xsd:attribute name="retryCount" type="xsd:int"/>

element LegacyBusinessTransaction/RequestingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>

element LegacyBusinessTransaction/RequestingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>

element LegacyBusinessTransaction/RequestingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>

element LegacyBusinessTransaction/RequestingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>

element LegacyBusinessTransaction/RespondingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RespondingBusinessActivityType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
source	<xsd:element name="RespondingBusinessActivity" minOccurs="0">   <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"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>           <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>           <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>         </xsd:sequence>         <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>         <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>         <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>         <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>       </xsd:restriction>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute LegacyBusinessTransaction/RespondingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute LegacyBusinessTransaction/RespondingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute LegacyBusinessTransaction/RespondingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute LegacyBusinessTransaction/RespondingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute LegacyBusinessTransaction/RespondingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute LegacyBusinessTransaction/RespondingBusinessActivity/@timeToAcknowledgeAcceptance

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>

element LegacyBusinessTransaction/RespondingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>

element LegacyBusinessTransaction/RespondingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>

element LegacyBusinessTransaction/RespondingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>

element LegacyBusinessTransaction/RespondingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>

element MultiPartyCollaboration

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	MultiPartyCollaborationType
properties	content  complex
children	Documentation Role TimeToPerform Start BeginsWhen PreCondition PostCondition EndsWhen BusinessTransactionActivity CollaborationActivity ComplexBusinessTransactionActivity Success Failure Transition Fork Join Decision
used by	complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          documentation May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided. isInnerCollaboration xsd:boolean    false      documentation Indicates whether or not this Business Collaboration definition can only be used within a Business Collaboration activity (as a sub collaboration) or initiated directly by a party.
annotation	documentation More than two roles - Defines the interaction between more than two top-level or abstract partner roles. Binary Collaboration is a choreographed state of more than two Business Collaboration roles. This collaboration is being deprecated.
source	<xsd:element name="MultiPartyCollaboration" type="MultiPartyCollaborationType">   <xsd:annotation>     <xsd:documentation>More than two roles - Defines the interaction between more than two top-level or abstract partner roles. Binary Collaboration is a choreographed state of more than two Business Collaboration roles. This collaboration is being deprecated.</xsd:documentation>   </xsd:annotation> </xsd:element>

element Notification

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionBaseType
properties	content  complex substGrp  BusinessTransactionHead
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation A concrete Business Transaction Pattern where there is a formal information exchange between parties that may affect the previous completion of a Commercial or Business Transaction (of the BusinessTransactionType). For example, when the Notification pattern is used for the Notification of Failure Business Transaction, this involves a business message. Another example of a business notification is an Advance Ship Notice. It is important to note that in this pattern there is a Responding Business Activity and corresponding Responding Role irrespective of the fact there is not a Responding Business Document.  That Responding role receives and processes (in an abstract sense) the Request. The Responding Business Activity binds the associate role to the business action. Each activity, Requesting or Responding, has roles bound and linked to it. Note: This concrete pattern was added in v2.0.
source	<xsd:element name="Notification" substitutionGroup="BusinessTransactionHead">   <xsd:annotation>     <xsd:documentation>A concrete Business Transaction Pattern where there is a formal information exchange between parties that may affect the previous completion of a Commercial or Business Transaction (of the BusinessTransactionType). For example, when the Notification pattern is used for the Notification of Failure Business Transaction, this involves a business message. Another example of a business notification is an Advance Ship Notice. It is important to note that in this pattern there is a Responding Business Activity and corresponding Responding Role irrespective of the fact there is not a Responding Business Document.  That Responding role receives and processes (in an abstract sense) the Request. The Responding Business Activity binds the associate role to the business action. Each activity, Requesting or Responding, has roles bound and linked to it. 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"/>                     <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>                     <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>                     <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>                   </xsd:sequence>                   <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>                   <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>                   <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>                   <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" minOccurs="0" maxOccurs="0"/>                     <xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0" maxOccurs="0"/>                     <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0" maxOccurs="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>

element Notification/RequestingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RequestingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          retryCount xsd:int
source	<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"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>           <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>           <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>         </xsd:sequence>         <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>         <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>         <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>         <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>         <xsd:attribute name="retryCount" type="xsd:int"/>       </xsd:restriction>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute Notification/RequestingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute Notification/RequestingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute Notification/RequestingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute Notification/RequestingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute Notification/RequestingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute Notification/RequestingBusinessActivity/@timeToAcknowledgeAcceptance

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>

attribute Notification/RequestingBusinessActivity/@retryCount

type	xsd:int
properties	isRef  0
source	<xsd:attribute name="retryCount" type="xsd:int"/>

element Notification/RequestingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>

element Notification/RequestingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>

element Notification/RequestingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>

element Notification/RequestingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>

element Notification/RespondingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RespondingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
source	<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" minOccurs="0" maxOccurs="0"/>           <xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0" maxOccurs="0"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0" maxOccurs="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>

attribute Notification/RespondingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute Notification/RespondingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute Notification/RespondingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute Notification/RespondingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute Notification/RespondingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

element Notification/RespondingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element Notification/RespondingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element Notification/RespondingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element Notification/RespondingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element OperationMapping

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	OperationMappingType
properties	content  complex
children	MessageMap SignalMap
used by	complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. roleRef xsd:IDREF required         documentation Maps to a Role element contained in collaboration. businessTransactionActivityRef xsd:IDREF required
annotation	documentation An abstract element that allows mapping a BTA and its BusinessDocuments to Interface/Operation messages. Specifies input, output, fault, interface, operation map to role, BTA and document envelope or Business Signal references. Note: This element was added in v2.0.
source	<xsd:element name="OperationMapping" type="OperationMappingType">   <xsd:annotation>     <xsd:documentation>An abstract element that allows mapping a BTA and its BusinessDocuments to Interface/Operation messages. Specifies input, output, fault, interface, operation map to role, BTA and document envelope or Business Signal references. Note: This element was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:element>

element Package

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of PackageType
properties	content  complex
children	Documentation AttributeSubstitution ExternalRoles Signal Variable Package BusinessDocument BusinessTransactionHead BinaryCollaboration MultiPartyCollaboration BusinessCollaboration OperationMapping
used by	complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. parentRef xsd:IDREF optional         documentation Defines the nameID reference for a Package.
identity constraints	Name   Refer   Selector   Field(s)   unique   Package-ID      .   nameID
annotation	documentation Defines a hierarchical name scope containing reusable elements.
source	<xsd:element name="Package">   <xsd:annotation>     <xsd:documentation>Defines a hierarchical name scope containing reusable elements.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="PackageType"/>     </xsd:complexContent>   </xsd:complexType>   <xsd:unique name="Package-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

element Performs

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of PerformsType
properties	content  complex
children	Documentation
used by	complexTypes  BusinessTransactionActivityType CollaborationActivityType
attributes	Name   Type   Use   Default   Fixed   Annotation currentRoleRef xsd:IDREF required         documentation The currentRoleRef attribute defines the nameID reference of the specific role currently used in an activity. If roles change, this name ID reference for the currently used role is the referring role that is linked to the referred-to role in the performsRoleRef. performsRoleRef xsd:IDREF optional         documentation The performsRoleRef attribute defines nameID reference of the referred-to role for the specific role used in an activity. This referred-to role is bound to the referring role (currentRoleRef).
identity constraints	Name   Refer   Selector   Field(s)   unique   Performs-ID      .   nameID
annotation	documentation Performs elements are required whenever referencing the RequestingBusinessActivity or RespondingBusinessActivity in a BTA or within the BTAs of a ComplexBTA. Also Performs elements are required when the Role values in a referring context differ from or need to be switched between the Role values in the referenced context. (The main referring contexts for Business Collaborations are the content models of the CollaborationActivity and ExternalRoles elements.The BTAs and ComplexBTAs are the other referring contexts.) For example, in a Business Collaboration between two parties is related to another Business Collaboration (also of two parties) using a Collaboration Activity, the roles may change for the involved parties. Those roles are traced and associated with the parties. This functionality supports tracing and binding of roles of the Business Collaboration across and within multiple levels of nesting. Where allowed, the Performs element may be omitted if the actual values of Roles in the referring and referred-to context are the same (i.e. string identical) and they match. Note: This element was added in v2.0.
source	<xsd:element name="Performs">   <xsd:annotation>     <xsd:documentation>Performs elements are required whenever referencing the RequestingBusinessActivity or RespondingBusinessActivity in a BTA or within the BTAs of a ComplexBTA. Also Performs elements are required when the Role values in a referring context differ from or need to be switched between the Role values in the referenced context. (The main referring contexts for Business Collaborations are the content models of the CollaborationActivity and ExternalRoles elements.The BTAs and ComplexBTAs are the other referring contexts.) For example, in a Business Collaboration between two parties is related to another Business Collaboration (also of two parties) using a Collaboration Activity, the roles may change for the involved parties. Those roles are traced and associated with the parties. This functionality supports tracing and binding of roles of the Business Collaboration across and within multiple levels of nesting. Where allowed, the Performs element may be omitted if the actual values of Roles in the referring and referred-to context are the same (i.e. string identical) and they match. Note: This element was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="PerformsType"/>     </xsd:complexContent>   </xsd:complexType>   <xsd:unique name="Performs-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

element ProcessSpecification

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of ProcessSpecificationType
properties	content  complex
children	Documentation AttributeSubstitution ExternalRoles Signal Variable Package BusinessDocument BusinessTransactionHead BinaryCollaboration MultiPartyCollaboration BusinessCollaboration OperationMapping
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. uuid xsd:string required         documentation Defines a string identification mechanism for a Process Specificiation. The uuid is not used for the purpose of versioning, so that even a change introduced by AttributeSubstitution (to business documents’ schemas, for example), would be marked by a new uuid. specificationVersion xsd:NMTOKEN optional         documentation Is the technical specification version of the Process Specification. Note: This attribute was added in v2.0. instanceVersion xsd:string optional         documentation Is the version of the Process Specification or artifact instance. An example would be the Australian Wheat Board v2.1. Note: This attribute was added in v2.0.
identity constraints	Name   Refer   Selector   Field(s)   unique   ProcessSpecification-ID      .   nameID
annotation	documentation Root element of a Process Specification document that has a globally unique identity. The Process Specification element can specify the version of the technical specification used and the process instance version related to the target ebBP (schema).
source	<xsd:element name="ProcessSpecification">   <xsd:annotation>     <xsd:documentation>Root element of a Process Specification document that has a globally unique identity. The Process Specification element can specify the version of the technical specification used and the process instance version related to the target ebBP (schema).</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="ProcessSpecificationType">         <xsd:attribute name="specificationVersion" type="xsd:NMTOKEN" use="optional">           <xsd:annotation>             <xsd:documentation>Is the technical specification version of the Process Specification. Note: This attribute was added in v2.0.</xsd:documentation>           </xsd:annotation>         </xsd:attribute>         <xsd:attribute name="instanceVersion" type="xsd:string" use="optional">           <xsd:annotation>             <xsd:documentation>Is the version of the Process Specification or artifact instance. An example would be the Australian Wheat Board v2.1. Note: This attribute was added in v2.0.</xsd:documentation>           </xsd:annotation>         </xsd:attribute>       </xsd:extension>     </xsd:complexContent>   </xsd:complexType>   <xsd:unique name="ProcessSpecification-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

attribute ProcessSpecification/@specificationVersion

type	xsd:NMTOKEN
properties	isRef  0 use  optional
annotation	documentation Is the technical specification version of the Process Specification. Note: This attribute was added in v2.0.
source	<xsd:attribute name="specificationVersion" type="xsd:NMTOKEN" use="optional">   <xsd:annotation>     <xsd:documentation>Is the technical specification version of the Process Specification. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute ProcessSpecification/@instanceVersion

type	xsd:string
properties	isRef  0 use  optional
annotation	documentation Is the version of the Process Specification or artifact instance. An example would be the Australian Wheat Board v2.1. Note: This attribute was added in v2.0.
source	<xsd:attribute name="instanceVersion" type="xsd:string" use="optional">   <xsd:annotation>     <xsd:documentation>Is the version of the Process Specification or artifact instance. An example would be the Australian Wheat Board v2.1. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element QueryResponse

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionBaseType
properties	content  complex substGrp  BusinessTransactionHead
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation A concrete Business Transaction Pattern where the Requester queries for information the Responder already has. The response meets the specified constraining criteria. If a complex set of interrelated results are required, use Request-Response Business Transaction Pattern. Typically no residual obligation between parties applies. Note: This concrete pattern was added in v2.0.
source	<xsd:element name="QueryResponse" substitutionGroup="BusinessTransactionHead">   <xsd:annotation>     <xsd:documentation>A concrete Business Transaction Pattern where the Requester queries for information the Responder already has. The response meets the specified constraining criteria. If a complex set of interrelated results are required, use Request-Response Business Transaction Pattern. Typically no residual obligation between parties applies. 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>

element QueryResponse/RequestingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RequestingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int
source	<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>

attribute QueryResponse/RequestingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute QueryResponse/RequestingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute QueryResponse/RequestingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute QueryResponse/RequestingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute QueryResponse/RequestingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute QueryResponse/RequestingBusinessActivity/@retryCount

type	xsd:int
properties	isRef  0
source	<xsd:attribute name="retryCount" type="xsd:int"/>

element QueryResponse/RequestingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>

element QueryResponse/RequestingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>

element QueryResponse/RequestingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element QueryResponse/RequestingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element QueryResponse/RespondingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RespondingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
source	<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>

attribute QueryResponse/RespondingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute QueryResponse/RespondingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute QueryResponse/RespondingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute QueryResponse/RespondingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute QueryResponse/RespondingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

element QueryResponse/RespondingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>

element QueryResponse/RespondingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>

element QueryResponse/RespondingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element QueryResponse/RespondingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element RequestConfirm

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionBaseType
properties	content  complex substGrp  BusinessTransactionHead
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation A concrete Business Transaction Pattern where an initiating party requests information about their status of a previous request or a Responder's business rules. Typically no residual obligation between parties applies. For example, an initiating party could request authorization to sell specific products where a confirmation response is expected. Note: This concrete pattern was added in v2.0.
source	<xsd:element name="RequestConfirm" substitutionGroup="BusinessTransactionHead">   <xsd:annotation>     <xsd:documentation>A concrete Business Transaction Pattern where an initiating party requests information about their status of a previous request or a Responder's business rules. Typically no residual obligation between parties applies. For example, an initiating party could request authorization to sell specific products where a confirmation response is expected. 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"/>                     <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>                     <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"/>                     <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>                     <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="isNonRepudiationRequired" type="xsd:boolean"/>                   <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>                   <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>                 </xsd:restriction>               </xsd:complexContent>             </xsd:complexType>           </xsd:element>         </xsd:sequence>       </xsd:extension>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

element RequestConfirm/RequestingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RequestingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int
source	<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"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>           <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>

attribute RequestConfirm/RequestingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute RequestConfirm/RequestingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute RequestConfirm/RequestingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute RequestConfirm/RequestingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute RequestConfirm/RequestingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute RequestConfirm/RequestingBusinessActivity/@retryCount

type	xsd:int
properties	isRef  0
source	<xsd:attribute name="retryCount" type="xsd:int"/>

element RequestConfirm/RequestingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>

element RequestConfirm/RequestingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>

element RequestConfirm/RequestingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element RequestConfirm/RequestingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element RequestConfirm/RespondingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RespondingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
source	<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"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>           <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="isNonRepudiationRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>         <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>       </xsd:restriction>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute RequestConfirm/RespondingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute RequestConfirm/RespondingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute RequestConfirm/RespondingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute RequestConfirm/RespondingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute RequestConfirm/RespondingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

element RequestConfirm/RespondingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>

element RequestConfirm/RespondingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>

element RequestConfirm/RespondingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element RequestConfirm/RespondingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element RequestingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	RequestingBusinessActivityType
properties	content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          documentation When a party uses isAuthorizationRequired on a Requesting and/or a Responding activity accordingly, the result that [the activity] will only be processed as valid if the party interpreting it successfully matches the stated identity of the activity's [Role] to a list of allowed values previously supplied by that party. Authorization typically relates to a signed business document and the association to the role identity of the party expected for that activity. isIntelligibleCheckRequired xsd:boolean          documentation Allows partners to agree that a message is confirmed by a Receipt Acknowledgement only if it is also legible. Legible means that it has passed structure/schema validity check. The content of the receipt and the legibility of a business message (if required) are reviewed prior to the processing of the Business Document or the evaluation of Condition Expressions in the business message's Business Documents or Document Envelope. isNonRepudiationRequired xsd:boolean          documentation If non-repudiation of origin and content is required, then the Business Activity stores the business document in its original form for the duration mutually agreed to in an agreement. isNonRepudiationReceiptRequired xsd:boolean          documentation Both parties agree to mutually verify receipt of a Requesting Business Document and that the receipt is non-repudiable. timeToAcknowledgeReceipt xsd:duration          documentation The time a Responding or Requesting role has to acknowledge receipt of a Business Document. timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
annotation	documentation A Business Action performed by the Requesting role within a Business Transaction.
source	<xsd:element name="RequestingBusinessActivity" type="RequestingBusinessActivityType">   <xsd:annotation>     <xsd:documentation>A Business Action performed by the Requesting role within a Business Transaction. </xsd:documentation>   </xsd:annotation> </xsd:element>

element RequestResponse

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionBaseType
properties	content  complex substGrp  BusinessTransactionHead
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	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.
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>

element RequestResponse/RequestingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RequestingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int
source	<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>

attribute RequestResponse/RequestingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute RequestResponse/RequestingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute RequestResponse/RequestingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute RequestResponse/RequestingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute RequestResponse/RequestingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute RequestResponse/RequestingBusinessActivity/@retryCount

type	xsd:int
properties	isRef  0
source	<xsd:attribute name="retryCount" type="xsd:int"/>

element RequestResponse/RequestingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>

element RequestResponse/RequestingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>

element RequestResponse/RequestingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element RequestResponse/RequestingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element RequestResponse/RespondingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RespondingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
source	<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>

attribute RequestResponse/RespondingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute RequestResponse/RespondingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute RequestResponse/RespondingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute RequestResponse/RespondingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute RequestResponse/RespondingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

element RequestResponse/RespondingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>

element RequestResponse/RespondingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>

element RequestResponse/RespondingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>

element RequestResponse/RespondingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>

element RespondingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	RespondingBusinessActivityType
properties	content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          documentation When a party uses isAuthorizationRequired on a Requesting and/or a Responding activity accordingly, the result that [the activity] will only be processed as valid if the party interpreting it successfully matches the stated identity of the activity's [Role] to a list of allowed values previously supplied by that party. Authorization typically relates to a signed business document and the association to the role identity of the party expected for that activity. isIntelligibleCheckRequired xsd:boolean          documentation Allows partners to agree that a message is confirmed by a Receipt Acknowledgement only if it is also legible. Legible means that it has passed structure/schema validity check. The content of the receipt and the legibility of a business message (if required) are reviewed prior to the processing of the Business Document or the evaluation of Condition Expressions in the business message's Business Documents or Document Envelope. isNonRepudiationRequired xsd:boolean          documentation If non-repudiation of origin and content is required, then the Business Activity stores the business document in its original form for the duration mutually agreed to in an agreement. isNonRepudiationReceiptRequired xsd:boolean          documentation Both parties agree to mutually verify receipt of a Requesting Business Document and that the receipt is non-repudiable. timeToAcknowledgeReceipt xsd:duration          documentation The time a Responding or Requesting role has to acknowledge receipt of a Business Document. timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
annotation	documentation A Business Action performed by the Responding role within a Business Transaction.
source	<xsd:element name="RespondingBusinessActivity" type="RespondingBusinessActivityType">   <xsd:annotation>     <xsd:documentation>A Business Action performed by the Responding role within a Business Transaction.</xsd:documentation>   </xsd:annotation> </xsd:element>

element Signal

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	SignalType
properties	content  complex
children	Documentation ConditionExpression Specification
used by	complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation As a Business Action, this element defines the identification structure for Business Signal messages to be sent to a trading partner.  Note: This element was explicitly added for Business Signals to mirror structure of the Business Document specification. This Business Action is non-substantive. A Business Signal is used for state alignment. Note: This element was added in v2.0.
source	<xsd:element name="Signal" type="SignalType">   <xsd:annotation>     <xsd:documentation>As a Business Action, this element defines the identification structure for Business Signal messages to be sent to a trading partner.  Note: This element was explicitly added for Business Signals to mirror structure of the Business Document specification. This Business Action is non-substantive. A Business Signal is used for state alignment. Note: This element was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:element>

element Specification

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
properties	content  complex
used by	element  Attachment complexTypes  BusinessDocumentType SignalType
attributes	Name   Type   Use   Default   Fixed   Annotation type DocumentSpecificationType optional   schema      documentation This attribute defines the type of the Specification of the particular ebBP element. Note: This attribute was added in v2.0. location xsd:anyURI required         documentation The location of the Specification of the particular ebBP element. Note: This attribute was added in v2.0. targetNamespace xsd:anyURI optional         documentation The target namespace of the Specification of the particular ebBP element. Note: This attribute was added in v2.0. externalDocumentDefRef xsd:normalizedString optional         documentation A name, URN or other reference that cites an external specification or reference that defines the document. This attribute was added during v2.0.1 Public Review and included in v2.0.2. name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation A specification element that can associate many references to a particular ebBP element. For example, multiple specifications associated with a logical Business Document. Note: This element was added in v2.0.
source	<xsd:element name="Specification">   <xsd:annotation>     <xsd:documentation>A specification element that can associate many references to a particular ebBP element. For example, multiple specifications associated with a logical Business Document. Note: This element was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:attribute name="type" type="DocumentSpecificationType" use="optional" default="schema">       <xsd:annotation>         <xsd:documentation>This attribute defines the type of the Specification of the particular ebBP element. Note: This attribute was added in v2.0.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>     <xsd:attribute name="location" type="xsd:anyURI" use="required">       <xsd:annotation>         <xsd:documentation>The location of the Specification of the particular ebBP element. Note: This attribute was added in v2.0.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>     <xsd:attribute name="targetNamespace" type="xsd:anyURI" use="optional">       <xsd:annotation>         <xsd:documentation>The target namespace of the Specification of the particular ebBP element. Note: This attribute was added in v2.0.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>     <xsd:attribute name="externalDocumentDefRef" type="xsd:normalizedString" use="optional">       <xsd:annotation>         <xsd:documentation>A name, URN or other reference that cites an external specification or reference that defines the document. This attribute was added during v2.0.1 Public Review and included in v2.0.2.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>     <xsd:attributeGroup ref="name"/>   </xsd:complexType> </xsd:element>

attribute Specification/@type

type	DocumentSpecificationType
properties	isRef  0 default  schema use  optional
facets	enumeration  schema enumeration  dtd enumeration  wsdl enumeration  relaxng enumeration  schematron enumeration  other
annotation	documentation This attribute defines the type of the Specification of the particular ebBP element. Note: This attribute was added in v2.0.
source	<xsd:attribute name="type" type="DocumentSpecificationType" use="optional" default="schema">   <xsd:annotation>     <xsd:documentation>This attribute defines the type of the Specification of the particular ebBP element. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute Specification/@location

type	xsd:anyURI
properties	isRef  0 use  required
annotation	documentation The location of the Specification of the particular ebBP element. Note: This attribute was added in v2.0.
source	<xsd:attribute name="location" type="xsd:anyURI" use="required">   <xsd:annotation>     <xsd:documentation>The location of the Specification of the particular ebBP element. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute Specification/@targetNamespace

type	xsd:anyURI
properties	isRef  0 use  optional
annotation	documentation The target namespace of the Specification of the particular ebBP element. Note: This attribute was added in v2.0.
source	<xsd:attribute name="targetNamespace" type="xsd:anyURI" use="optional">   <xsd:annotation>     <xsd:documentation>The target namespace of the Specification of the particular ebBP element. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute Specification/@externalDocumentDefRef

type	xsd:normalizedString
properties	isRef  0 use  optional
annotation	documentation A name, URN or other reference that cites an external specification or reference that defines the document. This attribute was added during v2.0.1 Public Review and included in v2.0.2.
source	<xsd:attribute name="externalDocumentDefRef" type="xsd:normalizedString" use="optional">   <xsd:annotation>     <xsd:documentation>A name, URN or other reference that cites an external specification or reference that defines the document. This attribute was added during v2.0.1 Public Review and included in v2.0.2.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element Start

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	StartType
properties	content  complex
children	Documentation ToLink
used by	complexTypes  BinaryCollaborationType BusinessCollaborationType MultiPartyCollaborationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
identity constraints	Name   Refer   Selector   Field(s)   unique   Start-ID      .   nameID
annotation	documentation The specific Collaboration started with to traverse a path through a graph to a Completion State.
source	<xsd:element name="Start" type="StartType">   <xsd:annotation>     <xsd:documentation>The specific Collaboration started with to traverse a path through a graph to a Completion State.</xsd:documentation>   </xsd:annotation>   <xsd:unique name="Start-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

element StatusVisibility

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
properties	content  complex
children	BusinessDocumentList SubstateVisibility
used by	elements  ComplexBusinessTransactionActivity ComplexBusinessTransactionActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation Information (which can be aggregated) returned by the subparties of an embedded Business Transaction Activity or ComplexBTA for visibility purposes to the outermost ComplexBTA. For example, a subparty (requester in an embedded BTA that is responder in ComplexBTA) returns aggregated supplier information to the ComplexBTA prior to the responder issuing an order response. The Status Visibility element specifies which status values and which Document Envelope events of the embedded processes are considered, if any, when returning the status value to the context of the ComplexBTA. If no status values or DocumentEnvelope events can be monitored, then both BusinessDocumentList and SubstateVisibility are omitted. Note, this element was added in v2.0.
source	<xsd:element name="StatusVisibility">   <xsd:annotation>     <xsd:documentation>Information (which can be aggregated) returned by the subparties of an embedded Business Transaction Activity or ComplexBTA for visibility purposes to the outermost ComplexBTA. For example, a subparty (requester in an embedded BTA that is responder in ComplexBTA) returns aggregated supplier information to the ComplexBTA prior to the responder issuing an order response. The Status Visibility element specifies which status values and which Document Envelope events of the embedded processes are considered, if any, when returning the status value to the context of the ComplexBTA. If no status values or DocumentEnvelope events can be monitored, then both BusinessDocumentList and SubstateVisibility are omitted. Note, this element was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:sequence>       <xsd:element name="BusinessDocumentList" type="BusinessDocumentValueList" minOccurs="0"/>       <xsd:element name="SubstateVisibility" type="ConditionGuardValueList" minOccurs="0"/>       <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>     </xsd:sequence>     <xsd:attributeGroup ref="name"/>   </xsd:complexType> </xsd:element>

element StatusVisibility/BusinessDocumentList

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	BusinessDocumentValueList
properties	isRef  0 minOcc  0 maxOcc  1 content  simple
source	<xsd:element name="BusinessDocumentList" type="BusinessDocumentValueList" minOccurs="0"/>

element StatusVisibility/SubstateVisibility

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionGuardValueList
properties	isRef  0 minOcc  0 maxOcc  1 content  simple
source	<xsd:element name="SubstateVisibility" type="ConditionGuardValueList" minOccurs="0"/>

element Success

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	CompletionType
properties	content  complex
children	Documentation FromLink
used by	group  collaborationGroup
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
identity constraints	Name   Refer   Selector   Field(s)   unique   Success-ID      .   nameID
annotation	documentation Defines a successful completion of a Collaboration as a transition from an activity.
source	<xsd:element name="Success" type="CompletionType">   <xsd:annotation>     <xsd:documentation>Defines a successful completion of a Collaboration as a transition from an activity.</xsd:documentation>   </xsd:annotation>   <xsd:unique name="Success-ID">     <xsd:selector xpath="."/>     <xsd:field xpath="nameID"/>   </xsd:unique> </xsd:element>

element TimeToPerform

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
properties	content  complex
children	Variable
used by	complexTypes  BinaryCollaborationType BusinessCollaborationType BusinessTransactionActivityType ForkType MultiPartyCollaborationType
attributes	Name   Type   Use   Default   Fixed   Annotation duration xsd:duration optional         documentation The duration of the maximum amount of time between the time at which the request is sent and the substantive response is received. Note: This attribute was added in v2.0. type TimeToPerformType optional   design      documentation The type as specified by the simpleType of TimeToPerformType. Note: This attribute was added in v2.0.
annotation	documentation The expected time available to successfully complete a specified activity such as a substantive response to a request. The Time To Perform could be a variable, i.e. it can be specified at different points during the process lifecycle. Note: This element was added (previously was an attribute on specific elements) in v2.0; capabilities were also added for late binding.
source	<xsd:element name="TimeToPerform">   <xsd:annotation>     <xsd:documentation>The expected time available to successfully complete a specified activity such as a substantive response to a request. The Time To Perform could be a variable, i.e. it can be specified at different points during the process lifecycle. Note: This element was added (previously was an attribute on specific elements) in v2.0; capabilities were also added for late binding.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:sequence>       <xsd:element ref="Variable" minOccurs="0"/>     </xsd:sequence>     <xsd:attribute name="duration" type="xsd:duration" use="optional">       <xsd:annotation>         <xsd:documentation>The duration of the maximum amount of time between the time at which the request is sent and the substantive response is received. Note: This attribute was added in v2.0.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>     <xsd:attribute name="type" type="TimeToPerformType" use="optional" default="design">       <xsd:annotation>         <xsd:documentation>The type as specified by the simpleType of TimeToPerformType. Note: This attribute was added in v2.0.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>   </xsd:complexType> </xsd:element>

attribute TimeToPerform/@duration

type	xsd:duration
properties	isRef  0 use  optional
annotation	documentation The duration of the maximum amount of time between the time at which the request is sent and the substantive response is received. Note: This attribute was added in v2.0.
source	<xsd:attribute name="duration" type="xsd:duration" use="optional">   <xsd:annotation>     <xsd:documentation>The duration of the maximum amount of time between the time at which the request is sent and the substantive response is received. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute TimeToPerform/@type

type	TimeToPerformType
properties	isRef  0 default  design use  optional
facets	enumeration  design enumeration  configuration enumeration  runtime
annotation	documentation The type as specified by the simpleType of TimeToPerformType. Note: This attribute was added in v2.0.
source	<xsd:attribute name="type" type="TimeToPerformType" use="optional" default="design">   <xsd:annotation>     <xsd:documentation>The type as specified by the simpleType of TimeToPerformType. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element ToLink

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessStateLinkType
properties	content  complex
children	Documentation ConditionExpression
used by	complexTypes  DecisionType ForkType JoinType StartType TransitionType
attributes	Name   Type   Use   Default   Fixed   Annotation toBusinessStateRef xsd:IDREF required         documentation The nameID reference of the Business State of the link transitioned to.
annotation	documentation A linking construct that indicates states that the current context (containing element) can transition to. The ToLink/@toBusinessStateRef attribute value references the state through its ID value. Completion States can have 0..n ConditionExpressions that are checked at runtime to determine whether the transition to a state is actually made. Note: This element was added in v2.0.
source	<xsd:element name="ToLink">   <xsd:annotation>     <xsd:documentation>A linking construct that indicates states that the current context (containing element) can transition to. The ToLink/@toBusinessStateRef attribute value references the state through its ID value. Completion States can have 0..n ConditionExpressions that are checked at runtime to determine whether the transition to a state is actually made. Note: This element was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:complexContent>       <xsd:extension base="BusinessStateLinkType">         <xsd:attribute name="toBusinessStateRef" type="xsd:IDREF" use="required">           <xsd:annotation>             <xsd:documentation>The nameID reference of the Business State of the link transitioned to.</xsd:documentation>           </xsd:annotation>         </xsd:attribute>       </xsd:extension>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute ToLink/@toBusinessStateRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation The nameID reference of the Business State of the link transitioned to.
source	<xsd:attribute name="toBusinessStateRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>The nameID reference of the Business State of the link transitioned to.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element Transition

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	TransitionType
properties	content  complex
children	FromLink ToLink
used by	group  collaborationGroup
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
annotation	documentation A link between business states in a Business Collaboration. Choreography is expressed as transitions between business states. Transition to the same business state is allowed.
source	<xsd:element name="Transition" type="TransitionType">   <xsd:annotation>     <xsd:documentation>A link between business states in a Business Collaboration. Choreography is expressed as transitions between business states. Transition to the same business state is allowed.</xsd:documentation>   </xsd:annotation> </xsd:element>

element Variable

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
properties	content  complex
children	ConditionExpression
used by	element  TimeToPerform complexTypes  PackageType ProcessSpecificationType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. businessTransactionActivityRef xsd:IDREF optional         documentation The nameID reference of the Business Transaction Activity associated with the semantic variable. Note: This attribute was added in v2.0. businessDocumentRef xsd:IDREF optional         documentation The nameID reference of the logical business document associated with the semantic variable. Note: This attribute was added in v2.0.
annotation	documentation A semantic element that supports the effective use of conditional constraints. The variable can be accessed by external elements. The businessTransactionActivityRef and businessDocumentRef point to what context and documents are relevant to Condition Expression evaluation. Variable assumes type, if any, from expression evaluation. This element, for example, could be associated with a logical Business Document. Given whether simple or complex variables are used, XPath or XSLT could be used, for example. Note: This complexType was added in v2.0.
source	<xsd:element name="Variable">   <xsd:annotation>     <xsd:documentation>A semantic element that supports the effective use of conditional constraints. The variable can be accessed by external elements. The businessTransactionActivityRef and businessDocumentRef point to what context and documents are relevant to Condition Expression evaluation. Variable assumes type, if any, from expression evaluation. This element, for example, could be associated with a logical Business Document. Given whether simple or complex variables are used, XPath or XSLT could be used, for example. Note: This complexType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:sequence>       <xsd:annotation>         <xsd:documentation>Exactly one ConditionExpression is used to provide values. If multiple ConditionExpressions are listed, each expressionLanguage value is different from others in the sequence and distinct.</xsd:documentation>       </xsd:annotation>       <xsd:element ref="ConditionExpression" maxOccurs="unbounded"/>     </xsd:sequence>     <xsd:attributeGroup ref="name"/>     <xsd:attribute name="businessTransactionActivityRef" type="xsd:IDREF" use="optional">       <xsd:annotation>         <xsd:documentation>The nameID reference of the Business Transaction Activity associated with the semantic variable. Note: This attribute was added in v2.0.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>     <xsd:attribute name="businessDocumentRef" type="xsd:IDREF" use="optional">       <xsd:annotation>         <xsd:documentation>The nameID reference of the logical business document associated with the semantic variable. Note: This attribute was added in v2.0.</xsd:documentation>       </xsd:annotation>     </xsd:attribute>   </xsd:complexType> </xsd:element>

attribute Variable/@businessTransactionActivityRef

type	xsd:IDREF
properties	isRef  0 use  optional
annotation	documentation The nameID reference of the Business Transaction Activity associated with the semantic variable. Note: This attribute was added in v2.0.
source	<xsd:attribute name="businessTransactionActivityRef" type="xsd:IDREF" use="optional">   <xsd:annotation>     <xsd:documentation>The nameID reference of the Business Transaction Activity associated with the semantic variable. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute Variable/@businessDocumentRef

type	xsd:IDREF
properties	isRef  0 use  optional
annotation	documentation The nameID reference of the logical business document associated with the semantic variable. Note: This attribute was added in v2.0.
source	<xsd:attribute name="businessDocumentRef" type="xsd:IDREF" use="optional">   <xsd:annotation>     <xsd:documentation>The nameID reference of the logical business document associated with the semantic variable. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

group collaborationGroup

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	BusinessTransactionActivity CollaborationActivity ComplexBusinessTransactionActivity Success Failure Transition Fork Join Decision
used by	complexTypes  BinaryCollaborationType BusinessCollaborationType MultiPartyCollaborationType
annotation	documentation The group that includes the various types of Collaborations. Note: The Business Collaboration will replace the Binary and MultiParty Collaboration in a future version. Note: This group was added in v2.0.
source	<xsd:group name="collaborationGroup">   <xsd:annotation>     <xsd:documentation>The group that includes the various types of Collaborations. Note: The Business Collaboration will replace the Binary and MultiParty Collaboration in a future version. Note: This group was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:choice>     <xsd:element ref="BusinessTransactionActivity" minOccurs="0"/>     <xsd:element ref="CollaborationActivity" minOccurs="0"/>     <xsd:element ref="ComplexBusinessTransactionActivity" minOccurs="0"/>     <xsd:element ref="Success" minOccurs="0"/>     <xsd:element ref="Failure" minOccurs="0"/>     <xsd:element ref="Transition" minOccurs="0"/>     <xsd:element ref="Fork" minOccurs="0"/>     <xsd:element ref="Join" minOccurs="0"/>     <xsd:element ref="Decision" minOccurs="0"/>   </xsd:choice> </xsd:group>

complexType AcceptanceAcknowledgementExceptionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of SignalEnvelopeType
properties	base  SignalEnvelopeType
children	Documentation
used by	elements  RequestConfirm/RequestingBusinessActivity/AcceptanceAcknowledgementException RequestConfirm/RespondingBusinessActivity/AcceptanceAcknowledgementException RequestResponse/RequestingBusinessActivity/AcceptanceAcknowledgementException RequestResponse/RespondingBusinessActivity/AcceptanceAcknowledgementException QueryResponse/RequestingBusinessActivity/AcceptanceAcknowledgementException QueryResponse/RespondingBusinessActivity/AcceptanceAcknowledgementException InformationDistribution/RequestingBusinessActivity/AcceptanceAcknowledgementException InformationDistribution/RespondingBusinessActivity/AcceptanceAcknowledgementException Notification/RequestingBusinessActivity/AcceptanceAcknowledgementException Notification/RespondingBusinessActivity/AcceptanceAcknowledgementException LegacyBusinessTransaction/RequestingBusinessActivity/AcceptanceAcknowledgementException LegacyBusinessTransaction/RespondingBusinessActivity/AcceptanceAcknowledgementException BusinessActionType/AcceptanceAcknowledgementException BusinessTransactionType/RequestingBusinessActivity/AcceptanceAcknowledgementException BusinessTransactionType/RespondingBusinessActivity/AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
annotation	documentation The type of a BusinessAction Business Signal of exception Acceptance Acknowledgement. A Business Signal is used for state alignment. Note: This type was added in v2.0.
source	<xsd:complexType name="AcceptanceAcknowledgementExceptionType">   <xsd:annotation>     <xsd:documentation>The type of a BusinessAction Business Signal of exception Acceptance Acknowledgement. A Business Signal is used for state alignment. Note: This type was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexContent>     <xsd:extension base="SignalEnvelopeType">       <xsd:attribute name="isPositiveSignal" fixed="false">         <xsd:annotation>           <xsd:documentation>For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.</xsd:documentation>         </xsd:annotation>       </xsd:attribute>     </xsd:extension>   </xsd:complexContent> </xsd:complexType>

attribute AcceptanceAcknowledgementExceptionType/@isPositiveSignal

properties	isRef  0 fixed  false
annotation	documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:attribute name="isPositiveSignal" fixed="false">   <xsd:annotation>     <xsd:documentation>For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType AcceptanceAcknowledgementType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of SignalEnvelopeType
properties	base  SignalEnvelopeType
children	Documentation
used by	elements  RequestConfirm/RequestingBusinessActivity/AcceptanceAcknowledgement RequestConfirm/RespondingBusinessActivity/AcceptanceAcknowledgement RequestResponse/RequestingBusinessActivity/AcceptanceAcknowledgement RequestResponse/RespondingBusinessActivity/AcceptanceAcknowledgement QueryResponse/RequestingBusinessActivity/AcceptanceAcknowledgement QueryResponse/RespondingBusinessActivity/AcceptanceAcknowledgement InformationDistribution/RequestingBusinessActivity/AcceptanceAcknowledgement InformationDistribution/RespondingBusinessActivity/AcceptanceAcknowledgement Notification/RequestingBusinessActivity/AcceptanceAcknowledgement Notification/RespondingBusinessActivity/AcceptanceAcknowledgement LegacyBusinessTransaction/RequestingBusinessActivity/AcceptanceAcknowledgement LegacyBusinessTransaction/RespondingBusinessActivity/AcceptanceAcknowledgement BusinessActionType/AcceptanceAcknowledgement BusinessTransactionType/RequestingBusinessActivity/AcceptanceAcknowledgement BusinessTransactionType/RespondingBusinessActivity/AcceptanceAcknowledgement
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
annotation	documentation The type of Business Action Business Signal of positive Acceptance Acknowledgement.  A Business Signal is used for state alignment. Note: This type was added in v2.0.
source	<xsd:complexType name="AcceptanceAcknowledgementType">   <xsd:annotation>     <xsd:documentation>The type of Business Action Business Signal of positive Acceptance Acknowledgement.  A Business Signal is used for state alignment. Note: This type was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexContent>     <xsd:extension base="SignalEnvelopeType">       <xsd:attribute name="isPositiveSignal" fixed="true">         <xsd:annotation>           <xsd:documentation>For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.</xsd:documentation>         </xsd:annotation>       </xsd:attribute>     </xsd:extension>   </xsd:complexContent> </xsd:complexType>

attribute AcceptanceAcknowledgementType/@isPositiveSignal

properties	isRef  0 fixed  true
annotation	documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:attribute name="isPositiveSignal" fixed="true">   <xsd:annotation>     <xsd:documentation>For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType AttributeSubstitutionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation
used by	element  AttributeSubstitution
attributes	Name   Type   Use   Default   Fixed   Annotation nameIDRef xsd:IDREF required         documentation Is the nameID reference to the Documentation related to a particular element. attributeName xsd:NMTOKEN required         documentation Is the name of an attribute of any element within the scope of the substitution set. value xsd:string required         documentation Is the value, which shall replace the current value of the attribute.
annotation	documentation Type for the attribute or document value used for substitution.
source	<xsd:complexType name="AttributeSubstitutionType">   <xsd:annotation>     <xsd:documentation>Type for the attribute or document value used for substitution.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attribute name="nameIDRef" type="xsd:IDREF" use="required">     <xsd:annotation>       <xsd:documentation>Is the nameID reference to the Documentation related to a particular element.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="attributeName" type="xsd:NMTOKEN" use="required">     <xsd:annotation>       <xsd:documentation>Is the name of an attribute of any element within the scope of the substitution set. </xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="value" type="xsd:string" use="required">     <xsd:annotation>       <xsd:documentation>Is the value, which shall replace the current value of the attribute. </xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute AttributeSubstitutionType/@nameIDRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation Is the nameID reference to the Documentation related to a particular element.
source	<xsd:attribute name="nameIDRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>Is the nameID reference to the Documentation related to a particular element.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute AttributeSubstitutionType/@attributeName

type	xsd:NMTOKEN
properties	isRef  0 use  required
annotation	documentation Is the name of an attribute of any element within the scope of the substitution set.
source	<xsd:attribute name="attributeName" type="xsd:NMTOKEN" use="required">   <xsd:annotation>     <xsd:documentation>Is the name of an attribute of any element within the scope of the substitution set. </xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute AttributeSubstitutionType/@value

type	xsd:string
properties	isRef  0 use  required
annotation	documentation Is the value, which shall replace the current value of the attribute.
source	<xsd:attribute name="value" type="xsd:string" use="required">   <xsd:annotation>     <xsd:documentation>Is the value, which shall replace the current value of the attribute. </xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType BinaryCollaborationType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation Role TimeToPerform Start BeginsWhen PreCondition PostCondition EndsWhen BusinessTransactionActivity CollaborationActivity ComplexBusinessTransactionActivity Success Failure Transition Fork Join Decision
used by	element  BinaryCollaboration
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          documentation May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided. isInnerCollaboration xsd:boolean    false      documentation Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.
annotation	documentation The type related to Binary Collaboration.
source	<xsd:complexType name="BinaryCollaborationType">   <xsd:annotation>     <xsd:documentation>The type related to Binary Collaboration.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="Role" type="RoleType" minOccurs="2" maxOccurs="2"/>     <xsd:element ref="TimeToPerform"/>     <xsd:element ref="Start"/>     <xsd:element name="BeginsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="PreCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="PostCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="EndsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:group ref="collaborationGroup" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="name"/>   <xsd:attribute name="pattern" type="xsd:anyURI">     <xsd:annotation>       <xsd:documentation>May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="isInnerCollaboration" type="xsd:boolean" default="false">     <xsd:annotation>       <xsd:documentation>Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute BinaryCollaborationType/@pattern

type	xsd:anyURI
properties	isRef  0
annotation	documentation May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided.
source	<xsd:attribute name="pattern" type="xsd:anyURI">   <xsd:annotation>     <xsd:documentation>May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute BinaryCollaborationType/@isInnerCollaboration

type	xsd:boolean
properties	isRef  0 default  false
annotation	documentation Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.
source	<xsd:attribute name="isInnerCollaboration" type="xsd:boolean" default="false">   <xsd:annotation>     <xsd:documentation>Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element BinaryCollaborationType/Role

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	RoleType
properties	isRef  0 minOcc  2 maxOcc  2 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
source	<xsd:element name="Role" type="RoleType" minOccurs="2" maxOccurs="2"/>

element BinaryCollaborationType/BeginsWhen

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="BeginsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element BinaryCollaborationType/PreCondition

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="PreCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element BinaryCollaborationType/PostCondition

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="PostCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element BinaryCollaborationType/EndsWhen

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="EndsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

complexType BusinessActionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
used by	element  BusinessAction complexTypes  RequestingBusinessActivityType RespondingBusinessActivityType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          documentation When a party uses isAuthorizationRequired on a Requesting and/or a Responding activity accordingly, the result that [the activity] will only be processed as valid if the party interpreting it successfully matches the stated identity of the activity's [Role] to a list of allowed values previously supplied by that party. Authorization typically relates to a signed business document and the association to the role identity of the party expected for that activity. isIntelligibleCheckRequired xsd:boolean          documentation Allows partners to agree that a message is confirmed by a Receipt Acknowledgement only if it is also legible. Legible means that it has passed structure/schema validity check. The content of the receipt and the legibility of a business message (if required) are reviewed prior to the processing of the Business Document or the evaluation of Condition Expressions in the business message's Business Documents or Document Envelope. isNonRepudiationRequired xsd:boolean          documentation If non-repudiation of origin and content is required, then the Business Activity stores the business document in its original form for the duration mutually agreed to in an agreement. isNonRepudiationReceiptRequired xsd:boolean          documentation Both parties agree to mutually verify receipt of a Requesting Business Document and that the receipt is non-repudiable. timeToAcknowledgeReceipt xsd:duration          documentation The time a Responding or Requesting role has to acknowledge receipt of a Business Document. timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
annotation	documentation The type related to the Business Action.
source	<xsd:complexType name="BusinessActionType">   <xsd:annotation>     <xsd:documentation>The type related to the Business Action.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="DocumentEnvelope" minOccurs="0" 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"/>     <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>   </xsd:sequence>   <xsd:attributeGroup ref="name"/>   <xsd:attributeGroup ref="quality"/> </xsd:complexType>

element BusinessActionType/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>

element BusinessActionType/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>

element BusinessActionType/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>

element BusinessActionType/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>

complexType BusinessActivityType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
used by	complexTypes  BusinessTransactionActivityType CollaborationActivityType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation The type related to the Business Transaction Activity or Collaboration Activity types (and business state).
source	<xsd:complexType name="BusinessActivityType">   <xsd:annotation>     <xsd:documentation>The type related to the Business Transaction Activity or Collaboration Activity types (and business state).</xsd:documentation>   </xsd:annotation>   <xsd:attributeGroup ref="name"/> </xsd:complexType>

complexType BusinessCollaborationType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation Role TimeToPerform Start BeginsWhen PreCondition PostCondition EndsWhen BusinessTransactionActivity CollaborationActivity ComplexBusinessTransactionActivity Success Failure Transition Fork Join Decision
used by	element  BusinessCollaboration
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          documentation May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided. isInnerCollaboration xsd:boolean    false      documentation Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.
annotation	documentation The type related to Business Collaboration.
source	<xsd:complexType name="BusinessCollaborationType">   <xsd:annotation>     <xsd:documentation>The type related to Business Collaboration.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="Role" type="RoleType" minOccurs="2" maxOccurs="unbounded"/>     <xsd:element ref="TimeToPerform"/>     <xsd:element ref="Start"/>     <xsd:element name="BeginsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="PreCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="PostCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="EndsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:group ref="collaborationGroup" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="name"/>   <xsd:attribute name="pattern" type="xsd:anyURI">     <xsd:annotation>       <xsd:documentation>May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="isInnerCollaboration" type="xsd:boolean" default="false">     <xsd:annotation>       <xsd:documentation>Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute BusinessCollaborationType/@pattern

type	xsd:anyURI
properties	isRef  0
annotation	documentation May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided.
source	<xsd:attribute name="pattern" type="xsd:anyURI">   <xsd:annotation>     <xsd:documentation>May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute BusinessCollaborationType/@isInnerCollaboration

type	xsd:boolean
properties	isRef  0 default  false
annotation	documentation Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.
source	<xsd:attribute name="isInnerCollaboration" type="xsd:boolean" default="false">   <xsd:annotation>     <xsd:documentation>Indicates whether or not this Business Collaboration definition can only be used within a Collaboration Activity (as a sub collaboration) or initiated directly by a party.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element BusinessCollaborationType/Role

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	RoleType
properties	isRef  0 minOcc  2 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
source	<xsd:element name="Role" type="RoleType" minOccurs="2" maxOccurs="unbounded"/>

element BusinessCollaborationType/BeginsWhen

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="BeginsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element BusinessCollaborationType/PreCondition

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="PreCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element BusinessCollaborationType/PostCondition

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="PostCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element BusinessCollaborationType/EndsWhen

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="EndsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

complexType BusinessDocumentType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation ConditionExpression Specification
used by	element  BusinessDocument
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation The type related to a Business Document.
source	<xsd:complexType name="BusinessDocumentType">   <xsd:annotation>     <xsd:documentation>The type related to a Business Document.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="ConditionExpression" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="Specification" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="name"/> </xsd:complexType>

complexType BusinessStateLinkType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation ConditionExpression
used by	elements  FromLink ToLink
annotation	documentation The type related to the linking constructs (TO and FROM). The type can have 0..n Condition Expression associated with it. Note: The linking constructs on a transition replaced the onInitiation flag in v2.0.
source	<xsd:complexType name="BusinessStateLinkType">   <xsd:annotation>     <xsd:documentation>The type related to the linking constructs (TO and FROM). The type can have 0..n Condition Expression associated with it. Note: The linking constructs on a transition replaced the onInitiation flag in v2.0. </xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0"/>     <xsd:element ref="ConditionExpression" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence> </xsd:complexType>

complexType BusinessTransactionActivityType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessActivityType
properties	base  BusinessActivityType
children	Documentation TimeToPerform Performs BeginsWhen PreCondition PostCondition EndsWhen
used by	elements  BusinessTransactionActivity ComplexBusinessTransactionActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. businessTransactionRef xsd:IDREF required         documentation The nameID reference for the Business Transaction. This attribute is used to reference the Business Transaction reused by the BusinessTransactionActivityType. hasLegalIntent xsd:boolean    false      documentation Indicates that a particular activity that could represent a statement or commitment between trading partners, and their shared intent. Note: This attribute was renamed to hasLegalIntent from isLegallyBinding in v2.0. isConcurrent xsd:boolean    true      documentation A parameter that governs the flow of transactions. Unlike the security and timing parameters it does not govern the internal flow of a transaction, rather it determines whether at run-time multiple instances of that Business Transaction Activity can be ‘open’ at the same time within any Business Collaboration instance performed between any two partners. isConcurrent limits the ability to execute multiple BTA of the same BT across Business Collaboration instances (with the same party), or within the same Business Collaboration if multiple paths are open. As a result, when isConcurrent is set to false, the BSIs of each party are responsible for serializing these Business Transaction activities.
annotation	documentation The type related to a Business Transaction Activity. The BusinessTransactionActivityType reuses previously defined Business Transactions. Performs elements are required to bind Role values to the Requesting and Responding activities. The older initiatingRoleIDRef attribute is removed as insufficiently versatile. Note: This complexType was added in v2.0.
source	<xsd:complexType name="BusinessTransactionActivityType">   <xsd:annotation>     <xsd:documentation>The type related to a Business Transaction Activity. The BusinessTransactionActivityType reuses previously defined Business Transactions. Performs elements are required to bind Role values to the Requesting and Responding activities. The older initiatingRoleIDRef attribute is removed as insufficiently versatile. Note: This complexType was added in v2.0. </xsd:documentation>   </xsd:annotation>   <xsd:complexContent>     <xsd:extension base="BusinessActivityType">       <xsd:sequence>         <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>         <xsd:element ref="TimeToPerform"/>         <xsd:element ref="Performs" minOccurs="2" maxOccurs="unbounded"/>         <xsd:element name="BeginsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>         <xsd:element name="PreCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>         <xsd:element name="PostCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>         <xsd:element name="EndsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>       </xsd:sequence>       <xsd:attribute name="businessTransactionRef" type="xsd:IDREF" use="required">         <xsd:annotation>           <xsd:documentation>The nameID reference for the Business Transaction. This attribute is used to reference the Business Transaction reused by the BusinessTransactionActivityType.</xsd:documentation>         </xsd:annotation>       </xsd:attribute>       <xsd:attribute name="hasLegalIntent" type="xsd:boolean" default="false">         <xsd:annotation>           <xsd:documentation>Indicates that a particular activity that could represent a statement or commitment between trading partners, and their shared intent. Note: This attribute was renamed to hasLegalIntent from isLegallyBinding in v2.0.</xsd:documentation>         </xsd:annotation>       </xsd:attribute>       <xsd:attribute name="isConcurrent" type="xsd:boolean" default="true">         <xsd:annotation>           <xsd:documentation>A parameter that governs the flow of transactions. Unlike the security and timing parameters it does not govern the internal flow of a transaction, rather it determines whether at run-time multiple instances of that Business Transaction Activity can be ‘open’ at the same time within any Business Collaboration instance performed between any two partners. isConcurrent limits the ability to execute multiple BTA of the same BT across Business Collaboration instances (with the same party), or within the same Business Collaboration if multiple paths are open. As a result, when isConcurrent is set to false, the BSIs of each party are responsible for serializing these Business Transaction activities.</xsd:documentation>         </xsd:annotation>       </xsd:attribute>     </xsd:extension>   </xsd:complexContent> </xsd:complexType>

attribute BusinessTransactionActivityType/@businessTransactionRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation The nameID reference for the Business Transaction. This attribute is used to reference the Business Transaction reused by the BusinessTransactionActivityType.
source	<xsd:attribute name="businessTransactionRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>The nameID reference for the Business Transaction. This attribute is used to reference the Business Transaction reused by the BusinessTransactionActivityType.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute BusinessTransactionActivityType/@hasLegalIntent

type	xsd:boolean
properties	isRef  0 default  false
annotation	documentation Indicates that a particular activity that could represent a statement or commitment between trading partners, and their shared intent. Note: This attribute was renamed to hasLegalIntent from isLegallyBinding in v2.0.
source	<xsd:attribute name="hasLegalIntent" type="xsd:boolean" default="false">   <xsd:annotation>     <xsd:documentation>Indicates that a particular activity that could represent a statement or commitment between trading partners, and their shared intent. Note: This attribute was renamed to hasLegalIntent from isLegallyBinding in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute BusinessTransactionActivityType/@isConcurrent

type	xsd:boolean
properties	isRef  0 default  true
annotation	documentation A parameter that governs the flow of transactions. Unlike the security and timing parameters it does not govern the internal flow of a transaction, rather it determines whether at run-time multiple instances of that Business Transaction Activity can be ‘open’ at the same time within any Business Collaboration instance performed between any two partners. isConcurrent limits the ability to execute multiple BTA of the same BT across Business Collaboration instances (with the same party), or within the same Business Collaboration if multiple paths are open. As a result, when isConcurrent is set to false, the BSIs of each party are responsible for serializing these Business Transaction activities.
source	<xsd:attribute name="isConcurrent" type="xsd:boolean" default="true">   <xsd:annotation>     <xsd:documentation>A parameter that governs the flow of transactions. Unlike the security and timing parameters it does not govern the internal flow of a transaction, rather it determines whether at run-time multiple instances of that Business Transaction Activity can be ‘open’ at the same time within any Business Collaboration instance performed between any two partners. isConcurrent limits the ability to execute multiple BTA of the same BT across Business Collaboration instances (with the same party), or within the same Business Collaboration if multiple paths are open. As a result, when isConcurrent is set to false, the BSIs of each party are responsible for serializing these Business Transaction activities.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element BusinessTransactionActivityType/BeginsWhen

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="BeginsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element BusinessTransactionActivityType/PreCondition

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="PreCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element BusinessTransactionActivityType/PostCondition

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="PostCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element BusinessTransactionActivityType/EndsWhen

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="EndsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

complexType BusinessTransactionBaseType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation RequestingRole RespondingRole
used by	elements  BusinessTransactionHead DataExchange InformationDistribution LegacyBusinessTransaction Notification QueryResponse RequestConfirm RequestResponse complexType  BusinessTransactionType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation The type related to the abstract superclass associated with Business Transactions.
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>

attribute BusinessTransactionBaseType/@pattern

type	xsd:anyURI
properties	isRef  0
annotation	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.
source	<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>

attribute BusinessTransactionBaseType/@isGuaranteedDeliveryRequired

type	xsd:boolean
properties	isRef  0 default  false
annotation	documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
source	<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>

element BusinessTransactionBaseType/RequestingRole

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	RoleType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	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.
source	<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>

element BusinessTransactionBaseType/RespondingRole

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	RoleType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	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.
source	<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>

complexType BusinessTransactionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessTransactionBaseType
properties	base  BusinessTransactionBaseType
children	Documentation RequestingRole RespondingRole RequestingBusinessActivity RespondingBusinessActivity
used by	elements  BusinessTransaction CommercialTransaction
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          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. isGuaranteedDeliveryRequired xsd:boolean    false      documentation Refers to the expectation that the underlying messaging service used to implement the Business Transaction protocol provides guaranteed delivery, i.e. reliable messaging.
annotation	documentation Either the Commercial Transaction or the Business Transaction elements map to type BusinessTransactionType that relates to the Commercial Transaction pattern. The type BusinessTransactionType alllows different communities to use the Commercial Transaction pattern via the two elements that map to it - Commercial Transaction or Business Transaction. Note: This complexType was added in v2.0.
source	<xsd:complexType name="BusinessTransactionType">   <xsd:annotation>     <xsd:documentation>Either the Commercial Transaction or the Business Transaction elements map to type BusinessTransactionType that relates to the Commercial Transaction pattern. The type BusinessTransactionType alllows different communities to use the Commercial Transaction pattern via the two elements that map to it - Commercial Transaction or Business Transaction. Note: This complexType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <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"/>                   <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>                   <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>                   <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>                 </xsd:sequence>                 <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>                 <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>                 <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>                 <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>                 <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>                 <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>                 <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"/>                   <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>                   <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>                   <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>                 </xsd:sequence>                 <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>                 <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>                 <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>                 <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>                 <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>                 <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>               </xsd:restriction>             </xsd:complexContent>           </xsd:complexType>         </xsd:element>       </xsd:sequence>     </xsd:extension>   </xsd:complexContent> </xsd:complexType>

element BusinessTransactionType/RequestingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RequestingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          retryCount xsd:int
source	<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"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>           <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>           <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>         </xsd:sequence>         <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>         <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>         <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>         <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>         <xsd:attribute name="retryCount" type="xsd:int"/>       </xsd:restriction>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute BusinessTransactionType/RequestingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute BusinessTransactionType/RequestingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute BusinessTransactionType/RequestingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute BusinessTransactionType/RequestingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute BusinessTransactionType/RequestingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute BusinessTransactionType/RequestingBusinessActivity/@timeToAcknowledgeAcceptance

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>

attribute BusinessTransactionType/RequestingBusinessActivity/@retryCount

type	xsd:int
properties	isRef  0
source	<xsd:attribute name="retryCount" type="xsd:int"/>

element BusinessTransactionType/RequestingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>

element BusinessTransactionType/RequestingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>

element BusinessTransactionType/RequestingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>

element BusinessTransactionType/RequestingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>

element BusinessTransactionType/RespondingBusinessActivity

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of RespondingBusinessActivityType
properties	isRef  0 content  complex
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          isIntelligibleCheckRequired xsd:boolean          isNonRepudiationRequired xsd:boolean          isNonRepudiationReceiptRequired xsd:boolean          timeToAcknowledgeReceipt xsd:duration          timeToAcknowledgeAcceptance xsd:duration          retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
source	<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"/>           <xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>           <xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>           <xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>         </xsd:sequence>         <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>         <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>         <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>         <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>         <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>       </xsd:restriction>     </xsd:complexContent>   </xsd:complexType> </xsd:element>

attribute BusinessTransactionType/RespondingBusinessActivity/@isAuthorizationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean"/>

attribute BusinessTransactionType/RespondingBusinessActivity/@isIntelligibleCheckRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean"/>

attribute BusinessTransactionType/RespondingBusinessActivity/@isNonRepudiationRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean"/>

attribute BusinessTransactionType/RespondingBusinessActivity/@isNonRepudiationReceiptRequired

type	xsd:boolean
properties	isRef  0
source	<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean"/>

attribute BusinessTransactionType/RespondingBusinessActivity/@timeToAcknowledgeReceipt

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration"/>

attribute BusinessTransactionType/RespondingBusinessActivity/@timeToAcknowledgeAcceptance

type	xsd:duration
properties	isRef  0
source	<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration"/>

element BusinessTransactionType/RespondingBusinessActivity/ReceiptAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>

element BusinessTransactionType/RespondingBusinessActivity/ReceiptAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ReceiptAcknowledgementExceptionType
properties	isRef  0 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>

element BusinessTransactionType/RespondingBusinessActivity/AcceptanceAcknowledgement

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       true   documentation For AcceptanceAcknolwedgmentType, specifies whether positive acceptance of a Business Signal is required (i.e. the Business Signal is not an exception) Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>

element BusinessTransactionType/RespondingBusinessActivity/AcceptanceAcknowledgementException

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	AcceptanceAcknowledgementExceptionType
properties	isRef  0 minOcc  0 maxOcc  1 content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For AcceptanceAcknowledgementExceptionType, specifies whether positive acceptance of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>

complexType CollaborationActivityType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessActivityType
properties	base  BusinessActivityType
children	Documentation Performs
used by	element  CollaborationActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. collaborationRef xsd:IDREF required         documentation The nameID reference for the Business Collaboration performed by the Collaboration Activity.
annotation	documentation The type related to a Collaboration Activity.
source	<xsd:complexType name="CollaborationActivityType">   <xsd:annotation>     <xsd:documentation>The type related to a Collaboration Activity.</xsd:documentation>   </xsd:annotation>   <xsd:complexContent>     <xsd:extension base="BusinessActivityType">       <xsd:sequence>         <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>         <xsd:element ref="Performs" minOccurs="0" maxOccurs="unbounded"/>       </xsd:sequence>       <xsd:attribute name="collaborationRef" type="xsd:IDREF" use="required">         <xsd:annotation>           <xsd:documentation>The nameID reference for the Business Collaboration performed by the Collaboration Activity.</xsd:documentation>         </xsd:annotation>       </xsd:attribute>     </xsd:extension>   </xsd:complexContent> </xsd:complexType>

attribute CollaborationActivityType/@collaborationRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation The nameID reference for the Business Collaboration performed by the Collaboration Activity.
source	<xsd:attribute name="collaborationRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>The nameID reference for the Business Collaboration performed by the Collaboration Activity.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType CompletionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation FromLink
used by	elements  Failure Success
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
annotation	documentation The type related to the Success for Failure completion of a Business Collaboration as a transition from an activity.
source	<xsd:complexType name="CompletionType">   <xsd:annotation>     <xsd:documentation>The type related to the Success for Failure completion of a Business Collaboration as a transition from an activity.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="FromLink" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="optname"/> </xsd:complexType>

complexType ConditionExpressionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation
used by	elements  BinaryCollaborationType/BeginsWhen BusinessTransactionActivityType/BeginsWhen MultiPartyCollaborationType/BeginsWhen BusinessCollaborationType/BeginsWhen ConditionExpression BusinessTransactionActivityType/EndsWhen BusinessCollaborationType/EndsWhen MultiPartyCollaborationType/EndsWhen BinaryCollaborationType/EndsWhen MultiPartyCollaborationType/PostCondition BusinessCollaborationType/PostCondition BinaryCollaborationType/PostCondition BusinessTransactionActivityType/PostCondition MultiPartyCollaborationType/PreCondition BusinessCollaborationType/PreCondition BusinessTransactionActivityType/PreCondition BinaryCollaborationType/PreCondition
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
annotation	documentation The type related to the ConditionExpression element. A BSI supports at least the XPath language, as well as the DocumentEnvelope (expressionLanguage of ExpressionLanguageType) which is the nameID of a Document Envelope. In previous versions, this was known as DocumentEnvelopeNotation. When variables are used, XPath and XSLT could be beneficial. Note: This complexType was added in v2.0.
source	<xsd:complexType name="ConditionExpressionType">   <xsd:annotation>     <xsd:documentation>The type related to the ConditionExpression element. A BSI supports at least the XPath language, as well as the DocumentEnvelope (expressionLanguage of ExpressionLanguageType) which is the nameID of a Document Envelope. In previous versions, this was known as DocumentEnvelopeNotation. When variables are used, XPath and XSLT could be beneficial. Note: This complexType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attribute name="expressionLanguage" type="ExpressionLanguageType" use="required">     <xsd:annotation>       <xsd:documentation>Defines the language used for the Condition Expression.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="expression" type="xsd:string" use="required">     <xsd:annotation>       <xsd:documentation>Defines the value for the Condition Expression.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="defaultValue" type="xsd:string" use="optional">     <xsd:annotation>       <xsd:documentation>Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute ConditionExpressionType/@expressionLanguage

type	ExpressionLanguageType
properties	isRef  0 use  required
facets	enumeration  ConditionGuardValue enumeration  DocumentEnvelope enumeration  XPath1 enumeration  XSLT1 enumeration  CAM1 enumeration  XPath2 enumeration  XSLT2 enumeration  XQuery1
annotation	documentation Defines the language used for the Condition Expression.
source	<xsd:attribute name="expressionLanguage" type="ExpressionLanguageType" use="required">   <xsd:annotation>     <xsd:documentation>Defines the language used for the Condition Expression.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute ConditionExpressionType/@expression

type	xsd:string
properties	isRef  0 use  required
annotation	documentation Defines the value for the Condition Expression.
source	<xsd:attribute name="expression" type="xsd:string" use="required">   <xsd:annotation>     <xsd:documentation>Defines the value for the Condition Expression.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute ConditionExpressionType/@defaultValue

type	xsd:string
properties	isRef  0 use  optional
annotation	documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:attribute name="defaultValue" type="xsd:string" use="optional">   <xsd:annotation>     <xsd:documentation>Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType DecisionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation FromLink ToLink
used by	element  Decision
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
annotation	documentation The type related to a Decision construct.
source	<xsd:complexType name="DecisionType">   <xsd:annotation>     <xsd:documentation>The type related to a Decision construct.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="FromLink"/>     <xsd:element ref="ToLink" minOccurs="2" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="optname"/> </xsd:complexType>

complexType DocumentationType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of xsd:string
properties	base  xsd:string
used by	element  Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation uri xsd:anyURI          documentation Defines the address of the Documentation object. A URL can be a URI. xml:lang          documentation Attempting to install the relevant ISO 2- and 3-letter          codes as the enumerated possible values is probably never          going to be a realistic possibility.  See          RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry          at http://www.iana.org/assignments/lang-tag-apps.htm for          further information.          The union allows for the 'un-declaration' of xml:lang with          the empty string.
annotation	documentation Type for the user documentation for any element.
source	<xsd:complexType name="DocumentationType">   <xsd:annotation>     <xsd:documentation>Type for the user documentation for any element.</xsd:documentation>   </xsd:annotation>   <xsd:simpleContent>     <xsd:extension base="xsd:string">       <xsd:attribute name="uri" type="xsd:anyURI">         <xsd:annotation>           <xsd:documentation>Defines the address of the Documentation object. A URL can be a URI. </xsd:documentation>         </xsd:annotation>       </xsd:attribute>       <xsd:attribute ref="xml:lang"/>     </xsd:extension>   </xsd:simpleContent> </xsd:complexType>

attribute DocumentationType/@uri

type	xsd:anyURI
properties	isRef  0
annotation	documentation Defines the address of the Documentation object. A URL can be a URI.
source	<xsd:attribute name="uri" type="xsd:anyURI">   <xsd:annotation>     <xsd:documentation>Defines the address of the Documentation object. A URL can be a URI. </xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType DocumentEnvelopeType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation Attachment
used by	element  DocumentEnvelope
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. businessDocumentRef xsd:IDREF required         documentation Indicates the nameID reference to the logical business document. isPositiveResponse xsd:boolean          documentation 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. isAuthenticated derived by: xsd:NMTOKEN          documentation The communications channel used to transport the Message provides transient authentication. The specific method will be determined by the communications protocol used. Persistent authentication means the Business Document signer’s identity is verified at the receiving application level. Authentication assists in verification of role identity of a participating party. isConfidential derived by: xsd:NMTOKEN          documentation Transient confidentiality is provided by a secure network protocol, such as SSL as the document is transferred between two adjacent ebXML Messaging Service or other transport messaging nodes. Persistent confidentiality is intended to preserve the confidentiality of the message such that only the intended party (application) can see it. isTamperDetectable derived by: xsd:NMTOKEN          documentation Transient isTamperDetectable is the ability to detect if the information has been tampered with during transfer between two adjacent Message Service Handler nodes. Persistent isTamperDetectable is the ability to detect if the information has been tampered with after it has been received by messaging node, between the messaging node and the application. Tamper detection assists in verification of content integrity between and within a participating party.
annotation	documentation The Type related to envelope that conveys business information.
source	<xsd:complexType name="DocumentEnvelopeType">   <xsd:annotation>     <xsd:documentation>The Type related to envelope that conveys business information.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="Attachment" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="name"/>   <xsd:attribute name="businessDocumentRef" type="xsd:IDREF" use="required">     <xsd:annotation>       <xsd:documentation>Indicates the nameID reference to the logical business document.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="isPositiveResponse" type="xsd:boolean">     <xsd:annotation>       <xsd:documentation>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.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attributeGroup ref="documentSecurity"/> </xsd:complexType>

attribute DocumentEnvelopeType/@businessDocumentRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation Indicates the nameID reference to the logical business document.
source	<xsd:attribute name="businessDocumentRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>Indicates the nameID reference to the logical business document.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute DocumentEnvelopeType/@isPositiveResponse

type	xsd:boolean
properties	isRef  0
annotation	documentation 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.
source	<xsd:attribute name="isPositiveResponse" type="xsd:boolean">   <xsd:annotation>     <xsd:documentation>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.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType ExternalRolesType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	BusinessPartnerRole
used by	element  ExternalRoles
annotation	documentation Types for the external role that maps to actual roles in a Business Collaboration. Performs elements are needed when the values of Roles declared in a Business Collaboration differ from the values declared with the @name attribute. Note: This complexType was added in v2.0.
source	<xsd:complexType name="ExternalRolesType">   <xsd:annotation>     <xsd:documentation>Types for the external role that maps to actual roles in a Business Collaboration. Performs elements are needed when the values of Roles declared in a Business Collaboration differ from the values declared with the @name attribute. Note: This complexType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element name="BusinessPartnerRole" minOccurs="2" maxOccurs="unbounded">       <xsd:annotation>         <xsd:documentation>Each business partner plays one or more abstract partner roles in the Business Collaboration. </xsd:documentation>       </xsd:annotation>       <xsd:complexType>         <xsd:sequence>           <xsd:element ref="Documentation" minOccurs="0"/>           <xsd:element name="Performs" type="PerformsType" minOccurs="0" maxOccurs="unbounded"/>         </xsd:sequence>         <xsd:attributeGroup ref="name"/>       </xsd:complexType>     </xsd:element>   </xsd:sequence> </xsd:complexType>

element ExternalRolesType/BusinessPartnerRole

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
properties	isRef  0 minOcc  2 maxOcc  unbounded content  complex
children	Documentation Performs
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation Each business partner plays one or more abstract partner roles in the Business Collaboration.
source	<xsd:element name="BusinessPartnerRole" minOccurs="2" maxOccurs="unbounded">   <xsd:annotation>     <xsd:documentation>Each business partner plays one or more abstract partner roles in the Business Collaboration. </xsd:documentation>   </xsd:annotation>   <xsd:complexType>     <xsd:sequence>       <xsd:element ref="Documentation" minOccurs="0"/>       <xsd:element name="Performs" type="PerformsType" minOccurs="0" maxOccurs="unbounded"/>     </xsd:sequence>     <xsd:attributeGroup ref="name"/>   </xsd:complexType> </xsd:element>

element ExternalRolesType/BusinessPartnerRole/Performs

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	PerformsType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
used by	complexTypes  BusinessTransactionActivityType CollaborationActivityType
attributes	Name   Type   Use   Default   Fixed   Annotation currentRoleRef xsd:IDREF required         documentation The currentRoleRef attribute defines the nameID reference of the specific role currently used in an activity. If roles change, this name ID reference for the currently used role is the referring role that is linked to the referred-to role in the performsRoleRef. performsRoleRef xsd:IDREF optional         documentation The performsRoleRef attribute defines nameID reference of the referred-to role for the specific role used in an activity. This referred-to role is bound to the referring role (currentRoleRef).
source	<xsd:element name="Performs" type="PerformsType" minOccurs="0" maxOccurs="unbounded"/>

complexType ForkType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation TimeToPerform FromLink ToLink
used by	element  Fork
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID          type derived by: xsd:NMTOKEN optional   OR      documentation Defines the type of Fork. OR: An OR value will mean that any business activity pointed to by a transition coming from the fork might be initiated. All activities may run in parallel. XOR: Only one of the possible activities will run.
annotation	documentation The type related to the Fork construct
source	<xsd:complexType name="ForkType">   <xsd:annotation>     <xsd:documentation>The type related to the Fork construct</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="TimeToPerform" minOccurs="0"/>     <xsd:element ref="FromLink"/>     <xsd:element ref="ToLink" minOccurs="2" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="optname"/>   <xsd:attribute name="type" use="optional" default="OR">     <xsd:annotation>       <xsd:documentation>Defines the type of Fork. OR: An OR value will mean that any business activity pointed to by a transition coming from the fork might be initiated. All activities may run in parallel. XOR: Only one of the possible activities will run.</xsd:documentation>     </xsd:annotation>     <xsd:simpleType>       <xsd:restriction base="xsd:NMTOKEN">         <xsd:enumeration value="OR"/>         <xsd:enumeration value="XOR"/>       </xsd:restriction>     </xsd:simpleType>   </xsd:attribute> </xsd:complexType>

attribute ForkType/@type

type	restriction of xsd:NMTOKEN
properties	isRef  0 default  OR use  optional
facets	enumeration  OR enumeration  XOR
annotation	documentation Defines the type of Fork. OR: An OR value will mean that any business activity pointed to by a transition coming from the fork might be initiated. All activities may run in parallel. XOR: Only one of the possible activities will run.
source	<xsd:attribute name="type" use="optional" default="OR">   <xsd:annotation>     <xsd:documentation>Defines the type of Fork. OR: An OR value will mean that any business activity pointed to by a transition coming from the fork might be initiated. All activities may run in parallel. XOR: Only one of the possible activities will run.</xsd:documentation>   </xsd:annotation>   <xsd:simpleType>     <xsd:restriction base="xsd:NMTOKEN">       <xsd:enumeration value="OR"/>       <xsd:enumeration value="XOR"/>     </xsd:restriction>   </xsd:simpleType> </xsd:attribute>

complexType GeneralExceptionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of SignalEnvelopeType
properties	base  SignalEnvelopeType
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For GeneralExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
annotation	documentation The type of a Business Action of general exception (exceptions other than Receipt and Acceptance Acknowledgement). During an interaction, if specified by the parties, the general exception may be used when a party has to trigger an exception, for example, for a general communication of catastrophic failure. A Business Signal is typically used for state alignment. As an unforeseen event, this type of Exception is outside of the currently defined concrete BT patterns. Note: this type was added in v2.0.
source	<xsd:complexType name="GeneralExceptionType">   <xsd:annotation>     <xsd:documentation>The type of a Business Action of general exception (exceptions other than Receipt and Acceptance Acknowledgement). During an interaction, if specified by the parties, the general exception may be used when a party has to trigger an exception, for example, for a general communication of catastrophic failure. A Business Signal is typically used for state alignment. As an unforeseen event, this type of Exception is outside of the currently defined concrete BT patterns. Note: this type was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexContent>     <xsd:extension base="SignalEnvelopeType">       <xsd:attribute name="isPositiveSignal" fixed="false">         <xsd:annotation>           <xsd:documentation>For GeneralExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.</xsd:documentation>         </xsd:annotation>       </xsd:attribute>     </xsd:extension>   </xsd:complexContent> </xsd:complexType>

attribute GeneralExceptionType/@isPositiveSignal

properties	isRef  0 fixed  false
annotation	documentation For GeneralExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:attribute name="isPositiveSignal" fixed="false">   <xsd:annotation>     <xsd:documentation>For GeneralExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType JoinType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation FromLink ToLink
used by	element  Join
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID          waitForAll xsd:boolean    true      documentation Indicates that all transitions coming into the Join are executed in order for the Business Collaboration to reach the Join state (AND-join). By default, the Join is an AND-join.
annotation	documentation The type related to the Join construct
source	<xsd:complexType name="JoinType">   <xsd:annotation>     <xsd:documentation>The type related to the Join construct</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="FromLink" minOccurs="2" maxOccurs="unbounded"/>     <xsd:element ref="ToLink" minOccurs="0"/>   </xsd:sequence>   <xsd:attributeGroup ref="optname"/>   <xsd:attribute name="waitForAll" type="xsd:boolean" default="true">     <xsd:annotation>       <xsd:documentation>Indicates that all transitions coming into the Join are executed in order for the Business Collaboration to reach the Join state (AND-join). By default, the Join is an AND-join.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute JoinType/@waitForAll

type	xsd:boolean
properties	isRef  0 default  true
annotation	documentation Indicates that all transitions coming into the Join are executed in order for the Business Collaboration to reach the Join state (AND-join). By default, the Join is an AND-join.
source	<xsd:attribute name="waitForAll" type="xsd:boolean" default="true">   <xsd:annotation>     <xsd:documentation>Indicates that all transitions coming into the Join are executed in order for the Business Collaboration to reach the Join state (AND-join). By default, the Join is an AND-join.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType MultiPartyCollaborationType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation Role TimeToPerform Start BeginsWhen PreCondition PostCondition EndsWhen BusinessTransactionActivity CollaborationActivity ComplexBusinessTransactionActivity Success Failure Transition Fork Join Decision
used by	element  MultiPartyCollaboration
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. pattern xsd:anyURI          documentation May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided. isInnerCollaboration xsd:boolean    false      documentation Indicates whether or not this Business Collaboration definition can only be used within a Business Collaboration activity (as a sub collaboration) or initiated directly by a party.
annotation	documentation The type related to MultiParty Collaboration.
source	<xsd:complexType name="MultiPartyCollaborationType">   <xsd:annotation>     <xsd:documentation>The type related to MultiParty Collaboration.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="Role" type="RoleType" minOccurs="3" maxOccurs="unbounded"/>     <xsd:element ref="TimeToPerform"/>     <xsd:element ref="Start"/>     <xsd:element name="BeginsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="PreCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="PostCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element name="EndsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>     <xsd:group ref="collaborationGroup" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="name"/>   <xsd:attribute name="pattern" type="xsd:anyURI">     <xsd:annotation>       <xsd:documentation>May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="isInnerCollaboration" type="xsd:boolean" default="false">     <xsd:annotation>       <xsd:documentation>Indicates whether or not this Business Collaboration definition can only be used within a Business Collaboration activity (as a sub collaboration) or initiated directly by a party.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute MultiPartyCollaborationType/@pattern

type	xsd:anyURI
properties	isRef  0
annotation	documentation May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided.
source	<xsd:attribute name="pattern" type="xsd:anyURI">   <xsd:annotation>     <xsd:documentation>May point to the pattern on which an activity or collaboration is based. This attribute is used only when not using the concrete BT patterns provided.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute MultiPartyCollaborationType/@isInnerCollaboration

type	xsd:boolean
properties	isRef  0 default  false
annotation	documentation Indicates whether or not this Business Collaboration definition can only be used within a Business Collaboration activity (as a sub collaboration) or initiated directly by a party.
source	<xsd:attribute name="isInnerCollaboration" type="xsd:boolean" default="false">   <xsd:annotation>     <xsd:documentation>Indicates whether or not this Business Collaboration definition can only be used within a Business Collaboration activity (as a sub collaboration) or initiated directly by a party.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

element MultiPartyCollaborationType/Role

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	RoleType
properties	isRef  0 minOcc  3 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
source	<xsd:element name="Role" type="RoleType" minOccurs="3" maxOccurs="unbounded"/>

element MultiPartyCollaborationType/BeginsWhen

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="BeginsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element MultiPartyCollaborationType/PreCondition

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="PreCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element MultiPartyCollaborationType/PostCondition

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="PostCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

element MultiPartyCollaborationType/EndsWhen

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	ConditionExpressionType
properties	isRef  0 minOcc  0 maxOcc  unbounded content  complex
children	Documentation
attributes	Name   Type   Use   Default   Fixed   Annotation expressionLanguage ExpressionLanguageType required         documentation Defines the language used for the Condition Expression. expression xsd:string required         documentation Defines the value for the Condition Expression. defaultValue xsd:string optional         documentation Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.
source	<xsd:element name="EndsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>

complexType OperationMappingType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	MessageMap SignalMap
used by	element  OperationMapping
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. roleRef xsd:IDREF required         documentation Maps to a Role element contained in collaboration. businessTransactionActivityRef xsd:IDREF required
annotation	documentation The type related to the abstract element mapping Operations to Business Actions, either business messages or signals. Note: This complexType was added in v2.0.
source	<xsd:complexType name="OperationMappingType">   <xsd:annotation>     <xsd:documentation>The type related to the abstract element mapping Operations to Business Actions, either business messages or signals. Note: This complexType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element name="MessageMap" maxOccurs="unbounded">       <xsd:complexType>         <xsd:attributeGroup ref="map"/>       </xsd:complexType>     </xsd:element>     <xsd:element name="SignalMap" minOccurs="0" maxOccurs="8">       <xsd:complexType>         <xsd:attributeGroup ref="map"/>       </xsd:complexType>     </xsd:element>   </xsd:sequence>   <xsd:attributeGroup ref="name"/>   <xsd:attribute name="roleRef" type="xsd:IDREF" use="required">     <xsd:annotation>       <xsd:documentation>Maps to a Role element contained in collaboration.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="businessTransactionActivityRef" type="xsd:IDREF" use="required"/> </xsd:complexType>

attribute OperationMappingType/@roleRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation Maps to a Role element contained in collaboration.
source	<xsd:attribute name="roleRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>Maps to a Role element contained in collaboration.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute OperationMappingType/@businessTransactionActivityRef

type	xsd:IDREF
properties	isRef  0 use  required
source	<xsd:attribute name="businessTransactionActivityRef" type="xsd:IDREF" use="required"/>

element OperationMappingType/MessageMap

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
properties	isRef  0 minOcc  1 maxOcc  unbounded content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation interfaceName xsd:NMTOKEN required         documentation Interface is called portType in WSDL 1.1. The name of the interface or portType mapped logically in Operation Mapping. Note: This attribute was added in v2.0. operationName xsd:NMTOKEN required         documentation The name of the operation mapped in the OperationMapping. Note: This attribute was added in v2.0. operationStep StepType required         documentation The name of operation step from the Step Type enumeration list for OperationMapping. Note: This attribute was added in v2.0. documentEnvelopeRef xsd:IDREF required         documentation The nameID reference of the Document Envelope related to the OperationMapping. Note: This attribute was added in v2.0.
source	<xsd:element name="MessageMap" maxOccurs="unbounded">   <xsd:complexType>     <xsd:attributeGroup ref="map"/>   </xsd:complexType> </xsd:element>

element OperationMappingType/SignalMap

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
properties	isRef  0 minOcc  0 maxOcc  8 content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation interfaceName xsd:NMTOKEN required         documentation Interface is called portType in WSDL 1.1. The name of the interface or portType mapped logically in Operation Mapping. Note: This attribute was added in v2.0. operationName xsd:NMTOKEN required         documentation The name of the operation mapped in the OperationMapping. Note: This attribute was added in v2.0. operationStep StepType required         documentation The name of operation step from the Step Type enumeration list for OperationMapping. Note: This attribute was added in v2.0. documentEnvelopeRef xsd:IDREF required         documentation The nameID reference of the Document Envelope related to the OperationMapping. Note: This attribute was added in v2.0.
source	<xsd:element name="SignalMap" minOccurs="0" maxOccurs="8">   <xsd:complexType>     <xsd:attributeGroup ref="map"/>   </xsd:complexType> </xsd:element>

complexType PackageType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation AttributeSubstitution ExternalRoles Signal Variable Package BusinessDocument BusinessTransactionHead BinaryCollaboration MultiPartyCollaboration BusinessCollaboration OperationMapping
used by	element  Package
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. parentRef xsd:IDREF optional         documentation Defines the nameID reference for a Package.
annotation	documentation Type for a hierarchical name scope containing reusable elements.
source	<xsd:complexType name="PackageType">   <xsd:annotation>     <xsd:documentation>Type for a hierarchical name scope containing reusable elements.</xsd:documentation>   </xsd:annotation>   <xsd:choice maxOccurs="unbounded">     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="AttributeSubstitution" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="ExternalRoles" minOccurs="0"/>     <xsd:element ref="Signal" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="Variable" minOccurs="0" maxOccurs="unbounded"/>     <xsd:choice minOccurs="0" maxOccurs="unbounded">       <xsd:element ref="Package" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="BusinessDocument" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="BusinessTransactionHead" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="BinaryCollaboration" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="MultiPartyCollaboration" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="BusinessCollaboration" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="OperationMapping" minOccurs="0"/>     </xsd:choice>   </xsd:choice>   <xsd:attributeGroup ref="name"/>   <xsd:attribute name="parentRef" type="xsd:IDREF" use="optional">     <xsd:annotation>       <xsd:documentation>Defines the nameID reference for a Package.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute PackageType/@parentRef

type	xsd:IDREF
properties	isRef  0 use  optional
annotation	documentation Defines the nameID reference for a Package.
source	<xsd:attribute name="parentRef" type="xsd:IDREF" use="optional">   <xsd:annotation>     <xsd:documentation>Defines the nameID reference for a Package.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType PerformsType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation
used by	elements  Performs ExternalRolesType/BusinessPartnerRole/Performs
attributes	Name   Type   Use   Default   Fixed   Annotation currentRoleRef xsd:IDREF required         documentation The currentRoleRef attribute defines the nameID reference of the specific role currently used in an activity. If roles change, this name ID reference for the currently used role is the referring role that is linked to the referred-to role in the performsRoleRef. performsRoleRef xsd:IDREF optional         documentation The performsRoleRef attribute defines nameID reference of the referred-to role for the specific role used in an activity. This referred-to role is bound to the referring role (currentRoleRef).
annotation	documentation The type related to the role binding Performs element.
source	<xsd:complexType name="PerformsType">   <xsd:annotation>     <xsd:documentation>The type related to the role binding Performs element.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0"/>   </xsd:sequence>   <xsd:attribute name="currentRoleRef" type="xsd:IDREF" use="required">     <xsd:annotation>       <xsd:documentation>The currentRoleRef attribute defines the nameID reference of the specific role currently used in an activity. If roles change, this name ID reference for the currently used role is the referring role that is linked to the referred-to role in the performsRoleRef. </xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="performsRoleRef" type="xsd:IDREF" use="optional">     <xsd:annotation>       <xsd:documentation>The performsRoleRef attribute defines nameID reference of the referred-to role for the specific role used in an activity. This referred-to role is bound to the referring role (currentRoleRef). </xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute PerformsType/@currentRoleRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation The currentRoleRef attribute defines the nameID reference of the specific role currently used in an activity. If roles change, this name ID reference for the currently used role is the referring role that is linked to the referred-to role in the performsRoleRef.
source	<xsd:attribute name="currentRoleRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>The currentRoleRef attribute defines the nameID reference of the specific role currently used in an activity. If roles change, this name ID reference for the currently used role is the referring role that is linked to the referred-to role in the performsRoleRef. </xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute PerformsType/@performsRoleRef

type	xsd:IDREF
properties	isRef  0 use  optional
annotation	documentation The performsRoleRef attribute defines nameID reference of the referred-to role for the specific role used in an activity. This referred-to role is bound to the referring role (currentRoleRef).
source	<xsd:attribute name="performsRoleRef" type="xsd:IDREF" use="optional">   <xsd:annotation>     <xsd:documentation>The performsRoleRef attribute defines nameID reference of the referred-to role for the specific role used in an activity. This referred-to role is bound to the referring role (currentRoleRef). </xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType ProcessSpecificationType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation AttributeSubstitution ExternalRoles Signal Variable Package BusinessDocument BusinessTransactionHead BinaryCollaboration MultiPartyCollaboration BusinessCollaboration OperationMapping
used by	element  ProcessSpecification
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. uuid xsd:string required         documentation Defines a string identification mechanism for a Process Specificiation. The uuid is not used for the purpose of versioning, so that even a change introduced by AttributeSubstitution (to business documents’ schemas, for example), would be marked by a new uuid.
annotation	documentation Type for the root element of a Process Specification document.
source	<xsd:complexType name="ProcessSpecificationType">   <xsd:annotation>     <xsd:documentation>Type for the root element of a Process Specification document.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="AttributeSubstitution" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="ExternalRoles" minOccurs="0"/>     <xsd:element ref="Signal" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="Variable" minOccurs="0" maxOccurs="unbounded"/>     <xsd:choice minOccurs="0" maxOccurs="unbounded">       <xsd:element ref="Package" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="BusinessDocument" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="BusinessTransactionHead" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="BinaryCollaboration" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="MultiPartyCollaboration" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="BusinessCollaboration" minOccurs="0" maxOccurs="unbounded"/>       <xsd:element ref="OperationMapping" minOccurs="0" maxOccurs="unbounded"/>     </xsd:choice>   </xsd:sequence>   <xsd:attributeGroup ref="name"/>   <xsd:attribute name="uuid" type="xsd:string" use="required">     <xsd:annotation>       <xsd:documentation>Defines a string identification mechanism for a Process Specificiation. The uuid is not used for the purpose of versioning, so that even a change introduced by AttributeSubstitution (to business documents’ schemas, for example), would be marked by a new uuid.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute ProcessSpecificationType/@uuid

type	xsd:string
properties	isRef  0 use  required
annotation	documentation Defines a string identification mechanism for a Process Specificiation. The uuid is not used for the purpose of versioning, so that even a change introduced by AttributeSubstitution (to business documents’ schemas, for example), would be marked by a new uuid.
source	<xsd:attribute name="uuid" type="xsd:string" use="required">   <xsd:annotation>     <xsd:documentation>Defines a string identification mechanism for a Process Specificiation. The uuid is not used for the purpose of versioning, so that even a change introduced by AttributeSubstitution (to business documents’ schemas, for example), would be marked by a new uuid.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType ReceiptAcknowledgementExceptionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of SignalEnvelopeType
properties	base  SignalEnvelopeType
children	Documentation
used by	elements  BusinessTransactionType/RespondingBusinessActivity/ReceiptAcknowledgementException BusinessTransactionType/RequestingBusinessActivity/ReceiptAcknowledgementException BusinessActionType/ReceiptAcknowledgementException LegacyBusinessTransaction/RespondingBusinessActivity/ReceiptAcknowledgementException LegacyBusinessTransaction/RequestingBusinessActivity/ReceiptAcknowledgementException DataExchange/RespondingBusinessActivity/ReceiptAcknowledgementException DataExchange/RequestingBusinessActivity/ReceiptAcknowledgementException Notification/RespondingBusinessActivity/ReceiptAcknowledgementException Notification/RequestingBusinessActivity/ReceiptAcknowledgementException InformationDistribution/RespondingBusinessActivity/ReceiptAcknowledgementException InformationDistribution/RequestingBusinessActivity/ReceiptAcknowledgementException QueryResponse/RespondingBusinessActivity/ReceiptAcknowledgementException QueryResponse/RequestingBusinessActivity/ReceiptAcknowledgementException RequestResponse/RespondingBusinessActivity/ReceiptAcknowledgementException RequestResponse/RequestingBusinessActivity/ReceiptAcknowledgementException RequestConfirm/RespondingBusinessActivity/ReceiptAcknowledgementException RequestConfirm/RequestingBusinessActivity/ReceiptAcknowledgementException
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal       false   documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
annotation	documentation The type of a BusinessAction Business Signal of exception Receipt Acknowledgement. A Business Signal is used for state alignment. Note: this type was added in v2.0.
source	<xsd:complexType name="ReceiptAcknowledgementExceptionType">   <xsd:annotation>     <xsd:documentation>The type of a BusinessAction Business Signal of exception Receipt Acknowledgement. A Business Signal is used for state alignment. Note: this type was added in v2.0. </xsd:documentation>   </xsd:annotation>   <xsd:complexContent>     <xsd:extension base="SignalEnvelopeType">       <xsd:attribute name="isPositiveSignal" fixed="false">         <xsd:annotation>           <xsd:documentation>For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0. </xsd:documentation>         </xsd:annotation>       </xsd:attribute>     </xsd:extension>   </xsd:complexContent> </xsd:complexType>

attribute ReceiptAcknowledgementExceptionType/@isPositiveSignal

properties	isRef  0 fixed  false
annotation	documentation For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0.
source	<xsd:attribute name="isPositiveSignal" fixed="false">   <xsd:annotation>     <xsd:documentation>For ReceiptAcknowledgementExceptionType, specifies whether positive receipt of a Business Signal is not allowed (i.e. the Business Signal is an exception). Note: This attribute was added in v2.0. </xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType ReceiptAcknowledgementType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of SignalEnvelopeType
properties	base  SignalEnvelopeType
children	Documentation
used by	elements  BusinessTransactionType/RespondingBusinessActivity/ReceiptAcknowledgement BusinessTransactionType/RequestingBusinessActivity/ReceiptAcknowledgement BusinessActionType/ReceiptAcknowledgement LegacyBusinessTransaction/RespondingBusinessActivity/ReceiptAcknowledgement LegacyBusinessTransaction/RequestingBusinessActivity/ReceiptAcknowledgement DataExchange/RespondingBusinessActivity/ReceiptAcknowledgement DataExchange/RequestingBusinessActivity/ReceiptAcknowledgement Notification/RespondingBusinessActivity/ReceiptAcknowledgement Notification/RequestingBusinessActivity/ReceiptAcknowledgement InformationDistribution/RespondingBusinessActivity/ReceiptAcknowledgement InformationDistribution/RequestingBusinessActivity/ReceiptAcknowledgement QueryResponse/RespondingBusinessActivity/ReceiptAcknowledgement QueryResponse/RequestingBusinessActivity/ReceiptAcknowledgement RequestResponse/RespondingBusinessActivity/ReceiptAcknowledgement RequestResponse/RequestingBusinessActivity/ReceiptAcknowledgement RequestConfirm/RespondingBusinessActivity/ReceiptAcknowledgement RequestConfirm/RequestingBusinessActivity/ReceiptAcknowledgement
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0. isPositiveSignal xsd:boolean       true   documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
annotation	documentation The type of Business Action Business Signal of positive Receipt Acknowledgement. A Business Signal is used for state alignment. Note: This type was added in v2.0.
source	<xsd:complexType name="ReceiptAcknowledgementType">   <xsd:annotation>     <xsd:documentation>The type of Business Action Business Signal of positive Receipt Acknowledgement. A Business Signal is used for state alignment. Note: This type was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:complexContent>     <xsd:extension base="SignalEnvelopeType">       <xsd:attribute name="isPositiveSignal" type="xsd:boolean" fixed="true">         <xsd:annotation>           <xsd:documentation>ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.</xsd:documentation>         </xsd:annotation>       </xsd:attribute>     </xsd:extension>   </xsd:complexContent> </xsd:complexType>

attribute ReceiptAcknowledgementType/@isPositiveSignal

type	xsd:boolean
properties	isRef  0 fixed  true
annotation	documentation ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.
source	<xsd:attribute name="isPositiveSignal" type="xsd:boolean" fixed="true">   <xsd:annotation>     <xsd:documentation>ReceiptAcknowledgementType specifies whether positive receipt of a Business Signal is required (i.e. the Business Signal is not an exception). Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType RequestingBusinessActivityType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessActionType
properties	base  BusinessActionType
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
used by	elements  RequestingBusinessActivity RequestConfirm/RequestingBusinessActivity RequestResponse/RequestingBusinessActivity QueryResponse/RequestingBusinessActivity InformationDistribution/RequestingBusinessActivity Notification/RequestingBusinessActivity DataExchange/RequestingBusinessActivity LegacyBusinessTransaction/RequestingBusinessActivity BusinessTransactionType/RequestingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          documentation When a party uses isAuthorizationRequired on a Requesting and/or a Responding activity accordingly, the result that [the activity] will only be processed as valid if the party interpreting it successfully matches the stated identity of the activity's [Role] to a list of allowed values previously supplied by that party. Authorization typically relates to a signed business document and the association to the role identity of the party expected for that activity. isIntelligibleCheckRequired xsd:boolean          documentation Allows partners to agree that a message is confirmed by a Receipt Acknowledgement only if it is also legible. Legible means that it has passed structure/schema validity check. The content of the receipt and the legibility of a business message (if required) are reviewed prior to the processing of the Business Document or the evaluation of Condition Expressions in the business message's Business Documents or Document Envelope. isNonRepudiationRequired xsd:boolean          documentation If non-repudiation of origin and content is required, then the Business Activity stores the business document in its original form for the duration mutually agreed to in an agreement. isNonRepudiationReceiptRequired xsd:boolean          documentation Both parties agree to mutually verify receipt of a Requesting Business Document and that the receipt is non-repudiable. timeToAcknowledgeReceipt xsd:duration          documentation The time a Responding or Requesting role has to acknowledge receipt of a Business Document. timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
annotation	documentation The type related to the Requesting Business Action.
source	<xsd:complexType name="RequestingBusinessActivityType">   <xsd:annotation>     <xsd:documentation>The type related to the Requesting Business Action.</xsd:documentation>   </xsd:annotation>   <xsd:complexContent>     <xsd:extension base="BusinessActionType"/>   </xsd:complexContent> </xsd:complexType>

complexType RespondingBusinessActivityType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	extension of BusinessActionType
properties	base  BusinessActionType
children	Documentation DocumentEnvelope ReceiptAcknowledgement ReceiptAcknowledgementException AcceptanceAcknowledgement AcceptanceAcknowledgementException
used by	elements  RespondingBusinessActivity RequestConfirm/RespondingBusinessActivity RequestResponse/RespondingBusinessActivity QueryResponse/RespondingBusinessActivity InformationDistribution/RespondingBusinessActivity Notification/RespondingBusinessActivity DataExchange/RespondingBusinessActivity LegacyBusinessTransaction/RespondingBusinessActivity BusinessTransactionType/RespondingBusinessActivity
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. isAuthorizationRequired xsd:boolean          documentation When a party uses isAuthorizationRequired on a Requesting and/or a Responding activity accordingly, the result that [the activity] will only be processed as valid if the party interpreting it successfully matches the stated identity of the activity's [Role] to a list of allowed values previously supplied by that party. Authorization typically relates to a signed business document and the association to the role identity of the party expected for that activity. isIntelligibleCheckRequired xsd:boolean          documentation Allows partners to agree that a message is confirmed by a Receipt Acknowledgement only if it is also legible. Legible means that it has passed structure/schema validity check. The content of the receipt and the legibility of a business message (if required) are reviewed prior to the processing of the Business Document or the evaluation of Condition Expressions in the business message's Business Documents or Document Envelope. isNonRepudiationRequired xsd:boolean          documentation If non-repudiation of origin and content is required, then the Business Activity stores the business document in its original form for the duration mutually agreed to in an agreement. isNonRepudiationReceiptRequired xsd:boolean          documentation Both parties agree to mutually verify receipt of a Requesting Business Document and that the receipt is non-repudiable. timeToAcknowledgeReceipt xsd:duration          documentation The time a Responding or Requesting role has to acknowledge receipt of a Business Document. timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
annotation	documentation The type related to the Responding Business Action.
source	<xsd:complexType name="RespondingBusinessActivityType">   <xsd:annotation>     <xsd:documentation>The type related to the Responding Business Action.</xsd:documentation>   </xsd:annotation>   <xsd:complexContent>     <xsd:extension base="BusinessActionType"/>   </xsd:complexContent> </xsd:complexType>

complexType RoleType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation
used by	elements  BusinessTransactionBaseType/RequestingRole BusinessTransactionBaseType/RespondingRole BinaryCollaborationType/Role MultiPartyCollaborationType/Role BusinessCollaborationType/Role
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation The type related to the Role of a Business Collaboration. For example, in a Business Collaboration, two or more top-level roles apply. The Role Type is a global element, that allows Role elements to be defined of Role Type.
source	<xsd:complexType name="RoleType">   <xsd:annotation>     <xsd:documentation>The type related to the Role of a Business Collaboration. For example, in a Business Collaboration, two or more top-level roles apply. The Role Type is a global element, that allows Role elements to be defined of Role Type.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0"/>   </xsd:sequence>   <xsd:attributeGroup ref="name"/> </xsd:complexType>

complexType SignalEnvelopeType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation
used by	complexTypes  AcceptanceAcknowledgementExceptionType AcceptanceAcknowledgementType GeneralExceptionType ReceiptAcknowledgementExceptionType ReceiptAcknowledgementType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance. signalDefinitionRef xsd:IDREF required         documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0.
annotation	documentation The type of a Signal Envelope definition that conveys Business Action information. This type for Business Signals mirrors the Document Envelope structure (where applicable). A Business Signal is used for state alignment. Note: This type was added in v2.0.
source	<xsd:complexType name="SignalEnvelopeType">   <xsd:annotation>     <xsd:documentation>The type of a Signal Envelope definition that conveys Business Action information. This type for Business Signals mirrors the Document Envelope structure (where applicable). A Business Signal is used for state alignment. Note: This type was added in v2.0. </xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="name"/>   <xsd:attribute name="signalDefinitionRef" type="xsd:IDREF" use="required">     <xsd:annotation>       <xsd:documentation>The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:complexType>

attribute SignalEnvelopeType/@signalDefinitionRef

type	xsd:IDREF
properties	isRef  0 use  required
annotation	documentation The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0.
source	<xsd:attribute name="signalDefinitionRef" type="xsd:IDREF" use="required">   <xsd:annotation>     <xsd:documentation>The nameID reference of the Business Signal definition for the Business Signal. Note: This attribute was added in v2.0.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

complexType SignalType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation ConditionExpression Specification
used by	element  Signal
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation The type of a Signal element. A Business Signal is used for state alignment. This construct allows specification references (such as those used for context), and a Signal Type may have 0..n Condition Expression. Note: This type was added in v2.0.
source	<xsd:complexType name="SignalType">   <xsd:annotation>     <xsd:documentation>The type of a Signal element. A Business Signal is used for state alignment. This construct allows specification references (such as those used for context), and a Signal Type may have 0..n Condition Expression. Note: This type was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="ConditionExpression" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="Specification" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="name"/> </xsd:complexType>

complexType StartType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	Documentation ToLink
used by	element  Start
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
annotation	documentation The type related to the Start of a specific Collaboration type within the Collaboration Group.
source	<xsd:complexType name="StartType">   <xsd:annotation>     <xsd:documentation>The type related to the Start of a specific Collaboration type within the Collaboration Group.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>     <xsd:element ref="ToLink" maxOccurs="unbounded"/>   </xsd:sequence>   <xsd:attributeGroup ref="optname"/> </xsd:complexType>

complexType TransitionType

diagram
namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
children	FromLink ToLink
used by	element  Transition
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
annotation	documentation The type related to the traverse between business states.
source	<xsd:complexType name="TransitionType">   <xsd:annotation>     <xsd:documentation>The type related to the traverse between business states.</xsd:documentation>   </xsd:annotation>   <xsd:sequence>     <xsd:element ref="FromLink"/>     <xsd:element ref="ToLink"/>   </xsd:sequence>   <xsd:attributeGroup ref="optname"/> </xsd:complexType>

simpleType BusinessDocumentValueList

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	list of xsd:NMTOKEN
used by	element  StatusVisibility/BusinessDocumentList
annotation	documentation The simpleType related to the (future) enumerated list for the Business Document list associated with the Status Visibility element. This simpleType is used in exposing visibility to documents from more deeply nested BTA. Thoses values are to be available as the expression language listed. Note: This simpleType was added in v2.0.
source	<xsd:simpleType name="BusinessDocumentValueList">   <xsd:annotation>     <xsd:documentation>The simpleType related to the (future) enumerated list for the Business Document list associated with the Status Visibility element. This simpleType is used in exposing visibility to documents from more deeply nested BTA. Thoses values are to be available as the expression language listed. Note: This simpleType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:list itemType="xsd:NMTOKEN"/> </xsd:simpleType>

simpleType ConditionGuardValue

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of xsd:NMTOKEN
used by	simpleType  ConditionGuardValueList attribute  FromLink/@conditionGuard
facets	enumeration  ProtocolSuccess enumeration  AnyProtocolFailure enumeration  RequestReceiptFailure enumeration  RequestAcceptanceFailure enumeration  ResponseReceiptFailure enumeration  ResponseAcceptanceFailure enumeration  SignalTimeout enumeration  ResponseTimeout enumeration  BusinessSuccess enumeration  BusinessFailure enumeration  Success enumeration  Failure
annotation	documentation The simpleType related to the enumerated list for the guard values associated with the FromLink in a Completion State. Each of the FromLinks in a Completion State can be specified to transition as a result of the ConditionGuardValues. This check is made every time a transition occurs from the real states. Because the FromLinks generally are from a specific state, only when that state has been reached is the check of conditionGuards from that state checked. Business Success and Failure relate to the business documents received. While conversely, any timeout is a business protocol failure, i.e. the state is not aligned. Note: This simpleType was added in v2.0.
source	<xsd:simpleType name="ConditionGuardValue">   <xsd:annotation>     <xsd:documentation>The simpleType related to the enumerated list for the guard values associated with the FromLink in a Completion State. Each of the FromLinks in a Completion State can be specified to transition as a result of the ConditionGuardValues. This check is made every time a transition occurs from the real states. Because the FromLinks generally are from a specific state, only when that state has been reached is the check of conditionGuards from that state checked. Business Success and Failure relate to the business documents received. While conversely, any timeout is a business protocol failure, i.e. the state is not aligned. Note: This simpleType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:restriction base="xsd:NMTOKEN">     <xsd:enumeration value="ProtocolSuccess"/>     <xsd:enumeration value="AnyProtocolFailure"/>     <xsd:enumeration value="RequestReceiptFailure"/>     <xsd:enumeration value="RequestAcceptanceFailure"/>     <xsd:enumeration value="ResponseReceiptFailure"/>     <xsd:enumeration value="ResponseAcceptanceFailure"/>     <xsd:enumeration value="SignalTimeout"/>     <xsd:enumeration value="ResponseTimeout"/>     <xsd:enumeration value="BusinessSuccess"/>     <xsd:enumeration value="BusinessFailure"/>     <xsd:enumeration value="Success"/>     <xsd:enumeration value="Failure"/>   </xsd:restriction> </xsd:simpleType>

simpleType ConditionGuardValueList

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	list of ConditionGuardValue
used by	element  StatusVisibility/SubstateVisibility
annotation	documentation The simpleType related to the content model for Status Visibility. Note: This simpleType was added in v2.0.
source	<xsd:simpleType name="ConditionGuardValueList">   <xsd:annotation>     <xsd:documentation>The simpleType related to the content model for Status Visibility. Note: This simpleType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:list itemType="ConditionGuardValue"/> </xsd:simpleType>

simpleType DocumentSpecificationType

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of xsd:NMTOKEN
used by	attribute  Specification/@type
facets	enumeration  schema enumeration  dtd enumeration  wsdl enumeration  relaxng enumeration  schematron enumeration  other
annotation	documentation The simpleType related to the enumerated list of specification types for the Specification element. Note: This simpleType was added in v2.0.
source	<xsd:simpleType name="DocumentSpecificationType">   <xsd:annotation>     <xsd:documentation>The simpleType related to the enumerated list of specification types for the Specification element. Note: This simpleType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:restriction base="xsd:NMTOKEN">     <xsd:enumeration value="schema"/>     <xsd:enumeration value="dtd"/>     <xsd:enumeration value="wsdl"/>     <xsd:enumeration value="relaxng"/>     <xsd:enumeration value="schematron"/>     <xsd:enumeration value="other"/>   </xsd:restriction> </xsd:simpleType>

simpleType ExpressionLanguageType

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of xsd:NMTOKEN
used by	attribute  ConditionExpressionType/@expressionLanguage
facets	enumeration  ConditionGuardValue enumeration  DocumentEnvelope enumeration  XPath1 enumeration  XSLT1 enumeration  CAM1 enumeration  XPath2 enumeration  XSLT2 enumeration  XQuery1
annotation	documentation This simpleType relates to the types of Expression language. An enumerated list is provided. Note: This simpleType was added in v2.0.
source	<xsd:simpleType name="ExpressionLanguageType">   <xsd:annotation>     <xsd:documentation>This simpleType relates to the types of Expression language. An enumerated list is provided. Note: This simpleType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:restriction base="xsd:NMTOKEN">     <xsd:enumeration value="ConditionGuardValue"/>     <xsd:enumeration value="DocumentEnvelope"/>     <xsd:enumeration value="XPath1"/>     <xsd:enumeration value="XSLT1"/>     <xsd:enumeration value="CAM1"/>     <xsd:enumeration value="XPath2"/>     <xsd:enumeration value="XSLT2"/>     <xsd:enumeration value="XQuery1"/>   </xsd:restriction> </xsd:simpleType>

simpleType StepType

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of xsd:NMTOKEN
used by	attribute  map/@operationStep
facets	enumeration  input enumeration  output enumeration  fault
annotation	documentation The simpleType related to the enumerated list of operation types supported by OperationMapping and OperationMappingType. Note: This simpleType was added in v2.0.
source	<xsd:simpleType name="StepType">   <xsd:annotation>     <xsd:documentation>The simpleType related to the enumerated list of operation types supported by OperationMapping and OperationMappingType. Note: This simpleType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:restriction base="xsd:NMTOKEN">     <xsd:enumeration value="input"/>     <xsd:enumeration value="output"/>     <xsd:enumeration value="fault"/>   </xsd:restriction> </xsd:simpleType>

simpleType TimeToPerformType

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
type	restriction of xsd:NMTOKEN
used by	attribute  TimeToPerform/@type
facets	enumeration  design enumeration  configuration enumeration  runtime
annotation	documentation The simpleType related to the definition of Time To Perform during the process lifecycle. Allows for late binding. Note: This simpleType was added in v2.0.
source	<xsd:simpleType name="TimeToPerformType">   <xsd:annotation>     <xsd:documentation>The simpleType related to the definition of Time To Perform during the process lifecycle. Allows for late binding. Note: This simpleType was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:restriction base="xsd:NMTOKEN">     <xsd:enumeration value="design"/>     <xsd:enumeration value="configuration"/>     <xsd:enumeration value="runtime"/>   </xsd:restriction> </xsd:simpleType>

attributeGroup documentSecurity

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
used by	element  Attachment complexType  DocumentEnvelopeType
attributes	Name   Type   Use   Default   Fixed   Annotation isAuthenticated derived by: xsd:NMTOKEN          documentation The communications channel used to transport the Message provides transient authentication. The specific method will be determined by the communications protocol used. Persistent authentication means the Business Document signer’s identity is verified at the receiving application level. Authentication assists in verification of role identity of a participating party. isConfidential derived by: xsd:NMTOKEN          documentation Transient confidentiality is provided by a secure network protocol, such as SSL as the document is transferred between two adjacent ebXML Messaging Service or other transport messaging nodes. Persistent confidentiality is intended to preserve the confidentiality of the message such that only the intended party (application) can see it. isTamperDetectable derived by: xsd:NMTOKEN          documentation Transient isTamperDetectable is the ability to detect if the information has been tampered with during transfer between two adjacent Message Service Handler nodes. Persistent isTamperDetectable is the ability to detect if the information has been tampered with after it has been received by messaging node, between the messaging node and the application. Tamper detection assists in verification of content integrity between and within a participating party.
annotation	documentation The attributeGroup related to document security, quality of service attributes. These attributes relate to the BT patterns and the operational semantics surrounding their use.
source	<xsd:attributeGroup name="documentSecurity">   <xsd:annotation>     <xsd:documentation>The attributeGroup related to document security, quality of service attributes. These attributes relate to the BT patterns and the operational semantics surrounding their use. </xsd:documentation>   </xsd:annotation>   <xsd:attribute name="isAuthenticated">     <xsd:annotation>       <xsd:documentation>The communications channel used to transport the Message provides transient authentication. The specific method will be determined by the communications protocol used. Persistent authentication means the Business Document signer’s identity is verified at the receiving application level. Authentication assists in verification of role identity of a participating party.</xsd:documentation>     </xsd:annotation>     <xsd:simpleType>       <xsd:restriction base="xsd:NMTOKEN">         <xsd:enumeration value="none"/>         <xsd:enumeration value="transient"/>         <xsd:enumeration value="persistent"/>         <xsd:enumeration value="transient-and-persistent"/>       </xsd:restriction>     </xsd:simpleType>   </xsd:attribute>   <xsd:attribute name="isConfidential">     <xsd:annotation>       <xsd:documentation>Transient confidentiality is provided by a secure network protocol, such as SSL as the document is transferred between two adjacent ebXML Messaging Service or other transport messaging nodes. Persistent confidentiality is intended to preserve the confidentiality of the message such that only the intended party (application) can see it.</xsd:documentation>     </xsd:annotation>     <xsd:simpleType>       <xsd:restriction base="xsd:NMTOKEN">         <xsd:enumeration value="none"/>         <xsd:enumeration value="transient"/>         <xsd:enumeration value="persistent"/>         <xsd:enumeration value="transient-and-persistent"/>       </xsd:restriction>     </xsd:simpleType>   </xsd:attribute>   <xsd:attribute name="isTamperDetectable">     <xsd:annotation>       <xsd:documentation>Transient isTamperDetectable is the ability to detect if the information has been tampered with during transfer between two adjacent Message Service Handler nodes. Persistent isTamperDetectable is the ability to detect if the information has been tampered with after it has been received by messaging node, between the messaging node and the application. Tamper detection assists in verification of content integrity between and within a participating party.</xsd:documentation>     </xsd:annotation>     <xsd:simpleType>       <xsd:restriction base="xsd:NMTOKEN">         <xsd:enumeration value="none"/>         <xsd:enumeration value="transient"/>         <xsd:enumeration value="persistent"/>         <xsd:enumeration value="transient-and-persistent"/>       </xsd:restriction>     </xsd:simpleType>   </xsd:attribute> </xsd:attributeGroup>

attributeGroup map

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
used by	elements  OperationMappingType/MessageMap OperationMappingType/SignalMap
attributes	Name   Type   Use   Default   Fixed   Annotation interfaceName xsd:NMTOKEN required         documentation Interface is called portType in WSDL 1.1. The name of the interface or portType mapped logically in Operation Mapping. Note: This attribute was added in v2.0. operationName xsd:NMTOKEN required         documentation The name of the operation mapped in the OperationMapping. Note: This attribute was added in v2.0. operationStep StepType required         documentation The name of operation step from the Step Type enumeration list for OperationMapping. Note: This attribute was added in v2.0. documentEnvelopeRef xsd:IDREF required         documentation The nameID reference of the Document Envelope related to the OperationMapping. Note: This attribute was added in v2.0.
annotation	documentation The attributeGroup related to interface/operation types supported by OperationMapping and OperationMappingType. The abstract map includes the interface, operation, the step (see StepType) and the document reference. Note: This attributeGroup was added in v2.0.
source	<xsd:attributeGroup name="map">   <xsd:annotation>     <xsd:documentation>The attributeGroup related to interface/operation types supported by OperationMapping and OperationMappingType. The abstract map includes the interface, operation, the step (see StepType) and the document reference. Note: This attributeGroup was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:attribute name="interfaceName" type="xsd:NMTOKEN" use="required">     <xsd:annotation>       <xsd:documentation>Interface is called portType in WSDL 1.1. The name of the interface or portType mapped logically in Operation Mapping. Note: This attribute was added in v2.0.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="operationName" type="xsd:NMTOKEN" use="required">     <xsd:annotation>       <xsd:documentation>The name of the operation mapped in the OperationMapping. Note: This attribute was added in v2.0.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="operationStep" type="StepType" use="required">     <xsd:annotation>       <xsd:documentation>The name of operation step from the Step Type enumeration list for OperationMapping. Note: This attribute was added in v2.0.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="documentEnvelopeRef" type="xsd:IDREF" use="required">     <xsd:annotation>       <xsd:documentation>The nameID reference of the Document Envelope related to the OperationMapping. Note: This attribute was added in v2.0.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:attributeGroup>

attributeGroup name

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
used by	elements  Attachment ExternalRolesType/BusinessPartnerRole Specification StatusVisibility Variable complexTypes  BinaryCollaborationType BusinessActionType BusinessActivityType BusinessCollaborationType BusinessDocumentType BusinessTransactionBaseType DocumentEnvelopeType MultiPartyCollaborationType OperationMappingType PackageType ProcessSpecificationType RoleType SignalEnvelopeType SignalType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string required         documentation A designation that may be relevant to a business analyst but is not intended for referencing. nameID xsd:ID required         documentation Used for referencing, for example, for identification of elements within an ebBP instance.
annotation	documentation The attributeGroup related to the identification information for most elements. For the name attribute, no white space restrictions are enforced. White space is not controlled but left to implementation to trigger faults or exceptions. Note: This group was enhanced to include not only name but nameID in v2.0.
source	<xsd:attributeGroup name="name">   <xsd:annotation>     <xsd:documentation>The attributeGroup related to the identification information for most elements. For the name attribute, no white space restrictions are enforced. White space is not controlled but left to implementation to trigger faults or exceptions. Note: This group was enhanced to include not only name but nameID in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:attribute name="name" type="xsd:string" use="required">     <xsd:annotation>       <xsd:documentation>A designation that may be relevant to a business analyst but is not intended for referencing.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="nameID" type="xsd:ID" use="required">     <xsd:annotation>       <xsd:documentation>Used for referencing, for example, for identification of elements within an ebBP instance.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:anyAttribute namespace="##other" processContents="lax"/> </xsd:attributeGroup>

attributeGroup optname

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
used by	complexTypes  CompletionType DecisionType ForkType JoinType StartType TransitionType
attributes	Name   Type   Use   Default   Fixed   Annotation name xsd:string          nameID xsd:ID
annotation	documentation The optname attributeGroup related to the identification information for some elements. This allows name or nameID to be optionally used. No white space restrictions are enforced. White space is not controlled but left to implementation to trigger faults or exceptions. Note: This group was added in v2.0.
source	<xsd:attributeGroup name="optname">   <xsd:annotation>     <xsd:documentation>The optname attributeGroup related to the identification information for some elements. This allows name or nameID to be optionally used. No white space restrictions are enforced. White space is not controlled but left to implementation to trigger faults or exceptions. Note: This group was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:attribute name="name" type="xsd:string"/>   <xsd:attribute name="nameID" type="xsd:ID"/>   <xsd:anyAttribute namespace="##other" processContents="lax"/> </xsd:attributeGroup>

attributeGroup quality

namespace	http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
used by	complexType  BusinessActionType
attributes	Name   Type   Use   Default   Fixed   Annotation isAuthorizationRequired xsd:boolean          documentation When a party uses isAuthorizationRequired on a Requesting and/or a Responding activity accordingly, the result that [the activity] will only be processed as valid if the party interpreting it successfully matches the stated identity of the activity's [Role] to a list of allowed values previously supplied by that party. Authorization typically relates to a signed business document and the association to the role identity of the party expected for that activity. isIntelligibleCheckRequired xsd:boolean          documentation Allows partners to agree that a message is confirmed by a Receipt Acknowledgement only if it is also legible. Legible means that it has passed structure/schema validity check. The content of the receipt and the legibility of a business message (if required) are reviewed prior to the processing of the Business Document or the evaluation of Condition Expressions in the business message's Business Documents or Document Envelope. isNonRepudiationRequired xsd:boolean          documentation If non-repudiation of origin and content is required, then the Business Activity stores the business document in its original form for the duration mutually agreed to in an agreement. isNonRepudiationReceiptRequired xsd:boolean          documentation Both parties agree to mutually verify receipt of a Requesting Business Document and that the receipt is non-repudiable. timeToAcknowledgeReceipt xsd:duration          documentation The time a Responding or Requesting role has to acknowledge receipt of a Business Document. timeToAcknowledgeAcceptance xsd:duration          documentation The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document. retryCount xsd:int          documentation The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.
annotation	documentation The attributeGroup related to quality of service attributes. These attributes relate to the BT patterns and the operational semantics surrounding their use. Note: This attributeGroup was added in v2.0.
source	<xsd:attributeGroup name="quality">   <xsd:annotation>     <xsd:documentation>The attributeGroup related to quality of service attributes. These attributes relate to the BT patterns and the operational semantics surrounding their use. Note: This attributeGroup was added in v2.0.</xsd:documentation>   </xsd:annotation>   <xsd:attribute name="isAuthorizationRequired" type="xsd:boolean">     <xsd:annotation>       <xsd:documentation>When a party uses isAuthorizationRequired on a Requesting and/or a Responding activity accordingly, the result that [the activity] will only be processed as valid if the party interpreting it successfully matches the stated identity of the activity's [Role] to a list of allowed values previously supplied by that party. Authorization typically relates to a signed business document and the association to the role identity of the party expected for that activity.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean">     <xsd:annotation>       <xsd:documentation>Allows partners to agree that a message is confirmed by a Receipt Acknowledgement only if it is also legible. Legible means that it has passed structure/schema validity check. The content of the receipt and the legibility of a business message (if required) are reviewed prior to the processing of the Business Document or the evaluation of Condition Expressions in the business message's Business Documents or Document Envelope. </xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean">     <xsd:annotation>       <xsd:documentation>If non-repudiation of origin and content is required, then the Business Activity stores the business document in its original form for the duration mutually agreed to in an agreement. </xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean">     <xsd:annotation>       <xsd:documentation>Both parties agree to mutually verify receipt of a Requesting Business Document and that the receipt is non-repudiable. </xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration">     <xsd:annotation>       <xsd:documentation>The time a Responding or Requesting role has to acknowledge receipt of a Business Document. </xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration">     <xsd:annotation>       <xsd:documentation>The time a Requesting and Responding role has to non-substantively acknowledge business acceptance of a Business Document.</xsd:documentation>     </xsd:annotation>   </xsd:attribute>   <xsd:attribute name="retryCount" type="xsd:int">     <xsd:annotation>       <xsd:documentation>The business retry for a RequestingBusinessActivity identifies the number of retries allowed in addition to the initial request while the Time To Perform has not been exceeded.</xsd:documentation>     </xsd:annotation>   </xsd:attribute> </xsd:attributeGroup>

attribute xml:base

namespace	http://www.w3.org/XML/1998/namespace
type	xsd:anyURI
annotation	documentation See http://www.w3.org/TR/xmlbase/ for                      information about this attribute.
source	<xsd:attribute name="base" type="xs:anyURI">   <xsd:annotation>     <xsd:documentation>See http://www.w3.org/TR/xmlbase/ for                      information about this attribute.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute xml:id

namespace	http://www.w3.org/XML/1998/namespace
type	xsd:ID
annotation	documentation See http://www.w3.org/TR/xml-id/ for                      information about this attribute.
source	<xsd:attribute name="id" type="xs:ID">   <xsd:annotation>     <xsd:documentation>See http://www.w3.org/TR/xml-id/ for                      information about this attribute.</xsd:documentation>   </xsd:annotation> </xsd:attribute>

attribute xml:lang

namespace	http://www.w3.org/XML/1998/namespace
type	union of (xsd:language, restriction of xsd:string)
annotation	documentation Attempting to install the relevant ISO 2- and 3-letter          codes as the enumerated possible values is probably never          going to be a realistic possibility.  See          RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry          at http://www.iana.org/assignments/lang-tag-apps.htm for          further information.          The union allows for the 'un-declaration' of xml:lang with          the empty string.
source	<xsd:attribute name="lang">   <xsd:annotation>     <xsd:documentation>Attempting to install the relevant ISO 2- and 3-letter          codes as the enumerated possible values is probably never          going to be a realistic possibility.  See          RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry          at http://www.iana.org/assignments/lang-tag-apps.htm for          further information.          The union allows for the 'un-declaration' of xml:lang with          the empty string.</xsd:documentation>   </xsd:annotation>   <xsd:simpleType>     <xsd:union memberTypes="xs:language">       <xsd:simpleType>         <xsd:restriction base="xs:string">           <xsd:enumeration value=""/>         </xsd:restriction>       </xsd:simpleType>     </xsd:union>   </xsd:simpleType> </xsd:attribute>

attribute xml:space

namespace	http://www.w3.org/XML/1998/namespace
type	restriction of xsd:NCName
facets	enumeration  default enumeration  preserve
source	<xsd:attribute name="space">   <xsd:simpleType>     <xsd:restriction base="xs:NCName">       <xsd:enumeration value="default"/>       <xsd:enumeration value="preserve"/>     </xsd:restriction>   </xsd:simpleType> </xsd:attribute>

attributeGroup xml:specialAttrs

namespace	http://www.w3.org/XML/1998/namespace
attributes	Name   Type   Use   Default   Fixed   Annotation xml:base          documentation See http://www.w3.org/TR/xmlbase/ for                      information about this attribute. xml:lang          documentation Attempting to install the relevant ISO 2- and 3-letter          codes as the enumerated possible values is probably never          going to be a realistic possibility.  See          RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry          at http://www.iana.org/assignments/lang-tag-apps.htm for          further information.          The union allows for the 'un-declaration' of xml:lang with          the empty string. xml:space
source	<xsd:attributeGroup name="specialAttrs">   <xsd:attribute ref="xml:base"/>   <xsd:attribute ref="xml:lang"/>   <xsd:attribute ref="xml:space"/> </xsd:attributeGroup>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy