...
For example, if there are multiple data sets associated with an entity and you have to multiple client configurations that reference the context for the entity but you don’t want all of the data for that entity available for all clients you can specify an a different context to the data sets and then add that context to the client configuration, along with the entity context. If you’re reading closely you just realised that that means that you can specify multiple context for a client.
...
The example for the client context above show shows one way of defining what contexts should be used in the client, namely as a comma separated list, where an item associated with any of those contexts, plus anything that’s not associated with any context, will be included in the client, but Weave 2.6.9 extends that to make the client context attribute more flexible.
...
Another limitation of this format is that it’s always an “or” decision, with out without the “only” prefix, that is, it always includes items that are in either the tree or finance context, there wasn’t a way to specify that only items that are in both the tree and finance contexts should be included, but in 2.6.9 you can do this with by providing an expression for the context, e.g.
...
In the same way that a client can be include items from multiple contexts, the items themselves can also be associated with multiple contexts, by setting the context attribute for the item to a comma separated list.
...