Input: [ID] 17 [Commenter] Detlev Fisher Kathleen Wahlbin (in questionnaire) [Location] 3.3.2 Step 3.b: Include Exemplar Instances of Web Pages - Requirement 3b [Status] Closed [Priority] Medium [Current Text] Requirement 3.b: At least two distinct web pages (where applicable) of each (1) key functionality, (2) content, design, and functionality, and (3) web technologies shall be part of the selected sample of web pages. [Rationale] One page per feature may be fine if the pages are nearly identical in structure and content. I believe that it must be down to the site exploration and the actual variation found whether one, two or more pages should be selected. Following this rule strictly it would greatly increase the number of pages in the sample (and in turn, effort) often with only marginal benefits. [Resolution] Resolution: Open an issue to "Discuss number of webpages for requirement 3.b", and ask specifically for comments on this section when we publish the draft for public comments Rationale: This issue requires more thought and discussion [Suggested Change]

Output: I would drop the requirement to have two distinct pages if what is meant is necessarily have two instances of page based on the same template. Instead I would put more emphasis than currently in evidence on exploring (and selecting, documenting) different *page states* (expanded menus, light boxes, tab panels, inserted error handling messages, etc)

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 18 [Commenter] Detlev Fisher [Location] 3.3.4 Step 3.d: Include Complete Processes in the Sample [Status] Closed [Priority] High [Current Text] Requirement 3.d: All web pages that are part of a complete process shall be included. The selected sample must include all web pages that belong to a series of web pages presenting a complete process. Also, no web page in the selected sample may be part of a process without all other web pages that are part of that process to be also included into the selected sample. [Rationale] Evaluating many near-identical process pages would be a waste of time. [Resolution] Resolution: No Change Resolution: To know this, it is necessary to do evaluation. Repetition is already covered in the Note in section 3.4 Step 4. [Suggested Change]

Output: Add a note: "Note: Including all pages of a process in the selected sample is not necessary when process steps are repetitive and based on the same template. For example, an online questionnaire may lead the user through dozens of multiple choice questions, each containing four radio buttons and based on the same template. In such case, including one of these pages in the selected sample would be sufficient."

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012

Listing of the comments for Section 3 - Conformance Evaluation Procedure and their proposed resolutions


Input: [ID] 19 [Commenter] Richard Warren and Kerstin Probiesch (in questionnaire) [Location] 3.4 Step 4: Audit the Selected Sample [Status] Closed [Priority] High [Current Text] Audit the Selected Sample [Rationale] We agreed that full audits were the default position [Resolution] Resolution: No change Rationale: Several places throughout the document explain that the sample can be the entire website (see resolution for comment ID14). The suggested change to the title adds considerable complexity for fairly few situations. [Suggested Change]

Output: Title should read 'Audit the site or the selected sample'. Change also every reference to this section in other sections.

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 20 [Commenter] Detlev Fisher [Location] 3.4 Step 4: Audit the Selected Sample - Note [Status] Closed [Priority] High [Current Text] Note at the end of the section [Rationale] I would argue that the assessment of WCAG SC should be carried out for each page in the sample [...] [Resolution] Resolution: No change Rationale: 3.4 Step 4 already states: "WCAG 2.0 defines five conformance requirements that need to be met for each web page in the sample [...] This includes checking whether each WCAG 2.0 Success Criterion in the target conformance level [...] has been met or not met for each of these web pages" [Suggested Change]

Output: All SC should be rated for all pages in the selected sample. Comments may be included just once and referenced from other places having the same issue.

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 21 [Commenter] Richard Warren (in questionnaire) [Location] 3.4 Step 4: Audit the Selected Sample - The penultimate sentence of the Note: for step 4 [Status] Closed [Priority] High [Current Text] evaluator may not need to continue to identify successes and failures in meeting the conformance target for each web page. [Rationale] The note refers to repetitive content. At present this sentence reads "evaluator may not need to continue to identify successes and failures in meeting the conformance target for each web page." This is a little ambiguous and could be taken to include none-repetitive content. [Resolution] Resolution: Change as suggested Rationale: Clarifies the intended meaning [Suggested Change]

Output: Change to add phrase "repetitive elements" and read as follows: "evaluator may not need to continue to identify successes and failures in meeting the conformance target for these repetitive elements on every web page."

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 22 [Commenter] Detlev Fisher Aurélien Levy (in questionnaire) [Location] 3.4 Step 4a: Check for the Broadest Variety of Use Cases - Requirement 4.a, Note 1 [Status] Closed [Priority] High [Current Text] Note: According to WCAG 2.0, Success Criteria that do not apply to the content are deemed to have been met. [Rationale] Whether WCAG-EM should include 'not applicable' as rating option has been discussed at length in a previous EVAL-TF teleconference and I remember there was a sound majority in favour of it. [Resolution] Previous resolution: Change note to read "Note: According to WCAG 2.0, Success Criteria that do not apply to the content are deemed to have been satisfied. An outcome such as 'Not Applicable' may be used to denote the particular situation where Success Criteria were satisfied because no relevant content was applicable", and add link to the definition of "satisfy" in WCAG2.0 Updated resolution: Further refine the note in response to WCAG WG Comment #19 to read "Note: According to WCAG 2.0, Success Criteria to which there is no matching content are deemed to have been satisfied. An outcome such as 'Not Applicable' may be used to denote the particular situation where Success Criteria were satisfied because no relevant content was applicable", and add link to the definition of "satisfy" in WCAG2.0 Rationale: Clarifies the use of terms such as 'Not Applicable' [Suggested Change]

Output: Note: While according to WCAG 2.0, Success Criteria that do not apply to the content are deemed to be satisfied, evaluators are free to set those Success Criteria to 'not applicable' since this differentiation can be highly meaningful for clients and other users of the evalution results.

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 24 [Commenter] Detlev Fisher [Location] 3.4 Step 4a: Check for the Broadest Variety of Use Cases - Requirement 4.a, Note 2 [Status] Closed [Priority] Medium [Current Text] Second Note (at the end of the section) [Rationale] I do not see how one would evaluate the template on its own, instead of a particular instance with all content rendered as web page. Therefore I find the whole paragraph rather confusing. The point included in my suggested revision is different: cut out repetition if some issue has already been explained on another page in the sample. [Resolution] Resolution: Change note to "Templates are often used to create many web pages, sometimes entire parts a website. While evaluating templates is optional in this methodology, in some contexts it can be helpful to check templates on their own. Evaluating templates may identify potential issues that may not be easily identified through evaluating individual instances of web pages. However, issues identified in templates alone do not necessarily imply that these issues occur on the website and need to be validated on individual instances of web pages. Also, identifying no issues in templates does not necessarily imply that no issues occur on on individual instances of web pages" Rationale: Some of the previous references to templates are removed per comment ID13a, so that this note may become more valuable. Evaluating templates on their own helps understand how a website is contructed and identify potential issues that are not easy to identify otherwise. See discussion thread on "templates" and Minutes from 30 August Telco for change from "usually" to "often" in the resolution [Suggested Change]

Output: "Many websites are based on templates. Evaluating one page based on a particular template can identify accessibility issues pertinent also to other pages based on the same template. When evaluating further pages based on the same template and the same template issue is found, Success Criteria ratings and comments may simply refer to other pages in the sample where the issue has already been covered."

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 25 [Commenter] Kerstin Probiesch and Aurélien Levy (in questionnaire) [Location] 3.4.2 Step 4.b: Use WCAG 2.0 Techniques Where Possible [Status] Closed [Priority] High [Current Text] Use WCAG 2.0 Techniques Where Possible [Rationale] As 3.1.5 Step 1.e is optional this step must be optional too. Furthermore without making it optional some of current wcag evaluation methodology such as Accessiweb, RGAA, UWEM,etc will fail to conform to WCAG-EM [Resolution] Resolution: Add "(Optional)" to the current title Rationale: It is understood that the use of techniques is optional [Suggested Change]

Output: Use WCAG 2.0 Techniques test procedure Where Possible (optional)

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 26 [Commenter] Richard Warren (in questionnaire) [Location] 3.4.2 Step 4.b: Use WCAG 2.0 Techniques Where Possible- Requirement 4.b [Status] Closed [Priority] High [Current Text] Requirement 4.b: "Where possible, WCAG 2.0 techniques shall be used to demonstrate successes and failures in meeting the WCAG 2.0 Success Criteria relevant per 3.1.3 Step 1.c: Define the Conformance Target." [Rationale] It is still not clear that if the evaluator can identify the correct use of WCAG techniques then these can be used by the evaluator as evidence of compliance. I suggest that the wording be changed. This means that the evaluator can confirm compliance if the appropriate technique has been correctly applied without having to do any other test. For example: if the label element has been applied to enclose both the field instruction and the input field then there is no need to check manually if the form progresses properly when using the keyboard or can work in forms mode with a screen reader. [Resolution] Resolution: Change to "Where possible, applicable WCAG 2.0 techniques shall be used to demonstrate successes and failures [...]" Rationale: "Common Failure" techniques can also be used to demonstrate *not* met Success Criteria [Suggested Change]

Output: Requirement 4.b: "Where the correct use of appropriate WCAG 2.0 techniques can be identified they can be used to demonstrate successes in meeting the WCAG 2.0 Success Criteria."

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 28 [Commenter] Kerstin Probiesch (in questionnaire) [Location] 3.4.2 Step 4.b: Use WCAG 2.0 Techniques Where Possible- Requirement 4b [Status] Closed [Priority] High [Current Text] In this case the evaluator must determine whether the WCAG 2.0 Success Criteria are met without the use of techniques. [Rationale] The sentence is unclear. Reason: there is no way to build a web page without using techniques. [Resolution] Previous resolution: Change to "In this case the evaluator must determine whether the WCAG 2.0 Success Criteria are met without the use of documented techniques." Previous rationale: Clarifies that we are refering to a particular use of the term 'techniques' (as per WCAG 2.0) Updated resolution: Comment addressed per changes in response to Comment #29 Updated rationale: The entire section has been rewritten so that particular comments is no longer applicable; however, the rationale of the comment has been principally accepted and integrated into the rewrite for the section [Suggested Change]

Output: Rewrite the sentence and the section and make it optional.

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 29 [Commenter] Detlev Fisher [Location] 3.4.2 Step 4.b: Use WCAG 2.0 Techniques Where Possible- Requirement 4b, first bullet point [Status] Closed [Priority] Medium [Current Text] Second paragraph, including bullet list [Rationale] Several rationale provided in the comment [Resolution] Resolution: We added an editor note with brief description of what we are looking for to step 1e to ask for public review on this section and open an issue to discuss this issue further after publication. Note: See suggestion for editorial improvements to 3.1.5 Step 1.e and 3.4.2 Step 4.b Rationale: Comments mostly accepted but wording such as "evidence" have not been directly adopted as proposed. See for final decision: EvalTF minutes of 30 August 2012 [Suggested Change]

Output: Complete rewording provided in the comment

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 30 [Commenter] Detlev Fisher [Location] 3.4.2 Step 4.b: Use WCAG 2.0 Techniques Where Possible- Requirement 4b, end of last but one paragraph [Status] Closed [Priority] Mild [Current Text] Otherwise it is good practice (for efficacy and justifiability) to use existing techniques to demonstrate successes and failures in meeting WCAG 2.0 Success Criteria. [Rationale] This is in substance a repetition of the intitial statement that (WCAG Techniques) "..provide an effective way of demonstrating whether WCAG 2.0 Success Criteria are met or not met." 'Justifiability' seems the wrong term - what is meant is that refering to the success or failure of using a WCAG Technique (established through its test) provides evidence for the conformance judgement of the evaluator. Also not sure whether referring to the matching WCAG Technique makes anything more 'efficacious' [...] [Resolution] Resolution: Removed as suggested Rationale: Agreement with the rationale provided Note: See also the changes to this sectuib in response to Comment #29 [Suggested Change]

Output: Delete the sentence.

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 31 [Commenter] Richard Warren (in questionnaire) [Location] 3.4.3 Step 4.c: Assess Accessibility Support for Technologies - Requirement 4c [Status] Closed [Priority] High [Current Text] Each use of the web technologies used to create the web page content shall be checked to be accessibility supported by the tools defined in Step 1.d:. [Rationale] We are not evaluating the tools etc used to create the site (e.g Dreamweaver, Joomla, Websphere etc). We are checking the technologies used to deliver the content to the user. For example if scripts are used to display content such as warnings (and we have note specified in step 1d that all users will have scripting enabled) will the content still display if scripting is not enabled ? [Resolution] Resolution: Changed as suggested Rationale: Clarifies the intended meaning [Suggested Change]

Output: Change word 'create' to 'present' in the requirement statement as follows: "Requirement 4.c: Each use of the web technologies used to present the web page content shall be checked to be accessibility supported by the tools defined in Step 1.d:".

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [ID] 32 [Commenter] Aurélien Levy (in questionnaire) [Location] 3.5.2 Step 5.b: Provide an Accessibility Statement (Optional) [Status] Closed [Priority] High [Current Text] The website owner commits to removing any valid issues known to them within 10 business days; [Rationale] Why 10 days? In some situations it can take longer to get something fixed on some big corporate or ministerial website. [Resolution] Resolution: Changed to "The website owner commits to ensuring the accuracy and validity of the accessibility statement"; See current discussion thread on "accessibility statements". Also: Changed Accessibility Statement (Optional)" to " Provide an Accessibility Evaluation Statement @@@ According to this Methodology (Optional)" in 4 september 2012 Editor Draft. Rationale: Remediation action is beyond the scope of an evaluation methodology [Suggested Change]

Output: The website owner commits to give feedback on any valid issues known to them within 5 business days; This feedback should containt a detailed planning of remediation or an alternative way to get access to the information

Disposition of Comments from Eval TF Review - WCAG-EM Editor Draft 30 July 2012


Input: [id] i1 [title] HTTP Version should be case sensitive [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i3 [title] Chunk Size Definition [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i5 [title] Via is a MUST [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i6 [title] Fragments allowed in Location [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i10 [title] Safe Methods vs Redirection [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i11 [title] URI includes query [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i12 [title] Invalidation after Update or Delete [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i14 [title] Clarification regarding quoting of charset values [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i15 [title] No close on 1xx responses [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i17 [title] Revise description of the POST method [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i18 [title] Cache validators in 206 responses [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i25 [title] Accept-Encoding BNF [target] RFC2616 [draft] 04 [type]

Output: design


Input: [id] i31 [title] qdtext BNF [target] RFC2616 [draft] 04 [type]

Output: design


Input: [id] i62 [title] Whitespace in quoted-pair [target] RFC2616 [type]

Output: design


Input: [id] i2 [title] 'unsafe' characters [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i4 [title] Message Length [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i7 [title] Editors Notes [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i8 [title] Media type registrations [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i9 [title] Trailer [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i16 [title] Remove 'identity' token references [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i26 [title] Import query BNF [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i42 [title] RFC2606 compliance [target] RFC2616 [draft] 02 [type]

Output: editorial


Input: [id] i44 [title] Unneeded references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i45 [title] RFC977 reference [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i46 [title] references to RFC1700 [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i47 [title] inconsistency in date format explanation [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i48 [title] Date reference typo [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i49 [title] Connection header text [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i65 [title] Informative references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i66 [title] ISO-8859-1 Reference [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i68 [title] Encoding References Normative [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i84 [title] Redundant cross-references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i86 [title] Normative up-to-date references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i87 [title] typo in 13.2.2 [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [Erratum] E1 [Bugzilla] 4372 [Category] substantive [Description]

Output: This erratum places constraints on the type of string that is valid for the doctype-public attribute of xsl:output.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E2 [Bugzilla] 4557 [Category] editorial [Description]

Output: This erratum corrects an editorial error concerning the number of phases of serialization.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E3 [Bugzilla] 5066 [Category] editorial [Description]

Output: This erratum corrects an editorial error concerning the currently registered XHTML media types.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E4 [Bugzilla] 5433 [Category] substantive [Description]

Output: This erratum clarifies how descendant elements of an XML island must be serialized according to the HTML output method.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E5 [Bugzilla] 5439 [Category] substantive [Description]

Output: This erratum aligns the description of the effect of the include-content-type serialization parameter of the HTML output method with that of the XHTML output method.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E6 [Bugzilla] 5458 [Category] substantive [Description]

Output: This erratum ensures that the sequence normalization process preserves any type annotations associated with nodes in the input sequence.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E7 [Bugzilla] 5300 [Category] substantive [Description]

Output: This erratum clarifies how elements with empty content models are to be serialized under the HTML and XHTML output methods.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E8 [Bugzilla] 5441 [Category] substantive [Description]

Output: This erratum ensures that Unicode normalization applies to all characters that might be adjacent in the serialized result produced by the text output method, including those that are in text nodes that are separated by element nodes in the data model instance.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E9 [Bugzilla] 5993 [Category] substantive [Description]

Output: This erratum makes previously non-normative text that describes how the xhtml and html output methods must behave if the indent parameter has the value yes into normative text.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E10 [Bugzilla] 6466 [Category] substantive [Description]

Output: This erratum specifies the syntactic constraints on the values of the doctype-public and doctype-system serialization parameters.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Erratum] E11 [Bugzilla] 6376 [Category] editorial [Description]

Output: This erratum makes clear which parts of the recommendation are not considered to be normative.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [id] i1 [target] RFC2616 [type] design [draft] 01 [title]

Output: HTTP Version should be case sensitive


Input: [id] i3 [target] RFC2616 [type] design [draft] 01 [title]

Output: Chunk Size Definition


Input: [id] i5 [target] RFC2616 [type] design [draft] 01 [title]

Output: Via is a MUST


Input: [id] i6 [target] RFC2616 [type] design [draft] 01 [title]

Output: Fragments allowed in Location


Input: [id] i10 [target] RFC2616 [type] design [draft] 01 [title]

Output: Safe Methods vs Redirection


Input: [id] i11 [target] RFC2616 [type] design [draft] 01 [title]

Output: URI includes query


Input: [id] i12 [target] RFC2616 [type] design [draft] 01 [title]

Output: Invalidation after Update or Delete


Input: [id] i14 [target] RFC2616 [type] design [draft] 01 [title]

Output: Clarification regarding quoting of charset values


Input: [id] i15 [target] RFC2616 [type] design [draft] 01 [title]

Output: No close on 1xx responses


Input: [id] i17 [target] RFC2616 [type] design [draft] 01 [title]

Output: Revise description of the POST method


Input: [id] i18 [target] RFC2616 [type] design [draft] 01 [title]

Output: Cache validators in 206 responses


Input: [id] i25 [target] RFC2616 [type] design [draft] 04 [title]

Output: Accept-Encoding BNF


Input: [id] i31 [target] RFC2616 [type] design [draft] 04 [title]

Output: qdtext BNF


Input: [id] i62 [target] RFC2616 [type] design [title]

Output: Whitespace in quoted-pair


Input: [id] i2 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: 'unsafe' characters


Input: [id] i4 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: Message Length


Input: [id] i7 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: Editors Notes


Input: [id] i8 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Media type registrations


Input: [id] i9 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: Trailer


Input: [id] i16 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: Remove 'identity' token references


Input: [id] i26 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Import query BNF


Input: [id] i42 [target] RFC2616 [type] editorial [draft] 02 [title]

Output: RFC2606 compliance


Input: [id] i44 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Unneeded references


Input: [id] i45 [target] RFC2616 [type] editorial [draft] 03 [title]

Output: RFC977 reference


Input: [id] i46 [target] RFC2616 [type] editorial [draft] 03 [title]

Output: references to RFC1700


Input: [id] i47 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: inconsistency in date format explanation


Input: [id] i48 [target] RFC2616 [type] editorial [draft] 03 [title]

Output: Date reference typo


Input: [id] i49 [target] RFC2616 [type] editorial [draft] 03 [title]

Output: Connection header text


Input: [id] i65 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Informative references


Input: [id] i66 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: ISO-8859-1 Reference


Input: [id] i68 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Encoding References Normative


Input: [id] i84 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Redundant cross-references


Input: [id] i86 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Normative up-to-date references


Input: [id] i87 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: typo in 13.2.2


Input: [#] 1 [Test case] | all | header | cookie | cookie-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Simple document with EXI Cookie


Input: [#] 2 [Test case] | all | header | schemaId | builtinElementGrammar | builtin.toSchemaInformed-00 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Built-in root tag with a schema-informed child element


Input: [#] 3 [Test case] | all | header | blockSize | blockSize-00 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Block size = 1 with a document containing 100 values


Input: [#] 4 [Test case] | all | header | blockSize | blockSize-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Block size = 100 with a document containing 100 values


Input: [#] 5 [Test case] | all | header | blockSize | blockSize-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Block size = 100 with a document containing 99 values


Input: [#] 6 [Test case] | all | header | blockSize | blockSize-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Block size = unbounded with a document containing 100 values


Input: [#] 7 [Test case] | all | header | blockSize | blockSize-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Block size = unbounded with a document containing 99 values


Input: [#] 8 [Test case] | all | header | blockSize | blockSize-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Block size = unbounded with a document containing 200 values


Input: [#] 9 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag


Input: [#] 10 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM before root tag


Input: [#] 11 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI before root tag


Input: [#] 12 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM before root tag


Input: [#] 13 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI before root tag


Input: [#] 14 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM after root tag


Input: [#] 15 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI after root tag


Input: [#] 16 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM after root tag


Input: [#] 17 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI after root tag


Input: [#] 18 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-10 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD


Input: [#] 19 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-11 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: DTD with SYSTEM


Input: [#] 20 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-12 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD with SYSTEM


Input: [#] 21 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-13 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: HTML DTD declaration


Input: [#] 22 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-14 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Mix of CM, PI and DTD


Input: [#] 23 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag


Input: [#] 24 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM before root tag


Input: [#] 25 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI before root tag


Input: [#] 26 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM before root tag


Input: [#] 27 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI before root tag


Input: [#] 28 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM after root tag


Input: [#] 29 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI after root tag


Input: [#] 30 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM after root tag


Input: [#] 31 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI after root tag


Input: [#] 32 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-10 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD


Input: [#] 33 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-11 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: DTD with SYSTEM


Input: [#] 34 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-12 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD with SYSTEM


Input: [#] 35 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-13 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: HTML DTD declaration


Input: [#] 36 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-14 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Mix of CM, PI and DTD


Input: [#] 37 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag


Input: [#] 38 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM before root tag


Input: [#] 39 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI before root tag


Input: [#] 40 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM before root tag


Input: [#] 41 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI before root tag


Input: [#] 42 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM after root tag


Input: [#] 43 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI after root tag


Input: [#] 44 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM after root tag


Input: [#] 45 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI after root tag


Input: [#] 46 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-10 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD


Input: [#] 47 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-11 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: DTD with SYSTEM


Input: [#] 48 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-12 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD with SYSTEM


Input: [#] 49 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-13 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: HTML DTD declaration


Input: [#] 50 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-14 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Mix of CM, PI and DTD


Input: [#] 51 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag


Input: [#] 52 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM before root tag


Input: [#] 53 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI before root tag


Input: [#] 54 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM before root tag


Input: [#] 55 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI before root tag


Input: [#] 56 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM after root tag


Input: [#] 57 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI after root tag


Input: [#] 58 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM after root tag


Input: [#] 59 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI after root tag


Input: [#] 60 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-10 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD


Input: [#] 61 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-11 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: DTD with SYSTEM


Input: [#] 62 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-12 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD with SYSTEM


Input: [#] 63 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-13 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: HTML DTD declaration


Input: [#] 64 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-14 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Mix of CM, PI and DTD


Input: [#] 65 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag


Input: [#] 66 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM before root tag


Input: [#] 67 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI before root tag


Input: [#] 68 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM before root tag


Input: [#] 69 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI before root tag


Input: [#] 70 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM after root tag


Input: [#] 71 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI after root tag


Input: [#] 72 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM after root tag


Input: [#] 73 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI after root tag


Input: [#] 74 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-10 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD


Input: [#] 75 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-11 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: DTD with SYSTEM


Input: [#] 76 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-12 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD with SYSTEM


Input: [#] 77 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-13 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: HTML DTD declaration


Input: [#] 78 [Test case] | all | header | builtinDocumentGrammar | builtin.doc-14 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Mix of CM, PI and DTD


Input: [#] 79 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Attribute uses with optional attributes present


Input: [#] 80 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Attribute uses with optional attributes omitted


Input: [#] 81 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Attribute uses with optional attributes and elements omitted


Input: [#] 82 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use of TypeEmpty in Complex Type Grammar


Input: [#] 83 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use of wildcard attribute with {namespace constraint} ##any


Input: [#] 84 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use of wildcard attribute with {namespace constraint} being a set of namespace names


Input: [#] 85 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use of wildcard attribute with {namespace constraint} ##other


Input: [#] 86 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-17 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use of a declared AT(*) to capture a globally-defined attribute with a valid value


Input: [#] 87 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-18 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use of a undeclared AT(*) [untyped value] to capture a globally-defined attribute with an invalid value


Input: [#] 88 [Test case] | all | header | complexTypeGrammar | initialEntries | schemaInformed.declared.complexType-19 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: URIs in specified namespace wildcards get in uri partition of the string table


Input: [#] 89 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-20 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Complex type of which {content type} is a simple type


Input: [#] 90 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-21 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Complex type of which {content type} is a particle


Input: [#] 91 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-22 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Complex type of which {content type} is empty


Input: [#] 92 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-23 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Complex type of which {content type} is a particle


Input: [#] 93 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-24 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use of xsi:type in a full-fledged complex type grammar


Input: [#] 94 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-25 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use AT(goo:*) where both AT(xsi:type) and AT(xsi:nil) are available.


Input: [#] 95 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-26 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use of xsi:nil in a full-fledged complex type grammar


Input: [#] 96 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-27 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use AT(goo:*) where there are no attribute uses available


Input: [#] 97 [Test case] | all | header | complexTypeGrammar | schemaInformed.declared.complexType-28 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Attribute uses that use local attributes. AT(aK) is typed as xsd:positiveInteger, whereas AT(foo:aK) is typed as xsd:date.


Input: [#] 98 [Test case] | all | header | fragment | schemaInformed.declared.fragment-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Tests the production order in fragment grammars. 1st part of event codes should take 4 bits when pis and comments are both preserved.


Input: [#] 99 [Test case] | all | header | fragment | schemaInformed.declared.fragment-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Tests the production order in fragment grammars. 1st part of event codes should take only 3 (instead of 4) bits when neither pis nor comments are preserved.


Input: [#] 100 [Test case] | all | header | fragment | schemaInformed.declared.fragment-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: There are 3 declarations of the element name 'foo:A' all of which use the same type. The same is true for the element name 'foo:B'.


Input: [#] 101 [Test case] | all | header | fragment | schemaInformed.declared.fragment-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: There are 5 declarations of the element name 'foo:A' the types of which vary. The same is true for the element name 'foo:B'.


Input: [#] 102 [Test case] | all | header | fragment | schemaInformed.declared.fragment-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: There are 3 declarations of the element name 'foo:A' all of which use the same type but with different nillability. The same is true for the element name 'foo:B'.


Input: [#] 103 [Test case] | all | header | fragment | schemaInformed.declared.fragment-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: There are 3 declarations of the element name 'foo:A' all of which use the same type with the same nillability 'true'. The same is true for the element name 'foo:B'.


Input: [#] 104 [Test case] | all | header | dtrMap | dtr-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Decimal mapped to string


Input: [#] 105 [Test case] | all | header | dtrMap | dtr-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Doubles mapped to decimal


Input: [#] 106 [Test case] | all | header | dtrMap | dtr-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Bounded integers to string


Input: [#] 107 [Test case] | all | header | dtrMap | dtr-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Several representation map in the derivation chains


Input: [#] 108 [Test case] | all | header | selfContained | builtinElementGrammar | builtin.sc-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Tests SC event type. String table and grammars have to be saved upon SC occurrences.


Input: [#] 109 [Test case] | all | header | selfContained | builtinElementGrammar | builtin.sc-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Tests SC event type with prefix preservation turned on. String table and grammars have to be saved upon SC occurrences.


Input: [#] 110 [Test case] | all | header | selfContained | addingProductionsDefault | schemaInformed.undeclared.sc-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Tests SC event type. String table and grammars have to be saved upon SC occurrences.


Input: [#] 111 [Test case] | all | header | selfContained | addingProductionsDefault | schemaInformed.undeclared.sc-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Tests SC event type with prefix preservation turned on. String table and grammars have to be saved upon SC occurrences.


Input: [#] 112 [Test case] | all | header | metadata | header.userDefinedMetadata-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Use of user defined meta-data


Input: [#] 113 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.ch-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag with CH


Input: [#] 114 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.ch-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag with an element child and then a CH


Input: [#] 115 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.ch-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Document with a CH element repeated several times


Input: [#] 116 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.ch-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Document with an element with mixed content repeated several times


Input: [#] 117 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.ch-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Document with an empty element repeated several times


Input: [#] 118 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.ch-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Document with an element with either CH or EE repeated several times


Input: [#] 119 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.ch-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Document with an element with either CH, elements or EE repeated several times


Input: [#] 120 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag


Input: [#] 121 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag with a child element


Input: [#] 122 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag with a child element


Input: [#] 123 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag with a child element


Input: [#] 124 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Promotion of a specific SE(qname) within StartTagContent grammar


Input: [#] 125 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Promotion of a specific SE(qname) within ElementContent grammar


Input: [#] 126 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Promotion of EE within StartTagContent grammar


Input: [#] 127 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Promotion of the same SE(qname) within StartTagContent and ElementContent grammars


Input: [#] 128 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Simple grammar search (same element qname at different places)


Input: [#] 129 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-10 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Independent learning between StartTagContent and ElementContent grammars


Input: [#] 130 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-11 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Progressive StartTagContent grammar learning


Input: [#] 131 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-12 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Progressive ElementContent grammar learning


Input: [#] 132 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-13 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Recursive element for StartTagContent grammar


Input: [#] 133 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-14 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Recursive element for StartTagContent grammar


Input: [#] 134 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-15 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Recursive element for ElementContent grammar


Input: [#] 135 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element-16 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Recursive element for ElementContent grammar


Input: [#] 136 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM in starttag


Input: [#] 137 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI in starttag


Input: [#] 138 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM in element content grammar


Input: [#] 139 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI in element content grammar


Input: [#] 140 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Various PI and CM


Input: [#] 141 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Single namespace definition


Input: [#] 142 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Redundant namespace definition


Input: [#] 143 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: default namespace


Input: [#] 144 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Initial Namespace Entry


Input: [#] 145 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: various namespaces, CM and PI


Input: [#] 146 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.element.other-10 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Various ER tests.


Input: [#] 147 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.attr-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Attribute learning


Input: [#] 148 [Test case] | all | bitAlign | builtinGrammar | builtinElementGrammar | builtin.attr-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Attribute learning with specific attributes (xsi:type and xsi:nil)


Input: [#] 149 [Test case] | all | bitAlign | builtinGrammar | fragment | builtin.fragment-00 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Schemaless Fragment with PIs and Comments


Input: [#] 150 [Test case] | all | bitAlign | builtinGrammar | fragment | builtin.fragment-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Schemaless Fragment without PIs and Comments


Input: [#] 151 [Test case] | all | bitAlign | builtinGrammar | fragment | builtin.fragment-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Schemaless Real Fragment Example


Input: [#] 152 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Root tag


Input: [#] 153 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM before root tag


Input: [#] 154 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI before root tag


Input: [#] 155 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM before root tag


Input: [#] 156 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI before root tag


Input: [#] 157 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM after root tag


Input: [#] 158 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI after root tag


Input: [#] 159 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: PI+CM after root tag


Input: [#] 160 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: CM+PI after root tag


Input: [#] 161 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-10 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD


Input: [#] 162 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-11 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: DTD with SYSTEM


Input: [#] 163 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-12 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Inline DTD with SYSTEM


Input: [#] 164 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-13 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: HTML DTD declaration


Input: [#] 165 [Test case] | all | bitAlign | builtinGrammar | builtinDocumentGrammar | builtin.doc-14 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Mix of CM, PI and DTD


Input: [#] 166 [Test case] | all | bitAlign | builtinGrammar | initialEntries | schemaless-cid-00 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Strings encoded as compact ids, some of them using prepopulated schemaless entries


Input: [#] 167 [Test case] | all | bitAlign | builtinGrammar | initialEntries | schemaless-cid-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Strings encoded as compact ids, some of them using prepopulated schemaless entries


Input: [#] 168 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.literal-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Element value with non-ascii characters


Input: [#] 169 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.literal-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Element name with non-ascii characters


Input: [#] 170 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.literal-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Element value with standard ASCII characters


Input: [#] 171 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.literal-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Element value with one character 2 bytes UTF-8


Input: [#] 172 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.literal-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Element value with one character 3 bytes UTF-8


Input: [#] 173 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.literal-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Element value with one character 3 bytes UTF-8 / 3 bytes EXI


Input: [#] 174 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.literal-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Element value with one character 4 bytes UTF-8


Input: [#] 175 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.indexed-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Locally indexed element value (same element qname)


Input: [#] 176 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.indexed-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Locally indexed attribute value (same element+attribute qname)


Input: [#] 177 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.indexed-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Locally indexed attribute value (same attribute qname, different element qname)


Input: [#] 178 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.indexed-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Locally indexed attribute value (element qname = attribute qname)


Input: [#] 179 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.indexed-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Globally indexed element-element value


Input: [#] 180 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.indexed-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Globally indexed attribute-attribute value


Input: [#] 181 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.indexed-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Globally indexed element-attribute value


Input: [#] 182 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.indexed-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Unindexed comment values


Input: [#] 183 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | string.indexed-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Unindexed PI values


Input: [#] 184 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | valuePartitionCapacity | boundedTables-00 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Value partition capacity test limited to 100 values


Input: [#] 185 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | valuePartitionCapacity | boundedTables-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Test the case of no string indexing


Input: [#] 186 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | valuePartitionCapacity | boundedTables-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Unlimited value partition capacity test


Input: [#] 187 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | valueMaxLength | boundedTables-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Value max length equal to 0


Input: [#] 188 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | valueMaxLength | boundedTables-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Value max length test


Input: [#] 189 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | stringTable | valueMaxLength | boundedTables-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Unlimited value max length


Input: [#] 190 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | binaryValid | base64.valid-00 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Valid small base64 element value


Input: [#] 191 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | binaryValid | base64.valid-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Valid base64 element value with '=' chars


Input: [#] 192 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | binaryValid | base64.valid-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Base64 element with no value


Input: [#] 193 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | binaryValid | base64.valid-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Valid base64+whitespaces element value


Input: [#] 194 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | binaryValid | base64.valid-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Valid whitespaces+base64 element value


Input: [#] 195 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | binaryValid | base64.valid-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Valid base64 attribute value


Input: [#] 196 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | binaryValid | hex.valid-00 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Valid hexa value


Input: [#] 197 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | booleanValid | boolean.valid-00 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: '1' boolean element value


Input: [#] 198 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | booleanValid | boolean.valid-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: '0' boolean element value


Input: [#] 199 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | booleanValid | boolean.valid-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: true boolean element value


Input: [#] 200 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | booleanValid | boolean.valid-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: false boolean value with '1' boolean attribute value


Input: [#] 201 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | booleanValid | boolean.valid-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: '1' boolean element value with pattern facet


Input: [#] 202 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | booleanValid | boolean.valid-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: 'true' boolean element value with pattern facet


Input: [#] 203 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-00 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Simple date value


Input: [#] 204 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-01 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Simple dateTime value


Input: [#] 205 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-02 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: dateTime with Z


Input: [#] 206 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-03 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: dateTime with time zone value


Input: [#] 207 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-04 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: dateTime with fractional value


Input: [#] 208 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-05 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: dateTime with time zone and fractional value


Input: [#] 209 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-06 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Simple gDay value


Input: [#] 210 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-07 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Simple gMonth value


Input: [#] 211 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-08 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: gMonth value with time zone


Input: [#] 212 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-08-1 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: gMonth value with time zone


Input: [#] 213 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-09 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: Simple gMonthDay value


Input: [#] 214 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-10 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: gMonthDay value with time zone


Input: [#] 215 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-11 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: gYear values


Input: [#] 216 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-12 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: gYear value with time zone


Input: [#] 217 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-13 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: gYearMonth value


Input: [#] 218 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-14 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: gYearMonth values with time zone


Input: [#] 219 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-14-1 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: gYearMonth values with time zone


Input: [#] 220 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-15 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: time values with or without time zone and fractional values


Input: [#] 221 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-15-1 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: time values with or without time zone and fractional values


Input: [#] 222 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-15-2 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: time values with or without time zone and fractional values


Input: [#] 223 [Test case] | all | bitAlign | builtinDatatypes | validDatatype | dateTimeValid | dateTime.valid-15-3 [3 to 1] PASSED [2 to 1] PASSED [3 to 2] PASSED [1 to 2] PASSED [2 to 3] PASSED [1 to 3] PASSED [Specification reference] specification [Input file] file [Testcase description]

Output: time values with or without time zone and fractional values