<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: About Reachtogether.co.uk</title>
	<atom:link href="http://fractionalnews.wordpress.com/about/feed/" rel="self" type="application/rss+xml" />
	<link>http://fractionalnews.wordpress.com</link>
	<description>News, views, and rants about fractional ownership, web marketing, and anything else!</description>
	<lastBuildDate>Thu, 21 Aug 2008 00:55:44 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: fractionalnews</title>
		<link>http://fractionalnews.wordpress.com/about/#comment-5</link>
		<dc:creator>fractionalnews</dc:creator>
		<pubDate>Tue, 04 Mar 2008 14:07:52 +0000</pubDate>
		<guid isPermaLink="false">#comment-5</guid>
		<description>Thanks for the comment.  I&#039;m not sure I&#039;ve succeded in making sense of it yet but I&#039;ll get there in the end.

So far as time allocation rules go I think the success of any idea depends on the people in each scheme.  The ideal is putting together people with/without school-age children to avoid the pressure on school holidays.  Not always possible though.  In the schemes on www.reachtogether.co.uk we have tended to go for time allocation by season, with each fraction owner picking in an order initially chosen at random (for each season) and then rotating each year (first choice going to last?).  Have you any experience/preference/ideas?</description>
		<content:encoded><![CDATA[<p>Thanks for the comment.  I&#8217;m not sure I&#8217;ve succeded in making sense of it yet but I&#8217;ll get there in the end.</p>
<p>So far as time allocation rules go I think the success of any idea depends on the people in each scheme.  The ideal is putting together people with/without school-age children to avoid the pressure on school holidays.  Not always possible though.  In the schemes on <a href="http://www.reachtogether.co.uk" rel="nofollow">http://www.reachtogether.co.uk</a> we have tended to go for time allocation by season, with each fraction owner picking in an order initially chosen at random (for each season) and then rotating each year (first choice going to last?).  Have you any experience/preference/ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M</title>
		<link>http://fractionalnews.wordpress.com/about/#comment-4</link>
		<dc:creator>M</dc:creator>
		<pubDate>Tue, 04 Mar 2008 09:13:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-4</guid>
		<description>Finally somebody who is trying to make sense of it all!
Having compared the many forms of fractionalizing, I agree that &#039;investors&#039; are better served when separate companies are created for each unit, rather than selling shares in the holding or operating company.

Has anyone found the most appealing RPS/Rotating Priority System yet? 

M</description>
		<content:encoded><![CDATA[<p>Finally somebody who is trying to make sense of it all!<br />
Having compared the many forms of fractionalizing, I agree that &#8216;investors&#8217; are better served when separate companies are created for each unit, rather than selling shares in the holding or operating company.</p>
<p>Has anyone found the most appealing RPS/Rotating Priority System yet? </p>
<p>M</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bibomedia</title>
		<link>http://fractionalnews.wordpress.com/about/#comment-3</link>
		<dc:creator>bibomedia</dc:creator>
		<pubDate>Wed, 27 Feb 2008 17:12:50 +0000</pubDate>
		<guid isPermaLink="false">#comment-3</guid>
		<description>Have a nice day !</description>
		<content:encoded><![CDATA[<p>Have a nice day !</p>
]]></content:encoded>
	</item>
</channel>
</rss>
