implementation-report/dev.html at main · kg-construct/implementation-report · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <title>RML Implementation Report</title>
  <script class="remove" src="https://www.w3.org/Tools/respec/respec-w3c" async></script>
  <script class="remove">
    var respecConfig = {
      specStatus: "unofficial",
      shortName: "rml-implementation-report",
      publishDate: "2026-04-21",
      editors: [
        {
          name: "David Chaves-Fraga",
          url: "https://davidchavesfraga.com",
          company: "CiTIUS &ndash; University of Santiago de Compostela",
          orcid: "0000-0003-3236-2789",
          companyURL: "https://citius.gal"
        }
      ],
      github: "https://github.com/kg-construct/implementation-report"
    };
  </script>
  <link rel="stylesheet" href="css/style.css" />
</head>
<body>
<section id="abstract">
  <p>
    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.
  </p>
</section>

<section id="sotd">
  <p>
    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.
  </p>
</section>

<section id="intro">
  <h2>Introduction</h2>
  <p>
    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.
  </p>
</section>

<section id="modules">
  <h2>Modules covered</h2>
  <ul>
    <li><strong><a href="http://w3id.org/rml/core/spec">RML-Core</a></strong>: schema transformations</li>
    <li><strong><a href="http://w3id.org/rml/io/spec">RML-IO</a></strong>: source and target data</li>
    <li><strong><a href="http://w3id.org/rml/fnml/spec">RML-FNML</a></strong>: transformation functions</li>
    <li><strong><a href="http://w3id.org/rml/cc/spec">RML-CC</a></strong>: collections &amp; containers</li>
    <li><strong><a href="http://w3id.org/rml/lv/spec">RML-LV</a></strong>: views over data sources</li>
    <li><strong><a href="http://w3id.org/rml/star/spec">RML-star</a></strong>: test-cases are not provide because the spec needs to adapted for RDF 1.2</li>
  </ul>
</section>

<section id="processors">
  <h2>Processors</h2>
  <div id="processors-table">Loading processors…</div>
</section>

<section id="summary">
  <h2>Coverage summary by engine and module</h2>
  <div id="summary-table">Loading summary…</div>
</section>

<section id="results">
  <h2>Implementation test results</h2>
  <section id="results-rml-core">
    <h3>RML-Core</h3>
    <div data-module-results="RML-Core">Loading results…</div>
  </section>
  <section id="results-rml-io">
    <h3>RML-IO</h3>
    <div data-module-results="RML-IO">Loading results…</div>
  </section>
  <section id="results-rml-fnml">
    <h3>RML-FNML</h3>
    <div data-module-results="RML-FNML">Loading results…</div>
  </section>
  <section id="results-rml-cc">
    <h3>RML-CC</h3>
    <div data-module-results="RML-CC">Loading results…</div>
  </section>
  <section id="results-rml-lv">
    <h3>RML-LV</h3>
    <div data-module-results="RML-LV">Loading results…</div>
  </section>
  <section id="results-rml-star">
    <h3>RML-star</h3>
    <div data-module-results="RML-star">Loading results…</div>
  </section>
</section>

<script src="js/app.js"></script>
</body>
</html>