dms
CORE · WIREDDynamic message signs: sign configuration, message lifecycle, and pixel/power fault reporting.
Data model
The configuration and state tree. Safety constraints are expressed as YANG must and validated at every boundary.
container dms {
leaf mode { type sign-mode; } // blank|message|test
leaf brightness { type uint8; units "percent"; }
list messages {
key "slot";
leaf state { type message-state; } // queued|active|cleared
leaf multi { type multi-string; } // NTCIP 1203 MULTI
must "state != 'active' or multi" {
error-message "active message requires MULTI content";
}
}
}
Notifications & events
Each event is its own typed notification with its own ce-type. Consumers filter by subject before parsing.
Event families:
fault
message
mode
Subject & bindings
# canonical subject (reference CloudEvents binding)
openits.us-tx.txdot.d07.dms.i35-exit-214.fault-cleared
Schema registry
Every revision is immutable and content-addressed. Cite the exact date in ce-dataschema; there is no latest alias.