This module interprets retained Google, Microsoft and Meta reporting captures with independent calendar, attribution and recency standing. A report context binds a raw artifact and native row to declared API, method, account, request time, zone and report settings. A current account setting alone cannot supply historical applicability to a captured report.
This is the unofficial 0.1.0 module specification. Source review and executable correctness are separate standings. Full generation, runtime and publication verification are pending configured GitHub CI; this draft supplies no release, native write or client-adoption qualification.
This module interprets retained Google, Microsoft and Meta reporting captures with independent calendar, attribution and recency standing. A report context binds a raw artifact and native row to declared API, method, account, request time, zone and report settings. A current account setting alone cannot supply historical applicability to a captured report.
Agents can inspect the selected retained evidence, ask for missing scope or review, and keep unresolved answers visible. A successful inspection remains separate from permission to act on a live account.
https://ontology.inferal.com/modules/advertising-reporting-context/
The prefix arc names the existing vocabulary. Term identity and the original RDF types remain stable. Shared advertising and commerce concepts supply scope; captured provider terms retain their provider-specific meaning.
NativeCapture retains raw payload and digest. ProjectionCandidate preserves unresolved metric evidence instead of inventing a UTC observation. CalendarBoundaryRequest selects local boundaries and retained timezone rules; CalendarResolution resolves both independently. QualifiedMetricObservation represents resolved reporting instants while keeping attribution and evidence-origin standings separate. DeliveryEvidence includes empty and partial captures in a declared retained series.
| Evidence | What the consumer can conclude |
|---|---|
| Retained source | The selected bytes and represented claims remain inspectable. |
| Scoped interpretation | The named contract supplies a result with its own qualification and coverage. |
| Current action authority | Live permission, native applicability and client adoption require separately qualified evidence. |
Native rows are expanded and projected in isolation with their retained published contexts. Source-artifact digest, capture ordinal, account and row scope must agree with declarations. The native inclusive stop date becomes an exclusive local end boundary through retained calendar mathematics. Gaps, overlaps, reversed intervals and unsupported dates remain unresolved. Calendar resolution alone cannot qualify attributed comparisons.
RDF permits incomplete descriptions. A conforming execution profile must enforce its declared closed-world input and output constraints. Unknown or conflicting business evidence must keep its explicit standing and cannot be converted into a favorable value.
The requested attribution report-time mode stays separate from the effective mode and its timing support. Requested impression, conversion or mixed behavior cannot be presumed honored. Matching basis labels cannot replace applicable native settings content. Attribution comparisons require separately qualified scope and settings. A newer declared empty, partial or missing capture remains part of recency assessment; selecting an older successful row cannot prove current provider freshness. A read-only report supplies no write permission.
Validation establishes conformance to a selected profile. Retained scope, reported evidence and operational success keep their separate meanings. Runtime and generation evidence for this source repair remain pending GitHub CI.
The partial context declares a native row and CallerDeclaredReportContext. It deliberately omits artifact, account, zone and attribution support, so it cannot qualify a reporting window or observation. A conforming context must supply the required scoped evidence instead of filling the omissions from a current account setting.
Inspect the declared roles and independent standings before using this evidence. Omitted source data or an unresolved qualification must remain visible. This example does not attest a live provider request or complete merchant history.
Classes, properties and existing controlled evidence values retain their authored labels and definitions. Listing a controlled value here does not change its RDF type or grant execution authority.
arc:CalendarBoundaryRequest — Local calendar boundary requestarc:CalendarResolution — Retained calendar resolutionarc:DeliveryEvidence — Retained delivery evidencearc:Diagnostic — Reporting qualification diagnosticarc:NativeCapture — Retained native capturearc:ProjectionCandidate — Reporting projection candidatearc:QualifiedMetricObservation — Qualified reporting observationarc:ReportContext — Declared report contextarc:accountScope — accountScopearc:apiVersion — apiVersionarc:basis — basisarc:calendarDigest — calendarDigestarc:calendarRelease — calendarReleasearc:candidate — candidatearc:capture — capturearc:captureOrdinal — captureOrdinalarc:capturedAt — capturedAtarc:closedStanding — closedStandingarc:contextDigest — contextDigestarc:contextStanding — contextStandingarc:currency — currencyarc:defaultGraph — defaultGrapharc:defaultReportingService — defaultReportingServicearc:deliverySeries — deliverySeriesarc:effectiveActionReportTime — effectiveActionReportTimearc:end — endarc:evidenceOrigin — evidenceOriginarc:forNativeReport — forNativeReportarc:freshnessStanding — freshnessStandingarc:interpretationDigest — interpretationDigestarc:leftCaptureOrdinal — leftCaptureOrdinalarc:leftSource — leftSourcearc:legacyObservation — legacyObservationarc:legacyReportingStanding — legacyReportingStandingarc:magnitude — magnitudearc:method — methodarc:metricKind — metricKindarc:nativePayload — nativePayloadarc:nativeSettingsLexical — nativeSettingsLexicalarc:nativeSource — nativeSourcearc:nativeStart — nativeStartarc:nativeStop — nativeStoparc:observationGrain — observationGrainarc:observationSubject — observationSubjectarc:processorPath — processorPatharc:provider — providerarc:qualifiedObservation — qualifiedObservationarc:reader — readerarc:reason — reasonarc:reportingSuccessor — reportingSuccessorarc:requestTime — requestTimearc:requestedActionReportTime — requestedActionReportTimearc:resolution — resolutionarc:rightCaptureOrdinal — rightCaptureOrdinalarc:rightSource — rightSourcearc:routeStanding — routeStandingarc:settingsApplicability — settingsApplicabilityarc:settingsStanding — settingsStandingarc:sourceArtifactSha256 — sourceArtifactSha256arc:start — startarc:timingStanding — timingStandingarc:timingSupport — timingSupportarc:windowStanding — windowStandingarc:zone — zonearc:zoneApplicability — zoneApplicabilityarc:zoneName — zoneNamearc:zoneStanding — zoneStanding