Solved

Issue with xsd:maxInclusive restriction for 'float' type

Posted on 2011-03-03
7
1,270 Views
Last Modified: 2012-05-11
Hi Experts,
My first question in the forum.

I've an XML file and an XSD to validate that. I've an element 'Duration' for which I've given a restriction of range. For eg [32.25, 128000]. I've defined the element as a simply type. Pls see  below,

 <xsd:simpleType>
      <xsd:restriction base="xsd:float">
           <xsd:minInclusive value="32.25"/>
            <xsd:maxInclusive value="128000"/>
      </xsd:restriction>
</xsd:simpleType>

But the problem is with values. If I give values like 128000.001, 128000.002, 12800.003 and validate against the schema 'no errors are reported!!'. But if I give a value 128000.004 or more I'm getting 'cvc-maxInclusive-valid' failure, which is what I need.
Note:
1) I'm using Oxygen 11.1 version.
2) The problem starts with values with 3 or more fractional digits.
Could u pls tell me wr the problem is?
0
Comment
Question by:vipinreyaroth
  • 3
  • 2
  • 2
7 Comments
 
LVL 60

Accepted Solution

by:
Geert Bormans earned 250 total points
Comment Utility
The problem is in the precision of a xs:float
If this is important for you at that level of precision,
you should use xs:double
(I wonder actually why you would use xs:float after all)
0
 
LVL 20

Expert Comment

by:ChristoferDutz
Comment Utility

I just had a look at the spec:
http://www.w3.org/TR/xmlschema-2/#rf-maxInclusive
There I can read:
The value of maxInclusive ·must· be in the ·value space· of the ·base type·.
And from the definition, i get:
value = anySimpleType

My guess would be that in your xsd 128000 is an integer and therefore the check is done in the integer value-space.
It's just a thing worth trying. Change your rule to this and see if it works:
<xsd:simpleType>
      <xsd:restriction base="xsd:float">
           <xsd:minInclusive value="32.25"/>
            <xsd:maxInclusive value="128000.0"/>
      </xsd:restriction>
</xsd:simpleType>

Open in new window

0
 

Author Comment

by:vipinreyaroth
Comment Utility
Hi Gertone, ChristoferDutz thanks for your inputs.
1) @Gertone: Changing to 'xsd:double' works with the precision of 11 digits. But I've to keep the type as 'float' ( that's a requirement). So I think restricting the number of fractions (upto 2 digits for floats) using a pattern would help.
2) @ChristoferDutz: I tried, but it doesn't work. :(
0
IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 20

Assisted Solution

by:ChristoferDutz
ChristoferDutz earned 250 total points
Comment Utility
Ahh ... dammit ... gertone is correct.
The problem is the number is internally represented as 32bit floating point number which means that it can store about 8 digits + their offset ... if you would set the upper limit to 128 instead of 128000 then you would get precision for 3 more digits in the fractional part. The problem is that when parsing the number as float the fractional part is simply stripped off and therefore cannot be used for comparison.
0
 
LVL 60

Expert Comment

by:Geert Bormans
Comment Utility
I was in the car for the past hour or so, so I missed your response.
You have conflicting requirements, you simply can't get the precision you want from an xs:float.

If you really want to use xs:float
and exclude some values at the high end,
use maxExclusive instead of maxInclusive (you will loose some valid values, but at least you get warned, being too strict is always better than not being strict enough)

Or use xs:double for the calculation in the schema and add a number type conversion after the validation in whatever technology you use to process the XML
At least your validation then happens on maximum precision
0
 

Author Comment

by:vipinreyaroth
Comment Utility
Thanks Gertone. It'll do.
0
 
LVL 60

Expert Comment

by:Geert Bormans
Comment Utility
welcome
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

The Problem How to write an Xquery that works like a SQL outer join, providing placeholders for absent data on the outer side?  I give a bit more background at the end. The situation expressed as relational data Let’s work through this.  I’ve …
The Confluence of Individual Knowledge and the Collective Intelligence At this writing (summer 2013) the term API (http://dictionary.reference.com/browse/API?s=t) has made its way into the popular lexicon of the English language.  A few years ago, …
This video discusses moving either the default database or any database to a new volume.
When you create an app prototype with Adobe XD, you can insert system screens -- sharing or Control Center, for example -- with just a few clicks. This video shows you how. You can take the full course on Experts Exchange at http://bit.ly/XDcourse.

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now