<?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>Invisible Fist &#187; Digital Liability</title>
	<atom:link href="http://www.invisiblefist.com/tag/digital-liability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.invisiblefist.com</link>
	<description>People-Compliant Content</description>
	<lastBuildDate>Sun, 29 Aug 2010 03:29:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>The Digital Liability</title>
		<link>http://www.invisiblefist.com/2009/08/26/the-digital-liability/</link>
		<comments>http://www.invisiblefist.com/2009/08/26/the-digital-liability/#comments</comments>
		<pubDate>Wed, 26 Aug 2009 11:48:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[CM, DAM. ECM...]]></category>
		<category><![CDATA[Digital Asset Management]]></category>
		<category><![CDATA[Digital Liability]]></category>

		<guid isPermaLink="false">http://www.invisiblefist.com/?p=15</guid>
		<description><![CDATA[During my time in the creative services and Web technology industries, a point of frustration has been that a lot of potentially productive energy is squandered as practitioners argue about whether a solution is one or more of the following: Web Content Management (WCM) or Digital Asset Management (DAM) or Enterprise Content Management (ECM) or [...]]]></description>
			<content:encoded><![CDATA[<p>During my time in the creative services and Web technology industries, a point of frustration has been  that a lot of potentially productive energy is squandered as  practitioners argue about whether a solution is one or more of the following:</p>
<ul>
<li>Web Content Management (WCM)  or</li>
<li>Digital Asset Management (DAM) or</li>
<li>Enterprise Content Management (ECM) or</li>
<li>Learning Content Management (LCM) or</li>
<li>Some Other Acronym</li>
</ul>
<p>So that we may bypass such distractions, let me say the following:</p>
<ul>
<li> All digital assets are content; however&#8230;</li>
<li>Not all content can be considered an asset.</li>
<li>Content must provide organizational value to be considered digital asset.</li>
<p>That being said, my question is what makes a digital liability?</ul>
<p>There many attributes about a content item that can diminish its value. These are a few that come to mind:</p>
<ul>
<li>Digital master is of insufficient resolution, improper color space, or inadequate frame rate (for video).</li>
<li>Content is improperly described by metadata.</li>
<li>Multiple replicas (or approximations) of a content item are stored many different locations. This can include copies  nested in files system directories or stored in offline media.</li>
<li>Organizational technologies or processes don&#8217;t provide adequate reuse/repurposing opportunities.</li>
<li>Inconsistent modifications among language derivatives of content items.</li>
<li>Orphaned files where renditions, or proxies become detached from their source files</li>
<li>Inadequate archival policy</li>
<li>Compound content (from Quark, InDesign, etc.) that is &#8216;unaware&#8217; of the locations of its supporting files such as photos and illustrations.</li>
<li>Bit Rot. This is the case where the storage medium (tape, optical disk, etc.) starts to degrade over time causing data loss.</li>
</ul>
<p>In short, if you content can&#8217;t be found, used, transformed, or shared then it is a digital liability.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.invisiblefist.com/2009/08/26/the-digital-liability/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
