Author: buildbot
Date: Mon Jan 16 10:00:34 2012
New Revision: 802699
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:00:34 2012
@@ -58,11 +58,14 @@
<div id="content">
<h1 class="title">Factstore</h1>
<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>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>
-<p>For this, we first need to create a so called fact schema that tells the
FactStore what we would like to store. A fact schema has a unique name (often
an URI is used) to identify it. To specify what kinds of entities we would like
to store, we specify the type of the entities. Each type has an URI and should
be defined by some ontology. For example, we can use the ontology specified by
http://schema.org/.</p>
-<p>According to http://schema.org/ a person is of type
http://schema.org/Person and an organization is of type
http://schema.org/Organization. We will use these type information to specify
the fact schema http://factschema.org/worksFor. The specification of a fact
schema is written in JSON-LD, like this:</p>
+<p>For this, we first need to create a so called fact schema that tells the
FactStore what we would like to store. A fact schema has a unique name (often
an URI is used) to identify it. To specify what kinds of entities we would like
to store, we specify the type of the entities. Each type has an URI and should
be defined by some ontology. For example, we can use the ontology specified by
<a href="http://schema.org/";>schema.org</a>.</p>
+<p>According to <a href="http://schema.org/";>schema.org</a> is a person of
type <a href="http://schema.org/Person";>http://schema.org/Person</a> and an
organization is of type <a
href="http://schema.org/Organization";>http://schema.org/Organization</a>. We
will use these type information to specify the fact schema
http://factschema.org/worksFor. The specification of a fact schema is written
in JSON-LD, like this:</p>
<div class="codehilite"><pre><span class="p">{</span>
<span class="s">"@context"</span> <span class="p">:</span> <span
class="p">{</span>
<span class="s">"#types"</span> <span class="p">:</span> <span
class="p">{</span>
@@ -98,7 +101,7 @@
<p>On success this will return a 201 (Created) and the URI of the newly
created fact in the location header of the response. To retrieve a fact you can
GET it from the returned URI.</p>
<h2 id="rest_api_documentation">REST API Documentation</h2>
-<p>To get the latest documentation you should start your copy of Apache
Stanbol and navigate your browser to http://localhost:8080/factstore. There
you will find more information and the documentation of the FactStore's REST
API.</p>
+<p>To get the latest documentation you should start your copy of an Apache
Stanbol launcher that includes the FactStore and navigate your browser to
http://localhost:8080/factstore. There you will find more information and the
documentation of the FactStore's REST API.</p>
</div>
<div id="footer">
