me'
01-12-2004, 06:06 PM
1.1. Why Build XHTML Modules?
XHTML is more than just a recasting of HTML into XML. It is also an extensible architecture that permits the ready definition of new document types. The W3C envisions that client manufacturers, document authors, and content providers may all use this architecture to define document types that are specific to their needs. The XHTML Modularization specification defines a collection of modules and a framework that make the definition of these new document types relatively easy. [quote source (http://www.w3.org/TR/xhtml-building/introduction.html#s_intro_building)]
It seems to me the last time people started adding little bits to a language was with the browser wars — browser makers adding little proprietary tags into HTML, that ended up with such nasties as <marquee> finding their way into the general web.
Sure, the very idea of XML is to let authors write their own documents, and as long as none of these made-up tags that only work in IE find their way into the DTDs there's no problem, right?
Well, I'm just wary that Microsoft (and possibly others) will sieze the opportunity, and induce a whole new wave of interwoven content and style (among other things) into the markup world.
XHTML is more than just a recasting of HTML into XML. It is also an extensible architecture that permits the ready definition of new document types. The W3C envisions that client manufacturers, document authors, and content providers may all use this architecture to define document types that are specific to their needs. The XHTML Modularization specification defines a collection of modules and a framework that make the definition of these new document types relatively easy. [quote source (http://www.w3.org/TR/xhtml-building/introduction.html#s_intro_building)]
It seems to me the last time people started adding little bits to a language was with the browser wars — browser makers adding little proprietary tags into HTML, that ended up with such nasties as <marquee> finding their way into the general web.
Sure, the very idea of XML is to let authors write their own documents, and as long as none of these made-up tags that only work in IE find their way into the DTDs there's no problem, right?
Well, I'm just wary that Microsoft (and possibly others) will sieze the opportunity, and induce a whole new wave of interwoven content and style (among other things) into the markup world.