4232 2007-01-16 11:37:31 +0000 Incorrect expected error for fn-collection-3 2007-03-09 17:09:37 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite unspecified PC All CLOSED FIXED P2 minor --- 1 nick andrew.eisenberg public-qt-comments oldest_to_newest 13577 0 nick 2007-01-16 11:37:31 +0000 fn-collection-3 fn:collection("invalidURI<>") expectes FODC0002 15.5.6 of F+O states: "if $arg is not a valid xs:anyURI, an error is raised [err:FODC0004]." (For what its worth, the recently added K2-SeqCollectionFunc-1 collection("http:\\invalid>URI\someURI") is testing the same thing, but with the correct error) 13579 1 mike 2007-01-16 12:38:27 +0000 You are assuming that "invalidURI<>" is not a valid instance of xs:anyURI. XML Schema Part 2 says that a string is a valid instance of xs:anyURI if it becomes a valid URI after you apply the escaping procedure defined in section 5.4 of XLink. That procedure escapes "excluded characters listed in Section 2.4 of [IETF RFC 2396], except for the number sign (#) and percent sign (%)". That set includes "<" and ">". So "invalidURI<>" is in fact valid. As far as I can see, "http:\\invalid>URI\someURI" is also a valid instance of xs:anyURI, for the same reasons. It's pretty meaningless as a URI, but the spec doesn't require it to me meaningful, only syntactically valid. 13584 2 nick 2007-01-16 13:16:21 +0000 Ah, yes, thanks I was making that assumption. But even once it is escaped I still think the error is wrong as then: "If Available collections provides no mapping for the string, an error is raised [err:FODC0004]." applies. err:FODC0002 is only thrown if there is no arguement and no default collection. 14363 3 carmelo 2007-03-09 16:37:44 +0000 Hey Nick: Thanks for teh comment. It looks like FODC0004 is a morte appropriate error code for this case. Changed the expected error to FODC0004. Thanks, Carmelo 14367 4 nick 2007-03-09 17:09:37 +0000 Thanks