<?xml version="1.0" encoding="UTF-8"?>

<!--
FILE INFORMATION

Description
   This XML file contains a WS-BPEL 2.0 abstract process for a PAL Rule
   defined as part of the PDE enabler.

Version: 1.0  
Date:    31 August 2010

OMA Permanent Document
   File: OMA-SUP-XML_pde_prIsAvailable-V1_0-20100831-C
   Type: text/xml

Public Reachable Information
   Path: http://www.openmobilealliance.org/tech/profiles/rules
   Name: pde_prIsAvailable-v1_0.xml

NORMATIVE INFORMATION

Information about this file can be found in the latest revision of the specification
OMA-DDS-PAL_Data_Ext-V1_0 available at
   http://www.openmobilealliance.org/

Send comments to technical-comments@mail.openmobilealliance.org
	
LEGAL DISCLAIMER

Use of this document is subject to all of the terms and conditions
of the Use Agreement located at
http://www.openmobilealliance.org/UseAgreement.html

You may use this document or any part of the document for internal
or educational purposes only, provided you do not modify, edit or
take out of context the information in this document in any manner.
Information contained in this document may be used, at your sole
risk, for any purposes.

You may not use this document in any other manner without the prior
written permission of the Open Mobile Alliance.  The Open Mobile
Alliance authorizes you to copy this document, provided that you
retain all copyright and other proprietary notices contained in the
original materials on any copies of the materials and that you
comply strictly with these terms.  This copyright permission does
not constitute an endorsement of the products or services.  The
Open Mobile Alliance assumes no responsibility for errors or
omissions in this document.

Each Open Mobile Alliance member has agreed to use reasonable
endeavors to inform the Open Mobile Alliance in a timely manner of
Essential IPR as it becomes aware that the Essential IPR is related
to the prepared or published specification.  However, the members
do not have an obligation to conduct IPR searches.  The declared
Essential IPR is publicly available to members and non-members of
the Open Mobile Alliance and may be found on the "OMA IPR
Declarations" list at http://www.openmobilealliance.org/ipr.html.
The Open Mobile Alliance has not conducted an independent IPR review
of this document and the information contained herein, and makes no
representations or warranties regarding third party IPR, including
without limitation patents, copyrights or trade secret rights.  This
document may contain inventions for which you must obtain licenses
from third parties before making, using or selling the inventions.
Defined terms above are set forth in the schedule to the Open Mobile
Alliance Application Form.

NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE
MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER
OR ITS AFFILIATES REGARDING ANY OF THE IPR'S REPRESENTED ON THE "OMA
IPR DECLARATIONS" LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY,
COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR     
NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL.

THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY
DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR
EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF
DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS.

Copyright 2010 Open Mobile Alliance Ltd.  All Rights Reserved.
Used with the permission of the Open Mobile Alliance Ltd. under the
terms set forth above.
-->

<bpel:process name="isAvailable"
         suppressJoinFailure="yes"
         targetNamespace="oma:prs:pal:rules"
         xmlns:tns="oma:prs:pal:rules"
         xmlns:pdf="urn:ietf:params:xml:ns:pidf"
         xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
         xmlns:prs="urn:oma:xml:prs:pidf:oma-pres"
         xmlns:bpt="urn:oma:xml:prs:pal:base-policy-type:1.0"
         xmlns:mpa="urn:oma:xml:prs:pal:payloads:1.0"
         xmlns:pal="urn:oma:xml:prs:pal:types:1.0"
         xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/abstract"
		 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
         abstractProcessProfile="http://docs.oasis-open.org/wsbpel/2.0/process/abstract/simple-template/2006/08"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
         xsi:schemaLocation="http://docs.oasis-open.org/wsbpel/2.0/process/abstract http://docs.oasis-open.org/wsbpel/2.0/CS01/process/abstract/ws-bpel_abstract_common_base.xsd">
       
    <!-- ================================================================= -->         
    <!-- PARTNERLINKS                                                      -->
    <!-- List of services participating in this BPEL process               -->
    <!-- ================================================================= -->         
    <bpel:partnerLinks>
        <bpel:partnerLink name="client" partnerLinkType="##opaque"/>
    </bpel:partnerLinks>
  
    <!-- ================================================================= -->         
    <!-- VARIABLES                                                         -->
    <!-- List of messages and XML documents used within this BPEL process  -->
    <!-- ================================================================= -->         
    <bpel:variables>
        <bpel:variable name="person"      type="pdf:tuple"/>
        <bpel:variable name="service"     type="pdf:tuple"/>
        <bpel:variable name="svcTmp"      type="pdf:tuple"/>
        <bpel:variable name="availEval"   type="pal:receiveAvailMessage"/>
        <bpel:variable name="theResult"   type="xsd:boolean"/>
        <bpel:variable name="boolTmp"     type="xsd:boolean"/>
        <bpel:variable name="acTmp"       element="rpid:activities"/>       
        <bpel:variable name="acPol"       element="rpid:activities"/>
        <bpel:variable name="tmpB"        element="bpt:UndefBarringStateType"/>
        <bpel:variable name="tmpR"        element="bpt:UndefRegistrationStateType"/>       
    </bpel:variables>

    <!-- ================================================================= -->         
    <!-- ORCHESTRATION LOGIC                                               -->
    <!-- Set of activities coordinating the flow of messages across the    -->
    <!-- services integrated within this business process                  -->
    <!-- ================================================================= -->         
    <bpel:sequence>
        <bpel:receive name="receiveInput" partnerLink="client" 
                operation="AvailRequest" variable="availEval"/>

          <bpel:assign validate="no">
              <bpel:documentation>
                  Establish the following local variables:
                     - PAL Policy 'unavailable-activities-set' from 'availEval'
                     - boolean variables $boolTmp and $theResult initialized to 'false'.
              </bpel:documentation>

              <bpel:copy>
                  <bpel:from>
                       bpel:getVariableProperty("availEval" "pc:unavailable-activities-set")
                  </bpel:from> 
                  <bpel:to>$acPol</bpel:to> 
              </bpel:copy>

              <bpel:copy>
                  <bpel:from>boolean(0)</bpel:from>
                  <bpel:to>$boolTmp</bpel:to> 
              </bpel:copy>
              <bpel:copy>
                  <bpel:from>boolean(0)</bpel:from> 
                  <bpel:to>$theResult</bpel:to>
              </bpel:copy>
          </bpel:assign>

	      <bpel:opaqueActivity name="determineApplicablePersonTuple">
                <bpel:documentation>
                    Determine applicable person PIDF tuple from 'availEval' and 
                    assign to $person as detailed in [PDE_Spec], 
                    section "Default Watcher Processing".
                </bpel:documentation>
          </bpel:opaqueActivity>

          <bpel:invoke name="validate" partnerLink="ValidationService" 
              operation="validatePersonsActivities" inputVariable="person" 
                outputVariable="acTmp">
                <bpel:documentation>
                    Validate Person tuple contained in $person, and establish all activities 
                    (i.e. exclusive of sub-elements '&lt;note&gt;' 
                    and '&lt;unknown&gt;') into variable $acTmp.
                </bpel:documentation>
          </bpel:invoke>

          <bpel:if xmlns:bpel2="http://docs.oasis-open.org/wsbpel/2.0/process/executable">
              <bpel:condition>
                  <![CDATA[count($acTmp) > 0 and count($acPol) > 0]]>
              </bpel:condition>
              <bpel:flow>
 
                  <bpel:opaqueActivity name="matchPersonActivities">
                      <bpel:documentation>
                          For each &lt;activities&gt; 'a' of $person tuple:
                             - determine if 'a' matches the i'th element from $acPol
                             - $boolTmp is non-zero if a match exists 
                               (i.e. Person 'unavailable').
                      </bpel:documentation>
                  </bpel:opaqueActivity>
              </bpel:flow>
          </bpel:if>
          
          <bpel:if xmlns:bpel2="http://docs.oasis-open.org/wsbpel/2.0/process/executable">
              <bpel:condition><![CDATA[$boolTmp = 0]]></bpel:condition>
              <bpel:flow>
                  <bpel:opaqueActivity name="findRelevantServiceTuple">
                      <bpel:documentation>
                          Find a service tuple(s) referenced by the applicable 
                          PAL Presence Context in $availEval, and assign the 
                          result to $service.
                      </bpel:documentation>
                  </bpel:opaqueActivity>

                  <bpel:invoke name="validate" partnerLink="ValidationService" 
                      operation="validateServiceTuple" inputVariable="service" 
                        outputVariable="svcTmp"/>

                  <!--  Concurrent activities -->
                  <bpel:opaqueActivity name="establishRegistrationState">
                      <bpel:documentation>
                          Establish &lt;registration-state&gt; and policy 
                          'pc:undef-registration-state' to determine an appropriate 
                          value for the registration state in ##opaque.regState.
                      </bpel:documentation>
                  </bpel:opaqueActivity>
                  <bpel:opaqueActivity name="establishBarringState">
                      <bpel:documentation>
                          Establish &lt;barring-state&gt; and policy 
                          'pc:undef-barring-state' to determine an appropriate 
                          value for the registration state in ##opaque.barState.
                      </bpel:documentation>
                  </bpel:opaqueActivity>
                  
                  <bpel:invoke name="reSync" partnerLink="##opaque" 
                      operation="validateBarRegStates"
                         inputVariable="##opaque" outputVariable="theResult">
                      <bpel:documentation>
                          Re-synchronize two concurrent flows, and verify the 
                          resulting values of ##opaque.regState
                          and ##opaque.barState.  If values are valid/defined, 
                          then $theResult is established based on both 
                          (##opaque.regState = 'active' AND ##opaque.barState = 'active),
                          otherwise base value of $theResult on whether tuple(s) in 
                          $service has a defined 'app-specific-availability' element. 
                      </bpel:documentation>
                  </bpel:invoke>
                      
              </bpel:flow>
          </bpel:if>
          
          <bpel:reply name="ReplyResponseToPartner" partnerLink="client" 
             operation="AvailSubmit" variable="theResult"/>
    </bpel:sequence>
</bpel:process>