Extbase MVC Framework

In FLOW3 we use the @format argument/configuration to specify the format of a view (xml, txt, html, ...).
That has been backported to Extbase, so you can specify the format in various view helpers and when interacting with the UriBuilder.
But additionally we're using the pageType to render those special formats (E.g. if you want to render an xml representation of your plugin, you don't want all the rest of the page to be rendered obviously).
This leads to the situation, that you currently have to specify both, format and targetPageType when creating a link to a special format (see http://git.typo3.org/TYPO3v4/CoreProjects/MVC/blog_example.git?a=blob;f=Resources/Private/Templates/Post/Index.html;h=fa8a3ffe9160a4d8ee66516b1489e6375ebe5ea7;hb=HEAD#l50 for example).

A solution would be a global mapping, for example in the form of a new TS configuration "formatToPageTypeMapping" (name to be discussed):

config.tx_extbase {
    view.formatToPageTypeMapping {
        txt = 99
        pdf = 123
    }
}

The UriBuilder could then transparently set the pageType argument if it was not specified.