Centre for Digital Public Infrastructure
english
english
  • THE DPI WIKI
    • 🎉About the DPI Wiki
    • 🔆What is DPI?
    • ✨DPI Overview
    • 📝DPI Tech Architecture Principles
      • 🔗Interoperability
      • 🧱Minimalist & Reusable Building Blocks
      • 💡Diverse, Inclusive Innovation
      • 💠Federated & Decentralised by Design
      • 🔐Security & Privacy By Design
    • 🎯DPI Implementation & Execution Guidance
    • 🆚DPG and DPI
    • ❓What DPI can I build?
    • 🥇First use case for DPI
    • 📘Inputs for designing a DPI informed digital transformation strategy
    • 💰How much does it cost to build DPI?
    • 📢Is my system a DPI?
      • TL; DR - Is my system a DPI?
  • Mythbusters and FAQs
    • 🔯DPI and Mandating Adoption
    • 🔯DPI and Private Competition
    • 🔯DPI and Privacy / Security
    • 🔯DPI and the Digital Divide
  • Technical Notes
    • 🆔Identifiers & Registries
      • Digital ID
        • Capabilities on ID system
        • ID-Auth
        • Face Authentication
        • eKYC/ Identity profile sharing
        • Single Sign On (SSO)
        • QR Code for Offline ID
    • 📂Data Sharing, Credentials and Models
      • A primer to personal data sharing
      • Data standards
      • Verifiable Credentials
      • Building Data Analytics Pipelines
      • eLockers
      • Non-personal Anonymised Datasets
    • 🔏Trust Infra
      • Digital Signatures and PKI
      • eConsent
      • eSign
    • 🛒Discovery & Fulfilment
      • Platforms to Protocols
    • 💸Payments
      • Financial Address
      • Interoperable QR Code
      • Interoperable Authentication
      • Interoperable Bill Payments
      • Cash in Cash Out (CICO)
      • Financial Address Mapper (G2P Connect)
      • G2P Payments
  • Initiatives
    • 🌐DPI advisory
    • 🚀DPI as a Packaged Solution (DaaS)
      • 💡Why do we need DaaS?
      • 🎯DaaS in a nutshell
      • 📦Pre-packaged DaaS kits
      • ♻️Reusable DaaS Artefacts
      • 3️⃣A 3-step process from idea to implementation!
      • 📈Funded DaaS Program overview
      • 👩‍💻Cohort 1: DaaS Offerings
        • Digital authentication
        • Digital credentials
        • ID Account Mapper
      • 🖥️Co-create with us!
      • 💬Upcoming DaaS cohorts
        • Functional Registries
        • AI Assistant
      • ❓FAQs on DaaS
        • Country x DPG MOU /LoI FAQs
        • Ecosystem Participation Terms FAQs
    • 📑DPI Residents Program
    • ⚖️DPI-CPA
    • 💸G2P Connect
    • 📨User Centric Credentialing & Personal Data Sharing
    • ⚕️DPI for Health
    • 🌍Agri Connect (forthcoming)
  • References
    • Glossary
    • Curated Specifications
  • Additional Info
    • 🤝Licensing
    • ✍️Contact Us
Powered by GitBook
On this page
  • Overview (What to aim for)
  • Technical Tools (How to achieve it)
  • Societal Outcomes (Why it matters)
Export as PDF
  1. THE DPI WIKI
  2. DPI Tech Architecture Principles

Diverse, Inclusive Innovation

by the ecosystem, via open & multi-modal access

Overview (What to aim for)

A DPI should not just be innovative in itself, but also enable diverse innovation by a public/private ecosystem of users.

A DPIs tech architecture should allow others (public and private innovators) to build solutions and services using the DPI at scale (akin to highways or the Internet) via tools such as open APIs (instead of DPI providers building the entire solution in a monolithic fashion).

Enable innovation both by ‘challenger’ market players in the ecosystem and by incumbents.

A digital back-end shouldn't presuppose a single digital front-end. Enable both the core DPI architecture and a diversity of innovative ecosystem-created solutions to power multi-modal access: across online, semi-online (low bandwidth connectivity), and offline modes; self-service and assisted modes; and in smartphone/feature phone/ no-phone modes.

  • For instance, payment systems or identity systems shouldn't presuppose just one mode of authentication (e.g. online API based) and allow for offline or semi-online modes (QR codes, local SDKs that can perform face authentication, etc.)

This is essential to catalyse private innovation that doesn't merely target an elite connected population in a country, but also innovates to solve the challenges of diverse populations who speak multiple languages and have varying levels of digital literacy - thus reducing the impact of a digital divide. The principle also addresses both scale and adaptability/sustainability over time.

Private Innovation can be leveraged both in building the DPI (for instance, in driving private partners to enroll individuals into an identity system) and in usage of the DPI in a wider digital economy to offer solutions (for instance, banks or private players using an identity eKYC to offer a service like opening a bank account).

Public/private adoption and innovation should be voluntary and demand-based rather than mandated by authorities. This tends to create sustained usage over time.

Technical Tools (How to achieve it)

Societal Outcomes (Why it matters)

PreviousMinimalist & Reusable Building BlocksNextFederated & Decentralised by Design

Last updated 1 year ago

📝
💡