25963 2014-06-03 16:35:54 +0000 [f+o 3.0] default second argument for resolve-uri() 2014-09-16 16:33:00 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 3.0 Working drafts PC All RESOLVED FIXED P2 normal --- 1 mike mike abel.braaksma public-qt-comments oldest_to_newest 107209 0 mike 2014-06-03 16:35:54 +0000 The spec says that the default for the second argument of resolve-uri() is effectively static-base-uri(). But static-base-uri() can return an empty sequence (if the static base uri is absent), while resolve-uri() does not accept an empty sequence here, and instead is defined to raise an error if there's no static base URI. 109236 1 abel.braaksma 2014-07-23 22:15:59 +0000 Considering the title of this bug, should this not have a component specification of F&O? 111296 2 mike 2014-09-09 19:18:23 +0000 The editor was asked to propose a resolution. The proposed resolution is to replace the rule If the second argument is absent, the effect is the same as calling the two-argument function with the value of fn:static-base-uri() as the second argument. by If the second argument is absent, the effect is as follows: * if the static base URI property in the static context is non-absent, it is used as the effective value of the second argument * otherwise, a dynamic error [FORG0002] is reported. 111597 3 mike 2014-09-16 15:37:52 +0000 Accepted with the caveat that if the first arg is an absolute URI, resolve-uri() should succeed even if there is no known base URI. 111605 4 mike 2014-09-16 16:33:00 +0000 The changes have been applied.