6943 2009-05-22 15:20:58 +0000 Minor editorial issue: nontimezoned or untimezoned 2009-10-23 16:12:02 +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 davep www-xml-schema-comments oldest_to_newest 25264 0 sandygao 2009-05-22 15:20:58 +0000 Section "3.3.8.2 Lexical Mapping" for "dateTime" introduces notions like "timezoned" and "untimezoned" values, but later on the "3.3.10 date" section uses the word "nontimezoned". Should be consistent. 25265 1 davep 2009-05-22 15:46:10 +0000 (In reply to comment #0) > Section "3.3.8.2 Lexical Mapping" for "dateTime" introduces notions like > "timezoned" and "untimezoned" values, but later on the "3.3.10 date" section > uses the word "nontimezoned". Should be consistent. Formal recommendation to the WG: In 3.3.8.2, first paragraph, change the two occurrences of 'nontimezoned' to 'untimezoned'. These appear to be the only two occurrences of 'nontimezoned' in the spec. 25367 2 David_E3 2009-05-29 16:01:02 +0000 RESOLUTION: resolve 6843 by replacing all occurrances of "untimezoned" to "nontimezoned". 25985 3 cmsmcq 2009-07-15 21:12:10 +0000 The change described in comment 2 has now been integrated into the status-quo documents. I am accordingly marking this issue resolved. (The minutes seemed to show a groundswell of opinion in favor of hyphenating 'non-timezoned', so I did that, too.) Sandy, as the originator, if you would signal your acceptance or rejection of this resolution by closing or reopening the bug in the usual manner, it would be helpful. If the working group does not hear otherwise from you in the next two weeks, we will assume that you are content with the disposition of this comment.