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 2179 - R-185: Question about cardinality of calendar types
Summary: R-185: Question about cardinality of calendar types
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2005-09-14 18:42 UTC by Sandy Gao
Modified: 2009-04-21 19:21 UTC (History)
0 users

See Also:


Attachments

Description Sandy Gao 2005-09-14 18:42:49 UTC
The datatypes for recurring calendar events (specifically gMonthDay, gDay and 
gMonth) are all recorded in appendix A with: 

<hfp:hasProperty name="cardinality" value="countably infinite"/> 
However it appears that there are at most 366 days in a year, and at most 59? 
timezones or maybe 290000 if we take an extremist view of the possible 
timezones. (Alternatively, the lexical form is of finite length and comes from 
a finite vocabulary, hence there are finitely many different lexical forms). 

Is this an oversight? 

See:
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002OctDec/0068.html
Comment 1 Sandy Gao 2005-09-14 18:42:58 UTC
Discussed at the 2003-11-20 telecon. Agreed to classify as error w/erratum. 
Agreed to change countably infinite to finite. Ashok to draft text.
Comment 2 Sandy Gao 2005-11-09 17:20:15 UTC
And whenever we change cardinality to finite, we also need to change bounded 
to "true".
Comment 3 C. M. Sperberg-McQueen 2006-01-06 14:02:29 UTC
Proposed fix:  (1) in the pseudo schema document with declarations for
the types gYearMonth, gYear, gMonthDay, gDay, and gMonth (currently
labeled "primitives.nxsd", but that name is subject to change), 
change 

   <hfp:hasProperty name="bounded" value="false"/>
   <hfp:hasProperty name="cardinality" value="countably infinite"/>

to

   <hfp:hasProperty name="bounded" value="true"/>
   <hfp:hasProperty name="cardinality" value="finite"/>

This should automatically repair the descriptions in sections
3.3.11.3, 3.3.12.3, etc., and in appendix F.

(2) Reply to Jeremy Caroll, who raised the issue long ago,
thanking him for the comment and explaining that in 1.0 we
were confused by the fact that each value of these types
itself denotes a countably infinite set (e.g. the infinite
set of periods of time labeled January in the Gregorian
calendar).

I am changing the 'version' field from 1.0/1.1 both to
1.1 only, and spawning a twin issue for the 1.0 corrigendum:
bug 2668 is the 1.0 twin.
Comment 4 C. M. Sperberg-McQueen 2006-01-06 14:15:26 UTC
Correction: gYearMonth is not finite, for the same reason that
gYear is not finite.  So it should NOT be changed.  It's only
the three types which don't have year information in them:
gMonth, gDay, and gMonthDay.  Sorry for the slip.
Comment 5 C. M. Sperberg-McQueen 2006-01-15 00:35:28 UTC
On its telcon of 13 January, the WG adopted the proposal in
comment 3, as amended in comment 4 and with the instruction
to the editor to get it right this time.  The change was
integrated into the status-quo document on 13 January 2006,