<?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"
	>
<channel>
	<title>Comments on: I&#8217;m on it</title>
	<atom:link href="http://blog.hackbash.com/2007/10/03/im-on-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hackbash.com/2007/10/03/im-on-it/</link>
	<description>wake up and smell the copy</description>
	<pubDate>Mon, 08 Sep 2008 09:04:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Leon</title>
		<link>http://blog.hackbash.com/2007/10/03/im-on-it/#comment-36</link>
		<dc:creator>Leon</dc:creator>
		<pubDate>Fri, 05 Oct 2007 14:21:43 +0000</pubDate>
		<guid isPermaLink="false">http://host.qsoftdns.net/~hackbash/blog/?p=38#comment-36</guid>
		<description>If it helps...

Information is published *on* a website. It is published *at* a URL/URI. This is not redundant and can't be conflated; one is an object, the other is a reference in an assumed address space. They normally covary, but consider such things as rebranding and mirror sites to see how anomalies might arise.</description>
		<content:encoded><![CDATA[<p>If it helps&#8230;</p>
<p>Information is published *on* a website. It is published *at* a URL/URI. This is not redundant and can&#8217;t be conflated; one is an object, the other is a reference in an assumed address space. They normally covary, but consider such things as rebranding and mirror sites to see how anomalies might arise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://blog.hackbash.com/2007/10/03/im-on-it/#comment-35</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Fri, 05 Oct 2007 14:20:30 +0000</pubDate>
		<guid isPermaLink="false">http://host.qsoftdns.net/~hackbash/blog/?p=38#comment-35</guid>
		<description>Could we draw any distinctions based on the structure of the site itself?  For example, the home page or top level of the web site could be the surface, so "on" is used.  Once you get to a lower level, it becomes "in".

In this context, "at" might well be usable for any addenda to a specific created object.  you would post "on" the front page of a blog, and leave a comment "at" that post.

I'd stress that all of this is dependent on the actions undertaken.  Where rules already exist they should be used, and in many cases a precise use of language should help matters.</description>
		<content:encoded><![CDATA[<p>Could we draw any distinctions based on the structure of the site itself?  For example, the home page or top level of the web site could be the surface, so &#8220;on&#8221; is used.  Once you get to a lower level, it becomes &#8220;in&#8221;.</p>
<p>In this context, &#8220;at&#8221; might well be usable for any addenda to a specific created object.  you would post &#8220;on&#8221; the front page of a blog, and leave a comment &#8220;at&#8221; that post.</p>
<p>I&#8217;d stress that all of this is dependent on the actions undertaken.  Where rules already exist they should be used, and in many cases a precise use of language should help matters.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
