The ITMO Schema defines a standardized structure for Internationally Transferred Mitigation Outcomes (ITMOs) as W3C Verifiable Credentials. It combines established standards with domain-specific extensions to ensure interoperability and compliance with Article 6.2 requirements.

Key Components

Standards Compliance

Built on W3C Verifiable Credentials and JSON-LD

Semantic Clarity

Unambiguous term definitions via JSON-LD context

Cryptographic Proofs

Ed25519-2018 suite for tamper-evident credentials

Data Provenance

W3C PROV vocabulary for traceability

Core Structure

JSON-LD Context

The JSON-LD context provides semantic meaning to ITMO data, enabling unambiguous interpretation across different systems while maintaining data integrity and provenance tracking.

Credential Attributes

Authorization Information

{
  "credentialSubject": {
    "itmo:authorizationInfo": {
      "itmo:authorizationReference": "AUTH-2024-001",
      "itmo:cooperativeApproachDuration": "2024-01-01T00:00:00Z/2024-12-31T23:59:59Z",
      "itmo:expectedMitigationOutcomes": {
        "2024": 5000
      },
      "itmo:participatingParties": ["ZMB", "CHE"],
      "itmo:authorizedEntities": [
        "did:ixo:entity:project123",
        "did:ixo:entity:verifier456"
      ]
    }
  }
}

NDC Quantification

{
  "credentialSubject": {
    "itmo:ndcQuantification": {
      "itmo:sectors": ["Residential", "Energy"],
      "itmo:sources": ["BiomassFuelCombustion"],
      "itmo:ghgs": ["CO2", "CH4", "N2O"],
      "itmo:referenceLevel": 1000,
      "itmo:targetLevel": 800,
      "itmo:quantificationTonnesCO2e": 200
    }
  }
}

Corresponding Adjustments

{
  "credentialSubject": {
    "itmo:correspondingAdjustments": {
      "itmo:singleYearTarget": true,
      "itmo:multiYearTarget": false,
      "itmo:emissionsTrajectory": [1000, 950, 900, 850, 800],
      "itmo:annualAdjustments": [40, 40, 40, 40, 40],
      "itmo:cumulativeAdjustment": 200
    }
  }
}

Validation & Proofs

Developer Best Practices

Interoperability

  • Use standard JSON-LD contexts
  • Implement full vocabulary
  • Support multiple proof types
  • Enable cross-registry exchange

Data Validation

  • Validate schema compliance
  • Check proof signatures
  • Verify credential status
  • Validate semantic constraints

Extension Points

  • Custom context terms
  • Additional proof methods
  • Enhanced provenance tracking
  • Registry-specific metadata

Implementation Guide

Create Credential

  1. Initialize context and type
  2. Add credential metadata
  3. Populate subject data
  4. Generate and attach proof

Verify Credential

  1. Validate JSON-LD structure
  2. Check schema compliance
  3. Verify cryptographic proof
  4. Validate business rules

Process Credential

  1. Parse semantic data
  2. Extract relevant claims
  3. Process adjustments
  4. Update registries

Next Steps