<?xml version='1.0' encoding='UTF-8'?>

<TESTCASES PROFILE='OASIS/NIST TESTS, 1-Nov-1998'>

  <TEST TYPE='valid' SECTIONS='2.2 [1]'

      ID='o-p01pass2' URI='p01pass2.xml'>

     various Misc items where they can occur

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.3 [6]'

      ID='o-p06pass1' URI='p06pass1.xml'>

     various satisfactions of the Names production in a NAMES

    attribute

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.3 [7]'

      ID='o-p07pass1' URI='p07pass1.xml'>

     various valid Nmtoken 's in an attribute list declaration.

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.3 [8]'

      ID='o-p08pass1' URI='p08pass1.xml' NAMESPACE='no'>

     various satisfaction of an NMTOKENS attribute value.

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.3 [9]'

      ID='o-p09pass1' ENTITIES="parameter" URI='p09pass1.xml'>

     valid EntityValue's.  Except for entity references,

              markup is not recognized.

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.3 [12]'

      ID='o-p12pass1' URI='p12pass1.xml'>

     valid public IDs.

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 [22]'

      ID='o-p22pass4' URI='p22pass4.xml'>

     XML decl and doctypedecl

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 [22]'

      ID='o-p22pass5' URI='p22pass5.xml'>

     just doctypedecl

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 [22]'

      ID='o-p22pass6' URI='p22pass6.xml'>

     S between decls is not required

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.1 [43] [44]'

      ID='o-p28pass1' URI='p28pass1.xml'>

    Empty-element tag must be used for element which are declared EMPTY.     </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 4.1 [28] [69]'

      ID='o-p28pass3' ENTITIES="parameter" URI='p28pass3.xml'>

    Valid doctypedecl with Parameter entity reference.  The declaration of a parameter entity must precede any reference to it.     </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 4.2.2 [28] [75]'

      ID='o-p28pass4' ENTITIES="parameter" URI='p28pass4.xml'>

    Valid doctypedecl with ExternalID as an External Entity declaration.     </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 4.1 [28] [69]'

      ID='o-p28pass5' ENTITIES="parameter" URI='p28pass5.xml'>

    Valid doctypedecl with ExternalID as an External Entity.  A parameter entity reference is also used.     </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 [29]'

      ID='o-p29pass1' URI='p29pass1.xml'>

     Valid types of markupdecl.

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 4.2.2 [30] [75]'

      ID='o-p30pass1' ENTITIES="parameter" URI='p30pass1.xml'>

    Valid doctypedecl with ExternalID as an External Entity.  The external entity has an element declaration.     </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 4.2.2 4.3.1 [30] [75] [77]'

      ID='o-p30pass2' ENTITIES="parameter" URI='p30pass2.xml'>

    Valid doctypedecl with ExternalID as an Enternal Entity.  The external entity begins with a Text Declaration.     </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 [31]'

      ID='o-p31pass1' ENTITIES="parameter" URI='p31pass1.xml'>

     external subset can be empty

    </TEST>

  <TEST TYPE='valid' SECTIONS='2.8 3.4 4.2.2 [31] [62] [63] [75]'

      ID='o-p31pass2' ENTITIES="parameter" URI='p31pass2.xml'>

    Valid doctypedecl with EXternalID as Enternal Entity.  The external entity contains a parameter entity reference and condtional sections.</TEST>

  <TEST TYPE='valid' SECTIONS='2.4 2.5 2.6 2.7 [15] [16] [18]'

      ID='o-p43pass1' URI='p43pass1.xml'>

    Valid use of character data, comments, processing instructions and CDATA sections within the start and end tag.     </TEST>

  <TEST TYPE='valid' SECTIONS='3.2 [45]'

      ID='o-p45pass1' URI='p45pass1.xml'>

     valid element declarations

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.2 3.2.1 3.2.2 [45] [46] [47] [51]'

      ID='o-p46pass1' URI='p46pass1.xml'>

    Valid use of contentspec, element content models, and mixed content within an element type declaration.     </TEST>

  <TEST TYPE='valid' SECTIONS='3.2 3.2.1 [45] [46] [47] '

      ID='o-p47pass1' URI='p47pass1.xml'>

    Valid use of contentspec, element content models, choices, sequences and content particles within an element type declaration.  The optional character following a name or list governs the number of times the element or content particle may appear.     </TEST>

  <TEST TYPE='valid' SECTIONS='3.2 3.2.1 [45] [46] [47]'

      ID='o-p48pass1' URI='p48pass1.xml'>

    Valid use of contentspec, element content models, choices, sequences and content particles within an element type declaration.  The optional character following a name or list governs the number of times the element or content particle may appear.    </TEST>

  <TEST TYPE='valid' SECTIONS='3.2 3.2.1 [45] [46] [47]'

      ID='o-p49pass1' URI='p49pass1.xml'>

    Valid use of contentspec, element content models, choices, and content particles within an element type declaration.  The optional character following a name or list governs the number of times the element or content particle may appear.  Whitespace is also valid between choices.   </TEST>

  <TEST TYPE='valid' SECTIONS='3.2 3.2.1 [45] [46] [47]'

      ID='o-p50pass1' URI='p50pass1.xml'>

    Valid use of contentspec, element content models, sequences and content particles within an element type declaration.  The optional character following a name or list governs the number of times the element or content particle may appear.  Whitespace is also valid between sequences.   </TEST>

  <TEST TYPE='valid' SECTIONS='3.2.2 [51]'

      ID='o-p51pass1' URI='p51pass1.xml'>

     valid Mixed contentspec's.

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.3 [52]'

      ID='o-p52pass1' URI='p52pass1.xml'>

     valid AttlistDecls: No AttDef's are required,

    and the terminating

          S is optional, multiple ATTLISTS per element are OK, and multiple

          declarations of the same attribute are OK.

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.3 [53]'

      ID='o-p53pass1' URI='p53pass1.xml'>

     a valid AttDef

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.3.1 [54]'

      ID='o-p54pass1' URI='p54pass1.xml'>

     the three kinds of attribute types

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.3.1 [55]'

      ID='o-p55pass1' URI='p55pass1.xml'>

     StringType = "CDATA"

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.3.1 [56]'

      ID='o-p56pass1' URI='p56pass1.xml'>

     the 7 tokenized attribute types

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.3.1 [57]'

      ID='o-p57pass1' URI='p57pass1.xml'>

     enumerated types are NMTOKEN or NOTATION lists

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.3.1 [58]'

      ID='o-p58pass1' URI='p58pass1.xml'>

     NOTATION enumeration has on or more items

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.3.1 [59]'

      ID='o-p59pass1' URI='p59pass1.xml'>

     NMTOKEN enumerations haveon or more items

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.3.2 [60]'

      ID='o-p60pass1' URI='p60pass1.xml'>

     the four types of default values

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.4 [61]'

      ID='o-p61pass1' ENTITIES="parameter" URI='p61pass1.xml'>

     valid conditional sections are INCLUDE and IGNORE

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.4 [62]'

      ID='o-p62pass1' ENTITIES="parameter" URI='p62pass1.xml'>

     valid INCLUDE sections -- options S before and

    after keyword, sections can nest

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.4 [63]'

      ID='o-p63pass1' ENTITIES="parameter" URI='p63pass1.xml'>

     valid IGNORE sections

    </TEST>

  <TEST TYPE='valid' SECTIONS='3.4 [64]'

      ID='o-p64pass1' ENTITIES="parameter" URI='p64pass1.xml'>

     IGNOREd sections ignore everything except section delimiters

    </TEST>

  <TEST TYPE='valid' SECTIONS='4.1 [68]'

      ID='o-p68pass1' URI='p68pass1.xml'>

     Valid entity references.  Also ensures that a charref to

          '&' isn't interpreted as an entity reference open delimiter

    </TEST>

  <TEST TYPE='valid' SECTIONS='4.1 [69]'

      ID='o-p69pass1' ENTITIES="parameter" URI='p69pass1.xml'>

     Valid PEReferences.

    </TEST>

  <TEST TYPE='valid' SECTIONS='4.2 [70]'

      ID='o-p70pass1' URI='p70pass1.xml'>

     An EntityDecl is either a GEDecl or a PEDecl

    </TEST>

  <TEST TYPE='valid' SECTIONS='4.2 [71]'

      ID='o-p71pass1' URI='p71pass1.xml'>

     Valid GEDecls

    </TEST>

  <TEST TYPE='valid' SECTIONS='4.2 [72]'

      ID='o-p72pass1' URI='p72pass1.xml'>

     Valid PEDecls

    </TEST>

  <TEST TYPE='valid' SECTIONS='4.2 [73]'

      ID='o-p73pass1' URI='p73pass1.xml'>

     EntityDef is either Entity value or an external id,

    with an optional NDataDecl

    </TEST>

  <TEST TYPE='valid' SECTIONS='4.2.2 [76]'

      ID='o-p76pass1' URI='p76pass1.xml'>

     valid NDataDecls

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.1 [1]'

      ID='o-p01pass1' URI='p01pass1.xml'>

     no prolog

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.1 [1]'

      ID='o-p01pass3' URI='p01pass3.xml'>

     Misc items after the document

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.3 [3]'

      ID='o-p03pass1' URI='p03pass1.xml'>

     all valid S characters

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.3 [4]'

      ID='o-p04pass1' URI='p04pass1.xml' NAMESPACE='no'>

     names with all valid ASCII characters, and one from each

              other class in NameChar

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.3 [5]'

      ID='o-p05pass1' URI='p05pass1.xml' NAMESPACE='no'>

     various valid Name constructions

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.3 [6]'

      ID='o-p06fail1' URI='p06fail1.xml'>

     Requires at least one name.

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.3 [8]'

      ID='o-p08fail1' URI='p08fail1.xml'>

     at least one Nmtoken is required.

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.3 [8]'

      ID='o-p08fail2' URI='p08fail2.xml'>

     an invalid Nmtoken character.

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.3 [10]'

      ID='o-p10pass1' URI='p10pass1.xml'>

     valid attribute values

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.4 [14]'

      ID='o-p14pass1' URI='p14pass1.xml'>

     valid CharData

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.5 [15]'

      ID='o-p15pass1' URI='p15pass1.xml'>

     valid comments

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.6 [16] [17]'

      ID='o-p16pass1' URI='p16pass1.xml'>

    Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.6 [16]'

      ID='o-p16pass2' URI='p16pass2.xml'>

    Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.6 [16]'

      ID='o-p16pass3' URI='p16pass3.xml'>

    Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.7 [18]'

      ID='o-p18pass1' URI='p18pass1.xml'>

     valid CDSect's.  Note that a CDStart in a CDSect is not

              recognized as such

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [22]'

      ID='o-p22pass1' URI='p22pass1.xml'>

     prolog can be empty

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [22]'

      ID='o-p22pass2' URI='p22pass2.xml'>

     XML declaration only

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [22]'

      ID='o-p22pass3' URI='p22pass3.xml'>

     XML decl and Misc

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [23]'

      ID='o-p23pass1' URI='p23pass1.xml'>

    Test shows a valid XML declaration along with version info.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [23]'

      ID='o-p23pass2' URI='p23pass2.xml'>

    Test shows a valid XML declaration along with encoding declaration.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [23]'

      ID='o-p23pass3' URI='p23pass3.xml'>

    Test shows a valid XML declaration along with Standalone Document Declaration.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [23]'

      ID='o-p23pass4' URI='p23pass4.xml'>

    Test shows a valid XML declaration, encoding declarationand Standalone Document Declaration.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [24]'

      ID='o-p24pass1' URI='p24pass1.xml'>

    Test shows a prolog that has the VersionInfo delimited by double quotes.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [24]'

      ID='o-p24pass2' URI='p24pass2.xml'>

    Test shows a prolog that has the VersionInfo delimited by single quotes.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [24]'

      ID='o-p24pass3' URI='p24pass3.xml'>

    Test shows whitespace is allowed in prolog before version info.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [24]'

      ID='o-p24pass4' URI='p24pass4.xml'>

    Test shows whitespace is allowed in prolog on both sides of equal sign.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [25]'

      ID='o-p25pass1' URI='p25pass1.xml'>

    Test shows whitespace is NOT necessary before or after equal sign of versioninfo.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [25]'

      ID='o-p25pass2' URI='p25pass2.xml'>

    Test shows whitespace can be used on both sides of equal sign of versioninfo.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [26]'

      ID='o-p26pass1' URI='p26pass1.xml'>

     The valid version number.  We cannot test others because

              a 1.0 processor is allowed to fail them.

    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [27]'

      ID='o-p27pass1' URI='p27pass1.xml'>

    Comments are valid as the Misc part of the prolog.    </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [27]'

      ID='o-p27pass2' URI='p27pass2.xml'>

    Processing Instructions are valid as the Misc part of the prolog.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [27]'

      ID='o-p27pass3' URI='p27pass3.xml'>

    Whitespace is valid as the Misc part of the prolog.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.8 [27]'

      ID='o-p27pass4' URI='p27pass4.xml'>

    A combination of comments, whitespaces and processing instructions are valid as the Misc part of the prolog.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.9 [32]'

      ID='o-p32pass1' URI='p32pass1.xml'>

    Double quotes can be used as delimeters for the value of a Standalone Document Declaration.     </TEST>

  <TEST TYPE='invalid' SECTIONS='2.9 [32]'

      ID='o-p32pass2' URI='p32pass2.xml'>

    Single quotes can be used as delimeters for the value of a Standalone Document Declaration.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3 3.1 [39] [44]'

      ID='o-p39pass1' URI='p39pass1.xml'>

    Empty element tag may be used for any element which has no content.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3 3.1 [39] [43]'

      ID='o-p39pass2' URI='p39pass2.xml'>

    Character data is valid element content.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [40]'

      ID='o-p40pass1' URI='p40pass1.xml'>

    Elements content can be empty.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [40]'

      ID='o-p40pass2' URI='p40pass2.xml'>

    Whitespace is valid within a Start-tag.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [40] [41]'

      ID='o-p40pass3' URI='p40pass3.xml'>

    Attributes are valid within a Start-tag.    </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [40]'

      ID='o-p40pass4' URI='p40pass4.xml'>

    Whitespace and Multiple Attributes are valid within a Start-tag.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [41]'

      ID='o-p41pass1' URI='p41pass1.xml'>

    Attributes are valid within a Start-tag.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [41]'

      ID='o-p41pass2' URI='p41pass2.xml'>

    Whitespace is valid within a Start-tags Attribute.    </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [42]'

      ID='o-p42pass1' URI='p42pass1.xml'>

    Test shows proper syntax for an End-tag.    </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [42]'

      ID='o-p42pass2' URI='p42pass2.xml'>

    Whitespace is valid after name in End-tag.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [44]'

      ID='o-p44pass1' URI='p44pass1.xml'>

    Valid display of an Empty Element Tag.    </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [44]'

      ID='o-p44pass2' URI='p44pass2.xml'>

    Empty Element Tags can contain an Attribute.    </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [44]'

      ID='o-p44pass3' URI='p44pass3.xml'>

    Whitespace is valid in an Empty Element Tag following the end of the attribute value.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [44]'

      ID='o-p44pass4' URI='p44pass4.xml'>

    Whitespace is valid after the name in an Empty Element Tag.     </TEST>

  <TEST TYPE='invalid' SECTIONS='3.1 [44]'

      ID='o-p44pass5' URI='p44pass5.xml'>

    Whitespace and Multiple Attributes are valid in an Empty Element Tag.    </TEST>

  <TEST TYPE='invalid' SECTIONS='4.1 [66]'

      ID='o-p66pass1' URI='p66pass1.xml'>

     valid character references

    </TEST>

  <TEST TYPE='invalid' SECTIONS='4.2 [74]'

      ID='o-p74pass1' URI='p74pass1.xml'>

     PEDef is either an entity value or an external id

    </TEST>

  <TEST TYPE='invalid' SECTIONS='4.2.2 [75]'

      ID='o-p75pass1' URI='p75pass1.xml'>

     valid external identifiers

    </TEST>

  <TEST TYPE='invalid' SECTIONS='3.3.1 [58] [59] Errata [E2]'

      ID='o-e2' URI='e2.xml'>

      Validity Constraint:  No duplicate tokens 

    </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.1 [1]'

      ID='o-p01fail1' URI='p01fail1.xml'>

     S cannot occur before the prolog

    </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.1 [1]'

      ID='o-p01fail2' URI='p01fail2.xml'>

     comments cannot occur before the prolog

    </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.1 [1]'

      ID='o-p01fail3' URI='p01fail3.xml'>

     only one document element

    </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.1 [1]'

      ID='o-p01fail4' URI='p01fail4.xml'>

     document element must be complete.

    </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail1' URI='p02fail1.xml'>

    Use of illegal character within XML document.     </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail10' URI='p02fail10.xml'>

    Use of illegal character within XML document.     </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail11' URI='p02fail11.xml'>

    Use of illegal character within XML document.     </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail12' URI='p02fail12.xml'>

    Use of illegal character within XML document.     </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail13' URI='p02fail13.xml'>

    Use of illegal character within XML document.     </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail14' URI='p02fail14.xml'>

    Use of illegal character within XML document.     </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail15' URI='p02fail15.xml'>

    Use of illegal character within XML document.     </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail16' URI='p02fail16.xml'>

    Use of illegal character within XML document.     </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail17' URI='p02fail17.xml'>

    Use of illegal character within XML document.     </TEST>

  <TEST TYPE='not-wf' SECTIONS='2.2 [2]'

      ID='o-p02fail18' URI='p02fail18.xml'>

    Use of illegal character within XML document.     </TEST>