|
Christos:
I designed the examples to be very short - XML IMO is verbose enough as it is. And I did mean the versions to be OR'ed (I wrote: "Receivers that support either L1, L2, or L3 may process it.").
But I fully agree that a more granular approach is, for instance the one you sketch, is possible and often even desirable. That's why I called it "Capability Compatibility" not "Version Compatibility Design Pattern". And yes, in that case one would need OR'ed sets of AND'ed capabilities.
Marc
|