Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/entityhub/entityhubandlinkeddata.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/entityhub/entityhubandlinkeddata.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/entityhub/entityhubandlinkeddata.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> @@ -121,8 +121,7 @@ structure and link data that describes t <li>Creating and updating of resources: Linked data currently covers only retrieval of information, which is sufficient for sites like <a href="http://dbpedia.org";>DBpedia</a> or <a href="http://www.geonames.org";>Geonames</a> where users are only able to consume data. When creating interactive (web) applications one needs to be able to create/update and remove information. Features that are currently not covered by linked data, but well defined for RESTful Services. The Linked Media proposal therefore suggest to use HTTP PUT, POST and DELETE request for this purpose.</li> <li>Handling both content and metadata: Linked Data uses Content Negotiation to select suitable content types. In addition it provides means to redirect to Information Resources about Non-Information Resources. However linked data does not differentiate between metadata and content. One can not explicitly ask first for an GIF Image and later for the metadata as RDF. Or first for an HTML blog post and later for its metadata formatted as HTML. Such a differentiation is only supported for Non-Information Resources. E.g. for a famous painting (Non-Information Resource) and a photo (Information Resource). Liked Media proposes to use the "rel" parameter of the Accept header to allow users to explicitly ask for content ("Accept: type/subtype; rel=content") or metadata ("Accept: type/subtype; rel=meta").</li> </ol> -<p>For a more detailed description please follow the link to the <a href="http://lists.w3.org/Archives/Public/public-lod/2011May/0019.html";>Linked Media proposal</a> [1] as posted by by Sebastian Schaffert on the linked open data mailing list of W3C. You might also be interested in reading the following discussion. Note also <a href="http://code.google.com/p/kiwi/source/browse/kiwi-core/src/main/java/kiwi/core/webservices/resource/ResourceWebService.java";>ResourceWebService</a> [2] a first implementation of the Linked Media proposal based on the <a href="http://code.google.com/p/kiwi/";>Kiwi2/Linked Media Framework</a> [3][4].<br /> -</p> +<p>For a more detailed description please follow the link to the <a href="http://lists.w3.org/Archives/Public/public-lod/2011May/0019.html";>Linked Media proposal</a> [1] as posted by by Sebastian Schaffert on the linked open data mailing list of W3C. You might also be interested in reading the following discussion. Note also <a href="http://code.google.com/p/kiwi/source/browse/kiwi-core/src/main/java/kiwi/core/webservices/resource/ResourceWebService.java";>ResourceWebService</a> [2] a first implementation of the Linked Media proposal based on the <a href="http://code.google.com/p/kiwi/";>Kiwi2/Linked Media Framework</a> [3][4]. </p> <h2 id="requirements-of-the-stanbol-entityhub">Requirements of the Stanbol Entityhub</h2> <p>This section tries to identify requirements of the Stanbol Entityhub related to Linked Data and Linked Media. The goal of this analysis is to identify where it makes sense to adopt Linked Data/Media principles for the RESTful interface of the Entityhub.</p> <p>The Entityhub fulfills two requirements: </p> @@ -199,21 +198,21 @@ structure and link data that describes t <p>This section evaluates necessary changes to the Entityhub.</p> <h3 id="uri-scheme-for-resources">URI scheme for Resources</h3> <p>The support of Linked Data requires the use of a local URI. This is in contrast to the parameter based approach ("?id={remoteURI}") as currently used by the Entityhub. The goal is that the Entityhub allows both variants</p> -<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="sr">/entity/</span><span class="p">{</span><span class="n">localname</span><span class="p">}</span> <span class="ow">and</span> -<span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="p">?</span><span class="n">uri</span><span class="o">=</span><span class="p">{</span><span class="n">uri</span><span class="p">}</span> +<div class="codehilite"><pre><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="o">/</span><span class="n">entityhub</span><span class="o">/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="o">/</span><span class="p">{</span><span class="n">localname</span><span class="p">}</span> <span class="n">and</span> +<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="o">/</span><span class="n">entityhub</span><span class="o">/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span>?<span class="n">uri</span><span class="p">={</span><span class="n">uri</span><span class="p">}</span> </pre></div> <p>to refer an Entity. This requires that the Entityhub provides a local HTTP URI for any (local or remote) entity. The suggestion is to use the local name of the remote entity or the MD5 of the whole URI in cases where this is not possible.</p> <p>To support the redirects as defined by Linked Data it is also necessary to generate own URIs for Representations. To support the differentiation between Content and Metadata we need also an own URI for the metadata.</p> <p>The proposal is to use file extension like additions to the local name of Entities:</p> -<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="sr">/entity/</span><span class="p">{</span><span class="n">localname</span><span class="p">}</span><span class="o">.</span><span class="n">rep</span> +<div class="codehilite"><pre><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="o">/</span><span class="n">entityhub</span><span class="o">/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="o">/</span><span class="p">{</span><span class="n">localname</span><span class="p">}.</span><span class="n">rep</span> </pre></div> <p>is used to directly refer to the Representation of an Entity - in Linked Media terminology the Information Resource. Note that the local HTTP URI is use as base for the ".rep" extension. "?uri={uri}.rep" will not be supported. Users of the Entityhub can therefore use the ".rep" extension to directly access the content for an Entity. Note that content negotiation will still be needed when requesting this kind of URIs.</p> <p>Similar to the above the ".meta" extension will be used for constructing URIs for the metadata:</p> -<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="sr">/entity/</span><span class="p">{</span><span class="n">localname</span><span class="p">}</span><span class="o">.</span><span class="n">meta</span> +<div class="codehilite"><pre><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="o">/</span><span class="n">entityhub</span><span class="o">/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="o">/</span><span class="p">{</span><span class="n">localname</span><span class="p">}.</span><span class="n">meta</span> </pre></div> @@ -222,15 +221,15 @@ structure and link data that describes t <p>Note that the URIs for Representations and Metadata are optional and will be omitted based on HTTP request headers in case redirects are disabled. However even in case that redirects are disabled it is still possible to use such URIs for requests.</p> <h3 id="uri-scheme-for-content-negotiation">URI scheme for Content Negotiation</h3> <p>To confirm with the Linked Data principles the Entityhub needs to provide unique HTTP URIs for any content type Information Resources (Content and Metadata Resoruces) can be serialized. As for the ".rep" and ".meta" extensions used to directly access Representations and their Metadata the proposal is also to use of file extensions to indicate the media type. In cases users wish to parse the remote URI as parameter it is also possible to parse the extension or the media type as parameter.</p> -<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="sr">/entity/</span><span class="p">{</span><span class="n">localname</span><span class="p">}</span><span class="o">.</span><span class="p">{</span><span class="n">extension</span><span class="p">}</span> <span class="ow">or</span> -<span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="p">?</span><span class="n">uri</span><span class="o">=</span><span class="p">{</span><span class="n">uri</span><span class="p">}</span><span class="o">&</span><span class="nb">format</span><span class="o">=</span><span class="p">{</span><span class="n">extension</span><span class="p">}</span><span class="o">&</span><span class="n">mediaType</span><span class="o">=</span><span class="p">{</span><span class="n">mediatype</span><span class="p">}</span> +<div class="codehilite"><pre><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="o">/</span><span class="n">entityhub</span><span class="o">/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="o">/</span><span class="p">{</span><span class="n">localname</span><span class="p">}.{</span><span class="n">extension</span><span class="p">}</span> <span class="n">or</span> +<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="o">/</span><span class="n">entityhub</span><span class="o">/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span>?<span class="n">uri</span><span class="p">={</span><span class="n">uri</span><span class="p">}</span><span class="o">&</span><span class="n">format</span><span class="p">={</span><span class="n">extension</span><span class="p">}</span><span class="o">&</span><span class="n">mediaType</span><span class="p">={</span><span class="n">mediatype</span><span class="p">}</span> </pre></div> <p>This shows the case that the extension is directly added to the local URI of the entity. In this case the "rel" parameter of the Accept header would be used to determine if the content - representation - or the metadata need to be encoded in the response. If not specified the representation will be returned.</p> <p>To allow also to directly address the representation or the metadata in a specific format the Entityhub also supports the following two variants: </p> -<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="sr">/entity/</span><span class="p">{</span><span class="n">localname</span><span class="p">}</span><span class="o">.</span><span class="n">rep</span><span class="o">.</span><span class="p">{</span><span class="n">extension</span><span class="p">}</span> -<span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="sr">/entity/</span><span class="p">{</span><span class="n">localname</span><span class="p">}</span><span class="o">.</span><span class="n">meta</span><span class="o">.</span><span class="p">{</span><span class="n">extension</span><span class="p">}</span> +<div class="codehilite"><pre><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="o">/</span><span class="n">entityhub</span><span class="o">/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="o">/</span><span class="p">{</span><span class="n">localname</span><span class="p">}.</span><span class="n">rep</span><span class="p">.{</span><span class="n">extension</span><span class="p">}</span> +<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="o">/</span><span class="n">entityhub</span><span class="o">/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="o">/</span><span class="p">{</span><span class="n">localname</span><span class="p">}.</span><span class="n">meta</span><span class="p">.{</span><span class="n">extension</span><span class="p">}</span> </pre></div> @@ -240,14 +239,13 @@ structure and link data that describes t <h4 id="accept-header"><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.1";>Accept header</a></h4> <p>The Accept header allows to specify the media type of the content as expected by the client in the response. The <a href="http://lists.w3.org/Archives/Public/public-lod/2011May/0019.html";>Linked Media proposal</a> suggests to use the "rel" parameter to specify if the response should return the data or the metadata of the requested resource. The semantics of the "rel" parameter is defined for the Link header by <a href="http://www.ietf.org/rfc/rfc5988.txt";>RFC5988</a>. An related example can be found on the <a href="http://www.w3.org/wiki/LinkHeader";>LinkHeader</a> page on the W3C wiki.</p> <p>The pattern useable for Accept header looks like</p> -<div class="codehilite"><pre><span class="n">Accept:</span> <span class="p">{</span><span class="n">media</span><span class="o">-</span><span class="n">type</span><span class="p">}[;</span> <span class="n">rel</span><span class="o">=</span><span class="n">meta</span><span class="p">]</span> +<div class="codehilite"><pre><span class="n">Accept</span><span class="p">:</span> <span class="p">{</span><span class="n">media</span><span class="o">-</span><span class="n">type</span><span class="p">}[;</span> <span class="n">rel</span><span class="p">=</span><span class="n">meta</span><span class="p">]</span> </pre></div> <p>If no "rel" pattern is specified the Entityhub will return the data (representation about the entity) as default. If users want to retrieve the the metadata they need to add "rel=meta". The {media-type} is always applied to the information selected by the "rel" parameter. </p> <h4 id="cache-control"><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9";>Cache-Control</a></h4> -<p>The Entityhub supports the following cache-request-directives to allow clients some control about local caching of entities managed by remote sites. Note that the Stanbol OFFLINE mode has precedence over Cache-Control specifications<br /> -</p> +<p>The Entityhub supports the following cache-request-directives to allow clients some control about local caching of entities managed by remote sites. Note that the Stanbol OFFLINE mode has precedence over Cache-Control specifications </p> <ul> <li>no-cache: Entities are retrieved from the remote site even if a local cache exists (if Stanbol is not in OFFLINE mode)</li> <li>no-store: Entities retrieved from a remote side are not cached locally (if Stanbol is not in OFFLINE mode)</li> @@ -257,13 +255,12 @@ structure and link data that describes t <h4 id="link-header"><a href="http://www.ietf.org/rfc/rfc5988.txt";>Link Header</a></h4> <p>The Link header is central to Linked Data and Linked Media because it is used to expose internal structures defined in-between Resources (in-between Entities but also between Entities and there Representations and Metadata)</p> <p>The principle Syntax of Link headers is as follows:</p> -<div class="codehilite"><pre><span class="n">Link:</span> <span class="o">&</span><span class="ow">lt</span><span class="p">;{</span><span class="n">uri</span><span class="p">}</span><span class="o">&</span><span class="ow">gt</span><span class="p">;;</span> <span class="n">rel</span><span class="o">=</span><span class="s">"{relation}"</span><span class="p">;</span> <span class="n">type</span><span class="o">=</span><span class="s">"{media-type}"</span> +<div class="codehilite"><pre><span class="n">Link</span><span class="p">:</span> <span class="o">&</span><span class="n">lt</span><span class="p">;{</span><span class="n">uri</span><span class="p">}</span><span class="o">&</span><span class="n">gt</span><span class="p">;;</span> <span class="n">rel</span><span class="p">=</span>"<span class="p">{</span><span class="n">relation</span><span class="p">}</span>"<span class="p">;</span> <span class="n">type</span><span class="p">=</span>"<span class="p">{</span><span class="n">media</span><span class="o">-</span><span class="n">type</span><span class="p">}</span>" </pre></div> <p>The relation parameter defines the type of the relation. <a href="http://www.iana.org/assignments/link-relations/link-relations.xml";>Registered relation types</a> are mainly used to improve the navigation of users. The values "content" and "meta" as suggested by the Linked Media proposal are currently not registered. In such cases <a href="http://www.ietf.org/rfc/rfc5988.txt";>RFC5988</a> requires the use of absolute URIs as {relation}. This document will use "content" and "meta" instead of the full URIs as required by RFC5988.</p> -<p>Regardless of that the values used for the "rel" parameter within the "Link" header by the Entityhub MUST BE the SAME as supported values for the "rel" parameter in the "Accept" header for requests. A pragmatic solution would be to support both the short form and a full URI.<br /> -</p> +<p>Regardless of that the values used for the "rel" parameter within the "Link" header by the Entityhub MUST BE the SAME as supported values for the "rel" parameter in the "Accept" header for requests. A pragmatic solution would be to support both the short form and a full URI. </p> <p>The Entityhub will add the following Links (if applicable)</p> <ul> <li>
Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/entityhub/index.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/entityhub/index.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/entityhub/index.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> @@ -89,8 +89,7 @@ <ul> <li><a href="/">Home</a></li> <li class="item"><a href="/docs/">Docs</a></li> <li class="item"><a href="/docs/0.9.0-incubating/">0.9.0-incubating</a></li> <li class="item"><a href="/docs/0.9.0-incubating/entityhub/">Entityhub</a></li> </ul> </div> <h1 class="title">Entityhub</h1> - <p>The Entityhub provides two main services. The Entityhub provides the connection to external linked open data sites as well as using indexes of them locally. Its services allow to manage a <strong>network of sites</strong> to consume entity information and to <strong>manage entities locally</strong>.<br /> -</p> + <p>The Entityhub provides two main services. The Entityhub provides the connection to external linked open data sites as well as using indexes of them locally. Its services allow to manage a <strong>network of sites</strong> to consume entity information and to <strong>manage entities locally</strong>. </p> <p>A small index of approx. 43k entities from dbpedia comes with the default installation.</p> <h2 id="service-endpoints">Service Endpoints</h2> <p>The RESTful API of the Entityhub ist structured as follows:</p> Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/factstore/implementation.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/factstore/implementation.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/factstore/implementation.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/factstore/index.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/factstore/index.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/factstore/index.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> @@ -97,10 +97,10 @@ <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> - <span class="s">"person"</span> <span class="p">:</span> <span class="s">"http://schema.org/Person"</span><span class="p">,</span> - <span class="s">"organization"</span> <span class="p">:</span> <span class="s">"http://schema.org/Organization"</span> + "<span class="p">@</span><span class="n">context</span>" <span class="p">:</span> <span class="p">{</span> + "#<span class="n">types</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">person</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">schema</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">Person</span>"<span class="p">,</span> + "<span class="n">organization</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">schema</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">Organization</span>" <span class="p">}</span> <span class="p">}</span> <span class="p">}</span> @@ -111,21 +111,21 @@ <code>/factstore/facts/http%3A%2F%2Ffactschema.org%2FworksFor</code>.</p> <p><em>Note</em>: If you want to avoid this URL-encoding step, you should chose another name for your fact schema that is not an URI by itself. You are free to do so!</p> <p>Now to PUT the <code>worksFor</code> fact schema we can use this cURL command.</p> -<div class="codehilite"><pre><span class="n">curl</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/factstore/</span><span class="n">facts</span><span class="o">/</span><span class="n">http</span><span class="nv">%3A%2F%2Ffactschema</span><span class="o">.</span><span class="n">org</span><span class="nv">%2FworksFor</span> <span class="o">-</span><span class="n">T</span> <span class="n">worksFor</span><span class="o">.</span><span class="n">json</span> +<div class="codehilite"><pre><span class="n">curl</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">localhost</span><span class="p">:</span>8080<span class="o">/</span><span class="n">factstore</span><span class="o">/</span><span class="n">facts</span><span class="o">/</span><span class="n">http</span><span class="c">%3A%2F%2Ffactschema.org%2FworksFor -T worksFor.json</span> </pre></div> <p>After creating the fact schema we can store the fact that John Doe works for Winzigweich by POSTing it to the FactStore. The fact is specified in JSON-LD syntax. The <code>@profile</code> defines the fact schema where this fact belongs to.</p> <div class="codehilite"><pre><span class="p">{</span> - <span class="s">"@profile"</span> <span class="p">:</span> <span class="s">"http://factschema.org/worksFor"</span><span class="p">,</span> - <span class="s">"person"</span> <span class="p">:</span> <span class="p">{</span> <span class="s">"@iri"</span> <span class="p">:</span> <span class="s">"http://www.doe.com/john"</span> <span class="p">},</span> - <span class="s">"organization"</span> <span class="p">:</span> <span class="p">{</span> <span class="s">"@iri"</span> <span class="p">:</span> <span class="s">"http://www.winzigweich.de"</span><span class="p">}</span> + "<span class="p">@</span><span class="n">profile</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">factschema</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">worksFor</span>"<span class="p">,</span> + "<span class="n">person</span>" <span class="p">:</span> <span class="p">{</span> "<span class="p">@</span><span class="n">iri</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">doe</span><span class="p">.</span><span class="n">com</span><span class="o">/</span><span class="n">john</span>" <span class="p">},</span> + "<span class="n">organization</span>" <span class="p">:</span> <span class="p">{</span> "<span class="p">@</span><span class="n">iri</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">winzigweich</span><span class="p">.</span><span class="n">de</span>"<span class="p">}</span> <span class="p">}</span> </pre></div> <p>Now we can POST this fact, e.g. stored in fact.json, to the FactStore at <code>/factstore/facts</code>. By using cURL it would be this command:</p> -<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">d</span> <span class="nv">@fact</span><span class="o">.</span><span class="n">json</span> <span class="o">-</span><span class="n">H</span> <span class="s">"Content-Type: application/json"</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/factstore/</span><span class="n">facts</span> +<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">d</span> <span class="p">@</span><span class="n">fact</span><span class="p">.</span><span class="n">json</span> <span class="o">-</span><span class="n">H</span> "<span class="n">Content</span><span class="o">-</span><span class="n">Type</span><span class="p">:</span> <span class="n">application</span><span class="o">/</span><span class="n">json</span>" <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">localhost</span><span class="p">:</span>8080<span class="o">/</span><span class="n">factstore</span><span class="o">/</span><span class="n">facts</span> </pre></div> Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/factstore/specification.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/factstore/specification.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/factstore/specification.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> @@ -108,13 +108,13 @@ <p>Data: The fact schema is sent as the PUT payload in JSON-LD format as a JSON-LD profile. The name of the fact is given by the URL. The elements of the schema are defined in the "#types" section of the JSON-LD "#context". Each element is specified using a unique role name for that entity plus the entity type specified by an URN.</p> <p>Example 1: PUT /factstore/facts/http%3A%2F%2Fiks-project.eu%2Font%2FemployeeOf with the following data</p> <div class="codehilite"><pre><span class="p">{</span> - <span class="s">"@context"</span> <span class="p">:</span> + "<span class="p">@</span><span class="n">context</span>" <span class="p">:</span> <span class="p">{</span> - <span class="s">"iks"</span> <span class="p">:</span> <span class="s">"http://iks-project.eu/ont/"</span><span class="p">,</span> - <span class="s">"#types"</span> <span class="p">:</span> + "<span class="n">iks</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">iks</span><span class="o">-</span><span class="n">project</span><span class="p">.</span><span class="n">eu</span><span class="o">/</span><span class="n">ont</span><span class="o">/</span>"<span class="p">,</span> + "#<span class="n">types</span>" <span class="p">:</span> <span class="p">{</span> - <span class="s">"person"</span> <span class="p">:</span> <span class="s">"iks:person"</span><span class="p">,</span> - <span class="s">"organization"</span> <span class="p">:</span> <span class="s">"iks:organization"</span> + "<span class="n">person</span>" <span class="p">:</span> "<span class="n">iks</span><span class="p">:</span><span class="n">person</span>"<span class="p">,</span> + "<span class="n">organization</span>" <span class="p">:</span> "<span class="n">iks</span><span class="p">:</span><span class="n">organization</span>" <span class="p">}</span> <span class="p">}</span> <span class="p">}</span> @@ -123,19 +123,19 @@ <p>will create the new fact schema for "employeeOf" at the given URL which is in decoded representation: /factstore/facts/http://iks-project.eu/ont/employeeOf</p> <p>Instead one can use the cURL tool for this. Store the fact schema in a JSON file and then use this command.</p> -<div class="codehilite"><pre><span class="n">curl</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/factstore/</span><span class="n">facts</span><span class="o">/</span><span class="n">http</span><span class="nv">%3A%2F%2Fiks</span><span class="o">-</span><span class="n">project</span><span class="o">.</span><span class="n">eu</span><span class="nv">%2Font%2FemployeeOf</span> <span class="o">-</span><span class="n">T</span> <span class="n">spec</span><span class="o">-</span><span class="n">example1</span><span class="o">.</span><span class="n">json</span> +<div class="codehilite"><pre><span class="n">curl</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">localhost</span><span class="p">:</span>8080<span class="o">/</span><span class="n">factstore</span><span class="o">/</span><span class="n">facts</span><span class="o">/</span><span class="n">http</span><span class="c">%3A%2F%2Fiks-project.eu%2Font%2FemployeeOf -T spec-example1.json</span> </pre></div> <p>Example 2: PUT /factstore/facts/http%3A%2F%2Fwww.schema.org%2FEvent.attendees with the following data</p> <div class="codehilite"><pre><span class="p">{</span> - <span class="s">"@context"</span> <span class="p">:</span> + "<span class="p">@</span><span class="n">context</span>" <span class="p">:</span> <span class="p">{</span> - <span class="s">"sorg"</span> <span class="p">:</span> <span class="s">"http://www.schema.org/"</span><span class="p">,</span> - <span class="s">"#types"</span> <span class="p">:</span> + "<span class="n">sorg</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">schema</span><span class="p">.</span><span class="n">org</span><span class="o">/</span>"<span class="p">,</span> + "#<span class="n">types</span>" <span class="p">:</span> <span class="p">{</span> - <span class="s">"event"</span> <span class="p">:</span> <span class="s">"sorg:Event"</span><span class="p">,</span> - <span class="s">"attendee"</span> <span class="p">:</span> <span class="p">[</span><span class="s">"sorg:Person"</span><span class="p">,</span><span class="s">"sorg:Organization"</span><span class="p">]</span> + "<span class="n">event</span>" <span class="p">:</span> "<span class="n">sorg</span><span class="p">:</span><span class="n">Event</span>"<span class="p">,</span> + "<span class="n">attendee</span>" <span class="p">:</span> <span class="p">[</span>"<span class="n">sorg</span><span class="p">:</span><span class="n">Person</span>"<span class="p">,</span>"<span class="n">sorg</span><span class="p">:</span><span class="n">Organization</span>"<span class="p">]</span> <span class="p">}</span> <span class="p">}</span> <span class="p">}</span> @@ -151,12 +151,12 @@ <p>Data: The fact schema is returned as a JSON-LD profile.</p> <p>Example: GET /factstore/facts/http%3A%2F%2Fiks-project.eu%2Font%2FemployeeOf will return the following data:</p> <div class="codehilite"><pre><span class="p">{</span> - <span class="s">"@context"</span> <span class="p">:</span> + "<span class="p">@</span><span class="n">context</span>" <span class="p">:</span> <span class="p">{</span> - <span class="s">"#types"</span> <span class="p">:</span> + "#<span class="n">types</span>" <span class="p">:</span> <span class="p">{</span> - <span class="s">"person"</span> <span class="p">:</span> <span class="s">"http://iks-project.eu/ont/person"</span><span class="p">,</span> - <span class="s">"organization"</span> <span class="p">:</span> <span class="s">"http://iks-project.eu/ont/organization"</span> + "<span class="n">person</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">iks</span><span class="o">-</span><span class="n">project</span><span class="p">.</span><span class="n">eu</span><span class="o">/</span><span class="n">ont</span><span class="o">/</span><span class="n">person</span>"<span class="p">,</span> + "<span class="n">organization</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">iks</span><span class="o">-</span><span class="n">project</span><span class="p">.</span><span class="n">eu</span><span class="o">/</span><span class="n">ont</span><span class="o">/</span><span class="n">organization</span>" <span class="p">}</span> <span class="p">}</span> <span class="p">}</span> @@ -172,13 +172,13 @@ <p>Using the instance by example variant requires the FactStore to resolve the entity in an EntityHub. An entity by example is specified by defining attributes and required values of the searched entity. A fact can only be stored if all entities can be uniquely identified either by their IRI or by example.</p> <p>Example 1: POST /factstore/facts with the following data</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">"iks"</span> <span class="p">:</span> <span class="s">"http://iks-project.eu/ont/"</span><span class="p">,</span> - <span class="s">"upb"</span> <span class="p">:</span> <span class="s">"http://upb.de/persons/"</span> + "<span class="p">@</span><span class="n">context</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">iks</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">iks</span><span class="o">-</span><span class="n">project</span><span class="p">.</span><span class="n">eu</span><span class="o">/</span><span class="n">ont</span><span class="o">/</span>"<span class="p">,</span> + "<span class="n">upb</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span><span class="o">/</span><span class="n">persons</span><span class="o">/</span>" <span class="p">},</span> - <span class="s">"@profile"</span> <span class="p">:</span> <span class="s">"iks:employeeOf"</span><span class="p">,</span> - <span class="s">"person"</span> <span class="p">:</span> <span class="p">{</span> <span class="s">"@iri"</span> <span class="p">:</span> <span class="s">"upb:bnagel"</span> <span class="p">},</span> - <span class="s">"organization"</span> <span class="p">:</span> <span class="p">{</span> <span class="s">"@iri"</span> <span class="p">:</span> <span class="s">"http://uni-paderborn.de"</span><span class="p">}</span> + "<span class="p">@</span><span class="n">profile</span>" <span class="p">:</span> "<span class="n">iks</span><span class="p">:</span><span class="n">employeeOf</span>"<span class="p">,</span> + "<span class="n">person</span>" <span class="p">:</span> <span class="p">{</span> "<span class="p">@</span><span class="n">iri</span>" <span class="p">:</span> "<span class="n">upb</span><span class="p">:</span><span class="n">bnagel</span>" <span class="p">},</span> + "<span class="n">organization</span>" <span class="p">:</span> <span class="p">{</span> "<span class="p">@</span><span class="n">iri</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">uni</span><span class="o">-</span><span class="n">paderborn</span><span class="p">.</span><span class="n">de</span>"<span class="p">}</span> <span class="p">}</span> </pre></div> @@ -236,15 +236,15 @@ <p><em>Note</em>: For the moment constraints only support the equals "=" relation. There may be more relations like ">" in future versions of this specification. If there is more than one constraint all constraints are concatenated by "AND".</p> <p>Example 1: POST /factstore/query with the following data</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">"iks"</span> <span class="p">:</span> <span class="s">"http://iks-project.eu/ont/"</span> + "<span class="p">@</span><span class="n">context</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">iks</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">iks</span><span class="o">-</span><span class="n">project</span><span class="p">.</span><span class="n">eu</span><span class="o">/</span><span class="n">ont</span><span class="o">/</span>" <span class="p">},</span> - <span class="s">"select"</span> <span class="p">:</span> <span class="p">[</span> <span class="s">"person"</span> <span class="p">],</span> - <span class="s">"from"</span> <span class="p">:</span> <span class="s">"iks:employeeOf"</span><span class="p">,</span> - <span class="s">"where"</span> <span class="p">:</span> <span class="p">[</span> + "<span class="n">select</span>" <span class="p">:</span> <span class="p">[</span> "<span class="n">person</span>" <span class="p">],</span> + "<span class="n">from</span>" <span class="p">:</span> "<span class="n">iks</span><span class="p">:</span><span class="n">employeeOf</span>"<span class="p">,</span> + "<span class="n">where</span>" <span class="p">:</span> <span class="p">[</span> <span class="p">{</span> - <span class="s">"="</span> <span class="p">:</span> <span class="p">{</span> - <span class="s">"organization"</span> <span class="p">:</span> <span class="p">{</span> <span class="s">"@iri"</span> <span class="p">:</span> <span class="s">"http://uni-paderborn.de"</span> <span class="p">}</span> + "<span class="p">=</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">organization</span>" <span class="p">:</span> <span class="p">{</span> "<span class="p">@</span><span class="n">iri</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">uni</span><span class="o">-</span><span class="n">paderborn</span><span class="p">.</span><span class="n">de</span>" <span class="p">}</span> <span class="p">}</span> <span class="p">}</span> <span class="p">]</span> @@ -254,22 +254,22 @@ <p>returns the list of all persons participating in the fact of type http://iks-project.eu/ont/employeeOf where the organization is http://uni-paderborn.de. The result is sent back in JSON-LD format with the result set specified by the select clause.</p> <div class="codehilite"><pre><span class="p">{</span> - <span class="s">"@subject"</span> <span class="p">:</span> <span class="p">[</span> + "<span class="p">@</span><span class="n">subject</span>" <span class="p">:</span> <span class="p">[</span> <span class="p">{</span> - <span class="s">"@subject"</span> <span class="p">:</span> <span class="s">"_bnode1"</span><span class="p">,</span> - <span class="s">"PERSON"</span> <span class="p">:</span> <span class="s">"http://upb.de/persons/gengels"</span> + "<span class="p">@</span><span class="n">subject</span>" <span class="p">:</span> "<span class="n">_bnode1</span>"<span class="p">,</span> + "<span class="n">PERSON</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span><span class="o">/</span><span class="n">persons</span><span class="o">/</span><span class="n">gengels</span>" <span class="p">},</span> <span class="p">{</span> - <span class="s">"@subject"</span> <span class="p">:</span> <span class="s">"_bnode2"</span><span class="p">,</span> - <span class="s">"PERSON"</span> <span class="p">:</span> <span class="s">"http://upb.de/persons/ssauer"</span> + "<span class="p">@</span><span class="n">subject</span>" <span class="p">:</span> "<span class="n">_bnode2</span>"<span class="p">,</span> + "<span class="n">PERSON</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span><span class="o">/</span><span class="n">persons</span><span class="o">/</span><span class="n">ssauer</span>" <span class="p">},</span> <span class="p">{</span> - <span class="s">"@subject"</span> <span class="p">:</span> <span class="s">"_bnode3"</span><span class="p">,</span> - <span class="s">"PERSON"</span> <span class="p">:</span> <span class="s">"http://upb.de/persons/bnagel"</span> + "<span class="p">@</span><span class="n">subject</span>" <span class="p">:</span> "<span class="n">_bnode3</span>"<span class="p">,</span> + "<span class="n">PERSON</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span><span class="o">/</span><span class="n">persons</span><span class="o">/</span><span class="n">bnagel</span>" <span class="p">},</span> <span class="p">{</span> - <span class="s">"@subject"</span> <span class="p">:</span> <span class="s">"_bnode4"</span><span class="p">,</span> - <span class="s">"PERSON"</span> <span class="p">:</span> <span class="s">"http://upb.de/persons/fchrist"</span> + "<span class="p">@</span><span class="n">subject</span>" <span class="p">:</span> "<span class="n">_bnode4</span>"<span class="p">,</span> + "<span class="n">PERSON</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span><span class="o">/</span><span class="n">persons</span><span class="o">/</span><span class="n">fchrist</span>" <span class="p">}</span> <span class="p">]</span> <span class="p">}</span> @@ -278,7 +278,7 @@ <p>If there is only one entry in the result set, this would be returned as follows.</p> <div class="codehilite"><pre><span class="p">{</span> - <span class="s">"PERSON"</span> <span class="p">:</span> <span class="s">"http://upb.de/persons/fchrist"</span> + "<span class="n">PERSON</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span><span class="o">/</span><span class="n">persons</span><span class="o">/</span><span class="n">fchrist</span>" <span class="p">}</span> </pre></div> @@ -286,17 +286,17 @@ <p>Status: <strong>Example 1 is implemented</strong>.</p> <p>Example 2: GET /factstore/query?q= with the following data as the request parameter "q"</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">"iks"</span> <span class="p">:</span> <span class="s">"http://iks-project.eu/ont/"</span> + "<span class="p">@</span><span class="n">context</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">iks</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">iks</span><span class="o">-</span><span class="n">project</span><span class="p">.</span><span class="n">eu</span><span class="o">/</span><span class="n">ont</span><span class="o">/</span>" <span class="p">},</span> - <span class="s">"select"</span> <span class="p">:</span> <span class="p">[</span> - <span class="s">"person.name"</span><span class="p">,</span> <span class="s">"person.email"</span> + "<span class="n">select</span>" <span class="p">:</span> <span class="p">[</span> + "<span class="n">person</span><span class="p">.</span><span class="n">name</span>"<span class="p">,</span> "<span class="n">person</span><span class="p">.</span><span class="n">email</span>" <span class="p">],</span> - <span class="s">"from"</span> <span class="p">:</span> <span class="s">"iks:employeeOf"</span><span class="p">,</span> - <span class="s">"where"</span> <span class="p">:</span> <span class="p">[</span> + "<span class="n">from</span>" <span class="p">:</span> "<span class="n">iks</span><span class="p">:</span><span class="n">employeeOf</span>"<span class="p">,</span> + "<span class="n">where</span>" <span class="p">:</span> <span class="p">[</span> <span class="p">{</span> - <span class="s">"="</span> <span class="p">:</span> <span class="p">{</span> - <span class="s">"organization"</span> <span class="p">:</span> <span class="p">{</span> <span class="s">"@iri"</span> <span class="p">:</span> <span class="s">"http://upb.de"</span> <span class="p">}</span> + "<span class="p">=</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">organization</span>" <span class="p">:</span> <span class="p">{</span> "<span class="p">@</span><span class="n">iri</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span>" <span class="p">}</span> <span class="p">}</span> <span class="p">}</span> <span class="p">]</span> @@ -306,15 +306,15 @@ <p>returns a list with names and e-mail addresses of all persons participating in the fact of type http://iks-project.eu/ont/employeeOf where the organization is http://upb.de. The result is sent back in JSON-LD format with the result set specified by the select clause.</p> <div class="codehilite"><pre><span class="p">{</span> - <span class="s">"resultset"</span><span class="p">:</span> <span class="p">[</span> - <span class="p">{</span> <span class="s">"person.name"</span> <span class="p">:</span> <span class="s">"Gregor Engels"</span><span class="p">,</span> - <span class="s">"person.email"</span><span class="p">:</span> <span class="s">"[email protected]"</span> <span class="p">},</span> - <span class="p">{</span> <span class="s">"person.name"</span> <span class="p">:</span> <span class="s">"Stefan Sauer"</span><span class="p">,</span> - <span class="s">"person.email"</span><span class="p">:</span> <span class="s">"[email protected]"</span> <span class="p">},</span> - <span class="p">{</span> <span class="s">"person.name"</span> <span class="p">:</span> <span class="s">"Benjamin Nagel"</span><span class="p">,</span> - <span class="s">"person.email"</span><span class="p">:</span> <span class="s">"[email protected]"</span> <span class="p">},</span> - <span class="p">{</span> <span class="s">"person.name"</span> <span class="p">:</span> <span class="s">"Fabian Christ"</span><span class="p">,</span> - <span class="s">"person.email"</span><span class="p">:</span> <span class="s">"[email protected]"</span> <span class="p">}</span> + "<span class="n">resultset</span>"<span class="p">:</span> <span class="p">[</span> + <span class="p">{</span> "<span class="n">person</span><span class="p">.</span><span class="n">name</span>" <span class="p">:</span> "<span class="n">Gregor</span> <span class="n">Engels</span>"<span class="p">,</span> + "<span class="n">person</span><span class="p">.</span><span class="n">email</span>"<span class="p">:</span> "<span class="n">engels</span><span class="p">@</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span>" <span class="p">},</span> + <span class="p">{</span> "<span class="n">person</span><span class="p">.</span><span class="n">name</span>" <span class="p">:</span> "<span class="n">Stefan</span> <span class="n">Sauer</span>"<span class="p">,</span> + "<span class="n">person</span><span class="p">.</span><span class="n">email</span>"<span class="p">:</span> "<span class="n">sauer</span><span class="p">@</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span>" <span class="p">},</span> + <span class="p">{</span> "<span class="n">person</span><span class="p">.</span><span class="n">name</span>" <span class="p">:</span> "<span class="n">Benjamin</span> <span class="n">Nagel</span>"<span class="p">,</span> + "<span class="n">person</span><span class="p">.</span><span class="n">email</span>"<span class="p">:</span> "<span class="n">nagel</span><span class="p">@</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span>" <span class="p">},</span> + <span class="p">{</span> "<span class="n">person</span><span class="p">.</span><span class="n">name</span>" <span class="p">:</span> "<span class="n">Fabian</span> <span class="n">Christ</span>"<span class="p">,</span> + "<span class="n">person</span><span class="p">.</span><span class="n">email</span>"<span class="p">:</span> "<span class="n">christ</span><span class="p">@</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span>" <span class="p">}</span> <span class="p">]</span> <span class="p">}</span> </pre></div> @@ -329,26 +329,26 @@ <p><em>Note</em>: For the moment constraints only support the equals "=" relation. There may be more relations like ">" in future versions of this specification. If there is more than one constraint all constraints are concatenated by "AND".</p> <p>Example: GET /factstore/query?q= with the following request data in request parameter "q"</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">"iks"</span> <span class="p">:</span> <span class="s">"http://iks-project.eu/ont/"</span> + "<span class="p">@</span><span class="n">context</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">iks</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">iks</span><span class="o">-</span><span class="n">project</span><span class="p">.</span><span class="n">eu</span><span class="o">/</span><span class="n">ont</span><span class="o">/</span>" <span class="p">},</span> - <span class="s">"select"</span><span class="p">:</span> <span class="p">[</span> - <span class="s">"iks:friendOf.friend.name"</span> + "<span class="n">select</span>"<span class="p">:</span> <span class="p">[</span> + "<span class="n">iks</span><span class="p">:</span><span class="n">friendOf</span><span class="p">.</span><span class="n">friend</span><span class="p">.</span><span class="n">name</span>" <span class="p">],</span> - <span class="s">"join"</span> <span class="p">:</span> <span class="p">{</span> - <span class="s">"iks:employeeOf.person"</span> <span class="p">:</span> <span class="s">"iks:friendOf.person"</span> + "<span class="n">join</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">iks</span><span class="p">:</span><span class="n">employeeOf</span><span class="p">.</span><span class="n">person</span>" <span class="p">:</span> "<span class="n">iks</span><span class="p">:</span><span class="n">friendOf</span><span class="p">.</span><span class="n">person</span>" <span class="p">},</span> - <span class="s">"where"</span> <span class="p">:</span> <span class="p">[</span> + "<span class="n">where</span>" <span class="p">:</span> <span class="p">[</span> <span class="p">{</span> - <span class="s">"="</span> <span class="p">:</span> <span class="p">{</span> - <span class="s">"iks:employeeOf.organization"</span> <span class="p">:</span> <span class="p">{</span> - <span class="s">"@iri"</span> <span class="p">:</span> <span class="s">"http://upb.de"</span> + "<span class="p">=</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">iks</span><span class="p">:</span><span class="n">employeeOf</span><span class="p">.</span><span class="n">organization</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="p">@</span><span class="n">iri</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">upb</span><span class="p">.</span><span class="n">de</span>" <span class="p">}</span> <span class="p">}</span> <span class="p">},</span> <span class="p">{</span> - <span class="s">"="</span> <span class="p">:</span> <span class="p">{</span> - <span class="s">"iks:friendOf.friend.city"</span> <span class="p">:</span> <span class="s">"Paderborn"</span> + "<span class="p">=</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">iks</span><span class="p">:</span><span class="n">friendOf</span><span class="p">.</span><span class="n">friend</span><span class="p">.</span><span class="n">city</span>" <span class="p">:</span> "<span class="n">Paderborn</span>" <span class="p">}</span> <span class="p">}</span> <span class="p">]</span> @@ -358,14 +358,14 @@ <p>will return a list of names of all the friends living in Paderborn of the employees of the University of Paderborn. The result in JSON-LD format would look like the following.</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">"iks"</span> <span class="p">:</span> <span class="s">"http://iks-project.eu/ont/"</span> + "<span class="p">@</span><span class="n">context</span>" <span class="p">:</span> <span class="p">{</span> + "<span class="n">iks</span>" <span class="p">:</span> "<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">iks</span><span class="o">-</span><span class="n">project</span><span class="p">.</span><span class="n">eu</span><span class="o">/</span><span class="n">ont</span><span class="o">/</span>" <span class="p">},</span> - <span class="s">"resultset"</span><span class="p">:</span> <span class="p">[</span> - <span class="p">{</span> <span class="s">"iks:friendOf.friend.name"</span> <span class="p">:</span> <span class="s">"Schmidt"</span> <span class="p">},</span> - <span class="p">{</span> <span class="s">"iks:friendOf.friend.name"</span> <span class="p">:</span> <span class="s">"Meier"</span> <span class="p">},</span> - <span class="p">{</span> <span class="s">"iks:friendOf.friend.name"</span> <span class="p">:</span> <span class="s">"Schneider"</span> <span class="p">},</span> - <span class="p">{</span> <span class="s">"iks:friendOf.friend.name"</span> <span class="p">:</span> <span class="s">"Schuster"</span> <span class="p">}</span> + "<span class="n">resultset</span>"<span class="p">:</span> <span class="p">[</span> + <span class="p">{</span> "<span class="n">iks</span><span class="p">:</span><span class="n">friendOf</span><span class="p">.</span><span class="n">friend</span><span class="p">.</span><span class="n">name</span>" <span class="p">:</span> "<span class="n">Schmidt</span>" <span class="p">},</span> + <span class="p">{</span> "<span class="n">iks</span><span class="p">:</span><span class="n">friendOf</span><span class="p">.</span><span class="n">friend</span><span class="p">.</span><span class="n">name</span>" <span class="p">:</span> "<span class="n">Meier</span>" <span class="p">},</span> + <span class="p">{</span> "<span class="n">iks</span><span class="p">:</span><span class="n">friendOf</span><span class="p">.</span><span class="n">friend</span><span class="p">.</span><span class="n">name</span>" <span class="p">:</span> "<span class="n">Schneider</span>" <span class="p">},</span> + <span class="p">{</span> "<span class="n">iks</span><span class="p">:</span><span class="n">friendOf</span><span class="p">.</span><span class="n">friend</span><span class="p">.</span><span class="n">name</span>" <span class="p">:</span> "<span class="n">Schuster</span>" <span class="p">}</span> <span class="p">]</span> <span class="p">}</span> </pre></div> Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/faq.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/faq.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/faq.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/features.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/features.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/features.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/index.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/index.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/index.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/mailinglists.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/mailinglists.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/mailinglists.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/multilingual.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/multilingual.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/multilingual.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul> @@ -116,7 +116,7 @@ <p>This enables the profile to build the OpenNLP models for all languages.</p> <p>After this the bundles are available in the folder</p> -<div class="codehilite"><pre><span class="p">{</span><span class="n">stanbol</span><span class="o">-</span><span class="n">root</span><span class="p">}</span><span class="sr">/data/o</span><span class="n">pennlp</span><span class="sr">/lang/</span><span class="p">{</span><span class="n">language</span><span class="p">}</span><span class="o">/</span><span class="n">target</span> +<div class="codehilite"><pre><span class="p">{</span><span class="n">stanbol</span><span class="o">-</span><span class="n">root</span><span class="p">}</span><span class="o">/</span><span class="n">data</span><span class="o">/</span><span class="n">opennlp</span><span class="o">/</span><span class="n">lang</span><span class="o">/</span><span class="p">{</span><span class="n">language</span><span class="p">}</span><span class="o">/</span><span class="n">target</span> </pre></div> @@ -138,8 +138,7 @@ <li><strong>Redirect Mode:</strong> Defines how to process redirects of Entities mentioned in the parsed content.. Three modes to deal with such links are supported: Ignore redirects; Add values from redirected Entities to extracted; Follow Redirects and suggest the redirected Entity instead of the extracted. </li> <li><strong>Min Token Length:</strong> The minimum length of Tokens used to lookup Entities within the Controlled Vocabulary. This parameter is ignored in case a POS (Part of Speech) tagger is available for the language of the parsed content.</li> <li><strong>Suggestions:</strong> The maximal number of suggestions returned for a single mention. (org.apache.stanbol.enhancer.engines.keywordextraction.maxSuggestions) -Languages <br /> -</li> +Languages </li> <li><strong>Languages to process:</strong> An empty text indicates that all languages are processed. Use ',' as separator for languages (e.g. 'en,de' to enhance only English and German texts). </li> <li><strong>Default Matching Language:</strong> The language used in addition to the language detected for the analysed text to search for Entities. Typically this configuration is an empty string to search for labels without any language defined, but for some data sets (such as DBpedia.org) that add languages to any labels it might improve resuls to change this configuration (e.g. to 'en' in the case of DBpedia.org).</li> </ul> Modified: websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/ontologymanager/index.html ============================================================================== --- websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/ontologymanager/index.html (original) +++ websites/staging/stanbol/trunk/content/docs/0.9.0-incubating/ontologymanager/index.html Thu Nov 20 12:50:47 2014 @@ -67,7 +67,7 @@ </ul> <h1 id="project">Project</h1> <ul> -<li><a href="/pmc/">PMC</a></li> +<li><a href="/team.html">Team</a></li> <li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li> <li><a href="/privacy-policy.html">Privacy Policy</a></li> </ul>
