<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Web Semantic &#187; Patterns</title>
	<atom:link href="http://www.thewebsemantic.com/category/patterns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thewebsemantic.com</link>
	<description>data for humans and computers and the tools that make it available</description>
	<lastBuildDate>Thu, 03 Jun 2010 16:27:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Indexing time and URI&#8217;s in jo4neo</title>
		<link>http://www.thewebsemantic.com/2010/01/06/indexing-time-and-uris-in-jo4neo/</link>
		<comments>http://www.thewebsemantic.com/2010/01/06/indexing-time-and-uris-in-jo4neo/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 05:48:22 +0000</pubDate>
		<dc:creator>tcowan</dc:creator>
				<category><![CDATA[Patterns]]></category>
		<category><![CDATA[neo4j]]></category>
		<category><![CDATA[jo4neo]]></category>

		<guid isPermaLink="false">http://www.thewebsemantic.com/?p=334</guid>
		<description><![CDATA[Graphs in and of themselves are not self indexing like relational databases, however, you can construct indexes via strong relationships between the nodes of interest.  The pattern I&#8217;ll be discussing in this post maps time (year, month, day, hour) into a graph format as nodes and edges.  Once time, or some subset, is represented as [...]]]></description>
		<wfw:commentRss>http://www.thewebsemantic.com/2010/01/06/indexing-time-and-uris-in-jo4neo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User/Roles Pattern in jo4neo</title>
		<link>http://www.thewebsemantic.com/2009/12/18/userroles-pattern-in-jo4neo/</link>
		<comments>http://www.thewebsemantic.com/2009/12/18/userroles-pattern-in-jo4neo/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 15:03:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Patterns]]></category>
		<category><![CDATA[java]]></category>
		<category><![CDATA[neo4j]]></category>
		<category><![CDATA[graphdb]]></category>
		<category><![CDATA[nosql]]></category>

		<guid isPermaLink="false">http://www.thewebsemantic.com/?p=233</guid>
		<description><![CDATA[Roles and Users is a classic domain model well suited to representation as a directed graph.  The neo4j team has provided us with a good summary of how to implement this pattern using neo4j here .  Utilizing jo4neo we can also solve this problem via a combination of the neo graph database and [...]]]></description>
		<wfw:commentRss>http://www.thewebsemantic.com/2009/12/18/userroles-pattern-in-jo4neo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User/Roles Pattern in OWL</title>
		<link>http://www.thewebsemantic.com/2009/12/10/userroles-pattern-in-owl/</link>
		<comments>http://www.thewebsemantic.com/2009/12/10/userroles-pattern-in-owl/#comments</comments>
		<pubDate>Fri, 11 Dec 2009 04:44:59 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Patterns]]></category>
		<category><![CDATA[semanticweb]]></category>

		<guid isPermaLink="false">http://www.thewebsemantic.com/?p=200</guid>
		<description><![CDATA[The standard User-Role or User-Group pattern is typically implemented as three tables; User, Group, and an associative table User_Group.  OWL (Ontology Web Language) is particularly suited to modeling this pattern, and, with a little help from an inferencing engine, can make some obvious yet valuable inferences for us.  In many organizations it&#8217;s easier to [...]]]></description>
		<wfw:commentRss>http://www.thewebsemantic.com/2009/12/10/userroles-pattern-in-owl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
