Re: Searchable Reader-side URL Anchors ...

On Wed, Jan 16, 2002 at 09:53:32AM -0500, Mirsad Todorovac wrote:
> 
> Hi, all!
> 
> Some of you might remember how it was proposed back then in 1994 or 5 or 6
> (I don't remember exactly the year but I'm certain about the period) the
> following thing:
> 
> As we may often watn to point with our URL not to a whole new document, it
> would be nice if we could point with our URL inside document, so readers
> wouldn't have to skim through the text to find desired paragraph.
> 
> For example, I refer to http://{...}/rfc1738.txt, second chapter, third
> paragraph - the cute way to do it would be to have browser immediatelly
> open desired chapter and paragraph; without forcing user to scroll and
> find it.
> 
> Back then I proposed syntax for new type of URL with new type of anchor:
> 
> 	http://{...}/.../.../rfc1738.txt##Second%20Chapter
> 
> ... to distinguish it from #Second%20Chapter, which would in turn refer to
> a <A NAME="Second Chapter"> in HTML file (but in plaintext, as you have
> already spotted - there are no anchors).
> 
> (But I do not insist on same syntax, that didn't pass earlier, and was
> blocked - I'm promoting the issue of Reader-side anchors, not the syntax)

WN has supported somehing like this ('fragments') for a long time, see

  http://hopf.math.nwu.edu/

However, yours seem to be client-side.  How do you propose to determine
where the anchors are?

> You must remember many situations when you were refered third chapter in
> larger page, but have been diverted your attention in first or second
> chapter and started to red that, forgetting what you came for in the first
> place?

Is the third chapter the third <H1>?  Or the third <H2>?  What if
the document is not HTML?

> If so, support this initiative!
> 
> Best regards,
> Mirsad T.

-- 
Reinier Post

Received on Thursday, 24 January 2002 04:22:17 UTC