Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Character Encoding mismatch!
The character encoding specified in the HTTP header
(utf-8)
is different from the value in the <meta> element
(iso-8859-1). I will use the
value from the HTTP header
(utf-8) for this
validation.
Mismatch between Public and System identifiers in the DOCTYPE declaration
This document uses an inconsistent DOCTYPE declaration.
The Public Identifier
-//W3C//DTD HTML 4.01 Transitional//EN declares the
HTML 4.01 Transitional document type, but the associated System Identifier
http://www.w3.org/TR/html40/loose.dtd does not match this document type.
The recommended System Identifier
for HTML 4.01 Transitional is http://www.w3.org/TR/html4/loose.dtd.
The safest way to use a correct DOCTYPE declaration is to copy and paste one from the recommended list and avoid editing that part of your markup by hand.
Line 59,
Column 52:
NET-enabling start-tag requires SHORTTAG YES
<meta name="author" content="Susan McLean" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 60,
Column 54:
NET-enabling start-tag requires SHORTTAG YES
<meta name="operator" content="manoj.c.nair" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 60,
Column 54:
document type does not allow element "META" here
<meta name="operator" content="manoj.c.nair" />The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 61,
Column 55:
NET-enabling start-tag requires SHORTTAG YES
<meta name="questions" content="susan.mclean" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 61,
Column 55:
document type does not allow element "META" here
<meta name="questions" content="susan.mclean" />The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 62,
Column 43:
NET-enabling start-tag requires SHORTTAG YES
<meta name="return" content="stp" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 62,
Column 43:
document type does not allow element "META" here
<meta name="return" content="stp" />The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 63,
Column 304:
document type does not allow element "META" here
…ration (NOAA), National Environmental Satellite, Data and Information Service">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 64,
Column 127:
document type does not allow element "META" here
…on, Magnetic Field, Geomagnetic Observatory, IGRF, WMM, Models, SPIDR, Indice">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 66,
Column 49:
document type does not allow element "META" here
<meta name="questions" content="geomag.models">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 67,
Column 39:
document type does not allow element "META" here
<meta name="return" content="geomag"> The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 68,
Column 11:
end tag for element "HEAD" which is not open
</head>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 70,
Column 53:
document type does not allow element "BODY" here
<body onload="loadSetup()" bgcolor="#FFFFFF">The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 79,
Column 106:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
…r="0" bgcolor="#ffffff" cellpadding="0" cellspacing="0" summary="layout table">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 84,
Column 27:
document type does not allow element "A" here
<a href="/ngdc.html"><img src="/image/nesdisngdcleft.gif" width="440" hei…The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 85,
Column 71:
NET-enabling start-tag requires SHORTTAG YES
title="go to NOAA/NESDIS/National Geophysical Data Center home" /></a>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 91,
Column 87:
NET-enabling start-tag requires SHORTTAG YES
…="affiliate" checked="checked" value="ngdc.noaa.gov" />Search NGDC</label>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 92,
Column 64:
NET-enabling start-tag requires SHORTTAG YES
…input type="radio" name="affiliate" value="noaa.gov" />Search NOAA</label>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 93,
Column 7:
NET-enabling start-tag requires SHORTTAG YES
<br />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 94,
Column 58:
NET-enabling start-tag requires SHORTTAG YES
<input type="hidden" name="v:project" value="firstgov" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 95,
Column 51:
NET-enabling start-tag requires SHORTTAG YES
<input type="text" name="query" id="query-field"/>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 96,
Column 37:
NET-enabling start-tag requires SHORTTAG YES
<input type="submit" value=" Go " />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 104,
Column 19:
NET-enabling start-tag requires SHORTTAG YES
<br clear="all" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 108,
Column 102:
document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
… width="90%" border="0" cellpadding="0" cellspacing="0" summary="layout table">The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 112,
Column 156:
NET-enabling start-tag requires SHORTTAG YES
…"44" border="0" usemap="#geomagtopbanner" alt="Geomag top navigation banner" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 119,
Column 120:
document type does not allow element "A" here
…ational Oceanic & Atmospheric Administration" class="topnav">NOAA</a> > The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 120,
Column 143:
document type does not allow element "A" here
…tal Satellite, Data, & Information Service" class="topnav">NESDIS</a> > The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 121,
Column 122:
document type does not allow element "A" here
…tle="go to National Geophysical Data Center home" class="topnav">NGDC</a> > The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 122,
Column 120:
document type does not allow element "A" here
….shtml" title="go to the Geomagnetic Data Home" class="topnav">Geomagnetism</a>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 127,
Column 119:
document type does not allow element "A" here
…title="send comments or take a survey" class="topnav">comments</a> | The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 128,
Column 133:
document type does not allow element "A" here
…privacy, disclaimer, & copyright notices" class="topnav">privacy policy</a>The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 135,
Column 159:
NET-enabling start-tag requires SHORTTAG YES
…op" title="go to related web resources" alt="Links to related web resources" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 135,
Column 160:
character data is not allowed here
…op" title="go to related web resources" alt="Links to related web resources" />You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 136,
Column 194:
NET-enabling start-tag requires SHORTTAG YES
…NOAA's Space Weather" alt="go to NOAA's Space Weather prediction Center Now" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 137,
Column 154:
NET-enabling start-tag requires SHORTTAG YES
…tle="go to DoD World Magnetic Model WMM" alt="DoD World Magnetic Model Home" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 138,
Column 173:
NET-enabling start-tag requires SHORTTAG YES
…o models" alt="Links and descriptions of magnetic field models and software" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 139,
Column 159:
NET-enabling start-tag requires SHORTTAG YES
…p" title="go to Geomagnetic Data Home" alt="go to the Geomagnetic Data Home" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 140,
Column 164:
NET-enabling start-tag requires SHORTTAG YES
…p" title="go to declination calculator" alt="go to all data and information" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 141,
Column 158:
NET-enabling start-tag requires SHORTTAG YES
…o to frequently asked questions" alt="Answers to Frequently Asked Questions" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 142,
Column 183:
NET-enabling start-tag requires SHORTTAG YES
…ic online databases" alt="Go to the Space Physics Interactive Data Resource" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 143,
Column 157:
NET-enabling start-tag requires SHORTTAG YES
…" title="go to listing of online data" alt="Geomagnetic Data online at NGDC" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 193,
Column 300:
end tag for element "A" which is not open
…,status=no,left=425,top=200,screenX=425,screenY=200')\">City or Location</a>"; The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 230,
Column 290:
end tag for element "A" which is not open
…ocation=no,status=no,left=425,top=200,screenX=425,screenY=200')\">Degree</a>"; The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 266,
Column 292:
end tag for element "A" which is not open
…ocation=no,status=no,left=425,top=200,screenX=425,screenY=200')\">Minute</a>"; The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 302,
Column 292:
end tag for element "A" which is not open
…ocation=no,status=no,left=425,top=200,screenX=425,screenY=200')\">Second</a>"; The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 338,
Column 291:
end tag for element "A" which is not open
…location=no,status=no,left=425,top=200,screenX=425,screenY=200')\">Model</a>"; The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 374,
Column 295:
end tag for element "A" which is not open
…tion=no,status=no,left=425,top=200,screenX=425,screenY=200')\">Elevation</a>"; The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 674,
Column 21:
end tag for "FORM" omitted, but its declaration does not permit this
</td>
The next message, "start tag was here"
points to the particular instance of the tag in question); the
positional indicator points to where the validator expected you to close the
tag.
Line 670,
Column 17:
start tag was here
<form name="IgrfWmmForm" method="post" action="/geomagmodels/st……ion=no,status=no,left=425,top=200,screenX=425,screenY=200')\">Step Size:</a>"; The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 1135,
Column 15:
end tag for element "FORM" which is not open
</form>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 1279,
Column 12:
NET-enabling start-tag requires SHORTTAG YES
<br/>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 1287,
Column 12:
NET-enabling start-tag requires SHORTTAG YES
<br/>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 1304,
Column 64:
NET-enabling start-tag requires SHORTTAG YES
<input type="hidden" name="questions" value="Susan.McLean" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 1305,
Column 65:
NET-enabling start-tag requires SHORTTAG YES
<input type="hidden" name="maintained" value="manoj.c.nair" />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 1306,
Column 258:
NET-enabling start-tag requires SHORTTAG YES
…NGDC</a>><a href='http://ngdc.noaa.gov/geomag/geomag.shtml'>Geomagnetism</a>"/>The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 1324,
Column 87:
end tag for "SCRIPT" omitted, but its declaration does not permit this
…<td align=\"left\"><div class=\"smallestblue\">" + breadcrumb + "</div></td>");
The next message, "start tag was here"
points to the particular instance of the tag in question); the
positional indicator points to where the validator expected you to close the
tag.
Line 1315,
Column 6:
start tag was here
<script type="text/javascript" src="http://www.ngdc.noaa.gov/bin/ngdcdynam……<td align=\"left\"><div class=\"smallestblue\">" + breadcrumb + "</div></td>");You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:
Line 1325,
Column 27:
an attribute value must be a literal unless it contains only name characters
document.write("<td align=\"right\"><div class=\"smallestblue\">");You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1325,
Column 27:
character "\" is not allowed in the value of attribute "ALIGN"
document.write("<td align=\"right\"><div class=\"smallestblue\">");
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 1325,
Column 27:
value of attribute "ALIGN" cannot be "\"RIGHT\""; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
document.write("<td align=\"right\"><div class=\"smallestblue\">");
The value of the attribute is defined to be one of a list of possible
values but in the document it contained something that is not allowed
for that type of attribute. For instance, the “selected” attribute must be either
minimized as “selected”
or spelled out in full as “selected="selected"”; a value like
“selected="true"” is not
allowed.
Line 1325,
Column 48:
an attribute value must be a literal unless it contains only name characters
document.write("<td align=\"right\"><div class=\"smallestblue\">");You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1326,
Column 36:
an attribute value must be a literal unless it contains only name characters
document.write("questions: <a href=\"mailto:" + questions + "@noaa.gov\" title=…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1326,
Column 47:
character "+" not allowed in attribute specification list
….write("questions: <a href=\"mailto:" + questions + "@noaa.gov\" title=\"ask q……rite("</div></td></tr><tr><td colspan=\"2\"><hr class=\"smallestblue\" size=\"…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1327,
Column 49:
character "\" is not allowed in the value of attribute "COLSPAN"
…rite("</div></td></tr><tr><td colspan=\"2\"><hr class=\"smallestblue\" size=\"…
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 1327,
Column 65:
an attribute value must be a literal unless it contains only name characters
…></tr><tr><td colspan=\"2\"><hr class=\"smallestblue\" size=\"1\" noshade></td…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1327,
Column 87:
an attribute value must be a literal unless it contains only name characters
…\"2\"><hr class=\"smallestblue\" size=\"1\" noshade></td></tr></tbody></table>…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1327,
Column 138:
an attribute value must be a literal unless it contains only name characters
… noshade></td></tr></tbody></table><div align=\"center\" class=\"footltbg\">");You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1327,
Column 138:
character "\" is not allowed in the value of attribute "ALIGN"
… noshade></td></tr></tbody></table><div align=\"center\" class=\"footltbg\">");
It is possible that you violated the naming convention for this attribute.
For example, id and name attributes must begin with
a letter, not a digit.
Line 1327,
Column 138:
value of attribute "ALIGN" cannot be "\"CENTER\""; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY"
… noshade></td></tr></tbody></table><div align=\"center\" class=\"footltbg\">");
The value of the attribute is defined to be one of a list of possible
values but in the document it contained something that is not allowed
for that type of attribute. For instance, the “selected” attribute must be either
minimized as “selected”
or spelled out in full as “selected="selected"”; a value like
“selected="true"” is not
allowed.
Line 1327,
Column 155:
an attribute value must be a literal unless it contains only name characters
… noshade></td></tr></tbody></table><div align=\"center\" class=\"footltbg\">");You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1328,
Column 25:
an attribute value must be a literal unless it contains only name characters
document.write("<a href=\"/ngdc.html\" title=\"go to NGDC home\">home</a> | ");You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1328,
Column 46:
an attribute value must be a literal unless it contains only name characters
document.write("<a href=\"/ngdc.html\" title=\"go to NGDC home\">home</a> | ");You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1328,
Column 54:
"TO" is not a member of a group specified for any attribute
document.write("<a href=\"/ngdc.html\" title=\"go to NGDC home\">home</a> | ");document.write("<a href=\"/ngdc.html\" title=\"go to NGDC home\">home</a> | ");document.write("<a href=\"/ngdc.html\" title=\"go to NGDC home\">home</a> | ");document.write("<a href=\"/feedback/cust_comments.html\" title=\"send NGDC comm…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1329,
Column 64:
an attribute value must be a literal unless it contains only name characters
…"/feedback/cust_comments.html\" title=\"send NGDC comments or take a survey\" …You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1329,
Column 76:
"NGDC" is not a member of a group specified for any attribute
…ust_comments.html\" title=\"send NGDC comments or take a survey\" class=\"foot……nts.html\" title=\"send NGDC comments or take a survey\" class=\"footltbg\">co…….html\" title=\"send NGDC comments or take a survey\" class=\"footltbg\">comme……\" title=\"send NGDC comments or take a survey\" class=\"footltbg\">comments</…… title=\"send NGDC comments or take a survey\" class=\"footltbg\">comments</a>……e=\"send NGDC comments or take a survey\" class=\"footltbg\">comments</a> | ");…e=\"send NGDC comments or take a survey\" class=\"footltbg\">comments</a> | ");You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1330,
Column 25:
an attribute value must be a literal unless it contains only name characters
document.write("<a href=\"/ngdcinfo/phone.html\" class=\"footltbg\" title=\"go …You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1330,
Column 56:
an attribute value must be a literal unless it contains only name characters
…a href=\"/ngdcinfo/phone.html\" class=\"footltbg\" title=\"go to NGDC director…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1330,
Column 75:
an attribute value must be a literal unless it contains only name characters
…phone.html\" class=\"footltbg\" title=\"go to NGDC directory of contacts\">con…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1330,
Column 83:
"TO" is not a member of a group specified for any attribute
…ml\" class=\"footltbg\" title=\"go to NGDC directory of contacts\">contacts</a……class=\"footltbg\" title=\"go to NGDC directory of contacts\">contacts</a> | "……lass=\"footltbg\" title=\"go to NGDC directory of contacts\">contacts</a> | ");…lass=\"footltbg\" title=\"go to NGDC directory of contacts\">contacts</a> | ");…lass=\"footltbg\" title=\"go to NGDC directory of contacts\">contacts</a> | ");document.write("<a href=\"/ngdcinfo/onlineaccess.html\" class=\"footltbg\" titl…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1331,
Column 63:
an attribute value must be a literal unless it contains only name characters
…\"/ngdcinfo/onlineaccess.html\" class=\"footltbg\" title=\"go to data availabl…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1331,
Column 82:
an attribute value must be a literal unless it contains only name characters
…ccess.html\" class=\"footltbg\" title=\"go to data available from NGDC\">data<…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1331,
Column 90:
"TO" is not a member of a group specified for any attribute
…ml\" class=\"footltbg\" title=\"go to data available from NGDC\">data</a> | ")……ml\" class=\"footltbg\" title=\"go to data available from NGDC\">data</a> | ");…ml\" class=\"footltbg\" title=\"go to data available from NGDC\">data</a> | ");…ml\" class=\"footltbg\" title=\"go to data available from NGDC\">data</a> | ");…ml\" class=\"footltbg\" title=\"go to data available from NGDC\">data</a> | ");document.write("<a href=\"/ngdcinfo/privacy.html\" class=\"footltbg\" title=\"g…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1332,
Column 58:
an attribute value must be a literal unless it contains only name characters
…href=\"/ngdcinfo/privacy.html\" class=\"footltbg\" title=\"go to NGDC privacy,…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1332,
Column 77:
an attribute value must be a literal unless it contains only name characters
…ivacy.html\" class=\"footltbg\" title=\"go to NGDC privacy, disclaimer, and co…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1332,
Column 85:
"TO" is not a member of a group specified for any attribute
…ml\" class=\"footltbg\" title=\"go to NGDC privacy, disclaimer, and copyright ……class=\"footltbg\" title=\"go to NGDC privacy, disclaimer, and copyright notic……"footltbg\" title=\"go to NGDC privacy, disclaimer, and copyright notices\">di……title=\"go to NGDC privacy, disclaimer, and copyright notices\">disclaimers</a……\"go to NGDC privacy, disclaimer, and copyright notices\">disclaimers</a> | ")……\"go to NGDC privacy, disclaimer, and copyright notices\">disclaimers</a> | ");…\"go to NGDC privacy, disclaimer, and copyright notices\">disclaimers</a> | ");document.write("<a href=\"/education/education.html\" class=\"footltbg\" title=…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1333,
Column 61:
an attribute value must be a literal unless it contains only name characters
…f=\"/education/education.html\" class=\"footltbg\" title=\"go to education and…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1333,
Column 80:
an attribute value must be a literal unless it contains only name characters
…ation.html\" class=\"footltbg\" title=\"go to education and outreach resources…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1333,
Column 88:
"TO" is not a member of a group specified for any attribute
…ml\" class=\"footltbg\" title=\"go to education and outreach resources and lin……=\"footltbg\" title=\"go to education and outreach resources and links\">educa……ootltbg\" title=\"go to education and outreach resources and links\">education…… title=\"go to education and outreach resources and links\">education</a> | ")…… title=\"go to education and outreach resources and links\">education</a> | ");… title=\"go to education and outreach resources and links\">education</a> | ");… title=\"go to education and outreach resources and links\">education</a> | ");document.write("<a href=\"/products/ngdc_news.html\" class=\"footltbg\" title=\…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1334,
Column 60:
an attribute value must be a literal unless it contains only name characters
…ef=\"/products/ngdc_news.html\" class=\"footltbg\" title=\"go to NGDC news and…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1334,
Column 79:
an attribute value must be a literal unless it contains only name characters
…_news.html\" class=\"footltbg\" title=\"go to NGDC news and features\">news</a…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1334,
Column 87:
"TO" is not a member of a group specified for any attribute
…html\" class=\"footltbg\" title=\"go to NGDC news and features\">news</a> | ");…html\" class=\"footltbg\" title=\"go to NGDC news and features\">news</a> | ");…html\" class=\"footltbg\" title=\"go to NGDC news and features\">news</a> | ");…html\" class=\"footltbg\" title=\"go to NGDC news and features\">news</a> | ");…html\" class=\"footltbg\" title=\"go to NGDC news and features\">news</a> | ");document.write("<a href=\"/products/ngdc_products.html\" class=\"footltbg\" tit…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1335,
Column 64:
an attribute value must be a literal unless it contains only name characters
…"/products/ngdc_products.html\" class=\"footltbg\" title=\"go to data products…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1335,
Column 83:
an attribute value must be a literal unless it contains only name characters
…ducts.html\" class=\"footltbg\" title=\"go to data products available from NGD…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1335,
Column 91:
"TO" is not a member of a group specified for any attribute
…ml\" class=\"footltbg\" title=\"go to data products available from NGDC\">prod……class=\"footltbg\" title=\"go to data products available from NGDC\">products<……footltbg\" title=\"go to data products available from NGDC\">products</a> | ");…footltbg\" title=\"go to data products available from NGDC\">products</a> | ");…footltbg\" title=\"go to data products available from NGDC\">products</a> | ");…footltbg\" title=\"go to data products available from NGDC\">products</a> | ");document.write("<a href=\"/sitemap/sitemap.html\" class=\"footltbg\" title=\"go…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1336,
Column 57:
an attribute value must be a literal unless it contains only name characters
… href=\"/sitemap/sitemap.html\" class=\"footltbg\" title=\"go to an index of t…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1336,
Column 76:
an attribute value must be a literal unless it contains only name characters
…temap.html\" class=\"footltbg\" title=\"go to an index of the NGDC Web site\">…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1336,
Column 84:
"TO" is not a member of a group specified for any attribute
…ml\" class=\"footltbg\" title=\"go to an index of the NGDC Web site\">site map……" class=\"footltbg\" title=\"go to an index of the NGDC Web site\">site map</a……lass=\"footltbg\" title=\"go to an index of the NGDC Web site\">site map</a>");…lass=\"footltbg\" title=\"go to an index of the NGDC Web site\">site map</a>");…lass=\"footltbg\" title=\"go to an index of the NGDC Web site\">site map</a>");…lass=\"footltbg\" title=\"go to an index of the NGDC Web site\">site map</a>");…lass=\"footltbg\" title=\"go to an index of the NGDC Web site\">site map</a>");…lass=\"footltbg\" title=\"go to an index of the NGDC Web site\">site map</a>");…ocument.write("maintained by: <a href=\"mailto:" + maintained + "@noaa.gov\" t…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1338,
Column 51:
character "+" not allowed in attribute specification list
…te("maintained by: <a href=\"mailto:" + maintained + "@noaa.gov\" title=\"cont…document.write("<a href=\"http://validator.w3.org/check/referer\" title=\"exter…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1339,
Column 73:
an attribute value must be a literal unless it contains only name characters
…alidator.w3.org/check/referer\" title=\"external link to www.w3.org html valid…You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 1339,
Column 89:
"LINK" is not a member of a group specified for any attribute
…check/referer\" title=\"external link to www.w3.org html validator\">html 4.01……ck/referer\" title=\"external link to www.w3.org html validator\">html 4.01</a……eferer\" title=\"external link to www.w3.org html validator\">html 4.01</a> ");…eferer\" title=\"external link to www.w3.org html validator\">html 4.01</a> ");…eferer\" title=\"external link to www.w3.org html validator\">html 4.01</a> "); </script> The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 1346,
Column 9:
NET-enabling start-tag requires SHORTTAG YES
<hr />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 1348,
Column 9:
NET-enabling start-tag requires SHORTTAG YES
<br />The sequence <FOO /> can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag <FOO (with an implied '>'). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.
Line 1352,
Column 10:
end tag for element "DIV" which is not open
</div>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 1353,
Column 8:
end tag for element "TD" which is not open
</td>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 1354,
Column 7:
end tag for element "TR" which is not open
</tr>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 1355,
Column 9:
end tag for element "TBODY" which is not open
</tbody>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 1356,
Column 8:
end tag for element "TABLE" which is not open
</table>The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 1363,
Column 11:
end tag for "CENTER" omitted, but its declaration does not permit this
</body>
The next message, "start tag was here"
points to the particular instance of the tag in question); the
positional indicator points to where the validator expected you to close the
tag.
Line 1143,
Column 51:
start tag was here
<center>The results will appear below.<center> </body>
The next message, "start tag was here"
points to the particular instance of the tag in question); the
positional indicator points to where the validator expected you to close the
tag.
Line 1143,
Column 13:
start tag was here
<center>The results will appear below.<center>