NRJ

The con­se­quences of this are legion. It means that pro­to­co­log­i­cal analy­sis must focus not on the sci­ences of mean­ing (representation/interpretation/reading), but rather on the sci­ences of pos­si­bil­ity (physics or logic)… (52)

This is from Alex Gal­loway’s Pro­to­col, which I’ve been reread­ing dur­ing the last few days. Galloway’s book is closely related to the project I’m cur­rently work­ing on. The pri­mary dif­fer­ence is that I’m focus­ing on the rela­tion­ship of pro­to­col and stan­dard­iza­tion to writ­ing and rhetoric whereas his argu­ment focused on pro­to­col and stan­dard­iza­tion through the lens of crit­i­cal social theory.

This pas­sage is sig­nif­i­cant in the way that it turns the inter­pre­tive method on its head. For Gal­loway, pro­to­co­log­i­cal (stan­dards) analy­sis explores pos­si­bil­ity rather than under­ly­ing mean­ing. This type of analy­sis explores pos­si­ble worlds that may not yet exist as a type of research, but are enabled through media, or in my favored ter­mi­nol­ogy: infrastructure.

Gal­loway calls this type of research hacking.

Before read­ing this, I’d formed an uncom­fort­able alliance with design study research, some­thing I’m not trained in, but found use­ful because of the its focus on pro­duc­ing pos­si­bil­i­ties rather than inter­pret­ing exist­ing texts. As I’ve worked on my own research, I’ve found it odd that rhetor­i­cal stud­ies hadn’t fre­quently taken the turn to pos­si­bil­i­ties and text pro­duc­tion more enthu­si­as­ti­cally. Rhetoric had his­tor­i­cally at one point been focused on cre­at­ing heuris­tics for pro­duc­ing new texts, not inter­pret­ing old ones. While a few rhetori­cians pur­sue that idea (Kaufer and Butler’s Rhetoric and the Arts of Design for exam­ple) and oth­ers have sug­gested that rhetor­i­cal analy­sis is pri­mar­ily a heuris­tic for pro­duc­tion rather than inter­pre­ta­tion (like in Dilip Gaonkar’s infa­mous attack on the rhetoric of sci­ence), research in rhetor­i­cal stud­ies in the mod­ern uni­ver­sity has largely remained a crit­i­cal act of inter­pre­ta­tion. I’m not sure why that is, per­haps there is more polit­i­cal power in the human­i­ties for being an inter­pre­tive dis­ci­pline rather than pro­duc­tive one. Any­way, I had taken to read­ing design schol­ar­ship because it embraces pro­duc­tion as research rather instead of the inter­pre­tive crit­i­cal approach.

Galloway’s work is moti­vat­ing because he takes the pro­duc­tive per­spec­tive from within media stud­ies, which is more closely aligned with rhetoric than design is, at least in North America.

As back­ground read­ing for a book project, I have been work­ing through Lin­gua Fracta by Collin Gif­ford Brooke. I like this book alot because of its genre: it’s the type of the­o­ret­i­cal work I’ve been writ­ing recently.

One part in par­tic­u­lar has stood out as par­tic­u­larly use­ful so far: Brooke’s dis­cus­sion of rhetor­i­cal ecolo­gies. Brooke describes a rhetor­i­cal ecol­ogy by way of the clas­si­cal rhetor­i­cal canons: inven­tion, arrange­ment, style, mem­ory, deliv­ery. An inven­tion ecol­ogy, for exam­ple, is “a per­sonal sen­si­tiv­ity to the con­di­tions under which inven­tion takes place in my own writ­ing” (44).

It’s his exam­ple of an inven­tional ecol­ogy that drew my attention:

I attend a cou­ple of con­fer­ences per year and each time, start­ing about halfway through the con­fer­ence and extend­ing to as long as a week fol­low­ing my return trip home, I am a par­tic­u­larly pro­duc­tive writer. I sus­pect that many peo­ple share this expe­ri­ence .… When I began blog­ging, I noticed a shift in my per­cep­tions of the world around me.… Over time, the sub­tle oblig­a­tion of the weblog has some­times encour­aged me to write when oth­er­wise I would not” (44).

Although Brooke is writ­ing largely about social con­ven­tions affect­ing the writ­ing process, I couldn’t help but think of a Howard Becker book (Art Worlds) in which he explores the infra­struc­ture of musi­cal con­certs. The typ­i­cal con­cert lasts about three hours and sys­tem­atic depen­den­cies like con­cert labor, park­ing space, and occu­pant spaces become hope­lessly entwined into that 3 hour time period. The odds of being able to run an eight-hour con­cert must work against a slew of pre­con­fig­ured and embed­ded con­ven­tions of prac­tice. The time of the con­cert, once estab­lished, lit­er­ally becomes infra­struc­tured into the social prac­tice of the con­cert. When these con­ven­tions become embed­ded within tech­ni­cal sys­tems, this infra­struc­tur­ing process becomes sig­nif­i­cantly more complex.

Mate­r­ial objects are built because of social con­ven­tion but then push back and solid­ify con­ven­tion (ANT the­o­rists will be yawn­ing at how rudi­men­tary that seems). Get­ting back to Brooke and his book, the thing I find inter­est­ing about rhetor­i­cal ecolo­gies is the infra­struc­ture involved in each. Yes, to some extent rhetor­i­cal ecolo­gies are dynamic, but they also con­sist of infra­struc­tured, mate­r­ial tech­nolo­gies. Just to begin think­ing about blog­ging, it seems that one part of the struc­tured ecol­ogy the HTML form field that is used in many con­tent man­age­ment sys­tems as a way to shut­tle text to the server. The inter­face pro­vides an easy way to write a ton of text, but it resists com­pos­ing with some­thing more like a mind map­ping piece of soft­ware. This is to say that it’s hard to doo­dle with bub­bles in a blog. I need to think a lit­tle bit more about this, but stan­dard­ized com­po­nents pro­vide resis­tance to writ­ing and rhetoric.

This is all just a long way of say­ing that I’m find­ing a lot I like about Brooke’s book. It’s smart, and I see some great places to add infra­struc­tural the­ory to his con­cep­tion of rhetoric.

Mal­one, Cheryl K., and Fer­nando Elichirigoity. “Infor­ma­tion as Com­mod­ity and Eco­nomic Sec­tor: Its Emer­gence in the Dis­course of Indus­trial Clas­si­fi­ca­tion.” Jour­nal of the Amer­i­can Soci­ety for Infor­ma­tion Sci­ence and Tech­nol­ogy 54, no. 6 (2003): 512–520.

I’m a fan of Elichirigoity’s work. His Planet Man­age­ment book is a cre­ative analy­sis of how ocu­lar tech­nol­ogy boot­strapped the con­cept of glob­al­iza­tion. He looks at how tech­niques drawn from sys­tems the­ory helped to gen­er­ate that idea. I draw a lot of inspi­ra­tion from Elichirigoity because he thinks with many of the same the­o­rists I do.

This par­tic­u­lar arti­cle was pub­lished in one of my core jour­nals, and the sub­ject mat­ter is a lit­tle bit closer to what I study: clas­si­fi­ca­tions, stan­dards, and infor­ma­tion infra­struc­ture of the web. I shouldn’t under­sell Cheryl Mal­one, either, who has done some impor­tant research on infor­ma­tion access and pub­lic libraries. I saw Cheryl Mal­one speak at SLIS in 2008 on Eliza Atkins. Mal­one gives lucid, intel­li­gent, and inspir­ing talks. If you’re look­ing for a library his­to­rian to speak, she’s worth get­ting in con­tact with.

This arti­cle is about the adop­tion of the North Amer­i­can Indus­try Clas­si­fi­ca­tion Sys­tem (NAICS). NAICS was cre­ated as a replace­ment for the exist­ing Stan­dard Indus­try Clas­si­fi­ca­tion (SIC) that had been in use in the United States since 1937. NAICS is used by North Amer­i­can gov­ern­ment offi­cials and busi­nesses for gath­er­ing and orga­niz­ing infor­ma­tion on the econ­omy. As an exam­ple, the NAICS is used to col­lect data for the U.S. Eco­nomic Cen­sus that’s given every five years. That data is added to the FactFinder site. This data is used to chart eco­nomic trends and sta­tis­ti­cians and researchers ana­lyze for a vari­ety of purposes.

Mal­one and Elichirigoity show how the NAICS was orga­nized around one cen­tral prin­ci­ple: indus­try would be orga­nized around pro­duc­tion. This isn’t part of their analy­sis, this is just some­thing that the orga­niz­ers aspired to. They saw it as a way to cre­ate a bet­ter clas­si­fi­ca­tion sys­tem (library sci­en­tists would likely give you a dif­fer­ent opinion).

To say this another way, the NAICS was writ­ten so that it could be reduced to one sim­ple rule. To give this idea some legs, con­sider some of the other ways that indus­try could be orga­nized. In the ICS, for exam­ple, some parts of indus­try were orga­nized around ser­vices or busi­ness orga­ni­za­tions. In the ICS, Libraries formed a basic clas­si­fi­ca­tion cat­e­gory. It was listed in ter­mi­nol­ogy con­sis­tent with being an orga­ni­za­tion. In the NAICS, libraries were listed as a sub­cat­e­gory of Infor­ma­tion Ser­vices and Data Pro­cess­ing Ser­vices. In the NAICS, the empha­sis is on the process of work­ing with infor­ma­tion.

Mal­one and Elichirigoity say the clas­si­fi­ca­tion cre­ates a dis­cur­sive for­ma­tion that changes the con­cept of infor­ma­tion and its related economies. They take a Fou­cauldian approach to argue that this cre­ates a new way of know­ing, or regime, of infor­ma­tional eco­nom­ics, one that depends on the orga­niz­ing prin­ci­ple of the NAICS. Because the NAICS is so cen­tral for under­stand­ing large economies, this regime has sig­nif­i­cant con­se­quences for the activ­i­ties being classified.

I like this piece, but not because it’s ground­break­ing or new. It com­bines some old ana­lytic con­cepts from LIS and dis­course analy­sis into one think piece about the North Amer­i­can econ­omy. It’s clear, well-written, and about a topic that seems par­tic­u­larly timely given the cur­rent global eco­nomic sit­u­a­tion. It would be great to see this analy­sis extended to include some con­tem­po­rary data, which wouldn’t be too dif­fi­cult since the cen­sus data is made avail­able to the pub­lic. Also, the authors say that this cre­ates a new regime of infor­ma­tion eco­nom­ics — it would have been awe­some if they pro­vided even a rudi­men­tary cri­tique of how that regime was dif­fer­ent than the pre­vi­ous rather than end­ing with that provocative claim.

Bowker, Geof­frey C. “The His­tory of Infor­ma­tion Infra­struc­tures: The Case of the Inter­na­tional Clas­si­fi­ca­tion of Dis­eases.” Infor­ma­tion Pro­cess­ing & Man­age­ment 32, no. 1 (Jan­u­ary 1996): 49–61.

This arti­cle is a lead up to a few chap­ters that ended up in Bowker and Star’s Sort­ing Things Out. I found my read­ing copy in a book called His­tor­i­cal Stud­ies in Infor­ma­tion Sci­ence.

There are sev­eral pay­offs for read­ing this arti­cle. One is that this is an early piece that shows how Bowker was think­ing about writ­ing his­to­ries of infor­ma­tion infra­struc­ture. Because the arti­cle is in a bit of a pri­mor­dial state, read­ing it helps to see how Bowker was think­ing dur­ing some of his later work.

This arti­cle also describes sev­eral key terms and con­cepts that are enor­mously help­ful for ana­lyz­ing infor­ma­tion infra­struc­ture: imbri­ca­tion, boot­strap­ping, figure/ground, and a short dis­cus­sion of infra­struc­tural inver­sion. “Imbri­ca­tion” is an ana­lytic con­cept that helps to ask­ing ques­tions about his­tor­i­cal data. A good exam­ple from my own work: I’m cur­rently work­ing back­wards through meth­ods of com­puter pro­gram­ming to see which pro­gram­ming con­cepts, clas­si­fi­ca­tions, and tech­niques are passed for­ward to new lan­guages and stan­dards. Com­puter lan­guages (unsur­pris­ingly) bor­row lots from the work that peo­ple have already done. Con­cerns, val­ues, and pol­i­tics of the past are passed for­ward with those concepts.

Boot­strap­ping” is the idea that infra­struc­ture must already exist in order to exist. Another way to say this is that infra­struc­ture forms an impor­tant part of social con­text. To cre­ate an infra­struc­ture as part of social con­text, peo­ple must already be work­ing with the imag­i­nary con­cepts of that con­text. This becomes par­tic­u­larly messy as an infra­struc­ture is used across large spans of time and space, yet its orig­i­nal design is context-dependent and built with the knowl­edge of the cul­tures that insti­gated the project. So to boot­strap is to build the exist­ing assump­tions and pol­i­tics about what infra­struc­ture is use­ful for into infra­struc­ture while real­iz­ing that the design of infra­struc­ture will simul­ta­ne­ously build those assump­tions and pol­i­tics into other times and spaces as the infra­struc­ture is adopted else­where. An exam­ple might be use­ful here. Bowker’s arti­cle deals mostly with the Inter­na­tional Clas­si­fi­ca­tion of Dis­eases (ICD), which has a rich clas­si­fi­ca­tion sys­tem for cat­e­go­riz­ing death. These clas­si­fi­ca­tions reflect the time that they were cre­ated (more peo­ple dying of tuber­cu­lo­sis at the begin­ning of the 20th cen­tury; fewer deaths can be attrib­uted to mul­ti­ple causes) and the pol­i­tics (why exactly does a state want to know that peo­ple are dying in “acci­dents from trans­port, acci­dents in mines and quar­ries, agri­cul­tural and forestry acci­dents, or acci­dents due to machin­ery” and why is it ok to group those together?).

Figure/ground” builds on the idea of boot­strap­ping. It’s a way of think­ing about infra­struc­ture that doesn’t see it solely as the prod­uct of human con­struc­tion or as a con­text shap­ing human activ­ity. Infra­struc­ture is both at the same time. When a clas­si­fi­ca­tion becomes a part of an infra­struc­ture, for exam­ple, it is embed­ded by some­one apply­ing agency.That agent is influ­enced by the larger assump­tions of the larger infra­struc­ture. That is, new clas­si­fi­ca­tions and stan­dards only make sense within the larger ecol­ogy of exist­ing infra­struc­ture. That clas­si­fi­ca­tion then simul­ta­ne­ously becomes part of the ecol­ogy for think­ing about the infra­struc­ture. Fur­ther devel­op­ment of infra­struc­tures will there­after have to fight with the orig­i­nal stan­dards and classifications.

Figure/ground is impor­tant for think­ing broadly about infra­struc­ture. It’s not that some­one can’t remove a clas­si­fi­ca­tion such as “died from tuber­cu­lo­sis,” although this could become dif­fi­cult as well if the stan­dards have become widely mate­ri­ally and socially enforced (think elec­tri­cal power lines, pipe fit­tings, or vot­ing procedures) it’s more that the entire infra­struc­ture was con­cep­tu­ally estab­lished as a whole with that clas­si­fi­ca­tion as a part of it. If you’re famil­iar with the parole/langue idea from Saus­sure, figure/ground is an elab­o­ra­tion that has been fil­tered through infra­struc­tural theory.

Bowker calls the sum of these ana­lytic meth­ods infra­struc­tural inver­sion, a con­cept with con­tributes to a good part of his work.

So noth­ing new for infra­struc­tural the­o­rists, but a good break­down and dis­cus­sion of key con­cepts. The arti­cle serves as primer/recap  for those inter­ested in think­ing the­o­ret­i­cally about infrastructure.

Day, Ronald E. “Death of the User: Recon­cep­tu­al­iz­ing Sub­jects, Objects, and Their Rela­tions.” Jour­nal of the Amer­i­can Soci­ety for Infor­ma­tion Sci­ence and Tech­nol­ogy 62, no. 1 (2011): 78–88.

Ron Day writes for JASIST alot.  His work devel­ops crit­i­cal the­ory in a jour­nal that is largely devoted to empir­i­cal social sci­ence. I have a con­flicted rela­tion­ship with most of his work that ends up in JASIST. Ron is super intel­li­gent, but the gen­eral audi­ence he ends up writ­ing for works from a very dif­fer­ent the­o­ret­i­cal per­spec­tive. This is great on the one hand because it gen­er­ates arti­cles that are acces­si­ble to a num­ber of dif­fer­ing per­spec­tives. But on the other hand, it also leads to some strange pas­sages that seem out of place because they read like direct responses to a peer reviewer–kind of like a short one-on-one Q & A ses­sion in the mid­dle of an arti­cle. Case in point:

… the method of this arti­cle requires expla­na­tion. One charge against it may be that the arti­cle involves intel­lec­tual brico­lage. This is true.

Any­way, this par­tic­u­lar arti­cle ana­lyzes the con­cept of the user in sev­eral the­o­ries cen­tral to Library & Infor­ma­tion Sci­ence, most notably Nick Belkin’s Anom­alous States of Knowl­edge (ASK). My inter­est with this arti­cle had to do with Day’s use of Lacan­ian psy­cho­analy­sis as a way to cri­tique “the infor­ma­tion user.” I’ve been work­ing on a sim­i­lar topic for  under­stand­ing infor­ma­tion architecture.

One of the most impor­tant sec­tions of this essay, at least for LIS, is Day’s expla­na­tion of Lacan­ian theory.

It is not at all the inten­tion of this sec­tion or this arti­cle to pro­pose psy­cho­analy­sis as a new ‘approach’ for empir­i­cal analy­sis, but rather, to exam­ine the con­struc­tion of the sub­ject within psy­cho­analy­sis, par­tic­u­larly, Lacan­ian psy­cho­analy­sis, as a bridge between the LIS user model—based on need—and a fuller and more pre­cise the­o­ret­i­cal, socio­cul­tural model. (82)

It seems to me that resis­tance to crit­i­cal approaches within LIS has often under­stood crit­i­cal the­ory as con­struct­ing empir­i­cal the­ory. This con­fu­sion has drawn cri­tique which argues that the crit­i­cal the­ory is a poor model for empir­i­cal infor­ma­tion behav­ior, and not with­out war­rant. Absolutely!

The issue here is that crit­i­cal the­ory does some­thing very dif­fer­ent than empir­i­cal the­ory. The con­fu­sion of the two approaches in LIS doesn’t seem pro­duc­tive, and it’s nice to see Day clearly say that crit­i­cal the­ory doesn’t nec­es­sar­ily pro­vide a model for empir­i­cal analy­sis. I should point out, that I think this the­o­ret­i­cal con­fu­sion is pri­mar­ily due to the dif­fer­ent the­o­ret­i­cal worlds that var­i­ous LIS schol­ars tend to approach their work with. One of the most use­ful exer­cises I did in grad school was to try and place the work of dif­fer­ent LIS aca­d­e­mics onto a spec­trum of research approaches. Although the exer­cise was nec­es­sar­ily reduc­tive, it was also a use­ful tool for under­stand­ing why peo­ple that seem to dis­agree with each other are dif­fer­ent. (Thanks to both Kristin Eschen­felder and Steve Pal­ing for ask­ing me to do those exer­cises!) Dif­fer­ences in cog­ni­tive frames make dis­ci­pli­nary dis­cus­sion pri­mar­ily dif­fi­cult at the the­o­ret­i­cal level.

One of the great things about this arti­cle is that it is a descrip­tive romp through Lacan­ian psy­cho­an­a­lytic con­cepts, dis­cur­sive psy­chol­ogy, and quasi-objects in the tra­di­tion of Ser­res and Latour. From my point of view, this is great: Day does some pow­er­ful work sum­ma­riz­ing dense con­cepts. The arti­cle isn’t a quick read, but because of its brevity and pub­li­ca­tion venue, it should be acces­si­ble to those who don’t fol­low the the­o­rists that Day describes.

The one thing I’m unsat­is­fied with, though, is that Day doesn’t ever get around to really cri­tiquing the information-seeking mod­els he men­tions. He sug­gests that the other information-seeking mod­els par­tic­i­pate in a folk psy­chol­ogy and mech­a­nis­tic view of infor­ma­tion behav­ior, but that’s the extent of cri­tique. It’s a lit­tle unsat­is­fy­ing to have the infor­ma­tion behav­ior lit­er­a­ture treated as if it is largely the same. (I should say that in a few places Day says that not all infor­ma­tion behav­ior mod­els have the same prob­lems he addresses, but that many do.) Maybe it’s just my per­sonal pref­er­ence as a rhetor­i­cal critic, but I wanted to see more cri­tique of a model like ASK (hope­fully con­tem­po­rary uses of ASK!) after the lengthy the­o­ret­i­cal description.

One rea­son I want to see that type of cri­tique: it seems to me that an infor­ma­tion behav­ior researcher’s eas­i­est appeal would be that they don’t actu­ally use the infor­ma­tion behav­ior mod­els in the way that Day sug­gests. So give them an exam­ple of how they do! (A hedge here: this paper came out of a con­fer­ence panel — per­haps a cri­tique wasn’t added­be­cause there was a very obvi­ous real dis­agree­ment dur­ing the panel. If that is the case, per­haps the peo­ple that Day is writ­ing for don’t need exam­ples of how they are using infor­ma­tion behav­ior mod­els mech­a­nis­ti­cally. Per­haps they were look­ing for a well-written descrip­tion of Day’s POV?) I guess my pri­mary con­cern is for Day to demon­strate that the tar­get of his cri­tique is legit­i­mately a con­tem­po­rary issue.

For my own work, I found his recap of imaginary/symbolic orders, affect, part-objects, and quasi-objects use­ful for fur­ther think­ing about stan­dards, clas­si­fi­ca­tions, and infor­ma­tion infra­struc­ture. Tech­ni­cal stan­dards, stan­dards doc­u­ments, clas­si­fi­ca­tion sys­tems, and the peo­ple inter­act­ing with them can be cri­tiqued with those con­cepts. Some­times it’s nice to have a well-written reminder of dense the­ory. Day does a nice job of that with this article.

UPDATE: Just a few notes after think­ing about this arti­cle a bit more.

Day’s dis­cus­sion about dif­fer­ences between sub­jects and iden­ti­ties is a use­ful dis­cus­sion for enrich­ing infor­ma­tion behav­ior stud­ies. Day puts it bet­ter than I could as he writes that in his under­stand­ing of the world includes  “the expres­sion and emer­gence of bod­ies, par­tic­u­larly sub­jects, as sin­gu­lar­i­ties, and then only later—through the over­lay of rep­re­sen­ta­tional cat­e­gories of recog­ni­tion and even classification—their being named as iden­ti­ties” (79: Check out the pas­sages around that area if you want to know more. It’s a good set of passages.) As far as I know, I hadn’t seen this dif­fer­ence men­tioned in the LIS lit­er­a­ture before. I hope it gets fur­ther explored in user studies.

Day’s con­cept of dou­ble medi­a­tion is also quite good. He describes a way of think­ing about infor­ma­tion behav­ior in terms of two axes. The first is a social/cultural/historical axis. That is, a way of under­stand­ing how a per­son is sit­u­ated within con­texts that afford their abil­ity to act in the world. The sec­ond axis, which I’m still think­ing about, he describes with heavy-handed term affect (I say heavy-handed, because this term has really taken off every­where. It’s hard to keep track of how it’s being used). He uses Deleuze and Guatarri’s writ­ing to talk about affect. By affect, he seems to mean the ways that bod­ies move through and inter­act in phys­i­cal space. The rea­son this part of his dis­cus­sion isn’t quite clear to me is because I’m try­ing to fig­ure out how to con­cep­tu­al­ize both axes together. It’s hard to focus on one axis with­out los­ing focus of the other.

Day describes the ideas he puts forth in this arti­cle as for­mal cau­sa­tion. I know this term has some dis­ci­pli­nary lever­age else­where, but I think that, at least within LIS, it would be use­ful to find a dif­fer­ent term to describe the same idea. For­mal cau­sa­tion, as a term, is a speed bump for me. I have to stop and think about it every time I see it. Because it’s con­cep­tu­ally related to mech­a­nis­tic cau­sa­tion, it also isn’t very cor­dial about the ways that it sug­gests other approaches to schol­ar­ship. There needs to be a bet­ter way to get at the same set of ideas.

One last thought: this arti­cle reminds me a lot of Josh Gunn’s “Refit­ting Fan­tasy” from a 1994 issue of the Quar­terly Jour­nal of Speech. Like Day, much of Gunn’s writ­ing is devoted to sketch­ing out con­cepts for an audi­ence that may be resis­tant to the ideas from Lacan (and in Gunn’s case, Slavoj Žižek). One rea­son that both are good arti­cles is because each author stretches to bring a extradis­ci­pli­nary ideas into the main­stream of their own discipline.