Differences

This shows you the differences between two versions of the page.

--- future_fabulators:confabulation [2014-02-12 23:44] – nik
+++ future_fabulators:confabulation [2014-02-14 06:33] – [scenario database] maja
@@ Line 6: / Line 6: @@
 “Any useful idea about the future should appear to be ridiculous” Dator’s 2nd Law of the Future (Dator 1995)
 ==== external / rational ====
@@ Line 47: / Line 46: @@
     * what is the shortest and/or longest time in which we can complete meaningful scenario workshops and/or prehearsals to come up with interesting results while keeping the process enjoyable for the participants?
     * what other methods, aside from scenario building, are used to discuss possible futures?
-    * what can we borrow from other fields, such as; improv,
+    * what can we borrow from other fields, such as; improv, role playing games, LARP, disaster drills, meditation… to improve prehearsals?
+  * how can we help increase the commitment of the participants to work towards their preferred future(s)? how much follow-up is needed?
+  * how could we enable participants to use digital tools to enrich the process, while avoiding distractions and displacements of email, social media, etc? what collaborative digital tools could we use to share the same digital working surface (something like Reactable for example)
+==== scenario database ====
+20140205 While editing [[scenarios]] it became apparent how tricky it is to keep a consistency in information and layout of the scenarios. The scenario database we're planning to make should make this easier. Components that seem to be needed in all scenarios:
+  * what is the question?
+  * what are the scenario axes?
+  * sometimes we have a short answer to the question (usually created after making the scenarios)
+  * how far in the future does the scenario take place?
+  * scenario description
+  * genaral image(s)
+  * more specific/clarifying images
+  * links to the pages of related scenarios (and a 'parent' page that describes the workshop goals etc. - not sure if we should include this in the database?)
+should we try to contextualise the scenarios directly in the database?
+  * a section with links to projects/theories/examples of (the beginnings of) this scenario already taking place today
+  * section on how the scenario is turned into a prehearsal (could be in the form of a 'day in the life of..."?
+  * reflections on the prehearsal
+  * etc.
+or should we keep the database only as a 'short story collection'?
+a rather bad example of a scenario database is the [[http://www.millennium-project.org/millennium/futuresmatrix.html|Millennium Project's Futures Matrix]]
+==== software & protocols ====
+  * open formats > closed formats
+  * utf-8 > ascii/latin-1/etc+
+  * documents
+    * utf-8 text or ODF (libreoffice, openoffice) for editable docs
+    * pdf for reference & archiving
+    * [[:graph_drawing#vue_visual_understanding_environment|VUE]] for diagrams
+  * semi syncronous; email, twitter, irc (freenode -> #ff ?)
+  * asyncronous; dokuwiki, django, gitlab
+  * algorithmic sketching; racket, common lisp, python, git
+  * online
+    * **libarynth** for text, tangents and collation -> http://libarynth.org
+    * **flickr** for image matter -> https://secure.flickr.com/photos/foam/
+    * **vimeo** for video matter -> http://vimeo.com/fo4m
+    * **zotero** for library and references -> https://www.zotero.org/groups/foam_library
+  * potentially
+    * tumblr, cargo, diasp, other?
+    * prediction book
+    * wikipedia