Since Drupal is a framework (and only really comes to life in most cases by permitting the use of contrib modules) that naming install profiles that ship with Drupal after something that will build user expectation would be a bad idea.

I do support a nice "blog" install profile, but if I was making an install profile for the most reviewable Drupal blog, it would certainly include pathauto, google analytics, etc.

I'd hate for Drupal to be judged on an install profile included in core that didn't deliver on the promise

thus... I would encourage install profiles shipped with core to have names that reflect what they aim to provide. Minimal, Basic, Core-Maximum ?

Minimal: only the absolutely required modules... this install would be used by those who know what they're doing and want lean and mean for their final result.

Basic: A few nice bits thrown in for good measure.

Core-Maximum: so named because everything in core is enabled with sample content (taxonomy, roles, everything++)... but the name doesn't suggest that people should stop at Core. This would be intended as an educational install, where you get to kick the tires of all functionality in a quick way.

Of course Drupal aims to be a framework. That's to it's credit. But let's not set up users who will be evaluating "Drupal" the framework, with any expectations that this is all Drupal can be.