| Re: tVersionNumber [message #1076 is a reply to message #1075] |
Thu, 12 June 2008 11:04   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Susanne Wunsch wrote:
> coord(at)timetablerailMLorg wrote:
>
>> a new Version "1.1.1" would be fine, but tVersionNumber is defined as
>> decimal (x.yy). Shall we switch to string with pattern xx.yy.zz ?
>
> If some release version needs correction, some three part version number
> should be helpful. (Your offer: xx.yy.zz)
>
> Changes in "rollingstock"-schema shows need for 1.1.1
>
> If nobody disagrees, I would help with new type for "tVersionNumber" in
> "genericRailML.xsd".
>
My offer would be following:
<xsd:simpleType name="tVersionNumber">
<xsd:restriction base="xsd:string">
<xsd:pattern value="[1-9][0-9]?\.([0-9]|[1-9][0-9])(\.[1-9][0-9]?)?"/>
</xsd:restriction>
</xsd:simpleType>
That allows version numbers like:
first part: 1.0 10.0 99.0
second part: 1.0 1.9 1.10 1.99
third part: 1.0.1 10.0.10 1.0.99
It doesn't match following strings:
0 no comment
1 use 1.0 instead
1.00 use 1.0 instead
1.0.0 use 1.0 instead
1.01 use 1.1 instead
1.0.01 use 1.0.1 instead
I hope, it might be understood. Anything else, I can help with less
theoretical examples.
Feel free to discuss.
Do we really need it???
If nobody disagrees, I upload the code in "common-genesis".
(http://www.railml.org/en/development/common_genesis.html)
Kind regards,
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
