13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

1/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

3810

Help on the options is available. Revalidate

Markup Validation ServiceCheck the markup (HTML, XHTML, …) of Web documents

Jump To: Validation Output

Errors found while checking this document as XHTML 1.0 Transitional!Result: 44 Errors, 74 warning(s)

Address : http://www.defense.gov/

Encoding : utf-8 (detect automatically)

Doctype : XHTML 1.0 Transitional (detect automatically)

Root Element: htmlRoot Namespace: http://www.w3.org/1999/xhtml

The W3C validators rely on community support for hosting and development.Donate and help us build better tools for a better web.

Options

Show Source Show Outline List Messages Sequentially Group Error Messages by Type

Validate error pages Verbose Output Clean up Markup with HTML-Tidy

! TOP

Validation Output: 44 Errors

Line 60, Column 37: there is no attribute "autocomplete"

<input autocomplete= " off" class="usagov-search-autocomplete Sea…

You have used the attribute named above in your document, but the document type you are using does not support that attribute forthis element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. youmust use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as"marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will haveno supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they areboth allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the<embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Line 218, Column 71: cannot generate system identifier for general entity "w"

…ight:6px;" src="/imgHandler.ashx?h=0& w =90&img=/DODCMSShare/NewsStoryPhoto/201…

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspellingthe reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error isunencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

2/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference mayget interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and&aelig; are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to yourproblem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usuallythese will all disappear when the original problem is fixed.

Line 218, Column 71: general entity "w" not defined and no default entity

…ight:6px;" src="/imgHandler.ashx?h=0& w =90&img=/DODCMSShare/NewsStoryPhoto/201…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 72: reference not terminated by REFC delimiter

…ght:6px;" src="/imgHandler.ashx?h=0&w = 90&img=/DODCMSShare/NewsStoryPhoto/2013…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 218, Column 72: reference to external entity in attribute value

…ght:6px;" src="/imgHandler.ashx?h=0&w = 90&img=/DODCMSShare/NewsStoryPhoto/2013…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 218, Column 72: reference to entity "w" for which no system identifier could be generated

…ght:6px;" src="/imgHandler.ashx?h=0&w = 90&img=/DODCMSShare/NewsStoryPhoto/2013…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 218, Column 76: cannot generate system identifier for general entity "img"

…6px;" src="/imgHandler.ashx?h=0&w=90& i mg=/DODCMSShare/NewsStoryPhoto/2013-01/…

An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspellingthe reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error isunencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your documentyou must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference mayget interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and&aelig; are different characters.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to yourproblem.

Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usuallythese will all disappear when the original problem is fixed.

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

3/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 218, Column 76: general entity "img" not defined and no default entity

…6px;" src="/imgHandler.ashx?h=0&w=90& i mg=/DODCMSShare/NewsStoryPhoto/2013-01/…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 79: reference not terminated by REFC delimiter

…;" src="/imgHandler.ashx?h=0&w=90&img = /DODCMSShare/NewsStoryPhoto/2013-01/scr…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 218, Column 79: reference to external entity in attribute value

…;" src="/imgHandler.ashx?h=0&w=90&img = /DODCMSShare/NewsStoryPhoto/2013-01/scr…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 218, Column 79: reference to entity "img" for which no system identifier could be generated

…;" src="/imgHandler.ashx?h=0&w=90&img = /DODCMSShare/NewsStoryPhoto/2013-01/scr…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 250, Column 72: reference not terminated by REFC delimiter

…ght:6px;" src="/imgHandler.ashx?h=0&w = 90&img=/DODCMSShare/NewsStoryPhoto/2013…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 250, Column 72: reference to external entity in attribute value

…ght:6px;" src="/imgHandler.ashx?h=0&w = 90&img=/DODCMSShare/NewsStoryPhoto/2013…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 250, Column 72: reference to entity "w" for which no system identifier could be generated

…ght:6px;" src="/imgHandler.ashx?h=0&w = 90&img=/DODCMSShare/NewsStoryPhoto/2013…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

!

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

4/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 250, Column 79: reference not terminated by REFC delimiter

…;" src="/imgHandler.ashx?h=0&w=90&img = /DODCMSShare/NewsStoryPhoto/2013-01/scr…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 250, Column 79: reference to external entity in attribute value

…;" src="/imgHandler.ashx?h=0&w=90&img = /DODCMSShare/NewsStoryPhoto/2013-01/scr…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 250, Column 79: reference to entity "img" for which no system identifier could be generated

…;" src="/imgHandler.ashx?h=0&w=90&img = /DODCMSShare/NewsStoryPhoto/2013-01/scr…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 284, Column 143: end tag for "img" omitted, but OMITTAG NO was specified

…><img src="/images/2.1/icons/icon_14px_blog.png" alt="icon: DOD Live"></a > </dt>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of">".

Line 284, Column 71: start tag was here

…logs/rss_dodlive.xml" target="_blank"> < img src="/images/2.1/icons/icon_14px_bl…

Line 292, Column 174: end tag for "img" omitted, but OMITTAG NO was specified

…"/images/2.1/icons/icon_14px_blog.png" alt="icon: Armed with Science"></a > </dt>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of">".

Line 292, Column 92: start tag was here

…med_with_science.xml" target="_blank"> < img src="/images/2.1/icons/icon_14px_bl…

Line 300, Column 156: end tag for "img" omitted, but OMITTAG NO was specified

…g src="/images/2.1/icons/icon_14px_blog.png" alt="icon: Warrior Care"></a > </dt>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of">".

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

5/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 300, Column 80: start tag was here

…rss_warrior_care.xml" target="_blank"> < img src="/images/2.1/icons/icon_14px_bl…

Line 308, Column 162: end tag for "img" omitted, but OMITTAG NO was specified

…src="/images/2.1/icons/icon_14px_blog.png" alt="icon: Family Matters"></a > </dt>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of">".

Line 308, Column 84: start tag was here

…s_family_matters.xml" target="_blank"> < img src="/images/2.1/icons/icon_14px_bl…

Line 316, Column 163: end tag for "img" omitted, but OMITTAG NO was specified

…images/2.1/icons/icon_14px_blog.png" alt="icon: The Pentagon Channel"></a > </dt>

You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of">".

Line 316, Column 79: start tag was here

…dodblogs/rss_tpc.xml" target="_blank"> < img src="/images/2.1/icons/icon_14px_bl…

Line 519, Column 133: reference not terminated by REFC delimiter

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 519, Column 133: reference to external entity in attribute value

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 519, Column 133: reference to entity "w" for which no system identifier could be generated

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

6/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 519, Column 140: reference not terminated by REFC delimiter

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 519, Column 140: reference to external entity in attribute value

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 519, Column 140: reference to entity "img" for which no system identifier could be generated

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 523, Column 131: reference not terminated by REFC delimiter

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 523, Column 131: reference to external entity in attribute value

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 523, Column 131: reference to entity "w" for which no system identifier could be generated

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 523, Column 138: reference not terminated by REFC delimiter

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

!

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

7/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 523, Column 138: reference to external entity in attribute value

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 523, Column 138: reference to entity "img" for which no system identifier could be generated

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 527, Column 131: reference not terminated by REFC delimiter

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 527, Column 131: reference to external entity in attribute value

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 527, Column 131: reference to entity "w" for which no system identifier could be generated

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 527, Column 138: reference not terminated by REFC delimiter

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 527, Column 138: reference to external entity in attribute value

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

!

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

8/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 527, Column 138: reference to entity "img" for which no system identifier could be generated

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 531, Column 131: reference not terminated by REFC delimiter

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 531, Column 131: reference to external entity in attribute value

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 531, Column 131: reference to entity "w" for which no system identifier could be generated

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 531, Column 138: reference not terminated by REFC delimiter

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 531, Column 138: reference to external entity in attribute value

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

9/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 531, Column 138: reference to entity "img" for which no system identifier could be generated

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 535, Column 131: reference not terminated by REFC delimiter

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 535, Column 131: reference to external entity in attribute value

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 535, Column 131: reference to entity "w" for which no system identifier could be generated

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 535, Column 138: reference not terminated by REFC delimiter

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 535, Column 138: reference to external entity in attribute value

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 535, Column 138: reference to entity "img" for which no system identifier could be generated

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

!

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

10/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 539, Column 131: reference not terminated by REFC delimiter

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 539, Column 131: reference to external entity in attribute value

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 539, Column 131: reference to entity "w" for which no system identifier could be generated

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 539, Column 138: reference not terminated by REFC delimiter

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 539, Column 138: reference to external entity in attribute value

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 539, Column 138: reference to entity "img" for which no system identifier could be generated

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

11/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 543, Column 131: reference not terminated by REFC delimiter

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 543, Column 131: reference to external entity in attribute value

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 543, Column 131: reference to entity "w" for which no system identifier could be generated

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 543, Column 138: reference not terminated by REFC delimiter

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 543, Column 138: reference to external entity in attribute value

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 543, Column 138: reference to entity "img" for which no system identifier could be generated

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 549, Column 131: reference not terminated by REFC delimiter

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

!

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

12/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 549, Column 131: reference to external entity in attribute value

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 549, Column 131: reference to entity "w" for which no system identifier could be generated

…ank"><img src="/imgHandler.ashx?h=54&w = 82&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 549, Column 138: reference not terminated by REFC delimiter

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 549, Column 138: reference to external entity in attribute value

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 549, Column 138: reference to entity "img" for which no system identifier could be generated

…mg src="/imgHandler.ashx?h=54&w=82&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 558, Column 39: reference not terminated by REFC delimiter

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

13/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 558, Column 39: reference to external entity in attribute value

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 558, Column 39: reference to entity "w" for which no system identifier could be generated

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 558, Column 47: reference not terminated by REFC delimiter

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 558, Column 47: reference to external entity in attribute value

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 558, Column 47: reference to entity "img" for which no system identifier could be generated

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 560, Column 39: reference not terminated by REFC delimiter

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 560, Column 39: reference to external entity in attribute value

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

!

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

14/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 560, Column 39: reference to entity "w" for which no system identifier could be generated

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 560, Column 47: reference not terminated by REFC delimiter

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 560, Column 47: reference to external entity in attribute value

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 560, Column 47: reference to entity "img" for which no system identifier could be generated

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 562, Column 39: reference not terminated by REFC delimiter

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 562, Column 39: reference to external entity in attribute value

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 562, Column 39: reference to entity "w" for which no system identifier could be generated

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

!

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

15/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 562, Column 47: reference not terminated by REFC delimiter

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 562, Column 47: reference to external entity in attribute value

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 562, Column 47: reference to entity "img" for which no system identifier could be generated

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 564, Column 39: reference not terminated by REFC delimiter

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 564, Column 39: reference to external entity in attribute value

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 564, Column 39: reference to entity "w" for which no system identifier could be generated

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

16/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 564, Column 47: reference not terminated by REFC delimiter

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 564, Column 47: reference to external entity in attribute value

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 564, Column 47: reference to entity "img" for which no system identifier could be generated

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 566, Column 39: reference not terminated by REFC delimiter

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 566, Column 39: reference to external entity in attribute value

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 566, Column 39: reference to entity "w" for which no system identifier could be generated

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

17/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 566, Column 47: reference not terminated by REFC delimiter

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 566, Column 47: reference to external entity in attribute value

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 566, Column 47: reference to entity "img" for which no system identifier could be generated

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 568, Column 39: reference not terminated by REFC delimiter

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 568, Column 39: reference to external entity in attribute value

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 568, Column 39: reference to entity "w" for which no system identifier could be generated

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 568, Column 47: reference not terminated by REFC delimiter

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

!

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

18/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 568, Column 47: reference to external entity in attribute value

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 568, Column 47: reference to entity "img" for which no system identifier could be generated

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 570, Column 39: reference not terminated by REFC delimiter

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 570, Column 39: reference to external entity in attribute value

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 570, Column 39: reference to entity "w" for which no system identifier could be generated

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 570, Column 47: reference not terminated by REFC delimiter

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 570, Column 47: reference to external entity in attribute value

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

!

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

19/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 570, Column 47: reference to entity "img" for which no system identifier could be generated

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

Line 572, Column 39: reference not terminated by REFC delimiter

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 572, Column 39: reference to external entity in attribute value

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

Line 572, Column 39: reference to entity "w" for which no system identifier could be generated

<a href="/imgHandler.ashx?h=170&w= 256&img=/dodcmsshare/homepagephoto/2013-…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 70: entity was defined here

…right:6px;" src="/imgHandler.ashx?h=0 & w=90&img=/DODCMSShare/NewsStoryPhoto/20…

Line 572, Column 47: reference not terminated by REFC delimiter

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is thatyou inadvertently created an entity by failing to escape an "&" character just before this text.

Line 572, Column 47: reference to external entity in attribute value

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You willneed to escape all instances of '&' into '&amp;'.

!

!

!

!

!

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

20/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Line 572, Column 47: reference to entity "img" for which no system identifier could be generated

…href="/imgHandler.ashx?h=170&w=256&img = /dodcmsshare/homepagephoto/2013-01/hire…

This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL orbody text. See the previous message for further details.

Line 218, Column 75: entity was defined here

…:6px;" src="/imgHandler.ashx?h=0&w=90 & img=/DODCMSShare/NewsStoryPhoto/2013-01…

! TOP

Home About... News Docs Help & FAQ Feedback Contribute

This service runs the W3C Markup Validator, v1.3.COPYRIGHT © 1994-2012 W3C® (MIT, ERCIM, KEIO), ALL RIGHTS RESERVED. W3C LIABILITY, TRADEMARK,DOCUMENT USE AND SOFTWARE LICENSING RULES APPLY. YOUR INTERACTIONS WITH THIS SITE ARE IN

ACCORDANCE WITH OUR PUBLIC AND MEMBER PRIVACY STATEMENTS.

!

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

21/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

13/01/08 15:45[Invalid] Markup Validation of http://www.defense.gov/ - W3C Markup Validator

22/22 ページhttp://validator.w3.org/check?uri=http%3A%2F%2Fwww.defense.gov%2F&charset=%28detect+automatically%29&doctype=Inline&group=0