Dublin Core has long since been superceded, even for the limited kinds of information it provides, e.g., by the Library of Congress defined Metadata Encoding Standard which has been standardized by ISO.<br><br>It does nothing whatsoever about essentials such as serviceable identifiers for saved objects, shareable linking, and dozens of other critical aspects.<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 10:44, Ronald Mak <span dir="ltr"><<a href="mailto:ron@apropos-logic.com">ron@apropos-logic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font color="#000080" face="Arial" size="2">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" target="_blank">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><font color="#000080" face="Arial" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#000080" face="Arial" size="2">I believe the CHM archives use the Dublin Core, but I'm not
sure.</font></span></div>
<div dir="ltr" align="left"><span><font color="#000080" face="Arial" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#000080" face="Arial" size="2">-- Ron</font></span></div><br>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div dir="ltr" align="left" lang="en-us">
<hr>
<font face="Tahoma" size="2"><div class="im"><b>From:</b> <a href="mailto:scc_active-bounces@computerhistory.org" target="_blank">scc_active-bounces@computerhistory.org</a>
[mailto:<a href="mailto:scc_active-bounces@computerhistory.org" target="_blank">scc_active-bounces@computerhistory.org</a>] <b>On Behalf Of </b>Henry
Gladney<br></div><b>Sent:</b> Saturday, August 22, 2009 6:24 AM<br><b>To:</b> Tim
Shoppa<br><b>Cc:</b> <a href="mailto:scc_active@computerhistory.org" target="_blank">scc_active@computerhistory.org</a><div class="im"><br><b>Subject:</b> Re:
[SPG_Active_Members] Your letter of 29th July<br></div></font><br></div><div><div></div><div class="h5">
<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/" target="_blank">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" target="_blank">shoppa@trailing-edge.com</a>></span>
wrote:<br>
<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
<div>Henry Gladney <<a href="mailto:hgladney@gmail.com" target="_blank">hgladney@gmail.com</a>> wrote:<br></div>
<div>> 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></div></div></blockquote></div>
</blockquote></div><br>