<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: PatREST to Include OCLC Audience Level Data</title>
	<link>http://www.blyberg.net/2006/09/15/patrest-to-include-oclc-audience-level-data/</link>
	<description>A library-geek blog</description>
	<pubDate>Wed, 20 Aug 2008 02:01:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Remaining Relevant &#187; Blog Archive &#187; Camping out.</title>
		<link>http://www.blyberg.net/2006/09/15/patrest-to-include-oclc-audience-level-data/#comment-6919</link>
		<dc:creator>Remaining Relevant &#187; Blog Archive &#187; Camping out.</dc:creator>
		<pubDate>Wed, 27 Sep 2006 12:12:29 +0000</pubDate>
		<guid>http://www.blyberg.net/2006/09/15/patrest-to-include-oclc-audience-level-data/#comment-6919</guid>
		<description>[...] Mash-ups and Patron-oriented Development John Byberg Facilitating patrons to create their own library-based tools. Application Program Interface [API] allow for more involvement from the community and get them developing their own applications and moving library resources and services away from the library website. By using these tools, the library becomes more omnipresent, it gets integrated with user everyday life. John&#8217;s example is patREST. This morhed into a discussion of why this is valuable and how that can be represented to library decision makers. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Mash-ups and Patron-oriented Development John Byberg Facilitating patrons to create their own library-based tools. Application Program Interface [API] allow for more involvement from the community and get them developing their own applications and moving library resources and services away from the library website. By using these tools, the library becomes more omnipresent, it gets integrated with user everyday life. John&#8217;s example is patREST. This morhed into a discussion of why this is valuable and how that can be represented to library decision makers. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john</title>
		<link>http://www.blyberg.net/2006/09/15/patrest-to-include-oclc-audience-level-data/#comment-6382</link>
		<dc:creator>john</dc:creator>
		<pubDate>Mon, 18 Sep 2006 13:09:52 +0000</pubDate>
		<guid>http://www.blyberg.net/2006/09/15/patrest-to-include-oclc-audience-level-data/#comment-6382</guid>
		<description>Ed, you're right, I think some real-life examples would be a god idea.  I'll put some in when I get the chance.

I thought about converting the percentile to a pure percentage, but then I figured that, programmatically, coders would have to convert it back to a decimal value to do anything with it.  What do you think?</description>
		<content:encoded><![CDATA[<p>Ed, you&#8217;re right, I think some real-life examples would be a god idea.  I&#8217;ll put some in when I get the chance.</p>
<p>I thought about converting the percentile to a pure percentage, but then I figured that, programmatically, coders would have to convert it back to a decimal value to do anything with it.  What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward Vielmetti</title>
		<link>http://www.blyberg.net/2006/09/15/patrest-to-include-oclc-audience-level-data/#comment-6357</link>
		<dc:creator>Edward Vielmetti</dc:creator>
		<pubDate>Mon, 18 Sep 2006 05:18:47 +0000</pubDate>
		<guid>http://www.blyberg.net/2006/09/15/patrest-to-include-oclc-audience-level-data/#comment-6357</guid>
		<description>hey john two suggestions

one is to give actual examples in the spec, and not just abstracted versions - that clarifies things sometimes.  (e.g. when multiple isbns are returned, it's not 100% clear that you just return multiple altisbn tags).

second is that if the level is a percentile then it should be scaled 0-100 not 0-1.</description>
		<content:encoded><![CDATA[<p>hey john two suggestions</p>
<p>one is to give actual examples in the spec, and not just abstracted versions - that clarifies things sometimes.  (e.g. when multiple isbns are returned, it&#8217;s not 100% clear that you just return multiple altisbn tags).</p>
<p>second is that if the level is a percentile then it should be scaled 0-100 not 0-1.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
