Author: buildbot
Date: Mon Jan 16 10:02:02 2012
New Revision: 802700

Log:
Staging update by buildbot for stanbol

Modified:
    
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/index.html

Modified: 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/index.html
==============================================================================
--- 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/index.html 
(original)
+++ 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/index.html 
Mon Jan 16 10:02:02 2012
@@ -60,7 +60,7 @@
     <p>The FactStore is a component that let's use store relations between 
entities identified by their URIs. A relation between two or more entities is 
called a <em>fact</em>. The FactStore let's you store N-ary facts according to 
a user defined fact schema. In consequence you can store relations between N 
participating entities.</p>
 <p>The FactStore only stores the relation and not the entities itself. It only 
uses references to entities by using the entities' URI. The entities itself 
should be handled by another component, e.g. the <a 
href="../entityhub.html">EntityHub</a>. A fact is defined by a fact schema 
which is defined over types of entities.</p>
 <p>A fact schema can be defined between an arbitrary number of entities. In 
most cases a fact schema is defined between two or three entities. For example, 
the fact schema 'works-for' can be defined as a relation between entities of 
type 'Person' and 'Organization'. The Fact Store interface allows the creation 
of custom fact schemata and to store facts according to these custom 
schemata.</p>
-<p>The Fact Store provides a simple to define and store facts. This component 
is meant to be used in scenarios where a simple solution is sufficient and it 
is not required to define a complex ontology with reasoning support.</p>
+<p>The Fact Store provides a simple way to define and store facts. This 
component is meant to be used in scenarios where a simple solution is 
sufficient and it is not required to define a complex ontology with reasoning 
support.</p>
 <p>Read on and have a look at a concrete example or go to the <a 
href="specification.html">FactStore specification</a> page for more details. If 
you need some information about its realization, read the notes about its <a 
href="implementation.html">implementation concept</a>.</p>
 <h2 id="example">Example</h2>
 <p>Imagine you want to store the fact that the person named John Doe works for 
the company Winzigweich. John Doe is represented by the URI 
http://www.doe.com/john and the company by http://www.winzigweich.de. This fact 
is stored as a relation between the entity http://www.doe.com/john and 
http://www.winzigweich.de.</p>


Reply via email to