Anatomy of a Pattern - Revision history

ValterAlves at 23:21, 24 May 2012

2012-05-24T23:21:47Z

ValterAlves at 21:09, 20 May 2012

2012-05-20T21:09:18Z

ValterAlves: /* On the higher level */

2012-02-21T10:54:27Z

‎On the higher level

ValterAlves: /* On the higher level */

2012-02-21T10:53:57Z

‎On the higher level

ValterAlves at 18:11, 30 December 2011

2011-12-30T18:11:11Z

ValterAlves at 22:26, 29 December 2011

2011-12-29T22:26:08Z

ValterAlves at 17:55, 29 September 2011

2011-09-29T17:55:55Z

ValterAlves at 15:55, 19 August 2011

2011-08-19T15:55:34Z

ValterAlves at 15:49, 19 August 2011

2011-08-19T15:49:59Z

ValterAlves at 15:48, 19 August 2011

2011-08-19T15:48:36Z

@@ Line 5: / Line 5: @@
 The nature of such relationships varies:
 * Patterns may contain (non-exclusive) '''alternative''' solutions to a problem
-** e.g. [[Sound Decoys]] and [[Sound Suppressing]] are both usable when willing to design low profile interaction with opponent characters
+** e.g., [[Sound Decoys]] and [[Sound Suppressing]] are both usable when willing to design low profile interaction with opponent characters
 * Patterns may contain '''contrasting''' solutions to a problem
-** e.g. [[Make Sound not War]] and [[Sonic Weapon]] suggest to different approaches to design conflicts
+** e.g., [[Make Sound not War]] and [[Sonic Weapon]] suggest to different approaches to design conflicts
 * A pattern may contribute to solve a specific case of a context/problem (i.e. in an included context)
-** e.g. [[Sound Effects]] may be used to present an [[Achievement]]
+** e.g., [[Sound Effects]] may be used to present an [[Achievement]]
 * A pattern may present a solution that may integrate solutions to different problems
-** e.g. [[Heartbeat]] may used to signal [[Imminent Death]] but may also serve as [[Beacon Locator]] in a [[Echolocation]] approach.
+** e.g., [[Heartbeat]] may used to signal [[Imminent Death]] but may also serve as [[Beacon Locator]] in a [[Echolocation]] approach.
-** e.g. [[Grunts]] may signal damage during an interaction ([[Ouch!]]) as they may be used to present an [[Unaware NPC]], or to provide auditory feedback on the magnitude of the effort the PC applies in some physical movement, amongst others
+** e.g., [[Grunts]] may signal damage during an interaction ([[Ouch!]]) as they may be used to present an [[Unaware NPC]], or to provide auditory feedback on the magnitude of the effort the PC applies in some physical movement, amongst others
 * Patterns may be exhibit solutions for possible '''parts''' of a "more complex" solution
-** e.g. [[Relaxation]], [[Anticipation]], [[Engagement]] and [[Decay]], though being usable in isolation, may be used to create [[R-A-E-D Iterations]]
+** e.g., [[Relaxation]], [[Anticipation]], [[Engagement]] and [[Decay]], though being usable in isolation, may be used to create [[R-A-E-D Iterations]]
 * Complementarity alternative solutions to a problem
@@ Line 20: / Line 20: @@
 Subjectivity added to the objectivity of rare (but relevant) exceptions make every setting of relationships potentially arguable. The expression of the set of relationships for a pattern is invariably the outcome of a compromise.
 For instance [pending]:
-** e.g. consider the patterns [[Achievement]] and [[Failure]]. Both usable to provide awareness for the outcome of a certain behaviour, but usually they are (...) . Still:
+** e.g., consider the patterns [[Achievement]] and [[Failure]]. Both usable to provide awareness for the outcome of a certain behaviour, but usually they are (...) . Still:
 *** they could be thought of as parts of an evaluation mechanism
 *** they do not necessarily inhibit each other in a same moment
@@ Line 45: / Line 45: @@
 * '''Synopsis''': the shortest possible sentence that identifies the contents of the pattern. In many cases we opted by the formula: 'use this solution when faced with this problem'. Still particular cases call for adaptations. For instance:
 **In higher level patterns this tends to be kind of problems addressed
-***e.g. in {{#rellist: Sound Input|:}} 'The way sound enters the game world'
+***e.g., in {{#rellist: Sound Input|:}} 'The way sound enters the game world'
-***e.g. in {{#rellist: Character Soundprint|:}} 'The set of sounds of a PC or NPC'
+***e.g., in {{#rellist: Character Soundprint|:}} 'The set of sounds of a PC or NPC'
-***e.g. in {{#rellist: Dialogue|:}} 'All sorts of conversation'
+***e.g., in {{#rellist: Dialogue|:}} 'All sorts of conversation'
 **In lower level patterns this tends to be the solution, and the problem and/or the context if its not tacit enough
-***e.g. in {{#rellist: Eavesdropping|:}} 'Adopting behaviours with the intention of gaining knowledge by listening to others' conversations.'
+***e.g., in {{#rellist: Eavesdropping|:}} 'Adopting behaviours with the intention of gaining knowledge by listening to others' conversations.'
-***e.g. in {{#rellist: Sing to Act|:}} 'Performing songs to achieve a purpose.'
+***e.g., in {{#rellist: Sing to Act|:}} 'Performing songs to achieve a purpose.'
 * '''Relationships''':
 {{InsertReferencesH2}}

@@ Line 45: / Line 45: @@
 * '''Synopsis''': the shortest possible sentence that identifies the contents of the pattern. In many cases we opted by the formula: 'use this solution when faced with this problem'. Still particular cases call for adaptations. For instance:
 **In higher level patterns this tends to be kind of problems addressed
-***e.g. in {{#rellist: Sound Input|:}} 'The way sound enters the gameworld'
+***e.g. in {{#rellist: Sound Input|:}} 'The way sound enters the game world'
 ***e.g. in {{#rellist: Character Soundprint|:}} 'The set of sounds of a PC or NPC'
 ***e.g. in {{#rellist: Dialogue|:}} 'All sorts of conversation'

@@ Line 33: / Line 33: @@
 ==== On the higher level====
-The highest level is symbolised by the card {{#rellist: Sound Design in Games}}which is assumedly a card aside others.
+The highest level is symbolised by the card {{#rellist: Sound Design in Games}} which is assumedly a card aside others.
 The next level of patterns are those that exclusively aggregate others, without carrying any specific exploration themselves. These aggregator patterns are relevant but not effective when expressed as deck cards (see the [[rationale]]). As such this is a level that interests us when considering patterns but which is out of boundaries when considering their representation as cards.

@@ Line 33: / Line 33: @@
 ==== On the higher level====
-The highest level is symbolised by the card {{#rellist: Sound Design in Games}} which is assumedly a card aside others.
+The highest level is symbolised by the card {{#rellist: Sound Design in Games}}which is assumedly a card aside others.
 The next level of patterns are those that exclusively aggregate others, without carrying any specific exploration themselves. These aggregator patterns are relevant but not effective when expressed as deck cards (see the [[rationale]]). As such this is a level that interests us when considering patterns but which is out of boundaries when considering their representation as cards.

@@ Line 7: / Line 7: @@
 ** e.g. [[Sound Decoys]] and [[Sound Suppressing]] are both usable when willing to design low profile interaction with opponent characters
 * Patterns may contain '''contrasting''' solutions to a problem
-** e.g. [[Make sound not War]] and [[Sonic Weapons]] suggest to different approaches to design conflicts
+** e.g. [[Make Sound not War]] and [[Sonic Weapon]] suggest to different approaches to design conflicts
 * A pattern may contribute to solve a specific case of a context/problem (i.e. in an included context)
 ** e.g. [[Sound Effects]] may be used to present an [[Achievement]]

@@ Line 28: / Line 28: @@
 [pending: graph illustrations allusive to overlapping pattens]
 ====Aggregator Cards====
-Were are calling '[[Aggregator Patterns|Aggregator Pattern]]' to those which exclusively characterise a set of more specific solutions, without present no specific solution per se. Aggregator Patterns evidence [[Categories]] of Patterns (a concept that we are considering to explore but did not yet, to date).
+We are calling '[[Aggregator Patterns|Aggregator Pattern]]' to those which exclusively characterise a set of more specific solutions, without present no specific solution per se. Aggregator Patterns evidence [[Categories]] of Patterns (a concept that we are considering to explore but did not yet, to date).
 ===On the boundaries of the global scope===

← Older revision		Revision as of 17:55, 29 September 2011
Line 1:		Line 1:
−	{{DraftNotice}}	+	{{DraftNotice}}<br />

	== Network of patterns ==		== Network of patterns ==

← Older revision		Revision as of 15:49, 19 August 2011
Line 52:		Line 52:
	***e.g. in {{#rellist: Sing to Act\|:}} 'Performing songs to achieve a purpose.'		***e.g. in {{#rellist: Sing to Act\|:}} 'Performing songs to achieve a purpose.'
	* '''Relationships''':		* '''Relationships''':
		+	<references>{{CompleteReferenceList}}</references>

@@ Line 2: / Line 2: @@
 == Network of patterns ==
-Patterns are by definition related. The specification of those relationships defines the language (of which the pattern names are the words of the vocabulary).
+In a Pattern Language, patterns relate to each other, by definition<ref name="Alexander79"/><ref name="Alexander77"/>. The specification of those relationships defines the language (of which the pattern names are the words of the vocabulary).
 The nature of such relationships varies:
 * Patterns may contain (non-exclusive) '''alternative''' solutions to a problem