Any23 Library

The RDFizer web service turns microformats into RDF, as well as extracting RDFa and convert from different RDF serialization formats. The details about how microformats are converted into RDF can be found in the microformat support section. The service uses the Any23 v0.4.1 library for extraction and conversion.

Convert document at URI

Pick an output format and enter the URI of a web document:

http://api.sindice.com/any23/any23/
best turtle ntriples nquads rdfxml

/

Fix[?] Report[?]

Convert copy&pasted document

Input format:

Output format:

auto-detect HTML with RDFa or microformats (text/html) XHTML with RDFa or microformats (application/xhtml+xml) Turtle (text/turtle) N-Triples (text/plain) N-Quads (text/plain) RDF/XML (application/rdf+xml) best (content-negotiated) turtle ntriples nquads rdfxml Fix[?] Report[?] @prefix foaf: <http://xmlns.com/foaf/0.1/> . [] a foaf:Person; foaf:name "John X. Foobar"; foaf:mbox_sha1sum "cef817456278b70cee8e5a1611539ef9d928810e"; .

Examples

Compact API

HTTP GET requests can be made to URIs of the shape

http://api.sindice.com/any23/any23/format/input-uri

The response is the input document converted to the desired output format.

Form-style GET API

HTTP GET requests can be made to the URI http://api.sindice.com/any23/any23/ with the following query parameters:

uri	URI of an input document
format	Desired output format; defaults to best

The response is the input document converted to the desired output format.

Direct POST API

HTTP POSTing a document body to http://api.sindice.com/any23/any23/format will convert the document to the specified output format. The media type of the input has to be specified in the Content-Type HTTP header. Depending on the servlet container, a Content-Length header specifying the length of the input document in bytes might also be required. Typical media types for supported input formats are:

Input format	Media type
HTML	text/html
RDF/XML	application/rdf+xml
Turtle	text/turtle
N-Triples	text/plain
N-Quads	text/plain

Example POST request:

POST /rdfxml HTTP/1.0
Host: example.com
Content-Type: text/turtle
Content-Length: 174
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
[] a foaf:Person;
    foaf:name "John X. Foobar";
    foaf:mbox_sha1sum "cef817456278b70cee8e5a1611539ef9d928810e";
    .

Form-style POST API

A document body can also be converted by HTTP POSTing form data to http://api.sindice.com/any23/any23/. The Content-Type HTTP header must be set to application/x-www-form-urlencoded. The following parameters are supported:

type	Media type of the input, see the table above. If not present, auto-detection will be attempted.
body	Document body to be converted
format	Desired output format; defaults to best

Output formats

Supported output format identifiers are:

• best for content negotiation according to the client's Accept HTTP header
• turtle, ttl, n3 for Turtle/N3
• ntriples, nt for N-Triples
• nquads, nq for N-Quads
• rdfxml, rdf, xml for RDF/XML

Error reporting

Processing errors are indicated via HTTP status codes and brief text/plain error messages. The following status codes can be returned:

Code	Reason
200 OK	Success
204 No Content	Extraction from input was successful, but yielded zero triples
400 Bad Request	Missing or malformed input parameter
404 Not Found	Malformed request URI
406 Not Acceptable	None of the media types specified in the Accept header are supported
415 Unsupported Media Type	Document body with unsupported media type was POSTed
502 Bad Gateway	Input document from a remote server could not be fetched or parsed

The full documentation for developers about Any23 can be found here.