<?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: My Thoughts About Privacy Commons</title>
	<atom:link href="http://www.aarontitus.net/blog/2009/12/06/my-thoughts-about-privacy-commons/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.aarontitus.net/blog/2009/12/06/my-thoughts-about-privacy-commons/</link>
	<description>Aaron Titus&#039; Personal Blog</description>
	<lastBuildDate>Tue, 10 Jan 2012 19:01:49 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Christopher Parsons</title>
		<link>http://www.aarontitus.net/blog/2009/12/06/my-thoughts-about-privacy-commons/comment-page-1/#comment-860</link>
		<dc:creator>Christopher Parsons</dc:creator>
		<pubDate>Thu, 10 Dec 2009 03:47:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.aarontitus.net/blog/?p=109#comment-860</guid>
		<description>This is a very delayed comment, so apologies for that. I&#039;d suggest that maybe the following set it items would be appropriate:

(1) iconography, displayed prominently on the main site or other commonly trafficked area of the site
(2) rather than a shorten privacy policy, privacy principles that apply to the organization as a whole
(3) a more complete privacy policy, in legalese, preferably with some kind of &#039;average english&#039; summary at each major point.

(3) in particular seems tricky to me, but might clarify both the intentions of the legal staff as well as let curious end users understand just what is actually being said. Maybe this tripartite system remains overly complicated though...</description>
		<content:encoded><![CDATA[<p>This is a very delayed comment, so apologies for that. I&#8217;d suggest that maybe the following set it items would be appropriate:</p>
<p>(1) iconography, displayed prominently on the main site or other commonly trafficked area of the site<br />
(2) rather than a shorten privacy policy, privacy principles that apply to the organization as a whole<br />
(3) a more complete privacy policy, in legalese, preferably with some kind of &#8216;average english&#8217; summary at each major point.</p>
<p>(3) in particular seems tricky to me, but might clarify both the intentions of the legal staff as well as let curious end users understand just what is actually being said. Maybe this tripartite system remains overly complicated though&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

