<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.6" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Making Metadata Pay</title>
	<link>http://www.architected.info/blog/making-metadata-pay</link>
	<description>How people, practices, and information are transformed into relationships and understanding.</description>
	<pubDate>Fri, 21 Nov 2008 22:55:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.6</generator>

	<item>
		<title>by: Architected Information &#187; Process Meta-Usability</title>
		<link>http://www.architected.info/blog/making-metadata-pay#comment-35</link>
		<pubDate>Fri, 07 Jul 2006 03:24:39 +0000</pubDate>
		<guid>http://www.architected.info/blog/making-metadata-pay#comment-35</guid>
					<description>[...] Human intervention &#8211; Trap and deal with every possible situation in the design phase. Also, when a human does have to be involved, make it easy for them to understand what is going on at a glance. This probably means documentation, standards, naming conventions, log files, metadata, the works. This isn&#8217;t as hard as it sounds, there are some easy steps that you can take to make things run more smoothly for your friendly neighborhood operator. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Human intervention &#8211; Trap and deal with every possible situation in the design phase. Also, when a human does have to be involved, make it easy for them to understand what is going on at a glance. This probably means documentation, standards, naming conventions, log files, metadata, the works. This isn&#8217;t as hard as it sounds, there are some easy steps that you can take to make things run more smoothly for your friendly neighborhood operator. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
