I agree that intents that are listed in mayProvide do not require a policy set. The binding/implementation provides the functionality of the intent if the intent is present on the relevant composite element. It looks to me that CompositeWireBuilderImpl, as part of the process of trying to find matching policy sets, removes intents that are found in mayProvide from the model object. In that case, how would the binding/implementation know it should provide the intent functionality if the intent isn't present in the model anymore?
Greg Dritschler
