[Nsi-wg] Change of xsd:int for large numbers

[John MacAuley]

People,

As I have been going through the service description I realized we are going to have problems with our current use of xsd:int which is a signed integer value.  If you remember we changed from the xsd:integer to an xsd:int in release 1.0 to simplify coding in Java since it uses a base int type instead of an Integer object.  This was okay in release 1 since we were specifying bandwidth in Mbps, however, with the introduction of service descriptions it is possible to specify the units for capacity.  This means with our current xsd:int definition we are unable to specify bps for capacity.  Also, it looks like burst size as an xsd:int will also not work.

Is anyone against me changing these to an integer or perhaps  nonNegativeInteger?

Thanks,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20130730/39e837e5/attachment.html>