Okay here is another way to approach it. I have an internet exchange where I have 30 peers. Each of those peers needs to receive around 60 advertisements EACH. They are all basically the same prefixes except their own. So I have 30 peers with 60 advertisements each. If I could reference one address list and then deny specific advertisements I would have a much smaller filter list.
See my point?
I am dealing with a similar situation, similar but slightly different...
I am using BGP communities to accomplish this goal....
e.g.
Inbound routes are marked with community 115 eg. 12345:115
Outbound Routes are marked with community 135 eg. 12345:135
as such I build by filters based on above communities.... (FYI, one can also use regex with ASN to create filters too)
if you are worried about advertising someone's own route back to them, you don't have to worry about it, since bgp, inherently drops those routes.... (technically if you are only worried about sending them their own route back, you don't need to worry about filtering anything, and just can advertise everything to everyone.....)
If you are trying to manage everyone's peering with each other, then you might be better off running a route-reflector on a private as, and using that to manage routing with each other.
One of the benefits of Peering Exchanges, is that each member as can manage their own routing .....