Latest revision as of 13:35, 6 June 2016

i-could-have-written-that

on the moments between you and text mining results

*

For in those realms machines are made to behave in wondrous ways, often sufficient to dazzle even the most experienced observer. But once a particular program is unmasked, once its inner workings are explained in language sufficiently plain to induce understanding, its magic crumbles away; it stands revealed as a mere collection of procedures, each quite comprehensible. The observer says to himself "I could have written that". With that thought he moves the program in question from the shelf marked "intelligent" to that reserved for curious. (Joseph Weizenbaum, 1966)

i-could-have-written-that - documentation

i-could-have-written-that.info
wiki page for catalog + website
research material collection

 workshop excercise: if, if, if, else

 workshop excercise: binary oppositions

process pages

* static HTML webpage; filesystem interface for research related material (+ about the workflow)
* collective archive ?
* historical context (of information-processing-systems/communication-systems/code-systems/...?) (list?)
* little glossary

zine editions

#0.1: heteromation

(on division of labour between humans & machines)
→ as publication next to the H.I.T. performance @ V2_ (Feb. 12th, 2016)

#0.2: algorithmic agreeability

on the systems of information creation in the field of text mining

hypothesis: The results of data-mining software are not mined, results are created.

currently working on

* terminology: data 'mining'
* Knowledge Discovery in Data (KDD) in the wild, problem formulations
* KDD, applications
* KDD, workflow
* text-processing: simplification
* list of data mining parties

exercises & co

* visual rhetorical rap - visualizing modality.py's effect on texts
* twitter-truth - training a KNN classifier on *live* tweets

#0.2 - NLP elements

(concequenses of?) naturalization of algortihmic & mining results

→ (too) easily regarded as objective 'truth' makers

* automatic reading machines; from encoding-decoding to constructed-truths (video/slideshow?)
* Antoinette Rouvroy; All Watched Over by Algorithms, Transmediale 2015 (transcription)
* •laughter•, it's embarrassing but these are the words
* EUR PhD presentation 'Sentiment Analysis of Text Guided by Semantics and Structure' (13-11-2015)
* what about text-mining? (readinglist sorted on points of 'algorithm' critique)

'knowledge bases'

→ taxonomies & vocabularies; linked data
→ aim for universal 'ontology' to represent the 'real'

* WordNet case-studies
* index of Roget's thesaurus (1805)

heteromation

→ 'heteromation': division of labor between humans and computer systems (more here)
→ aim for a syntactical perspective on computer processes or results
→ ways of relating to computers systems

* call for a syntactic view; Florian Cramer & Benjamin Bratton (text)
* anthropomorphic qualities of a computer (?)
* the photographic apparatus → the data apparatus (voice-over?)
* Computer Power and Human Reason, Joseph Weizenbaum (1976) (annotations)

object-predicate relation

* Matthew Fuller on 'the red haired man' (poem)

semantic math

* semantic averaging polarity rates in Pattern
* counting tokens for Friendly Flickr Tags

publishing

design of information processes

* html recipes
* WN nested structure proto? (catalog? (similar to i-will-tell-you-everything))
* information processes design proto's?

publishing references

* publication examples (current and former) (list)
* publishing frameworks (list)

notes

how to understand pattern recognition → in the wild → Algopop by Matthew Plummer-Fernandez

this language poem is a practise of using language,
in stead of reffering to the real world 
— Matthew Fuller, about 'the red-haired man' (Mons, Okt. 2015)

'information processing machines' vs. 'computer operating systems', Neal Stephenson

*design*: from 'designing information' to 'designing information processes'

@@ Line 2: / Line 2: @@
 __NOTOC__
 =i-could-have-written-that=
-[[File:Charles-Petzold_Chapt-11_wiring-relays_AND-OR-NAND-NOR.png]]<br>
+[[File:Perceiving-a-wordcloud.png|800px]]<br>
-<small>from: Charles Petzold's book 'Code', Chapter 11: Wiring Relays - AND OR NAND NOR</small>
+<small>on the moments between you and text mining results</small>
+==*==
+''For in those realms machines are made to behave in wondrous ways, often sufficient to dazzle even the most experienced observer. But once a particular program is unmasked, once its inner workings are explained in language sufficiently plain to induce understanding, its magic crumbles away; it stands revealed as a mere collection of procedures, each quite comprehensible. The observer says to himself "I could have written that". With that thought he moves the program in question from the shelf marked "intelligent" to that reserved for curious.'' [http://www.csee.umbc.edu/courses/331/papers/eliza.html (Joseph Weizenbaum, 1966)]
+==i-could-have-written-that - documentation==
+[http://www.i-could-have-written-that.info i-could-have-written-that.info]<br>
+[http://pzwiki.wdka.nl/mediadesign/I-could-have-written-that wiki page for catalog + website]<br>
+[http://pzwart1.wdka.hro.nl/~manetta/i-could-have-written-that/ research material collection]<br>
+ [[User:Manetta/i-could-have-written-that/workshop_if-if-if-else | workshop excercise: if, if, if, else]]
-==*==
+ [[User:Manetta/i-could-have-written-that/workshop_binary-oppositions | workshop excercise: binary oppositions]]
+<br>
+<br>
+<br>
+------------------------------------
+==process pages==
 [http://pzwart1.wdka.hro.nl/~manetta/i-could-have-written-that/ * static HTML webpage; filesystem interface for research related material] [[User:Manetta/i-could-have-written-that/filesystem-interface-related-material | (+ about the workflow)]]<br>
 [[User:Manetta/i-could-have-written-that/? | * collective archive ?]]<br>
@@ Line 12: / Line 29: @@
 [[User:Manetta/i-could-have-written-that/little-glossary | * little glossary]]<br>
-===editions===
+===zine editions===
 [[User:Manetta/i-could-have-written-that/issue-0.1/ | #0.1: heteromation]]
   (on division of labour between humans & machines)
@@ Line 24: / Line 41: @@
 ====currently working on====
 [[User:Manetta/i-could-have-written-that/from-mining-minerals-to-mining-data | * terminology: data 'mining']]<br>
-[[User:Manetta/i-could-have-written-that/data-mining-in-the-wild | * data mining in the wild, problem formulations]]<br>
+[[User:Manetta/i-could-have-written-that/data-mining-in-the-wild | * ''Knowledge Discovery in Data'' (KDD) in the wild, problem formulations]]<br>
-[[User:Manetta/i-could-have-written-that/knowledge-discovery-workflow | * knowledge discovery workflow]]<br>
+[[User:Manetta/i-could-have-written-that/kdd-applications | * ''KDD'', applications]]<br>
+[[User:Manetta/i-could-have-written-that/knowledge-discovery-workflow | * ''KDD'', workflow]]<br>
 [[User:Manetta/i-could-have-written-that/text-processing/simplification | * text-processing: simplification]]<br>
 [[User:Manetta/i-could-have-written-that/data-mining-parties | * list of data mining parties]]<br>
+====exercises & co ====
+[[User:Manetta/i-could-have-written-that/visual-rhetorical-rap | * visual rhetorical rap - visualizing modality.py's effect on texts]]<br>
+[[User:Manetta/i-could-have-written-that/twitter-truth | * twitter-truth - training a KNN classifier on *live* tweets]]<br>
 ==#0.2 - NLP elements==

User:Manetta/i-could-have-written-that: Difference between revisions