Author: buildbot
Date: Wed Feb 15 07:35:06 2012
New Revision: 804886
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/ (props changed)
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.png
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/contentitem.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.png
Propchange: websites/staging/stanbol/trunk/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb 15 07:35:06 2012
@@ -1 +1 @@
-1244385
+1244386
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.png
==============================================================================
Binary files - no diff available.
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/contentitem.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/contentitem.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/contentitem.html
Wed Feb 15 07:35:06 2012
@@ -134,14 +134,14 @@
<p>Stanbol supports the serialization of ContentItems as Multipart MIME. This
serialization is used by the RESTful API of the Stanbol Enhancer. This section
provides details about how ContentItems are represented using Multipart MIME.
For more information on how to send/receive multipart content items via the
RESTful Serivces provided by the Stanbol Enhancer please see the documentation
provided in the Web Interface (e.g. http://localhost:8080/enhancer).</p>
<p>The following figure provides an overview on how ContentItems are
represented using MultiPart MIME.</p>
<p><img alt="ConentItem Multipart MIME format"
src="contentitemmultipartmime.png" title="This figure provides an overview on
how ContentItems are serialize as MultiPart MIME" /></p>
-<p>Serialization Rules:</p>
+<p><strong>ContentItem Container:</strong></p>
<ul>
<li>ContentItems are con tainted within an "multipart/from-data" container</li>
<li>Apache Stanbol uses "contentItem" as "boundary", but users may use any as
long as the "boundary" parameter in the "Content-Type" header is set
correctly.</li>
<li>Stanbol uses UTF-8 as charset, but users might use any supported encoding
as long as the "charset" parameter in the "Content-Type" header is set
accordingly.</li>
</ul>
<p>The default Content-Type for serialized ContentItems is therefore
"multipart/form-data; boundary=contentItem; charset=UTF-8"</p>
-<h3 id="metadata">Metadata:</h3>
+<p><strong>Enhancement Metadata:</strong></p>
<ul>
<li>If present this MUST BE the first MIME part within the
"multipart/from-data" container representing the ContentItem.</li>
<li>The "name" parameter of the "Content-Disposition" header MUST BE
"metadata"</li>
@@ -149,7 +149,7 @@
<li>The "Content-Type" of the metadata can be any RDF serialization supported
by Apache Stanbol. UTF-8 is used as default charset.</li>
<li>The RDF data serialized in this MIME part represent the enhancement
results.</li>
</ul>
-<h3 id="content">Content</h3>
+<p><strong>Content:</strong></p>
<ul>
<li>If present the MIME part representing the Content MUST directly follow the
Metadata. If the Metadata are not present the Content MUST BE the first MIME
part within the "multipart/from-data" container representing the
ContentItem.</li>
<li>Because multiple Content variants can be included within a ContentItem a
"multipart/alternate" container is used to represent the content.</li>
@@ -161,8 +161,8 @@
<li>the "Content-Type" header must correspond to the media type of the
content</li>
</ul>
<p>Note that users that want to send a single ContentPart AND Metadata to the
Stanbol Enhancer can also directly add the content to the "multipart/from-data"
container of the ContentItem. In this case the "name" parameter MUST BE still
set to "content" but the "Content-Type" header needs to be directly set to the
media type of the parsed ContentPart. The Stanbol Enhancer does NOT use this
option when serializing ContentItems. It will ALWAYS use a
"multipart/alternate" container for the "content" even when only a single
ContnetPart is included in an Response.</p>
-<h3 id="additional_metadata">Additional Metadata</h3>
-<p>The <a href="#contentparts">ContentPart API</a> of the Stanbol ContentItem
allows to register content parts of any type. The MultiPart MIME serialization
of ContentItems supports the serialization of such additional parts as long as
they are encoded as RDF graphs (compatible to the Clerezza TripleCollection
class). Additional ContentParts that are not encoded as RDF data are currently
not supported by the Multipart MIME serialization.</p>
+<p><strong>Additional Metadata:</strong></p>
+<p>The <a href="#content_parts">ContentPart API</a> of the Stanbol ContentItem
allows to register content parts of any type. The MultiPart MIME serialization
of ContentItems supports the serialization of such additional parts as long as
they are encoded as RDF graphs (compatible to the Clerezza TripleCollection
class). Additional ContentParts that are not encoded as RDF data are currently
not supported by the Multipart MIME serialization.</p>
<ul>
<li>MimeParts representing such ContentParts MUST BE added after the MIME
parts for the "metadata" AND the "content"</li>
<li>The "name" parameter of the "Content-Disposition" MUST BE set to the URI
of the ContentPart in the ContentItem.</li>
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.png
==============================================================================
Binary files - no diff available.
