<?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> &#187; open access</title>
	<atom:link href="http://yaleisp.org/category/open-access/feed/" rel="self" type="application/rss+xml" />
	<link>http://yaleisp.org</link>
	<description></description>
	<lastBuildDate>Mon, 26 Jul 2010 20:53: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>Gaining Access to ICE&#039;s Varick Detention Center</title>
		<link>http://yaleisp.org/2010/02/gaining-access-to-ices-varick-detention-center/</link>
		<comments>http://yaleisp.org/2010/02/gaining-access-to-ices-varick-detention-center/#comments</comments>
		<pubDate>Sat, 13 Feb 2010 22:41:03 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[Blogosphere]]></category>
		<category><![CDATA[first amendment]]></category>
		<category><![CDATA[lamp]]></category>
		<category><![CDATA[open access]]></category>

		<guid isPermaLink="false">http://lamponline.org/?p=318</guid>
		<description><![CDATA[Just wanted to flag a MFIA victory &#8211; journalist Jacqueline Stevens, who writes for the Nation, will be given a tour of the Varick Detention Center in NYC next week (ICE had denied her previous requests for access). Approval came a day after the ACLU and the New York Civil Liberties Union sent a letter to [...]]]></description>
			<content:encoded><![CDATA[<p>Just wanted to flag a MFIA victory &#8211; journalist Jacqueline Stevens, who writes for the <a href="http://www.thenation.com/">Nation</a>, will be given a tour of the Varick Detention Center in NYC next week (<a href="http://www.ice.gov/">ICE</a> had denied her previous requests for access). Approval came a day after the <a href="http://www.aclu.org/">ACLU</a> and the <a href="http://www.nyclu.org/">New York Civil Liberties Union</a> sent a letter to ICE on behalf of the Nation, the <a href="http://www.nationinstitute.org/">Nation Institute</a>, and Ms. Stevens, requesting that Ms. Stevens be granted access to the center in accordance with ICE&#8217;s own regulations and First Amendment access principles. We here at the MFIA practicum helped gather the information and write the letter, so we&#8217;re all very excited about the recent developments.</p>
<p>This is an important step in better understanding what goes on in detention centers around the country. Check out more details <a href="http://stateswithoutnations.blogspot.com/2010/02/aclu-demands-varick-jail-tour-for.html">here</a> on Ms. Stevens&#8217; blog.</p>
]]></content:encoded>
			<wfw:commentRss>http://yaleisp.org/2010/02/gaining-access-to-ices-varick-detention-center/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FOI Fee Fraud?</title>
		<link>http://yaleisp.org/2010/02/foi-fee-fraud/</link>
		<comments>http://yaleisp.org/2010/02/foi-fee-fraud/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 20:17:07 +0000</pubDate>
		<dc:creator>Adri</dc:creator>
				<category><![CDATA[lamp]]></category>
		<category><![CDATA[open access]]></category>

		<guid isPermaLink="false">http://lamponline.org/?p=313</guid>
		<description><![CDATA[The Globe has an interesting article up about the prohibitive costs of government records requests. 
According to the story, one Boston reporter was given
an estimate of $6,600 by a large state agency in response to his requests to review the e-mails of several senior officials. The agency justified the price as the cost of finding the [...]]]></description>
			<content:encoded><![CDATA[<p>The Globe has an <a href="http://www.boston.com/news/local/massachusetts/articles/2009/09/24/municipalities_often_set_high_price_for_public_records/?page=2">interesting article</a> up about the prohibitive costs of government records requests. </p>
<p>According to the story, one Boston reporter was given</p>
<blockquote><p><em>an estimate of $6,600 by a large state agency in response to his requests to review the e-mails of several senior officials. The agency justified the price as the cost of finding the documents, printing them, and reviewing them for personal information that might be exempt from the public records law.</em></p></blockquote>
<p>What&#8217;s the real purpose for these fees? Is it to recoup the cost of redaction, search, and print? It seems like it would be pretty easy to get around the print / redaction fees, at the very least, by providing the records in electronic format &#8212; if I were to be pushing for a legislative fix of an open records law, it would be to mandate electronic format whenever the record is available in digital form (as an email most certainly is) and requested in that format. Well, that and actual enforcement mechanisms.</p>
<p>But there&#8217;s no way that printing costs by themselves amount to over $6 thou; on its face, this looks more like brazen disregard for the purpose of the open records law. Perhaps another solution would be to require an itemized receipt &#8211; if. there&#8217;s some inefficiency driving up the costs of FOI, the requestor &#8211; and the public at large &#8211; should know about it</p>
<p>The article also brings up a point of general concern in the open records world, which is the increasing shift of the burden of the search onto the requestor. More and more, agencies are demanding that requestors &#8220;perfect&#8221; their requests by identifying the databases in which the records they seek are stored, or  specifying the format (memorandum, report, correspondence) in which particular information is held. While the cost of searching government logs is not to be disregarded, we do have these things called computer keyword searches &#8230; and the solution certainly is not to create the circuitous situation in which the agency denies a  request because of the lack of specific information in the public sphere.</p>
]]></content:encoded>
			<wfw:commentRss>http://yaleisp.org/2010/02/foi-fee-fraud/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Networking and Information Sharing</title>
		<link>http://yaleisp.org/2010/02/networking-and-information-sharing/</link>
		<comments>http://yaleisp.org/2010/02/networking-and-information-sharing/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 18:58:35 +0000</pubDate>
		<dc:creator>betsycooper</dc:creator>
				<category><![CDATA[lamp]]></category>
		<category><![CDATA[open access]]></category>

		<guid isPermaLink="false">http://lamponline.org/?p=308</guid>
		<description><![CDATA[Hello from Betsy, new ISP fellow and blogger.
Perhaps this is old news, but I found this fascinating. A new Boston University study shows that the people with the largest social networks are not necessarily the best idea spreaders. Instead, the best ideas spreaders are those at strategically placed nodes, even if they are less well [...]]]></description>
			<content:encoded><![CDATA[<p>Hello from Betsy, new ISP fellow and blogger.</p>
<p>Perhaps this is old news, but I found this fascinating. A new Boston University study shows that the people with the largest social networks are not necessarily the best idea spreaders. Instead, the best ideas spreaders are those at strategically placed nodes, even if they are less well connected: <a href="http://www.technologyreview.com/blog/arxiv/24748/?ref=rss&amp;a=f">http://www.technologyreview.com/blog/arxiv/24748/?ref=rss&amp;a=f</a>.<br />
 <br />
This seems to suggest that people at nodes accessing diverse networks may be better equipped to spread information than those well connected within a single network. Does this redefine the &#8216;key players&#8217; for information-sharing, or how best to target advertising? Does it suggest yet another reason to value diversity in networks? Food for thought.</p>
]]></content:encoded>
			<wfw:commentRss>http://yaleisp.org/2010/02/networking-and-information-sharing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ISP Fellow Comments on the OSTP’s Public Access Policies for Science and Technology Funding Agencies – Post 3</title>
		<link>http://yaleisp.org/2010/01/isp-fellow-comments-comments-on-the-ostp%e2%80%99s-public-access-policies-for-science-and-technology-funding-agencies-%e2%80%93-post-3/</link>
		<comments>http://yaleisp.org/2010/01/isp-fellow-comments-comments-on-the-ostp%e2%80%99s-public-access-policies-for-science-and-technology-funding-agencies-%e2%80%93-post-3/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 20:21:12 +0000</pubDate>
		<dc:creator>vcstodden</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[open access]]></category>

		<guid isPermaLink="false">http://yaleisp.org/?p=746</guid>
		<description><![CDATA[The following comments were posted by ISP Fellow Victoria Stodden in response to the OSTP’s call, as announced here: http://www.ostp.gov/galleries/default-file/RFI%20Final%20for%20FR.pdf. The first wave, comments posted here, asked for feedback on implementation issues. The second wave requested input on Features and Technology (our post is here). For the third and final wave on Management, Chris Wiggins, [...]]]></description>
			<content:encoded><![CDATA[<p>The following comments were posted by ISP Fellow <a href=http://www.stodden.net>Victoria Stodden</a> in response to the OSTP’s call, as announced here: <a href=http://www.ostp.gov/galleries/default-file/RFI%20Final%20for%20FR.pdf>http://www.ostp.gov/galleries/default-file/RFI%20Final%20for%20FR.pdf</a>. The <a href=http://blog.ostp.gov/2009/12/10/policy-forum-on-public-access-to-federally-funded-research-implementation/>first wave</a>, comments posted <a http://blog.stodden.net/2009/12/21/the-ostps-call-for-comments-regarding-public-access-policies-for-science-and-technology-funding-agencies-across-the-federal-government/>here</a>, asked for feedback on implementation issues. The <a href=http://blog.ostp.gov/2009/12/21/policy-forum-on-public-access-to-federally-funded-research-features-and-technology>second wave</a> requested input on Features and Technology (our post is <a href=http://blog.stodden.net/2009/12/28/post-2-the-ostp%E2%80%99s-call-for-comments-regarding-public-access-policies-for-science-and-technology-funding-agencies-across-the-federal-government>here</a>). For the <a href=http://blog.ostp.gov/2010/01/01/policy-forum-on-public-access-to-federally-funded-research-management>third and final wave</a> on Management, Chris Wiggins, Matt Knepley, and I posted the following comments: </p>
<p> Q1: <i>Compliance. What features does a public access policy need to ensure compliance? Should this vary across agencies?</i></p>
<p></p>
<p>One size does not fit all research problems across all research communities, and a heavy-handed general release requirement across agencies could result in de jure compliance – release of data and code as per the letter of the law – without the extra effort necessary to create usable data and code facilitating reproducibility (and extension) of the results. One solution to this barrier would be to require grant applicants to formulate plans for release of the code and data generated through their research proposal, if funded. This creates a natural mechanism by which grantees (and peer reviewers), who best know their own research environments and community norms, contribute complete strategies for release. This would allow federal funding agencies to gather data on needs for release (repositories, further support, etc.); understand which research problem characteristics engender which particular solutions, which solutions are most appropriate in which settings, and uncover as-yet unrecognized problems particular researchers may encounter. These data would permit federal funding agencies to craft release requirements that are more sensitive to barriers researchers face and the demands of their particular research problems, and implement strategies for enforcement of these requirements. This approach also permits researchers to address confidentiality and privacy issues associated with their research. </p>
<p>
Examples:</p>
<p></p>
<p>    One exemplary precedent by a UK funding agency is the January 2007 &#8220;Policy on data management and sharing&#8221;<br />
(<a href="http://bit.ly/74pXhT">http://www.wellcome.ac.uk/About-us/Policy/Policy-and-position-statements/WTX035043.htm</a>)<br />
adopted by The Wellcome Trust (<a href="http://bit.ly/wRu9b">http://www.wellcome.ac.uk/About-us/index.htm</a>) according to which &#8220;the Trust will require that the applicants provide a data management and sharing plan as part of their application; and review these data management and sharing plans, including any costs involved in delivering them, as an integral part of the funding decision.&#8221; A comparable policy statement by US agencies would be quite useful in clarifying OSTP&#8217;s intent regarding the relationship between publicly-supported research and public access to the research products generated by this support. </p>
<p>
<span id="more-746"></span><br />
</p>
<p>    An exemplary precedent by a US funding agency is that of NSF&#8217;s &#8220;broader impact criterion&#8221; (cf. <a href="http://bit.ly/wRu9b">http://www.ndsciencehumanitiespolicy.org/workshop/</a> for an links to extensive discussions on history and examples of what qualifies as evidence of broad impact). Such an existing requirement could allow, encourage, or require data and code sharing plans as possible examples of broader impact.</p>
<p></p>
<p>    A second exemplary precedent by a US funding agency is that of NIH&#8217;s development of <a href="http://bit.ly/51tyAI">PubMed Central</a>. Submission of manuscripts resulting from NIH support is now mandatory (cf. <a href="http://bit.ly/5dy1ic">http://grants.nih.gov/grants/guide/notice-files/NOT-OD-08-033.html</a>). NIH or other agencies might consider developing a similar repository for code, data, or (even better) full compendia (manuscript, data, and code together) of computational research, and possibly requiring use of this reliable, searchable, open repository for future federal funding. By creating and requiring an open access repository for manuscripts, NIH has avoided the possibility that research results can only be accessed by libraries able to pay the increasing costs of subscriptions to closed-access journals.</p>
<p></p>
<p>
<p>    Q2: <i>Evaluation. How should an agency determine whether a public access policy is successful? What measures could agencies use to gauge whether there is increased return on federal investment gained by expanded access?</i></p>
<p></p>
<p>One simple gauge is the proportion of funded projects, by field and by agency, which are in compliance. Compliance could be easily measured: whether the research compendia have been made available according to agency policy and the details of the particular grant funding the researcher. When the work is computational, funding agencies could consider implementation of the Reproducible Research Standard (cf. V. Stodden &#8220;Enabling Reproducible Research: Licensing For Scientific Innovation&#8221; at <a href="http://bit.ly/RC7lx">http://www.ijclp.net/issue_13.html</a>) to untangle intellectual property rights associated with research release and clarify requirements.</p>
<p></p>
<p>    The Reproducible Research Standard (RRS) realigns the Intellectual Property framework faced by computational researchers with longstanding scientific norms. The RRS suggests a licensing structure for research compendia, including code and data, that permits others to use and re-use code and data without having to obtain prior permission or assume a Fair Use exception to copyright, so long as attribution is given. The RRS utilizes existing open licenses that permit the free use of licensed work, so long as attribution is given, and is satisfied if the following four conditions hold:</p>
<p></p>
<p>1. The full research compendium, including code and data, is available on the Internet,<br />
<br />
2. The media components such as text or figures, (including original selection and arrangement of the data), are licensed under the Creative Commons Attribution License 3.0 or released to the public domain under CC0,<br />
<br />
3. The code components are licensed under one of Apache 2.0, the MIT License, or the Modified BSD license, or released to the public domain under CC0,<br />
<br />
4. The data have been released into the public domain under CC0 or according to the Science Commons Open Data Protocol.<br />
</p>
<p>Using the RRS on all components of computational scholarship will encourage reproducible scientific investigation, facilitate greater collaboration, and promote engagement of the larger community in scientific learning and discovery.</p>
<p></p>
<p>Moreover, in evaluating compliance, we would also want to encompass the ability to build, run, and verify any source code. This might be accomplished using<br />
    <br />* spot checks of the repository<br />
    <br />* automated checks akin to unit tests<br />
    <br />* tests run by a separate reviewer at the time of inclusion</p>
<p></p>
<p>
<p>    Q3: <i>Roles. How might a public private partnership promote robust management of a public access policy? Are there examples already in use that may serve as models? What is the best role for the Federal government?</i></p>
<p></p>
<p>Two notable examples of public-private partnership which have benefited science are <a href="http://bit.ly/12MYix">http://arxiv.org</a>, which is partially NSF-supported, and <a href="http://bit.ly/16Imki">http://PDB.org</a>, funded by a number of (public and private) sources. PDB in particular has for more than a decade been an integral part of the funding and publication policies in the structural biology community (cf. <a href="http://bit.ly/5wzxeH">http://www.nature.com/nsmb/wilma/v5n3.892130820.html</a>).</p>
<p></p>
<p>That said, previous experimentation with private management of scientific works has been problematic in at least one case. In December 2008 Google shut down http://researchdatasets.google.com &#8211; a repository for research data (cf. <a href="http://bit.ly/7U10NJ">http://www.wired.com/wiredscience/2008/12/googlescienceda/</a>). Private interests are not aligned with those of the scientific community, and there must be a public role in the preservation of this aspect of our culture. Moreover, reliance on private resources comes with venerability to changing missions of or solvency of these private and/or corporate partners. The principle of Open Access recognizes that such collections should be considered valuable stewards of our culture just as the Library of Congress and the National Archives. Rewards for the availability of scientific compendia &#8212; papers, data, and code &#8212; come not only through views and downloads, but through the acceleration of scientific research, technological development, and an increase in scientific integrity.</p>
<p></p>
<p>Possible roles for the federal government include:<br />
<br />* facilitating and supporting an open an sustainable database comparable to the PDB for research compendia (manuscripts, data, and code)<br />
<br />* encouraging funding agencies to draft clear statements encouraging reproducibility (e.g., distribution of compendia) and public access to research results (e.g., submission to open access journals or arxiv.org)<br />
<br />* clarification of the relationship between copyright and open access (a topic currently under debate in the form of competing proposed congressional bills, cf.<br />
<a href="http://bit.ly/5Ehyj6">http://www.publishers.org/main/PressCenter/Archicves/2009_Feb/02_FairCopyright.htm</a> and<br />
<a href="http://bit.ly/8QvNU0">http://www.taxpayeraccess.org/issues/access/access_supporters/</a> for background)<br />
<br />* clarification of the relationship between broad impact of publicly-funded research (and public access to the output of this federal support) versus university-specific IP policies (e.g., governing code and data even where generated by publicly-funded research), which often act as a disincentive to sharing the results of federally-funded research.</p>
<p>
<p>
Victoria Stodden<BR><br />
Yale Law School, New Haven, CT<BR><br />
Science Commons, Cambridge, MA<BR><br />
<a href="http://bit.ly/4Uq6DT">http://www.stanford.edu/~vcs</a></p>
<p>
<p>
Chris Wiggins<BR><br />
Columbia University, New York, NY<BR><br />
<a href="http://bit.ly/4Uq6DT">http://www.columbia.edu/~chw2</a></p>
<p>
<p>
Matthew G. Knepley<BR><br />
University of Chicago, Chicago, IL<BR><br />
<a href="http://bit.ly/4oEU1V">http://www.cs.uchicago.edu/~knepley</a></p>
<p>
<p><b>References</b> These issues were discussed at a roundtable convened by one of the authors on research sharing issues held at Yale Law School on November 21, 2009.  The webpage, along with thought pieces and research materials, is located at <a href="http://bit.ly/5L6mTh">http://www.stanford.edu/~vcs/Conferences/RoundtableNov212009/</a>.</p>
<p>
<p>Crossposted to the <a href=http://blog.ostp.gov/2010/01/01/policy-forum-on-public-access-to-federally-funded-research-management/comment-page-2/#comment-10974>OSTP blog</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://yaleisp.org/2010/01/isp-fellow-comments-comments-on-the-ostp%e2%80%99s-public-access-policies-for-science-and-technology-funding-agencies-%e2%80%93-post-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>what we do and why terrorism matters</title>
		<link>http://yaleisp.org/2009/10/what-we-do-and-why-terrorism-matters/</link>
		<comments>http://yaleisp.org/2009/10/what-we-do-and-why-terrorism-matters/#comments</comments>
		<pubDate>Tue, 13 Oct 2009 00:34:12 +0000</pubDate>
		<dc:creator>Nabiha</dc:creator>
				<category><![CDATA[first amendment]]></category>
		<category><![CDATA[lamp]]></category>
		<category><![CDATA[open access]]></category>

		<guid isPermaLink="false">http://lamponline.org/?p=112</guid>
		<description><![CDATA[Our projects include a lot of national security-oriented topics, including Guantanamo, fusion centers, and the like. One might wonder &#8212; hell, we&#8217;ve wondered &#8212; how this intersects with our core mission to support newsgatherers. In an Information Society Project Ideas Lunch last week, Jack Balkin hit the nail on the head: the current onslaught of [...]]]></description>
			<content:encoded><![CDATA[<p>Our projects include a lot of national security-oriented topics, including Guantanamo, fusion centers, and the like. One might wonder &#8212; hell, <em>we&#8217;ve</em> wondered &#8212; how this intersects with our core mission to support newsgatherers. In an <a href="http://yaleisp.org/">Information Society Project</a> Ideas Lunch last week, <a href="http://balkin.blogspot.com/">Jack Balkin</a> hit the nail on the head: the current onslaught of secrecy, under the guise of national security, is just the most recent incarnation of the desire to suppress open information. Our projects will fluctuate to respond to the realities of the day. Right now, it just so happens that terrorism is a popular excuse for keeping information under wraps, and as such, inaccessible to the newsgatherers who want to write about it.</p>
<p>On that note, I was thrilled to find <a href="http://www.coe.int/t/dghl/standardsetting/media/Doc/SpeakingOfTerror_en.pdf">this report</a> on the <a title="Centre for Freedom of Media" href="http://www.cfom.org.uk" target="_blank">Centre for the Freedom of the Media</a> website. The Speaking of Terror report, drafted for the Council of Europe, outlines anti-terror laws have stifled freedom of expression and media operation in Europe. Anyone know of anything similar written about the United States? I&#8217;d love to read it.</p>
]]></content:encoded>
			<wfw:commentRss>http://yaleisp.org/2009/10/what-we-do-and-why-terrorism-matters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Can Judicial Openness Initiatives Disqualify Judges from Access Cases?</title>
		<link>http://yaleisp.org/2009/10/can-judicial-openness-initiatives-disqualify-judges-from-access-cases/</link>
		<comments>http://yaleisp.org/2009/10/can-judicial-openness-initiatives-disqualify-judges-from-access-cases/#comments</comments>
		<pubDate>Sat, 10 Oct 2009 15:49:59 +0000</pubDate>
		<dc:creator>Patrick Kabat</dc:creator>
				<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[cases]]></category>
		<category><![CDATA[first amendment]]></category>
		<category><![CDATA[lamp]]></category>
		<category><![CDATA[open access]]></category>
		<category><![CDATA[secret dockets]]></category>

		<guid isPermaLink="false">http://lamponline.org/?p=106</guid>
		<description><![CDATA[The Supreme Court has refused to indulge a stay sought by the Bridgeport Roman Catholic Diocesan Corporation which would have kept 12,000 pages of court records and depositions in a long-running CT clergy abuse case from public view.
The judgment sought to be stayed, Rosado v. Bridgeport Roman Catholic Diocesan Corp., raises some fascinating access issues, [...]]]></description>
			<content:encoded><![CDATA[<p>The Supreme Court has <a href="http://www.supremecourtus.gov/orders/courtorders/100509zor.pdf">refused to indulge a stay</a> sought by the Bridgeport Roman Catholic Diocesan Corporation which would have kept 12,000 pages of court records and depositions in a long-running CT clergy abuse case from public view.</p>
<p>The judgment sought to be stayed, <a href="http://www.jud.ct.gov/external/supapp/Cases/AROcr/CR292/292CR90.pdf"><em>Rosado v. Bridgeport Roman Catholic Diocesan Corp.,</em></a> raises some fascinating access issues, including an institutional-reform question which I haven&#8217;t seen elsewhere.  Does a judge&#8217;s participation on an open access task force mandate recusal by creating an appearance of impropriety in deciding open access questions?</p>
<p>Here, the Connecticut Supreme Court held that the trial judge&#8217;s failure to recuse himself in <em>Rosado</em>, despite his involvement with the Judicial Branch&#8217;s Public Access Task Force, did not amount to abuse of discretion:</p>
<p style="text-align: left;">&#8220;A trial judge has no affirmative duty to step down from a case merely on the basis of membership on a task force unless the agenda of the task force is inconsistent with the judge’s duty to judge impartially. Case law confirms that service on a commission concerned with improving the legal system and the administration of justice, without more, is not a basis for disqualification, even if the subject matter generally relates to the area of the law at issue in the case at hand.&#8221;</p>
<p>Good call, CT. An adverse ruling on this issue would certainly chill bench-led openness efforts. In this case, the precedent appears extensive and clear, but Justice Sullivan&#8217;s spirited <a href="http://www.jud.ct.gov/external/supapp/Cases/AROcr/CR292/292CR90E.pdf">dissent </a>demonstrates how the &#8220;appearance of impropriety&#8221; standard can be stretched to embrace reform initiatives.  Several features of the task force&#8217;s design were extremely important to the majority ruling, including instructions to consider privacy interests as well as disclosure interests.  Take note, other states seeking to institute openness initiatives, lest you design a task force which might jeopardize judges&#8217; ability to hear access cases.</p>
<p>The next steps, as the New York Times <a href="http://www.nytimes.com/2009/10/06/nyregion/06abuse.html?_r=1&amp;hp">reports</a>, will be unsealing hearings in the Connecticut Superior Court.  We will follow those with interest.</p>
]]></content:encoded>
			<wfw:commentRss>http://yaleisp.org/2009/10/can-judicial-openness-initiatives-disqualify-judges-from-access-cases/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>General shout-out to the Sunlight Foundation</title>
		<link>http://yaleisp.org/2009/10/general-shout-out-to-the-sunlight-foundation/</link>
		<comments>http://yaleisp.org/2009/10/general-shout-out-to-the-sunlight-foundation/#comments</comments>
		<pubDate>Thu, 08 Oct 2009 19:10:15 +0000</pubDate>
		<dc:creator>Margot</dc:creator>
				<category><![CDATA[first amendment]]></category>
		<category><![CDATA[lamp]]></category>
		<category><![CDATA[open access]]></category>
		<category><![CDATA[New Media]]></category>

		<guid isPermaLink="false">http://lamponline.org/?p=95</guid>
		<description><![CDATA[The Sunlight Foundation is committed to exactly the kind of transparency principles that journalism traditionally serves. Their projects include: compiling a list of people seeking tax breaks on imports from Congress; building a completely indexed and cross-referenced depository of federal documents; running the numbers on sources of Congressional wealth; opening bills to online, public review.
&#8220;The [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.sunlightfoundation.com/">Sunlight Foundation</a> is committed to exactly the kind of transparency principles that journalism traditionally serves. Their projects include: compiling a list of people seeking tax breaks on imports from Congress; building a completely indexed and cross-referenced depository of federal documents; running the numbers on sources of Congressional wealth; opening bills to online, public review.</p>
<p>&#8220;The Sunlight Foundation is a non-partisan non-profit dedicated to using the power of the Internet to catalyze greater government openness and transparency.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://yaleisp.org/2009/10/general-shout-out-to-the-sunlight-foundation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
