W3C home > Mailing lists > Public > uri@w3.org > July 2003

Re: #foo URI references

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Wed, 09 Jul 2003 16:36:11 -0400
To: Martin Duerst <duerst@w3.org>
Cc: Graham Klyne <GK@ninebynine.org>, Paul Grosso <pgrosso@arbortext.com>, uri@w3.org
Message-ID: <87vfubl9ok.fsf@nwalsh.com>

Hash: SHA1

/ Martin Duerst <duerst@w3.org> was heard to say:
| At 18:42 03/06/27 +0100, Graham Klyne wrote:
|> I think the underlying problem is that this bit of syntax (i.e. bare
|> #frag) is overloaded, and the most useful choice of functionality
|> varies with the use.  Which suggests that a fix to satisfy everybody
|> would require more syntax, but I don't know if that's a good idea,
|> or even possible.
| 'varies with use' does not automatically imply we need more syntax.
| The two uses we know are HTML-like, where it clearly is a same-document
| reference, and RDF-like, where it is treated as being relative to the
| relevant base. These uses should be distinguishable by context.

How do you mean?

  <blort href="#foo"/>

Which context is that?

This really does look like a serious problem. Some people want #foo to
be the same as it was in 2396 and some people probably describe that
as a bug in 2396. :-)

On the whole, given the significance of the change, I think it would
be better to stick with the status quo.

                                        Be seeing you,

- -- 
Norman.Walsh@Sun.COM    | A man is not necessarily intelligent because
XML Standards Architect | he has plenty of ideas, any more than he is a
Web Tech. and Standards | good general because he has plenty of
Sun Microsystems, Inc.  | soldiers.--Chamfort
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

Received on Wednesday, 9 July 2003 16:38:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:06 UTC