Well, yes; you can talk to it, using IP. I'm sorry if this sounds a flip answer; it's not intended to be.
Firstly, remember that the individual members of a bridge should not have addresses assigned to them, so you can't talk to the bridge that way.
Then, consider my problem, when I had a three legged firewall. Inside, on a simple interface, was 192.168.0.0/16; this would need to be NATted when traffic went outside. On the other two interfaces, I had 126.96.36.199/25, but I had a need for some machines in that address space to be exposed to the internet, and others to be behind a firewall - but the machines already there were addressed in such a way that I couldn't split it into 188.8.131.52/26 and 184.108.40.206/26. I had members of 220.127.116.11/25, high and low, on both the external and the DMZ interfaces.
My only choice was to make a bridge out of the external and DMZ interfaces, and use
--physdev-out rules to make firewalling decisions about bridging the packets across those interfaces.
But for traffic in and out of the internal interface, this was full layer-3 routing. The "external" interface of the firewall needed to have an address in order to NAT packets from the internal to the external interfaces, and it also needed an address for eg remote administration from the internet, VPN terminations, and so on.
So that was one circumstances where, as far as I could determine, a bridge interface definitely needed an IP address of its own. Does that make sense?