Aggregator Patterns - Revision history

ValterAlves at 22:26, 24 May 2012

2012-05-24T22:26:02Z

ValterAlves at 20:37, 23 May 2012

2012-05-23T20:37:20Z

ValterAlves at 15:15, 29 December 2011

2011-12-29T15:15:57Z

ValterAlves at 12:28, 29 December 2011

2011-12-29T12:28:20Z

ValterAlves at 10:57, 14 November 2011

2011-11-14T10:57:57Z

ValterAlves at 15:08, 25 September 2011

2011-09-25T15:08:23Z

ValterAlves: /* Candidates for the category "Aggregator Patterns" (aka "Umbrella Patterns" , "Aggregator Cards", "Umbrella Cards") */

2011-09-03T15:49:41Z

‎Candidates for the category "Aggregator Patterns" (aka "Umbrella Patterns" , "Aggregator Cards", "Umbrella Cards")

ValterAlves at 15:40, 3 September 2011

2011-09-03T15:40:24Z

ValterAlves at 15:38, 3 September 2011

2011-09-03T15:38:05Z

ValterAlves at 23:12, 17 August 2011

2011-08-17T23:12:47Z

@@ Line 1: / Line 1: @@
 We concluded, from the analysis of experiments [REFs], that cards containing aggregator patterns tend to be ineffective, at least when used with the [[Using the Deck|suggested setting]]. Consequently we decided to deprecate aggregator cards (starting from version 2.0).
-The discussion still runs regarding how to treat cards that, although being aggregator – in the sense that they point to other cards for many particular explorations inside its scope – still represent instances that are relevant and do not fit into any of the 'contained' cards. In some cases the solution may consist in creating specific cards to treat those particular exceptions (as we did in the case of the deprecated [[Genre]]). Yet, this is not always interesting because the patterns/cards being generated could be ''too'' specific.
+The discussion still runs regarding how to treat cards that, although being aggregator – in the sense that they point to other cards for many particular explorations inside its scope – still represent instances that are relevant and do not fit into any of the 'contained' cards. In some cases the solution may consist of creating specific cards to treat those particular exceptions (as we did in the case of the deprecated [[Genre]]). Yet, this is not always interesting because the patterns/cards being generated could be ''too'' specific.
 ==Candidates for the category "Aggregator Patterns" (aka "Umbrella Patterns" , "Aggregator Cards", "Umbrella Cards")==

@@ Line 9: / Line 9: @@
 === Borderline ===
 These patterns include many kinds of explorations, some of which are explored in other more specific ('contained') patterns but still address relevant explorations that do not fit other already defined patterns.<br />
-[[Awareness]], [[Acoustic Ecology]], [[Emotional Script]], [[Consequent Sound]], [[Make Sound not War]]
+[[Awareness]], [[Emotional Script]], [[Consequent Sound]], [[Make Sound not War]]

@@ Line 1: / Line 1: @@
 We concluded, from the analysis of experiments [REFs], that cards containing aggregator patterns tend to be ineffective, at least when used with the [[Using the Deck|suggested setting]]. Consequently we decided to deprecate aggregator cards (starting from version 2.0).
-The discussion still runs regarding how to treat cards that, although being aggregator – in the sense that they point to other cards for many particular explorations inside its scope – still represent instances that are relevant and do not fit into any of the 'contained' cards. Is some cases the solution may consist in creating specific cards to treat those particular exceptions (as we did in the case of the deprecated [[Genre]]). Yet, this is not always interesting because the patterns/cards being generated could be ''too'' specific.
+The discussion still runs regarding how to treat cards that, although being aggregator – in the sense that they point to other cards for many particular explorations inside its scope – still represent instances that are relevant and do not fit into any of the 'contained' cards. In some cases the solution may consist in creating specific cards to treat those particular exceptions (as we did in the case of the deprecated [[Genre]]). Yet, this is not always interesting because the patterns/cards being generated could be ''too'' specific.
 ==Candidates for the category "Aggregator Patterns" (aka "Umbrella Patterns" , "Aggregator Cards", "Umbrella Cards")==

@@ Line 9: / Line 9: @@
 === Borderline ===
 These patterns include many kinds of explorations, some of which are explored in other more specific ('contained') patterns but still address relevant explorations that do not fit other already defined patterns.<br />
-[[Awareness]], [[Acoustic Ecology]], [[Emotional Script]], [[Consequent Sound]], [[Make Sound not War]], [[Identification]]
+[[Awareness]], [[Acoustic Ecology]], [[Emotional Script]], [[Consequent Sound]], [[Make Sound not War]]

@@ Line 1: / Line 1: @@
-We concluded, from the analysis of experiments [REFs], that cards containing aggregator patterns tend to be ineffective. Consequently we decided to deprecate aggregator cards.
+We concluded, from the analysis of experiments [REFs], that cards containing aggregator patterns tend to be ineffective, at least when used with the [[Using the Deck|suggested setting]]. Consequently we decided to deprecate aggregator cards (starting from version 2.0).
-The discussion still runs regarding how to treat cards that, being aggregator – in the sense that they point to other cards to many particular explorations inside its scope – still represent instances that are relevant and do not fit into any of the 'contained' cards. Is some cases the solution may consist in creating specific cards to treat those particular exceptions (as we did in the case of the deprecated [[Genre]]). Yet, this is not always interesting because the patterns/cards being generated may be ''too'' specific.
+The discussion still runs regarding how to treat cards that, although being aggregator – in the sense that they point to other cards for many particular explorations inside its scope – still represent instances that are relevant and do not fit into any of the 'contained' cards. Is some cases the solution may consist in creating specific cards to treat those particular exceptions (as we did in the case of the deprecated [[Genre]]). Yet, this is not always interesting because the patterns/cards being generated could be ''too'' specific.
 ==Candidates for the category "Aggregator Patterns" (aka "Umbrella Patterns" , "Aggregator Cards", "Umbrella Cards")==

@@ Line 7: / Line 7: @@
 === Definitely 'Aggregator'===
 [[Genre]], [[Sound Layers and Semantics]] (renamed to [[Sound Layers]]), [[Gameplay]], [[Sound Places]]
-=== Boarderline ===
+=== Borderline ===
 These patterns include many kinds of explorations, some of which are explored in other more specific ('contained') patterns but still address relevant explorations that do not fit other already defined patterns.<br />
 [[Awareness]], [[Acoustic Ecology]], [[Emotional Script]], [[Consequent Sound]], [[Make Sound not War]], [[Identification]]