W3C home > Mailing lists > Public > www-html@w3.org > August 2003

Modularization in XHTML 1.1 (Why)

From: <luin5471@bellsouth.net>
Date: Tue, 26 Aug 2003 10:20:39 -0400
Message-ID: <001c01c36bdd$39fad470$6101a8c0@gateway>
To: <www-html@w3.org>
I'm a beginning student in XHTML (1.1) now, but I have significant
experience in other, high-level programming languages, such as C
and C++. 

I would like to hear from PROGRAMMERS about the concept of
modularization in XHTML 1.1 where a designer/programmer includes
or excludes certain of the functional modules, based on the
functionality of the program/product that is being developed. 

Simply put, with C++ for example, you could obtain certain
functionality for your program by linking to code libraries, but the
addition of each library increased the size of your code. 

Thinking, as I do, that these XHTML modules are nothing but DTD
"references", that is, there is no actual code or overhead added to
your program, what does it matter if a development author qualifies
which modules of XHTML his product supports? 

What is gained by editing a "standard" DTD in order to define the
functionality that a given program or product supports, that is, if a
hand-held widget did not make use of FRAMES functionality, what is
the negative effect if its referenced DTD includes the FRAMES module

I like the concept of modules and highly-defined structures, but how
does the practice of modularization actually affect the programmer?

I really would appreciate any information that the w3-savvy
programmers have to say about this issue. 

Received on Tuesday, 26 August 2003 10:20:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:05 UTC