<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=us-ascii" http-equiv=Content-Type> <META name=GENERATOR content="MSHTML 8.00.6001.18702"></HEAD> <BODY> <DIV dir=ltr align=left><SPAN class=625193617-22082009><FONT color=#000080 size=2 face=Arial>Back when I was designing and building information management systems for NASA, I investigated something called the Dublin Core metadata standard for creating and maintaining online descriptions of multimedia material. (Google it or or see <A href="http://en.wikipedia.org/wiki/Dublin_Core">http://en.wikipedia.org/wiki/Dublin_Core</A>). It's used by libraries. There are front-end search and query apps that understand this metadata standard. (I decided the standard was overkill for the Martian data I was managing.)</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=625193617-22082009><FONT color=#000080 size=2 face=Arial></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=625193617-22082009><FONT color=#000080 size=2 face=Arial>I believe the CHM archives use the Dublin Core, but I'm not sure.</FONT></SPAN></DIV> <DIV dir=ltr align=left><SPAN class=625193617-22082009><FONT color=#000080 size=2 face=Arial></FONT></SPAN> </DIV> <DIV dir=ltr align=left><SPAN class=625193617-22082009><FONT color=#000080 size=2 face=Arial>-- Ron</FONT></SPAN></DIV><BR> <BLOCKQUOTE style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"> <DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left> <HR tabIndex=-1> <FONT size=2 face=Tahoma><B>From:</B> scc_active-bounces@computerhistory.org [mailto:scc_active-bounces@computerhistory.org] <B>On Behalf Of </B>Henry Gladney<BR><B>Sent:</B> Saturday, August 22, 2009 6:24 AM<BR><B>To:</B> Tim Shoppa<BR><B>Cc:</B> scc_active@computerhistory.org<BR><B>Subject:</B> Re: [SPG_Active_Members] Your letter of 29th July<BR></FONT><BR></DIV> <DIV></DIV>In saying "you've always pushed hard for formalizing the software collection process," you express a misunderstanding.  I'm looking for something else--the ability of repositories and scholars to share stuff in those particular cases in which <U><B>they</B><B> want</B></U> to share, and to annotate by links that show "interesting" relationships of stuff as well as other metadata, sharing those annotations without confusing them with the original materials.  In this, "share" might or might not involve copying.<BR><BR>To achieve this without limiting what any institution or individual is able to do and also to support building on other people's similar work requires that certain aspects of metadata follow common conventions.  I.e., it helps immensely to have common methods/representations for how metadata is linked to data and other metadata.  E.g., a reason that you can productively use any library in the world is that the libraries use common conventions for their catalogues and for library-annotations on the spines of books.<BR><BR>Another way of saying the same thing is that a museum collection is useful only if it is a great deal more than a pile of stuff collected into a single room.  <BR><BR>Your "loose coalition" would not work without shared language among its members.  An example of shared language might be a common way of identifying works so that anybody can clearly see which are identical and which are different, and also which different ones are related to each other.<BR clear=all><BR>Best wishes, Henry<BR><BR>H.M. Gladney, Ph.D.     <A href="http://home.pacbell.net/hgladney/">http://home.pacbell.net/hgladney/</A>   (408)867-3933<BR><BR><BR> <DIV class=gmail_quote>On Sat, Aug 22, 2009 at 05:37, Tim Shoppa <SPAN dir=ltr><<A href="mailto:shoppa@trailing-edge.com">shoppa@trailing-edge.com</A>></SPAN> wrote:<BR> <BLOCKQUOTE style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class=gmail_quote> <DIV class=im>Henry Gladney <<A href="mailto:hgladney@gmail.com">hgladney@gmail.com</A>> wrote:<BR></DIV> <DIV class=im>> This is because I am disappointed that CHM some time ago quit credible<BR>> interest in preserving software, which I regard as of commensurate<BR>> importance to the areas that it is investing in.  This happened<BR>> notwithstanding the fact that there are clear ways of achieving this<BR>> relatively inexpensively and the efforts of the now-suspended volunteer<BR>> Software Preservation Group.<BR><BR></DIV>A couple years ago the SPG at CHM sponsored "The Attic and the Parlor",<BR>which made it clear to me that they appreciate the loose and broad<BR>coalition of individuals and corporations and institutions that<BR>preserve software.<BR><BR>I also got to hear some of the difficulties (esp. legal ones) and triumphs<BR>(CHM's then-new software curator's results) of doing this in the CHM<BR>framework.<BR><BR>Henry, it seems you've always pushed hard for formalizing the software<BR>collection process through the CHM. I've come to the realization that the base<BR>of interesting software "in the wild" is tremendously huge and often<BR>extremely specialized. I think a loose coalition of software archives<BR>and archivists, both professional and non-professional, is the right solution<BR>at this point.<BR><FONT color=#888888><BR>Tim.<BR></FONT></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>