RE: [F&O] 14.1.3 fn:namespace-uri can no longer return a string

Which raises the question about whether "" is a valid URI. RFC 2396 contains
a grammar which says it isn't, but then goes on to define semantics for
it...

I think we should just assume that "" is indeed a valid URI, and return it.
Returning () would be incompatible with XPath 1.0.

Michael Kay 

> -----Original Message-----
> From: public-qt-comments-request@w3.org 
> [mailto:public-qt-comments-request@w3.org] On Behalf Of Sarah Wilkin
> Sent: 08 September 2004 22:00
> To: public-qt-comments@w3.org
> Cc: Sarah Wilkin
> Subject: [F&O] 14.1.3 fn:namespace-uri can no longer return a string
> 
> 
> In F&O 14.1.3, namespace-uri was changed to return an 
> xs:anyURI instead 
> of an xs:string. The sentence "If $arg is the empty sequence, the 
> zero-length string is returned" is no longer valid. There may 
> be other 
> occurrences of this in the document where xs:string was changed to 
> xs:anyURI.
> 
> In similar cases (11.2.3) the signature is xs:anyURI?.
> 
> So either:
> fn:namespace-uri() as xs:anyURI?
> fn:namespace-uri($arg as node()?) as xs:anyURI?
> 
> If $arg is the empty sequence, the empty sequence returned.
> 
> or:
> fn:namespace-uri() as xs:anyURI
> fn:namespace-uri($arg as node()?) as xs:anyURI
> 
> If $arg is the empty sequence, xs:anyURI("") is returned.
> 
> --Sarah
> 
> 

Received on Wednesday, 8 September 2004 21:33:54 UTC