| Re: Infrastructure registers [message #1580 is a reply to message #1547] |
Thu, 18 May 2017 15:46   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Christian,
sorry but I don't understand the necessity. May be you can further explain?
From my understanding, the kind of register is (adequately) specified
by the parent element of <designator>. If it is a <designator> of an
<ocp>, the station registers are needed. If it is a <designator> of a
different parent element, a different register is needed.
As is can also happen to have different registers as sub-elements of
<infrastructure> in future (such as registers of line numbers), I would
not recommend naming the station lists @infrastructureRegister. I would
name them @ocpRegister. But this would, as I said, be redundant to the
parent's element name.
I agree that the file "Registers.xml" should not be named such in
future. It should be named "Registers_of_OCPs.xml" or such. But this
does not need to have consequences for the XSD, does it?
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
