attachment:KernelMetadataERCApplicationProfiles1_4a.htm of FrontPage

Attachment 'KernelMetadataERCApplicationProfiles1_4a.htm'

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head>


<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<meta name="robots" content="index,nofollow"><title>Kernel Metadata/ERC and Dublin Core Application Profiles</title>


</div>

<STYLE type=text/css>
BODY {
	FONT-SIZE: small; MARGIN: 2em; COLOR: #000; FONT-FAMILY: verdana, charcoal, helvetica, arial, sans-serif; BACKGROUND-COLOR: #fff
}
H1 {
	FONT-WEIGHT: bold; FONT-STYLE: normal; FONT-FAMILY: helvetica, monaco, "MS Sans Serif", arial, sans-serif
}
H2 {
	FONT-WEIGHT: bold; FONT-STYLE: normal; FONT-FAMILY: helvetica, monaco, "MS Sans Serif", arial, sans-serif
}
H3 {
	FONT-WEIGHT: bold; FONT-STYLE: normal; FONT-FAMILY: helvetica, monaco, "MS Sans Serif", arial, sans-serif
}
H4 {
	FONT-WEIGHT: bold; FONT-STYLE: normal; FONT-FAMILY: helvetica, monaco, "MS Sans Serif", arial, sans-serif
}
H5 {
	FONT-WEIGHT: bold; FONT-STYLE: normal; FONT-FAMILY: helvetica, monaco, "MS Sans Serif", arial, sans-serif
}
H6 {
	FONT-WEIGHT: bold; FONT-STYLE: normal; FONT-FAMILY: helvetica, monaco, "MS Sans Serif", arial, sans-serif
}
H1 {
	COLOR: #900; BACKGROUND-COLOR: transparent; TEXT-ALIGN: right
}
H3 {
	COLOR: #333; BACKGROUND-COLOR: transparent
}
TD.RFCbug {
	FONT-SIZE: x-small; VERTICAL-ALIGN: middle; WIDTH: 30px; PADDING-TOP: 2px; HEIGHT: 30px; BACKGROUND-COLOR: #000; TEXT-ALIGN: justify; TEXT-DECORATION: none
}
TD.RFCbug SPAN.RFC {
	FONT-WEIGHT: bold; COLOR: #666; FONT-FAMILY: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif
}
TD.RFCbug SPAN.hotText {
	FONT-WEIGHT: normal; COLOR: #fff; FONT-FAMILY: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif; TEXT-ALIGN: center
}
TABLE.TOCbug {
	WIDTH: 30px; HEIGHT: 15px
}
TD.TOCbug {
	WIDTH: 30px; COLOR: #fff; HEIGHT: 15px; BACKGROUND-COLOR: #900; TEXT-ALIGN: center
}
TD.TOCbug A {
	FONT-WEIGHT: bold; FONT-SIZE: x-small; COLOR: #fff; FONT-FAMILY: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif; BACKGROUND-COLOR: transparent; TEXT-DECORATION: none
}
TD.header {
	FONT-SIZE: x-small; VERTICAL-ALIGN: top; WIDTH: 33%; COLOR: #fff; FONT-FAMILY: arial, helvetica, sans-serif; BACKGROUND-COLOR: #666
}
TD.author {
	FONT-WEIGHT: bold; FONT-SIZE: x-small; MARGIN-LEFT: 4em
}
TD.author-text {
	FONT-SIZE: x-small
}
A.info {
	Z-INDEX: 24; POSITION: relative; TEXT-DECORATION: none
}
A.info:hover {
	Z-INDEX: 25; COLOR: #fff; BACKGROUND-COLOR: #900
}
A.info SPAN {
	DISPLAY: none
}
A.info:hover SPAN.info {
	BORDER-RIGHT: #333 1px solid; PADDING-RIGHT: 2px; BORDER-TOP: #333 1px solid; DISPLAY: block; PADDING-LEFT: 2px; FONT-SIZE: smaller; LEFT: -5em; PADDING-BOTTOM: 2px; BORDER-LEFT: #333 1px solid; WIDTH: 15em; COLOR: #900; PADDING-TOP: 2px; BORDER-BOTTOM: #333 1px solid; POSITION: absolute; TOP: 2em; BACKGROUND-COLOR: #eee; TEXT-ALIGN: left
}
A {
	FONT-WEIGHT: bold
}
A:link {
	COLOR: #900; BACKGROUND-COLOR: transparent
}
A:visited {
	COLOR: #633; BACKGROUND-COLOR: transparent
}
A:active {
	COLOR: #633; BACKGROUND-COLOR: transparent
}
P {
	MARGIN-LEFT: 2em; MARGIN-RIGHT: 2em
}
P.copyright {
	FONT-SIZE: x-small
}
P.toc {
	FONT-WEIGHT: bold; FONT-SIZE: small; MARGIN-LEFT: 3em
}
TABLE.toc {
	BORDER-TOP-WIDTH: 0px; PADDING-RIGHT: 0px; PADDING-LEFT: 0px; BORDER-LEFT-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px 0px 0px 3em; VERTICAL-ALIGN: text-top; PADDING-TOP: 0px; BORDER-RIGHT-WIDTH: 0px
}
TD.toc {
	FONT-WEIGHT: bold; FONT-SIZE: small; VERTICAL-ALIGN: text-top
}
OL.text {
	MARGIN-LEFT: 2em; MARGIN-RIGHT: 2em
}
UL.text {
	MARGIN-LEFT: 2em; MARGIN-RIGHT: 2em
}
LI {
	MARGIN-LEFT: 3em
}
EM {
	FONT-STYLE: italic
}
STRONG {
	FONT-WEIGHT: bold
}
DFN {
	FONT-WEIGHT: bold; FONT-STYLE: normal
}
CITE {
	FONT-WEIGHT: normal; FONT-STYLE: normal
}
TT {
	COLOR: #036
}
TT {
	FONT-SIZE: small; FONT-FAMILY: "Courier New", Courier, monospace
}
PRE {
	FONT-SIZE: small; FONT-FAMILY: "Courier New", Courier, monospace
}
PRE DFN {
	FONT-SIZE: small; FONT-FAMILY: "Courier New", Courier, monospace
}
PRE EM {
	FONT-SIZE: small; FONT-FAMILY: "Courier New", Courier, monospace
}
PRE CITE {
	FONT-SIZE: small; FONT-FAMILY: "Courier New", Courier, monospace
}
PRE SPAN {
	FONT-SIZE: small; FONT-FAMILY: "Courier New", Courier, monospace
}
PRE {
	PADDING-RIGHT: 4px; PADDING-LEFT: 4px; PADDING-BOTTOM: 4px; COLOR: #000; PADDING-TOP: 4px; BACKGROUND-COLOR: #ccc; TEXT-ALIGN: left
}
PRE DFN {
	COLOR: #900
}
PRE EM {
	FONT-WEIGHT: normal; COLOR: #66f; BACKGROUND-COLOR: #ffc
}
PRE .key {
	FONT-WEIGHT: bold; COLOR: #33c
}
PRE .id {
	COLOR: #900
}
PRE .str {
	COLOR: #000; BACKGROUND-COLOR: #cff
}
PRE .val {
	COLOR: #066
}
PRE .rep {
	COLOR: #909
}
PRE .oth {
	COLOR: #000; BACKGROUND-COLOR: #fcf
}
PRE .err {
	BACKGROUND-COLOR: #fcc
}
TABLE.all {
	BORDER-TOP-WIDTH: 2px; BORDER-LEFT-WIDTH: 2px; FONT-SIZE: small; BORDER-BOTTOM-WIDTH: 2px; VERTICAL-ALIGN: top; BORDER-COLLAPSE: collapse; TEXT-ALIGN: center; BORDER-RIGHT-WIDTH: 2px
}
TABLE.full {
	BORDER-TOP-WIDTH: 2px; BORDER-LEFT-WIDTH: 2px; FONT-SIZE: small; BORDER-BOTTOM-WIDTH: 2px; VERTICAL-ALIGN: top; BORDER-COLLAPSE: collapse; TEXT-ALIGN: center; BORDER-RIGHT-WIDTH: 2px
}
TABLE.headers {
	BORDER-TOP-WIDTH: 2px; BORDER-LEFT-WIDTH: 2px; FONT-SIZE: small; BORDER-BOTTOM-WIDTH: 2px; VERTICAL-ALIGN: top; BORDER-COLLAPSE: collapse; TEXT-ALIGN: center; BORDER-RIGHT-WIDTH: 2px
}
TABLE.none {
	BORDER-TOP-WIDTH: 2px; BORDER-LEFT-WIDTH: 2px; FONT-SIZE: small; BORDER-BOTTOM-WIDTH: 2px; VERTICAL-ALIGN: top; BORDER-COLLAPSE: collapse; TEXT-ALIGN: center; BORDER-RIGHT-WIDTH: 2px
}
TABLE.all {
	BORDER-LEFT-COLOR: black; BORDER-BOTTOM-COLOR: black; BORDER-TOP-STYLE: solid; BORDER-TOP-COLOR: black; BORDER-RIGHT-STYLE: solid; BORDER-LEFT-STYLE: solid; BORDER-RIGHT-COLOR: black; BORDER-BOTTOM-STYLE: solid
}
TABLE.full {
	BORDER-LEFT-COLOR: black; BORDER-BOTTOM-COLOR: black; BORDER-TOP-STYLE: solid; BORDER-TOP-COLOR: black; BORDER-RIGHT-STYLE: solid; BORDER-LEFT-STYLE: solid; BORDER-RIGHT-COLOR: black; BORDER-BOTTOM-STYLE: solid
}
TABLE.headers {
	BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none
}
TABLE.none {
	BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none
}
TH {
	BORDER-TOP-WIDTH: 2px; FONT-WEIGHT: bold; BORDER-LEFT-WIDTH: 2px; BORDER-LEFT-COLOR: black; BORDER-BOTTOM-WIDTH: 3px; BORDER-BOTTOM-COLOR: black; BORDER-TOP-COLOR: black; BORDER-RIGHT-WIDTH: 2px; BORDER-RIGHT-COLOR: black
}
TABLE.all TH {
	BORDER-TOP-STYLE: solid; BORDER-RIGHT-STYLE: solid; BORDER-LEFT-STYLE: solid; BORDER-BOTTOM-STYLE: solid
}
TABLE.full TH {
	BORDER-TOP-STYLE: solid; BORDER-RIGHT-STYLE: solid; BORDER-LEFT-STYLE: solid; BORDER-BOTTOM-STYLE: solid
}
TABLE.headers TH {
	BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: solid
}
TABLE.none TH {
	BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none
}
TABLE.all TD {
	BORDER-RIGHT: #333 2px solid; BORDER-TOP: #333 1px solid; BORDER-LEFT: #333 2px solid; BORDER-BOTTOM: #333 1px solid
}
TABLE.full TD {
	BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none
}
TABLE.headers TD {
	BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none
}
TABLE.none TD {
	BORDER-TOP-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none; BORDER-BOTTOM-STYLE: none
}
HR {
	HEIGHT: 1px
}
HR.insert {
	BORDER-RIGHT: 0px; BORDER-TOP: 0px; BORDER-LEFT: 0px; WIDTH: 80%; COLOR: #ccc; BORDER-BOTTOM: 0px; BACKGROUND-COLOR: #ccc
}
.style1 {
	color: #FF0000;
	font-weight: bold;
}
</STYLE>
<div id="page" dir="ltr" lang="en">
<div dir="ltr" id="content" lang="en">
<p>
</p>

<TABLE cellSpacing=0 cellPadding=0 width="66%" summary=layout border=0>
  <TBODY>
    <TR>
      <TD><TABLE cellSpacing=1 cellPadding=2 width="100%" summary=layout border=0>
        <TBODY>
          <TR>
            <TD class=header>DCMI Kernel Metadata Task Group</TD>
            <TD class=header>J. Kunze</TD>
          </TR>
          <TR>
            <TD class=header>&nbsp;</TD>
            <TD class=header>A. Turner</TD>
          </TR>
          <TR>
            <TD class=header>&nbsp;</TD>
            <TD class=header>California Digital Library</TD>
          </TR>
          <TR>
            <TD class=header>&nbsp;</TD>
            <TD class=header>February 20, 
              2008 - <span class="style1">DRAFT V1.4A</span></TD>
          </TR>
        </TBODY>
      </TABLE></TD>
    </TR>
  </TBODY>
</TABLE>
<h1>Kernel Metadata/ERC Application Profile </h1>

<h3>&nbsp;</h3>
<h3>Introduction</h3>
<p>Kernel metadata (<a href="#KSPEC">[KSPEC]</a>) is a small prescriptive vocabulary designed to support highly   uniform but minimal object descriptions for the purpose of orderly collection   management. The Kernel vocabulary, based on a subset of Dublin Core (DC)   properties as defined by the DC Abstract Model <a href="#DCAM">[DCAM]</a>, aims to describe objects of any form or category, but its   reach is limited to a small number of fundamental questions such as who, what,   when, and where. The Electronic Resource Citation (ERC) specifies requirements for representing Kernel metadata in any given object description. </p>
<h3>Functional Requirements and Domain Model </h3>

<p>Kernel metadata is designed to assist orderly collection management by   supporting the creation of brief but highly uniform object descriptions that can   be listed, surveyed, and searched efficiently during normal collection   maintenance and trouble-shooting activities. These descriptions serve as object   surrogates that are convenient for automated sorting and filtering operations   and are also eye-readable without specialized display software. The goal of   Kernel metadata is to balance the needs for expressive power, very simple   machine processing, and direct human manipulation of metadata records. </p>
<p>Kernel metadata is based on DC metadata <A href="#RFC5013">[RFC5013]</A> maintained by the Dublin Core Metadata   Initiative <A href="#DCMI">[DCMI]</A>. Kernel elements are descriptors that identify   various object properties. In principle they apply to any object in the   universe, whether digital, physical, or abstract, following in the tradition of <A href="#RFC3986">[RFC3986]</A>. This   extreme diversity of objects is approached with the hypothesis that highly   variable and rich object descriptions can be directly comparable at the level of   about four fundamental elements — who, what, when, and where — as applied to the expression (i.e., publication, installation, performance, discovery) of the object. This sequence is a recurring theme in the   Kernel. In anticipation of future extensions to "how" and "why", we refer to the   first four elements as "the four h's" (what they all have in common is an   initial aspirated "h" sound, which is also shorter to say than "w"). </p>
<p>Kernel-based descriptions make it possible to compare an extremely diverse   set of objects. Comparison is possible even when many other elements co-exist   with Kernel elements, or when a minor amount of information in other elements   overlaps with Kernel element information. Regardless of whether an object is   smoked, worn, navigated, or in any other way, interacted with, its Kernel based   description ensures the presence of a few predictable points of commonality in   the form of easily isolatable Kernel elements. Kernel elements provide a concise   intersection of interoperable (or at least comparable) elements across a broad   range of object descriptions. </p>
<h3>Syntax and Usage Guidelines </h3>
<p>The Kernel specification defines both metadata elements and how particular   data values should be structured within the elements. These rules may be   complemented by other conventions (e.g., <A href="#AACR2">[AACR2]</A>), although this is not required. As with most   vocabularies, ultimate responsibility for creating coherent and sensible   descriptions lies with the metadata creator. </p>
<p>Standard encoding methods such as <A href="#RDF">[RDF]</A> and <A href="#XML">[XML]</A> may be used to format ERCs and   Kernel metadata. It is also possible to encode modified forms of Kernel element   values using other methods, such as <A href="#MARC">[MARC]</A> or <A href="#MODS">[MODS]</A>, although some granularity of   information may be lost in the process. For specific syntax and usage guidelines, refer to the Kernel metadata specification  <a href="#KSPEC">[KSPEC]</a> and crosswalk to other encoding schemes <a href="#KMAP">[KMAP]</a>.</p>
<h3 id="head-b8ec269d34f306473fc59acd2f608629fb411042">Description Set Profile </h3>

<p>All four Kernel elements "who", "what", "when", and   "where" must be present with no missing values; these four h's each have the coded   synonyms h1, h2, h3, and h4, respectively. These four Kernel elements roughly correspond to Dublin Core elements, as described in the table below. If a best effort to supply a value   fails, in its place must be given a standardized value based on the Kernel specification <a href="#KSPEC">[KSPEC]</a> indicating the   reason for the missing value.</p>
<ul>
  <div style='display: table; width: 0; margin-left: 3em; margin-right: auto'>
    <pre>
KERNEL ELEMENT  SYNONYM			DUBLIN CORE ELEMENT APPROXIMATION

*  who          h1			Creator/Contributor/Publisher
*  what         h2			Title
*  when         h3			Date
*  where        h4			Identifier (permanent)

about-who      	h11			Subject (personage)
about-what     	h12			Subject
about-when     	h13			Coverage (temporal)
about-where    	h14			Coverage (spatial)
about-how      	h15			Description


*  A complete record requires a non-missing value for this element.

</pre>
  </div>
</ul>
<p>Some Kernel elements should contain values formatted in a particular manner:</p>
<ul>
  <li>The Kernel assumes that most values, especially personal names given in   "who", will be given in "sort-friendly" manner, for example, "lastname,   firstname" for western names and natural word order for Chinese names.</li>
  <li>The Kernel assumes <A href="#TEMPER">[TEMPER]</A> format for dates in order to express date   ranges, lists, approximate dates, and BC dates (not possible, for example, with <A href="#W3CDTF">[W3CDTF]</A>. </li>
</ul>
<H4>&nbsp;</H4>
<H4>Who</H4>
<HR>
<p><a href="http://n2t.info/ark:/99152/h1">http://n2t.info/ark:/99152/h1</a></p>
<DL>
  <DT><strong>Definition</strong>   
  <DD>A responsible person or party.</DD>
</DL>
<DL>
  <DT><strong>Comment</strong> </DT>

<dd>
  The Kernel assumes that most values, especially personal   names given in "who", will be given in "sort-friendly" manner, for example,   "lastname, firstname" for western names and natural word order for Chinese   names.</dd>
<p><strong>For example:</strong> </p>
<pre>Statement (
  Property URI ( who )
  Value String ( "Miller, Alice" )
)
</pre>
</DL>
<H4>&nbsp;</H4>
<H4>What</H4>
<HR>
<p><a href="http://n2t.info/ark:/99152/h2">http://n2t.info/ark:/99152/h2</a></p>
<DL>
  <DT><strong>Definition</strong>   
  <DD>A name or other human-oriented identifier. </DD>
</DL>
<p><strong>For example:</strong> </p>
<pre>Statement (
  Property URI ( what )
  Value String ( "The Decline and Fall of the Roman Empire" )
)
</pre>
<h3>&nbsp;</h3>
<H4>When</H4>
<HR>
<p><a href="http://n2t.info/ark:/99152/h3">http://n2t.info/ark:/99152/h3</a></p>
<DL>
  <DT><strong>Definition</strong>   
  <DD>A date important in the object's lifecycle. </DD>
  </DL>
<DL>
  <DT><strong>Comment</strong> </DT>
  <dd>The Kernel assumes the <A href="#TEMPER">[TEMPER]</A> format for dates in order to   express date ranges, lists, approximate dates, and BC dates (not possible, for   example, with <A href="#W3CDTF">[W3CDTF]</A>). </dd>
</DL>
<p><strong>For example:</strong> </p>
<pre>Statement (
  Property URI ( when )
  Value String ( "1952~, 1958-1967"
    Syntax Encoding Scheme URI ( TEMPER )
  )
</pre>
<H4>&nbsp;</H4>
<H4>Where</H4>
<HR>
<p><a href="http://n2t.info/ark:/99152/h4">http://n2t.info/ark:/99152/h4</a></p>
<DL>
  <DT><strong>Definition</strong>   
  <DD>A location or system-oriented identifier. </DD>
</DL>
<p><strong>For example:</strong> </p>
<pre>Statement (
  Property URI ( where )
  Value String ( "http://profiles.nlm.nih.gov/BB/AA/TT/tt.pdf"
  )
</pre>
<h3>&nbsp;</h3>
<H4>About-Who</H4>
<HR>
<p><a href="http://n2t.info/ark:/99152/h11">http://n2t.info/ark:/99152/h11</a></p>
<DL>
  <DT><strong>Definition</strong>   
  <DD>A person or party figuring in the information content.</DD>
</DL>
<p><strong>For example:</strong> </p>
<pre>Statement (
  Property URI ( about-who )
  Value String ( "van Gogh, Vincent"
  )
</pre>
<h3>&nbsp;</h3>
<H4>About-What</H4>
<HR>
<p><a href="http://n2t.info/ark:/99152/h12">http://n2t.info/ark:/99152/h12</a></p>
<DL>
  <DT><strong>Definition</strong>   
  <DD>A subject or topic figuring in the information content.</DD>
</DL>
<p><strong>For example:</strong> </p>
<pre>Statement (
  Property URI ( about-what )
  Value String ( "Nonlinearity"
  )
</pre>
<h3>&nbsp;</h3>
<H4>About-When</H4>
<HR>
<p><a href="http://n2t.info/ark:/99152/h13">http://n2t.info/ark:/99152/h13</a></p>
<DL>
  <DT><strong>Definition</strong>   
  <DD>A time period covered by the information content.</DD>
</DL>
<p><strong>For example:</strong> </p>
<pre>Statement (
  Property URI ( about-when )
  Value String ( "1781"
  )
</pre>
<h3>&nbsp;</h3>
<H4>About-Where</H4>
<HR>
<p><a href="http://n2t.info/ark:/99152/h14">http://n2t.info/ark:/99152/h14</a></p>
<DL>
  <DT><strong>Definition</strong>   
  <DD>A location or region covered by the information content.</DD>
</DL>
<p><strong>For example:</strong> </p>
<pre>Statement (
  Property URI ( about-where )
  Value String ( "Podunk, VT"
  )
</pre>
<h3>&nbsp;</h3>
<H4>About-How</H4>
<HR>
<p><a href="http://n2t.info/ark:/99152/h15">http://n2t.info/ark:/99152/h15</a></p>
<DL>
  <DT><strong>Definition</strong>   
  <DD>A description of the information content.</DD>
</DL>
<p><strong>For example:</strong> </p>
<pre>Statement (
  Property URI ( about-how )
  Value String ( "Cocktail Napkin Drawing #2, destroyed during spill of 19690401"
  )
</pre>
<h3>&nbsp;</h3>
<h3>References </h3>
<TABLE width="99%" border="0">
  <TBODY>
    <TR>
      <TD vAlign="top"><A name="AACR2">[AACR2]</A></TD>
      <TD>American Library Association, “<A href="http://www.aacr2.org/">Anglo-American Cataloguing Rules</A>,” 2007 (<A href="http://www.aacr2.org/">HTML</A>).</TD>
    </TR>

	    <TR>
      <TD vAlign="top"><A name="DCAM">[DCAM]</A></TD>
      <TD>Powell A. and M. Nilsson et al., “<A href="http://dublincore.org/documents/abstract-model/">DCMI Abstract Model</A>”, June 2007 (<A href="http://dublincore.org/documents/abstract-model/">HTML</A>).</TD>
    </TR>
    <TR>
      <TD vAlign="top"><A name="DCMI">[DCMI]</A></TD>
      <TD>Dublin Core Metadata Initiative, “<A href="http://dublincore.org/documents/dcmi-terms/">DCMI Metadata Terms</A>”, December 2006 (<A href="http://dublincore.org/documents/dcmi-terms/">HTML</A>).</TD>
    </TR>

    <TR>
      <TD vAlign="top"><A name="KMAP">[KMAP]</A></TD>
      <TD>Kunze, J. and A. Turner, “<A href="http://dublincore.org/kernelwiki/FrontPage?action=AttachFile&do=get&target=KernelMapXwalk.htm">Mapping and Crosswalk: Kernel Metadata to Dublin Core, MARC21, MODS, and VRA Core</A>”, September 2007 (<A href="http://dublincore.org/kernelwiki/FrontPage?action=AttachFile&do=get&target=KernelMapXwalk.htm">HTML</A>).</TD>
    </TR>
    <TR>
      <TD vAlign="top"><A name="KSPEC">[KSPEC]</A></TD>
      <TD>Kunze, J. and A. Turner, “<A href="http://dublincore.org/kernelwiki/FrontPage?action=AttachFile&do=get&target=Kernel1_1.html">Kernel Metadata and Electronic Resource Citations (ERCs)</A>”, October 2007 (<A href="http://dublincore.org/kernelwiki/FrontPage?action=AttachFile&do=get&target=Kernel1_1.html">HTML</A>).</TD>
    </TR>
    <TR>
      <TD vAlign="top"><A name="MARC">[MARC]</A></TD>
      <TD>Library of Congress, “<A href="http://www.loc.gov/marc/">Machine Readable Cataloguing</A>,” 2007 (<A href="http://www.loc.gov/marc/">HTML</A>).</TD>
    </TR>
    <TR>
      <TD vAlign="top"><A name="MODS">[MODS]</A></TD>
      <TD>Library of Congress, “<A href="http://www.loc.gov/standards/mods/">Metadata Object Description   Schema</A>,” June 2006 (<A href="http://www.loc.gov/standards/mods/">HTML</A>).</TD>
    </TR>
    <TR>
      <TD vAlign="top"><A name="RDF">[RDF]</A></TD>
      <TD>W3C, “<A href="http://www.w3.org/RDF/">Resource   Description Framework</A>”, 2004 (<A href="http://www.w3.org/RDF/">HTML</A>).</TD>
    </TR>
	    <TR>
      <TD vAlign="top"><A name="RFC5013">[RFC5013]</A></TD>
      <TD>Kunze, J. and T. Baker, “<A href="ftp://ftp.isi.edu/in-notes/rfc5013.txt">The Dublin Core Metadata Element   Set</A>,” RFC 5013, August 2007 (<A href="ftp://ftp.isi.edu/in-notes/rfc5013.txt">HTML</A>).</TD>
    </TR>

      <TD vAlign="top"><A name="TEMPER">[TEMPER]</A></TD>
      <TD>Blair, C. and J. Kunze, “<A href="http://www.cdlib.org/inside/diglib/ark/temperspec.pdf">Temporal Enumerated   Ranges</A>,” August 2007 (<A href="http://www.cdlib.org/inside/diglib/ark/temperspec.pdf">PDF</A>).</TD>
    </TR>
    <TR>
      <TD vAlign="top"><A name="W3CDTF">[W3CDTF]</A></TD>
      <TD>W3C, “<A href="http://www.w3.org/TR/NOTE-datetime">Date and   Time Formats (W3C profile of ISO8601)</A>”, September 1997 (<A href="http://www.w3.org/TR/NOTE-datetime">HTML</A>).</TD>
    </TR>
    <TR>
      <TD vAlign="top"><A name="XML">[XML]</A></TD>
      <TD>W3C, “<A href="http://www.w3.org/TR/REC-xml/">Extensible   Markup Language (XML) 1.0 (Fourth Edition)</A>,” August 2006 (<A href="http://www.w3.org/TR/REC-xml/">HTML</A>).</TD>



    </TR>
  </TBODY>
</TABLE>
</div>
<div id="pagebottom"></div>
</div>


<p>&nbsp;</p>
</body></html>

Attached Files

To refer to attachments on a page, use attachment:filename, as shown below in the list of files. Do NOT use the URL of the [get] link, since this is subject to change and can break easily.

You are not allowed to attach a file to this page.