CORA
Industry coordination layer in formation

Common Ontology for Real Assets

Making real assets standards interpretable by machines and interoperable by meaning.

Real assets data has always required reconciliation. What has changed is that interpretation can no longer remain manual.

CORA is a vendor-neutral coordination layer for real assets data standards. It provides the shared semantic infrastructure that allows existing standards, systems, and institutional workflows to preserve meaning across asset classes, ownership structures, capital stacks, geographies, and time.

CORA does not replace existing standards. It gives them a common frame.

Send Inquiry
  • Vendor-neutral
  • Global by design
  • Publicly available
  • Openly licensed
Overview

What CORA Is

The real assets industry does not lack data standards. It lacks a way to interpret them together.

Over the past two decades, multiple credible standards have emerged for specific audiences, workflows, and reporting obligations. CORA is being formed to connect that work, not replace it.

CORA is an ontology. It defines shared classes, relationships, identifiers, and provenance for real estate and infrastructure data across equity, debt, infrastructure, and operating contexts.

Horizontal tools — analytics, BI, AI — move data without knowing what it means. CORA supplies the real assets meaning they need to preserve.

CORA Is Designed As

  • A common ontology for real estate and infrastructure data
  • A coordination layer above existing data exchange standards
  • Shared classes, relationships, identifiers, and provenance for the domain
  • A foundation for agent-readable real assets data
  • Global by design, with extension points for local market and regulatory variation
  • Openly governed, openly licensed, and publicly available

CORA Is Not

  • A new transport protocol
  • A replacement for existing standards
  • A vendor product
  • A compliance mandate
  • A closed membership initiative
  • A standard limited to one asset class, geography, or layer of the capital stack
What the coordination layer adds

Two structural contributions

Existing standards bodies already do the foundational work of defining, maintaining, and distributing their own standards. CORA is not designed to duplicate that work.

Its role is narrower and connective: to maintain cross-standard mappings and a longitudinal record of how real assets definitions evolve across standards, versions, and market contexts.

Cross-standard mapping

A neutral record of how concepts correspond across multiple standards, schemas, and data models. Individual standards bodies maintain authority over their own work. CORA provides a shared mapping layer so those meanings can be interpreted together.

CORA maps between standards. It does not host, govern, or supersede them.

See the mapping fragment →

Longitudinal record of standards evolution

A public record of how real assets standards evolve over time, including where definitions converge, diverge, or change across versions.

Individual standards bodies track their own evolution. CORA provides the cross-standard view.

See the drift fragment →
v0.1 Scope

Scope of v0.1

Real assets data does not break in one place. It breaks across three recurring dimensions: the capital stack, the asset class, and the jurisdiction.

CORA v0.1 is designed to model those intersections. Data aggregates up from assets to portfolios, funds, and allocators. It disaggregates back down for valuation, operations, risk, reporting, and audit. At every handoff, meaning changes unless it is explicitly modeled.

v0.1 coverage matrixCORA v0.1 covers four capital stack layers (Limited Partner, General Partner, Asset Manager, Owner / Operator) across four asset class categories (Multifamily, Commercial, Debt, Infrastructure). All sixteen cells are within scope.DIFFERENT CONVENTIONS ACROSS COLUMNSMultifamilyCommercialDebtInfrastructureLimited PartnerGeneral PartnerAsset ManagerOwner / OperatorAGGREGATEDISAGGREGATEEACH CELL ALSO VARIES ACROSS GEOGRAPHIES
CORA v0.1 models the intersections of capital stack and asset class, with geography as a third dimension. Data aggregates up; disaggregates back down; conventions differ across columns; each cell also varies across jurisdiction.

The problem compounds because the planes intersect.

A global investor does not manage geography, asset class, and capital structure as separate planes. A vertically integrated real estate firm does not either. The same semantic friction appears inside the organization, across regions, business lines, acquired entities, and operating systems.

CORA v0.1 begins where the industry needs common ground: a global foundation, stable enough to coordinate across contexts and extensible enough to support sector and jurisdictional variation over time.

Asset classes

Real estate, equity

Multifamily, office, industrial and logistics, retail, hospitality, healthcare and senior housing, student housing, self-storage, and mixed-use. Direct property and portfolio structures, fund-level entities, ownership hierarchies, lease and operational data, valuation, transactions.

Real estate, debt

Mortgages, CMBS, mezzanine and preferred equity, construction lending, and other loan-level instruments. Servicer and lender entities. Securitization structures.

Infrastructure

Data centers, renewable energy assets, transport infrastructure, with defined extension points for additional sectors.

Capital stack

CORA spans the full real assets capital stack: capital allocators, fund sponsors, asset managers, owner-operators, property managers, fund administrators, lenders, servicers, valuation and forecasting providers, data providers, and technology platforms. The ontology models the entities, relationships, and data flows required to consolidate information from property-level operations up to portfolio, fund, and investor reporting, and to disaggregate it back down for analysis, operations, risk, and audit.

Geographic scope

CORA is global by design. Real assets data changes meaning across jurisdictions: legal entity structures, lease conventions, valuation standards, regulatory regimes, currencies, and reporting obligations all vary by market. CORA provides extension points for regional and jurisdiction-specific requirements across North America, EMEA, APAC, and Latin America. Specific mappings to regulatory and industry frameworks, including AIFMD, SEC, INREV, NCREIF, and regional equivalents, will be developed through the Standards Mapping working group.

Subsequent versions will extend coverage through public review and transparent governance.

Status

Currently in Formation

The formation period is focused on five workstreams: drafting the v0.1 specification, establishing governance principles, mapping CORA to existing real assets standards, defining the longitudinal record of standards evolution, and preparing public review materials.

v0.1 specification
The initial specification covers core ontology classes, relationship definitions, identifier patterns, provenance modeling, reference examples, and validation tooling.
Governance framework
The governance framework will define how CORA is reviewed, maintained, extended, and approved over time, including committee structure, working groups, public review, and version control.
Standards mapping
Draft mappings are being prepared between CORA and existing real assets data standards, in coordination with relevant standards bodies.
Longitudinal record of standards evolution
Establishing the methodology and tooling for tracking how real assets data standards evolve over time, and how their definitions diverge from one another. CORA produces a public, neutral record of structural, semantic, and coverage drift across versions and across standards - a record no upstream body can maintain alone.
Public review materials
Preparing the v0.1 release package - specification, mappings, governance materials, and supporting documentation - for open review and comment on publication.
Specification Repository
The repository is public. The README, governance framework, and supporting documentation are available now. The v0.1 specification, mappings, and reference examples will be committed as they are prepared for public review.
Anticipated v0.1 Public Release
Q2 2026
The v0.1 specification, initial mappings, governance materials, and public review process will be released together. The specification will then enter a public review and comment period.
Perspective

Why Now

Reports tolerated semantic drift because humans supplied the missing interpretation. Agents do not. They read data directly and reason from it, which is why the next generation of real assets infrastructure cannot rely on human judgment as the integration layer.

Perspective Detail →

Inquiry

CORA Inquiry

Use this form to ask a question, register interest, or share relevant institutional, technical, or standards context.

Public review materials and contribution guidelines will be released with v0.1.

The inquiry form is intended for questions, relevant context, and public review interest. Formal contribution guidelines will be released with v0.1.