Separating data and mark-up - JavaScript versus XSLT

To be clear, by "Dropping XSLT" I meant "Dropping browser-native XSLT and therefore losing the single URL model of podcast sharing and integration". Because it's not XSLT, per se, that is argued to undergird the ecosystem, but the single URL model. It's like flipping the YouTube model on its head, where a YouTube link functions as both a link to the raw video that can be followed by any HTTP-aware software, but also happens to magically render a convenient (yet host-controllable) UX when opened by a web browser. It's an artifact of the way the latter aspect works that helps to protect the viability and persistence of the former--open-access to the raw media.