This is exactly what I was trying to covey in the requirement (although it didn't come out that way with the read and create/update/delete separation)... I actually would rather be explicit with the create/update/delete for the requirement even though it may materialize as a single operation to support all of these in the spec. Here is another cut at the proposed rewording (we may want to split this into several requirements): "It should be possible for a Consumer to read multiple properties of the Producer with one invocation. It should be possible for a Consumer to batch create, update and delete multiple properties of the Producer with one invocation. It should also be possible to perform this operation in conjunction with other operations."