W3C home > Mailing lists > Public > uri@w3.org > March 2004

Re: FW: fragment prose proposal

From: Tony Hammond <thammond_2004@hotmail.com>
Date: Mon, 01 Mar 2004 15:09:26 +0000
To: derhoermi@gmx.net
Cc: uri@w3.org
Message-ID: <BAY15-F46ePSygqhvyV0002b89c@hotmail.com>

One would expect a broswer to understand a generic URI string /in context/. 
E.g. a browser could see something like

  <a href="this-is:a-uri-string"/>

and recognize (al teast) that this was a valid URI, albeit it may have no 
clue how to dereference it. But it could at least take some kind of action 
(popup window, or changing the presentation semantics of the link) rather 
than imply that this is in any way defective (unregistered, 
undereferenceable, etc).

And of course it should also recognize that

  <a href="this-is*not:a-uri-string"/>


>From: Bjoern Hoehrmann <derhoermi@gmx.net>
>To: tony@tonyhammond.net
>CC: uri@w3.org
>Subject: Re: FW: fragment prose proposal
>Date: Sun, 29 Feb 2004 14:54:15 +0100
>* Tony Hammond wrote:
> >>The open source applications don't seem to have any
> >>of the problems you describe.
> >
> >Not sure wat you mean by 'open source applications' here. I've never seen 
> >browser yet that understood what a generic URI is, be it mozilla, 
> >etc.
>How would a browser "understand" a "generic URI"?

Tired of 56k? Get a FREE BT Broadband connection 
Received on Monday, 1 March 2004 10:10:22 UTC

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