<?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>Technology of Content &#187; metadata</title>
	<atom:link href="http://blog.technologyofcontent.com/tag/metadata/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.technologyofcontent.com</link>
	<description>Ramblings on the technology of content management</description>
	<lastBuildDate>Sun, 25 Apr 2010 21:45:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Metadata is not what it used to be</title>
		<link>http://blog.technologyofcontent.com/2009/08/metadata-is-not-what-it-used-to-be/</link>
		<comments>http://blog.technologyofcontent.com/2009/08/metadata-is-not-what-it-used-to-be/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 14:54:05 +0000</pubDate>
		<dc:creator>justin</dc:creator>
				<category><![CDATA[CMS]]></category>
		<category><![CDATA[metadata]]></category>

		<guid isPermaLink="false">http://blog.technologyofcontent.com/?p=95</guid>
		<description><![CDATA[
  &#8220;Spent a week in a dusty library waiting for some words to jump at me&#8221; Camera Obscura.


Kas Thomas in his contribution to Julian Wraith&#8217;s popular thread on the future of content management really managed to make me disagree, the first of the posts that has!

The theme of this blog (yes it has got [...]]]></description>
			<content:encoded><![CDATA[<blockquote>
  <p>&#8220;Spent a week in a dusty library waiting for some words to jump at me&#8221; Camera Obscura.</p>
</blockquote>

<p><a href="http://www.cmswatch.com/Trends/1679-Future-CMS-Metadata">Kas Thomas</a> in his contribution to <a href="http://www.julianwraith.com/?p=328">Julian Wraith&#8217;s popular thread on the future of content management</a> really managed to make me disagree, the first of the posts that has!</p>

<p>The theme of this blog (yes it has got one) is that content management is changing as the web way of working starts to infiltrate the enterprise. And the web way of metadata is not what the old document oriented way was.</p>

<p>Kas says &#8220;Keeping knowledge about a file separate from the file itself is a hugely important concept.&#8221;</p>

<p>Looking at that point first. Look at any newish document format, from <a href="http://en.wikipedia.org/wiki/PDF/A">PDF/A</a> to <a href="http://en.wikipedia.org/wiki/EXIF">EXIF</a> via the HTML <code>meta</code> tag, even a Word document and you will find embedded metadata. Remember that documents are emailed around, generally get lost. Metadata is the dog collar with a name and phone number on, saying version me and send me home. This trend is not going away, documents are becoming self contained.</p>

<p>Kas then continues &#8220;A file&#8217;s metadata becomes its interface to the outside world. It&#8217;s like a service descriptor.&#8221; That is simply not the way the web works. Resources use self describing formats like HTML for core data, and then all the other important metadata is linking information. It used to be that you had a blob file type and a program that could understand it, that was the basis for the desktop architecture, but that is not the case any more, even on the desktop you have a choice of applications that can understand a given file type, and your choice depends on what you can do with them. The web architecture goes much further, and resources become fully self-describing, a browser can understand all the web as every resource carries its own description, and bundled code to help you interpret it. A web page is its own service descriptor, and defines application state through hyperlinks. The web architecture has never had service descriptions.</p>

<p>There is one vital part of metadata that is not kept with a file, that is the link. Kas says &#8220;content, on the whole, is becoming richer, less structured&#8221;, missing out completely on the big picture that content is being structured by the imposition of links onto it, by its transformation into a hypertext, that creates a much richer structure than the individual documents have in themselves. Documents contain metadata about other documents in the form of links. The semantic web project is an attempt to add further richness to this structure. &#8220;What does the trend toward richer, less structured content mean for management of content?&#8221; well that means that content management is going to be about managing those links and relations between items, a lot more than it is now, when it came from a background of just managing documents, each an isolated item.</p>

<p>In a way that does come back to &#8220;Keeping knowledge about a file separate from the file itself&#8221; but not at all in the way Kas was trying to argue. Now time to link this to his argument to create a structured discussion&#8230;</p>

<p><a href="http://www.threadless.com/product/1053/Now_That_s_Dope"><img src="http://www.threadless.com//product/1053/zoom.gif" width="450px"/></a></p>

<p>6f82f1d2683dc522545efe863e5d2b73</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.technologyofcontent.com/2009/08/metadata-is-not-what-it-used-to-be/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>
