Author: rwesten
Date: Wed Feb 15 07:35:02 2012
New Revision: 1244386
URL: http://svn.apache.org/viewvc?rev=1244386&view=rev
Log:
Minor corrections
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.png
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.png
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.png
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/chains/executionplan.png?rev=1244386&r1=1244385&r2=1244386&view=diff
==============================================================================
Binary files - no diff available.
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext?rev=1244386&r1=1244385&r2=1244386&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
Wed Feb 15 07:35:02 2012
@@ -92,7 +92,7 @@ The following figure provides an overvie
-Serialization Rules:
+__ContentItem Container:__
* ContentItems are con tainted within an "multipart/from-data" container
* 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.
@@ -100,7 +100,7 @@ Serialization Rules:
The default Content-Type for serialized ContentItems is therefore
"multipart/form-data; boundary=contentItem; charset=UTF-8"
-### Metadata:
+__Enhancement Metadata:__
* If present this MUST BE the first MIME part within the "multipart/from-data"
container representing the ContentItem.
* The "name" parameter of the "Content-Disposition" header MUST BE "metadata"
@@ -108,7 +108,7 @@ The default Content-Type for serialized
* The "Content-Type" of the metadata can be any RDF serialization supported by
Apache Stanbol. UTF-8 is used as default charset.
* The RDF data serialized in this MIME part represent the enhancement results.
-### Content
+__Content:__
* 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.
* Because multiple Content variants can be included within a ContentItem a
"multipart/alternate" container is used to represent the content.
@@ -121,9 +121,9 @@ The different content elements are conta
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.
-### Additional Metadata
+__Additional Metadata:__
-The [ContentPart API](#contentparts) 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.
+The [ContentPart API](#content_parts) 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.
* MimeParts representing such ContentParts MUST BE added after the MIME parts
for the "metadata" AND the "content"
* The "name" parameter of the "Content-Disposition" MUST BE set to the URI of
the ContentPart in the ContentItem.
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.png
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/executionmetadata.png?rev=1244386&r1=1244385&r2=1244386&view=diff
==============================================================================
Binary files - no diff available.
