** Maintenance of all services taking place on Saturday June 22, from 18:00 - 21:00 (GMT+2) **
 
1
0
-1

Is there a reason the XSD uses xs:Integer vs xs:Int?

Using a c# class generator turns xs:Integer in to string values instead of an int.  This is by design because of the definition of xs:Integer.  However it seems more straight forward if xs:Int were used as it translate to a c# int quite nicely.  Is there a reason xs:Integer is being used?


I'm not knowledgeable enough in the requirements to know the reason but this data definition guide seems to advise against using xs:Integer.

https://www.codalogic.com/lmx/xsd-overview.html#DefiningElementsPart1

    CommentAdd your comment...

    1 answer

    1.  
      2
      1
      0

      I agree that xs:int is correct for most values.

      I made FileSpec/@Size an xs:long for the corner case of a file >2GB on a 32 bit system

      1. satoshi yuki

        So will xs:int be used in the future? (except for FileSpec/@Size)

      CommentAdd your comment...