Proposal: Regional Alignment

Context / Problem Statement

Digital identity ecosystems are emerging globally, each with distinct regulatory requirements, trust frameworks, credential formats, and deployment timelines. Organizations operating across regions need a unified library that adapts to local requirements without maintaining separate codebases.

The SD-JWT .NET ecosystem currently has deep support for EU (via SdJwt.Net.Eudiw) but lacks:

• Pluggable regional profile abstraction
• APAC framework adapters (NZ DISTF, Australia, Thailand, Japan)
• Americas framework adapters (US, Canada, Brazil)
• Configuration-driven ecosystem alignment without code changes

Goals

1. Define a regional profile abstraction (IRegionalProfile) that encapsulates per-region requirements
2. Implement profiles for EMEA, APAC, Americas, and custom ecosystems
3. Allow configuration-driven profile selection (no code changes to switch regions)
4. Map each region's requirements to existing ecosystem packages
5. Provide compliance validation per regional profile

Non-Goals

• Implement region-specific wallet UX
• Manage regional certificate authorities
• Provide legal compliance advice (this is a technical framework, not legal counsel)

Proposed Design

Architecture

flowchart TB
    subgraph App["Application"]
        Config["Configuration"]
    end

    subgraph Profiles["Regional Profiles"]
        IProfile["IRegionalProfile"]
        EMEA["EMEA Profile"]
        APAC["APAC Profile"]
        Americas["Americas Profile"]
        Custom["Custom Profile"]
    end

    subgraph Existing["Existing Packages"]
        HAIP["SdJwt.Net.HAIP"]
        Eudiw["SdJwt.Net.Eudiw"]
        Trust["SdJwt.Net.Trust"]
        Wallet["SdJwt.Net.Wallet"]
    end

    Config --> IProfile
    IProfile --> EMEA
    IProfile --> APAC
    IProfile --> Americas
    IProfile --> Custom

    EMEA --> Eudiw
    EMEA --> HAIP
    APAC --> HAIP
    Americas --> HAIP
    Custom --> Trust
    Custom --> Wallet

Regional Profile Interface

public interface IRegionalProfile
{
    string RegionId { get; }
    string DisplayName { get; }

    // Credential format requirements
    IReadOnlyList<string> SupportedFormats { get; }

    // Algorithm requirements
    IReadOnlyList<string> AllowedAlgorithms { get; }
    int MinimumHaipLevel { get; }

    // Trust framework
    ITrustResolver GetTrustResolver();

    // Compliance validation
    Task<ComplianceResult> ValidateComplianceAsync(ComplianceContext context);
}

Regional Landscape

EMEA

APAC

Americas

API Surface

// Configuration-driven profile selection
var profile = RegionalProfileFactory.Create("emea-eidas2");

// Or custom profile
var custom = new CustomRegionalProfile()
    .WithFormats("vc+sd-jwt", "mso_mdoc")
    .WithAlgorithms("ES256", "ES384")
    .WithMinimumHaipLevel(2)
    .WithTrustResolver(new EidasTrustListAdapter(lotlUrl))
    .Build();

// Compliance check
var result = await profile.ValidateComplianceAsync(new ComplianceContext
{
    Credential = credential,
    IssuerIdentifier = "https://issuer.example.de",
    CredentialType = "eu.europa.ec.eudi.pid.1"
});

// result.IsCompliant = true
// result.Profile = "emea-eidas2"
// result.Details = ["Algorithm: ES256 (compliant)", "Trust: LOTL resolved", ...]

Security Considerations

Estimated Effort

Related Documentation

• EUDIW Deep Dive - EU-specific implementation
• HAIP Deep Dive - Security profiles
• Trust Registries Proposal - Trust infrastructure
• Capability Matrix - Feature coverage