|
Joshua Allen asks:
And why on earth do we need XHTML? XML + CSS is superior in practically every respect, and easier.
We need XHTML so that people could get your content (XHTML) and ignore your rendering commands (CSS). They could then display the content according to their own wishes. A general XML+CSS solution (that is, no predefined vocabulary) will immediately lead to the following scenario:
- You are subscribed to 10 XML/CSS sources
- Each source uses its own schema (we've ditched DTDs, no?)
- You want to display the sources in our own fashion, no the authors'
- Result: you need to create 10 different transformations (or 10 different CSS files), each suited for each source
This will get unmanageable quite quickly.
A related question might be why use XHTML instead of, say, DocBook. The answer to that, I think, is because using something as complex as DocBook means waving 90% of web content creators goodbye.
|
