Be careful about your generalizations, Pat. I do not consider all content equivalent/fungible. That’s a massive overextension of the fact that much, and often all, of the presentation can in be separated out and reused.
We don’t redesign paperback books for every new novel; if anything, the layout and rendering of the contents may bear recognizable indications of a particular publishing house’s practices. And that’s a set of style decisions that authors are generally willing to trust to the publisher, though there may be specific exceptions in specific places in specific stories. TO THAT EXTENT, the style of the presentation is separable from the author’s writing, and that style is reusable, and reused, across multiple editions and multiple authors.
I must admit I also feel particularly strongly about this because I’ve watched what an overemphasis on style – because it was almost impossible to keep your fingers out of the style – has done to the web. The original vision of HTML was that it was semantic markup, and that based on those semantics the details of rendering could be chosen by the browser and the user. That would have been a huge boon to the reader, especially but not limited to the reader who needs adaptive technology. Instead, people began trying to tweak presentation details directly thru the HTML, and moving into interaction techniques which are certainly appropriate if you’re thinking of the browser as a “thin client” for interactive applications but which do little but get in the way of presentation of relatively static data.
If someone wants to write content that takes full advantage of that, more power to them; then the presentation is legitimately part of the content – though they’re giving up some audience and exposing themselves to greater risk that a bug in the experience turns off someone who was actually interested in what they’re trying to present. But it’s being used at times when it really does do nothing but Look Pretty and Get In The Way, and in ways that defeat the original goal of improving the reading experience.
Neither content OR presentation is fungible. But if they’re properly defined, it really should be possible to separate them – again, see the examples I cited earlier – so that the guy who’s using a screen-reader gets an experience that’s tailored to him, and the gal who’s using a palmtop gets an experience that’s tailored to her, and the guy who hates flashy interactions and just wants to Read The Stuff gets an experience that’s tailored to him, and the one who wants full background music and interactive 3D rendering of the starship’s plans and wants to check that the line of sight really did permit that shot gets an experience tailored to her, and…
And we can’t do any of that while we’re defending turf and arguing about how the marketeers abuse the terms no matter WHICH definition you’re using. The distinction between content and presentation, IF not overused and IF used with respect for the authors and designers and so on, is a useful one.
All I’m asking is that we stop feeding an argument which shouldn’t exist in the first place and focus on how to productively move forward.