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 description of the handling of the $uri-sequence argument to fn:document() needs to be revised, since items in this sequence may be other than a node or atomic value. For easy of implementation, and clarity of error conditions, would it not make sense to state that this argument is atomized before any processing occurs, and that any errors caused by failure to atomize would be those defined for fn:data?
Thanks for pointing it out. I think it can be fixed simply by s/atomic value/item/ in the third bullet: If $uri-sequence (after atomizing any nodes) contains an atomic value of a type other than xs:string, xs:anyURI, or xs:untypedAtomic then a type error is raised [ERR XPTY0004] Atomizing the supplied sequence doesn't work, because the rules for resolving a relative URI are different for nodes and for atomic values.
The WG accepted the proposed fix. The text has been changed to read: <p> If <code>$uri-sequence</code> (after atomizing any nodes) contains an <phrase diff="chg" at="S-bug28153">item other than an atomic value of type</phrase> <code>xs:string</code>, <code>xs:anyURI</code>, or <code>xs:untypedAtomic</code> then a type error is raised <xerrorref spec="XP" class="TY" code="0004"/>. </p>