Pith. sign in

REVIEW 4 major objections 5 minor 17 references

Enhancing Systematic Interoperability: Convergences and Mismatches between Web 3.0 and the EU Data Act

T0 review · 4 major / 5 minor · reviewed 2026-08-05 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗

Pith's one-line read EU Data Act's interoperability stops at data while Web 3.0 spans systems and applications, the paper argues, and this gap could fragment the digital ecosystem.

desk verdict Plausible but under-demonstrated: the paper's core claim that the Data Act covers only data interoperability is asserted, not shown, despite the Act's own broader definition. read the letter →

arxiv 2508.07356 v1 pith:LKZFAKCL submitted 2025-08-10 cs.CY cs.ET

Linyi Xu , Zihao Li This is my paper · ORCID
classification cs.CYcs.ET
keywords interoperabilityWeb3.0EUDataActlegalcomplianceblockchaindecentralizedapplicationsstandardisedprotocolsregulation
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

This paper compares the technical interoperability built into Web 3.0 with the legal interoperability framework of the EU Data Act, asking whether the Data Act can support the kind of cross-platform integration Web 3.0 is designed to achieve. It argues that the Data Act operationally regulates only data-level interoperability, while Web 3.0 interoperability operates at data, system, and application layers. The mismatch means data can legally flow between platforms, but full system and application integration is neither recognized nor enabled by law, and in some cases legal compliance could actively limit it. The authors conclude that the Data Act should broaden its concept of interoperability to cover systems and applications, and should use soft-law mechanisms like negative lists to make standardised protocols legally actionable.

What carries the argument

The three-layer interoperability concept (data, system, application) is the analytic lens, mapped against the Data Act's provisions. The argument works by taking Web 3.0's technical stack—ERC token standards, cross-chain protocols, decentralised identity, DApps—and checking each layer against the Data Act's definitional articles, its chapter-wide interoperability provisions, and recitals 76-86. The mapping carries the conclusion that the Data Act recognises the data layer but neither regulates nor protects the system and application layers, which is the source of the mismatch.

What would settle it

A systematic article-by-article reading of the final Data Act text: if Articles 23-30 (especially the portability of applications and virtual machines under Article 26, and the smart-contract requirements of Article 30) already impose legally binding system- and application-level interoperability obligations, then the paper's central claim that the Data Act is data-only in its operational provisions would be falsified.

Watch

Extended reading notes

Core claim

On its own terms, the paper establishes that the Data Act's binding provisions—Articles 2(40)-(41) on definitions, Chapter 8 on interoperability, Articles 28-30 on data processing services and smart contracts—are oriented toward data exchange and portability, whereas Web 3.0's technical interoperability spans data, systems, and applications through mechanisms such as ERC standards, cross-chain bridges (Polkadot, Cosmos), and decentralised identity. The paper classifies Web 3.0 interoperability into three categories relative to law: aspects already recognised (standardised protocols supporting data circulation, decentralised identity aligning with data-ownership goals), aspects that may confl

Load-bearing premise

The entire mismatch argument rests on the interpretive premise that the Data Act's binding provisions cover only data-level interoperability, notwithstanding the Act's own statutory definition that explicitly includes systems, applications, and components; the paper asserts this premise without a detailed article-by-article demonstration.

Editorial extensions

If this is right

  • Cross-chain and DApp-integration projects face legal uncertainty under the Data Act, since none of its binding provisions address system or application-level interoperability.
  • The Data Act's stated goal of seamless data flow is only partially achievable: data travel is regulated, but the integrations that make data usable across platforms are not.
  • Broadening the Data Act to cover system and application interoperability would create new compliance questions, such as whether cross-chain bridges or DApp-to-DApp protocols become legally accountable for interoperability failures.
  • Using negative lists and soft-law standardisation could make protocol standards legally meaningful without freezing them into rigid technical mandates.
  • Aligning the Data Act's concept with Web 3.0's layered interoperability would also affect neighbouring legislation, since GDPR and the Interoperable Europe Act share the same data-centric emphasis.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • The same data-versus-systems comparison could be applied to sectoral Web 3.0 cases—finance, identity, supply chain—to test whether the mismatch is more severe in heavily regulated domains; the paper gestures at finance but does not carry this through.
  • A testable extension would code every article of the final Data Act for whether it imposes obligations on systems, applications, or only data; the paper asserts but does not perform such a systematic coding.
  • The paper implies, without stating, that Web 3.0's interoperability is itself layered—blockchain, protocol, and application—and that the Data Act's gap may be most acute at the application layer, which is the layer where DApps and cross-chain user interactions actually occur.
Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

4 major / 5 minor

Summary. The paper offers an interdisciplinary comparison between the technical interoperability of Web 3.0 and the legal interoperability framework of the EU Data Act (DA). It argues that Web 3.0 interoperability spans data, systems, and applications, while the DA focuses solely on data interoperability, creating a mismatch that risks ecosystem fragmentation. The paper recommends broadening the DA's concept of interoperability to include system and application layers and introducing soft-law mechanisms such as negative lists for standardized protocols. The analysis is qualitative, drawing on selected DA provisions and illustrative Web 3.0 examples, and concludes with policy-oriented recommendations.

Significance. If the central mismatch claim were well supported, this would be a timely and useful contribution to an active policy discussion on interoperability in the EU digital single market and the Web 3.0 ecosystem. The paper correctly identifies that technical interoperability standards (e.g., cross-chain protocols, ERC standards) and legal interoperability obligations may not be aligned, and it proposes concrete, if preliminary, legal design suggestions. The paper does not provide machine-checked proofs or quantitative analysis, but its contribution lies in framing the interdisciplinary question and offering comparative observations. The main significance is contingent on substantiating the claim that the DA's binding provisions are limited to data-level interoperability, which currently rests on an unsupported interpretive premise.

major comments (4)
  1. [Section I (quoted Art. 2(40) definition)] The paper quotes the DA's definition of interoperability as 'the ability of two or more data spaces or communication networks, systems, connected products, applications, data processing services or components to exchange and use data' and then asserts that 'since DA directly addresses only data interoperability.' These two statements are in direct tension. The quoted definition explicitly includes systems and applications as subjects of the exchange/use capability. The paper never reconciles this tension or demonstrates through an article-by-article analysis of the final Data Act text that the binding obligations stop at the data layer. This is the load-bearing premise for the paper's central mismatch argument and must be fixed.
  2. [Section IV.A] The paper claims that 'the regulations concerning system and application interoperability are broad and primarily found in the recitals, lacking the legal enforceability and practical applicability needed for effective interoperability.' This is contradicted by the paper's own survey in the same section: it cites Chapter VI on data processing services, Articles 23–26 on switching, Article 28–29 on interoperability requirements, and Article 30 on smart contracts. These are binding main-text provisions, not recitals. The paper needs to explain why these provisions do not constitute system/application interoperability obligations. Without that demonstration, the central mismatch is overstated. The recital claim is a factual legal assertion requiring specific evidence.
  3. [Section III.B] The examples used to illustrate conflicts between Web 3.0 interoperability and legal requirements are not about interoperability as defined by the DA. The DEX/KYC example concerns financial regulation and anti-money laundering, not data interoperability. The DeFi/social-media example is about privacy protection, not about system/application interoperability. These examples may support a broader claim about technology complying with sectoral law, but they do not support the section's title: 'Aspects of Web 3.0 Technical Interoperability That May Conflict with Legal Requirements.' The paper should either find examples where the technical interoperability mechanism itself (e.g., cross-chain bridges or DApp integration) collides with DA provisions, or retitle the section to reflect the actual scope.
  4. [Section VI.B] The recommendation to introduce a 'negative list' for standardized protocols is asserted rather than argued. The paper repeats the same paragraph nearly verbatim (the duplicated text about negative lists appears twice in this section), which suggests drafting oversight. More importantly, the proposal relies on citation [14], a self-citation by one of the authors, without explaining how such a negative list would interact with the DA's existing standardization mechanisms, such as Article 29 (essential requirements) and Article 33 (essential requirements for data interoperability). To be persuasive, this recommendation should be tied to the DA's enforcement structure and discuss how a negative list would be monitored and updated.
minor comments (5)
  1. [Abstract] Capitalization is inconsistent: 'Firstly, Web 3.0’s concept...' and 'Secondly' appear capitalized mid-sentence. Also, the abstract uses 'Web3.0' without a space in some places, while the main text uses 'Web 3.0'.
  2. [Section VI.B] The paragraph beginning 'Secondly, the DA addresses the establishment of standardised protocols only within the recitals...' is a near-duplicate of the preceding paragraph about negative lists. One of them should be removed.
  3. [Section II.A] The statement that 'GDPR ... implicitly supports data sharing and flow' is an overgeneralization. GDPR's data portability right is narrower than interoperability; the paper should phrase this more carefully to avoid conflating data portability with data sharing.
  4. [References] The article numbering in the paper appears to be based on an earlier version of the Data Act; the final adopted Regulation (EU) 2023/2854 may have different article numbers. The authors should verify and cite the final text throughout, especially when discussing Articles 23-30.
  5. [Section VI.A] The claimed advantages of system-level interoperability are normative and not grounded in the technical literature cited in the paper. Consider adding concrete technical references or toning down the language to avoid unsupported advocacy.

Circularity Check

0 steps flagged · score 1.0 of 10

No significant circularity: the central comparison is an interpretive legal-technical analysis based on external sources; the only self-citation is peripheral and non-load-bearing.

full rationale

The paper's central claim that the Data Act focuses on data interoperability while Web 3.0 encompasses system and application interoperability is an interpretive legal argument grounded in the DA's text and recitals. The paper quotes Article 2(40) defining interoperability as the ability of systems, applications, components, etc. to exchange and use data, but then argues from the structure of the DA that its operative interoperability provisions are data-centric. This is a contestable legal interpretation, not a conclusion that is equivalent to its premise by construction. No fitted parameters are renamed as predictions, no definition is self-referential, and no result is imported solely from the authors' prior work. The only self-citation, reference [14], supports a peripheral recommendation about negative lists and is not load-bearing for the convergence/mismatch analysis. The derivation chain is self-contained against external legal and technical sources. Any weakness lies in the completeness of the article-by-article analysis, which is a correctness risk, not circularity. Score 1 reflects the presence of one minor self-citation with no load-bearing effect.

Assumptions & free parameters 0 free parameters · 4 assumptions · 0 invented entities

The paper does not introduce mathematical parameters or invented entities. It relies on interpretive premises about the Data Act's scope, Web 3.0's technical layers, and the effectiveness of soft law tools.

assumptions (4)
  • domain assumption The DA's legal concept of interoperability is effectively limited to data interoperability, despite its broad statutory definition.
    The paper asserts this in the abstract and throughout, but does not reconcile it with the DA definition quoted in Section I that includes systems and applications. This interpretive premise is load-bearing.
  • domain assumption Web 3.0 interoperability spans data, systems, and applications levels.
    Assumed from selected examples (Polkadot, Cosmos, ERC standards) without a systematic survey of the Web 3.0 interoperability landscape.
  • domain assumption Soft law mechanisms such as negative lists can effectively fill legal gaps in the Data Act.
    Normative recommendation in Section VI.B, not demonstrated empirically or through legal analysis.
  • domain assumption The Data Act's recitals lack legal force and therefore cannot support standardization obligations.
    Standard legal principle, but the paper's conclusion that this is a deficiency depends on this assumption.

how reviews work

0 comments
Cite this review

Pith. "Pith review of Enhancing Systematic Interoperability: Convergences and Mismatches between Web 3.0 and the EU Data Act." pith.science (2026). https://pith.science/paper/LKZFAKCL

@misc{pith2026250807356,
  author       = {Pith},
  title        = {Pith review of: Enhancing Systematic Interoperability: Convergences and Mismatches between Web 3.0 and the EU Data Act},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/LKZFAKCL}},
  note         = {Machine review of arXiv:2508.07356}
}
read the original abstract

Interoperability is increasingly recognised as a foundational principle for fostering innovation, competition, and user autonomy in the evolving digital ecosystem. Existing research on interoperability predominantly focuses either on technological interoperability itself or on the legal regulations concerning interoperability, with insufficient exploration of their interdisciplinary intersection. This paper compares the technological interoperability in Web 3.0 with the theoretical framework of legal interoperability established by the EU Data Act, analysing the areas of convergence and mismatch. The goal is to align technical interoperability with legal concepts of interoperability, thereby enhancing the practical implementation of systematic interoperability in the next generation of the Web. This study finds that, firstly, Web 3.0's concept of interoperability spans data, systems, and applications, while the Data Act focuses solely on data. This narrow scope risks creating a fragmented ecosystem, where data exchange is possible, but full integration of systems and applications is hindered, leading to inefficiencies, and obstructing seamless data flow across platforms. Secondly, while Web 3.0 technically seeks to achieve interoperability through the integration of entire systems and decentralised applications, the compliance with Data Act might negatively limit such system and application interoperability through its data interoperability provisions. This paper suggests interdisciplinary recommendations to enhance the implementation and enforcement of interoperability. On one hand, the Data Act should broaden its concept of interoperability to encompass both the systems and applications layers. On the other hand, it is advisable to introduce provisions for standardised protocols through soft law mechanisms to address legal shortcomings and keep pace with technological advancements.

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

17 extracted references · 15 canonical work pages

  1. [13]

    Schnurr, ‘Switching and Interoperability Between Data Processing Services in the Proposed Data Act’, Switch

    D. Schnurr, ‘Switching and Interoperability Between Data Processing Services in the Proposed Data Act’, Switch. Interoperability Data Process. Serv. Propos. Data Act, 2022, Accessed: Jul. 25, 2024. [Online]. Available: https://cerre.eu/wp- content/uploads/2022/12/Data_Act_Cloud_Switching.pdf

    work page 2022

  2. [14]

    Z. Li, ‘Standardisation of Blockchain and Distributed Ledger Technologies—A Legal Voice from the Data Protection Law Perspective’, in 25th EURAS Annual Standardisation Conference–Standards for Digital Transformation: Blockchain and Innovation (The European Academy for Standardisation), 2020. Accessed: Aug. 08,

    work page 2020

  3. [1]

    C. Guan, D. Ding, J. Guo, and Y. Teng, ‘An ecosystem approach to Web3.0: a systematic review and research agenda’, J. Electron. Bus. Digit. Econ., vol. 2, no. 1, pp. 139–156, Jul. 2023, doi: 10.1108/JEBDE-10-2022-0039

    work page doi:10.1108/jebde-10-2022-0039 2023

  4. [2]

    H. Xu, Y. Sun, Z. Li, Y. Sun, L. Zhang, and X. Zhang, ‘deController: A Web3 Native Cyberspace Infrastructure Perspective’, IEEE Commun. Mag., vol. 61, no. 8, pp. 68–74, Aug. 2023, doi: 10.1109/MCOM.005.2200481

    work page doi:10.1109/mcom.005.2200481 2023

  5. [3]

    Z. Li, H. Xu, Y. Fang, B. Zhao, and L. Zhang, ‘Recordism: A social-scientific prospect of blockchain from social, legal, financial, and technological perspectives’, May 06, 2023, arXiv: arXiv:2204.00823. Accessed: Aug. 28, 2024. [Online]. Available: http://arxiv.org/abs/2204.00823

    work page Pith review arXiv 2023

  6. [4]

    Brown, ‘Interoperability as a tool for competition regulation’, 2020, Accessed: Jul

    I. Brown, ‘Interoperability as a tool for competition regulation’, 2020, Accessed: Jul. 25, 2024. [Online]. Available: https://osf.io/preprints/lawarxiv/fbvxd/

    work page 2020

  7. [5]

    da Silva Serapião Leal, W

    G. da Silva Serapião Leal, W. Guédria, and H. Panetto, ‘Interoperability assessment: A systematic literature review’, Comput. Ind., vol. 106, pp. 111–132, Apr. 2019, doi: 10.1016/j.compind.2019.01.002

    work page doi:10.1016/j.compind.2019.01.002 2019

  8. [6]

    Delgado, ‘Interoperability Effect in Big Data’, in Handbook of Smart Cities, J

    J. Delgado, ‘Interoperability Effect in Big Data’, in Handbook of Smart Cities, J. C. Augusto, Ed., Cham: Springer International Publishing, 2020, pp. 1–28. doi: 10.1007/978-3-030-15145-4_48-1

    work page doi:10.1007/978-3-030-15145-4_48-1 2020

Show all 17 references
  1. [7]

    I. Kang, A. Gupta, and O. Seneviratne, ‘Blockchain interoperability landscape’, in 2022 IEEE International Conference on Big Data (Big Data), IEEE, 2022, pp. 3191–

    2022

  2. [8]

    Burdges et al., ‘Overview of Polkadot and its Design Considerations’, May 29, 2020, arXiv: arXiv:2005.13456

    J. Burdges et al., ‘Overview of Polkadot and its Design Considerations’, May 29, 2020, arXiv: arXiv:2005.13456. Accessed: Aug. 14, 2024. [Online]. Available: http://arxiv.org/abs/2005.13456

    2020 arXiv

  3. [9]

    Kwon and E

    J. Kwon and E. Buchman, ‘Cosmos whitepaper’, Netw Distrib Ledgers, vol. 27, pp. 1–32, 2019

    2019

  4. [10]

    Norvill, B

    R. Norvill, B. Fiz, R. State, and A. Cullen, ‘Standardising smart contracts: Automatically inferring ERC standards’, in 2019 IEEE International Conference on Blockchain and Cryptocurrency (ICBC), IEEE, 2019, pp. 192–195. Accessed: Aug. 28, 2024. [Online]. Available: https://ie...

    2019

  5. [11]

    J. Xu, K. Paruch, S. Cousaert, and Y. Feng, ‘SoK: Decentralized Exchanges (DEX) with Automated Market Maker (AMM) Protocols’, ACM Comput. Surv., vol. 55, no. 11, pp. 1–50, Nov. 2023, doi: 10.1145/3570639

    2023 doi

  6. [12]

    Zuo, ‘Development, Application, And Regulation of Web3

    Z. Zuo, ‘Development, Application, And Regulation of Web3. 0’, Front. Bus. Econ. Manag., vol. 9, no. 3, pp. 22– 27, 2023

    2023

  7. [15]

    Zheng and D

    J. Zheng and D. K. C. Lee, ‘Understanding the Evolution of the Internet: Web1. 0 to Web3. 0, Web3 and Web 3 plus’, Handb. Digit. Curr. Bitcoin Innov. Financ. Instrum. Big Data Second Ed. 2023, 2023, Accessed: Aug. 13, 2024. [Online]. Available: https://papers.ssrn.com/sol3/pap...

    2023

  8. [2024]

    Available: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=389229 8

    [Online]. Available: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=389229 8

  9. [3200]

    04, 2024

    Accessed: Jul. 04, 2024. [Online]. Available: https://ieeexplore.ieee.org/abstract/document/10020412/

    2024

Pith tools

Reviewed August 5, 2026 · model on record in the stance chip above.