6547 2009-02-09 15:58:06 +0000 dateTime regular expression appears twice 2009-04-21 19:21:47 +0000 1 1 1 Unclassified XML Schema Datatypes: XSD Part 2 1.1 only PC Windows XP CLOSED FIXED resolved P2 normal --- 1 sandygao David_E3 cmsmcq www-xml-schema-comments oldest_to_newest 23596 0 sandygao 2009-02-09 15:58:06 +0000 In "3.3.8.2 Lexical Mapping" of the 3rd LC draft [1], the (very long) regular regular expression appears twice, once on a single line, and once split across 5 lines. [1] http://www.w3.org/TR/xmlschema11-2/#dateTime-lexical-mapping 23605 1 davep 2009-02-09 16:46:38 +0000 (In reply to comment #0) > In "3.3.8.2 Lexical Mapping" of the 3rd LC draft [1], the (very long) regular > regular expression appears twice, once on a single line, and once split across > 5 lines. Quite so. Was, I believe, also in the previous LC draft. :-( Both versions were added to the source at the same time and in response to the same bug; I assume one was meant to be removed and its removal got backburnered and then overlooked. Since the one-line version is quite long and thus quite useless on most browsers, and since the introductory text mentions that whitespace (which includes line breaks) is meant to be removed before the RE is used, I assume the one-line version should be removed and the other remain. WG should approve this solution (or reject it--I hope not). 23838 2 David_E3 2009-02-20 16:33:38 +0000 WG adopted the proposal in comment 1 24361 3 davep 2009-03-21 01:58:36 +0000 The WG approved the fix in http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.dp090225.html . The amendment has been incorporated in the XML master, and is awaiting republishing of a status quo document. 24363 4 davep 2009-03-21 02:04:39 +0000 (In reply to comment #3) > The amendment has been incorporated in the XML master, and is awaiting republishing > of a status quo document. Sorry, cut-and-paste error. There was no amendment; the fix was approved as presented, and will be included in the next status quo document. 24889 5 cmsmcq 2009-04-21 18:03:16 +0000 The problem described here appears to be corrected in the current status-quo document, so I'm marking this issue RESOLVED / FIXED. Sandy, over to you.