SCTE 104/35 Codex

Inside a multiple_operation_message the order of operations is meaningful. Each block in the data() loop begins with either a Normal request, such as splice_request or time_signal, that produces an SCTE 35 section on its own, or a Control request. Control requests generally stand on their own, and the encryption Control Word operations manage the Control Word database independently of any other operation. One exception is insert_audio_provisioning (added in the 2022 edition), which the opID table lists as Control but clause 9.8.12 describes as a Normal request that must be accompanied by a time_signal_request. A Normal request may be followed by Supplemental requests, such as insert_segmentation_descriptor or insert_tier_data, that modify or add to it, and they must follow the Normal request they apply to. Starting a new Normal request signals that the previous one is complete and ready to be formatted at the time given by the timestamp(). In the 2004-2014 editions the order of execution is clause 7.2.3.1 rather than 8.2.3.1.