W3C home > Mailing lists > Public > public-html@w3.org > January 2009

Re: ISSUE-54: doctype-legacy-compat

From: Sam Ruby <rubys@us.ibm.com>
Date: Fri, 16 Jan 2009 10:21:36 -0500
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Cc: public-html@w3.org, public-html-request@w3.org
Message-ID: <OF76965F3D.A8E2E897-ON85257540.00539C0E-85257540.0054604D@us.ibm.com>

Lachlan Hunt wrote on 01/16/2009 10:03:17 AM:
> Henri Sivonen wrote:
> > <!DOCTYPE html SYSTEM "about:sgml-compat"> would seem to fit the
> > requirements as a legacy generator alternative to <!DOCTYPE html>.
> Based on some further discussion in IRC, these are the advantages of
> using the SYSTEM identifier with an about: URI scheme.
> * Many people are already familiar with the scheme and so it's
>    memorable.  More so than, e.g., the tag: or data: URI schemes.
> * It's shorter than an equivalent http: URI would be
> * It's non-retrievable and so there's no expectation of a DTD.
> * Use of an absolute URI rather than a string like "sgml-compat" that is
>    indistinguishable from a relative URI prevents consumers that attempt
>    to retrieve DTDs from getting 404s from many servers.
> * Typing about:sgml-compat into browsers generally results in an error
>    message or blank page. This helps in pre-empting any bogus
>    rationalisations for why using this one with the URI is better than
>    <!DOCTYPE html> without the URI.
> * As Philip demonstrated earlier, using a SYSTEM identifer is generally
>    more compatible with legacy producers than a lone PUBLIC identifier.

Excellent!  Is this something everybody can live with?  If not, please
speak up.

As I tally it so far, there are strong objections to PUBLIC "" and PUBLIC
"XSLT-compat".  The objections to "legacy-compat" aren't quite as strong
and I haven't yet seen somebody say that they could not live with that.  As
I see it, the this proposal doesn't match any of the previously raised
objections, and would be preferred over legacy, provided:

1) it were optional, and that the shorter version is still considered

2) if there are any recommendations in the spec, they don't single out any
specific tool.

- Sam Ruby
Received on Friday, 16 January 2009 15:22:34 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:41 UTC