source: trunk/QA/xmlconf/eduni/errata-2e/testcases.dtd @ 450

Last change on this file since 450 was 450, checked in by cameron, 9 years ago

Include xmlconf

File size: 3.9 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!--
3    @(#)testcases.dtd   1.6 99/01/21
4    Original version copyright 1998 by Sun Microsystems, Inc.
5    All Rights Reserved.
6    Modifications copyright 1999 by OASIS.
7
8    1999-06-09 00:20
9
10    DTD describing a database of XML tests.
11
12    NOTE:  the OASIS/NIST test effort also has a DTD for its test
13    environment, but that DTD is not yet suited for automated test
14    processing.  (Among other issues, it doesn't record information
15    putting any test case into the test matrix.)  If that gets fixed,
16    it may be useful to switch over to that DTD.
17-->
18
19<!--
20    The root element of the whole collection is TESTSUITE.  While not
21    very different from TESTCASES, it must be distinguished due to
22    improper processing by IE5.
23-->
24<!ELEMENT TESTSUITE ( TESTCASES+ )>
25<!ATTLIST TESTSUITE 
26    PROFILE     CDATA           #IMPLIED
27    >
28
29<!--
30    The root element of a collection should be "TESTCASES".  It groups
31    a set of tests in a particular "PROFILE", which is descriptive.  For
32    example, a "Japanese" profile might group tests with documents
33    in standard Japanese encodings, using Japanese characters used
34    inside names and name tokens as well as inside text.  Or the
35    profile might be associated with the test supplier.
36-->
37
38<!ELEMENT TESTCASES (TEST|TESTCASES)*>
39<!ATTLIST TESTCASES
40    PROFILE     CDATA           #IMPLIED
41    >
42
43<!--
44    The body of each TEST element is its description, used
45    to evaluate the diagnostic produced on negative tests.
46    People will generally read this to evaluate whether the
47    test failed for the correct reason.
48
49    The type of (external) ENTITIES required affect the results
50    permitted for certain types of nonvalidating parsers.  In
51    some cases, errors (even well-formedness errors) can't be seen
52    without reading external parameter or general entities.
53
54    Each test has a unique ID used in diagnostics.
55
56    Tests with an OUTPUT attribute do dual duty:  not only must parsers
57    accept the test, but the data they report must also have "Second
58    Canonical Form" as found in the specified output file.  (This is
59    what James Clark titled "Canonical XML", with the addition of the
60    NOTATION declarations that all XML parsers are required to report.)
61
62    The OUTPUT3 attribute is like OUTPUT, but when sent through a
63    validating parser the data reported must have the "Third Canonical
64    Form" as found in the specified output file.  (This is Second
65    Canonical form, with declarations of unparsed ENTITY values and
66    with all ignorable whitespace removed.)
67
68    Tests apply to one or more particular SECTIONS.
69
70    Each test has a TYPE:
71    * All parsers must accept "valid" testcases.
72    * Nonvalidating parsers must also accept "invalid" testcases,
73      but validating ones must reject them.
74    * No parser should accept a "not-wf" testcase unless it's a
75      nonvalidating parser and the test contains external entities
76      that the parser doesn't read.
77    * Parsers are not required to report "errors".
78
79    Each test is in a particular XML document, with a URI.  If these
80    tests are accessed over a network, the path will be relative to
81    the base URI of the document holding the testcase.
82-->
83
84<!ELEMENT TEST (#PCDATA | EM | B)*>
85<!ATTLIST TEST
86    ENTITIES    (both|none|parameter|general)   "none"
87    ID          ID                              #REQUIRED
88    OUTPUT      CDATA                           #IMPLIED
89    OUTPUT3     CDATA                           #IMPLIED
90    SECTIONS    CDATA                           #REQUIRED
91    TYPE        (valid|invalid|not-wf|error)    #REQUIRED
92    URI         CDATA                           #REQUIRED
93    NAMESPACE   (yes|no)                        "yes"
94    >
95
96<!--
97    Really basic HTML font tweaks, to support highlighting
98    some aspects of test descriptions ...
99    EM == emphasis (e.g. italics, fun colors)
100    B == bold
101-->
102<!ELEMENT EM (#PCDATA | B)*>
103<!ELEMENT B (#PCDATA | EM)*>
Note: See TracBrowser for help on using the repository browser.