Re: Suggestion: ALTHREF attribute

jptxs (
Fri, 16 Jan 1998 10:07:31 -0500

Message-Id: <>
Date: Fri, 16 Jan 1998 10:07:31 -0500
To: James Green <>
From: jptxs <>
In-Reply-To: <>
Subject: Re: Suggestion: ALTHREF attribute

James Green wrote: 
If you think about this closely, it does sound as if a new META element 
is being thought of:

</snip> and <snip>
Further mirrors could be included:

HREF2="" HREF3="">

You get the general idea.</snip>

this all sounds great, but i think it could even be taken a step further.
there could be a kind of "server side" HTML doc that had a whole list of
options for the client such as different languages, abridged versions,
versions of the same materials at different server locations.  I'm not
really sure what the server side should be--now people do this sort of
thing with Javascript and Perl.  It's possible that it may even be able to
be pushed into CSS, seeing how some of these would effect the 'style' of
the document.

>The only problem it does not solve is if the source document itself 
>cannot be retrieved for some reason or another.

true, but there's not much to be done about that.

>Whilst this could work, it strays from usability quite wildly. The only 
>place it could be used is essentially in the corporate and professional 
>world. Certainly, web pages would increase in size and therefore 
>downloading times

with the instructions on the server, one could say that the document is not
growing in size, but it does mean that the client has to hit the server
again for another document--essentially losing some time.  but i'm apt to
think that it would be less time than trying to parse all that info into
the document.


"Bigamy is having one spouse too many.  
 Monogamy is the same."