Vadalingo is the translation layer that converts natural language descriptions, SQL queries, RDF data, and OWL ontologies into executable Vadalog rules. All paths are relative to the base URL and require authentication. All responses use the standard envelope.
Natural language → Vadalog
Translate a free-text description into a Vadalog program. The endpoint automatically loads every concept schema in the project to guide translation. Tag specific concepts with @concept_name in domain_knowledge to restrict context to only those schemas.
Example
If no @ tags are present, all concept schemas in the project are passed as context. Tag specific concepts when you want to constrain the translation or when the project has many concepts and precision matters.
SQL → Vadalog
Translate a SQL query into an equivalent Vadalog program.
Example
RDF → Vadalog
Translate RDF triples into Vadalog rules.
Example
OWL → Vadalog
Translate an OWL ontology into Vadalog rules. Accepts RDF/XML, Turtle, N3, and N-Triples serializations. When data_base_path is provided, Parquet datasets are written under disk/ and @bind annotations are injected into the output program. When add_concepts is true, the resulting program is saved as a new concept named owl_to_vadalog in the project (overwriting any existing concept with that name).
Example
concept_id is null unless add_concepts is true, in which case it contains the ID of the saved or updated concept.