<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Information Context (a.k.a Code/Data Duality)</title>
	<atom:link href="http://www.forensicblog.org/2006/09/27/information-context-aka-codedata-duality/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.forensicblog.org/2006/09/27/information-context-aka-codedata-duality/</link>
	<description>Digital forensics from the view of a computer scientist</description>
	<lastBuildDate>Fri, 26 Nov 2010 21:38:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: any</title>
		<link>http://www.forensicblog.org/2006/09/27/information-context-aka-codedata-duality/comment-page-1/#comment-2056</link>
		<dc:creator>any</dc:creator>
		<pubDate>Thu, 23 Apr 2009 05:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://forensicblog.org/2006/12/21/information-context-aka-codedata-duality/#comment-2056</guid>
		<description>域名：bags.shoppingsam.com
描述：&lt;a href=&quot;http://bags.shoppingsam.com&quot; rel=&quot;nofollow&quot;&gt;Chanel/Gucci/Chloe/Luis Victton Bags Online Dealer; 38% Discount Original Products On Sale; Free &amp; Fast Shipping; Order Now!!!&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>域名：bags.shoppingsam.com<br />
描述：<a href="http://bags.shoppingsam.com" rel="nofollow">Chanel/Gucci/Chloe/Luis Victton Bags Online Dealer; 38% Discount Original Products On Sale; Free &amp; Fast Shipping; Order Now!!!</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forensic Computing &#187; How digital forensics relates to computing</title>
		<link>http://www.forensicblog.org/2006/09/27/information-context-aka-codedata-duality/comment-page-1/#comment-3</link>
		<dc:creator>Forensic Computing &#187; How digital forensics relates to computing</dc:creator>
		<pubDate>Fri, 26 Jan 2007 05:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://forensicblog.org/2006/12/21/information-context-aka-codedata-duality/#comment-3</guid>
		<description>[...] There is one other concept to deal with before focusing on digital forensics, and that is how algorithms work with information. In order for an algorithm to transform and describe information, the information has to be encoded in some manner. For example, the letter &#8220;A&#8221; can be encoded (in ASCII) as the number 0&#215;41 (65). The number 0&#215;41 can then be represented in binary as 01000001. This binary number can then be encoded as the different positions of magnets and stored on a hard disk. Implicit in the structure of the algorithm, is how the algorithm decodes the representation of information. This means that given just raw the encoding of information (e.g. a stream of bits) we don&#8217;t know what information is represented, we still need to understand (to some degree) how the information is used by the algorithm. I blogged about this a bit in a previous post &#8220;Information Context (a.k.a. Code/Data Duality)&#8220;. [...]</description>
		<content:encoded><![CDATA[<p>[...] There is one other concept to deal with before focusing on digital forensics, and that is how algorithms work with information. In order for an algorithm to transform and describe information, the information has to be encoded in some manner. For example, the letter &#8220;A&#8221; can be encoded (in ASCII) as the number 0&#215;41 (65). The number 0&#215;41 can then be represented in binary as 01000001. This binary number can then be encoded as the different positions of magnets and stored on a hard disk. Implicit in the structure of the algorithm, is how the algorithm decodes the representation of information. This means that given just raw the encoding of information (e.g. a stream of bits) we don&#8217;t know what information is represented, we still need to understand (to some degree) how the information is used by the algorithm. I blogged about this a bit in a previous post &#8220;Information Context (a.k.a. Code/Data Duality)&#8220;. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

