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 29059 - 9.9.1 fn:parse-ietf-date
Summary: 9.9.1 fn:parse-ietf-date
Status: CLOSED WORKSFORME
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (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: http://www.w3.org/TR/xpath-functions-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-17 10:18 UTC by Tim Mills
Modified: 2015-09-01 16:24 UTC (History)
0 users

See Also:

Attachments

Description Tim Mills 2015-08-17 10:18:44 UTC 
Is this really the best name for a function returning an xs:dateTime?
Comment 1 Tim Mills 2015-08-17 10:35:51 UTC 
Also, the description doesn't mention the behaviour when $value is the empty sequence.
Comment 2 Michael Kay 2015-09-01 16:08:16 UTC 
As regards comment 1, the Rules include

"If the input is an empty sequence, the result is an empty sequence."

As regards comment 0, the WG felt that there was not a strong enough justification for making a change at this dateTime.
Comment 3 Tim Mills 2015-09-01 16:24:20 UTC 
(In reply to Michael Kay from comment #2)

> As regards comment 0, the WG felt that there was not a strong enough
> justification for making a change at this dateTime.

:)

I was hoping for fn:parse-ietf-dateTime, leaving scope for a future fn:parse-ietf-date which just parses the date part.