← Back to catalogue
Published

Report definition and release instance

EM-DAT-06 · em-dat-06

Report specification, parameters, run, publication and artifact. A dashboard is a set of permitted projections or a view of an explicitly modeled aggregate.

Enterprise profiles Enterprise subject EnterpriseDAT

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 5 findings · 10 questions

Definition What the report or dashboard is designed to show.

Report and dashboard definition

Specification, parameters and permitted projections.

Report definition

The versioned specification and its parameters.

  1. Which definition version and parameters does the report use?
  2. Which data sources and metrics does it draw on?

Permitted projections

What a dashboard may combine, under which rights.

  1. Which projections does the dashboard permit, and over which aggregate?
  2. Were rights checked before HR and financial data were combined?
Runs and releases Concrete executions and what was published.

Report run

A run pinned to a definition and an input snapshot.

Run record

Definition version, input snapshot and output artifact.

  1. Which definition version and input snapshot did the run use?
  2. Can the released artifact be reproduced from them?

Publication

Releases, corrections and disclosure control.

Release and correction

Published releases and later corrected releases.

  1. Who received the release, and when?
  2. Was a correction issued as a new release alongside the original?

Disclosure control

Rules that keep sensitive slices hidden in aggregates.

  1. Which disclosure policy applies to aggregated values?
  2. Could small groups in the aggregate reveal individuals?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseDAT
Industry
Cross-industry
Tags
EM-DAT-06W1subjectReportDefinitionReportRunReportArtifactPublicationRecordDashboardDefinition

What it is Filled

Report specification, parameters, run, publication and artifact. A dashboard is a set of permitted projections or a view of an explicitly modeled aggregate.

Why it exists Filled

Report specification, parameters, run, publication and artifact. A dashboard is a set of permitted projections or a view of an explicitly modeled aggregate.

Distinguishing features Filled

  • A report run pins the definition version and the input snapshot it used.
  • A corrected release is published as a new release and the original stays on record.
  • Aggregation does not remove the disclosure rules of the underlying data.
  • Distinct from metrics and analytical studies, which define values and justify conclusions.

What robots and AI may and may not do Filled

Must not

  • Combine HR and financial objects in one projection without a rights check.
  • Overwrite a published report with a corrected version.
  • Release aggregates that reveal individuals in small groups.
  • Send a report to recipients outside its distribution list.

Only with a human decision

  • Publishing a report outside the organisation.
  • Granting access to a dashboard that combines sensitive data.

May

  • Produce report runs and record definition version and input snapshot.
  • Issue a corrected release with a note on what changed.
  • Check aggregates for small cells before release.

Moral aspects Filled

  • Aggregates can still expose personal data about employees or customers.
  • Readers depend on knowing which version of a figure they acted on.

Who is affected

  • Report readers
  • Employees and customers in the data
  • Report owners

Owners Filled

Steward

The data owner or head of analytics who answers for data assets and their fitness for use.

Master systems

  • Data catalogue
  • Data warehouse
  • BI platform
  • Data orchestrator

Links to other meta-models Filled

neighbor

  • EM-DAT-05
  • EM-DAT-07

references

  • WM-REC-002 - conceptual-candidate
  • WM-REC-001 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by report definition identifier and version, and each release by run identifier and publication date.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A report release names a definition version, an input snapshot and a distribution.
  • Often confused with the dashboard view or with the underlying dataset.

Capabilities and actions required Filled

  • Past releases can be explained and reproduced.
  • Corrections are visible to readers next to the original.

Hazards and failure modes required Filled

  • Overwritten releases that hide what readers saw.
  • Disclosure of individuals through fine-grained aggregates.
  • Unchecked combination of sensitive domains in one view.

Standards and interfaces required Filled

  • W3C RDF Data Cube Vocabulary for published statistical data.
  • XBRL from XBRL International for business reporting.
  • W3C PROV-O for provenance of report runs.

Context of use required Filled

  • Used for management, financial and regulatory reporting and shared dashboards.
  • Regulated reports must remain reproducible for audit.

Sources Filled

  1. W3C DCAT: dataset, distribution, catalog
  2. W3C PROV and Data Cube: provenance and observation
  3. SDMX and BI/data catalog practice: indicators, breakdowns, definitions and releases
  4. W3C PROV-O: The PROV Ontology - Checked live (HTTP 200) on 2026-10-07.
  5. W3C The RDF Data Cube Vocabulary - Checked live (HTTP 200) on 2026-10-07.
  6. SDMX: Statistical Data and Metadata eXchange - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • What makes a release reproducible?
  • How to account for corrections to an already published report?
  • Which rights apply to aggregated values?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-dat-06/brief.json, ver-cy/world-models/card-supplements/em-dat-06.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.