3 ms·
This is clearly working for them. What is interesting about this is that it puts a vote on the SGML idea that content and presentation are nicely separated and
by wglb 17y ago
This is clearly working for them. What is interesting about this is that it puts a vote on the SGML idea that content and presentation are nicely separated and identified by the tags. But this has always faintly concerned me, as to whether this really will work.
As an example madair in an earlier comment notes that em is intended to be a semantic tag. But do the semantics of this particular tag ever mean anything outside of "show this text as emphasized"?
I am wondering if whatever semantic markup we do is still all about presentation, and takes a fairly arbitrary abstraction of what the text is to mean.
- madair 17y agoIt's a twist, but if we say that an iPod cannot emphasize text, then we can instruct the system to ignore <em> tags. Because the semantics of <em> are clearly defined, a judgment call is available to us to feel confident that we can ignore the tag completely under the circumstances. So we utilize the tag itself still by instructing the system to swallow it.
- wglb 17y agoSee, this is what I find a bit unclear. The concept is that presentation is distinct from content. But if we say that the semantics of the em tag are to effect the presentation, they seem to be not be separated anymore, right?
- madair 17y agoAt a certain point the semantics of the content get translated into an output format. In a browser it's italic. In an iPod it's ignored. The semantic tags are the means, but output presentation is still the end, and there's certainly no reason to expect that all devices can take the original semantic markup and use CSS or some other mechanism to present it. And because of the semantic meaning we can make the em disappear with confidence.