W3C home > Mailing lists > Public > www-validator@w3.org > June 1999

Re: Parser Error?

From: Lloyd Wood <L.Wood@surrey.ac.uk>
Date: Thu, 10 Jun 1999 12:25:29 +0100 (BST)
To: Jukka.Korpela@hut.fi
cc: www-validator@w3.org, gerald@w3.org
Message-ID: <Pine.SOL.4.02.9906101222070.4699-100000@petra.ee.surrey.ac.uk>
Thanks for all this; fills in a lot of blanks, but:

On Thu, 10 Jun 1999 Jukka.Korpela@hut.fi wrote:

> > The effect of widespread use of tilde (~) and ampersand (&) on URLs
> > sans escapement is a lost cause as far as validation is concerned.
> 
> The necessity of "escaping" ampersands in attribute values has
> _gained_ and is gaining importance. The more entities there are,
> the greater the risk of having &something processed in a way you
> really did not mean.
> 
> The tilde never was an issue in validation. Validators do not
> check URLs in any way, since to them, a URL is just CDATA.

Yet a URL with form state includes & between attribute values, gets
checked and gets complained about by the validator, which is pretty
much where we came in.

I don't see why & in CDATA can't simply be excepted...

cheers,

L.


> (That said,
> despite the fact that RFC 2396 relaxed the encoding requirements,
> it still is, as it always was, safest to encode ~ in a URL as %7e.
> In particular, trying to use the tilde in printed media is a lost cause,
> and who can predict which URLs get printed?) 
> 
> -- 
> Yucca, http://www.hut.fi/u/jkorpela/ or http://yucca.hut.fi/yucca.html

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>
Received on Thursday, 10 June 1999 07:25:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:13:52 GMT