Re: A Proposal from the Disabled Access Community wrote:
> >> compatibility problems. However I note that most browsers ignore a
> >> nonexistent fragment id so:
> >>
> >>     http://www.bogus/etc.html#foobar
> >>
> >> would position to the beginning of the document if there is no foobar
> >> anchor. Overloading # for this use would thus provide graceful fallback
> >
> >I never thought of that, that has some great promise!!
> >Do others agree that it could work??
> I can't speak for anyone else. :-) I think you meant to send this message
> to www-html, but you actually sent it just to me. I'm sending this
> message back to the list.
> >>     http://www.bogus/etc.html#foo#bar
> >
> >Can they be made to be that flexible?
> Yes they can.

Yes, in fact, in the XML working group, we're investigating
similar mechanisms. See[1]:

[1] Extensible Markup Language (XML):
                Part 2. Hypertext Links
W3C Working Draft March-31-97
5.3 TEI Extended Pointers

Using that sort of thing, I would suggest


Hmmm... the PATTERN keyword[2] seems to be part of the TEI
extended pointer syntax that isn't in xml-link --
at least not yet!

[1] The PATTERN Keyword

> But will this actually get implemented by browsers is a
> different question.

Whether support for XML mechanisms migrates into HTML
user agents is an open question.

The relavent HTML working draft is at:
Hypertext Links in HTML
           W3C Working Draft 28-Mar-97

To evaluate the W3C stragy for HTML and XML, stay tuned to:
W3C Activity: Hypertext Markup Language (HTML)

W3C Activity: Generic SGML

Dan Connolly, W3C Architecture Domain Lead
<> +1 512 310-2971
PGP:EDF8 A8E4 F3BB 0F3C FD1B 7BE0 716C FF21

Received on Wednesday, 30 April 1997 01:53:57 UTC