User:Kim/writing/Thesis outline draft: Difference between revisions

From XPUB & Lens-Based wiki
Line 33: Line 33:
<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>
<blockquote>Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) <ref>Genette, G. (1997) ''Paratexts: Thresholds of Interpretation'' Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).</ref></blockquote>
===KI 3 = Labor===
===KI 3 = Labor===
labor: holistic- vs prescriptive technologies and division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" enabled division of labor in print production) <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref> resulting in opaque processes and culture of compliance, refer to php key text <ref name=":0" /> and its point about server side writing and invisible labor
labor: holistic- vs prescriptive technologies and division of labor <ref>in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour</ref> (here also: using early markup "pecia system" enabled division of labor in print production) resulting in opaque processes and culture of compliance, refer to php key text <ref name=":0">"<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing</ref> and its point about server side writing and invisible labor


===Key issue 4 = chapter 4 (publishing otherwise) (infrastructures)===
===Key issue 4 = chapter 4===
i feel this chapter should contain more of my own stand point / towards (end) thesis <br>  
i feel this chapter should contain more of my own stand point / towards (end) thesis <br>  
why am i writing about this?
why am i writing about this?
* pushing against fragmentalization of: user / developer, against hidenness / black box of today technology,
* pushing against fragmentalization of: user / developer, against hidenness / black box of today technology,
* accepting notion of hidden, hides non canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref>
* notion of hidden hides non canon histories and voices in technology, hides uncertainty and inconsistency <ref>thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation</ref>
* highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another
* highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another
away from proprietary, bloated platforms and applications. highlight necessity of agency and collective autonomy both in the creation process and over public objects. discuss adjacent tools and attempts (octomode etc). making the hidden visible as possible breaking with closed of/ invisibility discussed in 1 - present git and version control. excurs into history and version control, socio-cultural embededdness of git, present gitpub.<br>
* whats the role of labor in all this?
maybe the last chapter could also have a rather infrastructural focus through which we arrive at the git software and gitpub? what would my take or understanding of infrastructure be in this context? it does relate to paratext in the sense of enabling circulation, it also mediates a relationship/ action, just as infrastructure does
'''publishing otherwise:'''
 
Move away from proprietary, bloated platforms and applications. Highlight the necessity of agency and collective autonomy both in the process of creation and over public objects. Discuss adjacent tools and attempts (octomode etc). Framing my attempt of making the hidden visible as possibility for breaking with closed off objects discussed in chapter 1. Here introduce git and version control: excurs into history and version control, socio-cultural embededdness of git, present gitpub project.
 
or '''Infrastructure:'''<br>
The last chapter could also have a rather infrastructural focus through which we arrive at the git software and gitpub (which would serve as examples for my argument). Infrastructure is commonly perceived as invisible <ref>S. Lee Star asserts that Infrastructures only become visible when they break, a claim that Brian Larkin counters in "Politics and Poetics of Infrastructure" while raising the importance of examining how this apparent ''opacity'' of infrastructures is instrumentailized and why.</ref> what would my take or understanding of infrastructure be in this context? To some extend, it relates to paratext, which enables circulation and mediates a relationship/ action, just as infrastructure does. But infrastructure here must also be seen from a more technical perspective. (wait, am I using the terms ''infrastructure'' and technology ''synonymously'' right now?)
* git is interesting bc it is connected to labor of programming (especially the writing of commit -m) it carries quite a lot of invisibility in itself
* git is interesting bc it is connected to labor of programming (especially the writing of commit -m) it carries quite a lot of invisibility in itself


Revision as of 12:47, 15 October 2025

This outline draft refers to the GitPub project proposal

step 1

1. What do you WANT to write?

[What will the text be about? (thesis). What do you want to explore? Be clear about HOW you want to tell your story.]

I aim to write a text that is concise, yet playful in its form. It will be about the role of meta data [1] [2] in (post) digital publishing practices. I will explore historical developments in the production of text by looking at early forms of markup such as marginalia and the pecia system [3], different digital characteristics for instance source code comments or protocols and will finally propose version control software for (collaborative, experimental) writing and making public. The meta data of the present text is a crucial part of the text and the process of writing itself.

2. Outline (three) key issues you want to explore

  1. hiddeness (veiled, closed source, seamless) in present day technology/ interfaces but also in the sense of invisible labor (in writing, rendering, reading?)
  2. paratexts
  3. labor
  4. how do we publish together but apart from platforms and bloated applications? or
  5. infrastructure (?)

step 2

Intro (what is this text about?)

In this text I will examine the role of meta data [1] [2] in publishing practices through the lense of invisibility and separation of labor. I will look at historical developments in the production of text through early forms of markup such as marginalia and the pecia system [3] and consider different digital characteristics for instance source code comments or protocols

Later I will turn towards specifically including meta data in digital/hybrid publishing projects, not only as means to an end of production but making them part of the text, the body of work at hand.

In the last part of the introduction I will define meta-data (or what ever terminology I come up with for this), and a contextualize my interests in-, and wider relevance of this text.

Key issue 1 = chapter 1 (invisibility)

ambiguity of visibility: its not always be good to be visible / legible (to whom? / whose benefit?)

  1. include "the right to opacity" [4] bc visibility must be understood contextually. could "right to opacity" also have implications for this specific technology / practice of publishing i am discussing?
  2. write about being legible, bc meta data is additional text (for whom?) write about machine readability and indexing / scraping

invisibility of 'software' [5] culture of compliance (resulting from prescriptive technologies) enforcing todays user condition (as opposed to programmer [6] but also as passive, dependent, convenience ... witfully outlined by Silvio Lorusso "User Condition" [7])

also had some ideas about interfaces [8]. invisibility of interface [9], whats their role here?, bc thats how we see (inside) and interact with a computer?

Key issue 2 = chapter 2 (Paratexts)

Paratexts: historically conceptualized for print / literature (include page numbers, headers, pre-and post faces, footnotes and other marginalia ...) - possibilities for digital paratext?, What implications do paratexts hold for present day digital / hybrid publishing? >> "paratext mediates between text and reader", what mediates relation between text and user?

Paratext is, rather, a threshold, (p 2) A Zone not only of transition but also transaction (p 2) [10]

KI 3 = Labor

labor: holistic- vs prescriptive technologies and division of labor [11] (here also: using early markup "pecia system" enabled division of labor in print production) resulting in opaque processes and culture of compliance, refer to php key text [12] and its point about server side writing and invisible labor

Key issue 4 = chapter 4

i feel this chapter should contain more of my own stand point / towards (end) thesis
why am i writing about this?

  • pushing against fragmentalization of: user / developer, against hidenness / black box of today technology,
  • notion of hidden hides non canon histories and voices in technology, hides uncertainty and inconsistency [13]
  • highlighting that writing technologies (print and digital) have contiguous history and are not opposed to another
  • whats the role of labor in all this?

publishing otherwise:

Move away from proprietary, bloated platforms and applications. Highlight the necessity of agency and collective autonomy both in the process of creation and over public objects. Discuss adjacent tools and attempts (octomode etc). Framing my attempt of making the hidden visible as possibility for breaking with closed off objects discussed in chapter 1. Here introduce git and version control: excurs into history and version control, socio-cultural embededdness of git, present gitpub project.

or Infrastructure:
The last chapter could also have a rather infrastructural focus through which we arrive at the git software and gitpub (which would serve as examples for my argument). Infrastructure is commonly perceived as invisible [14] what would my take or understanding of infrastructure be in this context? To some extend, it relates to paratext, which enables circulation and mediates a relationship/ action, just as infrastructure does. But infrastructure here must also be seen from a more technical perspective. (wait, am I using the terms infrastructure and technology synonymously right now?)

  • git is interesting bc it is connected to labor of programming (especially the writing of commit -m) it carries quite a lot of invisibility in itself


the program is part of the writing

making apparent software, process, how we write but also are written by technology

Conclusion

  • meta-data in publishing as a possibility for resisting (invisibility)

References

  1. ↑ 1.0 1.1 or information? this lets me think about how information is formatted data - what exactly am I aiming for in this case?
  2. ↑ 2.0 2.1 but for sure "paratext"
  3. ↑ 3.0 3.1 The Pecia system was developed in the 13th century in the so called Manuscript culture - a time in between oral and print based knowledge production, preservation and circulation. The Pecia system allowed for books to be split in several parts (peciae) which could then be transcribed by several copiers, working simultaneously, producing a copy in a significantly shorter amount of time than a single person working alone. Pecia marks were crucial to this whole process as they allowed for communication between copiers.
  4. ↑ Édouard Glissant called for a “right to opacity” throughout his works "Poetics of Relation", "Philosophy of Relation" and "Caribbean Discourse". I encountered the concept in "Imperfect Solidarities" by Aruna D'Souza, where she describes it as the right to remain intranslatable and unrecorded into western thought.
  5. ↑ Wendy Hui Kyong Chun "On Software, or the persistence of visual knowledge"
  6. ↑ Melanie Hoff "Always Already Programming"
  7. ↑ https://theusercondition.computer/
  8. ↑ Galloway, the interface effect, especially chapter 1: unworkable interface, where he inquires interfaces as windows and doors and general questions of visibility (seamfullness) as much as functionality (un-productiveness, un-workability) of those
  9. ↑ Donald Norman "Why Interfaces dont work"
  10. ↑ Genette, G. (1997) Paratexts: Thresholds of Interpretation Jane E. Lewin. Translated by J.E. Lewin. Cambridge: Cambridge University Press (Literature, Culture, Theory).
  11. ↑ in "Dividing and Sharing" Femke Snelting writes on the division of labor as a consequence of the separation of design from content in web programming (and standardization) https://gitlab.com/km_kt/xp-reader/-/blob/main/SI26/dividing-and-sharing.md?ref_type=heads#divisions-of-labour
  12. ↑ "<?php> - invisible code and the mystique of web writing" in "From A to <A> - Keywords of Markup" https://gitlab.com/km_kt/xp-reader/-/blob/main/browsing/from-a-to-%3Ca%3E.md?ref_type=heads#php---invisible-code-and-the-mystique-of-web-writing
  13. ↑ thinking of Johanna Druckers "Performative Materiality and Theoretical Approches to Interface" in which the author arguments towards interfaces that render visible and affirm acts of interpretation
  14. ↑ S. Lee Star asserts that Infrastructures only become visible when they break, a claim that Brian Larkin counters in "Politics and Poetics of Infrastructure" while raising the importance of examining how this apparent opacity of infrastructures is instrumentailized and why.
Retrieved from "https://pzwiki.wdka.nl/mw-mediadesign/index.php?title=User:Kim/writing/Thesis_outline_draft&oldid=310399"