<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rachel Heery on Ariadne</title>
    <link>http://www.ariadne.ac.uk/authors/rachel-heery/</link>
    <description>Recent content in Rachel Heery on Ariadne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 30 Oct 2006 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://www.ariadne.ac.uk/authors/rachel-heery/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>DC 2006: Metadata for Knowledge and Learning</title>
      <link>http://www.ariadne.ac.uk/issue/49/dc-2006-rpt/</link>
      <pubDate>Mon, 30 Oct 2006 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/49/dc-2006-rpt/</guid>
      <description>DC-2006 [1], the annual conference of the Dublin Core Metadata Initiative (DCMI), took place this year in the city of Manzanillo, on the Pacific coast of Mexico, with a subtitle of &amp;lsquo;Metadata for Knowledge and Learning&amp;rsquo;. The four-day conference was organised by the University of Colima [2], and the venue for the event was the Karmina Palace Hotel, a large hotel set within its own complex of restaurants, bars, shops and swimming pools.</description>
    </item>
    
    <item>
      <title>Application Profiles: Mixing and Matching Metadata Schemas</title>
      <link>http://www.ariadne.ac.uk/issue/25/app-profiles/</link>
      <pubDate>Sat, 23 Sep 2000 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/25/app-profiles/</guid>
      <description>BackgroundThis paper introduces application profiles as a type of metadata schema. We use application profiles as a way of making sense of the differing relationship that implementors and namespace managers have towards metadata schema, and the different ways they use and develop schema. The idea of application profiles grew out of UKOLN&amp;rsquo;s work on the DESIRE project (1), and since then has proved so helpful to us in our discussions of schemas and registries that we want to throw it out for wider discussion in the run-up to the DC8 Workshop in Ottawa in October.</description>
    </item>
    
    <item>
      <title>Metadata Corner: CrossROADS and Interoperability</title>
      <link>http://www.ariadne.ac.uk/issue/14/metadata/</link>
      <pubDate>Thu, 19 Mar 1998 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/14/metadata/</guid>
      <description>The third phase of the ROADS eLib project [1] puts service interoperability at centre stage. The project, which provides software to a number of subject services within eLib and beyond, is now working in an environment where interoperability is a requirement. There is a &amp;lsquo;strand&amp;rsquo; within the project where we are investigating a variety of tools and protocols that might contribute inter-working functionality to the ROADS &amp;lsquo;toolkit&amp;rsquo;. This account attempts to give some brief notes by way of context to this work and to provide a sketch of work in progress.</description>
    </item>
    
    <item>
      <title>What Is RDF?</title>
      <link>http://www.ariadne.ac.uk/issue/14/what-is/</link>
      <pubDate>Thu, 19 Mar 1998 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/14/what-is/</guid>
      <description>What is RDF? It&amp;rsquo;s the Resource Description Framework. Does that help? No? RDF is the latest acronym to add to your list, one that is set to gain in significance in the future. At present though it is early days for RDF and little accessible information is available for the interested reader. This short summary will try to outline some key points regarding RDF and point to available further information. What is certain is that this summary will go out of date quickly, RDF is &amp;lsquo;work in progress&amp;rsquo; and is an area which is undergoing rapid development and change.</description>
    </item>
    
    <item>
      <title>Metadata Corner: Naming Names - Metadata Registries</title>
      <link>http://www.ariadne.ac.uk/issue/11/metadata/</link>
      <pubDate>Thu, 18 Sep 1997 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/11/metadata/</guid>
      <description>To-day&amp;rsquo;s information user may well have access to a range of resources, and these resources will be described in more diverse resource description formats than traditional MARC. During the search process a user will encounter systems based on several different resource description formats, for example, their local OPAC, an internet subject gateway, an electronic text archive, each of which will manipulate a different variety of metadata. Although the promise of an increase in &amp;lsquo;seamless searching&amp;rsquo; across interoperable systems will mean the end user will not themselves be aware of these diverse formats, there are other people, and indeed software, that will need to understand and manage these formats.</description>
    </item>
    
    <item>
      <title>ROADS: Resource Organisation and Discovery in Subject-Based Services</title>
      <link>http://www.ariadne.ac.uk/issue/3/roads/</link>
      <pubDate>Sat, 18 May 1996 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/3/roads/</guid>
      <description>As MARC and cataloguing give way to metadata and resource description, the true impact of the internet is realised. Cataloguers are being transformed to.....metaloguers(?). The ranks of library school students who sat bemused through lectures on UKMARC and AACR need to indulge in a bit of reconstruction. Really they were applying a canonical syntactical representation to related manifestations, and maybe occasionally considering extensibility. They were doing metadata. And if we had realised that a bit earlier, maybe we would be as rich as Jerry Yang and David Filo; as reported in mid-April, the public share offering in the internet &#39;catalogue&#39; Yahoo!</description>
    </item>
    
  </channel>
</rss>