View source for A bag but is language nothing of words

(language is nothing but a bag of words)
{{NOTOC}}
<span class="name">[[author::Michael Murtaugh]]</span>
<div class="book">In text indexing and other machine reading applications the term "bag of words" is frequently used to underscore how processing algorithms often represent text using a data structure (word histograms or weighted vectors) where the original order of the words in sentence form is stripped away. While "bag of words" might well serve as a cautionary reminder to programmers of the essential violence perpetrated to a text and a call to critically question the efficacy of methods based on subsequent transformations, the expression's use seems in practice more like a badge of pride or a schoolyard taunt that would go: Hey language: you're nothin' but a big BAG-OF-WORDS.</div>

== Bag of words ==

In information retrieval and other so-called ''machine-reading'' applications (such as text indexing for web search engines) the term "bag of words" is used to underscore how in the course of processing a text the original order of the words in sentence form is stripped away. The resulting representation is then a collection of each unique word used in the text, typically weighted by the number of times the word occurs.

Bag of words, also known as word histograms or weighted term vectors, are a standard part of the data engineer's toolkit. But why such a drastic transformation? The utility of "bag of words" is in how it makes text amenable to code, first in that it's very straightforward to implement the translation from a text document to a bag of words representation. More significantly, this transformation then opens up a wide collection of tools and techniques for further transformation and analysis purposes. For instance, a number of libraries available in the booming field of "data sciences" work with "high dimension" vectors; bag of words is a way to transform a written document into a mathematical vector where each "dimension" corresponds to the (relative) quantity of each unique word. While physically unimaginable and abstract (imagine each of Shakespeare's works as points in a 14 million dimensional space), from a formal mathematical perspective, it's quite a comfortable idea, and many complementary techniques (such as principle component analysis) exist to reduce the resulting complexity.

What's striking about a bag of words representation, given is centrality in so many text retrieval application is its irreversibility. Given a bag of words representation of a text and faced with the task of producing the original text would require in essence the "brain" of a writer to recompose sentences, working with the patience of a devoted cryptogram puzzler to draw from the precise stock of available words. While "bag of words" might well serve as a cautionary reminder to programmers of the essential violence perpetrated to a text and a call to critically question the efficacy of methods based on subsequent transformations, the expressions use seems in practice more like a badge of pride or a schoolyard taunt that would go: Hey language: you're nothing but a big BAG-OF-WORDS. Following this spirit of the term, "bag of words" celebrates a perfunctory step of "breaking" a text into a purer form amenable to computation, to stripping language of its silly redundant repetitions and foolishly contrived stylistic phrasings to reveal a purer inner essence.

== Book of words ==

Lieber's Standard Telegraphic Code, first published in 1896 and republished in various updated editions through the early 1900s, is an example of one of several competing systems of telegraph code books. The idea was for both senders and receivers of telegraph messages to use the books to translate their messages into a sequence of code words which can then be sent for less money as telegraph messages were paid by the word. In the front of the book, a list of examples gives a sampling of how messages like: "Have bought for your account 400 bales of cotton, March delivery, at 8.34" can be conveyed by a telegram with the message "Ciotola, Delaboravi". In each case the reduction of number of transmitted words is highlighted to underscore the efficacy of the method. Like a dictionary or thesaurus, the book is primarily organized around key words, such as ''act'', ''advice'', ''affairs'', ''bags'', ''bail'', and ''bales'', under which exhaustive lists of useful phrases involving the corresponding word are provided in the main pages of the volume. <ref>Benjamin Franklin Lieber, Lieber's Standard Telegraphic Code, 1896, New York; https://archive.org/details/standardtelegrap00liebuoft</ref>

[[File:Liebers P1016847.JPG]]

[[File:Liebers P1016859.JPG]]

[[File:Liebers P1016861.JPG]]

[[File:Liebers P1016869.JPG]]

<blockquote>[...] my focus in this chapter is on the inscription technology that grew parasitically alongside the monopolistic pricing strategies of telegraph companies: telegraph code books. Constructed under the bywords “economy,” “secrecy,” and “simplicity,” telegraph code books matched phrases and words with code letters or numbers. The idea was to use a single code word instead of an entire phrase, thus saving money by serving as an information compression technology. Generally economy won out over secrecy, but in specialized cases, secrecy was also important.<ref>Katherine Hayles, "Technogenesis in Action: Telegraph Code Books and the Place of the Human", How We Think: Digital Media and Contemporary Technogenesis, 2006</ref></blockquote>

In Katherine Hayles' chapter devoted to telegraph code books she observes how:

<blockquote>The interaction between code and language shows a steady movement away from a human-centric view of code toward a machine-centric view, thus anticipating the development of full-fledged machine codes with the digital computer. <ref>Hayles</ref>
</blockquote>

[[File:Liebers P1016851.JPG]]
Aspects of this transitional moment are apparent in a notice included prominently inserted in the Lieber's code book:
<blockquote>After July, 1904, all combinations of letters that do not exceed ten will pass as one cipher word, provided that it is pronounceable, or that it is taken from the following languages: English, French, German, Dutch, Spanish, Portuguese or Latin -- International Telegraphic Conference, July 1903 <ref>Lieber's</ref>
</blockquote>

Conforming to international conventions regulating telegraph communication at that time, the stipulation that code words be actual words drawn from a variety of European languages (many of Lieber's code words are indeed arbitrary Dutch, German, and Spanish words) underscores this particular moment of transition as reference to the human body in the form of "pronounceable" speech from representative languages begins to yield to the inherent potential for arbitrariness in digital representation.

What telegraph code books do is remind us of is the relation of language in general to economy. Whether they may be economies of memory, attention, costs paid to a telecommunicatons company, or in terms of computer processing time or storage space, encoding language or knowledge in any form of writing is a form of shorthand and always involves an interplay with what one expects to perform or "get out" of the resulting encoding.

<blockquote>Along with the invention of telegraphic codes comes a paradox that John Guillory has noted: code can be used both to clarify and occlude. Among the sedimented structures in the technological unconscious is the dream of a universal language. Uniting the world in networks of communication that flashed faster than ever before, telegraphy was particularly suited to the idea that intercultural communication could become almost effortless. In this utopian vision, the effects of continuous reciprocal causality expand to global proportions capable of radically transforming the conditions of human life. That these dreams were never realized seems, in retrospect, inevitable. <ref>Hayles</ref>
</blockquote>

[[File:Liebers P1016884.JPG]]

[[File:Liebers P1016852.JPG]]

[[File:Liebers P1016880.JPG]]

Far from providing a universal system of encoding messages in the English language, Lieber's code is quite clearly designed for the particular needs and conditions of its use. In addition to the phrases ordered by keywords, the book includes a number of tables of terms for specialized use. One table lists a set of words used to describe all possible permutations of numeric grades of coffee (Choliam = 3,4, Choliambos = 3,4,5, Choliba = 4,5, etc.); another table lists pairs of code words to express the respective daily rise or fall of the price of coffee at the port of Le Havre in increments of a quarter of a Franc per 50 kilos ("Chirriado = prices have advanced 1 1/4 francs"). From an archaeological perspective, the Lieber's code book reveals a cross section of the needs and desires of early 20th century business communication between the United States and its trading partners.

The advertisements lining the Liebers Code book further situate its use and that of commercial telegraphy. Among the many advertisements for banking and law services, office equipment, and alcohol are several ads for gun powder and explosives, drilling equipment and metallurgic services all with specific applications to mining. Extending telegraphy's formative role for ship-to-shore and ship-to-ship communication for reasons of safety, commercial telegraphy extended this network of communication to include those parties coordinating the "raw materials" being mined, grown, or otherwise extracted from overseas sources and shipped back for sale.

== "Raw data now!" ==
{{RT|rawdata}}<blockquote><section begin='rawdata' />
<p>
Tim Berners-Lee:
[...] Make a beautiful website, but first give us the unadulterated data, we want the data. We want unadulterated data. OK, we have to ask for raw data now. And I'm going to ask you to practice that, OK? Can you say "raw"?
</p>

<p>Audience: Raw.</p>

<p>Tim Berners-Lee: Can you say "data"?</p>

<p>Audience: Data.</p>

<p>TBL: Can you say "now"?</p>

<p>Audience: Now!</p>

<p>TBL: Alright, "raw data now"! </p>

<p>[...]</p><section end='rawdata' />

<p>So, we're at the stage now where we have to do this -- the people who think it's a great idea. And all the people -- and I think there's a lot of people at TED who do things because -- even though there's not an immediate return on the investment because it will only really pay off when everybody else has done it -- they'll do it because they're the sort of person who just does things which would be good if everybody else did them. OK, so it's called linked data. I want you to make it. I want you to demand it. <ref>Tim Berners-Lee: The next web, TED Talk, February 2009 http://www.ted.com/talks/tim_berners_lee_on_the_next_web/transcript?language=en</ref></p>
</blockquote>

== Un/Structured ==
As graduate students at Stanford, Sergey Brin and Lawrence (Larry) Page had an early interest in producing "structured data" from the "unstructured" web. <ref>"Research on the Web seems to be fashionable these days and I guess I'm no exception." from Brin's [http://infolab.stanford.edu/~sergey/ Stanford webpage]</ref>

<blockquote>
<p>
The World Wide Web provides a vast source of information of almost all types, ranging from DNA databases to resumes to lists of favorite restaurants. However, this information is often scattered among many web servers and hosts, using many different formats. If these chunks of information could be extracted from the World Wide Web and integrated into a structured form, they would form an unprecedented source of information. It would include the largest international directory of people, the largest and most diverse databases of products, the greatest bibliography of academic works, and many other useful resources. [...]
</p>
<p>
'''2.1 The Problem'''<br>
Here we define our problem more formally:<br>
Let D be a large database of unstructured information such as the World Wide Web [...]
<ref>
Extracting Patterns and Relations from the World Wide Web, Sergey Brin,
Proceedings of the WebDB Workshop at EDBT 1998,
http://www-db.stanford.edu/~sergey/extract.ps
</ref>
</p>
</blockquote>

In a paper titled ''Dynamic Data Mining'' Brin and Page situate their research looking for ''rules'' (statistical correlations) between words used in web pages. The "baskets" they mention stem from the origins of "market basket" techniques developed to find correlations between the items recorded in the purchase receipts of supermarket customers. In their case, they deal with web pages rather than shopping baskets, and words instead of purchases. In transitioning to the much larger scale of the web, they describe the usefulness of their research in terms of its computational economy, that is the ability to tackle the scale of the web and still perform using contemporary computing power completing its task in a reasonably short amount of time.

<blockquote>
A traditional algorithm could not compute the large itemsets in the lifetime of the universe. [...] Yet many data sets are difficult to mine because they have many frequently occurring items, complex relationships between the items, and a large number of items per basket. In this paper we experiment with word usage in documents on the World Wide Web (see Section 4.2 for details about this data set). This data set is fundamentally different from a supermarket data set. Each document has roughly 150 distinct words on average, as compared to roughly 10 items for cash register transactions. We restrict ourselves to a subset of about 24 million documents from the web. This set of documents contains over 14 million distinct words, with tens of thousands of them occurring above a reasonable support threshold. Very many sets of these words are highly correlated and occur often. <ref>Dynamic Data Mining: Exploring Large Rule Spaces by Sampling; Sergey Brin and Lawrence Page, 1998; p. 2 http://ilpubs.stanford.edu:8090/424/</ref>
</blockquote>

== Un/Ordered ==

In programming, I've encountered a recurring "problem" that's quite
symptomatic. It goes something like this: you (the programmer) have
managed to cobble out a lovely "content management system" (either from
scratch, or using any number of helpful frameworks) where your user can enter some "items" into a
database, for instance to store bookmarks. After this ordered items are automatically presented in list
form (say on a web page). The author: It's great, except... could
this bookmark come before that one? The problem stems from the fact that
the database ordering (a core functionality provided by any database)
somehow applies a sorting logic that's almost but not quite right. A
typical example is the sorting of names where details (where to place a
name that starts with a Norwegian "Ø" for instance), are
language-specific, and when a mixture of languages occurs, no single
ordering is necessarily "correct". The (often) exascerbated programmer
might hastily add an additional database field so that each item can also have an
"order" (perhaps in the form of a date or some other kind of
(alpha)numerical "sorting" value) to be used to correctly order the
resulting list. Now the author has a means, awkward and indirect but
workable, to control the order of the presented data on the start page.
But one might well ask, why not just edit the resulting listing as a
document? Not possible! Contemporary content management systems are based on a data flow from a "pure" source of a database, through controlling code and templates to produce a document as a result. The document isn't the data, it's the end result of an irreversible process. This problem, in this and many variants, is widespread and
reveals an essential backwardness that a particular "computer scientist"
mindset relating to what constitutes "data" and in particular it's
relationship to order that makes what might be a straightforward
question of editing a document into an over-engineered database.

Recently working with Nikolaos Vogiatzis whose research explores
playful and radically subjective alternatives to the list, Vogiatzis was
struck by how from the earliest specifications of HTML (still valid
today) have separate elements (OL and UL) for "ordered" and "unordered"
lists.

<blockquote>
<p>
The representation of the list is not defined here, but a bulleted
list for unordered lists,  and a sequence of numbered paragraphs
for an ordered list would be quite appropriate. Other possibilities
for interactive display include embedded scrollable browse panels.
<ref>Hypertext Markup Language (HTML): "Internet Draft", Tim
Berners-Lee and Daniel Connolly, June 1993, http://www.w3.org/MarkUp/draft-ietf-iiir-html-01.txt</ref>
</p>

</blockquote>

Vogiatzis' surprise lay in the idea of a list ever being considered
"unordered" (or in opposition to the language used in the specification,
for order to ever be considered "insignificant"). Indeed in its
suggested representation, still followed by modern web browsers, the
only difference between the two visually is that UL items are
preceded by a bullet symbol, while OL items are numbered.

The idea of ordering runs deep in programming practice where essentially different data structures are employed depending on whether order is to be maintained. The indexes of a "hash" table, for instance (also known as an associative array), are ordered in an unpredictable way governed by a representation's particular implementation. This data structure, extremely prevalent in contemporary programming practice sacrifices order to offer other kinds of efficiency (fast text-based retrieval for instance).

== Data mining ==

In announcing Google's impending data center in Mons, Belgian prime minister Di Rupo invoked the link between the history of the mining industry in the region and the present and future interest in "data mining" as practiced by IT companies such as Google.

Whether speaking of bales of cotton, barrels of oil, or bags of words, what links these subjects is the way in which the notion of "raw material" obscures the labor and power structures employed to secure them. "Raw" is always relative: "purity" depends on processes of "refinement" that typically carry social/ecological impact.

Stripping language of order is an act of "disembodiment", detaching it from the acts of writing and reading. The shift from (human) reading to machine reading involves a shift of responsibility from the individual human body to the obscured responsibilities and seemingly inevitable forces of the "machine", be it the machine of a market or the machine of an algorithm.

{{RT|raw_work}}<section begin=raw_work />The computer scientists' view of textual content as "unstructured", be it in a webpage or the OCR scanned pages of a book, reflect a negligence to the processes and labor of writing, editing, design, layout, typesetting, and eventually publishing, collecting and cataloging <ref>http://informationobservatory.info/2015/10/27/google-books-fair-use-or-anti-democratic-preemption/#more-279</ref>.<section end=raw_work />

"Unstructured" to the computer scientist, means non-conformant to particular forms of machine reading. "Structuring" then is a social process by which particular (additional) conventions are agreed upon and employed. Computer scientists often view text through the eyes of their particular reading algorithm, and in the process (voluntarily) blind themselves to the work practices which have produced and maintain these "resources".

Berners-Lee, in chastising his audience of web publishers to not only publish online, but to release "unadulterated" data belies a lack of imagination in considering how language is itself structured and a blindness to the need for more than additional technical standards to connect to existing publishing practices. 

{{Revision}}
[[category:publication]]