<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exploring OpenLibrary Part Two</title>
	<atom:link href="http://dynamicorange.com/2008/10/22/exploring-openlibrary-part-two/feed/" rel="self" type="application/rss+xml" />
	<link>http://dynamicorange.com/2008/10/22/exploring-openlibrary-part-two/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=exploring-openlibrary-part-two</link>
	<description>A low-frequency blog by Rob Styles</description>
	<lastBuildDate>Sun, 29 Apr 2012 07:29:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Owen Stephens</title>
		<link>http://dynamicorange.com/2008/10/22/exploring-openlibrary-part-two/#comment-4281</link>
		<dc:creator>Owen Stephens</dc:creator>
		<pubDate>Fri, 31 Oct 2008 15:06:08 +0000</pubDate>
		<guid isPermaLink="false">http://dynamicorange.com/?p=318#comment-4281</guid>
		<description>Some questions and thoughts (sorry if they don&#039;t make sense):

It looks to me that ISO8601 allows YYYY as a format? Have I misunderstood Ian&#039;s problem with using bio:date (since he seems to have co-written it I probably shouldn&#039;t argue)?

I think handling the YYYY birthdate as a range makes sense. What I don&#039;t quite understand is why you don&#039;t express it as an actual range (e.g. 1900-01-01 to 1900-12-31) - this would allow you to be more (or less) precise where this was possible? Or does the model you&#039;ve adopted allow this anyway, and the use of YYYY where applicable is just more concise?

Re: The question of &#039;circa&#039; and what it means. This page http://www.library.yale.edu/cataloging/music/pernames.htm suggests that if you knew the birthdate within 7 years, you would give a range rather than use circa. I suspect in reality circa is used more than this. Is what you need is some way of modelling a &#039;margin of error&#039; or &#039;degree of uncertainty&#039;?

The other thing to note, going back to your previous post and mentioning natural keys, is that part of the point of adding dates into the catalogue records is not to be complete, but to offer ways of differentiating between people with same name - so once you have clean date data, you should consider incorporating the date into your natural key.</description>
		<content:encoded><![CDATA[<p>Some questions and thoughts (sorry if they don&#8217;t make sense):</p>
<p>It looks to me that ISO8601 allows YYYY as a format? Have I misunderstood Ian&#8217;s problem with using bio:date (since he seems to have co-written it I probably shouldn&#8217;t argue)?</p>
<p>I think handling the YYYY birthdate as a range makes sense. What I don&#8217;t quite understand is why you don&#8217;t express it as an actual range (e.g. 1900-01-01 to 1900-12-31) &#8211; this would allow you to be more (or less) precise where this was possible? Or does the model you&#8217;ve adopted allow this anyway, and the use of YYYY where applicable is just more concise?</p>
<p>Re: The question of &#8216;circa&#8217; and what it means. This page <a href="http://www.library.yale.edu/cataloging/music/pernames.htm" rel="nofollow">http://www.library.yale.edu/cataloging/music/pernames.htm</a> suggests that if you knew the birthdate within 7 years, you would give a range rather than use circa. I suspect in reality circa is used more than this. Is what you need is some way of modelling a &#8216;margin of error&#8217; or &#8216;degree of uncertainty&#8217;?</p>
<p>The other thing to note, going back to your previous post and mentioning natural keys, is that part of the point of adding dates into the catalogue records is not to be complete, but to offer ways of differentiating between people with same name &#8211; so once you have clean date data, you should consider incorporating the date into your natural key.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

