| train uniqueness constraint II [message #942] |
Wed, 26 June 2013 10:10  |
Andreas Tanner
Messages: 52
Registered: March 2012
|
Member |
|
|
Dear group,
once more, we have a problem with the uniqueness constraint for <train>
elements
"The compound of the attributes trainNumber, additionalTrainNumber and
scope has to be unique for all <train> elements. If some of these
attributes is absent the others have to be unique. The code attribute is
used for some unique string identifying the train regardless of the
unique attribute triple."
We would like to transmit the same train twice: once in processStatus
_planned_, once in state _changed_. I think this should be allowed, so I
would ask the specification text to be changed to
"The compound of the attributes trainNumber, additionalTrainNumber,
scope and processStatus ....
Best,
--Andreas.
|
|
|
|
Members
Search
Help
Login
Home
