Re: Explicitly closing implicitly opened elements

• Next message: Vidiot: "Validator errors"
• Previous message: Claus Färber: "Re: validator bug ?"
• In reply to: Terje Bless: "Explicitly closing implicitly opened elements (was: validator bug?)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Other mail archives: [this mailing list] [other W3C mailing lists]
• Mail actions: [ respond to this message ] [ mail a new topic ]

Date: Sun, 30 Jan 2000 15:47:12 -0500 (EST)
Message-Id: <200001302050.e0UKoLs12597@mercury.nildram.co.uk>
To: W3C Validator <www-validator@w3.org>
From: Leedsnet <info@leedsnet.com>
Subject: Re: Explicitly closing implicitly opened elements

>I agree, but I'm unsure if this can, or even should, be reported by the
>Validator as I suspect this is perfectly valid in SGML. 

I agree with all that you wrote, and like you, feel that the  validator
must report
exactly the result of parsing the mark-up with an SGML and nothing but
that. 

My guess is that this fell out of some feature of the language intended to 
ease typing. I cannot, though, believe that it was deliberate. The best I
can hope for is that it is documented on the parser site.

Ben.


-- 
Leedsnet - The information resource for Leeds and the West Riding
<URL:http://www.leedsnet.com/>

• Next message: Vidiot: "Validator errors"
• Previous message: Claus Färber: "Re: validator bug ?"
• In reply to: Terje Bless: "Explicitly closing implicitly opened elements (was: validator bug?)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Other mail archives: [this mailing list] [other W3C mailing lists]
• Mail actions: [ respond to this message ] [ mail a new topic ]