<?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>Change bLog &#187; Google Docs</title>
	<atom:link href="http://antjessop.edublogs.org/tag/google-docs/feed/" rel="self" type="application/rss+xml" />
	<link>http://antjessop.edublogs.org</link>
	<description>Another way?</description>
	<lastBuildDate>Thu, 05 Feb 2009 03:04:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Flickr and Google Docs CPD</title>
		<link>http://antjessop.edublogs.org/2008/01/24/flickr-and-google-docs-cpd/</link>
		<comments>http://antjessop.edublogs.org/2008/01/24/flickr-and-google-docs-cpd/#comments</comments>
		<pubDate>Thu, 24 Jan 2008 17:17:24 +0000</pubDate>
		<dc:creator>antjessop</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[collaborative]]></category>
		<category><![CDATA[CPD]]></category>
		<category><![CDATA[flickr]]></category>
		<category><![CDATA[Google Docs]]></category>
		<category><![CDATA[training]]></category>

		<guid isPermaLink="false">http://antjessop.edublogs.org/2008/01/24/flickr-and-google-docs-cpd/</guid>
		<description><![CDATA[Today we started the first of our weekly ICT staff training sessions.  After a shaky start (which lasted half an hour) we had some fun with Google Docs, working collaboratively on a presentation.  Unfortunately, this shaky start made everything appear far more complicated than it actually was.  However, as our staff became [...]]]></description>
			<content:encoded><![CDATA[<p>Today we started the first of our weekly ICT staff training sessions.  After a shaky start (which lasted half an hour) we had some fun with <a href="https://www.google.com/accounts/ServiceLogin?service=writely&amp;passive=true&amp;continue=http%3A%2F%2Fdocs.google.com%2F&amp;followup=http%3A%2F%2Fdocs.google.com%2F&amp;ltmpl=homepage&amp;nui=1">Google Docs</a>, working collaboratively on a presentation.  Unfortunately, this shaky start made everything appear far more complicated than it actually was.  However, as our staff became aware that they could edit each other&#8217;s work we began to have more fun!  Pictures were added by dragging photos from <a href="http://www.flickr.com">flickr</a> onto the document.  <a href="http://www.flickr.com">Flickr</a> is useful because, using an advanced search, photos can be found that are copywrite free, or at least only partially restricted using a <a href="http://creativecommons.org/">creative commons</a> license.  We will probably talk about properly attributing a persons work them at a later date (I don&#8217;t want to scare them off), as we shamefully haven&#8217;t included any in our presentation.  The presentation can be seen by clicking on the link below.</p>
<p><a href="http://docs.google.com/Present?docid=dcpbrp4d_9cd2d3nfv&amp;invite=hhjxqpt">http://docs.google.com/Present?docid=dcpbrp4d_9cd2d3nfv&amp;invite=hhjxqpt</a></p>
<p>It was mentioned that this technology could have positive implications for teaching and learning, but no concrete ideas were presented as to what these might actually be.  Any ideas or actual proof of the use of flickr or Google Docs in the classroom would be appreciated.  Please add your comments! </p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fantjessop.edublogs.org%2F2008%2F01%2F24%2Fflickr-and-google-docs-cpd%2F';
  addthis_title  = 'Flickr+and+Google+Docs+CPD';
  addthis_pub    = '';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://antjessop.edublogs.org/2008/01/24/flickr-and-google-docs-cpd/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
