HTML sémantique.
Comparer ce que les outils conservent.

Les valeurs doivent être retrouvées à l’identique dans la même ligne. Une légende XML ne vaut pas en-tête de colonne ; un tableau Markdown ne prouve pas la sémantique HTML de l’entrée. Périmètre du test.

<table><caption>Synthetic measurements</caption><thead><tr><th class="case-cell" scope="col">Indicator</th><th class="case-cell" scope="col">Unit</th><th class="case-cell" scope="col">Period</th><th class="case-cell" scope="col">Value</th></tr></thead><tbody><tr><th class="case-cell" scope="row">Response time</th><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table>

…
<table><caption>Synthetic measurements</caption><thead><tr><th scope="col">Indicator</th><th scope="col">Unit</th><th scope="col">Period</th><th scope="col">Value</th></tr></thead><tbody><tr><th scope="row">Response time</th><td>seconds</td><td>May 2026</td><td>1.8</td></tr></tbody></table><p>The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.</p></article></div></div>

{
  "status": "ok",
  "tool_class": "content_extractor",
  "format": "html",
  "table_structure": "present",
  "expected_data_row": "exact_values_in_order",
  "column_header_relation": "explicit",
  "row_header_relation": "explicit",
  "column_labels": [
    "Indicator",
    "Unit",
    "Period",
    "Value"
  ],
  "data_values": [
    "Response time",
    "seconds",
    "May 2026",
    "1.8"
  ],
  "evidence": {
    "header_row": "<th scope=\"col\">Indicator</th><th scope=\"col\">Unit</th><th scope=\"col\">Period</th><th scope=\"col\">Value</th>",
    "data_row": "<th scope=\"row\">Response time</th><td>seconds</td><td>May 2026</td><td>1.8</td>",
    "table_excerpt": "<table><caption>Synthetic measurements</caption><thead><tr><th scope=\"col\">Indicator</th><th scope=\"col\">Unit</th><th scope=\"col\">Period</th><th scope=\"col\">Value</th></tr></thead><tbody><tr><th scope=\"row\">Response time</th><td>seconds</td><td>May 2026</td><td>1.8</td></tr></tbody></table>"
  },
  "output_field": "readability.content",
  "output_sha256": "cc1de29c4ea5d07f4c69e5d5ad58d8d9d148b3bec31053ccf45b3eea11d6ceb8",
  "source_column_headers_explicit": true
}

<div id="readability-page-1" class="page"><div><article><p>This synthetic document compares two markups while text, order, classes and surroundings remain identical. The data are fictional and describe neither Edikka nor a client.</p><h2>Synthetic measurements</h2><table><caption>Synthetic measurements</caption><thead><tr><th scope="col">Indicator</th><th scope="col">Unit</th><th scope="col">Period</th><th scope="col">Value</th></tr></thead><tbody><tr><th scope="row">Response time</th><td>seconds</td><td>May 2026</td><td>1.8</td></tr></tbody></table><p>The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.</p></article></div></div>

{
  "version": "0.6.0",
  "configuration": {
    "keepClasses": false,
    "charThreshold": 500,
    "disableJSONLD": false
  }
}

<table><caption>Synthetic measurements</caption><thead><tr><td class="case-cell">Indicator</td><td class="case-cell">Unit</td><td class="case-cell">Period</td><td class="case-cell">Value</td></tr></thead><tbody><tr><td class="case-cell">Response time</td><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table>

…
<table><caption>Synthetic measurements</caption><thead><tr><td>Indicator</td><td>Unit</td><td>Period</td><td>Value</td></tr></thead><tbody><tr><td>Response time</td><td>seconds</td><td>May 2026</td><td>1.8</td></tr></tbody></table><p>The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.</p></article></div></div>

{
  "status": "ok",
  "tool_class": "content_extractor",
  "format": "html",
  "table_structure": "present",
  "expected_data_row": "exact_values_in_order",
  "column_header_relation": "not_explicit",
  "row_header_relation": "not_explicit",
  "column_labels": [
    "Indicator",
    "Unit",
    "Period",
    "Value"
  ],
  "data_values": [
    "Response time",
    "seconds",
    "May 2026",
    "1.8"
  ],
  "evidence": {
    "header_row": "<td>Indicator</td><td>Unit</td><td>Period</td><td>Value</td>",
    "data_row": "<td>Response time</td><td>seconds</td><td>May 2026</td><td>1.8</td>",
    "table_excerpt": "<table><caption>Synthetic measurements</caption><thead><tr><td>Indicator</td><td>Unit</td><td>Period</td><td>Value</td></tr></thead><tbody><tr><td>Response time</td><td>seconds</td><td>May 2026</td><td>1.8</td></tr></tbody></table>"
  },
  "output_field": "readability.content",
  "output_sha256": "d8405f99038c4ecba3d10c49c8a6d8f423938b614d71a6b754b8d8add9041188",
  "source_column_headers_explicit": false
}

<div id="readability-page-1" class="page"><div><article><p>This synthetic document compares two markups while text, order, classes and surroundings remain identical. The data are fictional and describe neither Edikka nor a client.</p><h2>Synthetic measurements</h2><table><caption>Synthetic measurements</caption><thead><tr><td>Indicator</td><td>Unit</td><td>Period</td><td>Value</td></tr></thead><tbody><tr><td>Response time</td><td>seconds</td><td>May 2026</td><td>1.8</td></tr></tbody></table><p>The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.</p></article></div></div>

{
  "version": "0.6.0",
  "configuration": {
    "keepClasses": false,
    "charThreshold": 500,
    "disableJSONLD": false
  }
}

Texte identique et intervention isolée dans cette paire, selon les témoins du protocole. Les traductions ne sont pas des observations indépendantes. Voir les témoins de la paire.