RML Implementation Report

Unofficial Draft

More details about this document
Latest published version:
none
Latest editor's draft:
https://kg-construct.github.io/implementation-report/
History:
Commit history
Editor:
David Chaves-Fraga (CiTIUS – University of Santiago de Compostela)
Feedback:
GitHub kg-construct/implementation-report (pull requests, new issue, open issues)

Abstract

This document reports implementation results for the RML specification family across six modules: RML-Core, RML-IO, RML-FNML, RML-CC, RML-LV, and RML-star. Engine metadata is loaded from this repository, while test-case metadata is pulled from the module repositories and engine results are loaded from one CSV file per engine.

Status of This Document

This document is a draft of a potential specification. It has no official standing of any kind and does not represent the support or consensus of any standards organization.

This is a living implementation report intended to be regenerated automatically from module test-case inventories and per-engine result CSV files, without requiring any server-side component.

1. Introduction

The goal of this report is to provide a lightweight, static, GitHub-friendly implementation report for the RML test suite. The report groups test cases by module and computes implementation coverage automatically in the browser.

2. Modules covered

3. Processors

CSV data could not be loaded automatically.

Failed to fetch

If you open dev.html directly from your disk, the browser may block access to local or remote files.

For local testing, run a static server in this folder, for example:

python3 -m http.server 8000

and then open http://localhost:8000/dev.html.

4. Coverage summary by engine and module

CSV data could not be loaded automatically.

Failed to fetch

If you open dev.html directly from your disk, the browser may block access to local or remote files.

For local testing, run a static server in this folder, for example:

python3 -m http.server 8000

and then open http://localhost:8000/dev.html.

5. Implementation test results

5.1 RML-Core

CSV data could not be loaded automatically.

Failed to fetch

If you open dev.html directly from your disk, the browser may block access to local or remote files.

For local testing, run a static server in this folder, for example:

python3 -m http.server 8000

and then open http://localhost:8000/dev.html.

5.2 RML-IO

CSV data could not be loaded automatically.

Failed to fetch

If you open dev.html directly from your disk, the browser may block access to local or remote files.

For local testing, run a static server in this folder, for example:

python3 -m http.server 8000

and then open http://localhost:8000/dev.html.

5.3 RML-FNML

CSV data could not be loaded automatically.

Failed to fetch

If you open dev.html directly from your disk, the browser may block access to local or remote files.

For local testing, run a static server in this folder, for example:

python3 -m http.server 8000

and then open http://localhost:8000/dev.html.

5.4 RML-CC

CSV data could not be loaded automatically.

Failed to fetch

If you open dev.html directly from your disk, the browser may block access to local or remote files.

For local testing, run a static server in this folder, for example:

python3 -m http.server 8000

and then open http://localhost:8000/dev.html.

5.5 RML-LV

CSV data could not be loaded automatically.

Failed to fetch

If you open dev.html directly from your disk, the browser may block access to local or remote files.

For local testing, run a static server in this folder, for example:

python3 -m http.server 8000

and then open http://localhost:8000/dev.html.

5.6 RML-star

CSV data could not be loaded automatically.

Failed to fetch

If you open dev.html directly from your disk, the browser may block access to local or remote files.

For local testing, run a static server in this folder, for example:

python3 -m http.server 8000

and then open http://localhost:8000/dev.html.