W3C home > Mailing lists > Public > public-evangelist@w3.org > October 2002

Re: Wired.com switched to a Web Standards compliant platform

From: Holly <hollymarie@ameritech.net>
Date: Mon, 14 Oct 2002 08:12:40 -0500
Message-ID: <046d01c27383$6008e1a0$0602a8c0@hollylpiggtm47>
To: "Christoph Schneegans" <Christoph@Schneegans.de>, <public-evangelist@w3.org>

From: "Christoph Schneegans"

|
| Dominique HazaŽl-Massieux wrote:
|
| > Wired.com announced 3 days ago that they switched to a fully
standard
| > compliant backbone:
| > http://www.wired.com/news/culture/0,1284,55675,00.html
| >
| > [...]
| >
| > (this very page has actually a small HTML error, ...
|
| It's written in XHTML which is not well-formed - that's worse than
HTML tag
| soup.

Strongly disagree here. I do not think that Tag Soup, including use of
Fonts, absolute sizing, improper nesting, Headers for bolding.
blockquoting for indents, and sizing is better than XHTML, even if there
are some minor items needing a change.

Of course we woud need a nice definition of what TAG soup means to apply
reasoning adequately.

On a more general approach, TAG Soup, to me, means excessive extra tags
and no organization, application of tags or elements not in the ways
which were meant.


| Furthermore, the page lacks a proper character encoding declaration,
| <meta http-equiv="Content-Type"> isn't sufficient in XHTML.

I see:
< meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"
/ >
and not the other mentioned, unless we are looking at different pages -
this is on the index.html
page that I see this.

| And constructs  like
|   <a href="#" onclick="setActiveStyleSheet('', 1);return false;">

Not sure where a problem with this one may be?

|   <!-- BEGIN colMain -->
|   <div id="colM">
|   <div class="content">
|   <div class="storyCap">
|   <div class="pgTitle">
|
| aren't examples for good XHTML either.

Why not on these items?
Choice of words?
Mixed case? [attribution words are not limited to lower case]
Use of class vs ID [re-usable styles for same doc page need class, one
time use per page ID]
or?

Does this page work on Text only or Lynx view and make sense?
Will an HTML doc with Tag Soup, degrade similarly for those cases, and
allow as many user options?

Interesting thoughts you posted, but I would like to hear more about why
or how this XHTML fails and why tag soup would be better?

holly
Received on Monday, 14 October 2002 09:09:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:16:17 UTC