<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>jodischneider.com/blog &#187; information ecosystem</title>
	<atom:link href="http://jodischneider.com/blog/category/information-ecosystem/feed/" rel="self" type="application/rss+xml" />
	<link>http://jodischneider.com/blog</link>
	<description>reading, technology, stray thoughts</description>
	<lastBuildDate>Fri, 23 Jul 2010 15:18:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Quoted in Inside Higher Ed</title>
		<link>http://jodischneider.com/blog/2010/07/17/quoted-in-inside-higher-ed/</link>
		<comments>http://jodischneider.com/blog/2010/07/17/quoted-in-inside-higher-ed/#comments</comments>
		<pubDate>Sat, 17 Jul 2010 19:05:19 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[future of publishing]]></category>
		<category><![CDATA[higher education]]></category>
		<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[scholarly communication]]></category>
		<category><![CDATA[acawiki]]></category>
		<category><![CDATA[Inside Higher Ed]]></category>
		<category><![CDATA[wikis]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=1275</guid>
		<description><![CDATA[Earlier this week, Inside Higher Ed published an article about wikis in higher education. I&#8217;m quoted in connection with my work1 with AcaWiki, which gathers summaries of research papers, books, etc.
The article was publicized with a tweet asking &#8220;Why haven&#8217;t #wikis revolutionized scholarship?&#8221;
Of course, I&#8217;d rather ask &#8220;how have wikis impacted scholarship?&#8221; &#8212; though that&#8217;s less sexy! First, [...]]]></description>
			<content:encoded><![CDATA[<p>Earlier this week, Inside Higher Ed published an <a href="http://www.insidehighered.com/news/2010/07/14/wikis">article about wikis in higher education</a>. I&#8217;m quoted in connection with my work<sup>1</sup> with <a href="http://acawiki.org/">AcaWiki</a>, which gathers summaries of research papers, books, etc.</p>
<p>The article was publicized with a tweet asking &#8220;<a href="http://twitter.com/IHEtech/status/18520449995">Why haven&#8217;t #wikis revolutionized scholarship?</a>&#8221;</p>
<p>Of course, I&#8217;d rather ask &#8220;how have wikis impacted scholarship?&#8221; &#8212; though that&#8217;s less sexy! First, the largest impact is in technological infrastructure: it&#8217;s now commonplace to use collaborative, networked tools with built-in version control. (Though &#8220;wiki&#8221; isn&#8217;t what we&#8217;d use to describe Google Docs nor Etherpad or its many clones). Second, wikis are ubiquitous in research, if you look in the right places. (<a href="http://ncatlab.org/nlab/show/HomePage" target="_self">nLab</a>, <a href="http://openwetware.org/wiki/Main_Page" target="_self">OpenWetWare</a>, and numerous departmental wikis). Third, &#8220;revolutions&#8221; take time, and academia is essentially conservative and slow-moving. For instance, ejournals (~15 years old and counting) are only just starting to depart significantly from the paper form (with multimedia inclusions, storage of data and other, public comments, overlay  journals, post-publication peer-review, etc). Wikis have been used for teaching since roughly 2002<sup>2</sup>, meaning that academic wikis might be only about 8 years old at this point.</p>
<p>Other responses: <a href="http://blogs.ubc.ca/brian/2010/07/viva-la-wiki/">Viva la wiki</a>, says Brian Lamb, who was also interviewed for the article. Daniel Mietchen <a href="http://en.citizendium.org/wiki/User:Daniel_Mietchen/Talks/LSWT_2010/Integrating_wikis_with_scientific_workflows">thinks big about the future of wikis for science</a>.</p>
<p>.</p>
<ol class="footnotes"><li id="footnote_0_1275" class="footnote">I used to be AcaWiki&#8217;s Community Liaison and now contribute summaries and help administer the wiki.</li><li id="footnote_1_1275" class="footnote">see e.g. Bergin, J. (2002). Teaching on the wiki web. In <span style="font-style:italic;">Proceedings of the 7th annual conference on Innovation and technology in computer science education</span> (pp. 195-195). Aarhus, Denmark: ACM. doi:<a href="http://dx.doi.org/10.1145/544414.544473">10.1145/544414.544473</a> and <a href="http://csis.pace.edu/~bergin/jwiki/index.html">related source code</a></li></ol>]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2010/07/17/quoted-in-inside-higher-ed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Book as experience? Or book as storage/retrieval mechanism?</title>
		<link>http://jodischneider.com/blog/2010/06/24/book-as-experience-or-book-as-storageretrieval-mechanism/</link>
		<comments>http://jodischneider.com/blog/2010/06/24/book-as-experience-or-book-as-storageretrieval-mechanism/#comments</comments>
		<pubDate>Thu, 24 Jun 2010 16:16:48 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[books and reading]]></category>
		<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[deep reading]]></category>
		<category><![CDATA[The Shallows]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=1234</guid>
		<description><![CDATA[Here&#8217;s a research question for historians of the book (and maybe book futurists, too):
What&#8217;s the key aspect of the book?

the cognitive experience
information storage and retrieval enabled (e.g. book features such as ToC &#038; indexes within a book itself; reproducibility of &#8216;exact&#8217; copies, wider distribution and ownership of books, ability to have multiple books on the [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a research question for historians of the book (and maybe book futurists, too):</p>
<p>What&#8217;s the key aspect of the book?</p>
<ol>
<li>the cognitive experience</li>
<li>information storage and retrieval enabled (e.g. book features such as ToC &#038; indexes within a book itself; reproducibility of &#8216;exact&#8217; copies, wider distribution and ownership of books, ability to have multiple books on the shelf, etc.)?</li>
</ol>
<p>That arises from Steven Berlin Johnson:</p>
<blockquote><p>[W]as the intellectual revolution post-Gutenberg driven by the mental experience of long-form reading? Or was it driven by the ability to share information asynchronously, and transmit that information easily around the globe? I think it is a mix of the two, but Nick, taking his cues from McLuhan, places almost all of his emphasis on the cognitive effects of deep focus reading. There&#8217;s no real way to prove it, but I think there&#8217;s a very strong case to be made that the information storage-and-retrieval advances made possible by the book were more important to the Enlightenment and the modern age than the contemplative mode of the literary mind. And if that&#8217;s true, then the Web should be seen as a continuation of the Gutenberg galaxy, not a betrayal of it.&#8221;</p></blockquote>
<p>from a post where Steven Berlin Johnson <a href="http://www.stevenberlinjohnson.com/2010/06/more-on-the-shallows.html">summarizes</a> his own New York Times essay <a href="http://www.nytimes.com/2010/06/20/business/20unbox.html?ref=business">Yes, People Still Read, but Now It’s Social</a> responding to Nick Carr&#8217;s book <a href="http://www.theshallowsbook.com/nicholascarr/The_Shallows.html">The Shallows: What the Internet Is Doing to Our Brains</a>. I assume Carr&#8217;s current position to be well-represented by his 2008 article in The Altantic, <a href="http://www.theatlantic.com/magazine/print/2008/07/is-google-making-us-stupid/6868/">Is Google Making Us Stupid? What the Internet Is Doing to Our Brains</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2010/06/24/book-as-experience-or-book-as-storageretrieval-mechanism/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Locative texts</title>
		<link>http://jodischneider.com/blog/2010/06/13/locative-texts/</link>
		<comments>http://jodischneider.com/blog/2010/06/13/locative-texts/#comments</comments>
		<pubDate>Sun, 13 Jun 2010 13:07:50 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[books and reading]]></category>
		<category><![CDATA[future of publishing]]></category>
		<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[ePub]]></category>
		<category><![CDATA[hypertext]]></category>
		<category><![CDATA[interactivity]]></category>
		<category><![CDATA[location-based storytelling]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=1229</guid>
		<description><![CDATA[A post at HLit got me thinking about locative hypertexts, which are meant to be read in a particular place.
Monday, Liza Daly shared an epub demo which pulls in the reader&#8217;s location, and makes decisions about the character&#8217;s actions based on movement. Think of it as a choose-your-own-adventure novel crossed with a geo-aware travel guide. [...]]]></description>
			<content:encoded><![CDATA[<p>A post at HLit got me thinking about <a href="http://htlit.com/archives/June2010/Locative.html">locative hypertexts</a>, which are meant to be read in a particular place.</p>
<p>Monday, Liza Daly <a href="http://blog.threepress.org/2010/06/08/geo-aware-ebook-demo/">shared an epub demo</a> which pulls in the reader&#8217;s location, and makes decisions about the character&#8217;s actions based on movement. Think of it as a choose-your-own-adventure novel crossed with a geo-aware travel guide. It&#8217;s a brief proof-of-concept, and the most exciting part is that the code is free for the taking under the very permissive (GPL + commercial-compatible) MIT License. Thanks, Liza and Threepress for lowering barriers to experimentation with ebooks!</p>
<p>&#8216;Locative hypertexts&#8217; also bring to mind GPS-based guidebooks as envisioned in the 2007 Editus video &#8216;Possible ou probable&#8230;?&#8217;<sup>1</sup>:<br />
<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="500" height="405" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube-nocookie.com/v/huV6kLrwiT8&amp;hl=en_GB&amp;fs=1&amp;rel=0&amp;border=1" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="500" height="405" src="http://www.youtube-nocookie.com/v/huV6kLrwiT8&amp;hl=en_GB&amp;fs=1&amp;rel=0&amp;border=1" allowscriptaccess="always" allowfullscreen="true"></embed></object></a></p>
<p>Tim McCormick <a href="http://postbook.wordpress.com/2009/07/19/the-future-of-the-book-and-the-sorrows-of-web-video/">summarizes</a>:</p>
<blockquote><p>In the 9-minute video, we get mouth-watering, partly tongue-in-cheek scenes of continental Europe’s quality-of-life — fantastic trains &amp; pedestrian streetscapes,independent bookstores, delicious food, world-class museums, weekend getaway to Bruges, etc.– as the movie follows a couple through a riotous few days of E-book high living.</p>
<p>On their fabulously svelte, Kindle 2-like devices, they</p>
<ul>
<li>read and purchase novels</li>
<li>enjoy reading on the beach</li>
<li>get multimedia museum guides</li>
<li>navigate foreign cities with ease</li>
<li>stay in multimedia contact with friends and family</li>
<li>collaborate with colleagues on shared virtual desktops while at sidewalk cafes</li>
<li>see many hi-resolution Breughel paintings online and off that I’m dying to see myself</li>
</ul>
<p>etc.</p></blockquote>
<p>Multimedia guidebooks<sup>2</sup> are approaching this vision. Combine them with (also-existing) turn-by-turn directions, and connectivity and privacy will be the largest remaining obstacles.</p>
<p>So then what about location-based storytelling? I got to thinking about the iPhone apps I&#8217;ve already encountered, which are intended for use in particular places:</p>
<ul>
<li>Walking Cinema: Murder on Beacon Hill &#8211; a murder mystery/travel series based in Boston (available as an iPhone app and podcast).</li>
<li> Museum of the Phantom City: Other Futures &#8211; a multimedia map/alternate history of NYC architecture, described as a way to &#8220;see the city that could have been&#8221;. It maps never-built structures envisioned by Buckminster Fuller, Gaudi, and others &#8211; ideally while you&#8217;re &#8220;standing on the projects&#8217; intended sites&#8221;.</li>
<li>Museum of London: Streetmuseum, true history of London in photos, meant for use on the streets</li>
<li>Historic Earth, has historical maps which could be interesting settings for historical locative storytelling</li>
</ul>
<ol class="footnotes"><li id="footnote_0_1229" class="footnote"><a href="http://www.editis.com/pages_html/video_possible02.htm">Editus&#8217; copy of the video</a></li><li id="footnote_1_1229" class="footnote">e.g. the Lonely Planet city guide series for iPhone</li></ol>]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2010/06/13/locative-texts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Amplify your conference with an iPhone app</title>
		<link>http://jodischneider.com/blog/2010/03/26/amplify-your-conference-with-an-iphone-app/</link>
		<comments>http://jodischneider.com/blog/2010/03/26/amplify-your-conference-with-an-iphone-app/#comments</comments>
		<pubDate>Fri, 26 Mar 2010 16:25:57 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[future of publishing]]></category>
		<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[scholarly communication]]></category>
		<category><![CDATA[amplification]]></category>
		<category><![CDATA[CHI2010]]></category>
		<category><![CDATA[ePub]]></category>
		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[ibisreader]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=1121</guid>
		<description><![CDATA[via Gene Golovchinsky, I learned of an iphone app for CHI2010. What a great way to amplify the conference! Thanks to Justin Weisz and the rest of the CMU crew.
I was happy to browse the proceedings while lounging. The papers I mark show up in my personal schedule and in a reading list. 

I think [...]]]></description>
			<content:encoded><![CDATA[<p>via <a href="http://palblog.fxpal.com/?author=4">Gene Golovchinsky</a>, I <a href="http://palblog.fxpal.com/?p=3247">learned</a> of an <a href="http://jweisz.org/2010/03/15/chi-2010-iphone-app/">iphone app</a> for <a href="http://chi2010.org/">CHI2010</a>. What a great way to amplify the conference! Thanks to <a href="http://jweisz.org/">Justin Weisz</a> and the rest of the CMU crew.</p>
<p>I was happy to browse the proceedings while lounging. The papers I mark show up in my personal schedule and in a reading list. </p>
<p><img src="http://jodischneider.com/blog/wp-content/uploads/2010/03/IMG_0389-e1269619404822.png" alt="Paper view" title="paper" width="250" height="375" class="alignnone size-full wp-image-1122" /><img src="http://jodischneider.com/blog/wp-content/uploads/2010/03/IMG_0393-e1269619292381.png" alt="Personalized conference schedule, generated from my selections" title="program" width="250" height="375" class="alignnone size-full wp-image-1133" /><br />
I think it&#8217;s an attractive alternative to making a paper list by hand, using some conferences&#8217; clunky online scheduling tool, or circling events in large conference handouts. If you keep an iPhone/iPod in your pocket, the app could be used during the conference, but I might also want to print out my sessions on an index card. So exporting the list would be a good enhancement: in addition to printing, I&#8217;d like to send the list of readings directly to <a href="http://www.zotero.org/">Zotero</a> (or another bibliographic manager). </p>
<p>The <a href="http://chi2010.org/attending/advance-program.html">advance program</a> embedded on the conference website still has some advantages: it&#8217;s easier to find out more about session types (e.g. <a href="http://chi2010.org/authors/cfp-altchi.html">alt.chi</a>). Courses and workshops stand out online, too.</p>
<p><img src="http://jodischneider.com/blog/wp-content/uploads/2010/03/IMG_0390-e1269619370281.png" alt="map of conference locations" title="map" width="250" height="375" class="alignnone size-full wp-image-1123" /><img src="http://jodischneider.com/blog/wp-content/uploads/2010/03/IMG_0391-e1269619350138.png" alt="searching the proceedings" title="search" width="250" height="375" class="alignnone size-full wp-image-1124" /></p>
<p>Wayfinding is hard in on-screen PDFs, so I hope that in the long run scholarly proceedings become more screen-friendly. While at present I find an iPhone appealing for reading fiction, on-screen scholarly reading is harder: for one thing, it&#8217;s not linear.</p>
<p>I&#8217;d like to see integrated, reader-friendly environments for conference proceedings, with full-text papers. I envision moving seamlessly between the proceedings and an offline reading environment. Publishers can already support offline reading on a wide variety of smartphones: the HTML5-based <a href="http://ibisreader.com/">Ibis Reader</a> uses <a href="http://en.wikipedia.org/wiki/EPUB">ePub</a>, a standard based on xHTML and CSS. There&#8217;s no getting around the download step, but an integrated environment can be &#8220;download first, choose later&#8221;. I&#8217;ve never had much luck with CD-ROM and USB-based conference proceedings, except in pulling off 2-3 PDFs of papers to read later.</p>
]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2010/03/26/amplify-your-conference-with-an-iphone-app/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How metadata could pay for newspapers</title>
		<link>http://jodischneider.com/blog/2010/02/13/how-metadata-could-pay-for-newspapers/</link>
		<comments>http://jodischneider.com/blog/2010/02/13/how-metadata-could-pay-for-newspapers/#comments</comments>
		<pubDate>Sat, 13 Feb 2010 13:24:28 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[future of publishing]]></category>
		<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[semantic web]]></category>
		<category><![CDATA[future of journalism]]></category>
		<category><![CDATA[future of reporting]]></category>
		<category><![CDATA[journalism]]></category>
		<category><![CDATA[linked data]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[newspapers]]></category>
		<category><![CDATA[structured data]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=1076</guid>
		<description><![CDATA[What if newspapers published not just stories but databases? Dan Conover&#8217;s vision for the future of newspapers  is inspired in part by his first reporting job, for NATO:
When we spotted something interesting, we recorded it in a highly structured way that could be accurately and quickly communicated over a two-way radio, to be transcribed [...]]]></description>
			<content:encoded><![CDATA[<p>What if newspapers published not just stories but databases? Dan Conover&#8217;s <a href="http://xark.typepad.com/my_weblog/2009/05/the-lack-of-vision-thing-well-heres-a-vision-for-you.html">vision for the future of newspapers </a> is inspired in part by his first reporting job, for NATO:</p>
<blockquote><p>When we spotted something interesting, we recorded it in a highly structured way that could be accurately and quickly communicated over a two-way radio, to be transcribed by specialists at our border camp and relayed to intelligence analysts in Brussells.</p></blockquote>
<p>The story, says Conover, is only one aspect of reporting. The other part? Gathering structured metadata, which could be stored in a database&mdash;or expressed as linked data.<sup>1</sup> </p>
<p>Newspapers already have classification systems and <a href="http://www.jennyjenny.org/">professional taxonomists</a>. The New York Times&#8217; classifications system,  in use since 1851, now aggregates stories from the archives in <a href="http://topics.nytimes.com/">Times Topics</a>, a website and API.<sup>2</sup></p>
<p>What if, in addition to these classifications, each story had even more structured metadata?<br />
Capturing metadata ranges from automatic to manual. Some automatic capture is already standard (timestamps) or could be (saving GPS coordinates from a photo or storing timestamps), and some information needing manual capture (like the number of alarms of a fire) is already reported. </p>
<p>Dan compares the &#8220;old way&#8221; with his &#8220;new way&#8221;:</p>
<blockquote><p>
<strong>The old way:</strong><br />
<em><br />
Dan the reporter covers a house fire in 2005. He gives the street address, the date and time, who was victimized, who put it out, how extensive the fire was and what investigators think might have caused it. He files the story, sits with an editor as it&#8217;s reviewed, then goes home. Later, he takes a phone call from another editor. This editor wants to know the value of the property damaged in the fire, but nobody has done that estimate yet, so the editor adds a statement to that effect. The story is published and stored in an electronic archive, where it is searchable by keyword.</em></p>
<p><strong>The new way:</strong><br />
<em><br />
Dan the reporter covers a house fire in 2010. In addition to a street address, he records a six-digit grid coordinate that isn&#8217;t intended for publication. His word-processing program captures the date and time he writes in his story and converts it to a Zulu time signature, which is also appended to the file.</p>
<p>As he records the names of the victimized and the departments involved in putting out the fire, he highlights each first reference for computer comparison. If the proper name he highlights has never been mentioned by the organization, Dan&#8217;s newswriting word processor prompts him to compare the subject to a list of near-matches and either associate the name with an existing digital file or approve the creation of a new one.</p>
<p>When Dan codes the story subject as &#8220;fire,&#8221; his word processor gives him a new series of fields to complete. How many alarms? Official cause? Forest fire (y/n)? Official damage estimate? Addresses of other properties damaged by the fire? And so on. Every answer he can&#8217;t provide is coded &#8220;Pending.&#8221;</p>
<p>Later, Dan sits with an editor as his story is reviewed, but a second editor decides not to call him at home because he sees the answer to the damage-estimate question in the file&#8217;s metadata. The story is published and archived electronically, along with extensive metadata that now exists in a relational database. New information (the name of victims, for instance) automatically generates new files, which are retained by the news organization&#8217;s database but not published.</p>
<p>And those information fields Dan coded as &#8220;Pending?&#8221; Dan and his editors will be prompted to provide that structured information later &#8212; and the prompting will continue until the data set is completed.</em>
</p></blockquote>
<p>- Dan Conover in  <a href="http://xark.typepad.com/my_weblog/2009/05/the-lack-of-vision-thing-well-heres-a-vision-for-you.html">The &#8220;Lack of Vision&#8221; thing? Well, here&#8217;s a hopeful vision for you</a></p>
<p>And that data set? It might even be saleable, even though each individual story had perhaps been given away for free. Dan highlights some possibilities, and entire industries have grown around repackaging free and non-free data (e.g. U.S. Census data, phone book data). I think of mashups such as <a href="http://www.everyblock.com/">Everyblock</a> and hyperlocal news sites like <a href="http://outside.in/">outside.in</a>. </p>
<ol class="footnotes"><li id="footnote_0_1076" class="footnote">Some news organizations, like the New York Times (see <a href="http://data.nytimes.com/">Linked Open Data</a>) and the BBC (<a href="http://www.bbc.co.uk/blogs/bbcinternet/2010/02/case_study_use_of_semantic_web.html">overview</a>, <a href="http://www.bbc.co.uk/blogs/radiolabs/michael_smethurst/">tech blog</a>) are already embracing linked data.</li><li id="footnote_1_1076" class="footnote">I delved into Times Topics&#8217; taxonomy and vocabulary in an <a href="http://jodischneider.com/blog/2008/10/23/nytimes-topics-quirky-useful-classification-finding-aid/">earlier post.</a></li></ol>]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2010/02/13/how-metadata-could-pay-for-newspapers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Salmon Protocol: Comments Swimming Upstream</title>
		<link>http://jodischneider.com/blog/2010/02/03/salmon-protocol-comments-swimming-upstream/</link>
		<comments>http://jodischneider.com/blog/2010/02/03/salmon-protocol-comments-swimming-upstream/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 00:05:28 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[social web]]></category>
		<category><![CDATA[activity streams]]></category>
		<category><![CDATA[aggregation]]></category>
		<category><![CDATA[distributed commenting]]></category>
		<category><![CDATA[distributed sources]]></category>
		<category><![CDATA[Salmon protocol]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=1044</guid>
		<description><![CDATA[Salmon, an aggregation protocol, is championed by Google&#8217;s John Panzer, and described as an &#8220;an open, simple, standards-based solution&#8221; for &#8220;unifying the conversations&#8221;.
&#8216;Conversations&#8217; is deliberately plural, I think, to evoke the many conversations, invisible to one another: &#8220;The comments, ratings, and annotations increasingly happen at the aggregator and are invisible to the original source.&#8221;
Using Salmon, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.salmon-protocol.org/">Salmon</a>, an aggregation protocol, is championed by Google&#8217;s <a href="http://www.abstractioneer.org/">John Panzer</a>, and described as an &#8220;an open, simple, standards-based solution&#8221; for &#8220;unifying the conversations&#8221;.</p>
<p>&#8216;Conversations&#8217; is deliberately plural, I think, to evoke the many conversations, invisible to one another: &#8220;The comments, ratings, and annotations increasingly happen at the aggregator and are invisible to the original source.&#8221;</p>
<p>Using Salmon, an aggregator pushes comments back to a &#8220;Salmon endpoint&#8221; (via POST). These can be published (or moderated) upstream at the original source. See also the <a href="http://www.salmon-protocol.org/salmon-protocol-summary">summary of the Salmon protocol.</a></p>
<p>Comments swimming upstream&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2010/02/03/salmon-protocol-comments-swimming-upstream/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Problems and Opportunities for the Social Web 2010</title>
		<link>http://jodischneider.com/blog/2010/02/03/problems-and-opportunities-for-the-social-web-2010/</link>
		<comments>http://jodischneider.com/blog/2010/02/03/problems-and-opportunities-for-the-social-web-2010/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 00:03:32 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[social web]]></category>
		<category><![CDATA[activity streams]]></category>
		<category><![CDATA[aggregation]]></category>
		<category><![CDATA[mobile web]]></category>
		<category><![CDATA[Salmon protocol]]></category>
		<category><![CDATA[social media]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=1040</guid>
		<description><![CDATA[In a post at ZDNet, Dion Hinchcliffe delineates 7 problems of today&#8217;s social web:


Fragmentation of conversation.
Disconnects between older and newer generations of social media
Lack of control of identity, contacts, and data.
A better social Web on mobile devices.
Poor integration between social media and location services.
Difficulty of coherently engaging in social activity across many channels.
Coping with and [...]]]></description>
			<content:encoded><![CDATA[<p>In a <a href="http://blogs.zdnet.com/Hinchcliffe/?p=1152">post at ZDNet</a>, Dion Hinchcliffe <a href="http://blogs.zdnet.com/Hinchcliffe/?p=1152">delineates 7 problems of today&#8217;s social web:</a></p>
<ol>
<blockquote>
<li>Fragmentation of conversation.</li>
<li>Disconnects between older and newer generations of social media</li>
<li>Lack of control of identity, contacts, and data.</li>
<li>A better social Web on mobile devices.</li>
<li>Poor integration between social media and location services.</li>
<li>Difficulty of coherently engaging in social activity across many channels.</li>
<li>Coping with and getting value from the expanding information volume of social media.</li>
</blockquote>
</ol>
<p>from <a href="http://blogs.zdnet.com/Hinchcliffe/?p=1152">&#8220;The social Web in 2010: The emerging standards and technologies to watch&#8221;</a> encountered via <a href=" http://asc-parc.blogspot.com/2010/01/what-are-big-research-problems-in.html">Ed H. Chi&#8217;s post</a> at the PARC Augmented Social Cognition blog.</p>
<p>The trends? Openness, portability, aggregation of distributed content. Hopefully we&#8217;ll see more on all these fronts in 2010 and beyond. Hinchcliffe also suggests that we want &#8220;Better social and location capabilities added to the core of mobile devices.&#8221;</p>
<p>See the <a href="http://blogs.zdnet.com/Hinchcliffe/?p=1152">full post at ZDNet</a> for more discussion and references to a number of standards, formats, and related developments. In the <a href="http://jodischneider.com/blog/2010/02/03/salmon-protocol-comments-swimming-upstream/">next post</a>, I&#8217;ll highlight <a href="http://www.salmon-protocol.org/">Salmon</a>, a protocol for distributed commenting, which I&#8217;d neither encountered nor heard of.</p>
]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2010/02/03/problems-and-opportunities-for-the-social-web-2010/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Juxtaposition</title>
		<link>http://jodischneider.com/blog/2010/01/28/juxtaposition/</link>
		<comments>http://jodischneider.com/blog/2010/01/28/juxtaposition/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 16:30:38 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[random thoughts]]></category>
		<category><![CDATA[archiving]]></category>
		<category><![CDATA[humor]]></category>
		<category><![CDATA[juxtaposition]]></category>
		<category><![CDATA[streams]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=1031</guid>
		<description><![CDATA[Sometimes it&#8217;s the juxtaposition that amuses me:
Jill Gengler: I love being able to save someone&#8217;s bacon.
Tom Coates: The great slab of fatty pork that I presume to call a brain is almost totally recumbent this morning. Come on piggy! Do some thinking!
We&#8217;re making progress at archiving individual streams, I think. But the overall conversation, &#8220;what [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes it&#8217;s the juxtaposition that amuses me:<br />
<div id="attachment_1032" class="wp-caption alignnone" style="width: 386px"><a href="http://jodischneider.com/blog/wp-content/uploads/2010/01/brains-and-bacon.png"><img class="size-full wp-image-1032" title="brains-and-bacon" src="http://jodischneider.com/blog/wp-content/uploads/2010/01/brains-and-bacon.png" alt="Jill Gengler: I love being able to save someone's bacon. Tom Coates: The great slab of fatty pork that I presume to call a brain is almost totally recumbent this morning. Come on piggy! Do some thinking!" width="376" height="136" /></a><p class="wp-caption-text">Tweetie</p></div></p>
<p>Jill Gengler: <a href="http://twitter.com/jillgengler/status/8326727712">I love being able to save someone&#8217;s bacon.</a></p>
<p>Tom Coates: <a href="http://twitter.com/tomcoates/status/8326615185">The great slab of fatty pork that I presume to call a brain is almost totally recumbent this morning. Come on piggy! Do some thinking!</a></p>
<p>We&#8217;re making progress at archiving individual streams, I think. But the overall conversation, &#8220;what was I seeing then&#8221;, and the links between things? Needs work, at least chez moi!</p>
<p>Updated 2010-04-14 to fix typos. :)</p>
]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2010/01/28/juxtaposition/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scholarly Streams</title>
		<link>http://jodischneider.com/blog/2009/11/10/scholarly-streams/</link>
		<comments>http://jodischneider.com/blog/2009/11/10/scholarly-streams/#comments</comments>
		<pubDate>Tue, 10 Nov 2009 17:18:47 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[scholarly communication]]></category>
		<category><![CDATA[egofeeds]]></category>
		<category><![CDATA[FriendFeed]]></category>
		<category><![CDATA[Kathleen Fitzpatrick]]></category>
		<category><![CDATA[lifestreams]]></category>
		<category><![CDATA[Media Commons]]></category>
		<category><![CDATA[NEH]]></category>
		<category><![CDATA[streams]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=902</guid>
		<description><![CDATA[Streams aren&#8217;t new. Funding for streams, though, that&#8217;s new. 
MediaCommons has just announced funding from the NEH to create &#8220;digital portfolios&#8221;:
&#8220;Given this proliferation, what we need as scholars may be less a system that will manage our communication for us than a system that will allow us to manage our communication, a system than recognizes [...]]]></description>
			<content:encoded><![CDATA[<p>Streams aren&#8217;t new. Funding for streams, though, that&#8217;s new. </p>
<p>MediaCommons has just announced funding from the <a href="http://en.wikipedia.org/wiki/NEH">NEH</a> to create &#8220;digital portfolios&#8221;:<br />
&#8220;Given this proliferation, what we need as scholars may be less a system that will manage our communication for us than a system that will allow us to manage our communication, a system than recognizes that <strong>the key aspect of scholarly communication into the future may be less the distribution of the products of our research than the management of the social networks through which our research is distributed.</strong>&#8221; [emphasis mine]  <a href="http://mediacommons.futureofthebook.org/blog/2009/11/10/mediacommons-digital-scholarly-network-unveiling-profile-system">MediaCommons as Digital Scholarly Network: Unveiling the Profile System</a>. Via <a href="http://twitter.com/kfitz/status/5590046582">@kfitz</a>.</p>
<p>So scholars don&#8217;t have to roll their own,<sup>1</sup> or depend on dubiously-funded startups.<sup>2</sup></p>
<p>While the announcement implies &#8220;less is more&#8221;, Kathleen&#8217;s <a href="http://mediacommons.futureofthebook.org/users/kfitz">sample profile</a> strikes me as a lifestream. Streams themselves are more &#8220;more&#8221; than &#8220;less&#8221;. (&#8216;Firehose&#8217; comes to mind.) So streams alone aren&#8217;t going to solve scholarly communication. But streams can be sliced and diced any number of ways. First the data. Then, if there&#8217;s interest, maybe some services.</p>
<ol class="footnotes"><li id="footnote_0_902" class="footnote">Personally I&#8217;m all for rolling your own. At least in theory. The first lifestream I ever noticed was code4lib&#8217;ber <a href="http://matienzo.org/planet">Mark Matienzo&#8217;s self-hosted planet </a>, which aggregates his blog posts (both personal and work), tweets, youtube uploads, delicious bookmarks, and last.fm scrobbles. Brilliant, but thus far I&#8217;ve been too shy &#038; lazy to follow suit.</li><li id="footnote_1_902" class="footnote">FriendFeed popularized lifestreams. When Facebook bought FriendFeed back in August, my networks of librarians and scientists <a href="http://friendfeed.com/cameronneylon/01cb927a/trouble-with-business-models-facebook-buys">had</a> several discussions <a href="http://friendfeed.com/neilfws/e7a94012/so-there-are-other-lifestream-applications<br />
">of alternatives</a> for <a href="http://friendfeed.com/mndoci/5d892625/friendfeed-facebook-and-scientific">scientists</a> and other <a href="http://friendfeed.com/lsw/670a7489/yes-reports-of-death-friendfeed-have-been">scholars</a>.</li></ol>]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2009/11/10/scholarly-streams/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Google Books settlement: a monopoly waiting to happen</title>
		<link>http://jodischneider.com/blog/2009/10/10/google-books-settlement-a-monopoly-waiting-to-happen/</link>
		<comments>http://jodischneider.com/blog/2009/10/10/google-books-settlement-a-monopoly-waiting-to-happen/#comments</comments>
		<pubDate>Sat, 10 Oct 2009 04:58:17 +0000</pubDate>
		<dc:creator>jodi</dc:creator>
				<category><![CDATA[books and reading]]></category>
		<category><![CDATA[future of publishing]]></category>
		<category><![CDATA[information ecosystem]]></category>
		<category><![CDATA[intellectual freedom]]></category>
		<category><![CDATA[library and information science]]></category>
		<category><![CDATA[digitization]]></category>
		<category><![CDATA[fair use]]></category>
		<category><![CDATA[Google Books]]></category>
		<category><![CDATA[orphan works]]></category>

		<guid isPermaLink="false">http://jodischneider.com/blog/?p=799</guid>
		<description><![CDATA[Will Google Books create a monopoly? Some1 people think2 so.   Brin claims it won&#8217;t:
If Google Books is successful, others will follow. And they will have an easier path: this agreement creates a books rights registry that will encourage rights holders to come forward and will provide a convenient way for other projects to [...]]]></description>
			<content:encoded><![CDATA[<p>Will Google Books create a monopoly? Some<sup>1</sup> people think<sup>2</sup> so.   Brin claims it won&#8217;t:</p>
<blockquote><p>If Google Books is successful, others will follow. And they will have an easier path: this agreement creates a books rights registry that will encourage rights holders to come forward and will provide a convenient way for other projects to obtain permissions.</p></blockquote>
<p>-Sergey Brin, New York Times, <a href="http://www.nytimes.com/2009/10/09/opinion/09brin.html">A Library To Last Forever</a> <span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info:ofi/fmt:kev:mtx:journal&amp;rft.jtitle=New%20York%20Times&#038;<br />
amp;rft.date=10%2F09%2F2009"><!-- This is a COinS: see http://ocoins.info --></span></p>
<p>Brin is wrong: the proposed Google Books settlement will <strong>not</strong> smooth the way for other digitization projects. It creates a red carpet for Google while leaving everyone else at risk of copyright infringement.</p>
<blockquote><p>
The safe harbor provisions apply only to Google.  Anyone else who wants to use one of these books would face the draconian penalties of statutory copyright infringement if it turned out the book was actually still copyrighted.  Even with all this effort, one will not be able to say with certainty that a book is in the public domain.  To do that would require a legislative change &#8211; and not a negotiated settlement.
</p></blockquote>
<p> &#8211; Peter Hirtle, LibraryLawBlog: <a href="http://blog.librarylaw.com/librarylaw/2009/04/the-google-book-settlement-and-the-public-domain.html">The Google Book Settlement and the Public Domain</a>.</p>
<p>Monopoly is not the only risk. Others include<sup>3</sup> <a href="http://go-to-hellman.blogspot.com/2009/08/what-google-books-settlement-agreement.html">reader privacy</a>, <a href="http://blip.tv/file/2471815">access to culture</a>, suitability for bulk and <a href="http://languagelog.ldc.upenn.edu/nll/?p=1701">some research users</a> (metadata, etc.). Too bad Brin isn&#8217;t acknowledging that!</p>
<p>Don&#8217;t know what all the fuss is with Google Books and the proposed settlement? <a href="http://www.wired.com/epicenter/2009/04/the-fight-over-the-worlds-greatest-library-the-wiredcom-faq/">Wired has a good outline from April.</a></p>
<ol class="footnotes"><li id="footnote_0_799" class="footnote">&#8220;Several European nations, including France and Germany, have expressed concern that the proposed settlement gives Google a <strong>monopoly in content</strong>. Since the settlement was the result of a class action against Google,<strong> it applies only to Google. Other companies would not be free to digitise books under the same terms.&#8221;</strong> (bolding mine) &#8211; Nigel Kendall, Times (UK) Online, <a href="http://technology.timesonline.co.uk/tol/news/tech_and_web/article6825134.ece">Google Book Search: why it matters</a><span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info:ofi/fmt:kev:mtx:journal&amp;rft.jtitle=Times%20Online&amp;rft.date=9%2F7%2F2009"><!-- This is a COinS: see http://ocoins.info --></span> </li><li id="footnote_1_799" class="footnote">&#8220;Google&#8217;s five-year head start and its relationships with libraries and publishers give it <strong>an effective monopoly</strong>: No competitor will be able to come after it on the same scale. Nor is technology going to lower the cost of entry. Scanning will always be an expensive, labor-intensive project.&#8221; (bolding mine) &#8211; Geoffrey Nunberg, Chronicle of Higher Education, <a href="http://chronicle.com/article/Googles-Book-Search-A/48245/">Google&#8217;s Book Search: A Disaster for Scholars</a> (pardon the paywall)<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info:ofi/fmt:kev:mtx:journal&amp;rft.jtitle=The%20Chronicle%20of%20Higher%20Education&amp;rft.issn=0009-5982&amp;rft.date=8%2F31%2F2009"><!-- This is a COinS: see http://ocoins.info --></span></li><li id="footnote_2_799" class="footnote">Of course there are lots of benefits, too!</li></ol>]]></content:encoded>
			<wfw:commentRss>http://jodischneider.com/blog/2009/10/10/google-books-settlement-a-monopoly-waiting-to-happen/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
