Allow xs:integer in ValueScheme

[dietuyt]

The types you can select for the valueScheme does not allow integers. Gertjan Postma of Meertens requested this during the cmdi workshop.

I checked the schema and it seems that integers are not a primitive type but a derrived type not sure if this makes any difference. Consult Dieter on this.

[patdui]

Thorsten also would like to have xs:id added. Is there a good reason why we just don't add all xml-types?

[dietuyt]

I contacted Gertjan to ask why float or digital is not enough. In theory we could indeed support all xml types, so far we took the KISS approach.

[twagoo]

What's the status of this? I added dateTime (see #163) to the development branch (soon te be deployed I hope), perhaps a good time to revisit.

[dietuyt]

We never got an answer from Gertjan, so I consider this request to be obsolete/not so important. I would give this ticket a WONTFIX status.

[twagoo]

There was a discussion today at a CMDI tutorial about this.
I think we should reconsider adding the int type, since it potentially has many valid use cases. Also, it is in fact supported by CMDI (any standard xml type is) and many people will be looking for it.

We should perhaps also consider having the positive and negative integer distinction.

[dietuyt]

Ok, if there is a real demand for this we can add it.

[dietuyt]

We've had several requests to add integer now, so I would suggest to add xs:int (​http://www.w3.org/TR/xmlschema-2/#int)

[olhsha]

fixed at Ola's branch

[twagoo]

Changed in general component schema in r2517.
ComponentRegistry-1.13 will take values in editor from schema, so no further work to be done; closing as fixed.