Inferal Advertising Budget Ontology

The Advertising Budget Ontology separates a spending allowance into its amount, recurrence, pacing, scope, sharing behavior, and effective window. It also distinguishes a budget that directs delivery from a spend cap that only limits it.

Prefix	Namespace IRI
`abg`	`https://ontology.inferal.com/modules/advertising-budget/`

Prefix

Namespace IRI

abg

https://ontology.inferal.com/modules/advertising-budget/

Scope

This module covers reified budgets, budget periods, delivery methods, budget scopes, spend caps, and the effective intervals over which allowances apply.

Actual spend is an advertising metric observation. Auction bidding, forecasts, recommendations, and currency conversion are outside this module. Advertising entities are referenced through a scope but are not defined here.

Competency Questions

Which budgets may be compared or summed?

Which budgets cover several entities, making per-entity spend attribution invalid?

Which budget pairs share a currency but use different periods?

Which budgets use accelerated rather than even pacing?

Which entities are constrained by a spend cap rather than directed by a budget?

Conceptual Model

Allowance as a resource

A numeric amount alone does not identify an allowance. A budget combines a monetary amount with a period, delivery method, and scope. Consumers MUST compare those qualifiers before treating two budget figures as equivalent.

Budget and cap

A budget is a target toward which delivery is paced. A spend cap is a ceiling that delivery must not exceed. Consumers MUST NOT interpret a cap as evidence of intended spend, and a cap does not carry a delivery method.

Shared scope

A scope can cover one or many advertising entities. When an allowance is shared, the amount applies to the pool. Consumers MUST NOT allocate that amount to one covered entity without separate attribution evidence.

Term Reference

Every term in this section is exported for cross-reference. Definitions state the term's meaning; the relations column summarizes declared RDFS and SKOS links. Closed-world cardinalities are specified separately in Validation.

Classes

Term	Kind	Normative meaning	Relations
`abg:Budget`	Class	A planned spending allowance: an amount of money, the period it applies over, how it is paced within that period, and the scope of entities it covers.	No local domain or range restriction.
`abg:BudgetPeriod`	Class	The recurrence over which a budget amount is allowed to be spent, such as each day or once over the whole flight.	Subclass of: `skos:Concept`
`abg:BudgetScope`	Class	The set of advertising entities a budget or spend cap applies to, and whether that set is shared.	No local domain or range restriction.
`abg:DeliveryMethod`	Class	How spending is paced within the budget period: evenly across it, or as quickly as inventory allows.	Subclass of: `skos:Concept`
`abg:SpendCap`	Class	A ceiling on spending that constrains delivery without directing it.	No local domain or range restriction.

Properties

Term	Kind	Normative meaning	Relations
`abg:appliesToScope`	Property	The scope of entities the budget covers.	Domain: `abg:Budget`; Range: `abg:BudgetScope`
`abg:budgetAmount`	Property	The allowance a budget permits, as a monetary amount reused from the advertising measurement vocabulary so budgets and spend are denominated in the same terms.	Domain: `abg:Budget`; Range: `adm:MonetaryAmount`
`abg:budgetDeliveryMethod`	Property	How the budget is paced within its period.	Domain: `abg:Budget`; Range: `abg:DeliveryMethod`
`abg:budgetPeriod`	Property	The recurrence the budget amount applies over.	Domain: `abg:Budget`; Range: `abg:BudgetPeriod`
`abg:capAmount`	Property	The ceiling a spend cap imposes, as a monetary amount reused from the advertising measurement vocabulary.	Domain: `abg:SpendCap`; Range: `adm:MonetaryAmount`
`abg:capPeriod`	Property	The recurrence a spend cap's ceiling applies over.	Domain: `abg:SpendCap`; Range: `abg:BudgetPeriod`
`abg:constrainsScope`	Property	The scope of entities a spend cap applies to.	Domain: `abg:SpendCap`; Range: `abg:BudgetScope`
`abg:coveredEntityCount`	Property	How many entities a scope covers, for providers that report the count without enumerating the entities.	Domain: `abg:BudgetScope`; Range: `xsd:integer`
`abg:coversEntity`	Property	An advertising entity that a scope covers. A scope covering more than one entity is shared, and spend under it cannot be attributed to any single covered entity.	Domain: `abg:BudgetScope`; Range: `rdfs:Resource`
`abg:effectiveWindow`	Property	The interval over which a budget or cap is in force, for a flight with a defined start and end. Open above when the allowance is standing.	Domain: `abg:Budget`; Range: `rng:Range`
`abg:sharedAcrossEntities`	Property	True when a scope's allowance is pooled across the entities it covers rather than divided among them. Asserted by producers even where it can be derived from the covered entities, because some providers report sharing without enumerating what is shared.	Domain: `abg:BudgetScope`; Range: `xsd:boolean`

Controlled concepts

Term	Kind	Normative meaning	Relations
`abg:acceleratedDelivery`	Concept	Spending proceeds as quickly as inventory allows and may exhaust the budget before the period ends.	Scheme: `abg:DeliveryMethodScheme`
`abg:customPeriod`	Concept	The amount is allowed once across a provider-defined span that is neither a day nor the entity's whole flight. The span itself is carried by the effective window rather than by this concept.	Scheme: `abg:BudgetPeriodScheme`
`abg:dailyPeriod`	Concept	The amount is allowed each day and resets at the provider's day boundary.	Scheme: `abg:BudgetPeriodScheme`
`abg:lifetimePeriod`	Concept	The amount is allowed once across the entire flight and does not reset.	Scheme: `abg:BudgetPeriodScheme`
`abg:standardDelivery`	Concept	Spending is paced evenly across the budget period.	Scheme: `abg:DeliveryMethodScheme`

Concept schemes

Term	Kind	Normative meaning	Relations
`abg:BudgetPeriodScheme`	Concept scheme	Controlled vocabulary of budget recurrences.	No local domain or range restriction.
`abg:DeliveryMethodScheme`	Concept scheme	Controlled vocabulary of pacing behaviours.	No local domain or range restriction.

Validation

The module's SHACL constraints provide the closed-world conformance profile. The following requirements summarize the constraints that affect ordinary data producers.

A budget MUST have exactly one monetary amount, period, delivery method, and scope. It MAY have one effective window.

A spend cap MUST have exactly one monetary amount, period, and scope, and MUST NOT have a budget delivery method.

A budget scope MAY enumerate covered entity IRIs and MAY state one covered-entity count and one shared flag.

Monetary amounts use the advertising measurement vocabulary, and effective windows use the shared range vocabulary.

@prefix abg: <https://ontology.inferal.com/modules/advertising-budget/> . @prefix adm: <https://ontology.inferal.com/modules/advertising-measurement/> . @prefix ex: <https://example.com/advertising-budget/> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . ex:scope a abg:BudgetScope ; abg:coversEntity ex:ad-group-a, ex:ad-group-b ; abg:sharedAcrossEntities true . ex:daily-budget a abg:Budget ; abg:budgetAmount ex:daily-amount ; abg:budgetPeriod abg:dailyPeriod ; abg:budgetDeliveryMethod abg:standardDelivery ; abg:appliesToScope ex:scope . ex:daily-amount a adm:MonetaryAmount ; adm:amountValue "500.00"^^xsd:decimal ; adm:currencyCode "USD" . ex:lifetime-cap a abg:SpendCap ; abg:capAmount ex:cap-amount ; abg:capPeriod abg:lifetimePeriod ; abg:constrainsScope ex:scope .

Extension and Interoperability

Controlled vocabularies use SKOS so provider profiles MAY add narrower or matched concepts without replacing the shared classes. Extensions MUST preserve the meanings and constraints of terms they reuse. A mapping MUST NOT assert equivalence merely because two provider fields have similar labels.

Namespace