<xs:documentation>The name for this timer. Every timer should have a unique name.  If a name is not specified then the name of the enclosing node is taken.</xs:documentation>
							</xs:annotation>
						</xs:attribute>
						<xs:attribute name="duedate" type="duedateType" use="required">
							<xs:annotation>
								<xs:documentation>The duration that specifies the time period between the creation of the timer and the execution of the timer.  This can be expressed in business hours, minutes, etc.  See the documentation for syntax for this attribute.</xs:documentation>
							</xs:annotation>
						</xs:attribute>
						<xs:attribute name="repeat" type="repeatType" use="optional">
							<xs:annotation>
								<xs:documentation>yes, true, or duration.  After a timer has been executed on the duedate, this repeat attribute specifies the duration between repeating timer executions until the node is left.  If yes or true are specified then the value of duedate is used.</xs:documentation>
							</xs:annotation>
						</xs:attribute>
						<xs:attribute name="transition" type="xs:string" use="optional">
							<xs:annotation>
								<xs:documentation>A transition name to be taken after the timer executes, the timer event is fired and execution of any specified actions has completed.</xs:documentation>
							</xs:annotation>
						</xs:attribute>
						<xs:attribute name="cancel-event" type="xs:string" use="optional" default="task-end">
							<xs:annotation>
								<xs:documentation>task-assign, task-start, task-end, or any combination of these specified as a comma separated list.</xs:documentation>
							</xs:annotation>
						</xs:attribute>
					</xs:complexType>
				</xs:element>
				<xs:element ref="exception-handler" minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			<xs:attribute name="name" type="xs:string" use="optional">
				<xs:annotation>
					<xs:documentation>Named tasks can be referenced and looked up via the TaskMgmtDefinition.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
			<xs:attribute name="blocking"   type="booleanType" use="optional" default="false"/>
			<xs:attribute name="signalling" type="booleanType" use="optional" default="true"/>
			<xs:attribute name="description" type="xs:string" use="optional"/>
			<xs:attribute name="duedate" type="duedateType" use="optional">
				<xs:annotation>
					<xs:documentation>The duration that specifies the time period between the creation of the timer and the execution of the timer.  This can be expressed in business hours, minutes, etc.  See the documentation for syntax for this attribute.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
			<xs:attribute name="swimlane" type="xs:string" use="optional"/>
			<xs:attribute name="priority" use="optional" default="normal">
				<xs:annotation>
					<xs:documentation>This value can also be any integer where the lower the number the higher the priority.</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:union>
						<xs:simpleType>
							<xs:restriction base="xs:string">
								<xs:enumeration value="highest"/>
								<xs:enumeration value="high"/>
								<xs:enumeration value="normal"/>
								<xs:enumeration value="low"/>
								<xs:enumeration value="lowest"/>
							</xs:restriction>
						</xs:simpleType>
						<xs:simpleType>
							<xs:restriction base="xs:int"/>
						</xs:simpleType>
					</xs:union>
				</xs:simpleType>
			</xs:attribute>
		</xs:complexType>
	</xs:element>
	<xs:element name="task-node">
		<xs:annotation>
			<xs:documentation>A node which accepts a list of tasks to be executed.</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element ref="task" minOccurs="0" maxOccurs="unbounded"/>
				<xs:element ref="transition" minOccurs="0" maxOccurs="unbounded"/>
				<xs:element ref="event" minOccurs="0" maxOccurs="unbounded"/>
				<xs:element ref="timer" minOccurs="0" maxOccurs="unbounded"/>
				<xs:element ref="exception-handler" minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			<xs:attribute name="name" type="xs:string" use="required"/>
			<xs:attribute name="signal" use="optional" default="last">
				<xs:annotation>
					<xs:documentation>Signal specifies the effect of task completion on the process execution continuation.</xs:documentation>
				</xs:annotation>
				<xs:simpleType>
					<xs:restriction base="xs:string">
						<xs:enumeration value="unsynchronized"/>
						<xs:enumeration value="never"/>
						<xs:enumeration value="first"/>
						<xs:enumeration value="first-wait"/>
						<xs:enumeration value="last"/>
						<xs:enumeration value="last-wait"/>
					</xs:restriction>
				</xs:simpleType>
			</xs:attribute>
			<xs:attribute name="create-tasks" type="booleanType" use="optional" default="true">
				<xs:annotation>
					<xs:documentation>Can be set to false when a runtime calculation has to determine which of the tasks have to be created.  In that case, add an action on node-enter, create the tasks in the action, and set create-tasks to false.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
			<xs:attribute name="end-tasks" type="booleanType" use="optional" default="false">
				<xs:annotation>
					<xs:documentation>Can be set to true, in which all the tasks that are still open are ended on the node-leave event.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
		</xs:complexType>
	</xs:element>
	<xs:element name="timer">
		<xs:annotation>
			<xs:documentation>Specifies a timer that monitors the duration of an execution in this node.</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:choice>
				<xs:element ref="action"/>
				<xs:element ref="script"/>
			</xs:choice>
			<xs:attribute name="name" type="xs:string" use="optional">
				<xs:annotation>
					<xs:documentation>The name for this timer. Every timer should have a unique name.  If a name is not specified then the name of the enclosing node is taken.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
			<xs:attribute name="duedate" type="duedateType" use="required">
				<xs:annotation>
					<xs:documentation>The duration that specifies the time period between the creation of the timer and the execution of the timer.  This can be expressed in business hours, minutes, etc.  See the documentation for syntax for this attribute.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
			<xs:attribute name="repeat" type="repeatType" use="optional">
				<xs:annotation>
					<xs:documentation>yes, true, or duration.  After a timer has been executed on the duedate, this repeat attribute specifies the duration between repeating timer executions until the node is left.  If yes or true are specified then the value of duedate is used.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
			<xs:attribute name="transition" type="xs:string" use="optional">
				<xs:annotation>
					<xs:documentation>A transition name to be taken after the timer executes, the timer event is fired and execution of any specified actions has completed.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
		</xs:complexType>
	</xs:element>
	<xs:element name="transition">
		<xs:annotation>
			<xs:documentation>The leaving transitions.  Each transition leaving a node must have a distinct name.  At most one transition can have no name.  The first transition specified is the default transition:  the path taken when the node is left without specifying a transition.</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:choice minOccurs="0" maxOccurs="unbounded">
					<xs:element ref="action"/>
					<xs:element ref="script"/>
					<xs:element ref="create-timer"/>
					<xs:element ref="cancel-timer"/>
				</xs:choice>
				<xs:element ref="exception-handler" minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			<xs:attribute name="name" type="xs:string" use="optional">
				<xs:annotation>
					<xs:documentation>The name of the transition.  Note that each transition leaving a node must have a distinct name.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
			<xs:attribute name="to" type="xs:string" use="required">
				<xs:annotation>
					<xs:documentation>The hierarchical name of the destination node.  See documentation for an description of hierarchical names.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
		</xs:complexType>
	</xs:element>
	<xs:element name="variable">
		<xs:annotation>
			<xs:documentation>Input and Output variables for the node.  Input variables are specified by access "read". If you have assigned variables during the script evaluation, the variables with "write" access allows you to store the values in the process instance.  It does not matter whether the variables existed prior to this action.</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded">
					<xs:annotation>
						<xs:documentation>User defined metadata.</xs:documentation>
					</xs:annotation>
				</xs:any>
			</xs:sequence>
			<xs:attribute name="name" type="xs:string" use="required"/>
			<xs:attribute name="access" type="accessType" use="optional" default="read,write"/>
			<xs:attribute name="mapped-name" type="xs:string" use="optional">
				<xs:annotation>
					<xs:documentation>Defaults to the process variable name as given by the name attribute.</xs:documentation>
				</xs:annotation>
			</xs:attribute>
		</xs:complexType>
	</xs:element>
	<xs:complexType name="process-definition-v3.0">
		<xs:annotation>
			<xs:documentation>Version 3.0 of the PDL schema</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="swimlane" minOccurs="0" maxOccurs="unbounded"/>
			<xs:element name="start-state" minOccurs="0">
				<xs:annotation>
					<xs:documentation>The start state of the process.  Note that a process without a start-state is valid, but cannot be executed.</xs:documentation>
				</xs:annotation>
				<xs:complexType>
					<xs:sequence>
						<xs:element ref="task" minOccurs="0"/>
						<xs:element ref="transition" minOccurs="0" maxOccurs="unbounded"/>
						<xs:element name="event" minOccurs="0" maxOccurs="unbounded">
							<xs:complexType>
								<xs:choice minOccurs="0" maxOccurs="unbounded">
									<xs:element ref="action"/>
									<xs:element ref="script"/>
									<xs:element ref="create-timer"/>
									<xs:element ref="cancel-timer"/>
								</xs:choice>
								<xs:attribute name="type" use="required">
									<xs:simpleType>
										<xs:restriction base="xs:string">
											<xs:enumeration value="node-leave"/>
											<xs:enumeration value="after-signal"/>
										</xs:restriction>
									</xs:simpleType>
								</xs:attribute>
							</xs:complexType>
						</xs:element>
						<xs:element ref="exception-handler" minOccurs="0" maxOccurs="unbounded"/>
					</xs:sequence>
					<xs:attribute name="name" type="xs:string" use="optional"/>
					<xs:attribute name="swimlane" type="xs:string" use="optional"/>
				</xs:complexType>
			</xs:element>
			<xs:choice minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>The nodes of the process definition.  Note that a process without nodes is valid, but cannot be executed.</xs:documentation>
				</xs:annotation>
				<xs:element ref="state"/>
				<xs:element ref="task-node"/>
				<xs:element ref="super-state"/>
				<xs:element ref="process-state"/>
				<xs:element ref="node"/>
				<xs:element ref="fork"/>
				<xs:element ref="join"/>
				<xs:element ref="decision"/>
				<xs:element ref="end-state"/>
			</xs:choice>
			<xs:choice minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Globally defined actions that can be referenced from events and transitions.  </xs:documentation>
				</xs:annotation>
				<xs:element ref="action"/>
				<xs:element ref="script"/>
				<xs:element ref="create-timer"/>
				<xs:element ref="cancel-timer"/>
			</xs:choice>
			<xs:element ref="task" minOccurs="0" maxOccurs="unbounded"/>
			<xs:element name="event" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Supports all event types.  Uniquely supports process-start and process-end.</xs:documentation>
				</xs:annotation>
				<xs:complexType>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="action"/>
						<xs:element ref="script"/>
						<xs:element ref="create-timer"/>
						<xs:element ref="cancel-timer"/>
					</xs:choice>
					<xs:attribute name="type" use="required">
						<xs:simpleType>
							<xs:restriction base="xs:string">
								<xs:enumeration value="node-enter"/>
								<xs:enumeration value="node-leave"/>
								<xs:enumeration value="before-signal"/>
								<xs:enumeration value="after-signal"/>
								<xs:enumeration value="superstate-enter"/>
								<xs:enumeration value="superstate-leave"/>
								<xs:enumeration value="task-create"/>
								<xs:enumeration value="task-assign"/>
								<xs:enumeration value="task-start"/>
								<xs:enumeration value="task-end"/>
								<xs:enumeration value="transition"/>
								<xs:enumeration value="timer"/>
								<xs:enumeration value="subprocess-created"/>
								<xs:enumeration value="subprocess-end"/>
								<xs:enumeration value="process-start"/>
								<xs:enumeration value="process-end"/>
							</xs:restriction>
						</xs:simpleType>
					</xs:attribute>
				</xs:complexType>
			</xs:element>
			<xs:element ref="exception-handler" minOccurs="0" maxOccurs="unbounded"/>
		</xs:sequence>
		<xs:attribute name="name" type="xs:string" use="optional">
			<xs:annotation>
				<xs:documentation>the name of the process</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
</xs:schema>