<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jeremy Frumkin on Ariadne</title>
    <link>http://www.ariadne.ac.uk/authors/jeremy-frumkin/</link>
    <description>Recent content in Jeremy Frumkin on Ariadne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Sat, 29 Jul 2006 23:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://www.ariadne.ac.uk/authors/jeremy-frumkin/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Introducing UnAPI</title>
      <link>http://www.ariadne.ac.uk/issue/48/chudnov-et-al/</link>
      <pubDate>Sat, 29 Jul 2006 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/48/chudnov-et-al/</guid>
      <description>Common Web tools and techniques cannot easily manipulate library resources. While photo sharing, link logging, and Web logging sites make it easy to use and reuse content, barriers still exist that limit the reuse of library resources within new Web services. [1][2] To support the reuse of library information in Web 2.0-style services, we need to allow many types of applications to connect with our information resources more easily. One such connection is a universal method to copy any resource of interest.</description>
    </item>
    
    <item>
      <title>Code4lib 2006</title>
      <link>http://www.ariadne.ac.uk/issue/47/code4lib-2006-rpt/</link>
      <pubDate>Sat, 29 Apr 2006 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/47/code4lib-2006-rpt/</guid>
      <description>Focused as a highly technical event, the inaugural code4lib conference resulted from the combined efforts of the code4lib community, a loosely connected set of programmers, hackers, librarians, and library technologists who pursue technologies related to libraries and information. Over 80 attendees had the opportunity to learn what their peers were pursuing at other institutions, to share projects, hacks, code, and ideas, and to participate in breakout sessions and give lightning talks.</description>
    </item>
    
    <item>
      <title>Opening Up OpenURLs with Autodiscovery</title>
      <link>http://www.ariadne.ac.uk/issue/43/chudnov/</link>
      <pubDate>Fri, 29 Apr 2005 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/43/chudnov/</guid>
      <description>Library users have never before had so many options for finding, collecting and sharing information. Many users abandon old information management tools whenever new tools are easier, faster, more comprehensive, more intuitive, or simply &#39;cooler.&#39; Many successful new tools adhere to a principle of simplicity - HTML made it simple for anyone to publish on the Web; XML made it simple for anyone to exchange more strictly defined data; and RSS made it simple to extract and repurpose information from any kind of published resource [1].</description>
    </item>
    
    <item>
      <title>Towards Library Groupware With Personalised Link Routing</title>
      <link>http://www.ariadne.ac.uk/issue/40/chudnov/</link>
      <pubDate>Thu, 29 Jul 2004 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/40/chudnov/</guid>
      <description>&#39;Library groupware&#39; - a set of networked tools supporting information management for individuals and for distributed groups - is a new class of service we may choose to provide in our libraries. In its simplest form, library groupware would help people manage information as they move through the diversity of online resources and online communities that make up today&#39;s information landscape. Complex implementations might integrate equally well with enterprise-wide systems such as courseware and portals on a university campus, and desktop file storage on private individual computers.</description>
    </item>
    
  </channel>
</rss>