<?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: Communicating with Congress Conference</title>
	<atom:link href="http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/</link>
	<description>Recommendations, Resources, and Reform</description>
	<lastBuildDate>Mon, 14 Feb 2011 15:53:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Daniel Bennett</title>
		<link>http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/comment-page-1/#comment-1260</link>
		<dc:creator>Daniel Bennett</dc:creator>
		<pubDate>Sun, 07 Oct 2007 14:37:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/#comment-1260</guid>
		<description>There already is an XML schema for communicating with Congress (and has been for over a decade). Although it has so far been mainly used internally (for the congressional hosted web forms), Maj. Leader Hoyer ran a beta test exposing the XML format with the addition of a new tag ( the topic code tag) which advocacy groups can put a URL into as a way to allow Hill staff to immediately tabulate incoming messages and assign responses. The beta test was very successful at saving offices time and with the increasing load of messages from advocacy campaigns will make life manageable for staffers. For advocacy groups it will mean that messages get recognized in a timely manner (before rather than after congressional votes).

As to the idea of Josh&#039;s, we had both spoken a couple years ago about &#039;connected conversations&#039; which would depend on legislative metadata standards as well as something like the topic code. I will look back through my notes for the slides we did. 

My paper about the topic code can be found at: http://www.advocatehope.org/project-papers/communicating-with-congress-by-way-of-advocacy</description>
		<content:encoded><![CDATA[<p>There already is an XML schema for communicating with Congress (and has been for over a decade). Although it has so far been mainly used internally (for the congressional hosted web forms), Maj. Leader Hoyer ran a beta test exposing the XML format with the addition of a new tag ( the topic code tag) which advocacy groups can put a URL into as a way to allow Hill staff to immediately tabulate incoming messages and assign responses. The beta test was very successful at saving offices time and with the increasing load of messages from advocacy campaigns will make life manageable for staffers. For advocacy groups it will mean that messages get recognized in a timely manner (before rather than after congressional votes).</p>
<p>As to the idea of Josh&#8217;s, we had both spoken a couple years ago about &#8216;connected conversations&#8217; which would depend on legislative metadata standards as well as something like the topic code. I will look back through my notes for the slides we did. </p>
<p>My paper about the topic code can be found at: <a href="http://www.advocatehope.org/project-papers/communicating-with-congress-by-way-of-advocacy" rel="nofollow">http://www.advocatehope.org/project-papers/communicating-with-congress-by-way-of-advocacy</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/comment-page-1/#comment-1201</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 04 Oct 2007 17:27:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/#comment-1201</guid>
		<description>i forgot to mention the Condorcet internet voting service</description>
		<content:encoded><![CDATA[<p>i forgot to mention the Condorcet internet voting service</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/comment-page-1/#comment-1200</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 04 Oct 2007 17:26:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/#comment-1200</guid>
		<description>many-to-one aggregated communication:
blog comments, forums (fora?), user-submitted aggregation sites (slashdot/digg/dell idea storm), anything with voting and ranking (youtube, etc.)

identification problem:
openid

...</description>
		<content:encoded><![CDATA[<p>many-to-one aggregated communication:<br />
blog comments, forums (fora?), user-submitted aggregation sites (slashdot/digg/dell idea storm), anything with voting and ranking (youtube, etc.)</p>
<p>identification problem:<br />
openid</p>
<p>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oxa Koba</title>
		<link>http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/comment-page-1/#comment-1190</link>
		<dc:creator>Oxa Koba</dc:creator>
		<pubDate>Thu, 04 Oct 2007 06:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.theopenhouseproject.com/2007/10/02/communicating-with-congress-conference/#comment-1190</guid>
		<description>But there are many other forms of many-to-one, aggregated communication,&#8230;

Could you elaborate on this please. It is not immediately obvious what these other forms are that might be appropriate for the congressional context.</description>
		<content:encoded><![CDATA[<p>But there are many other forms of many-to-one, aggregated communication,&hellip;</p>
<p>Could you elaborate on this please. It is not immediately obvious what these other forms are that might be appropriate for the congressional context.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

