- From: Gareth Hay <gazhay@gmail.com>
- Date: Tue, 1 May 2007 16:13:34 +0100
- To: Laurens Holst <lholst@students.cs.uu.nl>
- Cc: W3C List <public-html@w3.org>, "Philip Taylor (Webmaster)" <P.Taylor@Rhul.Ac.Uk>
Received on Tuesday, 1 May 2007 15:13:49 UTC
On 1 May 2007, at 15:42, Laurens Holst wrote: > What’s different from your ideas is that the difference lies not in > forcing people into a new model if they want to use HTML5 features, > but still produce HTML content. This is e.g. very relevant for > existing systems (that is, all systems that are existing now), > where people want to add functionality without being forced into > producing 100% well-formed XML content. I think this is the crux of the discussion. We both think the end point will be the same, but we arrive there by two opposing methods. In my reckoning, people will always choose the easiest path. If they write tag soup now, they will do so for HTML5 should it render and 'get the job done'. By forcing some kind of checking we are educating these users that they are doing it wrong, if they want to use new html5 features they *need* to learn about it. Otherwise they carry on writing html4 tag soup. I can't imagine any other discipline where lazy, lax, poor techniques are given such a priority, it should be discouraged IMO Gareth
Received on Tuesday, 1 May 2007 15:13:49 UTC