This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29113 - [XSLT30] fn:system-property does not a allow an EQName
Summary: [XSLT30] fn:system-property does not a allow an EQName
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-06 15:11 UTC by Abel Braaksma
Modified: 2015-10-29 12:42 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2015-09-06 15:11:46 UTC
We currently say about the only argument of fn:system-property (20.3.4 fn:system-property) that:

<quote>
The $property-name argument must evaluate to a lexical QName. 
</quote>

Since every other function we have that used to accept QNames now also accepts EQNames, I think this was possibly an oversight and should now (also) allow EQNames as an argument. See also Michael Kay's suggested conversion function which appears to assume this: https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Sep/0010.html (members only).
Comment 1 Michael Kay 2015-09-12 19:36:32 UTC
Anticipating the WG's agreement to remove this obvious inconsistency, I have applied the change to the spec but leave the bug open for review. The replacement text reads:

<p diff="chg" at="S-bug29113">The value of the <code>$property-name</code> argument 
<rfc2119>must</rfc2119> be a string containing an <termref def="dt-eqname">EQName</termref>. If it is a <termref def="dt-lexical-qname">lexical QName</termref> with a prefix, then it is expanded into an <termref def="dt-expanded-qname">expanded QName</termref> using the namespace declarations in the static context of the <termref def="dt-expression">expression</termref>. If there is no prefix, the name is taken as being in no namespace.</p>
Comment 2 Michael Kay 2015-10-09 11:41:52 UTC
The change was accepted.