This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Upon seeing the discussion surrounding bug 10867, I finally opened up the namespace document for the F&O functions. I noticed the following editorial/build issues: * The functions format-date, format-dateTime, format-number, format-time, has-children, innermost, outermost, unparsed-text, unparsed-text-lines, unparsed-text-available and uri-collection appear in both the XPath/XQuery section and in the XSLT-specific section. * Two summary sections appear beneath the XPath/XQuery entry for the unparsed-text function. The second summary actually describes the unparsed-text-lines function.
Most of these problems were caused by the fact that these functions were added to F+O before being removed from XSLT, just to make sure nothing fell through any holes in the process. They seem to be largely ironed out in the 14 June 2011 docs. There's one problem remaining, the unparsed-text function has a rather strange summary. ("A decision in principle has been reached...") I think this was caused by the fact that the build process for the F+O namespace doc looks at the XSLT specification, which was not in a stable published state at the time the F+O build was run. So this problem too will disappear when the specs get back into sync. Since no action is needed, I'm closing this as resolved-worksforme.