<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>Comments on: Pledges</title>
	<atom:link href="http://www.scottbot.net/HIAL/?feed=rss2&#038;p=6336" rel="self" type="application/rss+xml" />
	<link>http://www.scottbot.net/HIAL/?p=6336</link>
	<description>data are everywhen</description>
	<lastBuildDate>Sun, 13 Mar 2016 17:49:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.4.2</generator>
	<item>
		<title>By: Scott Weingart</title>
		<link>http://www.scottbot.net/HIAL/?p=6336#comment-396</link>
		<dc:creator><![CDATA[Scott Weingart]]></dc:creator>
		<pubDate>Sat, 17 Dec 2011 12:48:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottbot.net/HIAL/?p=6336#comment-396</guid>
		<description><![CDATA[Thanks! Unfortunately data in the humanities is traditionally not free, although thankfully there has been a recent push to change things.

While I will push for open access of all materials, I certainly don&#039;t plan on being mean about it; I think you can work on them opening their data (except where there are privacy concerns) without alienating them. Also, I tentatively support limited embargoes, where you have the dataset for up to a year before releasing it. It&#039;s not the ideal solution, but it&#039;ll protect people who think their biggest advantage is the fact that they have data that other people don&#039;t.]]></description>
		<content:encoded><![CDATA[<p>Thanks! Unfortunately data in the humanities is traditionally not free, although thankfully there has been a recent push to change things.</p>
<p>While I will push for open access of all materials, I certainly don&#8217;t plan on being mean about it; I think you can work on them opening their data (except where there are privacy concerns) without alienating them. Also, I tentatively support limited embargoes, where you have the dataset for up to a year before releasing it. It&#8217;s not the ideal solution, but it&#8217;ll protect people who think their biggest advantage is the fact that they have data that other people don&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Rudnick</title>
		<link>http://www.scottbot.net/HIAL/?p=6336#comment-390</link>
		<dc:creator><![CDATA[Alex Rudnick]]></dc:creator>
		<pubDate>Sat, 17 Dec 2011 04:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.scottbot.net/HIAL/?p=6336#comment-390</guid>
		<description><![CDATA[It&#039;s a really good pledge! Is data in your field typically publicly available, or is it out of the ordinary to share data and code freely?

I should be braver about this. In my own work with my advisor, we&#039;re all open-code and open-data, all the time. With the Complex Systems folks I&#039;ve been working with, the code isn&#039;t public and I think we&#039;re not allowed to redistribute the data: we pull a large fraction of the traffic from Twitter, as it happens. And I don&#039;t know how much I&#039;d be comfortable demanding, on future papers with them, that they only be in open-access places...]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s a really good pledge! Is data in your field typically publicly available, or is it out of the ordinary to share data and code freely?</p>
<p>I should be braver about this. In my own work with my advisor, we&#8217;re all open-code and open-data, all the time. With the Complex Systems folks I&#8217;ve been working with, the code isn&#8217;t public and I think we&#8217;re not allowed to redistribute the data: we pull a large fraction of the traffic from Twitter, as it happens. And I don&#8217;t know how much I&#8217;d be comfortable demanding, on future papers with them, that they only be in open-access places&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
