W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2006

[Bug 3386] Editorial, 15.5.4 fn:doc: error code not explicitly specified

From: <bugzilla@wiggum.w3.org>
Date: Sat, 24 Jun 2006 10:28:18 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1Fu5NC-0004m3-AW@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3386

           Summary: Editorial, 15.5.4 fn:doc: error code not explicitly
                    specified
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Keywords: editorial
          Severity: minor
          Priority: P2
         Component: Functions and Operators
        AssignedTo: ashok.malhotra@oracle.com
        ReportedBy: frans.englich@telia.com
         QAContact: public-qt-comments@w3.org


Close to the end of 15.5.4 fn:doc is this paragraph found:

<quote>
One possible processing model for this function is as follows. The resource
identified by the URI Reference is retrieved. If the resource cannot be
retrieved, an error is raised [err:FODC0002]. The data resulting from the
retrieval action is then parsed as an XML document and a tree is constructed in
accordance with the [XQuery 1.0 and XPath 2.0 Data Model]. If the top-level
media type is known and is "text", the content is parsed in the same way as if
the media type were text/xml; otherwise, it is parsed in the same way as if the
media type were application/xml. If the contents cannot be parsed successfully,
an error is raised. Otherwise, the result of the function is the document node
at the root of the resulting tree. This tree is then optionally validated
against a schema.
</quote>

It says "If the contents cannot be parsed successfully, an error is raised,"
without specifying the error code. I assume it's FODC0002, but specifying it
explicitly would be clearer. The description for FODC0002 reads "Error
retrieving resource."


Frans
Received on Saturday, 24 June 2006 10:28:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:12 UTC