<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Use Cases</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>Recent changes to Use Cases</description><atom:link href="https://sourceforge.net/p/statelets/wiki/Use%20Cases/feed" rel="self"/><language>en</language><lastBuildDate>Wed, 07 Mar 2012 15:23:47 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/statelets/wiki/Use%20Cases/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;--- v10 
+++ v11 
@@ -1,5 +1,5 @@
 Examples of people coordination in the Statelets language can be found in the Examples project in the source code. The examples where developed using Microsoft Visual Studio 2010.
-In order to try out examples, open the Statelets solution, set Examples as startup project and then run VS in debug mode (Program.fs contains functions representing several examples). Some examples also have accompanying dummy context providers that simulate integration of groupware and social networking services.
+In order to try out examples, open the Statelets solution, set Examples as startup project and then run it in a debug mode (Program.fs contains functions representing several examples). Some examples also have accompanying dummy context providers that simulate integration of groupware and social networking services.
 
 .) Analysis projects. This use case exemplifies implementation of a collaboration process based on MediaWiki engine. Collaboration is described as an evolving network of related documents. File: "usecase1.statelets"
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Wed, 07 Mar 2012 15:23:47 -0000</pubDate><guid>https://sourceforge.net7ebe21456363a180bfc77df05a43a3bd82edad85</guid></item><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;--- v9 
+++ v10 
@@ -1,5 +1,5 @@
 Examples of people coordination in the Statelets language can be found in the Examples project in the source code. The examples where developed using Microsoft Visual Studio 2010.
-In order to try out examples, open the Statelets solution, set Examples as startup project and then run VS in debug or release mode (Program.fs contains functions representing several examples). Some examples also have accompanying dummy context providers that simulate integration of groupware and social networking services.
+In order to try out examples, open the Statelets solution, set Examples as startup project and then run VS in debug mode (Program.fs contains functions representing several examples). Some examples also have accompanying dummy context providers that simulate integration of groupware and social networking services.
 
 .) Analysis projects. This use case exemplifies implementation of a collaboration process based on MediaWiki engine. Collaboration is described as an evolving network of related documents. File: "usecase1.statelets"
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Wed, 07 Mar 2012 15:23:13 -0000</pubDate><guid>https://sourceforge.neta94438eb65230634ab3d94bd29b08ad9d46ffe5a</guid></item><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;--- v8 
+++ v9 
@@ -1,8 +1,6 @@
 Examples of people coordination in the Statelets language can be found in the Examples project in the source code. The examples where developed using Microsoft Visual Studio 2010.
 In order to try out examples, open the Statelets solution, set Examples as startup project and then run VS in debug or release mode (Program.fs contains functions representing several examples). Some examples also have accompanying dummy context providers that simulate integration of groupware and social networking services.
 
-Here is the list of available currently examples:
-
 .) Analysis projects. This use case exemplifies implementation of a collaboration process based on MediaWiki engine. Collaboration is described as an evolving network of related documents. File: "usecase1.statelets"
 
 .) Engineering projects. This use case exemplifies selection of a reviewer socially related to a development team. File: "usecase2.statelets"
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Wed, 07 Mar 2012 15:16:22 -0000</pubDate><guid>https://sourceforge.net8370d1acde1f228159dacede93d00e24c4720660</guid></item><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;--- v7 
+++ v8 
@@ -3,14 +3,12 @@
 
 Here is the list of available currently examples:
 
-1) Analysis projects. This use case exemplifies implementation of a collaboration process based on MediaWiki engine. Collaboration is described as an evolving network of related documents. File: "usecase1.statelets"
-
-2) Engineering projects. This use case exemplifies selection of a reviewer socially related to a development team. File: "usecase2.statelets"
-
-3) Map/reduce pattern. This use case exemplifies implementation of classical map/reduce. Statelets do not offer any specific means to support this patter, the use case only shows how this pattern can be implemented to better understand the language. File: "mapReducePattern.statelets"
-
-4) Selection of a socially coherent team. This use case exemplifies declarative selection of a socially coherent teams that consist of 4 team members. The topology of the team is strictly specified (it should be square). This use case exemplifies suitability of statelets to detailed and specific social selection scenarios. File: "SociallyCoherentTeam.statelets"
-
-5) Party organization. In this use case is reflected behavior of certain social network. Each person in the network starts in a Bored state. If there is a message observed in a persons Twitter news-line with the word party, then workflow for this person switches to WantToParty state in order to publish its intention. Alternatively, if at least two of the friends want to party, then the same effect happens. File: "party.statelets".
-
-6) ...
+.) Analysis projects. This use case exemplifies implementation of a collaboration process based on MediaWiki engine. Collaboration is described as an evolving network of related documents. File: "usecase1.statelets"
+
+.) Engineering projects. This use case exemplifies selection of a reviewer socially related to a development team. File: "usecase2.statelets"
+
+.) Selection of a socially coherent team. This use case exemplifies declarative selection of a socially coherent teams that consist of 4 team members. The topology of the team is strictly specified (it should be square). This use case exemplifies suitability of statelets to detailed and specific social selection scenarios. File: "SociallyCoherentTeam.statelets"
+
+.) Party organization. In this use case is reflected behavior of certain social network. Each person in the network starts in a Bored state. If there is a message observed in a persons Twitter news-line with the word party, then workflow for this person switches to WantToParty state in order to publish its intention. Alternatively, if at least two of the friends want to party, then the same effect happens. File: "party.statelets".
+
+.) Map/reduce pattern. This use case exemplifies implementation of classical map/reduce. Statelets do not offer any specific means to support this patter, the use case only shows how this pattern can be implemented to better understand the language. File: "mapReducePattern.statelets"
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Wed, 07 Mar 2012 15:11:42 -0000</pubDate><guid>https://sourceforge.net28fcc3b6e574ef6e271ce002e4bbe3f38c990de8</guid></item><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;--- v6 
+++ v7 
@@ -11,6 +11,6 @@
 
 4) Selection of a socially coherent team. This use case exemplifies declarative selection of a socially coherent teams that consist of 4 team members. The topology of the team is strictly specified (it should be square). This use case exemplifies suitability of statelets to detailed and specific social selection scenarios. File: "SociallyCoherentTeam.statelets"
 
-5) Party organization. In this use case is reflected behavior of certain social network. Each person in the network starts in a Bored state. If there is a message observed in a persons Twitter news-line with the word party, then workflow for this person switches to WantToParty state in order to publish its intention, alternately, if at least two of the friends want to party, then the same effect happens. File: "party.statelets".
+5) Party organization. In this use case is reflected behavior of certain social network. Each person in the network starts in a Bored state. If there is a message observed in a persons Twitter news-line with the word party, then workflow for this person switches to WantToParty state in order to publish its intention. Alternatively, if at least two of the friends want to party, then the same effect happens. File: "party.statelets".
 
 6) ...
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Tue, 06 Mar 2012 17:07:21 -0000</pubDate><guid>https://sourceforge.net3f92de7f6256d456f556ab13d661a538772fe535</guid></item><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;--- v5 
+++ v6 
@@ -11,4 +11,6 @@
 
 4) Selection of a socially coherent team. This use case exemplifies declarative selection of a socially coherent teams that consist of 4 team members. The topology of the team is strictly specified (it should be square). This use case exemplifies suitability of statelets to detailed and specific social selection scenarios. File: "SociallyCoherentTeam.statelets"
 
-5) Social network behavior...
+5) Party organization. In this use case is reflected behavior of certain social network. Each person in the network starts in a Bored state. If there is a message observed in a persons Twitter news-line with the word party, then workflow for this person switches to WantToParty state in order to publish its intention, alternately, if at least two of the friends want to party, then the same effect happens. File: "party.statelets".
+
+6) ...
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Wed, 29 Feb 2012 08:52:18 -0000</pubDate><guid>https://sourceforge.netf6dd014f8af778d8543ad5066ae63e96072d9f59</guid></item><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;--- v4 
+++ v5 
@@ -9,6 +9,6 @@
 
 3) Map/reduce pattern. This use case exemplifies implementation of classical map/reduce. Statelets do not offer any specific means to support this patter, the use case only shows how this pattern can be implemented to better understand the language. File: "mapReducePattern.statelets"
 
-4) Selection of a socially coherent team. This use case exemplifies declarative selection of a socially coherent teams that consist of 4 team members. The topology of the team is strictly specified (it should be square). File: "SociallyCoherentTeam.statelets"
+4) Selection of a socially coherent team. This use case exemplifies declarative selection of a socially coherent teams that consist of 4 team members. The topology of the team is strictly specified (it should be square). This use case exemplifies suitability of statelets to detailed and specific social selection scenarios. File: "SociallyCoherentTeam.statelets"
 
 5) Social network behavior...
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Tue, 28 Feb 2012 16:39:17 -0000</pubDate><guid>https://sourceforge.net64d7b81a3e98b663205ecc05cca0c8956a60e23a</guid></item><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;--- v3 
+++ v4 
@@ -9,6 +9,6 @@
 
 3) Map/reduce pattern. This use case exemplifies implementation of classical map/reduce. Statelets do not offer any specific means to support this patter, the use case only shows how this pattern can be implemented to better understand the language. File: "mapReducePattern.statelets"
 
-4) Selection of a socially coherent team. This use case exemplifies declarative selection of a socially coherent teams that consist of 4 team members. File: "SociallyCoherentTeam.statelets"
+4) Selection of a socially coherent team. This use case exemplifies declarative selection of a socially coherent teams that consist of 4 team members. The topology of the team is strictly specified (it should be square). File: "SociallyCoherentTeam.statelets"
 
 5) Social network behavior...
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Tue, 28 Feb 2012 16:38:19 -0000</pubDate><guid>https://sourceforge.netebb5bf6026de423b9fb6c8d31dd338978b5bd4d3</guid></item><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;--- v2 
+++ v3 
@@ -1,2 +1,14 @@
 Examples of people coordination in the Statelets language can be found in the Examples project in the source code. The examples where developed using Microsoft Visual Studio 2010.
-In order to try out examples, open the Statelets solution, set Examples as startup project and then run VS in debug or release mode (Program.fs contains functions representing several examples).
+In order to try out examples, open the Statelets solution, set Examples as startup project and then run VS in debug or release mode (Program.fs contains functions representing several examples). Some examples also have accompanying dummy context providers that simulate integration of groupware and social networking services.
+
+Here is the list of available currently examples:
+
+1) Analysis projects. This use case exemplifies implementation of a collaboration process based on MediaWiki engine. Collaboration is described as an evolving network of related documents. File: "usecase1.statelets"
+
+2) Engineering projects. This use case exemplifies selection of a reviewer socially related to a development team. File: "usecase2.statelets"
+
+3) Map/reduce pattern. This use case exemplifies implementation of classical map/reduce. Statelets do not offer any specific means to support this patter, the use case only shows how this pattern can be implemented to better understand the language. File: "mapReducePattern.statelets"
+
+4) Selection of a socially coherent team. This use case exemplifies declarative selection of a socially coherent teams that consist of 4 team members. File: "SociallyCoherentTeam.statelets"
+
+5) Social network behavior...
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Tue, 28 Feb 2012 16:30:17 -0000</pubDate><guid>https://sourceforge.neta8ed2300a09d0b7aa7f7b464f4de637fb5224536</guid></item><item><title>WikiPage Use Cases modified by Vitaliy Liptchinsky</title><link>https://sourceforge.net/p/statelets/wiki/Use%2520Cases/</link><description>&lt;pre&gt;&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vitaliy Liptchinsky</dc:creator><pubDate>Tue, 28 Feb 2012 16:15:05 -0000</pubDate><guid>https://sourceforge.neta2a9d025dedd6481b1e0e873b73c2cc03fcf3df9</guid></item></channel></rss>