Skip to main content

DRR namespace structure

DRR namespace structure​

Digital Regulatory Reporting is layered and modular by design. The DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. model follows the CDMCDM Common Domain Model. A standardised, machine-readable and machine-executable blueprint for how financial products are traded and managed across the transaction lifecycle. It is represented as a domain model and distributed in open source.'s organising principles into namespaces.

  • Base: The Base namespace leverages elements defined in the CDMCDM Common Domain Model. A standardised, machine-readable and machine-executable blueprint for how financial products are traded and managed across the transaction lifecycle. It is represented as a domain model and distributed in open source.. It contains the core, reusable building blocks that underpin the entire DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. model.

  • Enrichment: The Enrichment namespace defines types, functions and rules that enrich DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. objects with the information required for regulatory reporting. Within this namespace, a trade can be enriched from a ReportableEvent into a TransactionReportInstruction, for example, adding elements such as ReportableInfomation and ReportingSide.

  • Ingest: The Ingest namespace contains the functional mappings for FpMLFpML Financial Products Markup Language Record Keeping trade messages. This namespace details the elements required to ingest a FpML NonPublicExecutionReport message and transform it directly into a ReportableEvent.

  • Standards: The Standards namespace defines and codifies the Critical Data Elements or CDEsCDE Critical Data Element of regulatory reporting. Critical Data Elements are standardised, well-defined data fields that are used consistently across regulatory reporting frameworks. They ensure that different firms and regulators interoperate and report the same information the same way. CDEsCDE Critical Data Element are the building blocks for regulatory reports.

  • Regulation: The Regulation namespace of DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. contains the reporting-specific logic, where regulatory text is digitised and translated into code. Reporting rules and their interperations include references to the relevant regulatory text and where applicable, the outcomes of the working group discussions. Within this namespace, sub-namespaces are organised by regulation name, along with a Common namespace. This houses shared rules and regulatory logic that apply across multiple regulatory regimes to ensure consistency and reuse throughout the DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. framework.

  • Projection: The Projection namespace contains elements necessary to transform DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. report output into a report file formatted for submission to trade repositories and regulators. This layer of the DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. structure ensures the report is structured, compliant and ready for regulatory consumption.

Workflow summary​

This overview of the DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. structure explains how the workflow is organised:

  • Projections build on Regulations

  • Which in turn draw on Common rules

  • Which call on CDEsCDE Critical Data Element

  • Which leverage the DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. Base namespace.

This hierarchical approach ensures that DRRDRR Digital Regulatory Reporting. An industry‑developed, machine‑executable interpretation of regulatory rules that produces consistent, transparent and fully traceable reporting outputs from standardised CDM data. is consistent, traceable and reusable across regulatory regimes.