<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Clark &amp;amp; Parsia: Thinking Clearly</title>
  <id>http://weblog.clarkparsia.com/</id>
  <updated>2006-02-10T00:00:00Z</updated>
  <author>
    <name></name>
  </author>
  <entry>
    <title>Semantic Versioning and OWL Ontologies</title>
    <link href="http://weblog.clarkparsia.com/2011/09/19/semantic-versioning-and-owl-ontologies/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2011/09/19/semantic-versioning-and-owl-ontologies/</id>
    <published>2011-09-19T00:00:00Z</published>
    <updated>2011-09-19T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;I begin with a bald, if not exactly bold claim: an OWL ontology is
like a public API for your data. Better: an OWL ontology is a public,
machine-readable contract between producers and consumers about the meaning
of data&amp;hellip;&lt;/p&gt;
</summary>
  </entry>
  <entry>
    <title>Stardog Performance: SP2B Benchmark</title>
    <link href="http://weblog.clarkparsia.com/2011/05/31/stardog-performance-sp2b-benchmark/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2011/05/31/stardog-performance-sp2b-benchmark/</id>
    <published>2011-05-31T00:00:00Z</published>
    <updated>2011-05-31T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;As you may already know, we&amp;rsquo;re working hard on
&lt;a href="http://stardog.com/"&gt;Stardog&lt;/a&gt;, our upcoming RDF database. It&amp;rsquo;s presently
in closed alpha testing (55 testers), at version 0.5.3, and progressing
rapidly. The overriding goals for Stardog, which we&amp;rsquo;ve repeated often, are:&lt;/p&gt;
</summary>
  </entry>
  <entry>
    <title>How to Create Business Value with Semantic Tech</title>
    <link href="http://weblog.clarkparsia.com/2011/05/04/how-to-create-business-value-with-semantic-tech/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2011/05/04/how-to-create-business-value-with-semantic-tech/</id>
    <published>2011-05-04T00:00:00Z</published>
    <updated>2011-05-04T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;I recently
&lt;a href="https://twitter.com/#!/kendall/status/65404717152473088"&gt;tweeted&lt;/a&gt; that we
build ontologies to create business value. I meant that we build Semantic
Technology-based software to empower our customers to create business value
(or to create it for them). In reply, a few people said they&amp;rsquo;d like to hear
more&amp;hellip;&lt;/p&gt;
</summary>
  </entry>
  <entry>
    <title>SDQ: Information Integration in the Real World</title>
    <link href="http://weblog.clarkparsia.com/2011/03/07/sdq-information-integration-in-the-real-world/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2011/03/07/sdq-information-integration-in-the-real-world/</id>
    <published>2011-03-07T00:00:00Z</published>
    <updated>2011-03-07T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;The semantic technology sweet spot is &lt;a href="http://en.wikipedia.org/wiki/Data_integration"&gt;information
integration&lt;/a&gt;; that means
(primarily, but not only) evaluating SPARQL queries over a set of
distributed, heterogeneous data sources. Such query results should be sound;
they can be, optionally, exact or approximative. SDQ is our product that
provides this (and more) functionality&amp;hellip;&lt;/p&gt;
</summary>
  </entry>
  <entry>
    <title>Why Expressive Reasoning is Hard</title>
    <link href="http://weblog.clarkparsia.com/2011/02/24/why-expressive-reasoning-is-hard/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2011/02/24/why-expressive-reasoning-is-hard/</id>
    <published>2011-02-24T00:00:00Z</published>
    <updated>2011-02-24T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;As semantic technologies mature, more and more people understand &lt;em&gt;that&lt;/em&gt;
automated reasoning is hard, but not really &lt;em&gt;why&lt;/em&gt; it&amp;rsquo;s hard. This blog post
explains in detail&amp;mdash;using a very simple, easy to understand example&amp;mdash;why
automated reasoning is computationally hard&amp;hellip;&lt;/p&gt;
</summary>
  </entry>
  <entry>
    <title>Stardog Talk at NYC Semweb Meetup</title>
    <link href="http://weblog.clarkparsia.com/2011/01/26/stardog-talk-at-nyc-semweb-meetup/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2011/01/26/stardog-talk-at-nyc-semweb-meetup/</id>
    <published>2011-01-26T00:00:00Z</published>
    <updated>2011-01-26T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;On 3 Feb, I&amp;rsquo;ll be giving a talk about Stardog at the &lt;a href="http://www.meetup.com/semweb-25/calendar/15655768/"&gt;Semweb Meetup in
NYC&lt;/a&gt;&amp;hellip;&lt;/p&gt;
</summary>
  </entry>
  <entry>
    <title>Invitation to Stardog Beta</title>
    <link href="http://weblog.clarkparsia.com/2011/01/10/stardog-beta/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2011/01/10/stardog-beta/</id>
    <published>2011-01-10T00:00:00Z</published>
    <updated>2011-01-10T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;&lt;strong&gt;TL;DR?&lt;/strong&gt; &lt;a href="http://stardog.com/"&gt;Stardog&lt;/a&gt; is a fast, lightweight RDF
database. Today we&amp;rsquo;re announcing limited access to our beta testing program,
in preparation for the 1.0 release. If you&amp;rsquo;re interested in beta-testing
Stardog, &lt;a href="mailto:kendall@clarkparsia.com"&gt;drop me an email&lt;/a&gt;&amp;hellip;&lt;/p&gt;
</summary>
  </entry>
  <entry>
    <title>Stardog is coming...</title>
    <link href="http://weblog.clarkparsia.com/2010/12/29/stardog-is-coming/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2010/12/29/stardog-is-coming/</id>
    <published>2010-12-29T00:00:00Z</published>
    <updated>2010-12-29T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;&lt;img src="/img/stardog.png" title="Don't Fear the Stardog" alt="Stardog is coming...!" /&gt;&lt;/p&gt;
</summary>
  </entry>
  <entry>
    <title>Ortiz: Pellet 3.0's Native API</title>
    <link href="http://weblog.clarkparsia.com/2010/12/17/ortiz-pellet/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2010/12/17/ortiz-pellet/</id>
    <published>2010-12-17T00:00:00Z</published>
    <updated>2010-12-17T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;The next major release of Pellet, due out in Q1 of next year, will be
version 3.0. One of the big changes to Pellet 3.0 is Ortiz, the new native
Java API. This is the first post in a series that will describe Pellet 3.0
and we&amp;rsquo;re starting with Ortiz&amp;hellip;&lt;/p&gt;
</summary>
  </entry>
  <entry>
    <title>Introducing Spanner: From Documents to Linked Data Apps</title>
    <link href="http://weblog.clarkparsia.com/2010/12/14/introducing-spanner/" rel="alternate"/>
    <id>http://weblog.clarkparsia.com/2010/12/14/introducing-spanner/</id>
    <published>2010-12-14T00:00:00Z</published>
    <updated>2010-12-14T00:00:00Z</updated>
    <author>
      <name></name>
    </author>
    <summary type="html">&lt;p&gt;&lt;strong&gt;TLDR?&lt;/strong&gt; Spanner is a new product that &lt;em&gt;automagically&lt;/em&gt; turns documents (of
any kind) into a full-featured semantic web&amp;mdash;or, if you prefer, &amp;ldquo;Linked
Data&amp;rdquo;&amp;mdash;application that is easily customized or extended via JavaScript&amp;hellip;&lt;/p&gt;
</summary>
  </entry>
</feed>

