OPDA Knowledge base
Physical — ontology

SKOS substrate

23 skos:ConceptScheme instances + 137 skos:Concept members emitted by opda-gen into opda-vocabularies.ttl per ADR-0010. Each scheme is classified into the 7-category UFO framework per ODR-0011 §1a + §8a.

Source

opda-vocabularies.ttl — 1165 lines, generated by opda-gen 1.0.0.

7-category UFO framework

Per ODR-0011 §8a, every scheme carries opda:ufoCategory from one of seven UFO categories. The framework distinguishes ontologically-distinct kinds of enumeration:

CategoryDescriptionSchemes
Substance Kind labelSortal labels naming a substantial KindOwnerType, PropertyType, TenureKind
Quale-in-RegionQuality particulars over a quality region (DOLCE)BuiltForm, CentralHeatingFuelType, CouncilTaxBand (EW + Scotland), CurrentEnergyRating, HeatingType, OffMainsDrainageSystemType, OwnershipType, YesNo, YesNoNotApplicable, YesNoNotKnown, YesNoNotRequired
Quality ValueDOLCE Quality Region valuesAddressVariant, AssuranceLevel, EvidenceMethod
Method/plan codeAction-modelling codes (Guizzardi & Wagner 2010)MilestoneKind, SellersCapacity
Phase labelIntra-Kind phase labelsParticipantStatus, TransactionStatus
Role labelAnti-rigid Role labelsRole
(Trust-tier label)(reserved for future use)

The 7-category framework is OPDA-native: an artefact of ODR-0011 §8a per S011/S012 framework convergence.

Scheme header pattern

Per ODR-0011 §1a + §8a, every scheme carries 7 metadata fields:

FieldPurpose
skos:prefLabelHuman-readable scheme label
dct:titleLong-form title (with disambiguation)
skos:definitionScheme-level definition
dct:sourceAuthoritative source (regulator or ODR §)
opda:ufoCategoryUFO meta-vocabulary classification
skos:scopeNoteUFO + DOLCE citation
opda:hasStewardCouncil steward (named)

Per-scheme files

SchemeUFO categoryStewardFile
AddressVariantQuality ValueGuizzardi (S015 Q1)address-variant.md
AssuranceLevelQuality ValueMoreau (S009 Q3)assurance-level.md
BuiltFormQuale-in-RegionAllemangbuilt-form.md
CentralHeatingFuelTypeQuale-in-RegionAllemangcentral-heating-fuel-type.md
CouncilTaxBandEWQuale-in-RegionBaker (VOA)council-tax-band-ew.md
CouncilTaxBandScotlandQuale-in-RegionBaker (SAA)council-tax-band-scotland.md
CurrentEnergyRatingQuale-in-RegionBaker (DESNZ)current-energy-rating.md
EvidenceMethodQuality ValueMoreau (S009 Q3)evidence-method.md
HeatingTypeQuale-in-RegionAllemangheating-type.md
MilestoneKindMethod/plan codeGuizzardi (S007 Q2)milestone-kind.md
OffMainsDrainageSystemTypeQuale-in-RegionAllemangoff-mains-drainage-system-type.md
OwnerTypeSubstance Kind labelGuizzardi (S006 Q1)owner-type.md
OwnershipTypeQuale-in-RegionKendallownership-type.md
ParticipantStatusPhase labelGuizzardi (S006 Q7)participant-status.md
PropertyTypeSubstance Kind labelAllemangproperty-type.md
RoleRole labelGuizzardirole.md
SellersCapacityMethod/plan codeGuizzardi (S006 Q4)sellers-capacity.md
TenureKindSubstance Kind labelKendalltenure-kind.md
TransactionStatusPhase labelGuizzardi (S007 Q3)transaction-status.md
YesNoQuale-in-RegionAllemangyes-no.md
YesNoNotApplicableQuale-in-RegionAllemangyes-no-not-applicable.md
YesNoNotKnownQuale-in-RegionAllemangyes-no-not-known.md
YesNoNotRequiredQuale-in-RegionAllemangyes-no-not-required.md

Identity rule

Per ODR-0005 Anti-pattern §5: scheme members bind to corresponding OWL classes via skos:exactMatchNEVER owl:sameAs (which would propagate identity-collapse across contexts under inference).

Deprecation lifecycle

Per ODR-0011 §5a + ODR-0017, deprecated members carry owl:deprecated true + dct:isReplacedBy to the successor concept. The opda:DeprecationChainRule SHACL-AF rule materialises opda:hasDeprecationStatus (“with-succession” or “without-succession”) into the validation report.

Source ADR + ODR

Comments

Loading comments…