<?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: Annotating Scripture References in Blog Posts: a Modest Proposal</title>
	<atom:link href="http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/feed/" rel="self" type="application/rss+xml" />
	<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/</link>
	<description>God's Word &#124; our words &#124; meaning, communication, &#38; technology &#124; following Jesus, the Word made flesh</description>
	<lastBuildDate>Sun, 14 Mar 2010 22:24:32 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Weston Ruter</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-34446</link>
		<dc:creator>Weston Ruter</dc:creator>
		<pubDate>Fri, 25 Jul 2008 04:32:28 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-34446</guid>
		<description>What about using OSIS references? The OSIS spec sets forth very comprehensive notation for specifying references and ranges.

Seems like every year I re-discover your site, and I am always pleased by what I find. Time to subscribe to your blog I guess :o)</description>
		<content:encoded><![CDATA[<p>What about using OSIS references? The OSIS spec sets forth very comprehensive notation for specifying references and ranges.</p>
<p>Seems like every year I re-discover your site, and I am always pleased by what I find. Time to subscribe to your blog I guess <img src='http://semanticbible.com/blogos/wp-includes/images/smilies/icon_surprised.gif' alt=':o' class='wp-smiley' /> )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vertaling Engels</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-30500</link>
		<dc:creator>Vertaling Engels</dc:creator>
		<pubDate>Thu, 26 Jun 2008 13:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-30500</guid>
		<description>A wonderful project indeed. Uniformity makes things so much easier for everyone. And especially with something like this that affects so many people.</description>
		<content:encoded><![CDATA[<p>A wonderful project indeed. Uniformity makes things so much easier for everyone. And especially with something like this that affects so many people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: English to Dutch Translation Services</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-16660</link>
		<dc:creator>English to Dutch Translation Services</dc:creator>
		<pubDate>Wed, 02 Apr 2008 08:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-16660</guid>
		<description>That is such a good idea! It would also take away the problem of people misquoting the Bible. It would be nice though to have the optional different translations of the Bible. People often are very attached to a specific translation of their favorite passage.</description>
		<content:encoded><![CDATA[<p>That is such a good idea! It would also take away the problem of people misquoting the Bible. It would be nice though to have the optional different translations of the Bible. People often are very attached to a specific translation of their favorite passage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everquest</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-16550</link>
		<dc:creator>Everquest</dc:creator>
		<pubDate>Sun, 30 Mar 2008 20:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-16550</guid>
		<description>We&#039;ve discussed this amongst the programming elite of our Church. Would be an excellent standard to introduce.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve discussed this amongst the programming elite of our Church. Would be an excellent standard to introduce.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenBible.info Blog &#187; Blog Archive &#187; Microformats Invert Assumptions</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-9734</link>
		<dc:creator>OpenBible.info Blog &#187; Blog Archive &#187; Microformats Invert Assumptions</dc:creator>
		<pubDate>Mon, 03 Sep 2007 20:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-9734</guid>
		<description>[...] â€œSolve small specific problems rather than big problemsâ€¦. By focusing on those rather than the big hard problems we get more done, and we learn important lessons (and perhaps even create a few building blocks) that make solving the harder problems easier.â€ An example of a big problem is the one posed by Axel about book-chapter-verse references not being unique identifiers because of different versification schemes. To my knowledge, only Logos has solved this problem, and they need a 57-MB data backend to support it. (57 MB != small problem.) Itâ€™s great that Axel brought up this problem; itâ€™s an excellent one to solve, but itâ€™s beyond the scope of a microformat solutionâ€”at least for now. [...]</description>
		<content:encoded><![CDATA[<p>[...] â€œSolve small specific problems rather than big problemsâ€¦. By focusing on those rather than the big hard problems we get more done, and we learn important lessons (and perhaps even create a few building blocks) that make solving the harder problems easier.â€ An example of a big problem is the one posed by Axel about book-chapter-verse references not being unique identifiers because of different versification schemes. To my knowledge, only Logos has solved this problem, and they need a 57-MB data backend to support it. (57 MB != small problem.) Itâ€™s great that Axel brought up this problem; itâ€™s an excellent one to solve, but itâ€™s beyond the scope of a microformat solutionâ€”at least for now. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Axel</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-9463</link>
		<dc:creator>Axel</dc:creator>
		<pubDate>Mon, 27 Aug 2007 10:51:52 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-9463</guid>
		<description>Thanks Sean.</description>
		<content:encoded><![CDATA[<p>Thanks Sean.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-9426</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Sun, 26 Aug 2007 00:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-9426</guid>
		<description>Axel:
No, i&#039;m not proposing a unique identification system. I think Logos may have an existing (internal) scheme for mapping across different verse reference systems, but frankly i think that&#039;s too ambitious for bibleref at this point. I&#039;d be happy with just two results at this point:
a) users unambiguously identifying when they&#039;re referencing the Bible
b) capturing what verses they&#039;re referencing (in whatever reference scheme they themselves are using)
I&#039;ll bet just these two things would still accurately capture 99% of the references that being used daily.</description>
		<content:encoded><![CDATA[<p>Axel:<br />
No, i&#8217;m not proposing a unique identification system. I think Logos may have an existing (internal) scheme for mapping across different verse reference systems, but frankly i think that&#8217;s too ambitious for bibleref at this point. I&#8217;d be happy with just two results at this point:<br />
a) users unambiguously identifying when they&#8217;re referencing the Bible<br />
b) capturing what verses they&#8217;re referencing (in whatever reference scheme they themselves are using)<br />
I&#8217;ll bet just these two things would still accurately capture 99% of the references that being used daily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Axel</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-9413</link>
		<dc:creator>Axel</dc:creator>
		<pubDate>Sat, 25 Aug 2007 08:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-9413</guid>
		<description>It&#039;s a goog idea! I am working on a bible project and run over a problem that book, chapter, vers is not a unique Identifier. For Example Psalms have different vers counting in different translations and languages. Do you have a unique identifier?</description>
		<content:encoded><![CDATA[<p>It&#8217;s a goog idea! I am working on a bible project and run over a problem that book, chapter, vers is not a unique Identifier. For Example Psalms have different vers counting in different translations and languages. Do you have a unique identifier?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Roberts</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-6991</link>
		<dc:creator>Chris Roberts</dc:creator>
		<pubDate>Thu, 07 Jun 2007 09:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-6991</guid>
		<description>I&#039;ve incorporated this in ESV WordPress Plugin version 3.0.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve incorporated this in ESV WordPress Plugin version 3.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Exploring the Mystery - Announcing WordPress ESV Plugin 3.0!</title>
		<link>http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/comment-page-1/#comment-6990</link>
		<dc:creator>Exploring the Mystery - Announcing WordPress ESV Plugin 3.0!</dc:creator>
		<pubDate>Thu, 07 Jun 2007 09:47:52 +0000</pubDate>
		<guid isPermaLink="false">http://semanticbible.com/blogos/2007/05/24/annotating-scripture-references-in-blog-posts-a-modest-proposal/#comment-6990</guid>
		<description>[...] Fourth, the new version incorporates the Bible microformat proposed at Blogos. Read the post there to see why these might be useful. [...]</description>
		<content:encoded><![CDATA[<p>[...] Fourth, the new version incorporates the Bible microformat proposed at Blogos. Read the post there to see why these might be useful. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
