blargney the second
blargney the minute's son
as a developer, what Monty's doing is exactly what he's supposed to.
Duplication of data is bad, it leads to stale data (because Monty is less likely to keep his copy up to date, than the master copy at d20srd). Barring performance problems, linking is the optimal solution. You only replicate data for performance reasons. Heck, if WotC ran the d20srd site, then that's the place to link to. Since WotC failed to provide such a useful service, d20srd.org is the central repository.
A better complaint would be based on the difference between showing an encounter description with a link to the monster stats, rather than embedding the monster stats into the encounter description.
The former requires the user to follow a link, and they cannot see the all the data within one screen (or print-out). Whereas the latter, embedding the data into the encounter, means the user can print out the page, and everything they need is there.
This is a good summary of the situation. Much as I hate iframes, they'd be a simple and effective way to implement what you're suggesting.
-blarg