Article 3 requires that connected products and related services be designed and manufactured in such a way that product data and related service data, including the relevant metadata necessary to interpret and use them, are, by default, easily, securely, free of charge, in a comprehensive, structured, commonly used and machine-readable format, and, where relevant and technically feasible, directly accessible to the user. Article 3(2) sets the pre-contractual information that the seller / rentor / lessor of a connected product must provide to the user about the data the product is capable of generating.
This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.