<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.7.1" -->
<rss version="0.92">
<channel>
	<title>communibuild.com</title>
	<link>http://www.communibuild.com</link>
	<description></description>
	<lastBuildDate>Thu, 18 Jun 2009 00:15:59 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>My OSTP Blog Comments on Changing the PRA</title>
		<description>I have just now started contributing to Phase II of the Open Government Directive.  CrisisCamp pretty much took up all of my spare time, but I'm going to try making up for it in the next few days.  Here's my comments I just made on fixing the Paperwork ...</description>
		<link>http://www.communibuild.com/2009/06/18/my-ostp-blog-comments-on-changing-the-pra/</link>
			</item>
	<item>
		<title>Gov2.0 Privacy Issues for PrivacyCampDC</title>
		<description>EDIT: This has also been Reposted on the PrivacyCampDC Blog

In looking toward participating in PrivacyCampDC this Saturday, there are a number of privacy issues I'm concerned about regarding the movement toward open government.  While I am totally in favor of transforming government through transparency, participation and collaboration, I think it ...</description>
		<link>http://www.communibuild.com/2009/06/16/gov20-privacy-issues-for-privacycampdc/</link>
			</item>
	<item>
		<title>508 Compliance: Stop Enforcing, Start Innovating</title>
		<description>In 1998, Congress amended the Rehabilitation Act to require Federal agencies to make their electronic and information technology accessible to people with disabilities.  Now known affectionately as Section 508, it directs all Federal agencies to ensure that their websites and electronic information are just as accessible to people with hearing ...</description>
		<link>http://www.communibuild.com/2009/03/27/transforming-508-compliance-stop-enforcing-start-innovating/</link>
			</item>
	<item>
		<title>Communication Evolution: Letters to 140 Characters</title>
		<description>Then:  Once upon a time when it took up to three weeks to delivery a communication, people would write long, multi-page letters to one another.  These letters provided a series of intertwined thoughts and emotions that conveyed everything a person was thinking, feeling and wondering, all within a semi-coherent narrative. ...</description>
		<link>http://www.communibuild.com/2009/03/26/communication-evolution-letters-to-140-characters/</link>
			</item>
	<item>
		<title>Putting Citizens on Par with Lobbyists</title>
		<description>The Transparency and Open Government memo states that "Executive departments and agencies should offer Americans increased opportunities to participate in policy making and to provide their Government with the benefits of their collective expertise and information."  While this is an important goal for the Executive Branch, it is just as critical ...</description>
		<link>http://www.communibuild.com/2009/03/16/putting-citizens-on-par-with-lobbyists/</link>
			</item>
	<item>
		<title>Office of Government Engagement Needed?</title>
		<description>The new Administration has put significant effort into the Transparency and Open Government effort.  There have certainly been examples of progress towards an open government, such as  HUD's Recovery Act site, which already has some great data on where their Recovery Act dollars are going. While there has been a ...</description>
		<link>http://www.communibuild.com/2009/03/13/office-of-government-engagement-needed/</link>
			</item>
	<item>
		<title>Open Source Government Transparency Projects</title>
		<description>A whole cadre of folks inside and outside government are awash with figuring out how to address the government transparency question brought on by the President's Transparency and Open Government memo. At the end of last weekend's TransparencyCamp, Clay Johnson, Director of Sunlight Labs, brought up the issue of bringing ...</description>
		<link>http://www.communibuild.com/2009/03/08/open-source-government-transparency-projects/</link>
			</item>
</channel>
</rss>
