Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Cross-Border Semantic Data Management Source: ISO/IEC/IEEE 42010:2022 Source reference: https://www.iso.org/standard/74393.html Additional information: Cross-border Semantic Data Management is a concept that refers to the management of data across different countries or regions, with a focus on ensuring that the data is consistent and understandable across all borders. This involves the use of semantic technologies, which allow for the creation of a common language or vocabulary that can be used to describe data in a way that is easily understood by all parties involved. The goal of cross-border semantic data management is to improve the efficiency and effectiveness of data sharing and collaboration across different regions, while also ensuring that the data remains secure and protected. This concept is particularly important in today's globalized economy, where businesses and organizations often need to work together across borders to achieve their goals. Example: Decision: Data provider discovery and (semantic) data management capabilities are both operated by the same entity, with the role of Cross-Border Data Exchange. Consequence: Cross-Border Data Management is a new business role. LOST view: Digital Solution Architecture Decisions Catalogue view Identifier: http://data.europa.eu/dr8/egovera/Cross-BorderSemanticDataManagementGoal EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal ABB name: egovera:Cross-BorderSemanticDataManagementGoal EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-06-15 dct:identifier: ADR-20230515180947395 dct:title: Architecture Decision Record about Cross-Border Semantic Data Management eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons. eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how. eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)] eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.