work-zone
CORE · WIREDWork zones: lane closures, roadworks and other planned disruptions to the traveled way. A work zone is reported, not managed, so this family carries types and events only, aligned with WZDx v4.
Data model
The configuration and state tree. Safety constraints are expressed as YANG must and validated at every boundary.
// no configuration or state tree: a work zone is reported, not managed,
// so the model is the event payload
notification zone-state-changed {
leaf kind { type identityref; } // activated|updated|cleared
leaf zone-id { type work-zone-id; }
uses geo-path; // at least one point
leaf window-start { type date-and-time; }
leaf lane-impact { type identityref; } // all-lanes-closed, merge-left, flagging...
leaf work-zone-type { type identityref; } // static|moving|planned-moving-area
container worker-presence {
leaf workers-present { type boolean; }
leaf last-confirmed-at { type date-and-time; }
}
leaf reduced-speed-limit-kmh { type speed-kmh; }
// fields follow WZDx v4 road events
}
Notifications & events
Each event is its own typed notification with its own ce-type. Consumers filter by subject before parsing.
Event families:
comm
zone
Subject & bindings
# canonical subject (reference CloudEvents binding)
openits.us-tx.txdot.d07.work-zone.i35-exit-214.comm-health-event
Schema registry
Every revision is immutable and content-addressed. Cite the exact date in ce-dataschema; there is no latest alias.