<?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: Follow-up: Designing Hierarchical IAs</title>
	<atom:link href="http://bokardo.com/archives/follow-up-designing-hierarchical-ias/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com/archives/follow-up-designing-hierarchical-ias/</link>
	<description>A Blog about Social Web Design</description>
	<lastBuildDate>Fri, 19 Feb 2010 06:52:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: donnam</title>
		<link>http://bokardo.com/archives/follow-up-designing-hierarchical-ias/comment-page-1/#comment-406</link>
		<dc:creator>donnam</dc:creator>
		<pubDate>Mon, 04 Apr 2005 00:23:21 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/61/#comment-406</guid>
		<description>Ahah. So that is the tricky part isn&#039;t it. I&#039;ve been thinking about it all weekend and still can&#039;t come up with something simple enough to suit a blog comment - I could write a long article or a book on it ;)

I&#039;ll keep thinking</description>
		<content:encoded><![CDATA[<p>Ahah. So that is the tricky part isn&#8217;t it. I&#8217;ve been thinking about it all weekend and still can&#8217;t come up with something simple enough to suit a blog comment &#8211; I could write a long article or a book on it <img src='http://bokardo.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>I&#8217;ll keep thinking</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://bokardo.com/archives/follow-up-designing-hierarchical-ias/comment-page-1/#comment-393</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Thu, 31 Mar 2005 11:27:19 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/61/#comment-393</guid>
		<description>Donna, I&#039;m all for defining terms. Why don&#039;t we start with your definition? Care to share one? </description>
		<content:encoded><![CDATA[<p>Donna, I&#8217;m all for defining terms. Why don&#8217;t we start with your definition? Care to share one?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: donnam</title>
		<link>http://bokardo.com/archives/follow-up-designing-hierarchical-ias/comment-page-1/#comment-386</link>
		<dc:creator>donnam</dc:creator>
		<pubDate>Thu, 31 Mar 2005 02:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/61/#comment-386</guid>
		<description>I&#039;ve been thinking further on this and you may need to go back one step to have a sensible conversation about this and ask:
&quot;What is a hierarchy?&quot;

It may sound obvious, but comments on your previous post lead me to believe that a number of people are viewing the concept of a hierarchy slightly differently.

Are you wondering why people design sites:
* in *strict* hierarchies, where everything has one place and only one place and only one way to get there
* in polyhierarchies where the site is hierarchical but content can be accessed from more than one branch

Additionally, most sites at least have a breakup of content at a top level. I still consider this hierarchical, even if the information in each section is based on facets or database structures.

So I think you may need to think a little more on what you actually want to know. It could then be a great conversation, but we need to be working with consistent concepts.

Email me if you want to go through some ideas.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been thinking further on this and you may need to go back one step to have a sensible conversation about this and ask:<br />
&#8220;What is a hierarchy?&#8221;</p>
<p>It may sound obvious, but comments on your previous post lead me to believe that a number of people are viewing the concept of a hierarchy slightly differently.</p>
<p>Are you wondering why people design sites:<br />
* in *strict* hierarchies, where everything has one place and only one place and only one way to get there<br />
* in polyhierarchies where the site is hierarchical but content can be accessed from more than one branch</p>
<p>Additionally, most sites at least have a breakup of content at a top level. I still consider this hierarchical, even if the information in each section is based on facets or database structures.</p>
<p>So I think you may need to think a little more on what you actually want to know. It could then be a great conversation, but we need to be working with consistent concepts.</p>
<p>Email me if you want to go through some ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CM Harrington</title>
		<link>http://bokardo.com/archives/follow-up-designing-hierarchical-ias/comment-page-1/#comment-379</link>
		<dc:creator>CM Harrington</dc:creator>
		<pubDate>Tue, 29 Mar 2005 23:21:07 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/61/#comment-379</guid>
		<description>On the value of serendipity. I&#039;d say it&#039;s *very* important, as often, on a public site, the visitor has not been indoctrinated into your controlled vocabulary/methodology. This usually means there is a deficiency in the visitors ability to articulate their question in a way that &quot;fits&quot; with the site. Being able to browse allows the visitor to &quot;feel out&quot; where they need to go, and find a &quot;good enough answer plus related things I didn&#039;t know I needed to know&quot; response.</description>
		<content:encoded><![CDATA[<p>On the value of serendipity. I&#8217;d say it&#8217;s *very* important, as often, on a public site, the visitor has not been indoctrinated into your controlled vocabulary/methodology. This usually means there is a deficiency in the visitors ability to articulate their question in a way that &#8220;fits&#8221; with the site. Being able to browse allows the visitor to &#8220;feel out&#8221; where they need to go, and find a &#8220;good enough answer plus related things I didn&#8217;t know I needed to know&#8221; response.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
