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

RE: Promotion of XHTML

From: Richard Norman <normri@samc.com>
Date: Tue, 07 Jan 2003 12:56:52 -0800
Message-Id: <se1acea2.075@samc.com>
To: <roconnor@Math.Berkeley.EDU>, <www-html@w3.org>

One other thing I would like to say about this is that in reading the
section of the specification, the "most" of the browsers have taken the
clearer high road as opposed to the technically correct road.  Taken
from the spec mentioned...
Some SGML SHORTTAG constructs save typing but add no expressive
capability to the SGML application. Although these constructs
technically introduce no ambiguity, they reduce the robustness of
documents, especially when the language is enhanced to include new
So in a sense they are cleaning up the spec where the the root
specification can not (since HTML and XHTML are based upon SGML, they
can not remove these shortcuts from their root I believe)
So anyway, I am glad to fully know this now.  Thanks for the info..
Richard Norman

-----Original Message-----
From: "Russell O'Connor" <roconnor@Math.Berkeley.EDU> 
Sent: Monday, December 30, 2002 1:15 PM
To: W3C HTML <www-html@w3.org>
Subject: RE: Promotion of XHTML

Hash: SHA1 

[To: www_html@w3.org] 

On Mon, 30 Dec 2002, Peter Foti (PeterF) wrote: 

> Also, if <br /> in HTML was equivalent to <br>&gt;, then that would
seem to 
> indicate that every web browser out there is broken, and should
display this 
> as a line break followed by the greater than symbol.  I don't know
> logic you are using to determine that <br /> = <br>&gt;, but it seems
> to me. 

Borris is correct.  Observe: 

> sgmlnorm _d _c ~/sgml/catalog ~/sgml/15445/15445.dcl "<osfd>0" 
sgmlnorm:/home/u2/grad/roconnor/sgml/15445/15445.dcl:28:33:W: characters

in the 
document character set with numbers exceeding 65535 not supported 
<!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HyperText Markup 
<HTML><HEAD><TITLE>TEST</TITLE><BODY><P>break<br />ing</P></BODY></HTML>

<!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HyperText Markup 

As you see, sgmlnorm parses <br /> as <BR>&gt;.  The same thing will 
happen if you use HTML 4.01 instead of ISO_HTML. 

Most popular browsers fail to follow the requirements indicated by
B.3.7 of the HTML 4.01 recommendation. 

It blows my mind that the W3C seems to bury it's head in the sand about 
the <br /> issues with ``compatibility'' between XHTML and HTML.  I just

don't understand what they were thinking when they came up with such 
plainly false claims of compatibility. 

_ __ 
Russell O'Connor            < HYPERLINK
``[Law enforcement officials] suggested that the activists were stopped 
not because their names are on the list, but because their names
those of suspected criminals or terrorists.'' __ SFGate.com 

Version: GnuPG v1.2.1 (SunOS) 


Incoming mail is certified Virus Free. 
Checked by AVG anti-virus system ( HYPERLINK "http://www.grisoft.com"
Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002 

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.434 / Virus Database: 243 - Release Date: 12/25/2002

The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or  the 
sender immediately and do not disclose the contents to any one or make copies.

Received on Tuesday, 7 January 2003 15:57:43 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 30 April 2020 16:20:48 UTC