There is currently a beta version 2.1 of the calendar... In the Known Issues section it explains this:
Known limitations
The following issues are known limitations about the calendar:
...
You can see events from other ward calendars through Locations, but the events do not indicate the ward the events belong to.
...
I don't see a modification to the design coming in the way you are suggesting. The current architecture seems to be very WARD-centric, entire applications have rolled out bypassing stake callings with access to them. This, I'm guessing, is an interpretation of tightening down on privacy issues. Additionally some design requirements might be due to other countries in the world and the laws around privacy they have, while we have more flexibility in the U.S., designing a system with the 'loose' privacy structure in the U.S. and trying to 'tighten' the structure to meet the laws implemented in other countries is probably harder than designing for the tight structure and living with the limitations in the U.S.
Just a guess.
“A long habit of not thinking a thing wrong, gives it a superficial appearance of being right, and raises at first a formidable outcry in defense of custom.”
― Thomas Paine, Common Sense
