[Bug 29373] New: Missing error code when fn:serialize receives a QName method in no namespace

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29373

            Bug ID: 29373
           Summary: Missing error code when fn:serialize receives a QName
                    method in no namespace
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: josh.spiegel@oracle.com
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

Consider test serialize-xml-120

 <test-case name="serialize-xml-120" covers="fn-serialize">
   ...
   <test>let $params := map { QName("","indent") : true() }
         return serialize(., $params)
   </test>
   <result>
     <error code="SEPM0017"/> 
   </result>
 </test-case>

SEPM0017 should not be expected in this case.  From SER31:

  https://www.w3.org/TR/2015/CR-xslt-xquery-serialization-31-20151217/
  "If in any case evaluating this expression would yield an error,
serialization error [err:SEPM0017] results."

"expression" refers to query that validates a serialization document and there
is no serialization document used in this case.

But I don't think the specification says which error code should be raised. 
http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/#func-serialize

"The key of the entry is an xs:string value in the cases of parameter names
defined in these specifications, or an xs:QName (with non-absent namespace) in
the case of implementation-defined serialization parameters."

Then the table has a note:

"If an xs:QName is supplied, then it must have a non-absent namespace URI. This
means that system-defined serialization methods such as xml and json are
defined as strings, not as xs:QName values."

One could argue that this falls under SEPM0016 but I think the definition
should clarify this.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 13 January 2016 17:14:10 UTC