Thinh thinks there is no need to have a filterId and filterRules for service information model, a composite service should have the information for its nested services, we don't need to know the inside services, but only know the outside presence.
Borislav illustrates the usage for filter. Filter realization is mature and implemented by SDC. When looking for services, we can use filter to choose the right satisfied nested services inside. For example, when instantiating service A, we have 5 service instances with different properties(latency, mobility,...), we need to choose one of them to compose A. The requirement is the latency of B should lower than A, the latency information can't be known in design time, only can know while instantiation, this is where the filter works.
Next step:
1. Leave one more week to receive coments.
2. Go through and make decisions one by one on the proposal attributes.
3. Borislav will do some updates for the slides on the pages related to Thinh's proposal.

Recordings

Space shortcuts