<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Data Model Extensibility, Part 1</title>
	<link>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 18:57:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>

	<item>
		<title>By: Enabling the Distributed Family Tree &#187; Blog Archive &#187; Data Model Extensibility, Part 2</title>
		<link>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-33</link>
		<author>Enabling the Distributed Family Tree &#187; Blog Archive &#187; Data Model Extensibility, Part 2</author>
		<pubDate>Tue, 28 Nov 2006 14:46:18 +0000</pubDate>
		<guid>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-33</guid>
					<description>[...] This is the second of a five part series on the DFT data model.Â  Part one covered the fundamentals: RDF, OWL, and Named Graphs. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This is the second of a five part series on the DFT data model.Â  Part one covered the fundamentals: RDF, OWL, and Named Graphs. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Enabling the Distributed Family Tree &#187; Blog Archive &#187; Data Model Extensibility, Part 3</title>
		<link>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-35</link>
		<author>Enabling the Distributed Family Tree &#187; Blog Archive &#187; Data Model Extensibility, Part 3</author>
		<pubDate>Wed, 29 Nov 2006 16:02:28 +0000</pubDate>
		<guid>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-35</guid>
					<description>[...] This is theÂ third of a five part series on the DFT data model.Â  Part one covered the fundamentals: RDF, OWL, and Named Graphs.Â  Part two demonstrated how basic genealogical information can be recorded in RDF. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This is theÂ third of a five part series on the DFT data model.Â  Part one covered the fundamentals: RDF, OWL, and Named Graphs.Â  Part two demonstrated how basic genealogical information can be recorded in RDF. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Enabling the Distributed Family Tree &#187; Blog Archive &#187; Data Model Extensibility, Part 4</title>
		<link>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-37</link>
		<author>Enabling the Distributed Family Tree &#187; Blog Archive &#187; Data Model Extensibility, Part 4</author>
		<pubDate>Thu, 30 Nov 2006 17:54:00 +0000</pubDate>
		<guid>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-37</guid>
					<description>[...] This is theÂ fourth of a five part series on the DFT data model.Â  Part one covered the fundamentals: RDF, OWL, and Named Graphs.Â  Part two demonstrated how basic genealogical information can be recorded in RDF.Â  Part three showed how to record informationÂ that changed over the lifetime of an individual, such as surname. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This is theÂ fourth of a five part series on the DFT data model.Â  Part one covered the fundamentals: RDF, OWL, and Named Graphs.Â  Part two demonstrated how basic genealogical information can be recorded in RDF.Â  Part three showed how to record informationÂ that changed over the lifetime of an individual, such as surname. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Enabling the Distributed Family Tree &#187; Blog Archive &#187; Data Model Extensibility, Part 5</title>
		<link>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-40</link>
		<author>Enabling the Distributed Family Tree &#187; Blog Archive &#187; Data Model Extensibility, Part 5</author>
		<pubDate>Fri, 01 Dec 2006 22:15:04 +0000</pubDate>
		<guid>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-40</guid>
					<description>[...] This is theÂ last of a five part series on the DFT data model.Â  Part one covered the fundamentals: RDF, OWL, and Named Graphs.Â  Part two demonstrated how basic genealogical information can be recorded in RDF.Â  Part three showed how to record informationÂ that changed over the lifetime of an individual, such as surname.Â  Part four showed how to cite sources. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This is theÂ last of a five part series on the DFT data model.Â  Part one covered the fundamentals: RDF, OWL, and Named Graphs.Â  Part two demonstrated how basic genealogical information can be recorded in RDF.Â  Part three showed how to record informationÂ that changed over the lifetime of an individual, such as surname.Â  Part four showed how to cite sources. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Enabling the Distributed Family Tree &#187; Blog Archive &#187; Storage and Querying of E-Commerce Data</title>
		<link>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-53</link>
		<author>Enabling the Distributed Family Tree &#187; Blog Archive &#187; Storage and Querying of E-Commerce Data</author>
		<pubDate>Fri, 08 Dec 2006 22:55:15 +0000</pubDate>
		<guid>http://www.dftproject.org/blog/2006/11/27/data-model-extensibility-part-1/#comment-53</guid>
					<description>[...] Sound familiar?Â  I thought so too.Â  I was especially excited to read about their analysis of why a vertical representation is desirable.Â  The benefit that really stood out to me was rapidÂ schema evolution:Â the ability to frequently add new attributes without incurring significant costs.Â  This is key to the extensibility of the DFT data model. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Sound familiar?Â  I thought so too.Â  I was especially excited to read about their analysis of why a vertical representation is desirable.Â  The benefit that really stood out to me was rapidÂ schema evolution:Â the ability to frequently add new attributes without incurring significant costs.Â  This is key to the extensibility of the DFT data model. [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
