<?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: Proposal: New standards and tools for distributed online reporting</title>
	<atom:link href="http://www.ojr.org/051110niles/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ojr.org/051110niles/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=051110niles</link>
	<description>Focusing on the future of digital journalism</description>
	<lastBuildDate>Sun, 07 Apr 2013 15:02:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Robert Niles</title>
		<link>http://www.ojr.org/051110niles/#comment-404</link>
		<dc:creator>Robert Niles</dc:creator>
		<pubDate>Wed, 16 Nov 2005 22:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=884#comment-404</guid>
		<description><![CDATA[That&#039;s an intersting effort, certainly, but more along a narrative model than the data-driven incident reporting process I&#039;m talking about. But two models could, and should, work together.]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s an intersting effort, certainly, but more along a narrative model than the data-driven incident reporting process I&#8217;m talking about. But two models could, and should, work together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Pandolfo</title>
		<link>http://www.ojr.org/051110niles/#comment-403</link>
		<dc:creator>Joe Pandolfo</dc:creator>
		<pubDate>Wed, 16 Nov 2005 21:31:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=884#comment-403</guid>
		<description><![CDATA[The Independent Media Center website network &lt;&quot;http://www.indymedia.org/en/index.shtml&quot;&gt; has been fastgrowing (since inception at the renowned Seattle WTO protests), but in a structured way. Good model. ]]></description>
		<content:encoded><![CDATA[<p>The Independent Media Center website network < "http://www.indymedia.org/en/index.shtml"> has been fastgrowing (since inception at the renowned Seattle WTO protests), but in a structured way. Good model. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Humphrey</title>
		<link>http://www.ojr.org/051110niles/#comment-402</link>
		<dc:creator>Brian Humphrey</dc:creator>
		<pubDate>Sun, 13 Nov 2005 14:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=884#comment-402</guid>
		<description><![CDATA[Robert,

I applaud your grassroots effort to develop the tools necessary to gather and coordinate such information.

I thought you might be interested in a parallel if not similar effort taking place among those of us in the public safety and service realm.

Among the most promising tools for both senders and recipients of &quot;emergency incident&quot; information is the seminal &lt;a HREF=&quot;http://en.wikipedia.org/wiki/Common_Alerting_Protocol&quot; rel=&quot;nofollow&quot;&gt;Common Alerting Protocol (CAP)&lt;/A&gt;, a data interchange standard for alerting and event notification applications.

Some of our nation&#039;s best and brightest are working on this concept in earnest, and the Los Angeles Fire Department is but one of &lt;a HREF=&quot;http://www.incident.com/cookbook/index.php/Who_Is_Using_CAP%3F&quot; rel=&quot;nofollow&quot;&gt;several noteworthy agencies&lt;/A&gt; supporting the implementation of CAP.

The &lt;a HREF=&quot;http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency&quot; rel=&quot;nofollow&quot;&gt;Organization for the Advancement of Structured Information Standards (OASIS)&lt;/A&gt; adopted CAP 1.1 as a standard on 10/1/2005, and their Technical Committee welcomes participation by stakeholders and members of the public concerned with disaster management and response.

I&#039;d encourage anyone interested in learning more about CAP to visit Art Botterell&#039;s ever popular &lt;a HREF=&quot;http://www.incident.com/cookbook/index.php/Welcome_to_the_CAP_Cookbook&quot; rel=&quot;nofollow&quot;&gt;CAP Cookbook&lt;/A&gt;.

While CAP may not directly solve the conundrum you mention, I do think that at the very least, the process that brought forth CAP might be of interest.

Respectfully Yours in Safety and Service,

Brian Humphrey
Firefighter/Paramedic
Public Information Officer
Los Angeles Fire Department
]]></description>
		<content:encoded><![CDATA[<p>Robert,</p>
<p>I applaud your grassroots effort to develop the tools necessary to gather and coordinate such information.</p>
<p>I thought you might be interested in a parallel if not similar effort taking place among those of us in the public safety and service realm.</p>
<p>Among the most promising tools for both senders and recipients of &#8220;emergency incident&#8221; information is the seminal <a HREF="http://en.wikipedia.org/wiki/Common_Alerting_Protocol" rel="nofollow">Common Alerting Protocol (CAP)</a>, a data interchange standard for alerting and event notification applications.</p>
<p>Some of our nation&#8217;s best and brightest are working on this concept in earnest, and the Los Angeles Fire Department is but one of <a HREF="http://www.incident.com/cookbook/index.php/Who_Is_Using_CAP%3F" rel="nofollow">several noteworthy agencies</a> supporting the implementation of CAP.</p>
<p>The <a HREF="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency" rel="nofollow">Organization for the Advancement of Structured Information Standards (OASIS)</a> adopted CAP 1.1 as a standard on 10/1/2005, and their Technical Committee welcomes participation by stakeholders and members of the public concerned with disaster management and response.</p>
<p>I&#8217;d encourage anyone interested in learning more about CAP to visit Art Botterell&#8217;s ever popular <a HREF="http://www.incident.com/cookbook/index.php/Welcome_to_the_CAP_Cookbook" rel="nofollow">CAP Cookbook</a>.</p>
<p>While CAP may not directly solve the conundrum you mention, I do think that at the very least, the process that brought forth CAP might be of interest.</p>
<p>Respectfully Yours in Safety and Service,</p>
<p>Brian Humphrey<br />
Firefighter/Paramedic<br />
Public Information Officer<br />
Los Angeles Fire Department</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vish Iyer</title>
		<link>http://www.ojr.org/051110niles/#comment-401</link>
		<dc:creator>Vish Iyer</dc:creator>
		<pubDate>Thu, 10 Nov 2005 17:22:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=884#comment-401</guid>
		<description><![CDATA[Hello Robert,
I find this project very interesting. We have launched a craigslist style classifieds posting site, based on community involvement(www.citiposts.com). We are an xml based website, and make the contents available in RSS, wireless and audio formats. All of this is done automatically, using our translation engine.
Once a bunch of sites agree on a simple (but functional) XML format that works for all the sites that exchange information, I think we might already have the code to make this happen.

Please contact me if you would like further discussions.

Thanks
Vish
(vish[at]21stsolutions[dot]com)]]></description>
		<content:encoded><![CDATA[<p>Hello Robert,<br />
I find this project very interesting. We have launched a craigslist style classifieds posting site, based on community involvement(www.citiposts.com). We are an xml based website, and make the contents available in RSS, wireless and audio formats. All of this is done automatically, using our translation engine.<br />
Once a bunch of sites agree on a simple (but functional) XML format that works for all the sites that exchange information, I think we might already have the code to make this happen.</p>
<p>Please contact me if you would like further discussions.</p>
<p>Thanks<br />
Vish<br />
(vish[at]21stsolutions[dot]com)</p>
]]></content:encoded>
	</item>
</channel>
</rss>