This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The values of typeName and typeNamespace expected in elementgetschematypeinfo04 and elementgetschematypeinof07 are no longer accurate as a result of recent changes to hc_staff.xsd (Revision 1.5). In hc_staff.xsd : ---- Revision 1.4 ++++ Revision 1.5 - <xsd:element name="code" type="xsd:string"/> + <xsd:element name="code" type="code"/> - <xsd:element name="sup" type="xsd:string"/> + <xsd:element name="sup" type="sup"/> Patch for elementgetschematypeinfo04: -<assertEquals expected='"string"' actual="typeName" +<assertEquals expected='"code"' actual="typeName" -<assertEquals expected='"http://www.w3.org/2001/XMLSchema"' - actual="typeNamespace" +<assertEquals expected='"http://www.w3.org/1999/xhtml"' actual="typeNamespace" Patch for elementgetschematypeinfo07: -<assertEquals expected='"string"' actual="typeName" +<assertEquals expected='"sup"' actual="typeName" -<assertEquals expected='"http://www.w3.org/2001/XMLSchema"' - actual="typeNamespace" +<assertEquals expected='"http://www.w3.org/1999/xhtml"'actual="typeNamespace"
Created attachment 282 [details] Fixes to those tests, elimination of conflicting impl attributes Specifying <implementationAttribute name="schemaValidating" value="true"/> forces namespaceAware=true and (DTD) validation=false. Removed inconsistent implementationAttributes from similar tests.