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 2220 - R-228: Suggestion for changes in fractionDigits example in part 2
Summary: R-228: Suggestion for changes in fractionDigits example in part 2
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: unspecified
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 19:20 UTC by Sandy Gao
Modified: 2009-04-21 19:21 UTC (History)
0 users

See Also:


Attachments

Description Sandy Gao 2005-09-14 19:20:37 UTC
The value of totalDigits at the example [1] 

<simpleType name='celsiusBodyTemp'>
  <restriction base='decimal'>
    <totalDigits value='4'/>
    <fractionDigits value='1'/>
    <minInclusive value='36.4'/>
    <maxInclusive value='40.5'/>
  </restriction>
</simpleType>

should probably be 3 -- if at all present. The presence of both minInclusive 
and maxInclusive make totalDigits superfluous. The fractionDigits set to 1 
means that only one digit after the decimal point is allowed. 

Considering the other three facets all valid values have at max 3 digits. 

Also ,the magnitude of a (live) person's body temperature on the Celsius scale 
would probably go up to 42 Celsius... 

[1] http://www.w3.org/TR/2004/PER-xmlschema-2-20040318/#rf-fractionDigits 

See:
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2003JulSep/0033.html
Comment 1 Dave Peterson 2006-11-18 02:01:14 UTC
Approved by the WG; awaiting incorporation into the status quo document.
Comment 2 Dave Peterson 2006-11-18 02:15:34 UTC
(In reply to comment #1)
> Approved by the WG; awaiting incorporation into the status quo document.

Specifically, the approved fix is to delete the totalDigits element and change the minInclusive value
to 32 (89.6 F) and maxInclusive value to 41.7 (107.1 F). 

Comment 3 C. M. Sperberg-McQueen 2007-09-18 00:40:02 UTC
The change proposed above was approved by the WG in its call of 
17 November 2006.  It is now reflected in the status quo version 
of the Datatypes spec.  Accordingly, I am setting the disposition of 
this issue to RESOLVED / FIXED.

If the originator of the issue would examine the change and let 
us know whether it satisfactorily resolves the problem or not, 
we'd be grateful.   To signal that the resolution is acceptable, 
change the status of the issue to CLOSED.  Otherwise, to signal 
that it's NOT acceptable, change the status to REOPENED (and 
tell us what's wrong).

If we don't hear from you in the next three weeks, we'll assume 
that silence betokens consent, and close the issue ourselves.