<?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: Metadata fundamentals for intranets and websites</title>
	<atom:link href="http://www.steptwo.com.au/papers/kmc_metadata/index.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html</link>
	<description>Beyond The Idea</description>
	<lastBuildDate>Fri, 19 Mar 2010 09:40:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: wendy</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-1294</link>
		<dc:creator>wendy</dc:creator>
		<pubDate>Thu, 21 Jan 2010 03:47:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-1294</guid>
		<description>James, Thank you for your insight. I&#039;m new to the design and development of websites for a small community. Your descriptions really help the new developer understand the basics.</description>
		<content:encoded><![CDATA[<p>James, Thank you for your insight. I&#8217;m new to the design and development of websites for a small community. Your descriptions really help the new developer understand the basics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Robertson</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-757</link>
		<dc:creator>James Robertson</dc:creator>
		<pubDate>Wed, 08 Apr 2009 01:36:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-757</guid>
		<description>@Russ, a late reply on your comment about providing metadata to help applications/bots to find data. Definitely an important aspect, but I&#039;d highlight that concrete needs must be identified in advance.

For example, in Australian government, a lot of metadata was collected against future plans to automatically create &quot;portals&quot; on specific topics. But these never eventuated, in part due to the patchy quality of the metadata itself. So that left gov agencies with the mandated requirement to collect masses of data, but for no clear purpose. (This has subsequently been made optional in most cases.)

So automatic use of metadata is incredibly powerful, but only when done well (or at all!).</description>
		<content:encoded><![CDATA[<p>@Russ, a late reply on your comment about providing metadata to help applications/bots to find data. Definitely an important aspect, but I&#8217;d highlight that concrete needs must be identified in advance.</p>
<p>For example, in Australian government, a lot of metadata was collected against future plans to automatically create &#8220;portals&#8221; on specific topics. But these never eventuated, in part due to the patchy quality of the metadata itself. So that left gov agencies with the mandated requirement to collect masses of data, but for no clear purpose. (This has subsequently been made optional in most cases.)</p>
<p>So automatic use of metadata is incredibly powerful, but only when done well (or at all!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amal Arunesh</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-755</link>
		<dc:creator>Amal Arunesh</dc:creator>
		<pubDate>Mon, 06 Apr 2009 11:50:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-755</guid>
		<description>Great to know the basics of metadata. The article is very simple to understand.

Could you tell me how to insert metadata in the intranet. Is XML the best way to integrate metadata</description>
		<content:encoded><![CDATA[<p>Great to know the basics of metadata. The article is very simple to understand.</p>
<p>Could you tell me how to insert metadata in the intranet. Is XML the best way to integrate metadata</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simplify your intranet by using PDFs - but DON&#8217;T make documents searchable &#171; manIA</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-405</link>
		<dc:creator>Simplify your intranet by using PDFs - but DON&#8217;T make documents searchable &#171; manIA</dc:creator>
		<pubDate>Sat, 29 Nov 2008 16:11:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-405</guid>
		<description>[...] can learn more about metadata from James Robertson&#8217;s article in the Step Two [...]</description>
		<content:encoded><![CDATA[<p>[...] can learn more about metadata from James Robertson&#8217;s article in the Step Two [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian F</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-399</link>
		<dc:creator>Brian F</dc:creator>
		<pubDate>Thu, 27 Nov 2008 22:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-399</guid>
		<description>Hmmm, maybe I need to get out more, but I haven&#039;t seen a taxonomy that delivers much benefit. I&#039;m happy with basic metadata as described above for basic site management but doubt we can even justify the effort put into AGLS metdata, given that it is only used by one search engine that generates maybe 1% of traffic. If metadata is only for internal use, it probably doesn&#039;t need to be so complex, and we can simply accept that it only serves one purpose. At the CBR WSG meeting yesterday Stephen Zafira described tagging as &#039;dynamic IA&#039;, which I think is a step in the right direction towards accepting that data will be interpreted in different ways by different users, and frees us from trying to write &#039;one taxonomy to rule them all&#039;. KISS, live and let live.</description>
		<content:encoded><![CDATA[<p>Hmmm, maybe I need to get out more, but I haven&#8217;t seen a taxonomy that delivers much benefit. I&#8217;m happy with basic metadata as described above for basic site management but doubt we can even justify the effort put into AGLS metdata, given that it is only used by one search engine that generates maybe 1% of traffic. If metadata is only for internal use, it probably doesn&#8217;t need to be so complex, and we can simply accept that it only serves one purpose. At the CBR WSG meeting yesterday Stephen Zafira described tagging as &#8216;dynamic IA&#8217;, which I think is a step in the right direction towards accepting that data will be interpreted in different ways by different users, and frees us from trying to write &#8216;one taxonomy to rule them all&#8217;. KISS, live and let live.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Robertson</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-394</link>
		<dc:creator>James Robertson</dc:creator>
		<pubDate>Thu, 27 Nov 2008 01:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-394</guid>
		<description>Hi Brian, completely agree on the challenges inherent to taxonomies! These are hugely hard things to put into place, mostly due to the underlying organisational complexities.

Of course, if an effective taxonomy can be deployed, the benefits gained are ten times the initial cost. But I agree, there are few organisations who have mature enough information management practices to allow this to happen.

One good book to read on taxonomies has been written by Patrick Lambe in Singapore:

http://www.organisingknowledge.com/</description>
		<content:encoded><![CDATA[<p>Hi Brian, completely agree on the challenges inherent to taxonomies! These are hugely hard things to put into place, mostly due to the underlying organisational complexities.</p>
<p>Of course, if an effective taxonomy can be deployed, the benefits gained are ten times the initial cost. But I agree, there are few organisations who have mature enough information management practices to allow this to happen.</p>
<p>One good book to read on taxonomies has been written by Patrick Lambe in Singapore:</p>
<p><a href="http://www.organisingknowledge.com/" rel="nofollow">http://www.organisingknowledge.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian F</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-393</link>
		<dc:creator>Brian F</dc:creator>
		<pubDate>Thu, 27 Nov 2008 00:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-393</guid>
		<description>After working with some biggies, I&#039;m *very* wary of taxonomies. The theory of using established taxonomies and everyone being able to share data in insightful ways is great, it just doesn&#039;t work. To begin with, there&#039;s the question of which taxonomy. I was once involved with a defence project that was investigating which of say 10 main taxonomies used in Australia and by our main allies could be usefully implemented, each offering several dozen top-level categories and up to tens of thousands of individual terms. The plain fact is that no-one does or is going to use these taxonomies comprehensively or correctly. Secondly, it&#039;s impossible to know what users want from your data. You might think you&#039;re publishing country profiles or travel guides, but what people are searching for is economic data or industry insights. Finally, there&#039;s the sheer size and consequent management issues of these taxonomies. The reasons you can go to hospital fills a 1000-page book in 9-point type and keeps an office within the health department quite busy. AGIMO&#039;s new master metadata plan fills an A3 page in maybe 8-point type without even beginning to address how it will relate to other industry-specific taxonomies relevant to specific departments. All of these initiatives are fantastic in theory but will never be used by more than a handful of people. Metadata can&#039;t be generic enough.</description>
		<content:encoded><![CDATA[<p>After working with some biggies, I&#8217;m *very* wary of taxonomies. The theory of using established taxonomies and everyone being able to share data in insightful ways is great, it just doesn&#8217;t work. To begin with, there&#8217;s the question of which taxonomy. I was once involved with a defence project that was investigating which of say 10 main taxonomies used in Australia and by our main allies could be usefully implemented, each offering several dozen top-level categories and up to tens of thousands of individual terms. The plain fact is that no-one does or is going to use these taxonomies comprehensively or correctly. Secondly, it&#8217;s impossible to know what users want from your data. You might think you&#8217;re publishing country profiles or travel guides, but what people are searching for is economic data or industry insights. Finally, there&#8217;s the sheer size and consequent management issues of these taxonomies. The reasons you can go to hospital fills a 1000-page book in 9-point type and keeps an office within the health department quite busy. AGIMO&#8217;s new master metadata plan fills an A3 page in maybe 8-point type without even beginning to address how it will relate to other industry-specific taxonomies relevant to specific departments. All of these initiatives are fantastic in theory but will never be used by more than a handful of people. Metadata can&#8217;t be generic enough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ia play :: metadata fundamentals article</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-367</link>
		<dc:creator>ia play :: metadata fundamentals article</dc:creator>
		<pubDate>Wed, 12 Nov 2008 17:07:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-367</guid>
		<description>[...] James Robertson of Step Two has published Metadata fundamentals for intranets and websites [...]</description>
		<content:encoded><![CDATA[<p>[...] James Robertson of Step Two has published Metadata fundamentals for intranets and websites [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Robertson</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-332</link>
		<dc:creator>James Robertson</dc:creator>
		<pubDate>Fri, 24 Oct 2008 21:30:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-332</guid>
		<description>Hi Martin, I love your step-by-step approach to developing a taxonomy, many organisations could learn from this! The use as a glossary is a nice end-user feature to deliver from the behind-the-scenes taxonomy...</description>
		<content:encoded><![CDATA[<p>Hi Martin, I love your step-by-step approach to developing a taxonomy, many organisations could learn from this! The use as a glossary is a nice end-user feature to deliver from the behind-the-scenes taxonomy&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Robertson</title>
		<link>http://www.steptwo.com.au/papers/kmc_metadata/index.html/comment-page-1#comment-331</link>
		<dc:creator>James Robertson</dc:creator>
		<pubDate>Fri, 24 Oct 2008 21:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=1601#comment-331</guid>
		<description>Hi Kate, metadata can be used in a variety of powerful ways, including driving content reuse and automated related links.

Of course, a high level of discipline is required to make this successful. If the metadata isn&#039;t consistently high-quality, then automated uses of it can break down, or generate some strange results.

Well done on making this work, no wonder you have an award-winning intranet! :-)</description>
		<content:encoded><![CDATA[<p>Hi Kate, metadata can be used in a variety of powerful ways, including driving content reuse and automated related links.</p>
<p>Of course, a high level of discipline is required to make this successful. If the metadata isn&#8217;t consistently high-quality, then automated uses of it can break down, or generate some strange results.</p>
<p>Well done on making this work, no wonder you have an award-winning intranet! :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
