| Re: tVersionNumber [message #1075 is a reply to message #1074] |
Mon, 09 June 2008 11:01   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
coord(at)timetablerailMLorg wrote:
> Hi Susanne,
> 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 ?
>
> Kind regards,
> Joachim Rubröder
Maybe or not.
We should distinguish between "release version" and "developer version".
If some release version needs correction, some three part version number
should be helpful. (Your offer: xx.yy.zz)
In October, 2007 we released railML 1.1. That means all schemas got
release version number 1.1.
So next release version should also cover all sub-schemas:
* in case of corrections with next minor version 1.1.1,
* in case of minor changes with 1.2
* in case of restructuring with 2.0
Changes in "rollingstock"-schema shows need for 1.1.1
If nobody disagrees, I would help with new type for "tVersionNumber" in
"genericRailML.xsd".
For developer version we should find another way, tagging it!
I would prefer some version control tool like CVS or Subversion.
In order to operate until this question is solved, we can use simple
counting appending to file name (e. g. "timetable_1.1-R1.xsd") and
uploading to "genesis site".
Feel free to comment.
Kind regards,
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
