4126 2007-01-02 12:34:04 +0000 MS dataTypes anyURI_a004 2011-12-09 16:25:02 +0000 1 1 1 Unclassified XML Schema Test Suite Microsoft tests 2006-11-06 PC Windows XP REOPENED Test and metadata updated 2010-07-05 decided P2 normal --- 1 mike ht David_E3 public-xml-schema-testsuite oldest_to_newest 13312 0 mike 2007-01-02 12:34:04 +0000 In the Microsoft DataTypes test set, test <test group="anyURI_a004_1339" name="anyURI_a004_1339"/> the schema contains: <!-- should give only 3 warning for the unresolved schemaLocations --> <xsd:include schemaLocation="ftp://ftp.is.co.za/rfc/rfc1808.txt"/> <xsd:import schemaLocation="gopher://spinaltap.micro.umn.edu/00/Weather/California/Los%20Angeles" namespace="gopher://spinaltap.micro.umn.edu/00/Weather/California/Los%20Angeles"/> <xsd:redefine schemaLocation="mailto:mduerst@ifi.unizh.ch"/> The test appears to be written on the assumption that the URIs should fail to resolve, and that this is a warning condition rather than an error. However, the first URI does resolve, and yields a resource that cannot be parsed as XML. XML Schema Part 1, Schema Representation Constraint: Inclusion Constraints and Semantics states: In addition to the conditions imposed on <include> element information items by the schema for schemas, all of the following must be true: 1 If the ·actual value· of the schemaLocation [attribute] successfully resolves one of the following must be true: 1.1 It resolves to (a fragment of) a resource which is an XML document (of type application/xml or text/xml with an XML declaration for preference, but this is not required), which in turn corresponds to a <schema> element information item in a well-formed information set, which in turn corresponds to a valid schema. 1.2 It resolves to a <schema> element information item in a well-formed information set, which in turn corresponds to a valid schema. Given that the actual value resolves, and neither 1.1 nor 1.2 is true, the schema is invalid. 13802 1 zafara 2007-01-24 19:27:58 +0000 This test should indeed be invalid. This is due a bug in the packaging process of Microsoft schema tests. 35795 2 David_E3 2010-05-21 15:42:30 +0000 HT suggests changing the first schemaLocation to http://127.0.0.1/must%20not%20resolve%20.xyzzy or something guaranteed not to be resolved. WG agrees. 36721 3 mike 2010-07-09 11:37:21 +0000 With the change applied in comment #2, both the schema and the instance now appear to be valid, but the instance is still marked as invalid in the metadata. I have marked the instanceTest as "queried". 61306 4 David_E3 2011-12-09 16:25:02 +0000 WG believes the metadata should be updated per comment 3.