<?xml version="1.0" encoding="UTF-8"?>
  <mods xmlns:xlink="http://www.w3.org/1999/xlink" version="3.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-0.xsd">
	<titleInfo>
		<title>Introducing unAPI</title>
	</titleInfo>
	<name type="personal">
		<namePart>Michael Giarlo</namePart>
	</name>
	<originInfo>
		<publisher>&amp;#964;&amp;#949;&amp;#967;&amp;#957;&amp;#959;&amp;#963;&amp;#959;&amp;#966;&amp;#953;&amp;#945;</publisher>
		<dateIssued>Sat, 23 Sep 2006 16:44:13 +0000</dateIssued>
	</originInfo>
	<language>
		<languageTerm authority="rfc3066" type="code">en</languageTerm>
	</language>
	<physicalDescription>
  	<form authority="marcform">electronic</form>
  	<digitalOrigin>born digital</digitalOrigin>
  	<reformattingQuality>access</reformattingQuality>
  	<internetMediaType>application/xml</internetMediaType>
	</physicalDescription>
        <typeOfResource>text</typeOfResource>
	<location>
		<url>http://lackoftalent.org/michael/blog/2006/09/07/introducing-unapi/</url>
	</location>
	<abstract>'What is unAPI? Why should you care about it? Read Introducing unAPI, in Ariadne issue 48, for answers to those questions&#8230; and more! Here&#039;s the obligatory snippet: 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 [...]'</abstract>
        <subject authority="local">
                         <topic>Digital Libraries and Archives</topic>
                 <topic>Libraries</topic>
                 <topic>Semantic Web</topic>
                 <topic>code4lib</topic>
                 <topic>unAPI</topic>
        </subject>
  </mods>
