W3C home > Mailing lists > Public > w3c-sgml-wg@w3.org > June 1997

Re: The importance of PUBLIC (response to NOTATIONS and DATA TYPES)

From: Dan Connolly <connolly@w3.org>
Date: Thu, 12 Jun 1997 09:19:44 -0500
Message-ID: <33A00580.2F84@w3.org>
To: "Rivers-Moore, Daniel" <daniel.rivers-moore@rivcom.com>
CC: "XML Working Group (E-mail)" <w3c-sgml-wg@w3.org>
Rivers-Moore, Daniel wrote:

>         But if the web is your only target, URLs are all you need.
>         </danconnolly>
>         Strange. I seem to remember I once clicked on a hotspot on an
> HTML page and found that the link was broken!

Such things do happen. But consider that even in that case,
you have as much information as an FPI gives you: you have
an identifier in a global context.

> I would argue that it is
> precisely _because_ public identifiers cannot be fully resolved by the
> system that they are so important.

I don't follow you. How does this make them important and/or
useful? Could you give me pointers to this discussion
you referred to?

> This means there must be
> redundancy _and_ recourse to something beyond the system. This is
> precisely what PUBLIC provides.

I agree that redundancy helps when things break. But what
recourse do FPIs provide that URLs don't? If you mean
the ISO owner registry, how is that better/different from
the DNS domain registry? If you can't access it, it's equally
useless, no? Unless you've seen the owner string before.
And I'll bet the odds are higher that the DNS domain owner
string is in your cache than that the ISO FPI string is
in your cache, because URLs are used for all sorts of
things and FPIs are only used for SGML stuff.

Dan Connolly, Architecture Domain Lead
Received on Thursday, 12 June 1997 10:25:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:25:10 UTC