Variable 

A semantic element that supports the effective use of conditional
	constraints. The variable can be accessed by external elements. The
	businessTransactionActivityRef and businessDocumentRef point to what context and
	documents are relevant to Condition Expression evaluation. Variable assumes type, if
	any, from expression evaluation. This element, for example, could be associated with
	a logical Business Document. Given whether simple or complex variables are used,
	XPath or XSLT could be used, for example. Note: This complexType was added in
v2.0.

Element Information

Model

ConditionExpression+
Children: ConditionExpression

Attributes

QName Type Fixed Default Use Inheritable Annotation
businessDocumentRef xsd:IDREF optional 
The nameID reference of the logical business document
associated with the semantic variable. Note: This attribute was added in v2.0.
businessTransactionActivityRef xsd:IDREF optional 
The nameID reference of the Business Transaction Activity
associated with the semantic variable. Note: This attribute was added in v2.0.
name xsd:string required 
A designation that may be relevant to a business analyst but is
not intended for referencing.
nameID xsd:ID required 
Used for referencing, for example, for identification of elements
within an ebBP instance.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://docs.oasis-open.org/ebxmlbp/ebbp-2.0'

Used By

Complex Types PackageType, ProcessSpecificationType
Elements Package, ProcessSpecification, TimeToPerform

Source 

<xsd:element name="Variable">
  <xsd:annotation>
    <xsd:documentation>A semantic element that supports the effective use of conditional constraints. The variable can be accessed by external elements. The businessTransactionActivityRef and businessDocumentRef point to what context and documents are relevant to Condition Expression evaluation. Variable assumes type, if any, from expression evaluation. This element, for example, could be associated with a logical Business Document. Given whether simple or complex variables are used, XPath or XSLT could be used, for example. Note: This complexType was added in v2.0.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:annotation>
        <xsd:documentation>Exactly one ConditionExpression is used to provide values. If multiple ConditionExpressions are listed, each expressionLanguage value is different from others in the sequence and distinct.</xsd:documentation>
      </xsd:annotation>
      <xsd:element ref="ConditionExpression" maxOccurs="unbounded"/>
    </xsd:sequence>
    <xsd:attributeGroup ref="name"/>
    <xsd:attribute name="businessTransactionActivityRef" type="xsd:IDREF" use="optional">
      <xsd:annotation>
        <xsd:documentation>The nameID reference of the Business Transaction Activity associated with the semantic variable. Note: This attribute was added in v2.0.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="businessDocumentRef" type="xsd:IDREF" use="optional">
      <xsd:annotation>
        <xsd:documentation>The nameID reference of the logical business document associated with the semantic variable. Note: This attribute was added in v2.0.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>

Sample