[7264] in www-talk@info.cern.ch
Re: videomap
daemon@ATHENA.MIT.EDU (Marc VanHeyningen)
Sat Jan 21 01:11:25 1995
Date: Sat, 21 Jan 1995 06:22:29 +0100
Errors-To: listmaster@www0.cern.ch
Reply-To: mvanheyn@cs.indiana.edu
From: Marc VanHeyningen <mvanheyn@cs.indiana.edu>
To: Multiple recipients of list <www-talk@www0.cern.ch>
> The basic idea is simple. Video information is 3D in comparison to imagemap
> which is 2D. So we only need to return x,y, and t coordinates in stead of x and y
> in the imagemap case.
I think the "x,y" coordinate for imagemaps was a quick hack that should be
upgraded; it's very limiting. Extending it to video would be even more
limiting.
Newer approaches involve having the document specify a polygon which
constitute an anchor in an image, along with associated attributes (e.g.
destination URL, REL or REV tags, that sort of disposition information.)
That way, browsers can clearly indicate which part of the image is a valid link
and which is not, where it goes, whether it should pop up in a separate window
or replace what you're watching, etc.
I'd suggest extending that to video by just adding a couple of attributes to
the polygon (starting time and ending time, in frames or whatever.)
