<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Gov2.Info &#187; federal</title>
	<atom:link href="http://gov2.info/tag/federal/feed/" rel="self" type="application/rss+xml" />
	<link>http://gov2.info</link>
	<description>Showcasing Government sites in the Web2.0 age</description>
	<lastBuildDate>Thu, 22 Oct 2009 10:00:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>AGIMO have a blog</title>
		<link>http://gov2.info/agimo-have-a-blog/</link>
		<comments>http://gov2.info/agimo-have-a-blog/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 09:57:48 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[.gov.au]]></category>
		<category><![CDATA[Blogs]]></category>
		<category><![CDATA[AGIMO]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[federal]]></category>

		<guid isPermaLink="false">http://gov2.info/?p=103</guid>
		<description><![CDATA[The Web Publishing Guide Review
AGIMO (the Australian Government Information Management Office) has a blog which is dedicated to the review of the Web Publishing Guide. Hopefully this blog will lead by example in showing how a Government department can communicate using a blog, lead to a more useful  and usable Web Publishing Guide. As [...]]]></description>
			<content:encoded><![CDATA[<h3><a href="http://wpgblog.agimo.gov.au/">The Web Publishing Guide Review</a></h3>
<p>AGIMO (the Australian Government Information Management Office) has a blog which is dedicated to the review of the Web Publishing Guide. Hopefully this blog will lead by example in showing how a Government department can communicate using a blog, lead to a more useful  and usable Web Publishing Guide. As well as AGIMO beginning to understand web 2.0 tools and will start making use of other web 2.0 tools.</p>
<p>The big surprise for me (blogging more than a year after I expected is only minor), is that it is hosted in the cloud by wordpress.com. Not that there is anything wrong with this. I would actually recommend hosting a blog with wordpress.com  as this resolves issues regarding security and keeping the wordpress current. It is just a conservative government department with I assume considerable IT resources  surrendering the total control of hosting in house for the <em>less secure</em> external hosting.</p>
]]></content:encoded>
			<wfw:commentRss>http://gov2.info/agimo-have-a-blog/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>HREOC Blog</title>
		<link>http://gov2.info/hreoc-blog/</link>
		<comments>http://gov2.info/hreoc-blog/#comments</comments>
		<pubDate>Wed, 16 Jan 2008 23:48:46 +0000</pubDate>
		<dc:creator>nick</dc:creator>
				<category><![CDATA[.gov.au]]></category>
		<category><![CDATA[Blogs]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[federal]]></category>
		<category><![CDATA[HREOC]]></category>
		<category><![CDATA[human rights]]></category>
		<category><![CDATA[issues]]></category>

		<guid isPermaLink="false">http://gov2.info/?p=15</guid>
		<description><![CDATA[
HREOC listening tour blog
Now this is your traditional blog, running on WordPress and allowing comments to promote the Listening Tour of the HREOC Commissioner Broderick as she travels around Australia and to gather your feedback on the direction HREOC should take over the next five years. The comments are moderated as expected and are governed [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://hreocblog.com/"><img src='http://gov2.info/wp-content/uploads/2008/01/hreoc.png' alt='HREOC listening tour blog' /></a><br />
<h3><a href="http://hreocblog.com/">HREOC listening tour blog</a></h3>
<p>Now this is your traditional blog, running on WordPress and allowing comments to promote the <em>Listening Tour</em> of the HREOC Commissioner Broderick as she travels around Australia and to gather your feedback on the direction HREOC should take over the next five years. The comments are moderated as expected and are governed by an <a href="http://www.humanrights.gov.au/listeningtour/acceptable.html">acceptable use policy</a>. A couple of the more interesting conditions are:</p>
<ul>
<li>do protect your personal privacy and that of others by not including personal information of about yourself or about others in your posts to the blog, (such as names, email addresses, private addresses or phone numbers);</il></p>
<li>do represent your own views and not impersonate or falsely represent any other person;</li>
</ul>
<p>Overall a positive use of a blog to interact with their audience.</p>
<p>What I found interesting was while the blog and main HREOC site look identical they have different domain names and hosting half a world apart. The blog&#8217;s domain name is <a href="http://hreocblog.com">hreocblog.com</a> and hosted on a commercial provider in the US. While <a href="http://www.humanrights.gov.au">www.humanrights.gov.au</a> is hosted in Australia, probably inhouse. This does not surprise me, I know of more that a few Government IT departments that are unwilling to host a blog inhouse because of <em>security fears</em>(ie fear of the unknown), lack of skills and/or knowledge or just because it is easier to say <em>NO</em>. It also looks like the communications staff of HREOC, who I assume are responsible for the blog where unable or unwilling to get their IT people to delegate a subdomain name like blog.humanrights.gov.au and point that to their blog on the other side of the world.</p>
]]></content:encoded>
			<wfw:commentRss>http://gov2.info/hreoc-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
