svn commit: r805175 - in /websites/staging/stanbol/trunk: ./ content/stanbol/docs/trunk/enhancer/enhancerrest.html

[bu...@apache.org]

Author: buildbot
Date: Fri Feb 17 11:54:15 2012
New Revision: 805175

Log:
Staging update by buildbot for stanbol

Modified:
    websites/staging/stanbol/trunk/   (props changed)
    websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/enhancerrest.html

Propchange: websites/staging/stanbol/trunk/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Feb 17 11:54:15 2012
@@ -1 +1 @@
-1245395
+1245416

Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/enhancerrest.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/enhancerrest.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/enhancerrest.html Fri Feb 17 11:54:15 2012
@@ -109,11 +109,11 @@ In addition this request is directed to 
 <p>The following QueryParameters are defined by the multi-part content item extension:</p>
 <ul>
 <li>
-<p><strong>outputContentType=[mediaType]:</strong> Allows to specify the Mimetypes of content included within the Response of the Stanbol Enhancer. This parameter supports wild cards (e.g. '<em>' ... all, 'text/</em>'' ... all text versions,  'text/plain' ... only the plain text version). This parameter can be used multiple times.</p>
+<p><strong>outputContent=[mediaType]:</strong> Allows to specify the Mimetypes of content included within the Response of the Stanbol Enhancer. This parameter supports wild cards (e.g. '<em>' ... all, 'text/</em>'' ... all text versions,  'text/plain' ... only the plain text version). This parameter can be used multiple times.</p>
 <p>Responses to requests with this parameter will be encoded as <code>multipart/from-data</code>. If the "Accept" header of the request is not compatible to <code>multipart/from-data</code> it is assumed as a <code>400 BAD_REQUEST</code>. For details see the documentation of the <a href="contentitem.html#multipart_mime_serialization">Multipart MIME format for ContentItems</a>.</p>
 </li>
 <li>
-<p><strong>omitParsed=[true/false]:</strong> Makes only sense in combination with  the <code>outputContentType</code> parameter. This allows to exclude all content included in the request from the response. A typical combination is <code>outputContentType=<em>/</em>&amp;omitParsed=true</code>. The default value of this parameter is <code>false</code></p>
+<p><strong>omitParsed=[true/false]:</strong> Makes only sense in combination with  the <code>outputContent</code> parameter. This allows to exclude all content included in the request from the response. A typical combination is <code>outputContent=<em>/</em>&amp;omitParsed=true</code>. The default value of this parameter is <code>false</code></p>
 </li>
 <li>
 <p><strong>outputContentPart=[uri/'*']:</strong> This parameter allows to explicitly include content parts with a specific URI in the response. Currently this only supports <a href="contentitem.html#content_parts">ContentParts</a> that are stored as RDF graphs. </p>