Contribute to Canonical ESG

Canonical ESG maintains two independent systems with distinct contribution pathways.

Two Independent Systems:

  • • CDI/CEDM Semantic Infrastructure — For organization-level sustainability reporting standards
  • • UPPS Product Passport Standards — For product-level disclosure requirements

Choose your contribution area below.

Part 1: CDI/CEDM Semantic Infrastructure

For organization-level sustainability reporting standards (GRI, ESRS, ISSB, TCFD, CSRD)

Why Contribute to Semantic Infrastructure

Sustainability reporting today is fragmented across multiple frameworks, jurisdictions, and interpretive layers.

CDI/CEDM semantic infrastructure provides:

  • Stable semantic disclosure intents (CDI)
  • Cross-framework mapping infrastructure (CMP)
  • Regulatory modelling across jurisdictions
  • Version-safe extensibility
  • Semantic equivalence analysis across standards

Contributors help:

  • Strengthen semantic precision
  • Expand framework coverage
  • Stress-test cross-framework mappings
  • Identify structural inconsistencies
  • Improve regulatory modelling architecture

This is infrastructure work.

Who Should Contribute (Semantic Infrastructure)

We welcome contributions from:

  • ESG and sustainability reporting specialists
  • ESRS technical practitioners
  • ISSB / IFRS S1–S2 experts
  • GRI specialists (Universal, 200, 300, 400)
  • SASB standards practitioners
  • CDP reporting professionals
  • EU Taxonomy regulatory experts
  • TNFD and biodiversity disclosure specialists
  • RegTech engineers
  • Semantic modelling researchers
  • Accounting and assurance professionals
  • Policy and regulatory analysts

Institutional affiliation is not required.

Rigor is.

Semantic Infrastructure Contribution Areas

1. CDI Taxonomy Refinement

  • Clarification proposals
  • Semantic precision improvements
  • Cross-domain consistency enhancements
  • Future domain proposals (for CDI v2)

2. New Framework Coverage

  • Additional voluntary standards
  • Emerging regulatory regimes
  • Jurisdiction-specific requirements
  • Sector-specific disclosure regimes

3. Stress Testing & Equivalence Analysis

  • Line-by-line framework comparison
  • Conflict detection
  • Coverage gap identification
  • Cross-framework semantic reconciliation

4. Regulatory Modelling Enhancements

  • Technical screening criteria modelling
  • KPI architecture refinement
  • Eligibility vs alignment logic modelling
  • DNSH and safeguard modelling

5. Governance & Documentation

  • Versioning architecture improvements
  • Schema validation refinement
  • Contribution governance proposals

Semantic Infrastructure Contribution Principles

All semantic infrastructure contributions must align with core principles:

  • Framework Independence
  • Semantic Stability
  • Non-Authoritativeness
  • Regulatory Neutrality
  • Explicit Scope Boundaries
  • Version Safety

CDI/CEDM does not create legal interpretations.

It models structure — not compliance.

How to Contribute (Semantic Infrastructure)

Step 1 — Review the Architecture

Before submitting a proposal, review:

  • CDI Taxonomy (v1)
  • CMP Schema
  • Global CMPs
  • Jurisdiction CMPs
  • Version freeze declarations

Step 2 — Prepare a Structured Proposal

Your proposal should clearly state:

  • Scope of change
  • Affected CDI identifiers
  • Relevant framework references
  • Semantic justification
  • Cross-framework impact analysis
  • Backward compatibility assessment

Unstructured suggestions will not be evaluated.

Step 3 — Submit Proposal

Proposals may be submitted via:

Semantic Infrastructure Governance

CDI/CEDM currently operates under a curated stewardship model.

  • CDI v1 is frozen.
  • Major semantic extensions require a new major version.
  • CMPs may evolve without altering CDI semantics.
  • All accepted changes are documented through version history.

As participation grows, governance formalization will expand.

Early Contributor Participation (Semantic Infrastructure)

We are currently inviting early contributors to:

  • Stress-test cross-framework mappings
  • Review regulatory modelling architecture
  • Participate in semantic equivalence analysis
  • Shape the CDI v2 roadmap

Early contributors influence structural direction.

Part 2: UPPS Product Passport Standards

For product-level disclosure requirements

Why Contribute to UPPS Standards

Product-level sustainability disclosure is emerging as a critical requirement globally, driven by regulations like the EU Digital Product Passport (DPP) and growing consumer demand for transparency.

UPPS provides:

  • Standardized product disclosure requirements across six key areas
  • Alignment with emerging regulations (EU DPP, ESPR, CSRD)
  • Sector-specific implementation guidance
  • Data quality and verification frameworks
  • Interoperability with existing standards

Contributors help:

  • Refine disclosure requirements based on implementation experience
  • Develop sector-specific guidance
  • Improve data quality and verification protocols
  • Ensure regulatory alignment without compromising global applicability
  • Identify practical implementation challenges

Who Should Contribute (UPPS Standards)

We welcome contributions from:

  • Product sustainability managers and practitioners
  • Supply chain transparency specialists
  • Circular economy experts
  • LCA (Life Cycle Assessment) professionals
  • Product compliance and regulatory experts
  • Digital product passport implementers
  • Traceability and blockchain specialists
  • Consumer goods and manufacturing professionals
  • Packaging and materials experts
  • Social compliance and labor rights specialists
  • Product assurance and verification professionals

UPPS Contribution Areas

1. Standard Refinement

  • Clarification of disclosure requirements
  • Methodology improvements
  • Boundary definition refinements
  • Calculation guidance enhancements

2. Sector-Specific Guidance

  • Textiles and apparel guidance
  • Electronics and ICT sector requirements
  • Food and beverage disclosures
  • Construction materials standards
  • Automotive and transportation

3. Implementation Experience

  • Pilot implementation feedback
  • Data availability challenges
  • Practical implementation barriers
  • Cost-benefit analysis

4. Data Quality and Verification

  • Data quality tier definitions
  • Verification protocol development
  • Assurance level guidance
  • Auditor qualification requirements

5. Regulatory Alignment

  • EU DPP compliance mapping
  • ESPR alignment analysis
  • Regional regulatory requirements
  • International standard harmonization

How to Contribute (UPPS Standards)

Step 1 — Review UPPS Standards

Before submitting feedback, review:

Step 2 — Prepare Structured Feedback

Your feedback should include:

  • Specific standard and section reference
  • Clear description of issue or improvement
  • Rationale (implementation experience, regulatory alignment, etc.)
  • Proposed solution or alternative language
  • Impact assessment on existing implementations
  • Sector or product category context

Step 3 — Submit Feedback

UPPS feedback may be submitted via:

  • Email: hello@canonicalesg.org (subject: "UPPS Feedback")
  • Public consultation periods (announced on website)
  • Stakeholder working groups (by invitation)

UPPS Governance

UPPS standards are currently in Draft status (v0.1).

  • Substantive changes undergo 60-day public consultation
  • Stakeholder feedback is documented and addressed transparently
  • Standards evolve based on implementation experience
  • Version 1.0 release planned after pilot implementations and stakeholder validation

Early feedback shapes the foundation of UPPS standards.

Contact for Contributions

For all contribution inquiries:

Email: hello@canonicalesg.org

Semantic Infrastructure GitHub: github.com/udaysxd/canonicalesg_open_architecture

Please specify whether your contribution relates to CDI/CEDM Semantic Infrastructure or UPPS Product Passport Standards.