Notice the Decision Service Name in the CorticonResponse – this informs the consuming application (which may be consuming several Decision Services asynchronously) which Decision Service is responding in this message:

<CorticonResponse decisionServiceName=“tutorial_example” 
xmlns=“urn:Corticon” xmlns:xsi= “http://www.w3.org/2001/XMLSchema-instance”>
   <WorkDocuments>
     <Cargo id=“Cargo_id_1”>
       <volume>40.000000</volume>
       <weight>16000.000000</weight

Notice that the optional newOrModified attribute has been set to true, indicating that container was modified by the Corticon Server. The value of container, oversize, is the new data derived by the Decision Service.

<container newOrModified=“true”>oversize</container>
     </Cargo>   
  </WorkDocuments> 
</CorticonResponse>
The data contained in the CorticonRequest is returned in the CorticonResponse: 
         <volume>400.000000</volume>
         <weight>160000.000000</weight>
       </cargo>     
    </FlightPlan>   
  </WorkDocuments>   
<Messages version=“1”>

Notice the message generated and returned by the Server:

<Message>
       <severity>Info</severity>       
       <text>Cargo weighing between 150,000 and 200,000 kilograms must be carried
            by a 747.</text>

The entityReference contains an href that associates this message with the FlightPlan that caused it to be produced

      <entityReference href=“#FlightPlan_id_1”/>
     </Message>
   </Messages>
 </CorticonResponse>