<?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: Page Description Diagrams</title>
	<atom:link href="http://wireframes.linowski.ca/2009/04/page-description-diagrams/feed/" rel="self" type="application/rss+xml" />
	<link>http://wireframes.linowski.ca/2009/04/page-description-diagrams/</link>
	<description>Because every IA has something funky up their sleeve</description>
	<lastBuildDate>Mon, 06 Feb 2012 15:18:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mitzie</title>
		<link>http://wireframes.linowski.ca/2009/04/page-description-diagrams/comment-page-1/#comment-25633</link>
		<dc:creator>Mitzie</dc:creator>
		<pubDate>Mon, 11 Oct 2010 00:39:42 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=699#comment-25633</guid>
		<description>Very late to this conversation, but I just have to ask: Why don&#039;t more information architects use these in 2010? So many wireframes I receive have very specific visual treatments suggested. If I suggest a design outside of these, I have to research and defend the interactions that justify an alternate approach. PDD seems like an ideal approach to keeping both the IA and the visual designer on respectful terms of each others&#039; contribution. I understand that some sites are very complex require the wireframe approach, however, it would be great if we could explore using this more. </description>
		<content:encoded><![CDATA[<p>Very late to this conversation, but I just have to ask: Why don&#039;t more information architects use these in 2010? So many wireframes I receive have very specific visual treatments suggested. If I suggest a design outside of these, I have to research and defend the interactions that justify an alternate approach. PDD seems like an ideal approach to keeping both the IA and the visual designer on respectful terms of each others&#039; contribution. I understand that some sites are very complex require the wireframe approach, however, it would be great if we could explore using this more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: semanticwill</title>
		<link>http://wireframes.linowski.ca/2009/04/page-description-diagrams/comment-page-1/#comment-9985</link>
		<dc:creator>semanticwill</dc:creator>
		<pubDate>Tue, 12 Jan 2010 15:41:09 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=699#comment-9985</guid>
		<description>Let&#039;s not forget to give credit where credit is due - Dan Brown is responsible for first creating Page Description Diagrams and writing about them way back in 2002 in his article &quot;Where the Wireframes Are: Special Deliverable #3&quot;  - before that article - there was no such thing as such a UX deliverable :-) 
 
- SW </description>
		<content:encoded><![CDATA[<p>Let&#039;s not forget to give credit where credit is due &#8211; Dan Brown is responsible for first creating Page Description Diagrams and writing about them way back in 2002 in his article &quot;Where the Wireframes Are: Special Deliverable #3&quot;  &#8211; before that article &#8211; there was no such thing as such a UX deliverable :-)</p>
<p>- SW</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wireframes Magazine</title>
		<link>http://wireframes.linowski.ca/2009/04/page-description-diagrams/comment-page-1/#comment-9981</link>
		<dc:creator>Wireframes Magazine</dc:creator>
		<pubDate>Tue, 12 Jan 2010 13:37:04 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=699#comment-9981</guid>
		<description>[...] definite Clickframe analogy which comes to mind is that of an interactive and auto-generated page description diagram. What both page description diagrams and clickframes in my opinion lack is the concreteness of [...]</description>
		<content:encoded><![CDATA[<p>[...] definite Clickframe analogy which comes to mind is that of an interactive and auto-generated page description diagram. What both page description diagrams and clickframes in my opinion lack is the concreteness of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyeshasnow</title>
		<link>http://wireframes.linowski.ca/2009/04/page-description-diagrams/comment-page-1/#comment-653</link>
		<dc:creator>Tyeshasnow</dc:creator>
		<pubDate>Fri, 03 Apr 2009 19:22:45 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=699#comment-653</guid>
		<description>i&#039;ve been waiting for an opportunity to use your template for a while. i really like it. just another tool for our box. it&#039;s amazing how each project requires such different deliverable.  thanks for sharing! </description>
		<content:encoded><![CDATA[<p>i&#039;ve been waiting for an opportunity to use your template for a while. i really like it. just another tool for our box. it&#039;s amazing how each project requires such different deliverable.  thanks for sharing!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

