<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:blue'>Harlan Yu will present his preFPO on Friday April 22 at 2PM in the <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:blue'>CITP Conference Room, 3d floor, Sherrerd Hall. The members of <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:blue'>his committee are: Ed Felten, advisor; Jen Rexford and Beth <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:blue'>Noveck (NYU Law School), readers; Mike Freedman and Matt <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:blue'>Salganik (SOC), nonreaders. Everyone is invited to attend his <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:blue'>talk. His abstract follows below.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";color:blue'>-------------------------------<o:p></o:p></span></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Title: Designing Software to Shape Open Government Policy<o:p></o:p></p></div><div><p class=MsoNormal>Abstract:<br><br>An open government is fundamental to democratic societies. Openness enables citizens to make well-informed electoral choices and to hold the government accountable for its actions, and it promotes trust between the government and its people.<br><br>Modern advances in computing and communications technologies have transformed what it means for a government to be open and transparent. Governments today can instantly transmit large amounts of data directly to citizens, and citizens now have vast capabilities to process and understand this information.<br><br>In this dissertation, we establish the basic principles for government’s use of information technology to increase openness, by focusing on the publication of raw machine-processable datasets. We then discuss how the design of software can help guide the government toward these openness principles and eventually to changes in existing policies, processes or both. We consider two projects aimed at creating such changes at the federal level.<br><br>The first project examines the closed nature of federal court records in the United States. We describe the RECAP browser extension, which we purpose-built to liberate court documents in a distributed and collaborative way, and show how its core design features were essential to its widespread adoption. We address the impact our tool has made on the policy discourse, as well as the limitations of this methodology to influence desirable policy changes.<br><br>The second project looks at Congress and how the current legislative process significantly hinders software-enabled transparency efforts. We show how the maintenance of the United States Code is similar to—and distinct from—revision control of source code, and we discuss the implications of these differences. We demonstrate new software tools that can, in a limited setting, provide novel benefits to the legislative process, including automatic error-detection and more efficient bill drafting. Finally, we outline what Congress should do to facilitate the development of these new transparency tools.<o:p></o:p></p></div></div></body></html>