<?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: Information as an Object</title>
	<atom:link href="http://archivemati.ca/2007/02/05/information-as-an-object/feed/" rel="self" type="application/rss+xml" />
	<link>http://archivemati.ca/2007/02/05/information-as-an-object/</link>
	<description>archives. technology.</description>
	<lastBuildDate>Sun, 18 Jan 2009 06:37:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Peter Van Garderen</title>
		<link>http://archivemati.ca/2007/02/05/information-as-an-object/comment-page-1/#comment-122</link>
		<dc:creator>Peter Van Garderen</dc:creator>
		<pubDate>Wed, 14 Feb 2007 18:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://archivemati.ca/?p=65#comment-122</guid>
		<description>Hi Andrew,

Thanks for you thoughtful feedback. Yes, I remember meeting you in Ottawa last May. You did a presentation on the SHERPA-DP project right?

Before I launch into my comments I just want to add the disclaimer that my definitions and opinions are based within the viewpoint of my own research domain. They may not work everywhere. However, I have tried to start from scratch and work my way back up and that at least provides for some interesting reading as you so kindly noted (at least for digital preservation geeks ;-)

1) RE: &quot;Information&quot;: I am trying to avoid the word &lt;em&gt;data&lt;/em&gt; altogether. It&#039;s become a little clouded. Instead I am using &lt;em&gt;content&lt;/em&gt; in combination with the concept of &lt;em&gt;message&lt;/em&gt;, &lt;em&gt;signs&lt;/em&gt;, &lt;em&gt;symbols&lt;/em&gt;, or &lt;em&gt;patterns&lt;/em&gt;. I define content as &quot;the message that is communicated by information.&quot;

2) RE: &quot;Context&quot;: I agree 100% that context must be present along with content and structure, otherwise we are not dealing with information but just an incomprehensible message or, if you like, just a bunch of data.

I think I made that point in the section above entitled &quot;The Message Has No Meaning Without Context&quot; as well as in the &lt;a href=&quot;http://archivemati.ca/2007/01/29/what-is-information-anyway/&quot;&gt;previous post on Information&lt;/a&gt; in the section entitled &quot;The Importance of Context and Knowledge&quot;. But maybe I should clarify it more simply somewhere in there: no context =  no information.

3) RE: &quot;Digital&quot;: In the &lt;a href=&quot;http://archivemati.ca/2007/02/12/the-anatomy-of-a-digital-information-object/&quot;&gt;next post&lt;/a&gt; I look a little closer at Digital Information Objects. There I point out that there is no theoretical difference between an information object in analogue or digital form. However, in reality managing the content, structure, and context of digital information objects is much more complex and vulnerable to loss. On top of that we have to accept the enigma that the digital object&#039;s structure exists but we can never be truly specific about where (see the section &#039;If a Digital Information Object Falls in the Forestâ€¦&#039;).

4) RE: &quot;Location of Contextual Information&quot;: I think it is commonly accepted in the digital preservation world that contextual information does not have to be embedded with the digital object (both OAIS and ISO15489 allow for the linking to external or remote metadata repositories/databases). However, if the links to the metadata is lost then we are back to square one and we are once again not dealing theoretically with &lt;em&gt;information&lt;/em&gt; but just with a bunch of content and possibly some structure. So sure, embedding is probably less risky from a preservation point-of-view but it is not a requirement, as long as the contextual information can be brought together with the content and structure at the point of access.

5) RE: &quot;OAIS&quot;: Yes, like most of our colleagues I have been guided or influenced by the OAIS concepts for quite some time now. The concept of the Information Package (whether AIP or DIP) is very useful. In the course of actually developing a physical data model that implements these concepts I have stripped down and simplified the Information Package (to the  point that I can&#039;t call it an OAIS Information Package anymore). Quite simply, when I refer to &lt;em&gt;content&lt;/em&gt;, I am referring to the OAIS Content Data Object. When I am referring to &lt;em&gt;contextual information&lt;/em&gt;, I am referring to the OAIS Representation Information, Preservation Descriptive Information, Packaging Information, and Descriptive Information. Some or all of this contextual information is required to give the digital information object its structure but, once again, it is not the actual structure.</description>
		<content:encoded><![CDATA[<p>Hi Andrew,</p>
<p>Thanks for you thoughtful feedback. Yes, I remember meeting you in Ottawa last May. You did a presentation on the SHERPA-DP project right?</p>
<p>Before I launch into my comments I just want to add the disclaimer that my definitions and opinions are based within the viewpoint of my own research domain. They may not work everywhere. However, I have tried to start from scratch and work my way back up and that at least provides for some interesting reading as you so kindly noted (at least for digital preservation geeks <img src='http://archivemati.ca/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>1) RE: &#8220;Information&#8221;: I am trying to avoid the word <em>data</em> altogether. It&#8217;s become a little clouded. Instead I am using <em>content</em> in combination with the concept of <em>message</em>, <em>signs</em>, <em>symbols</em>, or <em>patterns</em>. I define content as &#8220;the message that is communicated by information.&#8221;</p>
<p>2) RE: &#8220;Context&#8221;: I agree 100% that context must be present along with content and structure, otherwise we are not dealing with information but just an incomprehensible message or, if you like, just a bunch of data.</p>
<p>I think I made that point in the section above entitled &#8220;The Message Has No Meaning Without Context&#8221; as well as in the <a href="http://archivemati.ca/2007/01/29/what-is-information-anyway/">previous post on Information</a> in the section entitled &#8220;The Importance of Context and Knowledge&#8221;. But maybe I should clarify it more simply somewhere in there: no context =  no information.</p>
<p>3) RE: &#8220;Digital&#8221;: In the <a href="http://archivemati.ca/2007/02/12/the-anatomy-of-a-digital-information-object/">next post</a> I look a little closer at Digital Information Objects. There I point out that there is no theoretical difference between an information object in analogue or digital form. However, in reality managing the content, structure, and context of digital information objects is much more complex and vulnerable to loss. On top of that we have to accept the enigma that the digital object&#8217;s structure exists but we can never be truly specific about where (see the section &#8216;If a Digital Information Object Falls in the Forestâ€¦&#8217;).</p>
<p>4) RE: &#8220;Location of Contextual Information&#8221;: I think it is commonly accepted in the digital preservation world that contextual information does not have to be embedded with the digital object (both OAIS and ISO15489 allow for the linking to external or remote metadata repositories/databases). However, if the links to the metadata is lost then we are back to square one and we are once again not dealing theoretically with <em>information</em> but just with a bunch of content and possibly some structure. So sure, embedding is probably less risky from a preservation point-of-view but it is not a requirement, as long as the contextual information can be brought together with the content and structure at the point of access.</p>
<p>5) RE: &#8220;OAIS&#8221;: Yes, like most of our colleagues I have been guided or influenced by the OAIS concepts for quite some time now. The concept of the Information Package (whether AIP or DIP) is very useful. In the course of actually developing a physical data model that implements these concepts I have stripped down and simplified the Information Package (to the  point that I can&#8217;t call it an OAIS Information Package anymore). Quite simply, when I refer to <em>content</em>, I am referring to the OAIS Content Data Object. When I am referring to <em>contextual information</em>, I am referring to the OAIS Representation Information, Preservation Descriptive Information, Packaging Information, and Descriptive Information. Some or all of this contextual information is required to give the digital information object its structure but, once again, it is not the actual structure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://archivemati.ca/2007/02/05/information-as-an-object/comment-page-1/#comment-121</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 13 Feb 2007 23:55:52 +0000</pubDate>
		<guid isPermaLink="false">http://archivemati.ca/?p=65#comment-121</guid>
		<description>Hi Peter

I think we met an an IS&#038;T Conference? Anyway, I&#039;m wondering about your use of the word &#039;information&#039; as opposed to data in the case of digital objects. Sure digital objects contain content (data) and structure but often they do not contain all the contextual information necessary to understand them. In that case does that mean they are not information objects? And they cannot be used on their own as paper records can - they must be mediated by hardware and software oeprating together with the data object to produce the record/information.

In archival institutions the information object will most often be the actual digital data object plus a lot of contextual metadata that lives somewhere else. Does this mean that archival institutions are not preserving information objects? I guess you have looked at the OAIS reference model? Perhaps the concept of the archival information package (AIP) could be useful for you?

Anyway, this is interesting reading - keep it up!

cheers
Andrew Wilson</description>
		<content:encoded><![CDATA[<p>Hi Peter</p>
<p>I think we met an an IS&#38;#38;T Conference? Anyway, I&#8217;m wondering about your use of the word &#8216;information&#8217; as opposed to data in the case of digital objects. Sure digital objects contain content (data) and structure but often they do not contain all the contextual information necessary to understand them. In that case does that mean they are not information objects? And they cannot be used on their own as paper records can &#8211; they must be mediated by hardware and software oeprating together with the data object to produce the record/information.</p>
<p>In archival institutions the information object will most often be the actual digital data object plus a lot of contextual metadata that lives somewhere else. Does this mean that archival institutions are not preserving information objects? I guess you have looked at the OAIS reference model? Perhaps the concept of the archival information package (AIP) could be useful for you?</p>
<p>Anyway, this is interesting reading &#8211; keep it up!</p>
<p>cheers<br />
Andrew Wilson</p>
]]></content:encoded>
	</item>
</channel>
</rss>

