Skip to content

Draft for review only

TrafficRegulation

A traffic regulation is a rule having the force of law that is established by a regulator through a traffic regulation order.

IRI: https://w3id.org/itsdata/regulation/v1/TrafficRegulation

Diagram

cluster_associated its-core_OfficialThing its-core:OfficialThing RegulationThing RegulationThing TrafficRegulation TrafficRegulation hasEnforcementMethod hasInceptionDate [0..1] hasLegalStatus [1..*] hasTerminationDate [0..1] isSuspect [0..1] requiresSupplementalData TrafficRegulation->its-core_OfficialThing TrafficRegulation->RegulationThing TrafficRegulation->TrafficRegulation hasAssociatedRestriction 0..1 Condition Condition TrafficRegulation->Condition hasCondition 0..1 its-core_ActivationStatusCode its-core:ActivationStatusCode TrafficRegulation->its-core_ActivationStatusCode its-core:hasActivationStatus 1 LegalBasis LegalBasis TrafficRegulation->LegalBasis hasLegalBasis 1 PermitType PermitType TrafficRegulation->PermitType hasPermitType RegulationCategoryCode RegulationCategoryCode TrafficRegulation->RegulationCategoryCode hasRegulationCategory 1..* TrafficControlDevice TrafficControlDevice TrafficRegulation->TrafficControlDevice associatedTrafficControlDevice Trustworthiness Trustworthiness TrafficRegulation->Trustworthiness hasTrustworthiness 0..1

TrafficRegulation Diagram

Specializations of TrafficRegulation

Class Description
Coded Pair Regulation A restriction defined by a code.
Coded Regulation A restriction defined by a code.
Coded Regulation With Fee A condition defined by a code.
Coded Regulation With Threshold A restriction defined by a code coupled with a threshold value.
Textual Regulation A textual regulation is a rule having the force of law that is established by a regulator through a traffic regulation order.

Formalization for TrafficRegulation

Property Constraint
associatedTrafficControlDevice only TrafficControlDevice
hasAssociatedRestriction max 1 TrafficRegulation
hasCondition max 1 Condition
hasInceptionDate max 1 xsd:date
hasLegalBasis exactly 1
hasPermitType only PermitType
hasRegulationCategory min 1 RegulationCategoryCode
hasTerminationDate max 1 xsd:date
hasTrustworthiness max 1 Trustworthiness
isSuspect max 1 SuspectStatusCode
its-core:hasActivationStatus exactly 1 its-core:ActivationStatusCode
hasEnforcementMethod only EnforcementMethod
hasLegalStatus min 1 LegalStatusCode
requiresSupplementalData only RequiredSupplementalData
subClassOf RegulationThing
subClassOf its-core:OfficialThing

Other annotations

Property Value
ReqView ID its-regulation-59
dash:abstract true
skos:editorialNote The latest release of DATEX-II assigns a legalBasis to each condition rather than to the regulation. This seems odd; I have added a link for both in this model.
skos:editorsNote It is unclear if PermitInformation needs to be associated directly with TrafficRegulation and why. It seems as if PermitCondition is a more appropriate way to describe the association.