BDI Public Documentation
  • Reference Architecture
    • INTRODUCTION
      • Core Principles
      • Stack and KITs
      • BDI Technical Roles
    • BDI Maintenance and Community Contributions
    • Trust KIT
      • Digital Identity
        • Digital Identity M2M
        • Digital Identity H2M
      • Authentication
        • Authentication M2M
        • Page
        • Authentication H2M
      • Authorization
      • Edge agreements
      • Policy agreements
      • Onboarding Terms and Conditions
      • Association Register
      • Discovery
      • Demos
        • Trusted Goods Release & Delegation
    • Logistics Event KIT
      • Notification pub/sub service
      • Event Choreography
      • Trusted Goods Release - Event Demo
    • Semantics KIT
      • Overview
      • Logistics event Ontology
      • Demos
    • Representation KIT
      • Representation Chain
      • Professional Qualification Chain
      • BDI Association Roles
      • Demos
    • Federation KIT
      • Federation of Associations
      • Business Partner Reputation Model
      • Interoperability
      • Demos
    • Data Set KIT
      • Data Licenses
      • Demos
    • Verifiable Credentials KIT​
      • Verifiable Credentials
      • Provenance & Traceability
      • Demos
    • Security
      • Information Security Policy
      • Risk Assessment and Treatment
      • Control Implementation
      • Monitoring, Measurement, Analysis, and Improvement
    • Boundary Management
      • Digital Asset Boundaries
      • Physical Asset Boundaries
      • Legal Asset Boundaries
      • Demos
    • GLOSSARY
      • BDI Terms
Powered by GitBook
On this page
  • Introduction to the BDI Reference Architecture
  • Observations
Export as PDF
  1. Reference Architecture

INTRODUCTION

PreviousReference ArchitectureNextCore Principles

Last updated 5 months ago

Introduction to the BDI Reference Architecture

The Basic Data Infrastructure Framework (BDI) is an infrastructure framework for controlled data sharing, supporting automated advanced information logistics in the physical economy. Departing from traditional messaging paradigms, the BDI shifts towards event-driven data collection at the source, fostering efficient and secure coordination through proven publish-and-subscribe architectures.

This introduction provides a short overview of some issues which play a role in the design of the architecture. We start with some observations about data in a logistic environment. These observations are used in the formulation of architectural principles which are in turn the basis of BDI building blocks. Finally, these building blocks are grouped in functional subsets called KITs.

See for a full account of these concepts.

Observations

  • The data exchange patterns in typical operational networks are a result of “doing business” have specific characteristics:

    • The network of involved parties is driven by the fulfillment of an assignment - these networks are temporary and fluid, that is, members are added whenever necessary and the network is dissolved when the job is done.

    • Data exchanges are between members of a closed group, i.e. the members are vetted in advance.

    • There can be time constraints on the exchange of data.

  • A common data exchange infrastructure for operational networks should support:

    • Dynamic instances

    • Multiple concurrent instances

    • Controlled event-driven exchange

  • Event-driven exchange of operational data within an instance must be:

    • Efficient: no polling, no unnecessary retrieval

    • Effective: easy distribution to multiple parties simultaneously

    • Controlled:

      • Limited exposure to malicious actors.

      • Only authorized parties can retrieve information.

      • Role based data access.

      • The Data Owner tracks access, providing a clear audit trail.

  • The value of data:

    • Data has value

    • Data owners want to protect and monetize this value

  • The importance of trust in global business networks

    • Identification authentication and authorization play an important role in establishing trust.

    • Zero trust - do not trust anyone before trust is established.

    • Perimeterless trust - do not base trust on membership of a closed group of trusted parties

bdinetwork.org