Author: buildbot
Date: Thu Feb  9 15:33:41 2012
New Revision: 804351

Log:
Staging update by buildbot for stanbol

Added:
    websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/
    
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/cmsadapter5min.html
    
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/index.html

Added: 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/cmsadapter5min.html
==============================================================================
--- 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/cmsadapter5min.html
 (added)
+++ 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/cmsadapter5min.html
 Thu Feb  9 15:33:41 2012
@@ -0,0 +1,134 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+  <title>Apache Stanbol - </title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <link rel="icon" type="image/png" 
href="/stanbol/images/stanbol-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+  <div id="navigation"> 
+  <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" 
height="101" border="0" 
src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+  <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL";>Issue 
Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the_asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org";>Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html";>Become a 
Sponsor</a></li>
+<li><a href="http://www.apache.org/security/";>Security</a></li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title"></h1>
+    <h1 id="5_minutes_documentation_for_cms_adapter">5 Minutes Documentation 
for CMS Adapter</h1>
+<p>CMS Adapter component acts as a bridge between content management systems 
and the Apache Stanbol. Please note that all components of Apache Stanbol also 
provides RESTful services which allow accesing them directly from outside. CMS 
Adapter interacts with content management systems through JCR and CMIS 
specifications. In other words, any content repository compliant with JCR or 
CMIS specifications can make use of CMS Adapter functionalities. For the time 
being, there are two main functionalities that CMS Adapter offers: 
"Bidirectional Mapping" and "Contenthub Feed". </p>
+<p><strong>Note</strong>: URLs given in the curl commands and link are valid 
as long as full launcher of the Stanbol is launched with the default 
configurations. In other words, it assumed that the root URL of the Stanbol is 
<strong>http://localhost:8080</strong>.</p>
+<h2 id="session_management">Session Management</h2>
+<p>To be able to use Contenthub features, it is necessary to get a session key 
beforehand. While obtaining this key, CMS Adapter caches a JCR/CMIS session to 
be used when the generated session key is passed in the subsequent operations 
that require interaction with the content repository. A session can key can be 
obtained through REST services as follows:</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span 
class="o">-</span><span class="n">X</span> <span class="n">GET</span> <span 
class="o">-</span><span class="n">H</span> <span class="s">&quot;Accept: 
text/plain&quot;</span> <span 
class="s">&quot;http://localhost:8080/cmsadapter/session?repositoryURL=rmi://localhost:1099/crx&amp;workspaceName=demo&amp;username=admin&amp;password=admin&amp;connectionType=JCR&quot;</span>
+</pre></div>
+
+
+<p>In this example a session key is obtained for a JCR compliant repository. 
CMS Adapter use RMI protocol to get session from JCR repositories or it tries 
to access repository via a URL. So, RMI endpoint or URL of the repository is 
specified. Furthermore target workspace in the repository has been specified 
together with the username and password to access it. While accessing CMIS 
repositories AtomPub binding is used, so repository URL should be specified 
considering this protocol.</p>
+<p>Apart from the retrieval of session key by providing one by one as in the 
RESTful example, Java API of CMS Adapter also allows obtaining a session key 
with an already available session object through the SessionManager service. 
Thus, this is a more convenient way while obtaining a session key using CMS 
Adapter through its Java API.</p>
+<h2 id="bidirectional_mapping">Bidirectional Mapping</h2>
+<p>This feature provides bidirectional mappings between JCR/CMIS compliant 
content repositories and external RDF data. Using this feature it is possible 
to generate RDF data from content repository or populate content repository 
based on the external RDF data.</p>
+<p>The functionality described in this feature is realized by a two-step 
process. This process includes sequential execution of RDFBridge and RDFMapper 
services of CMS Adapter. Considering the update of content repository based on 
external RDF data, in the first step the given raw RDF data is annotated with 
standard terms by RDFBridge. There are a few terms that are described in the 
<strong>CMS Vocabulary</strong> section. RDFMapper processes the annotated RDF 
and update the content repository accordingly. From the other direction, in the 
first step content repository structure is transformed into RDF annotated with 
the CMS Vocabulary terms by RDFMappers. In the second step RDFBridges add 
implementation specific annotations.</p>
+<p>From one perspective, bidirectional mapping feature makes possible to 
exploit open linked data, which is already available on the web, in content 
management systems. Apart from the already available RDF data on the web, any 
RDF data can be mapped to content repository. By mapping external RDF data 
existing content repository items can be updated or new ones created. </p>
+<p>This services is also available through RESTful API. A curl command as 
follows will map the rdf data given in rdfData file to content repository. The 
mapping done according to configurations of default RDF Bridge implementation 
which can be changed through the <strong>Apache Stanbol CMS Adapter Default RDF 
Bridge Configurations</strong> entry of <a 
href="http://localhost:8080/system/console/configMgr";>Configuration Panel 
Apache Felix Web Console</a>. It is possible to define several configurations 
and all of these configurations are processed in transformation process. In 
case of no configuration, provided RDF is processed by RDFMapper directly.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span 
class="o">-</span><span class="n">i</span> <span class="o">-</span><span 
class="n">X</span> <span class="n">POST</span> <span class="o">--</span><span 
class="n">data</span><span class="o">-</span><span class="n">urlencode</span> 
<span class="s">&quot;serializedGraph@rdfData&quot;</span> <span 
class="o">--</span><span class="n">data</span> <span 
class="s">&quot;sessionKey=9ef42d3c-aaa3-494f-ba6f-c247a58ac2db&quot;</span> 
<span class="n">http:</span><span class="sr">//</span><span 
class="n">localhost:8080</span><span class="sr">/cmsadapter/m</span><span 
class="n">ap</span><span class="o">/</span><span class="n">rdf</span>
+</pre></div>
+
+
+<p>This <a 
href="http://blog.iks-project.eu/adding-knowledge-to-jcrcmis-content-repositories/";>blog
 post</a> from October 2011 describes the process of adding knowledge from 
DBPedia to a Nuxeo content management system which is a CMIS compliant 
repository. </p>
+<p>From the other perspective, thanks to this feature repository structure can 
be transformed into RDF through RESTful services as well. A curl command 
similar to following one can be used to map content repository structure into 
RDF format.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span 
class="o">-</span><span class="n">i</span> <span class="o">-</span><span 
class="n">X</span> <span class="n">POST</span> <span class="o">--</span><span 
class="n">data</span> <span 
class="s">&quot;sessionKey=9ef42d3c-aaa3-494f-ba6f-c247a58ac2db&amp;baseURI=http://www.apache.org/stanbol/cms&quot;</span>
 <span class="n">http:</span><span class="sr">//</span><span 
class="n">localhost:8080</span><span class="sr">/cmsadapter/m</span><span 
class="n">ap</span><span class="o">/</span><span class="n">cms</span>
+</pre></div>
+
+
+<p>Note that during the mapping process of bidirectional mappings the same RDF 
Bridge configurations are used in both directions. Also, 
<strong>baseURI</strong> is a mandatory parameter that is used as the base URI 
of the RDF to be generated.</p>
+<p>RDF representation of a content management system helps building semantic 
services on top of the existing system. Contenthub component of Apache Stanbol 
can be used to provide semantic indexing and search functionalities based on 
the RDF representation of content repositories. That is, the RDF representation 
is used as a resource that Contenthub uses to populate the underlying semantic 
index.</p>
+<h2 id="contenthub_feed">Contenthub Feed</h2>
+<p>Contenthub feed feature aims to manage content repository items within the 
Contenthub component of Apache Stanbol. The management process includes only 
two types of operations, submit and delete. </p>
+<p>Submission and deletion operations can be done based on the identifiers of 
path of the content repository items. During the submission process, properties 
of content repository items are collected and they are stored along with the 
actual content. This makes possible faceted search over the properties of 
items.</p>
+<p>RESTful API of CMS Adapter can be used submit content repository items to 
Contenthub.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span 
class="o">-</span><span class="n">i</span> <span class="o">-</span><span 
class="n">X</span> <span class="n">POST</span> <span class="o">--</span><span 
class="n">data</span> <span 
class="s">&quot;sessionKey=9ef42d3c-aaa3-494f-ba6f-c247a58ac2db&amp;path=/contenthubfeedtest&amp;recursive=true&quot;</span>
 <span class="n">http:</span><span class="sr">//</span><span 
class="n">localhost:8080</span><span class="sr">/cmsadapter/co</span><span 
class="n">ntenthubfeed</span>
+</pre></div>
+
+
+<p>The previous curl command submits all content repository items under the 
<strong>/contenthubfeedtest</strong> path to the Contenthub. In a similar way 
content item can be deleted from Contenthub. Following command deletes the 
content items corresponding to the content repository items under the 
/contenthubfeedtest path.</p>
+<div class="codehilite"><pre><span class="n">curl</span> <span 
class="o">-</span><span class="n">i</span> <span class="o">-</span><span 
class="n">X</span> <span class="n">DELETE</span> <span class="o">--</span><span 
class="n">data</span> <span 
class="s">&quot;sessionKey=9ef42d3c-aaa3-494f-ba6f-c247a58ac2db&amp;path=/contenthubfeedtest&amp;recursive=true&quot;</span>
 <span class="n">http:</span><span class="sr">//</span><span 
class="n">localhost:8080</span><span class="sr">/cmsadapter/co</span><span 
class="n">ntenthubfeed</span>
+</pre></div>
+
+
+<h2 id="cms_vocabulary">CMS Vocabulary</h2>
+<p>This vocabulary aims to provide a standardized mapping between content 
repositories and RDF data. This vocabulary includes a small number of essential 
terms to map an RDF data to a content repository. As well as general terms that 
are commonly used for both JCR and CMIS repositories there are also JCR or CMIS 
specific terms.</p>
+<h3 id="general_terms">General Terms</h3>
+<ul>
+<li>CMS_OBJECT: In a CMS vocabulary annotated RDF, if a resource has this URI 
reference as value of its rdf:type property, the subject of that resource 
represents a content repository item e.g a node in JCR compliant content 
repositories or an object in CMIS compliant content repositories.</li>
+<li>CMS_OBJECT_NAME: This URI reference represents the name of the content 
repository item.</li>
+<li>CMS_OBJECT_PATH: This URI reference represents the absolute path of the 
content repository item.</li>
+<li>CMS_OBJECT_PARENT_REF: This URI reference represents the item to be 
created as parent of the item having this property.</li>
+<li>CMS_OBJECT_HAS_URI: This URI reference represents the URI which is 
associated with the content repository item.</li>
+</ul>
+<h3 id="jcr_specific_properties">JCR Specific Properties</h3>
+<ul>
+<li>JCR_PRIMARY_TYPE: This URI reference represents primary node of the 
content repository item associated with the resource within the RDF.</li>
+<li>JCR_MIXIN_TYPES: This URI reference represents the mixin type of the 
content repository item associated with the resource within the RDF.</li>
+</ul>
+<h3 id="cmis_specific_properties">CMIS Specific Properties</h3>
+<ul>
+<li>CMIS_BASE_TYPE_ID: This URI reference represents the base type of the 
content repository item associated with the resource within the RDF.</li>
+</ul>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2010 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0";>Apache 
License, Version 2.0</a>.
+        <br />
+        Apache, Stanbol and the Apache feather and Stanbol logos are 
trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/index.html
==============================================================================
--- 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/index.html 
(added)
+++ 
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/index.html 
Thu Feb  9 15:33:41 2012
@@ -0,0 +1,90 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
+  <title>Apache Stanbol - </title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <link rel="icon" type="image/png" 
href="/stanbol/images/stanbol-logo/stanbol-favicon.png"/>
+</head>
+
+<body>
+  <div id="navigation"> 
+  <a href="/stanbol/index.html"><img alt="Apache Stanbol" width="220" 
height="101" border="0" 
src="/stanbol/images/stanbol-logo/stanbol-2010-12-14.png"/></a>
+  <h1 id="stanbol">Stanbol</h1>
+<ul>
+<li><a href="/stanbol/index.html">Home</a></li>
+<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
+</ul>
+<h1 id="project">Project</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/mailinglists.html">Mailing Lists</a></li>
+<li><a href="https://issues.apache.org/jira/browse/STANBOL";>Issue 
Tracker</a></li>
+<li><a href="/stanbol/team.html">Project Team</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0";>License</a></li>
+</ul>
+<h1 id="downloads">Downloads</h1>
+<ul>
+<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
+</ul>
+<h1 id="the_asf">The ASF</h1>
+<ul>
+<li><a href="http://www.apache.org";>Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html";>Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html";>Become a 
Sponsor</a></li>
+<li><a href="http://www.apache.org/security/";>Security</a></li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title"></h1>
+    <h1 id="cms_adapter">CMS Adapter</h1>
+<p>CMS Adapter component acts as a bridge between content management systems 
and the Apache Stanbol. Please note that all components of Apache Stanbol also 
provides RESTful services which allow accesing them directly from outside. CMS 
Adapter interacts with content management systems through JCR and CMIS 
specifications. In other words, any content repository compliant with JCR or 
CMIS specifications can make use of CMS Adapter functionalities. For the time 
being, there are two main functionalities that CMS Adapter offers: 
"Bidirectional Mapping" and "Contenthub Feed". </p>
+<h2 id="bidirectional_mapping">Bidirectional Mapping</h2>
+<p>From one perspective, this feature enables content management systems to 
represent their content repository structure in RDF format. This helps building 
semantic services on top of the existing content management systems using their 
RDF representation. </p>
+<p>From the other perspective, bidirectional mapping feature makes possible to 
exploit open linked data, which is already available on the web, in content 
management systems. Apart from the already available data on the web, any RDF 
data can be mapped to content repository. By mapping external RDF data existing 
content repository items can be updated or new ones created. </p>
+<h2 id="contenthub_feed">Contenthub Feed</h2>
+<p>Contenthub feed feature of CMS Adapter provides managemet of content 
repository items within Contenthub. The management process includes only two 
types of operations, namely: submit and delete. By submitting content items to 
Contenthub, you can make use of indexing and search functionalities of 
Contenthub over the submitted items.</p>
+<h2 id="use_cases">Use Cases</h2>
+<h3 id="faceted_search">Faceted Search</h3>
+<p>As properties of content repository items are submitted to Contenthub along 
with the actual content, it is possible to provide to obtain faceted search 
facility for the content items managed within Contenthub. Furthermore, any kind 
of Solr query can be executed on the index keeping the submitted content 
items.</p>
+<h3 id="exploiting_linked_data">Exploiting Linked Data</h3>
+<p>Chance of mapping any RDF data to content repository enables users making 
use of <a href="http://linkeddata.org/";>open linked data</a> available on the 
web. Current implementation is especially handy for hierarchical RDF data e.g. 
category, topic hierarchies. Users can populate content repositories with 
hierarchies in which further content items can be created.</p>
+<h2 id="building_and_launching">Building and Launching</h2>
+<p>Since CMS Adapter is included in the Full Launcher of Apache Stanbol it is 
built with Apache Stanbol by default and can be launched under Apache Stanbol 
Full Launcher. For detailed instructions to build and launch Apache Stanbol see 
this README file.</p>
+<p>CMS Adapter serves its features through its Java API together with the 
corresponding RESTful services. Restful services can be accessed starting from 
the root resource: http://localhost:8080/cmsadapter after launching the full 
launcher with default configurations.</p>
+<p>More detailed information can be found in <a href="cmsadapter5min">5-minute 
documentation</a> of CMS Adapter.</p>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2010 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0";>Apache 
License, Version 2.0</a>.
+        <br />
+        Apache, Stanbol and the Apache feather and Stanbol logos are 
trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>


Reply via email to