<?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: Unobtrusive Collaboration in Google Docs</title>
	<atom:link href="http://edte.ch/blog/2008/10/10/unobtrusive-collaboration-in-google-docs/feed/" rel="self" type="application/rss+xml" />
	<link>http://edte.ch/blog/2008/10/10/unobtrusive-collaboration-in-google-docs/</link>
	<description>Inspire Connect Engage Create</description>
	<lastBuildDate>Wed, 08 Feb 2012 03:54:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Eric Nentrup</title>
		<link>http://edte.ch/blog/2008/10/10/unobtrusive-collaboration-in-google-docs/comment-page-1/#comment-4778</link>
		<dc:creator>Eric Nentrup</dc:creator>
		<pubDate>Sun, 31 Jul 2011 12:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://tbarrett.edublogs.org/?p=309#comment-4778</guid>
		<description>You&#039;re so right!

I work like this with my high school upperclassmen on a very regular basis. In fact, I teach them to setup a peer-editing framework from the start of a new writing assignment. I do so by telling and modeling to the students the notion of &quot;turning in a paper before you write it&quot;.I get students in the habit of creating a new document, renaming it with their name and the assignment short name (Suzy Q - Essay 1), and IMMEDIATELY sharing it with ME, and two peers who agree to proofread it. I login to their documents VERY early in the assignment, offer them some encouragement by way of the sidebar chat, and do so to let them know I&#039;m &quot;watching&quot; them (to prevent loafing). I&#039;ll also do this when students don&#039;t have confidence in their writing skills, and I can even give them prompts IN their document while having a sidebar chat about how they feel about the assignment.If it&#039;s a multi-day writing project, I&#039;ll  start the 2nd or 3rd day with a brief demo of how to leave peer comments using the INSERT COMMENT function.Regarding marking up student work, I&#039;ve recently decided to put up a poster in my room with my &quot;short hand&quot; for editorial marks. This replaces the markup we used to do in red ink! So, I&#039;ll highlight a chunk of their text containing the error, and use the keyboard shortcut for inserting a comment, quickly type in something like &quot;SVA&quot; (Subject/Verb Agreement) or &quot;CAPS&quot; or &quot;CS&quot; (Comma Splice). Students can then refer to the poster which includes links to the Purdue Online Writing Lab, one of the BEST tools for remediating grammar and formatting skills.Students who are faster than the rest of the class go into &quot;teacher assistant&quot; mode, and spend the remainder of that period or those days in the lab editing others&#039; work, and offering encouragement to those who aren&#039;t as speedy with their work.So, I&#039;m a HUGE believer in your approach to the less-obtrusive, more fluid writing instruction. I can&#039;t imagine doing it without GDocs!</description>
		<content:encoded><![CDATA[<p>You&#8217;re so right!</p>
<p>I work like this with my high school upperclassmen on a very regular basis. In fact, I teach them to setup a peer-editing framework from the start of a new writing assignment. I do so by telling and modeling to the students the notion of &#8220;turning in a paper before you write it&#8221;.I get students in the habit of creating a new document, renaming it with their name and the assignment short name (Suzy Q &#8211; Essay 1), and IMMEDIATELY sharing it with ME, and two peers who agree to proofread it. I login to their documents VERY early in the assignment, offer them some encouragement by way of the sidebar chat, and do so to let them know I&#8217;m &#8220;watching&#8221; them (to prevent loafing). I&#8217;ll also do this when students don&#8217;t have confidence in their writing skills, and I can even give them prompts IN their document while having a sidebar chat about how they feel about the assignment.If it&#8217;s a multi-day writing project, I&#8217;ll  start the 2nd or 3rd day with a brief demo of how to leave peer comments using the INSERT COMMENT function.Regarding marking up student work, I&#8217;ve recently decided to put up a poster in my room with my &#8220;short hand&#8221; for editorial marks. This replaces the markup we used to do in red ink! So, I&#8217;ll highlight a chunk of their text containing the error, and use the keyboard shortcut for inserting a comment, quickly type in something like &#8220;SVA&#8221; (Subject/Verb Agreement) or &#8220;CAPS&#8221; or &#8220;CS&#8221; (Comma Splice). Students can then refer to the poster which includes links to the Purdue Online Writing Lab, one of the BEST tools for remediating grammar and formatting skills.Students who are faster than the rest of the class go into &#8220;teacher assistant&#8221; mode, and spend the remainder of that period or those days in the lab editing others&#8217; work, and offering encouragement to those who aren&#8217;t as speedy with their work.So, I&#8217;m a HUGE believer in your approach to the less-obtrusive, more fluid writing instruction. I can&#8217;t imagine doing it without GDocs!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Using Voicethread for Writing Ideas and for Peer Marking &#124; edte.ch</title>
		<link>http://edte.ch/blog/2008/10/10/unobtrusive-collaboration-in-google-docs/comment-page-1/#comment-1880</link>
		<dc:creator>Using Voicethread for Writing Ideas and for Peer Marking &#124; edte.ch</dc:creator>
		<pubDate>Mon, 01 Feb 2010 20:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://tbarrett.edublogs.org/?p=309#comment-1880</guid>
		<description>[...] we were working in Google Docs I dipped into their work as they were busy writing. I have written before about how this is less obtrusive than looking over their shoulder or taking their books off of [...]</description>
		<content:encoded><![CDATA[<p>[...] we were working in Google Docs I dipped into their work as they were busy writing. I have written before about how this is less obtrusive than looking over their shoulder or taking their books off of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver Quinlan</title>
		<link>http://edte.ch/blog/2008/10/10/unobtrusive-collaboration-in-google-docs/comment-page-1/#comment-850</link>
		<dc:creator>Oliver Quinlan</dc:creator>
		<pubDate>Sun, 11 Oct 2009 20:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://tbarrett.edublogs.org/?p=309#comment-850</guid>
		<description>This sounds like a great idea, very good to encourage actually using marking to influence work. It is so easy, especially when using docs, to mark a piece of work and not really give the pupils opportunity for your comments to influence what they are doing (or even give time to look at them sometimes!). This approach could really scaffold the children to improve what they are doing, I will definitely try in as soon as I can with my class.</description>
		<content:encoded><![CDATA[<p>This sounds like a great idea, very good to encourage actually using marking to influence work. It is so easy, especially when using docs, to mark a piece of work and not really give the pupils opportunity for your comments to influence what they are doing (or even give time to look at them sometimes!). This approach could really scaffold the children to improve what they are doing, I will definitely try in as soon as I can with my class.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Useful Sites (weekly) &#171; Rhondda&#8217;s Reflections - wandering around the Web</title>
		<link>http://edte.ch/blog/2008/10/10/unobtrusive-collaboration-in-google-docs/comment-page-1/#comment-849</link>
		<dc:creator>Useful Sites (weekly) &#171; Rhondda&#8217;s Reflections - wandering around the Web</dc:creator>
		<pubDate>Sun, 30 Nov 2008 07:33:40 +0000</pubDate>
		<guid isPermaLink="false">http://tbarrett.edublogs.org/?p=309#comment-849</guid>
		<description>[...] Unobtrusive Collaboration in Google Docs &#124; ICT in my Classroom [...]</description>
		<content:encoded><![CDATA[<p>[...] Unobtrusive Collaboration in Google Docs | ICT in my Classroom [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Online coachen via Google Docs</title>
		<link>http://edte.ch/blog/2008/10/10/unobtrusive-collaboration-in-google-docs/comment-page-1/#comment-848</link>
		<dc:creator>Online coachen via Google Docs</dc:creator>
		<pubDate>Mon, 20 Oct 2008 20:33:14 +0000</pubDate>
		<guid isPermaLink="false">http://tbarrett.edublogs.org/?p=309#comment-848</guid>
		<description>[...] net een heel interessant bericht van Tom Barett Unobtrusing Collaboration in Google docs waarin hij beschreef hoe hij Google Docs gebruikte om [...]</description>
		<content:encoded><![CDATA[<p>[...] net een heel interessant bericht van Tom Barett Unobtrusing Collaboration in Google docs waarin hij beschreef hoe hij Google Docs gebruikte om [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Googlies &#171; J&#8217;suis snob</title>
		<link>http://edte.ch/blog/2008/10/10/unobtrusive-collaboration-in-google-docs/comment-page-1/#comment-847</link>
		<dc:creator>Googlies &#171; J&#8217;suis snob</dc:creator>
		<pubDate>Wed, 15 Oct 2008 04:56:52 +0000</pubDate>
		<guid isPermaLink="false">http://tbarrett.edublogs.org/?p=309#comment-847</guid>
		<description>[...] Unobtrusive Collaboration in Google Docs &#124; ICT in my Classroom via kwout   &#160; [...]

[WORDPRESS HASHCASH] The comment&#039;s server IP (76.74.255.43) doesn&#039;t match the comment&#039;s URL host IP (76.74.254.123) and so is spam.</description>
		<content:encoded><![CDATA[<p>[...] Unobtrusive Collaboration in Google Docs | ICT in my Classroom via kwout   &nbsp; [...]</p>
<p>[WORDPRESS HASHCASH] The comment&#8217;s server IP (76.74.255.43) doesn&#8217;t match the comment&#8217;s URL host IP (76.74.254.123) and so is spam.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

