Skip to content
#software testing Dataset Open access

Semantic HTML extraction: controlled FR/EN fixtures, seven tools and revised relation evaluation (v1.2.1)

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

This bilingual French/English dataset archives Semantic HTML extraction protocol v1.2.0, published by Edikka on 20 September 2026. Twelve synthetic HTML fixtures form three controlled families: native headings versus styled generic elements; table header cells with scope versus data cells; and an essential caveat in a paragraph versus an aside. Visible text and surrounding markup are held constant within each pair except for the declared treatment. Language variants are not counted as independent replications. Seven pinned tools run twice on identical input bytes: Mozilla Readability 0.6.0, Trafilatura 2.2.0, readability-lxml 0.8.4.1, newspaper4k 0.9.3.1, jusText 3.0.2, html2text 2025.4.15 and markdownify 1.2.2. Five extraction/readability tools and two Markdown converters are described separately. Expected relationships, fixtures, native outputs, observations, hashes and standalone reproduction code are included. A descriptive addendum archives eight complete Edikka page snapshots captured on 11 September 2026. All eight come from one publisher; this convenience sample is neither representative of the Web nor a causal comparison. A newspaper4k replay instability on one English page is retained. Separate evidence records one scripted keyboard interaction with DOM and accessibility-tree observations before and after JavaScript execution. This is not an autonomous-agent benchmark or a rendered-crawl experiment. The protocol measures preservation, flattening or loss of information and relationships in these inputs. It does not measure accessibility conformance, search indexing, rankings, retrieval, model understanding or citation probability. FR : jeu de données bilingue comprenant douze fixtures contrôlées, sept outils aux versions fixées, huit pages Edikka archivées, les sorties brutes, les résultats défavorables, un scénario d’interaction clavier et le nécessaire de reproduction autonome. Les variantes linguistiques ne constituent pas des réplications indépendantes. Aucun gain SEO ou de citation IA n’est mesuré. Release v1.2.1 preserves extraction protocol 1.2.0 and introduces relation-evaluation revision 2.0.0. It re-examines all twelve archived cases for all seven tools without rerunning the extractors. Column-header and row-header observations are separated; each primary native output is identified by field and SHA-256 and accompanied by an excerpt. The original aggregate counted a caption marked role=head as evidence of explicit table headers. Its four counter-test entries were also fixed declarations, not executed checks. The correction executes four deliberate corruptions in each language, after a valid positive control, against the evaluator of archived Mozilla Readability output. These eight checks validate that evaluator; they are not eight new extractor tests or independent Web observations. Original results and a correction note are preserved with the revised data. Release 1.2.1 is a correction to evaluation and documentation, not a new collection or extractor run. Extraction protocol: 1.2.0; original run: 20 September 2026; revised evaluation: 2.0.0 on 21 September 2026. Earlier public archives retain their original bytes. CC BY 4.0 covers original Edikka-authored material within the scope of the supplied licence; third-party software, notices and components retain their own terms. Conflict of interest: Edikka publishes this protocol while offering web development, SEO and AI visibility services. English is the primary metadata language; fixtures and documentation include French and English. The record does not imply peer review.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.