| Re: Some hints for changes in railwayBaseTypes.xsd [message #1093 is a reply to message #1091] |
Mon, 30 August 2010 22:17   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hello everybody,
"Carsten Weber" <weber(at)irfpde> writes:
> "Joerg von Lingen" <joergvon_lingendd(at)t-onlinede> schrieb im Newsbeitrag
> news:i5g58d$1uc$1(at)sifaivifhgde...
>>
>> On 23.08.2010 22:10, Carsten Weber wrote:
>>>
>>> - The attribute named "count" inside the attribute group aPlaces should
>>> change his type to nonNegativeInteger to differ between known values by
>>> zero
>>> and unknown values by a not existing entry inside the list of places.
>> Why not changing tCounter completely to nonNegativeInteger?
>>
> This is also a solution, but I'm not sure which elements refer to tCounter
> and might be in trouble by value zero.
I also feel troubles with changing 'tCounter' to
'xs:nonNegativeInteger'. It is sometimes used for 'sequence' attributes,
which start with '1'.
Lot's of RS 'number*' attributes are bound to 'tCounter'. Should they
allow value 'zero'?
I would inheret a new type 'tCounterZero' for positive integer values
starting with zero (means non-negative integer). This way you can choose
that type that covers the meaning best.
I put this trouble in Trac Ticket #65.
http://trac2.assembla.com/railML/ticket/65
I will summarize it, when the solution is clear.
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
