Glossary

• Asynchronous processing A form of communication — such as batch processing, file transfer, and streaming — in which processing continues without waiting for the result of an external call, and the result is received via a callback or similar mechanism. The receiving side continues to receive data until the calling side stops processing.

• Backward compatibility A state in which a newer means within the same family encompasses (is compatible with) the specifications and functions of older means.

• Closed World Assumption (CWA) A principle in which, if a piece of information does not exist in a knowledge base, that information is regarded as "false." This is the assumption underlying relational databases and general DBMS.

• Common Functionalities A set encompassing the basic protocols for ensuring interoperability across dataspaces. Includes versioning, logging, monitoring, notifier, and similar functions.

• Complementary Protocol Specifications for providing supplementary functions required to realize Open Dataspaces; protocols that may be adopted as needed to realize the functions of the corresponding layer or perspective.

• Core services Within DFS, services within DFS that provide, as managed services, the core components playing a central role in each of layers L1 through L4.

• Data Free Flow with Trust (DFFT) A concept that aims to promote internationally free data flows in which data beneficial to business and societal challenges can move freely across borders without constraint, while ensuring trust with respect to privacy, security, and intellectual property rights.

• Data Layer (L1) The layer that addresses the problems of data usage control, data tampering, and data quality.

• Data provider An entity that provide data and exercises usage control over it. The data provider self-determines the storage and usage conditions to be applied when granting permission for data use.

• Data user An entity that uses data. Data users comply with the self-determination of data providers and acquire, store, and use data within the scope of the storage and usage conditions set by the data provider.

• Dataspace Complementary Services (DCS) Services that provide, as managed services, the technical implementations of the functions required to realize the complementary protocol requirements defined in ODP.

• Dataspace Fundamental Services (DFS) Services that provide, as managed services, the technical implementations of the functions required to realize the fundamental protocol requirements defined in ODP.

• DSSP (Dataspace Service Provider) A managed service for the basic software stack constituting the DPQM, provided by an intermediary on behalf of domain owners.

• Enterprise data A collective term for all data — regardless of whether structured or unstructured — that an organization generates, acquires, processes, uses, transfers, provides, stores, and disposes of in the course of its economic activities.

• Federated service model A model in which an managed service provider (intermediary) delivers the basic software stack that constitutes DPQM on behalf of the domain owner, while the domain owner retains responsibility for providing Data/Ontology Product

• Fundamental Protocol Specifications for providing the core functions required to realize Open Dataspaces; protocols that must be adopted to realize the functions of the corresponding layer or perspective.

• Governance Perspective (P2) A perspective that establishes common rules and policies to achieve specific objectives within the ecosystem, and performs cross-cutting management, oversight, and administration.

• Hybrid Service Model (HSM) A hybrid of the distributed service model and the federated service model. A service model in which both approaches coexist: domain owners onboarding voluntarily under loosely defined rules, and onboarding via DSSP intermediation.

• Identity Layer (L3) The layer that addresses the problems of authentication and authorization.

• Industry Service (IS) Services that provide business applications and business platforms specialized for specific industries and domain use cases.

• Intermediary An entity that provides managed services as DSSP on behalf of data providers and data users who are unable to build and operate their own environments.

• Layers Logical tiers into which the dataspace is separated according to functional purpose.

• Logging A function that enables comprehensive recording and analysis of system communication status, processing results of each service, and overall monitoring and operational status, based on three categories: communication logs, service logs, and processing logs.

• Monitoring A function for continuously monitoring and managing system health and performance by tracking the execution environment and service operational status from system logs.

• Notifier A notification function for sharing updates and acknowledgment status related to data transactions between data providers and data users.

• Open Data Spaces (ODS) An open and scalable foundation for distributed data, built on organizational and national diversity by design.

• Open Data Spaces Protocols (ODS Protocols: ODP) A set of technical specifications that provide the functions realizing distributed data management and ensure the interoperability of Open Dataspaces.

• Open World Assumption (OWA) A principle in which, if a piece of information does not exist in a knowledge base, that information is regarded as "neither true nor false (unknown)." This is the assumption underlying Semantic Web technologies such as RDF/OWL.

• Perspectives Logical viewpoints that fulfill cross-cutting functions across the ecosystem encompassing the entirety of Open Dataspaces.

• Reference implementation Hardware or software that realizes a certain function and is created for the purpose of helping others implement it independently using it as a reference.

• Schema-first A methodology in which a schema is defined in advance and data is entered in conformance with that definition. Synonymous with Schema-on-write.

• Schema-flexible A methodology premised on the absence of a pre-defined schema or the existence of multiple different pre-defined schemas, in which analysis is performed based on metadata and similar information only when data is read, and the data is made to conform to a schema as needed. Synonymous with schema-on-read.

• Security-by-Design An approach to ensuring security from the planning and design stages.

• Security Perspective (P3) A perspective that presents the security requirements and measures required in whole or in part within the ecosystem.

• Semantics Layer (L4) The layer that addresses the problems of addressability and semantics.

• Service Perspective (P1) A perspective that bridges the technical domain — encompassing functions and operations — with the business domain.

• Structured data Formalized data such as web API request/response data, database transfers, and message queues. Premised on being read by systems, with schema structure as the priority, based on clear type definitions using Open API, Async API, and similar standards.

• Synchronous processing A form of communication — such as API request/response — in which processing waits until the result of an external call is received. Processing terminates upon completion of the transmission and reception of the specified data.

• Transaction component The core component of the transaction layer (L2) used by data providers when transmitting data.

• Transaction Layer (L2) The layer that addresses the problems of modal, query, and protocol.

• Trust Perspective (P4) A perspective that presents the trust requirements and measures required in whole or in part within the ecosystem.

• Unified Meta Identifier (UMI) An identifier developed in a form that abstracts identifier systems that have been individually optimized within enterprises and industries and exist as heterogeneous systems.

• Unstructured data Data with diverse formats — such as images, video, audio, drawings, and log data — that has a free structure not bound by a fixed schema.

• Versioning A function that manages changes to specifications, configurations, and components to maintain interoperability among participants under the same premises.