Chain agreements: feedback, correction, chunking, transport, releases
Chunking on the sender side: splitting a large message
Since Release 2026 a large message (typically message 3 with thousands of cohorts) can be split into sub-messages. Each sub-message carries a chunking block with currentChunkId, chunkSequenceNumber, totalNumberOfChunks and the JMESPath references to the message parts it contains. The base message holds the common header; the chunks hold the cohort data.
Steps
- Step 1SenderDetermine the number of chunks and generate one currentChunkId for the series.
- Step 2SenderCreate per chunk a valid message with the same commonTechnical and commonFunctional, an increasing chunkSequenceNumber and chunkFragmentPaths to the included parts.0001c
- Step 3SenderSend the chunks in order; each chunk gets its own feedback.feedback
Rules and consistency checks
- Every chunk must be schema-valid on its own.
- SIVI publishes a chunk template and sample chunks with message 3.
Source: Handleiding paragraaf 7.6.1 en 7.6.2