Several § 9.3.3 exclusive and batch-operation distop TCs make the Context Source Registration list specific entity ids so the registration matches the entities under test. - @arenab (!294): hardcoding two ids *"defeats the purpose of trying to create a batch of entities"* — the registration should accept the entity **idPattern**, or a dynamic array of ids. - @arenab (!288): same concern. **Decision needed:** how the registration should express its entity set (idPattern vs a dynamic id list) so batch TCs can scale, then apply it across the affected TCs and the shared fixture/keyword. **Files to consider:** - `…/BatchEntities/CreateBatchOfEntities/D012_01_exc.robot`, `DeleteBatchOfEntities/D015_01_exc.robot` - `…/BatchEntities/UpsertBatchOfEntities/D013_01_exc.robot`, `D013_01_red.robot`, `D013_02_exc.robot`, `D013_02_red.robot` - `…/BatchEntities/UpdateBatchOfEntities/D014_01_exc.robot`, `D014_02_exc.robot`; `MergeBatchOfEntities/D016_01_exc.robot` - `…/EntityAttributes/{PartialAttributeUpdate/D005_01_exc, DeleteEntityAttributes/D006_01_red, D006_02_red, ReplaceEntityAttribute/D009_01_exc, D009_01_red}.robot` - `data/csourceRegistrations/context-source-registration-vehicle-speed-with-batch-ops-exclusive.jsonld` - `resources/ApiUtils/ContextSourceRegistration.resource` _Originated from !288 + !294 (closed in favour of this issue)._