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 consensus from the teleconference is that a type should be considered derived by restriction from itself and that a type should not be considered derived by restriction if every member of a union type is a restriction of the specified type. typeinfoisderivedfrom01: Checks that a DTD type will return true for restriction if the namespace is the XML URI and the name matches the DTD type name. Previously DTD types always returned false for isDerived. typeinfoisderivedfrom02, 14, 28: These tests used to check that a schema type was not considered derived from itself. The tests have been changes so that a type is considered derived from itself by restriction but not any other method. typeinfoisderivedfrom18: This test checked if a union type where every member type was derived from xsd:ID considered itself derived from ID by restriction. Previously expected true, now false. typeinfoisderivedfrom64: This test was submitted in last nights submission from IBM and was not consistent with the previous tests. This test checked if the type of an attribute considered itself derived from itself. It was rewritten so it passed the previous impl and back to close to its original form (plus an extra assertion). typeinfoisderivedfrom65: The previous test expected the type for the sub element to be a list of strings which it is not. Changed the element name to "strong" which is a list of strings.
Created attachment 272 [details] Patch
Created attachment 273 [details] Reverting changes to typeinfoisderivedfrom01
Reverted changes to typeinfoisderivedfrom01. DTD types derive from nothing again.