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 b