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 2571 - R-090: Questions about the lexical and canonical rep'ns of dateTime
Summary: R-090: Questions about the lexical and canonical rep'ns of dateTime
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.0 only
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: needsAgreement
Depends on:
Blocks:
 
Reported: 2005-12-09 04:19 UTC by Sandy Gao
Modified: 2011-10-21 16:39 UTC (History)
0 users

See Also:


Attachments

Description Sandy Gao 2005-12-09 04:19:54 UTC
Refer to bug 2080 for detailed description.
Comment 1 Sandy Gao 2005-12-09 04:46:53 UTC
A conformance note is only available for duration. We need to considering doing 
the following:
1. Apply a similar note to other types.
2. For duration, provide conformance criteria for other fields than year and 
second. The lex value "P99999999999999999999999999M" is currently allowed, but 
I don't think we want to require mininum conforming processors to support it 
when they are allowed not to support "P10000Y".

For #1, the solution is abviously to apply the note we have for duration to 
dateTime, time, date, gYear, and gYearMonth.

For #2, there are 2 ways to solve it: either we specify limits for each field, 
or we specify limits on the equivalent (month,second) values. That is,

Option A: All minimum conforming processor must support duration values 
(y,m,d,h,mm,ss):
1) y <= 9999
2) m <= 11
3) d <= 30
4) h < 24
5) mm < 60
6) ss < 60
7) ss with at most 3 fractional digits

Option B: All minimum conforming processor must support duration values 
(y,m,d,h,mm,ss):
a. abs(y*12+m) < 120000
b. abs(d*24*3600+h*3600+mm*60+ss) < 31*24*3600
c. ss with at most 3 fractional digits