{"id":119,"date":"2005-03-30T12:52:13","date_gmt":"2005-03-30T12:52:13","guid":{"rendered":"\/ifbookblog\/?p=119"},"modified":"2005-03-30T12:52:13","modified_gmt":"2005-03-30T12:52:13","slug":"visions_of_revisions","status":"publish","type":"post","link":"https:\/\/futureofthebook.org\/blog\/2005\/03\/30\/visions_of_revisions\/","title":{"rendered":"visions of revisions"},"content":{"rendered":"<p>What does the evolution of a complex, multi-authored document look like over time? Below are revision histories of two <a href=\"http:\/\/en.wikipedia.org\/wiki\/Main_Page\">Wikipedia<\/a> articles, &#8220;<a href=\"http:\/\/en.wikipedia.org\/wiki\/Brazil\">Brazil<\/a>&#8221; and &#8220;<a href=\"http:\/\/en.wikipedia.org\/wiki\/Love\">love<\/a>,&#8221; as rendered by <a href=\"http:\/\/www.alphaworks.ibm.com\/tech\/historyflow\">History Flow Visualization<\/a>, a new application from <a href=\"http:\/\/www.alphaworks.ibm.com\/\">alphaWorks<\/a>, the emerging technologies division at IBM.<br \/>\n<img loading=\"lazy\" decoding=\"async\" alt=\"brazilwikihistory.jpg\" src=\"\/blog\/archives\/brazilwikihistory.jpg\" width=\"290\" height=\"223\" \/> <img loading=\"lazy\" decoding=\"async\" alt=\"lovewikihistory.jpg\" src=\"\/blog\/archives\/lovewikihistory.jpg\" width=\"290\" height=\"213\" \/><br \/>\nChanges are depicted as parallelograms along two axes, the vertical axis representing the document&#8217;s length, and the horizontal axis representing time. The tool offers &#8220;community&#8221; or single-author views, and uses color to emphasize or isolate specific information &#8211; i.e. to distinguish authors, or to measure age of a contribution. (<a href=\"http:\/\/www.alphaworks.ibm.com\/screenshots\/0JU\/historyflow01.html?opendocument&#038;techid=0JU\">view screenshots<\/a>)<br \/>\nIf you open Wikipedia&#8217;s <a href=\"http:\/\/en.wikipedia.org\/w\/index.php?title=Brazil&#038;action=history&#038;limit=500&#038;offset=0\">revision history<\/a> of the Brazil article, you find a daunting list of hundreds of recorded changes. It&#8217;s hard to get any sense of how this history compares in overall shape, complexity, and pattern of growth to that of <a href=\"http:\/\/en.wikipedia.org\/w\/index.php?title=Love&#038;action=history&#038;limit=500&#038;offset=0\">love<\/a>.   But with the alphaWorks tool, it&#8217;s clear at a glance that the Brazil article almost tripled in size in 2003, and seems to have been suddenly saturated in yellow (perhaps representing the preponderant influence of a single author?). We&#8217;re looking not at a list, but a situation: in 2003, a self-designated authority on Brazil swaggered in and assumed leadership of the country&#8217;s wiki-destiny, whereas love seems to have grown at a fairly constant rate with a pretty consistent mix of contributors &#8211; no swaggering, yellow Brazilians.<br \/>\nI&#8217;d say that the alphaWorks tool suggests something powerful, but is probably of limited use. It&#8217;s good at providing the quick glance, but seems a little too mashed and muddled for line-by-line analysis. Good visualization tools are those that give a sense of the whole but also allow for minute investigation. At their best, they convey information meaningfully, even movingly. Nurturing a complex, multi-authored work is in some ways like raising a child. You mark its height against the wall, take photographs, file away old homework assignments, gather artifacts &#8211; in short, you construct a history, of &#8220;<a href=\"http:\/\/www.bartleby.com\/198\/1.html\">a hundred indecisions..and..a hundred visions and revisions<\/a>.&#8221;<br \/>\n(from <a href=\"http:\/\/science.slashdot.org\/article.pl?sid=05\/03\/28\/054225&#038;from=rss\">Slashdot<\/a> via <a href=\"http:\/\/www.eyebeam.org\/reblog\/archives\/2005\/03\/history_flow_shows_how_wiki_arti.html\">reBlog<\/a>)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>What does the evolution of a complex, multi-authored document look like over time? Below are revision histories of two Wikipedia articles, &#8220;Brazil&#8221; and &#8220;love,&#8221; as rendered by History Flow Visualization, a new application from alphaWorks, the emerging technologies division at IBM. Changes are depicted as parallelograms along two axes, the vertical axis representing the document&#8217;s [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1861],"tags":[],"class_list":["post-119","post","type-post","status-publish","format-standard","hentry","category-the_networked_book"],"_links":{"self":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts\/119","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/comments?post=119"}],"version-history":[{"count":0,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts\/119\/revisions"}],"wp:attachment":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/media?parent=119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/categories?post=119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/tags?post=119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}