caprice Wiki Rss Feedhttps://caprice.codeplex.com/caprice Wiki Rss DescriptionUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=42<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps: <br />(See example screenshots for each step by clicking the associated link)
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b>:Build a domain model consisting of context attributes and learned inference rules.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b>: Initialise a repository of privacy policies.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b>: Build a finite state machine and associate policies to state transitions.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b>: Build a group of interacting agents and associate a FSM instance to each agent.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b>:
<ol><li>Configure adaptation rules based specifying mitigation actions based on threat severity. </li>
<li>Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.</li></ol></li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b>: Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</li></ol></div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:58:10 GMTUpdated Wiki: User Manual 20120515015810PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=41<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps (See example screenshots for each step by clicking the associated link):
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b>:Build a domain model consisting of context attributes and learned inference rules.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b>: Initialise a repository of privacy policies.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b>: Build a finite state machine and associate policies to state transitions.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b>: Build a group of interacting agents and associate a FSM instance to each agent.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b>:
<ol><li>Configure adaptation rules based specifying mitigation actions based on threat severity. </li>
<li>Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.</li></ol></li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b>: Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</li></ol></div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:57:36 GMTUpdated Wiki: User Manual 20120515015736PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=40<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps (clicking the link for each step shows some example screenshots for that step):
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b>:Build a domain model consisting of context attributes and learned inference rules.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b>: Initialise a repository of privacy policies.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b>: Build a finite state machine and associate policies to state transitions.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b>: Build a group of interacting agents and associate a FSM instance to each agent.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b>:
<ol><li>Configure adaptation rules based specifying mitigation actions based on threat severity. </li>
<li>Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.</li></ol></li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b>: Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</li></ol></div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:56:16 GMTUpdated Wiki: User Manual 20120515015616PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=39<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps:
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b>:Build a domain model consisting of context attributes and learned inference rules.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b>: Initialise a repository of privacy policies.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b>: Build a finite state machine and associate policies to state transitions.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b>: Build a group of interacting agents and associate a FSM instance to each agent.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b>:
<ol><li>Configure adaptation rules based specifying mitigation actions based on threat severity. </li>
<li>Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.</li></ol></li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b>: Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</li></ol></div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:53:43 GMTUpdated Wiki: User Manual 20120515015343PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=38<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps:<br />
<ol><li><u><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b></u>:Build a domain model consisting of context attributes and learned inference rules.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b>: Initialise a repository of privacy policies.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b>: Build a finite state machine and associate policies to state transitions.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b>: Build a group of interacting agents and associate a FSM instance to each agent.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b>:
<ol><li>Configure adaptation rules based specifying mitigation actions based on threat severity. </li>
<li>Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.</li></ol></li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b>: Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</li></ol></div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:52:29 GMTUpdated Wiki: User Manual 20120515015229PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=37<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps:<br />
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b>:</li></ol>
Build a domain model consisting of context attributes and learned inference rules.
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b>: Initialise a repository of privacy policies.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b>: Build a finite state machine and associate policies to state transitions.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b>: Build a group of interacting agents and associate a FSM instance to each agent.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b>:
<ol><li>Configure adaptation rules based specifying mitigation actions based on threat severity. </li>
<li>Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.</li></ol></li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b>: Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</li></ol></div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:51:49 GMTUpdated Wiki: User Manual 20120515015149PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=36<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps:<br />
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b>: Build a domain model consisting of context attributes and learned inference rules.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b>: Initialise a repository of privacy policies.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b>: Build a finite state machine and associate policies to state transitions.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b>: Build a group of interacting agents and associate a FSM instance to each agent.</li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b>:
<ol><li>Configure adaptation rules based specifying mitigation actions based on threat severity. </li>
<li>Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.</li></ol></li>
<li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b>: Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</li></ol></div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:50:49 GMTUpdated Wiki: User Manual 20120515015049PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=35<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps:<br />
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b>: Build a domain model consisting of context attributes and learned inference rules.</li></ol>
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b>: Initialise a repository of privacy policies</li></ol>
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b>: Build a finite state machine and associate policies to state transitions.</li></ol>
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b>: Build a group of interacting agents and associate a FSM instance to each agent.</li></ol>
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b>:
<ol><li>Configure adaptation rules based specifying mitigation actions based on threat severity. </li>
<li>Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.</li></ol></li></ol>
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b>: Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</li></ol></div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:50:14 GMTUpdated Wiki: User Manual 20120515015014PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=34<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps:<br />
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b>:</li></ol>
Build a domain model consisting of context attributes and learned inference rules<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:48:26 GMTUpdated Wiki: User Manual 20120515014826PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=33<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps:<br />
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b>: Build a domain model consisting of context attributes and learned inference rules</li></ol>
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:48:12 GMTUpdated Wiki: User Manual 20120515014812PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=32<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps:<br />
<ol><li><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b></li></ol>
Build a domain model consisting of context attributes and learned inference rules<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:47:51 GMTUpdated Wiki: User Manual 20120515014751PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=31<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
Generally, using Caprice involves the following steps:<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b></h5>
Build a domain model consisting of context attributes and learned inference rules<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:39:14 GMTUpdated Wiki: User Manual 20120515013914PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=30<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
<br />Generally, using Caprice involves the following steps:<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b></h5>
Build a domain model consisting of context attributes and learned inference rules<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:38:57 GMTUpdated Wiki: User Manual 20120515013857PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=29<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.</li>
<li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
<br />Generally, involves the following usage steps:<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b></h5>
Build a domain model consisting of context attributes and learned inference rules<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:37:59 GMTUpdated Wiki: User Manual 20120515013759PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=28<div class="wikidoc"><b>Usage Guide</b><br />The download bundle comes with two preinstalled examples.
<ol><li>The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.
<ol><li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol></li></ol>
<br />Generally, involves the following usage steps:<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b></h5>
Build a domain model consisting of context attributes and learned inference rules<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:37:48 GMTUpdated Wiki: User Manual 20120515013748PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=27<div class="wikidoc"><b>Usage Guide</b>
<ol><li>The download bundle comes preinstalled with two examples.</li></ol>
The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.
<ol><li>The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.</li></ol>
<br />Generally, involves the following usage steps:<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b></h5>
Build a domain model consisting of context attributes and learned inference rules<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:37:08 GMTUpdated Wiki: User Manual 20120515013708PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=26<div class="wikidoc"><b>Usage Guide</b><br />#The download bundle comes preinstalled with two examples.<br />The first example is a track sharing mobile application for runners and other outdoor activity. Similar examples of such application include B.iCycle (http://b-icycle.com/), MyTracks (mytracks.appspot.com/) etc. Typically, such applications enable a group of runners to share live GPS tracks and performance statistics with fellow runners and other agents such as their fitness instructors and physicians.<br />##The second example is a participatory sensing system that helps drivers spend less time looking for parking spaces in a city centre. Typical examples include Google Open Spot (openspot.googlelabs.com/) and Roadify (www.roadify.com/). We focus on key functionalities that enable drivers to post, request and display the fuel-optimal, shortest, or fastest routes to an empty parking space.<br /><br />Generally, involves the following usage steps:<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b></h5>
Build a domain model consisting of context attributes and learned inference rules<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:36:48 GMTUpdated Wiki: User Manual 20120515013648PUpdated Wiki: Homehttp://caprice.codeplex.com/wikipage?version=16<div class="wikidoc"><b>Project Description</b><br />Caprice is a tool aimed at supporting software engineers in the design of applications that appropriately adapt their behaviour to mitigate privacy threats. This tool helps provide software engineers design-time insight on the functional behaviour of a system and the associated runtime context changes that can threaten privacy.<br /><br /><b>Core features:</b>
<ul><li> Identifies the contextual properties that have to be monitored in order to detect context changes that might threaten privacy. </li>
<li>Reasons over a history of agent interactions to discover privacy threats. </li>
<li>Suggests possible threat mitigation action based on the severity of discovered threat. </li></ul>
<b><a href="http://caprice.codeplex.com/documentation?referringTitle=Home">Documentation</a></b>, <b><a href="http://caprice.codeplex.com/wikipage?title=User%20Manual&referringTitle=Home">User Manual</a></b>, <b><a href="http://caprice.codeplex.com/wikipage?title=Installation%20Instructions&referringTitle=Home">Installation Instructions</a></b><br /><br /><img src="http://i3.codeplex.com/Download?ProjectName=caprice&DownloadId=379088" alt="Capturexxyyz.PNG" title="Capturexxyyz.PNG" /><br />(<b>NOTE:</b> This tool is made available for review and testing purpose only.)</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:17:25 GMTUpdated Wiki: Home 20120515011725PUpdated Wiki: User Manualhttp://caprice.codeplex.com/wikipage?title=User Manual&version=25<div class="wikidoc"><b>Usage Guide</b><br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%201%20%28e.g.%29&referringTitle=User%20Manual">Step 1 &#40;e.g.&#41;</a></b></h5>
Build a domain model consisting of context attributes and learned inference rules<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%202%20%28e.g.%29&referringTitle=User%20Manual">Step 2 &#40;e.g.&#41;</a></b></h5>
Initialise a repository of privacy policies<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%203%20%28e.g.%29&referringTitle=User%20Manual">Step 3 &#40;e.g.&#41;</a></b></h5>
Build a finite state machine and associate policies to state transitions<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%204%20%28e.g.%29&referringTitle=User%20Manual">Step 4 &#40;e.g.&#41;</a></b></h5>
Build a group of interacting agents and associate a FSM instance to each agent.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%205%20%28e.g.%29&referringTitle=User%20Manual">Step 5 &#40;e.g.&#41;</a></b></h5>
- Configure adaptation rules based specifying mitigation actions based on threat severity. <br />- Configure meta-adaptation rules based on the frequency of reoccurrence of previously mitigated privacy threat.<br />
<h5><b><a href="http://caprice.codeplex.com/wikipage?title=Step%206%20%28e.g.%29&referringTitle=User%20Manual">Step 6 &#40;e.g.&#41;</a></b></h5>
Based on Step 4 and 5, Caprice emulates a group interaction process. This involves simulating a sequence of message transfers between different agents across different operational context instances. For each message transfer, the associated operational context is analysed to discover if privacy is threatened as a result of the interaction. If privacy is threatened, Caprice also suggests appropriate mitigation action based on the severity of the threat.</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:15:35 GMTUpdated Wiki: User Manual 20120515011535PUpdated Wiki: Homehttp://caprice.codeplex.com/wikipage?version=15<div class="wikidoc"><b>Project Description</b><br />Caprice is a tool aimed at supporting software engineers in the design of applications that appropriately adapt their behaviour to mitigate privacy threats. This tool helps provide software engineers design-time insight on the functional behaviour of a system and the associated runtime context changes that can threaten privacy.<br /><br /><b>Core features:</b>
<ul><li> Identifies the contextual properties that have to be monitored in order to detect context changes that might threaten privacy. </li>
<li>Reasons over a history of agent interactions to discover privacy threats. </li>
<li>Suggests possible threat mitigation action based on the severity of discovered threat. </li></ul>
<b><a href="http://caprice.codeplex.com/documentation?referringTitle=Home">Documentation</a></b>, <b><a href="http://caprice.codeplex.com/wikipage?title=User%20Manual&referringTitle=Home">User Manual</a></b>, <b><a href="http://caprice.codeplex.com/wikipage?title=Installation%20Instructions&referringTitle=Home">Installation Instructions</a></b><br /><br /><img src="http://i3.codeplex.com/Download?ProjectName=caprice&DownloadId=379085" alt="Capture_09_05_1.PNG" title="Capture_09_05_1.PNG" /><br />(<b>NOTE:</b> This tool is made available for review and testing purpose only.)</div><div class="ClearBoth"></div>omoronyiaTue, 15 May 2012 13:14:41 GMTUpdated Wiki: Home 20120515011441P