Ontology details

Applicability Conditions

Each compliance record type declares when it is required using prism:ApplicabilityCondition. An obligation may have multiple conditions (disjunction — any one is sufficient to trigger it).

Property	Description	Example values
`prism:forActor`	Actor role	`eu-aiact:AIProvider`, `eu-aiact:AIDeployer`
`prism:forRiskLevel`	Risk classification	`eu-aiact:RiskLevelHigh`, `eu-aiact:RiskLevelHigh-A6-2`
`prism:atLifecycleStage`	ISO 22989 lifecycle stage	`ai:DesignStage`, `ai:OperationStage`
`prism:forSector`	Annex III regulatory sector	`eu-aiact:EmploymentSector`, `eu-aiact:JusticeSector`
`prism:forSystemType`	AI system type classification	`eu-aiact:BiometricCategorisationSystem`, `prism:ChatBot`
`prism:forEntityType`	Entity type	`eu-aiact:PublicSector`

Regulatory Processes and Governance Activities

In addition to lifecycle stages, PRISM defines two types of compliance-related concepts that are not lifecycle stages themselves:

Concept	Type	Lifecycle stages
`prism:ConformityAssessment`	Regulatory Process	`ai:VerificationStage`, `ai:ValidationStage`
`prism:SupplyChainVerification`	Regulatory Process	`ai:DeploymentStage`
`prism:MarketEntry`	Regulatory Process	`ai:DeploymentStage`
`prism:InternalProcesses`	Governance Activity	Ongoing (all stages)
`prism:RiskAssessment`	Governance Activity	Ongoing (may recur)

Compliance Record Types

Each record type is a subclass of prism:ComplianceRecord and declares its own applicability conditions via prism:hasApplicabilityCondition. Where a matching eu-aiact: concept exists the record links to it via prism:evidencesObligation; where DPV has not yet modelled the obligation, the article is noted via prism:pendingArticle. Full applicability conditions for each record type are available on its individual term page.

Economic Sector Coverage

PRISM distinguishes between two uses of "sector":

Industry (dpv:hasSector + NACE codes) — answers "where does this system operate?" and shapes record content: how obligations are fulfilled in that business context.

Annex III sector (prism:forSector + eu-aiact sectors) — answers "which regulatory category applies?" and determines whether an obligation triggers at all.

For example, a credit scoring system might have dpv:hasSector nace:K (financial services industry) — this shapes the content of its risk management records. Separately, if it falls under eu-aiact:EmploymentSector (Annex III), that triggers the FRIA obligation via prism:forSector.

`prism:EconomicSector`

PRISM defines a prism:EconomicSector class (subclass of dpv:Sector) with six instances covering the industries most relevant to EU AI Act compliance. Two properties work together to describe an AI system's industry context:

dpv:hasSector — identifies where the system operates, using a prism:EconomicSector instance
dpv:hasPurpose — identifies why data is processed, using terms from the linked DPV sector extension

ex:MyCreditScorer
    dpv:hasSector   prism:Finance ;
    dpv:hasPurpose  sector-finance:CreditChecking .

Supported Economic Sectors

PRISM term	Label	NACE	DPV sector extension
`prism:Finance`	Financial and Insurance Activities	K	`sector-finance:`
`prism:Health`	Human Health and Social Work Activities	Q	`sector-health:`
`prism:Education`	Education	P	`sector-education:`
`prism:Infrastructure`	Infrastructure	D, E, F, H	`sector-infra:`
`prism:LawEnforcement`	Law Enforcement and Justice	O (O84.23)	`sector-law:`
`prism:PublicServices`	Public Administration and Defence	O	`sector-publicservices:` ★

★ sector-publicservices is a draft DPV module. Use the versioned URI https://w3id.org/dpv/2.3/sector/publicservices until the non-versioned redirect stabilises.

Scope Limitation

DPV 2.x sector extensions provide dpv:Purpose subclasses only — they describe why data is processed within a sector, not sector identity itself. prism:EconomicSector instances fill this gap by giving each sector a stable, resolvable IRI for use with dpv:hasSector.

For AI systems operating in sectors not listed above (e.g. manufacturing, retail, agriculture), use a generic dpv:Purpose term with dpv:hasPurpose and omit dpv:hasSector, or extend PRISM with additional prism:EconomicSector instances.