MediaWiki table to RDF Turtle API

Code examples

These examples send the sample as multipart/form-data and save the returned bytes unchanged. Set TABLECONVERT_API_KEY in your environment.

curl --fail-with-body --max-time 40 \
  'https://api.tableconvert.com/v2/convert/mediawiki-to-rdf' \
  --header "Authorization: Bearer $TABLECONVERT_API_KEY" \
  --form-string 'data={| class="wikitable"
! name !! city !! role
|-
| Alice || London || editor
|-
| Bob || Paris || viewer
|}' \
  --output 'mediawiki-to-rdf.ttl'

import os
from pathlib import Path
import requests

endpoint = "https://api.tableconvert.com/v2/convert/mediawiki-to-rdf"
headers = {"Authorization": "Bearer " + os.environ["TABLECONVERT_API_KEY"]}
fields = {
    "data": (None, "{| class=\"wikitable\"\n! name !! city !! role\n|-\n| Alice || London || editor\n|-\n| Bob || Paris || viewer\n|}"),
}

response = requests.post(endpoint, headers=headers, files=fields, timeout=40)
response.raise_for_status()
Path("mediawiki-to-rdf.ttl").write_bytes(response.content)

import { writeFile } from "node:fs/promises";

const form = new FormData();
form.set("data", "{| class=\"wikitable\"\n! name !! city !! role\n|-\n| Alice || London || editor\n|-\n| Bob || Paris || viewer\n|}");

const response = await fetch("https://api.tableconvert.com/v2/convert/mediawiki-to-rdf", {
  method: "POST",
  headers: { Authorization: "Bearer " + process.env.TABLECONVERT_API_KEY },
  body: form,
  signal: AbortSignal.timeout(40_000),
});
if (!response.ok) {
  throw new Error("HTTP " + response.status + ": " + await response.text());
}
await writeFile("mediawiki-to-rdf.ttl", Buffer.from(await response.arrayBuffer()));

Request parameters

MediaWiki table cell syntax is reduced to plain rows for conversion. Wiki page expansion and template execution are outside this importer.

Send one source: data, file, or url. The examples below use the source mode appropriate for this format.

Output options

Generate Turtle-style RDF triples with an example namespace, record subjects and header predicates. This is not RDF/XML and does not infer an ontology.

This output format does not expose additional options.

Conversion rules

How the input is read

• Supply a {| … |} table with clear cell and row boundaries.
• Simplify table attributes and merged cells before conversion; wiki layout metadata is not a portable data model.
• Wiki links, templates and inline markup are not expanded into rendered page content.
• Confirm the extracted header and cell text before creating named records or code.

How the output is written

• Each row creates a numbered record subject and each header supplies a predicate.
• Replace the example.org namespace and record identifiers with your real vocabulary and identity policy.
• Validate Turtle names and escaped string literals before loading a triple store.

When to use this API

Responses and errors

Check the response before retrying. A new HTTP request is a new conversion and may use credits again.

Limits, billing and versions

Local previews accept up to 200 KB. The current API implementation allows one uploaded file up to 50 MiB, limits each multipart text field to 1 MiB, and gives v2 conversion tasks a 30-second deadline. Deployment limits may be stricter. Read the returned error before retrying; some parser or renderer failures return HTTP 500.

Live calls follow the API credit policy. Failed conversions are refunded; a completed conversion is not undone if the download connection later fails.

References and format specifications

Format references explain the underlying syntax. The conversion rules and samples above describe TableConvert’s implementation.

• www.mediawiki.org
• www.w3.org