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 4898 - [FS] 8.5.1 Type promotion
Summary: [FS] 8.5.1 Type promotion
Status: CLOSED DUPLICATE of bug 3670
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Recommendation
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Michael Dyck
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL: http://www.w3.org/TR/xquery-semantics...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-31 14:56 UTC by Ben Wagner
Modified: 2009-06-22 20:46 UTC (History)
0 users

See Also:


Attachments

Description Ben Wagner 2007-07-31 14:56:25 UTC
In the XPath and XQuery language recommendations there is an Appendix B ( http://www.w3.org/TR/xpath20/#promotion and http://www.w3.org/TR/xquery/#promotion respectively) which describe 1. Numeric Type Promotion and 2. URI Type Promotion. However, in section 8.5.1 of the Formal Semantics, the Numeric Promotion is described, but the URI Promotion is not. It appears that there should be a rule of the form

xs:anyURI can be promoted to the type xs:string

--------------------------------------------------
statEnv |-  xs:anyURI can be promoted to xs:string

in order to bring the Formal Semantics document into line with the language specifications.
Comment 1 Michael Dyck 2007-07-31 18:26:25 UTC
> It appears that there should be a rule of the form
> 
> xs:anyURI can be promoted to the type xs:string
> 
> --------------------------------------------------
> statEnv |-  xs:anyURI can be promoted to xs:string

(I'm assuming that "xs:anyURI can be promoted to the type xs:string" isn't part of the rule per se, but rather is the preceding prose.)

Yes, I agree. This was pointed out (and resolved) last year as part of Bug 3670, but the fix did not make it into the Recommendation. Instead it will appear as an erratum.

I'm marking this issue as 'Resolved, duplicate of 3670'. If you agree with this resolution, please close the issue. 

*** This bug has been marked as a duplicate of bug 3670 ***
Comment 2 Michael Dyck 2009-06-22 20:46:49 UTC
The requested change appears in the Proposed Edited Recommendation
for the FS.

After almost two years with no response from the original reporter,
I am marking this issue CLOSED.  Feel free to reopen it
if you disagree with this outcome.