ConditionExpressionType 

The type related to the ConditionExpression element. 
A BSI supports at least the XPath language, as well as the DocumentEnvelope
(expressionLanguage of ExpressionLanguageType) which is the nameID of a Document
Envelope. In previous versions, this was known as DocumentEnvelopeNotation. When
variables are used, XPath and XSLT could be beneficial. Note: This complexType was
added in v2.0.

Complex Type Information

Model

Documentation*
Children: Documentation

Attributes

QName Type Fixed Default Use Inheritable Annotation
defaultValue xsd:string optional 
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.
expression xsd:string required 
Defines the value for the Condition
Expression.
expressionLanguage ExpressionLanguageType required 
Defines the language used for the Condition
Expression.

Used By

Elements BinaryCollaborationType/BeginsWhen, BinaryCollaborationType/EndsWhen, BinaryCollaborationType/PostCondition, BinaryCollaborationType/PreCondition, BusinessCollaborationType/BeginsWhen, BusinessCollaborationType/EndsWhen, BusinessCollaborationType/PostCondition, BusinessCollaborationType/PreCondition, BusinessTransactionActivityType/BeginsWhen, BusinessTransactionActivityType/EndsWhen, BusinessTransactionActivityType/PostCondition, BusinessTransactionActivityType/PreCondition, ConditionExpression, MultiPartyCollaborationType/BeginsWhen, MultiPartyCollaborationType/EndsWhen, MultiPartyCollaborationType/PostCondition, MultiPartyCollaborationType/PreCondition

Source 

<xsd:complexType name="ConditionExpressionType">
  <xsd:annotation>
    <xsd:documentation>The type related to the ConditionExpression element. A BSI supports at least the XPath language, as well as the DocumentEnvelope (expressionLanguage of ExpressionLanguageType) which is the nameID of a Document Envelope. In previous versions, this was known as DocumentEnvelopeNotation. When variables are used, XPath and XSLT could be beneficial. Note: This complexType was added in v2.0.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element ref="Documentation" minOccurs="0" maxOccurs="unbounded"/>
  </xsd:sequence>
  <xsd:attribute name="expressionLanguage" type="ExpressionLanguageType" use="required">
    <xsd:annotation>
      <xsd:documentation>Defines the language used for the Condition Expression.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="expression" type="xsd:string" use="required">
    <xsd:annotation>
      <xsd:documentation>Defines the value for the Condition Expression.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="defaultValue" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation>Allows a default value to be specified for the Condition Expression. This default value is expressed as an xsd:string. To acquire an xsd:boolean, an XSLT constant boolean function of TRUE or FALSE may be used.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
</xsd:complexType>