Home » railML newsgroups » railML.infrastructure » small issues on "register" and "tLineInfrastructureManagerCode"
Re: small issues on "register" and "tLineInfrastructureManagerCode" [message #468 is a reply to message #463] Mon, 26 November 2012 12:10 Go to previous messageGo to previous message
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
Christian Rahmig <coord(at)infrastructurerailmlorg> writes:

>> I reopened the Trac ticket for this issue to clarify with railML 2.2:
>>
>> http://trac.assembla.com/railML/ticket/112#comment:10
>
> I agree with the idea to change the type of the register's name from
> string to an enumeration list.

Me not ... sorry to change the opinion to this aspect.

As agreed at the meeting in Zurich we will implement a free string
attribute in the XML Schema, but provide an additional XML file with
pre-defined values for this attribute.

Kind regards...
Susanne

--
Susanne Wunsch
Schema Coordinator: railML.common
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: <crossSection>.ocpTrackID
Next Topic: request for an attribute for the Infrastructure Manager of a line
Goto Forum:
  


Current Time: Fri May 17 14:19:52 CEST 2024