Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 206,
Column 158:
cannot generate system identifier for general entity "os_id"
…php?_action=katalog2/osoby/pokazOsobe&os_id=112753">Adamczyk, Michal (Universi…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 206,
Column 158:
general entity "os_id" not defined and no default entity
…php?_action=katalog2/osoby/pokazOsobe&os_id=112753">Adamczyk, Michal (Universi…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 206,
Column 163:
reference to entity "os_id" for which no system identifier could be generated
…action=katalog2/osoby/pokazOsobe&os_id=112753">Adamczyk, Michal (University of…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 206,
Column 157:
entity was defined here
….php?_action=katalog2/osoby/pokazOsobe&os_id=112753">Adamczyk, Michal (Univers……tenkarte.show_vcard?pPersonenGruppe=3&pPersonenId=1F94550D61861782">Bierbaumer…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 266,
Column 162:
general entity "pPersonenId" not defined and no default entity
…tenkarte.show_vcard?pPersonenGruppe=3&pPersonenId=1F94550D61861782">Bierbaumer…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 266,
Column 173:
reference to entity "pPersonenId" for which no system identifier could be generated
…ow_vcard?pPersonenGruppe=3&pPersonenId=1F94550D61861782">Bierbaumer, Peter (Ka…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 266,
Column 161:
entity was defined here
…itenkarte.show_vcard?pPersonenGruppe=3&pPersonenId=1F94550D61861782">Bierbaume……struttura/strutturasmst.asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 428,
Column 142:
general entity "persona" not defined and no default entity
…struttura/strutturasmst.asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 428,
Column 149:
reference to entity "persona" for which no system identifier could be generated
…ra/strutturasmst.asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&titolo=…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 428,
Column 141:
entity was defined here
…/struttura/strutturasmst.asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena……rutturasmst.asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&titolo=Prof.…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 428,
Column 154:
general entity "nome" not defined and no default entity
…rutturasmst.asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&titolo=Prof.…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 428,
Column 158:
reference to entity "nome" for which no system identifier could be generated
…urasmst.asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&titolo=Prof.ssa"…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 428,
Column 153:
entity was defined here
…trutturasmst.asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&titolo=Prof……asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&titolo=Prof.ssa">Dossena…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 428,
Column 166:
general entity "cognome" not defined and no default entity
…asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&titolo=Prof.ssa">Dossena…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 428,
Column 173:
reference to entity "cognome" for which no system identifier could be generated
…rica=1&persona=246&nome=Marina&cognome=Dossena&titolo=Prof.ssa">Dossena, Marin…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 428,
Column 165:
entity was defined here
….asp?rubrica=1&persona=246&nome=Marina&cognome=Dossena&titolo=Prof.ssa">Dossen……rsona=246&nome=Marina&cognome=Dossena&titolo=Prof.ssa">Dossena, Marina (Univer…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 428,
Column 182:
general entity "titolo" not defined and no default entity
…rsona=246&nome=Marina&cognome=Dossena&titolo=Prof.ssa">Dossena, Marina (Univer…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 428,
Column 188:
reference to entity "titolo" for which no system identifier could be generated
…246&nome=Marina&cognome=Dossena&titolo=Prof.ssa">Dossena, Marina (University o…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 428,
Column 181:
entity was defined here
…ersona=246&nome=Marina&cognome=Dossena&titolo=Prof.ssa">Dossena, Marina (Unive……tructura/personal?p_departamento=1882&p_profesor=35142">Esteve Ramos, Mar&iacu…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 466,
Column 163:
general entity "p_profesor" not defined and no default entity
…tructura/personal?p_departamento=1882&p_profesor=35142">Esteve Ramos, Mar&iacu…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 466,
Column 173:
reference to entity "p_profesor" for which no system identifier could be generated
…ersonal?p_departamento=1882&p_profesor=35142">Esteve Ramos, María Jos&e…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 466,
Column 162:
entity was defined here
…structura/personal?p_departamento=1882&p_profesor=35142">Esteve Ramos, Mar&iac……ttps://www.dlls.univr.it/?ent=persona&id=455">Facchinetti, Roberta (University…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 480,
Column 121:
general entity "id" not defined and no default entity
…ttps://www.dlls.univr.it/?ent=persona&id=455">Facchinetti, Roberta (University…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 480,
Column 123:
reference to entity "id" for which no system identifier could be generated
…ps://www.dlls.univr.it/?ent=persona&id=455">Facchinetti, Roberta (University o…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 480,
Column 120:
entity was defined here
…https://www.dlls.univr.it/?ent=persona&id=455">Facchinetti, Roberta (Universit……il-fak.uni-koeln.de/index.php?id=7050&L=9">Kohnen, Tanja (University of Cologn…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 688,
Column 141:
general entity "L" not defined and no default entity
…il-fak.uni-koeln.de/index.php?id=7050&L=9">Kohnen, Tanja (University of Cologn…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 688,
Column 142:
reference to entity "L" for which no system identifier could be generated
…l-fak.uni-koeln.de/index.php?id=7050&L=9">Kohnen, Tanja (University of Cologne…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 688,
Column 140:
entity was defined here
…hil-fak.uni-koeln.de/index.php?id=7050&L=9">Kohnen, Tanja (University of Colog……cnrs.fr/annuaires/index.asp?Langue=EN&Page=Diana%20LEWIS">Lewis, Diana M. (Uni…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 744,
Column 144:
general entity "Page" not defined and no default entity
…cnrs.fr/annuaires/index.asp?Langue=EN&Page=Diana%20LEWIS">Lewis, Diana M. (Uni…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 744,
Column 148:
reference to entity "Page" for which no system identifier could be generated
….fr/annuaires/index.asp?Langue=EN&Page=Diana%20LEWIS">Lewis, Diana M. (Univers…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 744,
Column 143:
entity was defined here
….cnrs.fr/annuaires/index.asp?Langue=EN&Page=Diana%20LEWIS">Lewis, Diana M. (Un……action=katalog2/osoby/pokazOsobe&os_id=100135&lang=en">Mokrowiecki, Tomasz (Ad…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 206,
Column 157:
entity was defined here
….php?_action=katalog2/osoby/pokazOsobe&os_id=112753">Adamczyk, Michal (Univers……gv.edu/aa/dm/index.cfm?action=profile&user=john.newman">Newman, John (Universi…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 892,
Column 139:
general entity "user" not defined and no default entity
…gv.edu/aa/dm/index.cfm?action=profile&user=john.newman">Newman, John (Universi…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 892,
Column 143:
reference to entity "user" for which no system identifier could be generated
…du/aa/dm/index.cfm?action=profile&user=john.newman">Newman, John (University o…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 892,
Column 138:
entity was defined here
…rgv.edu/aa/dm/index.cfm?action=profile&user=john.newman">Newman, John (Univers…</dl>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.
Line 997,
Column 135:
cannot generate system identifier for general entity "ver"
…c.es/index.php?pagina=merodriguez.dfm&ver=inicio">Rodríguez Gil, Mar&ia…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 997,
Column 135:
general entity "ver" not defined and no default entity
…c.es/index.php?pagina=merodriguez.dfm&ver=inicio">Rodríguez Gil, Mar&ia…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 997,
Column 138:
reference to entity "ver" for which no system identifier could be generated
…s/index.php?pagina=merodriguez.dfm&ver=inicio">Rodríguez Gil, Mar&iacut…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 997,
Column 134:
entity was defined here
…gc.es/index.php?pagina=merodriguez.dfm&ver=inicio">Rodríguez Gil, Mar&i……ww.uis.no/article.php?articleID=74071&categoryID=11198">Thengs, Kjetil Vikhama…An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded 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 you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
Line 1137,
Column 129:
general entity "categoryID" not defined and no default entity
…ww.uis.no/article.php?articleID=74071&categoryID=11198">Thengs, Kjetil Vikhama…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 1137,
Column 139:
reference to entity "categoryID" for which no system identifier could be generated
…article.php?articleID=74071&categoryID=11198">Thengs, Kjetil Vikhamar (Univers…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 1137,
Column 128:
entity was defined here
…www.uis.no/article.php?articleID=74071&categoryID=11198">Thengs, Kjetil Vikham…</dl>Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.
