<?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: Oh, good! More metadata specifications!</title>
	<atom:link href="http://www.darcynorman.net/2006/01/30/oh-good-more-metadata-specifications/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.darcynorman.net/2006/01/30/oh-good-more-metadata-specifications/</link>
	<description>apparently much happier in person</description>
	<lastBuildDate>Fri, 20 Nov 2009 14:35:07 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott Leslie</title>
		<link>http://www.darcynorman.net/2006/01/30/oh-good-more-metadata-specifications/#comment-81153</link>
		<dc:creator>Scott Leslie</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">418976153#comment-81153</guid>
		<description>What would have been useful for these folks to consider (maybe they have?) is actual usage data from existing repositories (and applications) that have used the existing LOM - what fields did people actual complete, and what fields did people actually try to use in creating complex queries. You did track all of this in Careo, right? ;-) If we set aside the issue of gathering the darn stuff in the first place (which is setting aside a whole lot!) one thing that&#039;s always frustrated me about the LOM was how incredibly abstract and arcane some of the fields seemed to be, like it was invented by a bunch of people sitting round wondering &quot;if people could search for these little atomic bits of learning using any field conceivable, what would they use.&quot; Oh wait, that is how it was invented!</description>
		<content:encoded><![CDATA[<p>What would have been useful for these folks to consider (maybe they have?) is actual usage data from existing repositories (and applications) that have used the existing LOM &#8211; what fields did people actual complete, and what fields did people actually try to use in creating complex queries. You did track all of this in Careo, right? <img src='http://www.darcynorman.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  If we set aside the issue of gathering the darn stuff in the first place (which is setting aside a whole lot!) one thing that&#8217;s always frustrated me about the LOM was how incredibly abstract and arcane some of the fields seemed to be, like it was invented by a bunch of people sitting round wondering &#8220;if people could search for these little atomic bits of learning using any field conceivable, what would they use.&#8221; Oh wait, that is how it was invented!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
