Page lifespan?

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

I found some details on a musical festival, made my plans, and only found
out by chance that the site was two years out of date.

Is there some HTML way of setting a lifespan on a webpage on creation so
that, should the creator neglect to remove it, browsers will not render it?

If not should such a mechanism exist?
Perhaps with page expired message?

David F. Cox

Re: Page lifespan?

Quoted text here. Click to load it


Quoted text here. Click to load it


Yes. The author should heep the web page up to date. Then again some web
pages last a very very long time. The HTML specs for instance.


Re: Page lifespan?

David Cox wrote:

Quoted text here. Click to load it

Removing a site is rather a bad idea, even when it's "obsolete".
The solution is to date documents and clearly display the date at the top  
of the page.
Then, people who find it, will immediately see the context, and may still  
find it valuable.
If the site maintainer is nice, he may even update the site when the  
festival is over, and diplay clearly a banner: "Event passed -- this event  
is now kept for historical purposes only".

Quoted text here. Click to load it

For simple server side removal:

If you're the creator, this only depends on your server-side tools.
You may write a Web server that automatically removes old documents (a  
pretty bad idea).

If you're not the creator, and you think the contents of the page should  
be removed, send a mail to the webmaster.

For a user-agent:
There's no standard HTTP header field for telling the user agent that the  
page is obsolete.
You may search with google for an HTTP extension, or define your own  
"X-Obsolete-after: date-time;" HTTP header field.

More simply, you may write a user-agent which recognizes the hCalendar  
microformat, and doesn't load the page, or display a big red warning, if  
all events in the calendar have passed. If may also display a different  
type of warning, if some events are currently running.
Of course, the page author has to use an hCalendar.
It's impossible to automatically get the end date information if the  
author didn't specify it somewhere.

I didn't write any Firefox extension (so I cannot tell what can or cannot  
be done with it), but that *might* be feasible with a Firefox extension.


Re: Page lifespan?

André Gillibert wrote:

Quoted text here. Click to load it

I can agree with leaving the page there, from a page I found, on research
that would take 5 years, and the page was 5 years old.  Should be ready
right now (it wasn't.)  But that fact wasn't clearly stated anywhere,
although I did find it.

Doug L.
The art of being wise is the art of knowing what to overlook.
   - William James.

Re: Page lifespan?

On Sep 1, 8:25 am, "Andr=E9 Gillibert"
Quoted text here. Click to load it

And then there are the Marketing Types out there who insist on putting
some silly script into their pages that inserts the current date no
matter when the page is viewed, to give it an illusion of being up-to-
date when it may actually be long obsolete.  The death penalty would
be appropriate for such people.


Re: Page lifespan?

On 9/1/2007 4:32 AM, David Cox wrote:
Quoted text here. Click to load it

Per RFC 2616, it is possible to set an expiration date for a page.  This
can be done via
<META HTTP-EQUIV="expires" CONTENT="Wed, 26 Feb 2008 08:21:57 GMT">

However, that has no real effect on the existence of the page.  It only
affects caching.


David E. Ross
< .

The only reason we have so many laws is that not enough people will do
the right thing.  (© 1997)

Re: Page lifespan?

Quoted text here. Click to load it

I might have guessed that the situation would be worse than I had feared. We
have an "expires" provision, but the neither the page or some of its content

David Cox

Site Timeline