Web Interface (HTTP Matching Interface)

In this section, the REST API interface for a matcher is described. It is used for matchers running on servers and not locally. When using a docker based matcher, the communication interface is exactly the same.

There are two possible content types (below: drop-down menu for “Request body”): (1) An URL encoded form and (2) multipart upload. For the first option, URLs are provided pointing to the data files. In this case, the matching server will access the URL and download the data. For the second option, the files are directly contained in the HTTP POST request.

source and target are plain RDF files (RDF/XML, Turtle, N3).

inputAlignment is an alignment in the alignment format.

parameters are used to provide task-specific information (for example “match only classes”). Some keys are already defined by MELT. The parameters can be transferred as JSON (preferred) or YAML.

The system directly returns the resulting alignment in the alignment format.

See also a more complete documentation in MELT Web packaging.

Swagger documentation of the Web API

The swagger documentation is displayed below / [open full screen documentation in a new tab]