Re: Document available (Error in doc found)

"Roy T. Fielding" <fielding@avron.ICS.UCI.EDU>
Date: Fri, 14 Oct 94 15:09:22 EDT
Message-id: <9410141209.aa23287@paris.ics.uci.edu>
Reply-To: fielding@avron.ICS.UCI.EDU
Originator: html-wg@oclc.org
Sender: html-wg@oclc.org
Precedence: bulk
From: "Roy T. Fielding" <fielding@avron.ICS.UCI.EDU>
To: Multiple recipients of list <html-wg@oclc.org>
Subject: Re: Document available (Error in doc found) 
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: HTML Working Group (Private)
Earl Hood writes:

> If the document contains: 
> 
> <META EXPIRES HTTP-EQUIV="Expires">Tue, 04 Dec 1993 21:29:02 GMT</expires>
> ----------------------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> <META HTTP-EQUIV="Keywords" CONTENT="Fred, Barney">
> <META HTTP-EQUIV="Reply-to" content="fielding@ics.uci.edu (Roy Fielding)">
> 
> 
> Shouldn't it be:
> 
> <META EXPIRES HTTP-EQUIV="Expires" CONTENT="Tue, 04 Dec 1993 21:29:02 GMT">

Actually, it should either be

  <expires HTTP-EQUIV="Expires">Tue, 04 Dec 1993 21:29:02 GMT</expires>

or

  <META HTTP-EQUIV="Expires" CONTENT="Tue, 04 Dec 1993 21:29:02 GMT">

The former example was intended to demonstrate how an extended element
like EXPIRES (I think it was one of the Proposed at one time) could also
have an HTTP-EQUIV attribute.  However, I think that is now passe' and
the latter example should be used for the spec (i.e. delete the EXPIRES word).


.....Roy Fielding   ICS Grad Student, University of California, Irvine  USA
                                     <fielding@ics.uci.edu>
                     <URL:http://www.ics.uci.edu/dir/grad/Software/fielding>