<?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: universal declaration of users rights</title>
	<atom:link href="http://isomorpho.us/2008/11/universal-declaration-of-users-rights/feed/" rel="self" type="application/rss+xml" />
	<link>http://isomorpho.us/2008/11/universal-declaration-of-users-rights/</link>
	<description>same as...</description>
	<lastBuildDate>Mon, 30 Aug 2010 05:02:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Miek Dunbar</title>
		<link>http://isomorpho.us/2008/11/universal-declaration-of-users-rights/comment-page-1/#comment-838</link>
		<dc:creator>Miek Dunbar</dc:creator>
		<pubDate>Thu, 20 Nov 2008 01:51:19 +0000</pubDate>
		<guid isPermaLink="false">http://isomorpho.us/2008/11/universal-declaration-of-users-rights/#comment-838</guid>
		<description>I have tried using the term &#039;artifact&#039; instead of &#039;product&#039;. It seems to work quite well, except that the word doesn&#039;t really fly much outside academia. It also doesn&#039;t apply to services very well, but if you think of services as experiences, and experiences as objects to look back on and examine, then you could perhaps use artifacts. Or maybe just &#039;things&#039;. An experience can be a thing.

I have more of a problem with the term &#039;user&#039; still. I think people should have the right not to be labeled as &#039;users&#039;, hooked onto some kind of junk.</description>
		<content:encoded><![CDATA[<p>I have tried using the term &#8216;artifact&#8217; instead of &#8216;product&#8217;. It seems to work quite well, except that the word doesn&#8217;t really fly much outside academia. It also doesn&#8217;t apply to services very well, but if you think of services as experiences, and experiences as objects to look back on and examine, then you could perhaps use artifacts. Or maybe just &#8216;things&#8217;. An experience can be a thing.</p>
<p>I have more of a problem with the term &#8216;user&#8217; still. I think people should have the right not to be labeled as &#8216;users&#8217;, hooked onto some kind of junk.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
