W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2006

[Bug 2179] R-185: Question about cardinality of calendar types

From: <bugzilla@wiggum.w3.org>
Date: Fri, 06 Jan 2006 14:02:28 +0000
To: www-xml-schema-comments@w3.org
Cc:
Message-Id: <E1EusAm-0007l0-Rr@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2179


cmsmcq@w3.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|1.0/1.1 both                |1.1 only




------- Additional Comments From cmsmcq@w3.org  2006-01-06 14:02 -------
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.
Received on Friday, 6 January 2006 14:02:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:13:10 GMT