Standards and semantic requirements
Relationship to existing standards
UCEM specifies bounded economic meaning and source documentation requirements. Those requirements can be expressed through an existing standard's structures and metadata; another record format is not a prerequisite.
Responsibilities in publication processing
- Publisher materialThe actual statistical release or inspected research publication, with its original expression and edition.
- Standards and source definitionsData structures, publisher concepts, classifications, units, research descriptions and provenance.
- Shared economic requirementsUCEM's bounded clauses require material construction, source provenance, unknowns and limits on a requested use to remain explicit.
- Application checksSoftware applies a named, scoped check to the selected sources. Structural validity and an economic interpretation are different judgments.
- Human or model explanationThe response distinguishes source documentation, application assessments and generated text. Model outputs do not define the specification or certify an interpretation.
Existing standards already define substantial semantics. The additional question is whether a reusable economic profile improves consistency or reduces repeated mapping work. Equivalent rules in an SDMX application can produce the same judgments.
Applicable standards
| Foundation | Existing responsibility | Economic profile responsibility |
|---|---|---|
| SDMX | Statistical concepts, structures, observations and metadata. | Bind the required construction, sources and unresolved states to an explicit profile; retain the standard's own semantics. |
| DDI | Descriptions of research data, variables and research processes. | Reuse applicable descriptions while retaining each reported finding's estimator, comparison and source scope. |
| W3C PROV | Models for entities, activities and agents involved in producing information. | Keep source capture, interpretation and derivation roles explicit; a provenance link alone does not establish correctness. |
| UCUM | Unit expressions with defined composition and semantic comparison. | Reuse applicable units. Economic population, price basis and estimator distinctions require their own explicit definitions. |
| XBRL | Business facts qualified by concepts, entities, periods, units and other dimensions. | Treat existing fact/context and validation machinery as prior art, and assess applicable reuse before adding structure. |
The table can scroll sideways. Focus it and use the Left and Right arrow keys. These are reuse directions, not demonstrated adapters or interoperability certifications.
UCUM-informed semantic-profile research
UCUM defines unit symbols and composition rules; fully conforming implementations compare expressions by meaning. A UCUM-inspired economic profile would need equally explicit definitions and rules for its chosen scope, including when meaning remains unresolved. It would not make every economic construction a universally convertible unit.
In the retained NBER example, -0.210 is reported as an OLS coefficient divided by a reference mean. A probability-difference interpretation requires support for that construction, which the inspected passage does not supply. A shared profile could define this distinction and a check, with its source bindings, independently of its SDMX representation.
This is a research direction. Accepted bounded clauses already document selected obligations. No general economic code grammar, computable equivalence engine or advantage over a competent existing-standard profile has been established.
Inspect the coefficient's actual source constructionData Commons reference study
Data Commons already has measurement qualifiers, provenance and agent-oriented discovery workflows. Its schema and software serve as conceptual and technical references. Economic data is acquired directly from authoritative publishers; Data Commons data and economic mappings do not supply these records.
The reference study distinguishes candidate discovery, meaning qualification and source selection. A nearest semantic match is still a candidate. Source dates, units and methods must survive the final consumer view.
Read the inspected Data Commons researcher workflowImplementation scope
UCEM 1.0 includes the model and binding requirements and a bounded SDMX binding. The reference examples demonstrate source preservation and resolution within their declared layouts. Broader interoperability requires separate implementation assessment.
The public library supports automated publication analysis. Each record describes its generation method and checks. Those checks have a separate scope from specification conformance.