Open Public Standard · Carbon Intelligence Infrastructure
COMET.
Carbon Ontology for Markets, Emissions & Trade — v0.1 Public Draft
A shared, versioned, community-governed meta-ontology mapping product-level carbon footprint data, supply chain verification endpoints, Environmental Attribute Certificates, and market-pricing signals into a single interoperable knowledge graph.
Repositorygithub.com/comet-ontology/comet
LicenseCC BY 4.0 + Apache 2.0
Namespacecomet.carbon/v1/
StatusPublic Draft · RFC Open
Initiated2025-Q1
Visualization 01 — Architecture
The COMET Seven-Layer Stack
Seven semantic layers from raw measurement to market signal. Each layer is independently versionable. Upper layers depend on lower; contributions target specific layers via labeled PR tags.
Eight primary stakeholder rings — each contributes different artifacts, extracts different value. The ontology serves all simultaneously without privileging any single actor.
Visualization 03 — Maturity Model
Data & Ontology Maturity Levels
Organizations enter COMET at their current data maturity. The ontology supports all levels simultaneously — spend-based proxies through primary verified data — enabling progressive improvement without system replacement.
Domain
L1 — Spend Proxy
L2 — Activity Avg
L3 — Site Primary
L4 — Verified
L5 — Market-Traded
Emission Factor
EEIO spend-based factor ($/kg)
Industry avg (kg CO₂e/unit)
Site-specific primary measured
3rd-party verified, ISO-compliant
EAC-adjusted, registry-linked
Allocation
Mass fraction default
Economic value
Physical causality
PCR-mandated method
Contract-specified
System Boundary
Cradle-to-gate approx.
Defined gate-to-gate
Full cradle-to-gate mapped
Cradle-to-grave, LCA-complete
Dynamic — contract scope
Verification
Self-declared
Internal audit
3rd party limited assurance
Reasonable assurance (ISO)
Continuous digital audit
EAC Linkage
None
Book & claim intent
Book & claim active
Registry-retired, traced
Tokenized, on-chain settlement
PACT Transport
None
CSV batch upload
API endpoint declared
PACT v3 certified connector
Real-time streaming event
Active = supported in COMET v0.1 · Planned = v0.3 roadmap · Sources: GHG Protocol Product Standard · ISO 14067:2018 · WBCSD PACT v3.0
Visualization 04 — Namespace Architecture
Prefix Registry & URI Structure
Stable, dereferenceable URIs per layer. External namespaces imported under COMET control via owl:imports. Third-party contributions extend via sub-namespaces without breaking core.
Core namespace URIs never deleted, only deprecated with owl:deprecated true and a replacement pointer. Versioned sub-paths allow simultaneous v1/v2 support.
RULE 02 — Dereferenceable URIs
Every URI returns OWL Turtle on Accept: text/turtle and JSON-LD on Accept: application/ld+json. Human HTML docs served by default (content negotiation).
RULE 03 — Extension Isolation
Community extensions live under comet-ext:{org}. They may extend core classes but never modify them. Promotion from ext→core requires TSC vote.
RULE 04 — Alignment Mapping
PACT v3, GHG Protocol, and ISO 14067 concepts are imported, not redefined. COMET wraps them with owl:equivalentClass mappings maintained in a dedicated alignment module.
Visualization 05 — Data Flow & Transport Layer
COMET as the Semantic Backbone of PACT v3
PACT v3's transport protocol moves PCF data between supply chain actors. COMET provides the shared vocabulary so that data received from any PACT endpoint has a consistent, machine-interpretable meaning.
COMET does not replace standards — it provides the connective tissue. Each standard maps to one or more layers, and COMET expresses their key concepts in a shared, interoperable vocabulary.
COMET's market layer (L7) encodes the economic logic: products with lower-than-benchmark carbon intensity command premiums; those above face discounts or regulatory tariffs. The ontology makes this relationship machine-readable and audit-able.
Illustrative. CI = Carbon Intensity. Sources: CBAM Regulation (EU) 2023/956 · SteelZero market data · Rhodium Group hydrogen premium analysis
Visualization 08 — EAC Taxonomy
Environmental Attribute Certificate Class Hierarchy
All EAC types in COMET share a base class with common properties (serial number, registry, issuance date, retirement event). Subclasses specialize for energy, carbon removal, and material certification.
Visualization 09 — Governance
Three-Body Governance Model
COMET governance separates strategic direction (Steering Committee), technical decisions (Technical Steering Committee), and domain working groups. All decisions traceable via public GitHub issues and votes.
Body 01
Steering Committee (SC)
Strategic direction, funding allocation, and formal relationship with standards bodies (ISO, WBCSD, EU Commission). Meets quarterly. Decisions by supermajority (⅔).
Sector-specific extension development (Steel-WG, Hydrogen-WG, Cement-WG, EAC-WG). Open participation. Produce PRs targeting L5–L7 and domain ext: namespaces.
Any contributorIndustry expertsPlatform vendors
Open enrollment · Bi-weekly calls · RFC process
Decision Type
Decision Body
Threshold
Comment Period
Veto Right
New core class (L1–L4)
TSC
Simple majority
21 days
SC (strategic conflict)
URI deprecation / rename
TSC
Supermajority (⅔)
60 days
Any TSC member (delay only)
New domain extension (L5–L7)
DWG + TSC review
DWG consensus + TSC ACK
14 days
None on ext: namespace
New standard alignment module
TSC
Simple majority
30 days
SC (license conflict)
Governance charter amendment
SC
Supermajority (⅔)
90 days
None (SC is final)
Visualization 10 — Contribution Model
How COMET Evolves: The PR Workflow
Any organization or individual can propose changes. The pathway from idea to merged class is deterministic, public, and time-bounded. Layer tags route PRs to the correct review body automatically.
1
File a GitHub Issue with RFC label
Describe the gap, the proposed class/property, and which layer (L1–L7) it targets. Tag with standard (e.g., iso14067, pact-v3, cbam). Issue is auto-assigned to the relevant DWG.
2
DWG Discussion & Refinement (14-day minimum)
Working group comments, requests alignment mapping, checks for existing equivalent classes. A DWG chair signals ready-for-pr when consensus is reached.
3
Open Pull Request (OWL Turtle or YAML-LD)
Contributor submits PR with: class definition, rdfs:label, rdfs:comment, skos:example, alignment triples (owl:equivalentClass), and a SHACL shape for validation.
4
Automated CI Validation
GitHub Actions runs: OWL consistency check (HermiT reasoner), SHACL validation against test instances, namespace uniqueness check, URI dereference test.
5
TSC Review & Merge Decision
For L1–L4: TSC votes (21-day public comment). For L5–L7 and ext:: DWG chair merges with TSC ACK. All votes recorded in GitHub as labeled comments.
6
Release & Version Bump
Merged classes appear in next patch release (semver). Changelog auto-generated. PURL redirects updated. NPM / PyPI packages published with new ontology snapshot.
PR Labeling Convention
layer:L1–L7 Target layer
type:new-class Change type
std:iso14067 Standard reference
breaking Semver major bump
sector:steel Domain tag
status:rfc-open Review state
SLA Targets — Review Timelines
Ext: namespace PR
7 days
L5–L7 (DWG scope)
14 days
L4 PCF (TSC review)
21 days
L1–L3 core (public comment)
60 days
Breaking / deprecation
90 days
Visualization 11 — CADTrust & Verification Chain
From Measurement to Market-Tradeable Claim
COMET's verification layer (L6) maps the CADTrust carbon data model and third-party audit workflow. Each node in the chain is a typed COMET class with provenance properties — enabling downstream market actors to evaluate claim strength.
Visualization 12 — Core Class Inventory
COMET v0.1 — 48 Core Classes, 7 Modules
A snapshot of the v0.1 class inventory by module. Each cell represents one owl:Class. Green = stable, amber = under review, white = placeholder for community contribution.
L1 CORE
L2 EF
L3 SC
L4 PCF
L5 EAC
L6 VER
L7 MKT
Organization
EmissionFactor
SupplyChainLink
ProductCarbonFootprint
EAC
VerificationClaim
CarbonPremium
Site
LCIDataset
ActivityDataRecord
FunctionalUnit
EnergyAttrCert
AssuranceLevel
MarketBenchmark
Process
GWP100Value
SpendProxy
SystemBoundary
CarbonRemovalCert
AuditTrail
CBMADiscount
Material
DataProvenance
TransportEvent
AllocationMethod
MaterialStewardCert
CADTrustAttestation
PricingSignal
UnitOfMeasure
GeographyScope
PrimaryDataShare
LCIAResult
RetirementEvent
VerificationScope
EACSpotPrice
TimePeriod
TechRepLevel
BookAndClaim
PCRReference
CertRegistry
QualifiedVerifier
[ open slot ]
⬜ White = stable v0.1⬜ Amber = v0.2 candidate⬜ Green = recently merged⬜ Italic = open for contribution
Visualization 13 — PACT Transport Alignment
COMET Properties Mapped to PACT v3 Fields
PACT v3 defines a JSON schema for PCF exchange. COMET provides the OWL ontology layer that gives those fields semantic identity — enabling SPARQL queries, reasoning, and cross-platform data fusion.
The ontology evolves in annual major releases. Minor releases (patch) are continuous. Each milestone is tied to regulatory forcing functions or major standard releases.
COMET encodes the PACT v3 Data Quality Indicator (DQI) as a typed class with five ordinal properties. Every PCF result carries a DQI instance — enabling automated trust-scoring by downstream systems.
⬡
COVERAGE
What share of inputs have primary data vs. proxies. Score 1–3.
comet-sc:coverageDQI
⬡
TEMPORALITY
Age of emission factors and activity data relative to reporting year.
comet-sc:temporalityDQI
⬡
GEOGRAPHY
Specificity of emission factor geography to actual production location.
comet-sc:geographyDQI
⬡
TECHNOLOGY
Match between emission factor technology and actual process used.
comet-sc:technologyDQI
⬡
RELIABILITY
Data source reliability: measured, calculated, estimated, reported.
comet-sc:reliabilityDQI
DQI framework: WBCSD PACT v3.0 §3.3 · Frischknecht et al. (2005) pedigree matrix · ecoinvent Data Quality Guidelines
Visualization 16 — Module Architecture
COMET as a Modular Ontology — Load Only What You Need
Implementers can import the full ontology or just the modules relevant to their use case. Each module is an independent OWL file with explicit dependencies declared via owl:imports.
Required — Always load
comet-core
Organization, Site, Process, Material, UnitOfMeasure, TimePeriod. Foundation for all other modules. ~12 classes.
owl:imports: QUDT, prov-o
Module 2 — Common use
comet-pcf
Full ISO 14067 product carbon footprint model. FunctionalUnit, SystemBoundary, AllocationMethod, LCIAResult. ~18 classes.
owl:imports: comet-core, comet-ef
Module 3 — Supply chains
comet-supplychain
SupplyChainLink, ActivityDataRecord, DataQualityIndicator, TransportEvent, SpendProxy. PACT transport adapter. ~14 classes.
Steel-WG, Hydrogen-WG, Cement-WG, Aluminium-WG extensions. Sector-specific subclasses and properties under org namespaces.
PR-contributed · DWG governed
Visualization 17 — Sector Coverage
Hard-to-Abate Sector Ontology Readiness
Coverage depth varies by sector. Steel and chemicals anchor v0.1. Hydrogen, cement, and aluminium follow in v1.0. Each sector requires sector-specific PCR references and allocation rules mapped as COMET sub-classes.
Visualization 18 — Regulatory Architecture
How COMET Wires Into Compliance Mandates
Regulations require specific data fields. COMET maps each regulatory data requirement to a typed class — enabling automated compliance reporting without custom-coding per regulation.
Regulation 01 — Mandatory 2026
EU CBAM (Reg. 2023/956)
Requires embedded emissions per tonne for steel, cement, aluminium, fertilisers, hydrogen. COMET provides CBMADeclaration class with all required fields as typed properties. Importers generate CBAM XML from COMET instances.
Requires lifecycle GHG intensity (kg CO₂e / kg H₂) below 4 kg for any credit. Three pillars: additionality, deliverability, temporal matching for clean electricity. COMET HydrogenCI class encodes all three.
comet-ext:HydrogenCIcomet-eac:TemporalMatch
Regulation 03 — Mandatory 2025
EU CSRD / ESRS E1
Requires disclosure of Scope 1/2/3 emissions with value chain boundaries. ESRS E1-6 Scope 3 includes purchased goods — directly mapping to COMET's supply chain module and PCF results.
comet-sc:Scope3Cat1comet-pcf:SupplierPCF
Regulation 04 — EU Mandatory
EU Construction Products (EN 15804)
EPDs for construction products require 7 environmental impact categories (A1–A3 modules minimum). COMET's EN 15804 alignment module handles multi-impact declaration beyond carbon-only.
comet-pcf:EPDDeclarationcomet-pcf:ImpactCategory
Regulation 05 — Active Global
PACT v3 Pathfinder Network
PACT v3 mandates specific data fields and API endpoints for PCF exchange between value chain partners. COMET's PACT adapter module ensures semantic interoperability across all certified PACT systems.
comet-pcf:PACTv3Footprintcomet-sc:PACTEndpoint
Emerging — Watch list
US SEC Climate Disclosure / UK TCFD
SEC climate disclosure rules and UK TCFD mandate scenario analysis. COMET's market layer can express physical and transition risk scenarios using carbon price paths — planned for v1.1.
comet-mkt:ClimateRisk [planned]
Visualization 19 — Network Effects
The COMET Adoption Flywheel
Each new implementer increases the value of the shared vocabulary. More data flowing through COMET classes means better emission factor coverage, more verified PCFs, and stronger market price signals — compounding the case for adoption.
Visualization 20 — Economic Thesis
Carbon Becomes Currency: The COMET Value Proposition
COMET exists because carbon variance is becoming a financial variable. The ontology is the shared language that makes carbon-as-currency legible to procurement systems, capital markets, and regulatory authorities simultaneously.
Sources: BloombergNEF H₂ Economy Outlook · SteelFirst price indices · EU ETS carbon price (ICE) · CBAM Commission Impact Assessment · Rhodium Group
Why a Shared Ontology Unlocks Value
Without a shared vocabulary, carbon data is siloed, incomparable, and untradeable. Procurement systems cannot compare a PCF from CarbonSig with one from a competitor platform. Verifiers cannot automate checks against ISO 14067. Market pricing cannot be algorithmic.
COMET resolves this by providing a neutral, openly governed common layer — analogous to how TCP/IP enabled the internet without any single actor owning it.
The Three Markets COMET Enables
⬡
Compliance
CBAM, CSRD, 45V reporting with machine-verified data