Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
why w3c has the conventions of different Doc-types .. ? Instead they could have recommended only one Doc-type (say loose type.. as it would prone to less number of SILLY errors) and would have standardized it to all browsers (including the ones in mob and PDAs) ..
I haven’t got any satisfying answer in any tutorial yet .. I have been reading “how these different Doc-types differ in” but I want to know do we really need it ???
The old doctypes (pre-HTML 5) are standardized mechanisms in SGML to embed version and validation information. If you use a full-featured SGML workflow, they offer great possibilities to automatically process the file.
In this context the different DOCTYPES of HTML 4/XHTML 1 were then (10 years ago) quite a nice idea. They allowed the authors to say: “Oh, I’ve an old page, and I’m bound to use this and that tag.” or “Yes, I use the newest and cleanest markup out there. I know what I’m doing.”
Why this “public identifier” stuff and so? One example of the benefit: It allows to store locally (and re-assign later) the DTD of any HTML file and let’s you validate it even without Internet access. (Remember: SGML was standardized in the 80’s.)