Sector Code
Objective
Capture and validate the sector code element within the Regulatory & Cross-Sector Metadata layer.
UAIF requirement
The incident record should implement the canonical sector_code field using the defined UAIF data type, validation constraints, and conditional rules.
Business impact
Provides sector and jurisdiction routing context without turning metadata or a trigger flag into a legal determination.
Validation approach
Validate sector_code for required in the Core profile, controlled vocabulary membership. Then review semantic consistency against the source incident evidence and the selected conformance profile.
Expected evidence
Retain the source record or analyst input for sector_code, schema-validation output, transformation history, selected profile, schema version and reviewer rationale where judgement is involved.
Mapping and source
UAIF Schema Specification; UAIF Technical Specification; JSON pointer /properties/sector_code.
Implementation guidance
Populate sector_code from an identified source or documented analyst decision. Enforce the schema constraints at record creation and update, preserve the original value and provenance, and surface validation failures without silently coercing data.
Assessment considerations
Sample records across normal, boundary and invalid conditions. Confirm that sector_code is populated only when applicable, conditional rules are enforced, provenance is retained and downstream systems do not change its meaning or precision.
Canonical schema definition
| JSON property | sector_code |
|---|---|
| Required in core profile | Yes |
| Type | "string" |
| Allowed values | ENERGY, TRANSPORT, BANKING, FINANCIAL_MARKETS, HEALTH, DRINKING_WATER, WASTE_WATER, DIGITAL_INFRA, ICT_SERVICES, PUBLIC_ADMIN, SPACE, POSTAL, WASTE_MGMT, CHEMICALS, FOOD, MANUFACTURING, TELECOM, RESEARCH, OTHER |
Source: UAIF Schema Specification and UAIF Core JSON Schema.