You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by rw...@apache.org on 2012/02/16 08:48:00 UTC
svn commit: r1244874 - /incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext

Author: rwesten
Date: Thu Feb 16 07:48:00 2012
New Revision: 1244874

URL: http://svn.apache.org/viewvc?rev=1244874&view=rev
Log:
Trying syntax hilighter on code blocks as described on http://wiki.apache.org/general/ApacheCms2010

Modified:
    incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext

Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext?rev=1244874&r1=1244873&r2=1244874&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/index.mdtext Thu Feb 16 07:48:00 2012
@@ -12,11 +12,13 @@ The following figure provides an overvie
 
 The content to analyze should be sent in a POST request with the mimetype specified in the Content-type header. The response will hold the RDF enhancement serialized in the format specified in the Accept header:
 
+    :::bash
     curl -X POST -H "Accept: text/turtle" -H "Content-type: text/plain" \
         --data "John Smith was born in London." http://localhost:8080/enhancer
 
 The RESTful interface also provides parameters that can be used to parse/request additional informations. The following Example shows a request that would answer with the plain/text version of the parsed HTML content
 
+    :::bash
     curl -v -X POST -H "Accept: text/plain" \
         -H "Content-type: text/html; charset=UTF-8" \
         --data "<html><body><p>John Smith was born in London.</p></body></html>" \
@@ -57,6 +59,7 @@ This code snipped shows how to enhance a
     
 After the enhancement process finishes ContentIems do not only contain the metadata but also other informations such as converted versions of the parsed content. The following code snippet shows how to retrieve the text version of the parsed HTML content such as created by the [Metaxa Engine](engines/metaxaengine.html).
 
+    :::java
     Entry<UriRef,Blob> textContentPart = 
             ContentItemHelper.getBlob(contentItem, 
                 Collections.singleton("text/plain"));
@@ -115,6 +118,7 @@ The entity annotation type refers to nam
 
 The Apache Stanbol enhancer is able to serialize the response in the following RDF formats:
 
+    :::none
     application/json (JSON-LD)
     application/rdf+xml (RDF/XML)
     application/rdf+json (RDF/JSON)
@@ -123,6 +127,7 @@ The Apache Stanbol enhancer is able to s
 
 By default the URI of the content item being enhanced is a local, non de-referencable URI automatically built out of a hash digest of the binary content. Sometimes it might be helpful to provide the URI of the content-item to be used in the enhancements RDF graph. This can be achieved by passing a URI request parameter as follows:
 
+    :::bash
     curl -X POST -H "Accept: text/turtle" -H "Content-type: text/plain" \
     --data "John Smith was born in London." \
     "http://localhost:8080/engines?uri=urn:fise-example-content-item"