> From: Sarah Currier <[log in to unmask]>
..
>I do think that including a URL to the
> source of the taxonomy is a good idea though- I'm not sure where else
> that information would go.
Here is a suggestion.
www.schemeta.com/stuff/term_extensions_0_2.htm
Cheers
Mike 7:-D
-----------
Mike Collett, Schemeta
+44 7798 728 747
------------
www.schemeta.com
email: [log in to unmask]
<html>
<head>
<meta name=Title content=Title>
<meta http-equiv=Content-Type content="text/html">
<link rel=Edit-Time-Data href="Term_extensions_0_1_files/editdata.mso">
<title>Title</title>
<style><!--
.Tabletext9pt
{font-size:9.0pt;
font-family:Arial;}
.Section1
{page:Section1;}
-->
</style>
</head>
<body bgcolor=white link=black vlink=purple class="Normal" lang=EN-GB>
<div class=Section1>
<h1><font face="Arial, Helvetica, sans-serif">Vocabulary Type</font></h1>
<p><font face="Arial, Helvetica, sans-serif">A proposed extension data type</font></p>
<p><font face="Arial, Helvetica, sans-serif"><span style='font-size:8.0pt'>Prepared
by Mike Collett [log in to unmask]</span></font></p>
<p><font face="Arial, Helvetica, sans-serif"><span style='font-size:8.0pt'>Date:
16th March 2005 Version 0_2</span></font></p>
<h1><font face="Arial, Helvetica, sans-serif"><a name="_Toc709331">Introduction</a></font></h1>
<p><font face="Arial, Helvetica, sans-serif">This document outlines an approach
for dealing with vocabularies and terms within <i>LOM</i><span style='font-style:normal'>
and possibly other metadata schemes. </span></font></p>
<p><font face="Arial, Helvetica, sans-serif">There is increasing use of multiple
vocabularies and taxonomies in metadata instances, making interoperability
more complex. There are several standards for representing vocabularies, both
structured and unstructured. Most of these include an identifier as well as
the name of the term. </font></p>
<p><font face="Arial, Helvetica, sans-serif">LOM defines a data type called
Vocabulary. This has a C<i>haracterString</i><span
style='font-style:normal'> for the </span><i>Source</i><span style='font-style:
normal'> and then multiple C</span><i>haracterString</i><span style='font-style:
normal'> for the list of terms (</span><i>Value</i><span style='font-style:
normal'>). Each term is identified only by the string and has no other identifier.
</span></font></p>
<p><font face="Arial, Helvetica, sans-serif">LOM also allows for vocabularies
to be included in <i>Classification</i><span
style='font-style:normal'>. Each </span><i>Taxon Path</i><span
style='font-style:normal'> includes the </span><i>Source</i><span
style='font-style:normal'>, as in vocabulary, and a list of </span><i>Taxons</i><span
style='font-style:normal'>. The difference from the </span><i>Vocabulary</i><span
style='font-style:normal'> type is that each </span><i>Taxon</i><span
style='font-style:normal'> includes an identifier (</span><i>Id</i><span
style='font-style:normal'>)</span><i> </i><span style='font-style:normal'>and
a term (</span><i>Entry)</i><span style='font-style:normal'>. </span></font></p>
<p><font face="Arial, Helvetica, sans-serif">It is suggested that LOM and other
schemes would benefit from improved data types that are used to define vocabularies
and terms.</font></p>
<h1><font face="Arial, Helvetica, sans-serif">Identification</font></h1>
<p><font face="Arial, Helvetica, sans-serif">The combination of <i>Source</i><span style='font-style:
normal'> and </span><i>Value</i><span style='font-style:normal'> is often insufficient
to uniquely identify the concept represented by a term. A term (</span><i>Value</i><span
style='font-style:normal'>) is usually used as a person readable string. Unique
identifiers are usually intended for machine readability not for people. </span></font></p>
<p><font face="Arial, Helvetica, sans-serif">If some communities use <i>Value</i><span style='font-style:
normal'> to be person readable and others use it as an opaque machine-readable
identifier there will be greater confusion and less semantic interoperability.</span></font></p>
<p><font face="Arial, Helvetica, sans-serif">There are considerable advantages
to having a resolvable identifier for all the parts of a metadata instance
that include vocabularies or terms. These include the source of the vocabulary,
the source of the term and the concept that the term is used to name.</font></p>
<p><font face="Arial, Helvetica, sans-serif">The proposed structures allow for
the identification, naming, description and resolution of each term separately
as well as the source of the vocabulary as a whole. In addition the source
of each term can be provided. It is recommended that all person readable values
terms or descriptions are capable
of being delivered in multiple languages. The LOM LangString is one way of
doing this.</font></p>
<h1><font face="Arial, Helvetica, sans-serif">Data Types</font></h1>
<p><font face="Arial, Helvetica, sans-serif">The following is a description
of a type that identifies and describes an item and how this can be used to
construct a vocabulary type. It is provide in simple tabular form but could
be expressed in various formats or bindings if required.</font></p>
<p><font face="Arial, Helvetica, sans-serif">To increase interoperability the
existing LOM elements could retain their names in XML or other bindings.</font></p>
<p><font face="Arial, Helvetica, sans-serif">The ItemNameType could also be
used to extend some of the other LOM elements that are sometimes ambiguous,
such as coverage.</font></p>
<h2><font face="Arial, Helvetica, sans-serif">ItemNameType</font></h2>
<table border=1 cellspacing=0 cellpadding=0>
<thead>
<tr>
<td width=27 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>N</b></font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>Name</b></font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>Size</b></font></p></td>
<td width=100 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>Type</b></font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>Notes</b></font></p></td>
</tr>
</thead>
<tr>
<td width=27 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1</font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">ItemName</font></p></td>
<td width=35 valign=top class="Normal"> </td>
<td width=100 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Container</font></p></td>
<td width=175 valign=top class="Normal"> </td>
</tr>
<tr>
<td width=27 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1.1</font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Identifier</font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">0..*
C</font></p></td>
<td width=100 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">CharacterString(1000)</font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Must
be present if title is not. Preferably expressed in uri syntax, though
may be a local identification scheme.</font></p>
<p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">The first
identifier is the preferred identifier if there is more than one, this
is recommended as being a globally unique identifier.</font></p></td>
</tr>
<tr>
<td width=27 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1.2</font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Name</font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">0..1
C</font></p></td>
<td width=100 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">LangString(1000)</font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Must
be present if identifier is not.</font></p></td>
</tr>
<tr>
<td width=27 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1.3</font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Description</font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">0..1</font></p></td>
<td width=100 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">LangString(2000)</font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">A
person readable description.</font></p></td>
</tr>
<tr>
<td width=27 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1.4</font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Location</font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">0..*</font></p></td>
<td width=100 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">CharacterString(1000)</font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">A
resolvable location that contains the item, metadata or further information
about the item. Preferably expressed as a registered uri. For example
this could include the identifier embedded in a URL.</font></p>
<p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">If only
a single resolution is required, and the namespace is dual purpose,
the identifier may provide the location.</font></p></td>
</tr>
</table>
<h2><font face="Arial, Helvetica, sans-serif">VocabularyType</font></h2>
<table border=1 cellspacing=0 cellpadding=0>
<tr>
<td width=31 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>N</b></font></p></td>
<td width=95 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>Name</b></font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>Size</b></font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>Type</b></font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif"><b>Notes</b></font></p></td>
</tr>
<tr>
<td width=31 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1</font></p></td>
<td width=95 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Vocabulary</font></p></td>
<td width=35 valign=top class="Normal"> </td>
<td width=99 valign=top class="Normal"> </td>
<td width=175 valign=top class="Normal"> </td>
</tr>
<tr>
<td width=31 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1.1</font></p></td>
<td width=95 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">VocabularySource</font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">0..1</font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">ItemNameType</font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">The
source of the collection of terms. This may be a structured vocabulary
or taxonomy.</font></p></td>
</tr>
<tr>
<td width=31 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1.2</font></p></td>
<td width=95 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Terms</font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1..*</font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Container</font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">A
collection (bag) of terms each possibly with a separate source.</font></p></td>
</tr>
<tr>
<td width=31 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1.2.1</font></p></td>
<td width=95 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">Term</font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1</font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">ItemNameType</font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">The
name of the term.</font></p></td>
</tr>
<tr>
<td width=31 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">1.2.3</font></p></td>
<td width=95 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">TermSource</font></p></td>
<td width=35 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">0..1</font></p></td>
<td width=99 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">ItemNameType</font></p></td>
<td width=175 valign=top class="Normal"> <p class=Tabletext9pt><font face="Arial, Helvetica, sans-serif">The
source of the term. </font></p></td>
</tr>
</table>
<p><font face="Arial, Helvetica, sans-serif">From the LOM vocabulary type</font></p>
</div>
<blockquote>
<div class=Section1><font face="Arial, Helvetica, sans-serif"><i>Source</i><span
style='font-style:normal'> maps to Source.Name</span></font></div>
<div class=Section1><font face="Arial, Helvetica, sans-serif"><i>Value</i><span
style='font-style:normal'> maps to Term.Name</span></font></div>
</blockquote>
<div class=Section1>
<p><font face="Arial, Helvetica, sans-serif">It may be useful to add an element
that defines if the list is ordered (enumerated) or unordered (state).</font></p>
<p><font face="Arial, Helvetica, sans-serif">Similarly in Classification, <i>Source</i><span
style='font-style:normal'> and </span><i>Taxon</i><span style='font-style:normal'>
could both be extended by defining them as ItemNameTypes. From the LOM Classification
type </span></font></p>
</div>
<blockquote>
<div class=Section1><font face="Arial, Helvetica, sans-serif"><i>Source</i><span
style='font-style:normal'> maps to VocabularySource.ItemName.Name</span></font></div>
<div class=Section1><font face="Arial, Helvetica, sans-serif"><i>Taxon.Id</i><span
style='font-style:normal'> maps to Term.ItemName.Identifer</span></font></div>
<div class=Section1>
<p><font face="Arial, Helvetica, sans-serif"><i>Taxon.Entry</i><span
style='font-style:normal'> maps to Term.ItemName.Name</span></font></p>
</div>
</blockquote>
<br>
<br>
<p><font face="Arial, Helvetica, sans-serif"><a href="http://creativecommons.org/licenses/by/2.0/">Some
rights reserved</a></font></p>
</body>
</html>
|