[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ebBP 2/15/2005: Updated Draft Schema
Integrates the changes we discussed today to add more annotations on the BT patterns and the DocumentEnvelopeNotation. This also integrates updates requested by Dale. This will be posted with the technical specification draft later this week. Thanks to everyone for their hard work.
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://www.oasis-open.org/committees/ebBP/BPS/2.0"; xmlns="http://www.oasis-open.org/committees/ebBP/BPS/2.0"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xi="http://www.w3.org/2001/XInclude"; elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"; schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<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 BPSS instance version related to the target
BPSS (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 version of the Process Specification. Note:
This attribute was added in v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="instanceVersion" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Is the version of the Process Specification or
artifact instance. An example would be the Australian Wheat Board
v2.1. Note: This attribute was added in v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:unique name="ProcessSpecification-ID">
<xsd:selector xpath="."/>
<xsd:field xpath="nameID"/>
</xsd:unique>
</xsd:element>
<xsd:complexType name="ProcessSpecificationType">
<xsd:annotation>
<xsd:documentation>Type for the root element of a process specification document.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="AttributeSubstitution" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="ExternalRoles" minOccurs="0"/>
<xsd:element ref="Signal" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Variable" minOccurs="0" maxOccurs="unbounded"/>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element ref="Package" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="BusinessDocument" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="BusinessTransactionHead" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="BinaryCollaboration" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="MultiPartyCollaboration" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="BusinessCollaboration" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="OperationMapping" minOccurs="0" maxOccurs="unbounded"/>
</xsd:choice>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="uuid" type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation>Defines a string identification mechanism for a Process
Specificiation. The uuid SHALL NOT be 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. So while the same instance
version could appear in two documents with different schema namespaces, for
example, they each would have different uuids.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<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>
<xsd:complexType name="PackageType">
<xsd:annotation>
<xsd:documentation>Type for a hierarchical name scope containing reusable elements.</xsd:documentation>
</xsd:annotation>
<xsd:choice maxOccurs="unbounded">
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="AttributeSubstitution" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="ExternalRoles" minOccurs="0"/>
<xsd:element ref="Signal" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Variable" minOccurs="0" maxOccurs="unbounded"/>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:element ref="Package" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="BusinessDocument" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="BusinessTransactionHead" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="BinaryCollaboration" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="MultiPartyCollaboration" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="BusinessCollaboration" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="OperationMapping" minOccurs="0"/>
</xsd:choice>
</xsd:choice>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="parentRef" type="xsd:IDREF" use="optional">
<xsd:annotation>
<xsd:documentation>Defines the nameID reference for a Package.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<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: xml:lang added in v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="DocumentationType">
<xsd:annotation>
<xsd:documentation>Type for the user documentation for any element.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="uri" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>Defines the address of the Documentation object. A URL
can be a URI. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute ref="xml:lang"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!--AttributeSubstitution allowed to "edit" references (IDREFS) or other attribute values. -->
<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 can be used for document
substitution in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="AttributeSubstitutionType"/>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="AttributeSubstitutionType">
<xsd:annotation>
<xsd:documentation>Type for the attribute or document value used for substitution.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="nameIDRef" type="xsd:IDREF" use="required">
<xsd:annotation>
<xsd:documentation>Is the nameID reference to the Documentation related to a
particular element.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="attributeName" type="xsd:NMTOKEN" use="required">
<xsd:annotation>
<xsd:documentation>Is the name of an attribute of any element within the scope of
the substitution set. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="value" type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation>Is the value, which shall replace the current value of the
attribute. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<!--Include element is replaced by XInclude's include element. This include element is not imported into our schema, but should be processed (and replaced by the referenced XML) prior to validation of instances-->
<xsd:element name="ExternalRoles" type="ExternalRolesType">
<xsd:annotation>
<xsd:documentation>External role element maps to the actual roles used in a
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>
<xsd:complexType name="ExternalRolesType">
<xsd:annotation>
<xsd:documentation>Types for the external role that maps to actual roles in a
collaboration. Performs elements are needed when the values of Roles declared in a
collaboration differ from the values declared with the @name attribute. Note: This
complexType was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="BusinessPartnerRole" minOccurs="2" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0"/>
<xsd:element name="Performs" type="PerformsType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:group name="collaborationGroup">
<xsd:annotation>
<xsd:documentation>The group that includes the various types of Collaborations. Note: In
v2.0, the Business Collaboration is introduced and will replace Binary and
MultiParty Collaboration in a future version. Note: This group was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element ref="BusinessTransactionActivity" minOccurs="0"/>
<xsd:element ref="CollaborationActivity" minOccurs="0"/>
<xsd:element ref="ComplexBusinessTransactionActivity" minOccurs="0"/>
<xsd:element ref="Success" minOccurs="0"/>
<xsd:element ref="Failure" minOccurs="0"/>
<xsd:element ref="Transition" minOccurs="0"/>
<xsd:element ref="Fork" minOccurs="0"/>
<xsd:element ref="Join" minOccurs="0"/>
<xsd:element ref="Decision" minOccurs="0"/>
</xsd:choice>
</xsd:group>
<xsd:element name="BinaryCollaboration" type="BinaryCollaborationType">
<xsd:annotation>
<xsd:documentation>Two roles - Defines the interaction between two roles. Binary
Collaboration is a choreographed state of two collaboration roles. This
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>
<xsd:complexType name="BinaryCollaborationType">
<xsd:annotation>
<xsd:documentation>The type related to Binary Collaboration.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="Role" type="RoleType" minOccurs="2" maxOccurs="2"/>
<xsd:element ref="TimeToPerform"/>
<xsd:element ref="Start"/>
<xsd:group ref="collaborationGroup" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="pattern" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>May point to the pattern on which an activity or collaboration is
based. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isInnerCollaboration" type="xsd:boolean" default="false">
<xsd:annotation>
<xsd:documentation>Indicates whether or not this collaboration definition can only
be used within a collaboration activity (as a sub collaboration) or initiated
directly by a party.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:element name="MultiPartyCollaboration" type="MultiPartyCollaborationType">
<xsd:annotation>
<xsd:documentation>More than two roles - Defines the interaction between more than two
roles. Binary Collaboration is a choreographed state of more than two collaboration
roles. This collaboration is being deprecated.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="MultiPartyCollaborationType">
<xsd:annotation>
<xsd:documentation>The type related to MultiParty Collaboration.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="Role" type="RoleType" minOccurs="3" maxOccurs="unbounded"/>
<xsd:element ref="TimeToPerform"/>
<xsd:element ref="Start"/>
<xsd:group ref="collaborationGroup" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="pattern" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>May point to the pattern on which an activity or collaboration is based.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isInnerCollaboration" type="xsd:boolean" default="false">
<xsd:annotation>
<xsd:documentation>Indicates whether or not this collaboration definition can only
be used within a collaboration activity (as a sub collaboration) or initiated
directly by a party.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<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 roles. Binary Collaboration is a choreographed state of two or
more collaboration roles. This element will replace Binary and MultiParty
collaboration elements in a future version.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="BusinessCollaborationType">
<xsd:annotation>
<xsd:documentation>The type related to Business Collaboration.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="Role" type="RoleType" minOccurs="2" maxOccurs="unbounded"/>
<xsd:element ref="TimeToPerform"/>
<xsd:element ref="Start"/>
<xsd:group ref="collaborationGroup" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="pattern" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>May point to the pattern on which an activity or collaboration is based.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isInnerCollaboration" type="xsd:boolean" default="false">
<xsd:annotation>
<xsd:documentation>Indicates whether or not this collaboration definition can only
be used within a collaboration activity (as a sub collaboration) or initiated
directly by a party.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<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>
<xsd:complexType name="DocumentEnvelopeType">
<xsd:annotation>
<xsd:documentation>The Type related to envelope that conveys business information.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Attachment" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="businessDocumentRef" type="xsd:IDREF" use="required">
<xsd:annotation>
<xsd:documentation>Indicates the nameID reference to the logical business document.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isPositiveResponse" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Evaluates to TRUE or FALSE. If TRUE, the DocumentEnvelope is
intended as a positive response to a request. The value for this parameter is
used to evaluate a Business Success or Failure of the corresponding Business Transaction.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attributeGroup ref="documentSecurity"/>
</xsd:complexType>
<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>
<xsd:complexType name="BusinessDocumentType">
<xsd:annotation>
<xsd:documentation>The type related to a Business Document.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="ConditionExpression" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Specification" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
</xsd:complexType>
<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>
<xsd:element name="Specification">
<xsd:annotation>
<xsd:documentation>A specification element that can associate many references to a
particular BPSS element. For example, multiple specifications associated with a
logical Business Document. Note: This element was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="type" type="DocumentSpecificationType" use="optional" default="schema">
<xsd:annotation>
<xsd:documentation>This attribute defines the type of the Specification of the
particular BPSS element. Note: This attribute was added in v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="location" type="xsd:anyURI" use="required">
<xsd:annotation>
<xsd:documentation>The location of the Specification of the particular BPSS
element. Note: This attribute was added in v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="targetNamespace" type="xsd:anyURI" use="optional">
<xsd:annotation>
<xsd:documentation>The target namespace of the Specification of the particular
BPSS element. Note: This attribute was added in v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attributeGroup ref="name"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="BusinessTransactionActivity">
<xsd:annotation>
<xsd:documentation>Defines a business transaction activity within a collaboration. A
business transaction activity is a business activity that executes a business
transaction. Note in v2.0, isLegallyBinding has been replaced by hasLegalIntent.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessTransactionActivityType"/>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="BusinessTransactionActivityType">
<xsd:annotation>
<xsd:documentation>The type related to a Business Transaction Activity. Performs
elements are required to bind Role values to the Requesting and Responding
activities. The older initiatingRoleIDRef attribute is removed as insufficiently
versatile. Note: This complexType was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="BusinessActivityType">
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="TimeToPerform"/>
<xsd:element ref="Performs" minOccurs="2" maxOccurs="unbounded"/>
<xsd:element name="BeginsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="PreCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="PostCondition" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="EndsWhen" type="ConditionExpressionType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="businessTransactionRef" type="xsd:IDREF" use="required">
<xsd:annotation>
<xsd:documentation>The nameID reference for the Business Transaction.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="hasLegalIntent" type="xsd:boolean" default="false">
<xsd:annotation>
<xsd:documentation>Indicates that a particular activity that could
represents a statement or commitment between trading partners, and their
shared intent. Note: This attribute was renamed to hasLegalIntent from
isLegallyBinding in v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isConcurrent" type="xsd:boolean" default="true">
<xsd:annotation>
<xsd:documentation>A parameter that governs the flow of transactions. Unlike
the security and timing parameters it does not govern the internal flow
of a transaction, rather it determines whether at run-time multiple
instances of that business transaction activity can be ‘open’ at the
same time within any collaboration instance performed between any two
partners. isConcurrent limits the ability to execute multiple BTA of the
same BT across collaboration instances (with the same party), or within
the same collaboration if multiple paths are open. As a result, when
isConcurrent is set to false, the BSIs of each party are responsible for
serializing these business transaction activities.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<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 visibilty only not a
multiparty collaboration). The subparties in the cBTA are auxiliary partners (not
constrained by the Business Collaboration). Note: In v2.0, cBTA and other linking
constructs replace the onInitiation flag.</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>
<xsd:element name="StatusVisibility">
<xsd:annotation>
<xsd:documentation>Information (which can be aggregated) returned by the subparties of
an embedded Business Transaction Activity for visibility purposes to the cBTA. For
example, a subparty (requester in an embedded BTA that is responder in cBTA) returns
aggregated supplier information to the cBTA prior to the responder issuing an order
response. The Status Visibility element specifies which status values of the
embedded processes are considered, if any, when returning the status value to the
context of the cBTA. Note, this element was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BusinessDocumentList" type="BusinessDocumentValueList"/>
<xsd:element name="SubstateVisibility" type="ConditionGuardValueList"/>
<xsd:any/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:anyAttribute namespace="##any"/>
</xsd:complexType>
</xsd:element>
<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>
<xsd:complexType name="CollaborationActivityType">
<xsd:annotation>
<xsd:documentation>The type related to a Collaboration Activity.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="BusinessActivityType">
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Performs" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="collaborationRef" type="xsd:IDREF" use="required">
<xsd:annotation>
<xsd:documentation>The nameID reference for the collaboration performed by
the Collaboration Activity.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<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>
<xsd:element name="ToLink">
<xsd:annotation>
<xsd:documentation>A linking construct that indicates states that the current context
(containing element) can transition to. The ToLink/@toBusinessStateRef attribute
value references the state through its ID value. Completion States can have 0..n
ConditionExpressions that are checked at runtime to determine whether the transition
to a state is actually made. Note: This element was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessStateLinkType">
<xsd:attribute name="toBusinessStateRef" type="xsd:IDREF" use="required">
<xsd:annotation>
<xsd:documentation>The nameID reference of the Business State of the
link transitioned to.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="BusinessStateLinkType">
<xsd:annotation>
<xsd:documentation>The type related to the linking constructs (TO and FROM). The type
can have 0..n Condition Expression associated with it. Note: In v2.0, the linking
constructs on a transition replace the onInitiation flag. </xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0"/>
<xsd:element ref="ConditionExpression" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="ConditionExpression">
<xsd:annotation>
<xsd:documentation>An expression element that can be evaluated and provide a TRUE or
FALSE. Note: In v2.0, multiple Condition Expression languages and expressions can be
used. Note: In v2.0, the capability whereby multiple Condition Expression languages
and expressions can be used has been expanded (and can be used with variables).</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="ConditionExpressionType"/>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ConditionExpressionType">
<xsd:annotation>
<xsd:documentation>The type related to the expression element. XPath or XSLT may be used as expression languages in the Condition Expression. The Condition Expression
relates to the DocumentEnvelopeNotation defined in the v2.0 technical specification. For conformance, a BSI is required to support at least the XPath language, as well as the DocumentEnvelopeNotation (nameID of a Document Envelope), while use of XSLT is also recommended. Use of XPath and XSLT may be beneficial when variables are used. Note: This complexType was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="expressionLanguage" type="ExpressionLanguageType" use="required">
<xsd:annotation>
<xsd:documentation>Defines the language used for the Condition Expression.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="expression" type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation>Defines the value for the Condition Expression.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="defaultValue" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Allows a default value to be specified for the Condition Expression.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:element name="Start" type="StartType">
<xsd:annotation>
<xsd:documentation>The specific Collaboration started with to traverse a path through a
graph to a Completion State.</xsd:documentation>
</xsd:annotation>
<xsd:unique name="Start-ID">
<xsd:selector xpath="."/>
<xsd:field xpath="nameID"/>
</xsd:unique>
</xsd:element>
<xsd:complexType name="StartType">
<xsd:annotation>
<xsd:documentation>The type related to the Start of a specific Collaboration type within
the Collaboration Group.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="ToLink" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
</xsd:complexType>
<xsd:element name="Transition" type="TransitionType">
<xsd:annotation>
<xsd:documentation>The traverse between two business states in a Business Collaboration.
Choreography is expressed as transitions between business states. Transition to the
same business state is allowed.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="TransitionType">
<xsd:annotation>
<xsd:documentation>The type related to the traverse between business states.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="FromLink"/>
<xsd:element ref="ToLink"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="Decision" type="DecisionType">
<xsd:annotation>
<xsd:documentation>A business state (pseudo-state) on a transition. For example, a
choice. This is equivalent to a Decision in a UML activity diagram although the
semantics may differ. A Business Activity may have many incoming transitions but
only one outgoing one.</xsd:documentation>
</xsd:annotation>
<xsd:unique name="Decision-ID">
<xsd:selector xpath="."/>
<xsd:field xpath="nameID"/>
</xsd:unique>
</xsd:element>
<xsd:complexType name="DecisionType">
<xsd:annotation>
<xsd:documentation>The type related to a Decision business state (pseudo-state).</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="FromLink"/>
<xsd:element ref="ToLink" minOccurs="2" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
</xsd:complexType>
<xsd:element name="Fork" type="ForkType">
<xsd:annotation>
<xsd:documentation>A business state with one incoming transition and many outgoing
transitions. All outgoing transitions are considered to happen in parallel or
exclusive OR.</xsd:documentation>
</xsd:annotation>
<xsd:unique name="Fork-ID">
<xsd:selector xpath="."/>
<xsd:field xpath="nameID"/>
</xsd:unique>
</xsd:element>
<xsd:complexType name="ForkType">
<xsd:annotation>
<xsd:documentation>The type related to the Fork business state (pseudo-state).</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="TimeToPerform" minOccurs="0"/>
<xsd:element ref="FromLink"/>
<xsd:element ref="ToLink" minOccurs="2" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="type" use="optional" default="OR">
<xsd:annotation>
<xsd:documentation>Defines the type of Fork. OR: An OR value will mean that any
business activity pointed to by a transition coming from the fork might be
initiated. All activities may run in parallel. XOR: Only one of the possible
activities will run.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="OR"/>
<xsd:enumeration value="XOR"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
<xsd:element name="Join" type="JoinType">
<xsd:annotation>
<xsd:documentation>A business state where the activity is waiting for the completion of
one or more activities. Defines the point where one or more forked activities join.</xsd:documentation>
</xsd:annotation>
<xsd:unique name="Join-ID">
<xsd:selector xpath="."/>
<xsd:field xpath="nameID"/>
</xsd:unique>
</xsd:element>
<xsd:complexType name="JoinType">
<xsd:annotation>
<xsd:documentation>The type related to the Join business state (pseudo-state).</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="FromLink" minOccurs="2" maxOccurs="unbounded"/>
<xsd:element ref="ToLink" minOccurs="0"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="waitForAll" type="xsd:boolean" default="true">
<xsd:annotation>
<xsd:documentation>Indicates that all transitions coming into the Join shall be
executed in order for the collaboration to reach the Join state (AND-join). By
default, the Join is an AND-join.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:element name="Success" type="CompletionType">
<xsd:annotation>
<xsd:documentation>Defines a successful completion of a Collaboration as a transition
from an activity.</xsd:documentation>
</xsd:annotation>
<xsd:unique name="Success-ID">
<xsd:selector xpath="."/>
<xsd:field xpath="nameID"/>
</xsd:unique>
</xsd:element>
<xsd:element name="Failure" type="CompletionType">
<xsd:annotation>
<xsd:documentation>Defines a failure completion of a 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>
<xsd:complexType name="CompletionType">
<xsd:annotation>
<xsd:documentation>The type related to the Success for Failure completion of a
Collaboration as a transition from an activity.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="FromLink" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
</xsd:complexType>
<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>
<xsd:complexType name="BusinessActionType">
<xsd:annotation>
<xsd:documentation>The type related to the Business Action.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="DocumentEnvelope" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>
<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>
<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>
<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attributeGroup ref="quality"/>
</xsd:complexType>
<xsd:element name="RequestingBusinessActivity" type="RequestingBusinessActivityType">
<xsd:annotation>
<xsd:documentation>A Business Action performed by the requesting role within a Business
Transaction. </xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="RequestingBusinessActivityType">
<xsd:annotation>
<xsd:documentation>The type related to the requesting Business Action.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="BusinessActionType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="RespondingBusinessActivity" type="RespondingBusinessActivityType">
<xsd:annotation>
<xsd:documentation>A Business Action performed by the responding role within a Business Transaction.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="RespondingBusinessActivityType">
<xsd:annotation>
<xsd:documentation>The type related to the responding Business Action.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="BusinessActionType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="BusinessActivityType">
<xsd:annotation>
<xsd:documentation>The type related to the Business Transaction Activity or
Collaboration Activity types (and business state).</xsd:documentation>
</xsd:annotation>
<xsd:attributeGroup ref="name"/>
</xsd:complexType>
<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 CBTA. 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 or when they need to be switched. (The main referring contexts for
Collaborations are the content models of the CollaborationActivity and ExternalRoles
elements.The BTAs and CBTAs are the other referring contexts previously discussed.)
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>
<xsd:complexType name="PerformsType">
<xsd:annotation>
<xsd:documentation>The type related to the role binding Performs element.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="currentRoleRef" type="xsd:IDREF" use="required">
<xsd:annotation>
<xsd:documentation>The currentRoleRef attribute defines the nameID reference of the
specific role currently used in an activity. If roles change, this name ID
reference for the currently used role is the referring role that is linked to
the referred-to role in the performsRoleRef. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="performsRoleRef" type="xsd:IDREF" use="optional">
<xsd:annotation>
<xsd:documentation>The performsRoleRef attribute defines nameID reference of the
referred-to role for the specific in an activity. This referred-to role is bound
to the referring role (currentRoleRef). </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="initiatingRoleRef" type="xsd:IDREF" use="optional">
<xsd:annotation>
<xsd:documentation>The initiatingRoleRef attribute defines nameID reference to the
role that initiates the activity.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="respondingRoleRef" type="xsd:IDREF" use="optional">
<xsd:annotation>
<xsd:documentation>The respondingRoleRef attribute defines nameID reference for the
role that responds in an activity.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:complexType name="RoleType">
<xsd:annotation>
<xsd:documentation>The type related to the Role of a Collaboration. For example, in a
Business Collaboration, two or more top-level roles apply. The Role Type is a global
element, that allows Role elements to be defined of Role Type.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required"/>
<xsd:attribute name="nameID" type="xsd:ID" use="required"/>
</xsd:complexType>
<xsd:element name="BusinessTransactionHead" type="BusinessTransactionType" abstract="true">
<xsd:annotation>
<xsd:documentation>The abstract superclass associated with the concrete set of defined
Business Transaction patterns. Note, in v2.0, the Business Transaction Head replaces
the Business Transaction element. A Business Transaction is a set of business
information and business signal exchanges amongst partners that occurs in an agreed
upon format and sequence (as supported by the patterns). In v2.0, the Business
Transaction Head, the concrete set of BT patterns and the Data Exchange element
(allows pattern specialization) enable business exchange through a defined pattern.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="BusinessTransactionType">
<xsd:annotation>
<xsd:documentation>The type related to the abstract superclass associated with Business Transactions.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="pattern" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>May point to the pattern on which the Business Transaction is
based. This attribute is retained for backward compatibility. The concrete
Business Transaction patterns are also specified. This attribute should not be
used if one of the concrete, extensible (Data Exchange) or Business Transaction
(used for conversion purposes only) patterns are used. Note: These changes were
made in v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isGuaranteedDeliveryRequired" type="xsd:boolean" default="false">
<xsd:annotation>
<xsd:documentation>Refers to the expectation that the underlying messaging service
used to implement the business transaction protocol provides guaranteed
delivery, i.e. reliable messaging.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:element name="CommercialTransaction" substitutionGroup="BusinessTransactionHead">
<xsd:annotation>
<xsd:documentation>A concrete Business Transaction Pattern where there is a formal
obligation between parties. The Commercial Transaction is actually colloquially
known as the Business Transaction (as one of the defined patterns). The Commercial Transaction can relate to the trading partners' decision to use NOF (Notification of Failure). This construct has historically and parocially known as a business transaction with the formal pattern being named Commercial Transaction. An example of a Commercial Transaction may be: Buyer requests a product or service in a specific time delivered to a pre-determined location from a Seller. Accepting the obligation, the Seller agrees and commits to delivery to complete a business transaction. The parties may have a pre-existing agreement to exchange goods and payment.Note: This
concrete pattern is added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessTransactionType">
<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" default="true"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration" default="PT2H"/>
<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration" default="PT6H"/>
<xsd:attribute name="retryCount" type="xsd:int" use="optional"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="RespondingBusinessActivity">
<xsd:complexType>
<xsd:complexContent>
<xsd:restriction base="RespondingBusinessActivityType">
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="DocumentEnvelope" maxOccurs="unbounded"/>
<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>
<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>
<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0"/>
<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration" default="PT2H"/>
<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration" default="PT6H"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="RequestConfirm" substitutionGroup="BusinessTransactionHead">
<xsd:annotation>
<xsd:documentation>A concrete Business Transaction Pattern where an initiating partner requests information about their status of a previous request or a responder's business rules. Typically no residual obligation between parties applies. An example of he RequestConfirm pattern may be: A Buyer requests from a Seller if it is still authorized to sell certain product. The Buyer expects a confirmation response. A response does not equate to an obligation, although further action could subsequently occur. A previous contract may or may not have existed between the parties. The Seller confirms he is still authorized to sell the product. Typically, the Request-Confirm involves a simple Yes/No answer from the responding party. Note: This concrete pattern is added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessTransactionType">
<xsd:sequence>
<xsd:element name="RequestingBusinessActivity">
<xsd:complexType>
<xsd:complexContent>
<xsd:restriction base="RequestingBusinessActivityType">
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="DocumentEnvelope"/>
<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>
<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>
<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>
<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration" default="PT0H"/>
<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="retryCount" type="xsd:int" use="optional"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="RespondingBusinessActivity">
<xsd:complexType>
<xsd:complexContent>
<xsd:restriction base="RespondingBusinessActivityType">
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="DocumentEnvelope" maxOccurs="unbounded"/>
<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType"/>
<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType"/>
<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>
<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration" default="PT2H"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="RequestResponse" substitutionGroup="BusinessTransactionHead">
<xsd:annotation>
<xsd:documentation>A concrete Business Transaction Pattern where there is typically no
residual obligation between the parties. The Request-Response Business Transaction
Pattern can be used when an initiating party requests information the responding
party already has. This pattern is used when a complex set of interrelated results
are required; otherwise use Query-Response. An example of the RequestResponse pattern may be: A Buyer asks a Seller in a request for the price and availability of a particular product. This request does not result in the responding party allocating product for future purchase. The Seller queries its inventory and other applications to provide a sufficient response by checking their Supply Chain Management and Inventory systems. The Seller has to calculate the current price based on availability, its Suppliers' details, etc. Most often, the Request-Response does not involve a simple Yes/No answer from the responding party. Note: This concrete pattern is added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessTransactionType">
<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" default="false"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="retryCount" type="xsd:int" use="optional"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="RespondingBusinessActivity">
<xsd:complexType>
<xsd:complexContent>
<xsd:restriction base="RespondingBusinessActivityType">
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="DocumentEnvelope" maxOccurs="unbounded"/>
<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>
<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>
<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>
<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="false"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="QueryResponse" substitutionGroup="BusinessTransactionHead">
<xsd:annotation>
<xsd:documentation>A concrete Business Transaction Pattern where the requester queries for information the responder already has. The response meets the specified constraining criteria. If a complex set of interrelated results are required, use Request-Response Business Transaction Pattern. This pattern should be used when the response meets the specified constraining criteria. If this involves a complex set of results, use request-response pattern. Use when no interdependency exists between the query results. Can use this pattern when querying business information and for specifying the structure of the response (without complex constraints). Typically no residual obligation between parties applies. An example of the QueryResponse pattern may be: A Buyer asks a Seller in a request for the price and availability of a particular product. This request does not result in the responding party allocating product for future purchase. The Seller maintains a online product catalog of products and can provide the Buyer a response without complex constraints or backend processing. Note: This concrete pattern is added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessTransactionType">
<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" default="false"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="retryCount" type="xsd:int" use="optional"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="RespondingBusinessActivity">
<xsd:complexType>
<xsd:complexContent>
<xsd:restriction base="RespondingBusinessActivityType">
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="DocumentEnvelope" maxOccurs="unbounded"/>
<xsd:element name="ReceiptAcknowledgement" type="ReceiptAcknowledgementType" minOccurs="0"/>
<xsd:element name="ReceiptAcknowledgementException" type="ReceiptAcknowledgementExceptionType" minOccurs="0"/>
<xsd:element name="AcceptanceAcknowledgement" type="AcceptanceAcknowledgementType" minOccurs="0" maxOccurs="0"/>
<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0" maxOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="false"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<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 response applies. An example of the Information Distribution pattern may be: A Seller notifies its Buyers of the relase of a new product line that become part of an product catalog. As each Buyer retains a copy of the product catalog, they may acknowledge receipt. Without non-repudiation, Information Distribution may be difficult to prove authorship and adherence.Note: This concrete pattern is added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessTransactionType">
<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"/>
<xsd:element name="AcceptanceAcknowledgementException" type="AcceptanceAcknowledgementExceptionType" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" use="optional"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration" default="PT24H"/>
<xsd:attribute name="timeToAcknowledgeAcceptance" use="prohibited"/>
<xsd:attribute name="retryCount" type="xsd:int" use="optional"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<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 affects the previous completion of a
Commercial Transaction. The Notification pattern (i.e. the Notification of Failure) can apply to timeout on responding party's document or an issue with the received responding party's document (signature missing or invalid, erroneous, not authorized - maps back to TPA). It is recommended this be sent over an alternate communication channel. How and when the NOF is used is TPA specific. Provides further flexibility given decisions between the parties. An example of a Notification (NOF) pattern use may be: A requesting role that throws a business protocol exception terminates the transaction and then sends a notification revoking the offending business document request. The requesting role cannot send a business signal to the responding role to terminate the transaction. A responding role that throws a business protocol exception signals the exception back to the requesting role and then terminates the business transaction. Note: This concrete pattern is added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessTransactionType">
<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:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="DataExchange" substitutionGroup="BusinessTransactionHead">
<xsd:annotation>
<xsd:documentation>The new element is open and allows definition of other patterns
unspecified in the concrete set of Business Transaction patterns. Note, in v2.0, the
new DataExchange element is not constrained to support state alignment. The
semantics related to DataExchange are partner-specific and therefore left unspecified.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessTransactionType">
<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: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" default="false"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="false"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="false"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="BusinessTransaction" substitutionGroup="BusinessTransactionHead">
<xsd:annotation>
<xsd:documentation>Note: In v2.0, Business Transaction is being retained for
conversions. The Business Transaction element is being replaced by the Business
Transaction Head abstract superclass and the concrete set of Business Transaction
Patterns. Note: The Business Transaction will be deprecated in a future version.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="BusinessTransactionType">
<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" default="true"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration" default="PT6H"/>
<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration" default="PT2H"/>
<xsd:attribute name="retryCount" type="xsd:int" use="optional"/>
</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" default="true"/>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean" default="true"/>
<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration" default="PT2H"/>
<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration" default="PT6H"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!--NotificationOfFailure,ReceiptOfResponseAcknowledgement,General Exception-->
<xsd:element name="Signal" type="SignalType">
<xsd:annotation>
<xsd:documentation>As a Business Action, this element defines the identification
structure for business signal messages to be sent to a trading partner Note, this
element was explicitly added in v2.0 for signals to mirror structure of the Business
Document specification. This Business Action is non-substantive. A signal is used
for state alignment.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="SignalEnvelopeType">
<xsd:annotation>
<xsd:documentation>The type of a Signal Envelope definition that conveys Business Action
information. Note, this type was added in v2.0 for signals to mirror the Document
Envelope structure (where applicable). A signal is used for state alignment.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="signalDefinitionRef" type="xsd:IDREF" use="required">
<xsd:annotation>
<xsd:documentation>The nameID reference of the signal definition for the Business Signal.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:complexType name="SignalType">
<xsd:annotation>
<xsd:documentation>The type of a Signal element. Note, this type was added in v2.0. A
signal is used for state alignment. This construct allows specification references
(such as those used for context), and a Signal Type may have 0..n Condition Expression.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="ConditionExpression" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Specification" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
</xsd:complexType>
<xsd:complexType name="ReceiptAcknowledgementType">
<xsd:annotation>
<xsd:documentation>The type of Business Action signal of positive Receipt
Acknowledgement. Note, this type was added in v2.0. A signal is used for state alignment.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="SignalEnvelopeType">
<xsd:attribute name="isPositiveReceipt" type="xsd:boolean" fixed="true">
<xsd:annotation>
<xsd:documentation>Specifies whether positive receipt of a Business Signal
is required (i.e. the business signal is not an exception).</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ReceiptAcknowledgementExceptionType">
<xsd:annotation>
<xsd:documentation>The type of a BusinessAction signal of exception Receipt
Acknowledgement. Note, this type was added in v2.0. A signal is used for state alignment.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="SignalEnvelopeType">
<xsd:attribute name="isPositiveSignal" fixed="false"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="AcceptanceAcknowledgementType">
<xsd:annotation>
<xsd:documentation>The type of Business Action signal of positive Acceptance
Acknowledgement. Note, this type was added in v2.0. A signal is used for state alignment.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="SignalEnvelopeType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="AcceptanceAcknowledgementExceptionType">
<xsd:annotation>
<xsd:documentation>The type of a BusinessAction signal of exception Acceptance
Acknowledgement. Note, this type was added in v2.0. A signal is used for state alignment.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="SignalEnvelopeType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="GeneralExceptionType">
<xsd:annotation>
<xsd:documentation>The type of a Business Action of general exception (exceptions other
than Receipt and Acceptance Acknowledgement). Note, this type was added in v2.0.
During an interaction, the general exception can be used when a party must trigger
an exception, for example, for a general communication failure. A signal is used for
state alignment.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="SignalEnvelopeType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="TimeToPerform">
<xsd:annotation>
<xsd:documentation>The expected time available to successfully complete a specified
activity such as a substantive response to a request. Note, in v2.0, this element
was added (previously was an attribute on specific elements). Also, in v2.0, the TTP
can be variable, i.e. it can be specified at different points during the process lifecycle.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Variable" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="duration" type="xsd:duration" use="optional">
<xsd:annotation>
<xsd:documentation>The duration of the maximum amount of time between the time
at which the request is sent and the substantive response is received.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="type" type="TimeToPerformType" use="optional" default="design"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="Variable">
<xsd:annotation>
<xsd:documentation>A semantic element that supports the effective use of conditional constraints. The variable can be accessed by external elements.
businessTransactionActivityRef and businessDocumentRef point to what context and documents are relevant to Condition Expression evaluation. Variable assumes type, if any, from expression evaluation. This element, for example, could be associated with a logical Business Document. The Condition Expression also relates to the DocumentEnvelopeNotation. For conformance, a BSI is required to support at least the XPath language, as well as the DocumentEnvelopeNotation [change] (nameID of a Document Envelope), while use of XSLT is
also recommended. Use of XPath and XSLT may be beneficial when variables are used. Note: This element was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Exactly one ConditionExpression is used to provide values. If
multiple ConditionExpressions are listed, each expressionLanguage value must
be different from others in the sequence.</xsd:documentation>
</xsd:annotation>
<xsd:element ref="ConditionExpression" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="businessTransactionActivityRef" type="xsd:IDREF" use="optional">
<xsd:annotation>
<xsd:documentation>The nameID reference of the Business Transaction Activity
associated with the semantic variable.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="businessDocumentRef" type="xsd:IDREF" use="optional">
<xsd:annotation>
<xsd:documentation>The nameID reference of the logical business document
associated with the semantic variable.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<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. Must specify input, output,
fault, interface, operation, role, BTA and document envelope or signal reference.
Note: This element was added in v2.0.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="OperationMappingType">
<xsd:annotation>
<xsd:documentation>The type related to the abstract element mapping Operations to
Business Actions, either business messages or signals. Note: This complexType was
added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="MessageMap" maxOccurs="unbounded">
<xsd:complexType>
<xsd:attributeGroup ref="map"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="SignalMap" minOccurs="0" maxOccurs="8">
<xsd:complexType>
<xsd:attributeGroup ref="map"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attributeGroup ref="name"/>
<xsd:attribute name="roleRef" type="xsd:IDREF" use="required"/>
<xsd:attribute name="businessTransactionActivityRef" type="xsd:IDREF" use="required"/>
</xsd:complexType>
<xsd:simpleType name="TimeToPerformType">
<xsd:annotation>
<xsd:documentation>The simpleType related to the definition of Time To Perform during
the process lifecycle. Note, this simpleType was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="design"/>
<xsd:enumeration value="configuration"/>
<xsd:enumeration value="runtime"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="BusinessDocumentValueList">
<xsd:annotation>
<xsd:documentation>The simpleType related to the (future) enumerated list for the
business document list associated with the Status Visibility element. This
simpleType is used in exposing visibility to documents from more deeply nested BTA.
Thoses values are to be available as the expression language listed. Note: This
simpleType was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:list itemType="xsd:NMTOKEN"/>
</xsd:simpleType>
<xsd:simpleType name="ConditionGuardValueList">
<xsd:annotation>
<xsd:documentation>The simpleType related to the content model for Status Visibility.
Note: This simpleType was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:list itemType="ConditionGuardValue"/>
</xsd:simpleType>
<xsd:simpleType name="ConditionGuardValue">
<xsd:annotation>
<xsd:documentation>The simpleType related to the enumerated list for the guard values
associated with the FromLink in a Completion State. Each of the FromLinks in a
Completion State can be specified to transition as a result of the
ConditionGuardValues. This check is made everytime a transition occurs from the real
states. Because the FromLinks generally are from a specific state, only when that
state has been reached is the check of conditionGuards from that state checked.
Note, this simpleType was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="ProtocolSuccess"/>
<xsd:enumeration value="AnyProtocolFailure"/>
<xsd:enumeration value="RequestReceiptFailure"/>
<xsd:enumeration value="RequestAcceptanceFailure"/>
<xsd:enumeration value="ResponseReceiptFailure"/>
<xsd:enumeration value="ResponseAcceptanceFailure"/>
<xsd:enumeration value="SignalTimeout"/>
<xsd:enumeration value="ResponseTimeout"/>
<xsd:enumeration value="BusinessSuccess"/>
<xsd:enumeration value="BusinessFailure"/>
<xsd:enumeration value="Success"/>
<xsd:enumeration value="Failure"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="DocumentSpecificationType">
<xsd:annotation>
<xsd:documentation>The simpleType related to the enumerated list of specification types
for the Specification element. Note: This simpleType was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="schema"/>
<xsd:enumeration value="dtd"/>
<xsd:enumeration value="wsdl"/>
<xsd:enumeration value="relaxng"/>
<xsd:enumeration value="other"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StepType">
<xsd:annotation>
<xsd:documentation>The simpleType related to the enumerated list of operation types
supported by OperationMapping and OperationMappingType. Note: This simpleType was
added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="input"/>
<xsd:enumeration value="output"/>
<xsd:enumeration value="fault"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="ExpressionLanguageType">
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="DocumentEnvelope"/>
<xsd:enumeration value="XPath1"/>
<xsd:enumeration value="XSLT1"/>
<xsd:enumeration value="CAM1"/>
<xsd:enumeration value="XPath2"/>
<xsd:enumeration value="XSLT2"/>
<xsd:enumeration value="XQuery1"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:attributeGroup name="documentSecurity">
<xsd:annotation>
<xsd:documentation>The attributeGroup related to document security, quality of service
attributes. </xsd:documentation>
</xsd:annotation>
<xsd:attribute name="isAuthenticated">
<xsd:annotation>
<xsd:documentation>The communications channel used to transport the Message provides
transient authentication. The specific method will be determined by the
communications protocol used. Persistent authentication means the Business
Document signer’s identity SHALL be verified at the receiving application level.
Authentication assists in verification of role identity of a participating party.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="none"/>
<xsd:enumeration value="transient"/>
<xsd:enumeration value="persistent"/>
<xsd:enumeration value="transient-and-persistent"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="isConfidential">
<xsd:annotation>
<xsd:documentation>Transient confidentiality is provided by a secure network
protocol, such as SSL as the document is transferred between two adjacent ebXML
Messaging Service (MSH) or other transport messaging nodes. Persistent
confidentiality is intended to preserve the confidentiality of the message such
that only the intended party (application) can see it.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="none"/>
<xsd:enumeration value="transient"/>
<xsd:enumeration value="persistent"/>
<xsd:enumeration value="transient-and-persistent"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="isTamperDetectable">
<xsd:annotation>
<xsd:documentation>Transient isTamperDetectableis the ability to detect if the
information has been tampered with during transfer between two adjacent MSH
nodes. Persistent isTamperDetectable is the ability to detect if the information
has been tampered with after it has been received by messaging node, between the
messaging node and the application. Tamper detection assists in verification of
content integrity between and within a participating party.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="none"/>
<xsd:enumeration value="transient"/>
<xsd:enumeration value="persistent"/>
<xsd:enumeration value="transient-and-persistent"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:attributeGroup>
<xsd:attributeGroup name="map">
<xsd:annotation>
<xsd:documentation>The attributeGroup related to interface/operation types supported by
OperationMapping and OperationMappingType. The map includes the interface
(portType), operation, the step (see StepType) and the document reference. Note,
this attributeGroup was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="interfaceName" type="xsd:NMTOKEN" use="required">
<xsd:annotation>
<xsd:documentation>Interface is called portType in WSDL 1.1. The name of the
interface or portType mapped logically in Operation Mapping.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="operationName" type="xsd:NMTOKEN" use="required">
<xsd:annotation>
<xsd:documentation>The name of the operation mapped in the OperationMapping.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="operationStep" type="StepType" use="required">
<xsd:annotation>
<xsd:documentation>The name of operation step from the Step Type enumeration list
for OperationMapping.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="documentEnvelopeRef" type="xsd:IDREF" use="required">
<xsd:annotation>
<xsd:documentation>The nameID reference of the Document Envelope related to the OperationMapping.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:attributeGroup>
<xsd:attributeGroup name="name">
<xsd:annotation>
<xsd:documentation>The attributeGroup related to the identification information for most
elements. For the name attribute, no white space restrictions are enforced. White
space is not controlled but left to implementation to trigger faults or exceptions.
Note: In v2.0, this group was enhanced to include not only name but nameID.</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="name" type="xsd:string" use="required"/>
<xsd:attribute name="nameID" type="xsd:ID" use="required"/>
</xsd:attributeGroup>
<xsd:attributeGroup name="quality">
<xsd:annotation>
<xsd:documentation>The attributeGroup related to quality of service attributes. Note:
This attributeGroup was added in v2.0.</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="isAuthorizationRequired" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>A party MAY specify isAuthorizationRequired on a requesting
and/or a responding activity accordingly, with the result that [the activity]
will only be processed as valid if the party interpreting it successfully
matches the stated identity of the activity's [Role] to a list of allowed values
previously supplied by that party. Authorization typically relates to a signed
business document and the association to the role identity of the party expected
for that activity.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isIntelligibleCheckRequired" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Allows partners to agree that a message should be 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 message's business documents or document envelope. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isNonRepudiationRequired" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>If non-repudiation of origin and content is required then the
business activity MUST store the business document in its original form for the
duration mutually agreed to in a trading partner agreement. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isNonRepudiationReceiptRequired" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>Both partners agree to mutually verify receipt of a requesting
business document and that the receipt MUST be non-repudiable. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="timeToAcknowledgeReceipt" type="xsd:duration">
<xsd:annotation>
<xsd:documentation>The time a responding or requesting role has to acknowledge
receipt of a business document. </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="timeToAcknowledgeAcceptance" type="xsd:duration">
<xsd:annotation>
<xsd:documentation>The time a responding or requesting role has to non-substantively
acknowledge business acceptance of a business document.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="retryCount" type="xsd:int">
<xsd:annotation>
<xsd:documentation>The business retry for a RequestingBusinessActivity identifies
the number of retries allowed in addition to the initial request while the time
to perform has not been exceeded.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:attributeGroup>
</xsd:schema>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]