<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>iterating toward openness &#187; metadata</title>
	<atom:link href="http://opencontent.org/blog/archives/tag/metadata/feed" rel="self" type="application/rss+xml" />
	<link>http://opencontent.org/blog</link>
	<description>pragmatism over zeal</description>
	<lastBuildDate>Fri, 03 Feb 2012 22:21:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>START-ing to think about user-contributed metadata</title>
		<link>http://opencontent.org/blog/archives/331</link>
		<comments>http://opencontent.org/blog/archives/331#comments</comments>
		<pubDate>Fri, 11 May 2007 12:58:51 +0000</pubDate>
		<dc:creator>david</dc:creator>
				<category><![CDATA[metadata]]></category>

		<guid isPermaLink="false">http://opencontent.org/blog/archives/331</guid>
		<description><![CDATA[Phil describes Prabhakar Raghavan&#8217;s keynote about Web N.0 in some detail (at WWW2007), including the following framework for thinking about user-contributed metadata. User-generated metadata is growing. Anchortext and tags are growing at the rate of 100 Mb/day. Pageviews are around &#8230; <a href="http://opencontent.org/blog/archives/331">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Phil <a href="http://www.windley.com/archives/2007/05/prabhakar_raghavan_on_web_n0.shtml">describes</a> Prabhakar Raghavan&#8217;s keynote about Web N.0 in some detail (at WWW2007), including the following framework for thinking about user-contributed metadata.</p>
<blockquote><p>User-generated metadata is growing. Anchortext and tags are growing at the rate of 100 Mb/day. Pageviews are around 50-100 Gb/day. Reviews and ratings are small. All of these, are important, but only anchors are central to how people work on the Web.</p>
<p>START metadata:</p>
<p>    * Star: I like this<br />
    * Tag: creating tags on pictures, etc.<br />
    * Access: you view a page (in a way I can see)<br />
    * Routing: forwarding things to friends<br />
    * Text: write a review, blog article, etc.</p>
<p>These are in order of increasing engagement.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://opencontent.org/blog/archives/331/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Metadata is a Derivative Work</title>
		<link>http://opencontent.org/blog/archives/281</link>
		<comments>http://opencontent.org/blog/archives/281#comments</comments>
		<pubDate>Wed, 25 Oct 2006 21:32:45 +0000</pubDate>
		<dc:creator>david</dc:creator>
				<category><![CDATA[open content]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[open-education]]></category>

		<guid isPermaLink="false">http://opencontent.org/blog/archives/281</guid>
		<description><![CDATA[At the OCW Consortium meetings at the Open Education conference in September, I asked whether other OCWs had explicitly CC licensed their metadata. In talking to people then and since then, the general response is best characterized as hemming and &#8230; <a href="http://opencontent.org/blog/archives/281">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>At the OCW Consortium meetings at the <a href="http://cosl.usu.edu/conferences/opened2006/">Open Education conference</a> in September, I asked whether other OCWs had explicitly CC licensed their metadata. In talking to people then and since then, the general response is best characterized as hemming and hawing. Very folks appear to have considered this licensing status of their metadata. But this seems like a very clear issue to my very simple mind. I mean, what&#8217;s the point of creating open access materials if you&#8217;re going to hoard your metadata and make it hard for people to find the materials? (This same problem is what seems to have stymied the NSDL for a few years in the early 2000s.)</p>
<p>In thinking about this issue again today, it occurred to me that metadata are derivative works based on the original materials. What this means is that, for those OCW or OER sharing entities that don&#8217;t explicitly CC-license their metadata, the community could create metadata based on the materials themselves (to replace the privately-held metadata), which would obviously be a derivative work, and would therefore automatically invoke the Share-Alike clause so many OCW and OER providers use for their materials. And that&#8217;s how we get CC-licensed metadata. </p>
<p>Hopefully it doesn&#8217;t come to that, and open educational resource providers will do the right thing and save the community the extra work&#8230; We&#8217;d rather spend our time using the materials in our classrooms or communities than using it to *re*create their *existing* metadata. But the notion of metadata as derivative work seems like an interesting one worth exploring.</p>
]]></content:encoded>
			<wfw:commentRss>http://opencontent.org/blog/archives/281/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>On Metacrap</title>
		<link>http://opencontent.org/blog/archives/256</link>
		<comments>http://opencontent.org/blog/archives/256#comments</comments>
		<pubDate>Fri, 31 Mar 2006 17:31:57 +0000</pubDate>
		<dc:creator>david</dc:creator>
				<category><![CDATA[folksonomy]]></category>
		<category><![CDATA[metadata]]></category>

		<guid isPermaLink="false">http://opencontent.org/blog/archives/256</guid>
		<description><![CDATA[I was recently asked what I thought of Cory Doctorow&#8217;s classic Metacrap paper. He was, of course, dead on when he wrote it. The nagging question at the time was &#8220;what alternatives do we have?&#8221; And the sad answer was &#8230; <a href="http://opencontent.org/blog/archives/256">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I was recently asked what I thought of Cory Doctorow&#8217;s classic <a href="http://www.well.com/~doctorow/metacrap.htm">Metacrap</a> paper. He was, of course, dead on when he wrote it. The nagging question at the time was &#8220;what alternatives do we have?&#8221; And the sad answer was &#8220;not many.&#8221;</p>
<p><span id="more-256"></span></p>
<p>Creating metadata, as traditionally conceived, is the ultimate form of unidirectional asynchronous communication (aka &#8211; a message in a bottle). The cataloger attempts to divine a number of individuals who, at some point in the future, are trying to locate a particular resource or one like it, and asks him/herself, &#8220;how could I best describe this resource so that these imaginary inhabitants of the future will be able to find it?&#8221; </p>
<p>Best practice has been to create controlled vocabularies, publish those so that future searchers will be able to find them, and mandate and guarantee consistency of application of these terms to resources by catalogers. The description of the controlled vocabulary becomes the secret decoder ring that an individual needs in order to find resources. Quite without intent, this practice doubles the searcher&#8217;s task for all but the most trivial searchers (like finding a book when you know the author&#8217;s name): now a searcher must first find the decoder ring; then, they must figure out how to use it to find the resource they&#8217;re looking for. </p>
<p>On very rare occasions, and I mean that seriously, technology comes riding to the rescue. Today we do have at least one viable alternative to the scenario Cory outlined what seems like an eternity ago. <a href="http://del.icio.us/">Delicious</a>, <a href="http://flickr.com/">Flickr</a>, and other sites show the first step. First, instead of having people catalog resources they know about for others to find, they let people catalog things they know about so that *they* can find them again later. No imagining future searchers; no wondering what terms will be meaningful to them. Also, no incentive problems &#8211; why spend the time cataloging things for the possible benefit of imaginary people in the future, when you could catalog things for your own benefit? </p>
<p>Delicious and Flickr get a quarter of the way to the last step. When I tag a resource in delicious with &#8220;python&#8221; or &#8220;ruby&#8221;, the tag itself becomes a link to all the resources other people have tagged with the same term. That&#8217;s pretty useful. What would be even more useful, and we&#8217;re going to be showing this in May, is a collaborative filtering system or recommender system (think Amazon&#8217;s book recommendations) that matches you with other people like you based on your actual tagging behavior. You just go on bookmarking, blogging, and tagging for your own benefit, and at no extra cost to you the system will help you find other resources and, even more valuable, like-minded people. </p>
<p>In other words, one solution to the problem Cory outlined is the free and open sharing of catalog data created by an individual for their own use, and the automation of person to person recommendations of resources and people based on that data. Notice that folksonomies don&#8217;t solve the problem by themselves &#8211; free and open access to a large collection of folksonomic data is necessary. We&#8217;re calling the work we do in this area &#8220;folksemantic&#8221; because it blends folksonomic approaches with semantic web approaches (which strictly speaking shouldn&#8217;t work &#8211; which is why we love it).</p>
]]></content:encoded>
			<wfw:commentRss>http://opencontent.org/blog/archives/256/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

