--- title: "EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/items/page/15" author: "Sorena AI" description: "Grounded EU Data Act FAQ index covering connected-product data access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, trade secrets, and application dates." published_at: "2026-05-06" updated_at: "2026-05-25" keywords: - "EU Data Act FAQ" - "Data Act scope" - "connected product data" - "B2G data sharing" - "cloud switching" - "GDPR Data Act" - "EU Data Act" - "Data Act FAQ" - "Regulation (EU) 2023/2854" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates Grounded EU Data Act FAQ index covering connected-product data access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, trade secrets, and application dates. *FAQ* *EU* *Data Act* ## EU Data Act FAQ hub Answers to the recurring EU Data Act questions that decide whether connected-product data, related-service data, B2G requests, cloud contracts, or smart-contract tooling need a compliance review. Use this index to orient product, legal, cloud, procurement, data protection, security, and public-sector request teams before opening the deeper topic modules. The EU Data Act, Regulation (EU) 2023/2854, creates horizontal rules for fair access to and use of data. Its FAQ set is not only about IoT data portability: it also covers mandatory B2B sharing terms, unfair contractual terms, public-sector access in exceptional need, cloud and edge switching, safeguards against unlawful third-country government access to non-personal data, interoperability, smart contracts, enforcement, and the boundary with GDPR. ## Browse sub-FAQ modules ### [Data Act and Data Governance Act Overlap FAQ](/artifacts/eu/data-act/faq/data-governance-act-overlap.md) FAQ explaining where the EU Data Act and Data Governance Act overlap, how they differ, and how to route product, cloud, public-sector reuse, intermediary, and data altruism workflows. - 12 items ### [Data Act and GDPR Personal Data Overlap FAQ](/artifacts/eu/data-act/faq/gdpr-personal-data-overlap.md) FAQ on how the EU Data Act works when connected-product or related-service data includes personal data, mixed datasets, GDPR roles, lawful basis, trade secrets, and third-party sharing. - 12 items ### [Data Act Audit Evidence And Request Logs FAQ](/artifacts/eu/data-act/faq/audit-evidence-and-request-logs.md) FAQ for Data Act request logs covering user and third-party access, B2G exceptional need requests, cloud switching records, contract terms, trade secrets, and GDPR boundaries. - 12 items ### [Data Act Cloud Switching Contract Terms FAQ](/artifacts/eu/data-act/faq/cloud-switching-contract-terms.md) FAQ on EU Data Act cloud switching contract terms: Article 25 clauses, assistance, notice, transition, charges, export, termination, interoperability, and records. - 12 items ### [Data Act Cloud Switching Fees And Deadlines FAQ](/artifacts/eu/data-act/faq/cloud-switching-fees-and-deadlines.md) FAQ on EU Data Act cloud switching charges, 2027 fee removal, notice periods, transition windows, data retrieval, contract terms, and evidence records. - 12 items ### [Data Act Complaints and Dispute Settlement FAQ](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md) FAQ on EU Data Act complaints, competent authorities, dispute settlement bodies, B2B data-sharing disputes, B2G requests, cloud switching disputes, and evidence records. - 12 items ### [Data Act Exportable Data and Metadata FAQ](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md) FAQ explaining which product, related service, metadata, and cloud switching data must be exportable under the EU Data Act, and which data can be excluded. - 12 items ### [Data Act FAQ for Aftermarket Repair and Mobility Services](/artifacts/eu/data-act/faq/aftermarket-repair-and-mobility-services.md) FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services. - 12 items ### [Data Act Functional Equivalence FAQ](/artifacts/eu/data-act/faq/functional-equivalence.md) FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence. - 12 items ### [Data Act Indirect Access Request Flows FAQ](/artifacts/eu/data-act/faq/indirect-access-request-flows.md) FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited. - 12 items ### [Data Act International Government Access FAQ](/artifacts/eu/data-act/faq/international-government-access.md) FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers. - 12 items ### [Data Act Interoperability Standards FAQ](/artifacts/eu/data-act/faq/interoperability-standards.md) FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614. - 12 items ### [Data Act Model Contractual Terms FAQ](/artifacts/eu/data-act/faq/model-contractual-terms.md) FAQ on the EU Data Act non-binding model contractual terms for data access and use, cloud switching clauses, B2B use, unfair terms, and evidence. - 12 items ### [Data Act Public Emergency Requests FAQ](/artifacts/eu/data-act/faq/public-emergency-requests.md) FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records. - 12 items ### [Data Act SME Exceptions and Startups FAQ](/artifacts/eu/data-act/faq/sme-exceptions-and-startups.md) FAQ on where the EU Data Act gives micro, small, medium-sized, startup, and SME actors narrower treatment for access duties, compensation, and B2B terms. - 12 items ### [Data Act Trade Secret Technical Protection Measures FAQ](/artifacts/eu/data-act/faq/trade-secret-technical-protection-measures.md) FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence. - 12 items ### [EU Data Act and Common European Data Spaces FAQ](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md) FAQ on how EU Data Act interoperability duties, Data Governance Act rules, and sector data-space governance fit together without treating participation as a general obligation. - 12 items ### [EU Data Act Application Dates And Transition FAQ](/artifacts/eu/data-act/faq/application-dates-and-transition.md) FAQ on when the EU Data Act applies, which obligations are delayed, and what product, contract, cloud, and evidence records teams should maintain. - 12 items ### [EU Data Act Article 36 Smart Contract Controls FAQ](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md) FAQ explaining when EU Data Act Article 36 applies to smart contracts for data-sharing agreements and what controls, conformity evidence, and limits it requires. - 12 items ### [EU Data Act B2B Data Sharing Compensation FAQ](/artifacts/eu/data-act/faq/compensation-for-b2b-data-sharing.md) FAQ on when Data Act data holders may charge B2B data recipients, what reasonable compensation can include, SME limits, unfair terms, disputes, and trade secret safeguards. - 12 items ### [EU Data Act B2G Compensation and Costs FAQ](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md) FAQ on when Data Act B2G exceptional-need requests are free, when fair compensation may be claimed, which costs can be included, and what records to keep. - 12 items ### [EU Data Act B2G Exceptional Need FAQ](/artifacts/eu/data-act/faq/b2g-exceptional-need.md) When public-sector bodies can request business-held data under the EU Data Act, what a valid request must contain, and how data holders handle limits, trade secrets, compensation, and evidence. - 13 items ### [EU Data Act Cloud Switching Procurement FAQ](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md) Procurement checklist FAQ for EU Data Act cloud switching: contract terms, exit support, exportable data, switching charges, interoperability, termination, and supplier evidence. - 12 items ### [EU Data Act Connected Product Scope FAQ](/artifacts/eu/data-act/faq/scope-connected-products.md) FAQ explaining when connected products, related services, generated data, EU market placement, and SME exceptions fall within EU Data Act scope. - 12 items ### [EU Data Act data spaces interoperability FAQ](/artifacts/eu/data-act/faq/data-spaces-interoperability.md) FAQ explaining Article 33 Data Act interoperability requirements for data-space participants, common European data spaces, standards, APIs, metadata, and architecture evidence. - 12 items ### [EU Data Act Direct Access by Design FAQ](/artifacts/eu/data-act/faq/direct-access-by-design.md) FAQ for product and legal teams designing user access to connected-product and related-service data under the EU Data Act. - 12 items ### [EU Data Act Enforcement And Competent Authorities FAQ](/artifacts/eu/data-act/faq/enforcement-and-competent-authorities.md) FAQ on who enforces the EU Data Act, how complaints work, how Member States set penalties, when dispute settlement can be used, and when GDPR authorities remain responsible. - 12 items ### [EU Data Act Non-Emergency Public-Sector Requests FAQ](/artifacts/eu/data-act/faq/non-emergency-public-sector-requests.md) FAQ on EU Data Act requests where a public body claims exceptional need outside a public emergency, including scope, request contents, limits, compensation, confidentiality, and evidence. - 12 items ### [EU Data Act Non-Personal Data and Mixed Datasets FAQ](/artifacts/eu/data-act/faq/non-personal-data-and-mixed-datasets.md) FAQ on how the EU Data Act treats non-personal data, mixed datasets, GDPR precedence, user and third-party access, trade-secret limits, and evidence records. - 12 items ### [EU Data Act Pre-Contractual Information FAQ](/artifacts/eu/data-act/faq/pre-contractual-information.md) FAQ on EU Data Act Article 3 pre-contract information for connected products and related services, including data categories, access methods, data holder identity, third-party sharing, and GDPR boundaries. - 12 items ### [EU Data Act Product Data vs Related Service Data FAQ](/artifacts/eu/data-act/faq/product-data-and-service-data.md) FAQ explaining how the EU Data Act separates connected product data, related service data, readily available raw and pre-processed data, metadata, and inferred or derived outputs. - 12 items ### [EU Data Act Readily Available Data FAQ](/artifacts/eu/data-act/faq/readily-available-data.md) FAQ on what counts as readily available data under the EU Data Act, including product data, related service data, metadata, inferred data, and access mechanics. - 12 items ### [EU Data Act Related Services FAQ](/artifacts/eu/data-act/faq/related-services.md) FAQ explaining when software is a Data Act related service, how it links to connected products, which product and service data are in scope, and what exclusions apply. - 12 items ### [EU Data Act Smart Contracts for Data Sharing FAQ](/artifacts/eu/data-act/faq/smart-contracts-for-data-sharing.md) Answers on Article 36 Data Act smart-contract requirements for data sharing: scope, robustness, access control, termination, archiving, conformity assessment, contract terms, and standards status. - 12 items ### [EU Data Act Third-Party Data Sharing FAQ](/artifacts/eu/data-act/faq/third-party-data-sharing.md) FAQ on user-directed third-party data sharing under the EU Data Act, covering data holder duties, recipient limits, trade secrets, security, GDPR, and gatekeepers. - 12 items ### [EU Data Act Trade Secret Safeguards FAQ](/artifacts/eu/data-act/faq/trade-secrets-safeguards.md) FAQ on protecting trade secrets when handling EU Data Act user and third-party data access requests, including safeguards, withholding, suspension, refusal, notices, and records. - 12 items ### [EU Data Act Unfair Contractual Terms FAQ](/artifacts/eu/data-act/faq/unfair-contractual-terms.md) FAQ on Article 13 of the EU Data Act: B2B unfair contract terms, unilateral take-it-or-leave-it clauses, always-unfair terms, presumed-unfair terms, SMEs, model terms, and review evidence. - 12 items ### [EU Data Act Users, Data Holders, and Recipients FAQ](/artifacts/eu/data-act/faq/users-data-holders-and-recipients.md) FAQ explaining Data Act users, data holders, data recipients, connected products, related services, user access, third-party limits, and GDPR boundaries. - 12 items ### [EU Data Act Vehicle Data Guidance FAQ](/artifacts/eu/data-act/faq/vehicle-data-guidance.md) FAQ on EU Data Act vehicle data guidance for connected vehicles, aftermarket repair, mobility services, third-party access, trade secrets, security, and GDPR boundaries. - 12 items Browse all indexed questions: [/artifacts/eu/data-act/faq/items](/artifacts/eu/data-act/faq/items.md) ## All FAQ items *Page 15 of 24. Showing 20 of 469 items.* ### [What is a related service, and when does an app count under the Data Act?](/artifacts/eu/data-act/faq/scope-connected-products.md#what-is-a-related-service-and-when-does-an-app-count-under-the-data-act) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Under the Data Act, a related service is a digital service, other than an electronic communications service, that is connected with the product at purchase, rent, or lease so that the product would lose one or more functions without it, or that is later connected to add, update, or adapt product functions. Software can be a related service when it is linked to product operation. - Look for commands, settings, updates, or data flows that affect how the product behaves. - Review user expectations, marketing, contract terms, replaceability, and whether the service is pre-installed or bundled. - Separate related services from ordinary connectivity, electricity, analytics, consulting, finance, repair, and maintenance services. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 2(6) defines related service; Recital 17 distinguishes related services from connectivity, power supply, consulting, analytics, finance, repair, and maintenance. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Question 10 gives the bidirectional-data and product-function tests for related services. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer gives a washing-machine app example of a related service that uses sensor data and adjusts a cycle. ### [Which generated data is inside connected-product scope under the Data Act?](/artifacts/eu/data-act/faq/scope-connected-products.md#which-generated-data-is-inside-connected-product-scope-under-the-data-act) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Under the Data Act, Chapter II focuses on product data and related service data that is readily available to the data holder. Product data is data generated by use of the connected product and designed to be retrievable. Related service data is data representing user actions or events related to the product during the related service. - Include data about use, performance, status, environment, user action, inaction, and product-related events when it is readily available. - Include relevant metadata such as basic context and timestamps where needed to make the data usable. - Treat personal and non-personal data separately for privacy compliance, but do not exclude data from Data Act scope just because it may include personal data. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 2(15)-(17), Recital 15, Article 3, and Article 4 define product data, related service data, readily available data, metadata, and access duties. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 4, 5, and 5a explain raw data, pre-processed data, metadata, readily available data, and edge-processing scenarios. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer states that Chapter II applies to raw and pre-processed data generated from use of connected products or related services that is readily available to the data holder. ### [What data and products are outside this connected-product scope under the Data Act?](/artifacts/eu/data-act/faq/scope-connected-products.md#what-data-and-products-are-outside-this-connected-product-scope-under-the-data-act) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Under the Data Act, several exclusions matter. Prototypes are outside scope because their manufacturing stage has not been completed. Data that is inferred or derived from product data through additional investment, including proprietary complex algorithms, is not treated as data that must be made available under Chapter II unless the parties agree otherwise. - Exclude prototypes, unless a specific contractual arrangement permits use of data from testing products or processes not yet placed on the market. - Separate raw and pre-processed data from inferred or derived insights produced by proprietary or complex analytics. - Do not convert third-party infrastructure data, audiovisual content, or unrelated software content into product data merely because the connected product interacts with it. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Recitals 14-16 and Article 5(2) support the prototype, inferred-or-derived-data, content, and testing exclusions. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 5, 6, and 7 explain derived data, content, infrastructure data, and prototypes. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer gives the smart-TV film example and distinguishes content from product-generated data. ### [How do micro, small, and newer medium-sized manufacturers affect scope under the Data Act?](/artifacts/eu/data-act/faq/scope-connected-products.md#how-do-micro-small-and-newer-medium-sized-manufacturers-affect-scope-under-the-data-act) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Article 7 of the Data Act creates an important Chapter II limitation. The Chapter II obligations do not apply to data generated through connected products manufactured or designed, or related services provided, by a microenterprise or small enterprise, if the linked-enterprise and subcontracting conditions in Article 7 are satisfied. - Verify the actual manufacturer, designer, related-service provider, linked enterprises, and subcontracting position. - For medium-sized enterprises, record when the enterprise first qualified as medium-sized and when the individual connected product was placed on the market. - Do not use SME context to remove GDPR, contract, product-safety, or other non-Data-Act obligations. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 7 sets Chapter II scope limitations for microenterprises, small enterprises, and newer medium-sized enterprises. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer confirms that micro and small companies as manufacturers or related-service providers are not subject to the same Chapter II obligations as larger companies. ### [What access and disclosure duties follow once a product is in scope under the Data Act?](/artifacts/eu/data-act/faq/scope-connected-products.md#what-access-and-disclosure-duties-follow-once-a-product-is-in-scope-under-the-data-act) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* If the connected product or related service is in scope, Article 3 of the Data Act requires product data and related service data, including relevant metadata, to be designed or provided so that they are easily, securely, free of charge, and in a comprehensive, structured, commonly used, machine-readable format accessible to the user, where relevant and technically feasible directly. - Build a data map that names product data, related service data, metadata, storage location, retention period, access method, and prospective data holder. - Use customer-facing disclosures before purchase, rent, lease, or related-service contract conclusion. - Give users a simple electronic request path where technically feasible when data cannot be directly accessed. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 3 and 4 set design, pre-contractual information, direct access, and request-based access duties for connected products and related services. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer summarizes user access, free availability to users, simple request processes, and contracts defining data access, use, and sharing rights. ### [What examples should teams use when applying the scope test under the Data Act?](/artifacts/eu/data-act/faq/scope-connected-products.md#what-examples-should-teams-use-when-applying-the-scope-test-under-the-data-act) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Use Data Act examples that separate the product, the user, the data holder, and the data. A company operating a connected bulldozer may be the user, while the bulldozer manufacturer is typically the data holder. A connected fridge with an app can involve two data holders: the entity placing the fridge on the market and the provider of the related app. - For each example, name the connected product, related service if any, user, likely data holder, and generated data category. - For connected TVs, separate product telemetry such as brightness from the film or audiovisual content itself. - For second-hand products, remember that the Data Act does not distinguish first-hand and second-hand connected products for user access rights. Sources for this answer: - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer gives examples involving bulldozers, connected fridges, smart TVs, connected cars, medical and fitness devices, planes, robots, and industrial machines. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 7, 9, 10, and 11 give examples for infrastructure boundaries, mobile products, related services, and second-hand connected products. - [European Commission - Data Act press release](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission press release uses examples such as smartwatches, cars, smart TVs, and industrial machinery to describe connected-device user control. ### [What evidence should a connected-product scope file keep under the Data Act?](/artifacts/eu/data-act/faq/scope-connected-products.md#what-evidence-should-a-connected-product-scope-file-keep-under-the-data-act) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* A useful Data Act scope file should be narrow: product identifier, EU market-placement basis, manufacturer or designer, related-service provider if any, user categories, data holder, generated data categories, readiness of access, exclusions applied, and source citation. It should be written so product, legal, engineering, support, and sales teams can apply the same classification. - Keep one product-scope record per product family and update it when architecture, related services, market placement, or contracts change. - Record exclusions separately for prototypes, content, infrastructure data, inferred or derived data, security restrictions, trade secrets, and personal-data limits. - Attach public-source citations to factual claims about scope, exclusions, users, and data categories. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 1-7 and Recitals 14-18 provide the legal fields needed to classify connected-product scope, users, data holders, related services, generated data, and SME limitations. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ provides implementation checks for connected-product status, EU market placement, related services, users, data categories, and exclusions. ### [What source evidence should teams keep for the EU Data Act connected-product scope decision later?](/artifacts/eu/data-act/faq/scope-connected-products.md#what-source-evidence-should-teams-keep-for-the-eu-data-act-connected-product-scope-decision-later) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Keep the Data Act legal basis and the practical facts together. For each scope decision, store the cited clause or recital, the Commission guidance relied on, the product family or service, the data categories involved, the trigger for the review, and the person who approved the classification. - Map the scope decision to a cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger. - Note any assumptions about market placement, user status, related services, or SME status so they can be rechecked later. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Primary legal source for connected-product definitions, territorial scope, product and related-service data, Article 3 access-by-design duties, Article 4 request access, Article 5 third-party sharing, and Article 7 SME limitations. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ source for connected-product classification, EU market placement, related-service tests, raw and pre-processed data, exclusions, users, and examples. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for Chapter II IoT scope, connected-product and related-service examples, user and data-holder roles, and user access mechanics. - [European Commission - Data Act press release](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission source for public examples of connected devices and practical user-control framing. ### [How should teams assign ownership for EU Data Act connected-product scope work and later reviews?](/artifacts/eu/data-act/faq/scope-connected-products.md#how-should-teams-assign-ownership-for-eu-data-act-connected-product-scope-work-and-later-reviews) *Module: [EU Data Act Connected Product Scope](/artifacts/eu/data-act/faq/scope-connected-products.md)* Assign one accountable owner who can change the affected process under the Data Act, then record the supporting teams separately. Legal, product, procurement, cloud, support, and security may all be involved, but the scope file should name a single owner for follow-up. - Map the scope decision to a cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger. - Use one named owner per product family so updates and reviews do not get lost between teams. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Primary legal source for connected-product definitions, territorial scope, product and related-service data, Article 3 access-by-design duties, Article 4 request access, Article 5 third-party sharing, and Article 7 SME limitations. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ source for connected-product classification, EU market placement, related-service tests, raw and pre-processed data, exclusions, users, and examples. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for Chapter II IoT scope, connected-product and related-service examples, user and data-holder roles, and user access mechanics. - [European Commission - Data Act press release](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission source for public examples of connected devices and practical user-control framing. ### [Who has Data Act Article 33 interoperability duties in a data space?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#who-has-data-act-article-33-interoperability-duties-in-a-data-space) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* The Data Act context is the starting point for this answer. Article 33 targets participants in data spaces that offer data or data services to other participants. The relevant question is not whether an organisation mentions a data space in marketing copy; it is whether the organisation is offering data, a data-sharing service, or a service used by other participants inside a purpose-specific, sector-specific, or cross-sector data-sharing framework. - Treat Article 33 as relevant when a participant offers data or data services to other participants in a data space. - Record which elements are under the participant's control before assigning remediation work. - Do not treat every internal data platform, data lake, or bilateral API as a common European data space without a supported governance and participant context. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding source for Article 33 scope and the participant-focused interoperability requirements for data spaces. - [Publications Office - European data spaces and data.europa.eu](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Explains that a data space combines participants, governance, data, technology, and services rather than being only a platform or catalogue. ### [What must a participant describe to meet EU Data Act Article 33 data-space interoperability duties?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#what-must-a-participant-describe-to-meet-eu-data-act-article-33-data-space-interoperability-duties) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* The Data Act context is the starting point for this answer. Article 33 requires descriptions that make data findable, accessible, usable, and technically exchangeable. The required descriptions cover dataset content, use restrictions, licences, collection methodology, data quality and uncertainty; data structures, formats, vocabularies, classification schemes, taxonomies and code lists where available; technical means of access such as APIs, terms of use, and quality of service; and, where applicable, means for interoperable automation of data-sharing agreements such as smart contracts. - Publish or expose enough metadata for recipients to find, access, and use the data. - Describe formats, vocabularies, taxonomies, classification schemes, and code lists consistently where they exist. - Describe API, bulk-download, continuous, or real-time access conditions without promising a mode that is not technically feasible. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 33 lists the dataset, semantic, access, API, quality-of-service, and automation descriptions that support interoperability. - [European Commission - Data Act FAQs](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ context confirms that Data Act portability and access work depends on metadata and interoperable machine-readable formats. ### [How do common European data spaces change the implementation context under the Data Act?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#how-do-common-european-data-spaces-change-the-implementation-context-under-the-data-act) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* The Data Act context is the starting point for this answer. Common European data spaces are EU-supported data infrastructures and governance frameworks for trusted data pooling and sharing in strategic sectors and domains of public interest. Commission material describes the original strategic fields as health, agriculture, manufacturing, energy, mobility, financial, public administration, skills, the European Open Science Cloud, and the Green Deal, with further areas such as media and cultural heritage emerging later. - Start with the data space's governance framework and participant rules before choosing architecture controls. - Keep horizontal Article 33 evidence separate from sector-specific rules and participant agreements. - Expect interoperability to include legal, organisational, semantic, and technical choices, not only API connectivity. Sources for this answer: - [European Commission - Staff working document on common European data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Commission source for the concept of common European data spaces and the original strategic fields announced in the European data strategy. - [European Commission - Second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Commission update on the status of common European data spaces, DSSC, Simpl, EDICs, and standards and interoperability work. ### [Does the Data Act mandate a specific standard, API, ontology, or catalogue profile for data spaces?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#does-the-data-act-mandate-a-specific-standard-api-ontology-or-catalogue-profile-for-data-spaces) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* No single named technical standard is mandated by Article 33 itself. The Data Act creates essential requirements and a standards route: the Commission requests European standardisation organisations to draft harmonised standards, participants using harmonised standards cited in the Official Journal can benefit from a presumption of conformity for covered requirements, and common specifications are a fallback when the standardisation route does not deliver as required. - Use named technical standards when the relevant data space, contract, procurement, or cited EU standardisation result requires them. - Track harmonised standards and common specifications separately from internal architecture preferences. - Do not call DCAT, NGSI-LD, SAREF, oneM2M, IDS, Gaia-X, or any other named technology mandatory under Article 33 unless a source for that exact obligation is available. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding source for the Article 33 harmonised-standards route, presumption of conformity, and common-specification fallback. - [CEN-CENELEC - Data Act Standardization Request officially accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Standardisation update confirming acceptance of Mandate M/614 and planned European standardisation deliverables for the Data Act. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Policy and standardisation context for data interoperability, data-space interoperability, data governance, metadata, and common European data spaces. ### [What should engineering and architecture teams change for Data Act data-space interoperability?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#what-should-engineering-and-architecture-teams-change-for-data-act-data-space-interoperability) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* The Data Act context is the starting point for this answer. Treat interoperability as a published contract between participants. Architecture work should make the data discoverable, the meanings stable, the access route documented, and the governance constraints enforceable. In practice, that means versioned catalogue metadata, data dictionaries, semantic mappings, API or file-transfer specifications, licence and restriction fields, quality and uncertainty fields, authentication and authorisation rules, audit logs, error handling, and service-level descriptions. - Create a versioned interoperability profile for each high-value data-space flow. - Keep API documentation, metadata samples, semantic mappings, licence terms, and QoS commitments aligned. - Separate Article 33 data-space controls from Chapter VI cloud-switching controls so deadlines, standards, and evidence do not get mixed. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding source distinguishing Article 33 data-space interoperability from Article 30 and Article 35 data-processing-service interoperability. - [European Commission - Data Act FAQs](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ explains the separate central Union repository process for interoperability of data processing services. ### [What evidence should support a Data Act data-space interoperability review?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#what-evidence-should-support-a-data-act-data-space-interoperability-review) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* The Data Act context is the starting point for this answer. Keep evidence that proves the participant did more than connect systems. A useful file includes the Article 33 scope assessment, participant role map, data-space governance rulebook or participation terms, catalogue extract, metadata schema, data-quality and uncertainty fields, licence and use-restriction fields, API or transfer specification, QoS description, semantic mappings, standards tracker, and test results for automated access or transmission. - Retain the source-linked reason for including or excluding Article 33 from each data-space flow. - Keep proof that metadata, semantics, access methods, terms of use, and QoS were actually published or shared with participants. - Review the evidence when the data space changes governance rules, when standards are cited, or when APIs and data models are versioned. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding source for Article 33 evidence themes: descriptions of datasets, restrictions, licences, quality, semantic assets, access means, and automation tools. - [Publications Office - European data spaces and data.europa.eu](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Supports the evidence focus on governance, participants, services, decentralisation, automation, and common standards in data-space operations. ### [What should teams record when deciding how EU Data Act Article 33 applies to a data-space flow?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#what-should-teams-record-when-deciding-how-eu-data-act-article-33-applies-to-a-data-space-flow) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* Under the Data Act, keep a short decision record that shows the article or clause relied on, the data-space participant role, the dataset or service in scope, and the person who approved the interpretation. The record should also note the source URL, date, reviewer, and any unresolved assumptions that still need follow-up. - Link the decision to the specific Data Act source URL and article number. - Keep the owner, workflow, evidence artifact, and review trigger together with the decision note. - Store the note with the implemented profile so the legal rationale and technical setup stay connected. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding legal source for Article 33 data-space interoperability scope, essential requirements, harmonised standards, and common specifications. - [European Commission - Data Act FAQs](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source used for interoperability context, metadata and portability explanations, and the central Union repository distinction. - [European Commission - Staff working document on common European data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Commission source for the concept and original strategic fields of common European data spaces. - [European Commission - Second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Commission source for the later data-space implementation context, including DSSC, Simpl, EDICs, and standards work. - [Publications Office - European data spaces and data.europa.eu](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - EU publication supporting practical context on data-space governance, participants, decentralisation, automation, and common standards. - [CEN-CENELEC - Data Act Standardization Request officially accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Standardisation source for Mandate M/614 and planned deliverables supporting Article 33 of the Data Act. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Standardisation policy source for data economy interoperability, data-space interoperability, metadata, governance, and common European data spaces. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support. ### [How should teams assign ownership for Data Act Article 33 implementation work?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#how-should-teams-assign-ownership-for-data-act-article-33-implementation-work) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* Under the Data Act, assign one accountable owner who can change the affected process, plus the technical and legal contacts who will help maintain the Article 33 profile. That owner should be named in the record, along with the workflow they control, such as catalogue publishing, API maintenance, data-model governance, procurement, or participant onboarding. - Name one accountable owner per data-space flow. - List the legal, product, procurement, cloud, or security teams that must be consulted before changes are approved. - Tie ownership to a concrete review trigger, not to a general compliance mailbox. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding legal source for Article 33 data-space interoperability scope, essential requirements, harmonised standards, and common specifications. - [European Commission - Data Act FAQs](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source used for interoperability context, metadata and portability explanations, and the central Union repository distinction. - [European Commission - Staff working document on common European data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Commission source for the concept and original strategic fields of common European data spaces. - [European Commission - Second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Commission source for the later data-space implementation context, including DSSC, Simpl, EDICs, and standards work. - [Publications Office - European data spaces and data.europa.eu](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - EU publication supporting practical context on data-space governance, participants, decentralisation, automation, and common standards. - [CEN-CENELEC - Data Act Standardization Request officially accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Standardisation source for Mandate M/614 and planned deliverables supporting Article 33 of the Data Act. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Standardisation policy source for data economy interoperability, data-space interoperability, metadata, governance, and common European data spaces. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support. ### [What should teams keep so they can justify an EU Data Act Article 33 decision later on?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#what-should-teams-keep-so-they-can-justify-an-eu-data-act-article-33-decision-later-on) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* Under the Data Act, the useful evidence is the kind that lets a later reviewer reconstruct the decision without guesswork. That usually includes the relevant clause, the participant's role, the dataset or service, the contract or request trigger, and the external source URL. If the team relied on a standards or governance assumption, that assumption should be written down too. - Keep source URLs, the decision date, and the reviewer name in the same file as the implementation artifact. - Record unresolved assumptions and the standardisation status when those shaped the decision. - Use the same folder or system for the legal note and the technical profile so they do not drift apart. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding legal source for Article 33 data-space interoperability scope, essential requirements, harmonised standards, and common specifications. - [European Commission - Data Act FAQs](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source used for interoperability context, metadata and portability explanations, and the central Union repository distinction. - [European Commission - Staff working document on common European data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Commission source for the concept and original strategic fields of common European data spaces. - [European Commission - Second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Commission source for the later data-space implementation context, including DSSC, Simpl, EDICs, and standards work. - [Publications Office - European data spaces and data.europa.eu](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - EU publication supporting practical context on data-space governance, participants, decentralisation, automation, and common standards. - [CEN-CENELEC - Data Act Standardization Request officially accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Standardisation source for Mandate M/614 and planned deliverables supporting Article 33 of the Data Act. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Standardisation policy source for data economy interoperability, data-space interoperability, metadata, governance, and common European data spaces. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support. ### [When should a Data Act data-space interoperability decision be reviewed again?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#when-should-a-data-act-data-space-interoperability-decision-be-reviewed-again) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* Under the Data Act, review the decision whenever the participant role, dataset, service, contract wording, or governance rule changes. A new API version, a new data structure, or a new sector rulebook can all change what Article 33 requires in practice. - Set a review date and add event-based triggers for contract, dataset, or standards changes. - Recheck the profile when a data space changes governance rules or participant terms. - Update the evidence when the architecture, API, or metadata model changes. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding legal source for Article 33 data-space interoperability scope, essential requirements, harmonised standards, and common specifications. - [European Commission - Data Act FAQs](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source used for interoperability context, metadata and portability explanations, and the central Union repository distinction. - [European Commission - Staff working document on common European data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Commission source for the concept and original strategic fields of common European data spaces. - [European Commission - Second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Commission source for the later data-space implementation context, including DSSC, Simpl, EDICs, and standards work. - [Publications Office - European data spaces and data.europa.eu](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - EU publication supporting practical context on data-space governance, participants, decentralisation, automation, and common standards. - [CEN-CENELEC - Data Act Standardization Request officially accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Standardisation source for Mandate M/614 and planned deliverables supporting Article 33 of the Data Act. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Standardisation policy source for data economy interoperability, data-space interoperability, metadata, governance, and common European data spaces. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support. ### [What should teams avoid when applying the Data Act Article 33 FAQ answer?](/artifacts/eu/data-act/faq/data-spaces-interoperability.md#what-should-teams-avoid-when-applying-the-data-act-article-33-faq-answer) *Module: [EU Data Act data spaces interoperability](/artifacts/eu/data-act/faq/data-spaces-interoperability.md)* Do not treat the Data Act Article 33 answer as a generic privacy, cloud, or procurement checklist. The right answer depends on the participant role, the data-space governance context, and the exact dataset or service being shared. - Do not copy the same requirement into every data-space flow without checking the role and trigger. - Do not cite a technology as mandatory unless the source actually says so. - Do not separate the legal decision from the implementation record. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding legal source for Article 33 data-space interoperability scope, essential requirements, harmonised standards, and common specifications. - [European Commission - Data Act FAQs](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Commission FAQ source used for interoperability context, metadata and portability explanations, and the central Union repository distinction. - [European Commission - Staff working document on common European data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Commission source for the concept and original strategic fields of common European data spaces. - [European Commission - Second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Commission source for the later data-space implementation context, including DSSC, Simpl, EDICs, and standards work. - [Publications Office - European data spaces and data.europa.eu](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - EU publication supporting practical context on data-space governance, participants, decentralisation, automation, and common standards. - [CEN-CENELEC - Data Act Standardization Request officially accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Standardisation source for Mandate M/614 and planned deliverables supporting Article 33 of the Data Act. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Standardisation policy source for data economy interoperability, data-space interoperability, metadata, governance, and common European data spaces. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support. ## FAQ Pagination - Canonical index (page 1): [/artifacts/eu/data-act/faq/items](/artifacts/eu/data-act/faq/items.md) - Page 1 rule: `/page/1` is intentionally not generated; use the canonical index markdown URL. - Current page: 15 of 24 Pages: [1](/artifacts/eu/data-act/faq/items.md) | [2](/artifacts/eu/data-act/faq/items/page/2.md) | [3](/artifacts/eu/data-act/faq/items/page/3.md) | [4](/artifacts/eu/data-act/faq/items/page/4.md) | [5](/artifacts/eu/data-act/faq/items/page/5.md) | [6](/artifacts/eu/data-act/faq/items/page/6.md) | [7](/artifacts/eu/data-act/faq/items/page/7.md) | [8](/artifacts/eu/data-act/faq/items/page/8.md) | [9](/artifacts/eu/data-act/faq/items/page/9.md) | [10](/artifacts/eu/data-act/faq/items/page/10.md) | [11](/artifacts/eu/data-act/faq/items/page/11.md) | [12](/artifacts/eu/data-act/faq/items/page/12.md) | [13](/artifacts/eu/data-act/faq/items/page/13.md) | [14](/artifacts/eu/data-act/faq/items/page/14.md) | [15](/artifacts/eu/data-act/faq/items/page/15.md) | [16](/artifacts/eu/data-act/faq/items/page/16.md) | [17](/artifacts/eu/data-act/faq/items/page/17.md) | [18](/artifacts/eu/data-act/faq/items/page/18.md) | [19](/artifacts/eu/data-act/faq/items/page/19.md) | [20](/artifacts/eu/data-act/faq/items/page/20.md) | [21](/artifacts/eu/data-act/faq/items/page/21.md) | [22](/artifacts/eu/data-act/faq/items/page/22.md) | [23](/artifacts/eu/data-act/faq/items/page/23.md) | [24](/artifacts/eu/data-act/faq/items/page/24.md) [Previous page](/artifacts/eu/data-act/faq/items/page/14.md) | [Next page](/artifacts/eu/data-act/faq/items/page/16.md) *Recommended next step* *Placement: before sources* ## Turn a Data Act FAQ answer into a scoped review Review one product, dataset, cloud contract, public-sector request, or smart-contract deployment against the cited Data Act source and keep the scope, role, evidence, and unresolved questions together. - [Open Research Copilot](/solutions/research-copilot.md): Check Data Act scope, GDPR boundaries, cloud switching, and contract questions with cited source outputs. - [Talk through Data Act implementation](/contact.md): Review one connected product, data-sharing contract, cloud switch, or public-sector request before committing to an implementation path. --- [Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/data-act/faq/items/page/15