Home » railML newsgroups » railML.infrastructure » Fwd: Mapping of code and abbreviation for ocps
Re: Fwd: Mapping of code and abbreviation for ocps [message #380 is a reply to message #376] Sat, 06 October 2012 08:06 Go to previous message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear Dirk,

>> 'date' defines the publishing date of the register.
>
> I guess 'date' is optional. Before it is too late: Shouldn't we name it
> 'startDate' and possibly introduce an (optional) 'endDate', too?

thank you for your important remark. As described in detail in trac
ticket [1] I renamed "date" into "beginDate" and added "endDate". Both
dates are optional while the other parameters, "register" and "entry"
are set to be required.

Can you please copy your examples into the Wiki? Thank you again.

[1] https://trac.assembla.com/railML/ticket/112

Regards

--
Christian Rahmig
railML.infrastructure coordinator
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: ocp's/stations and their properties
Next Topic: Identical signal representation [de:Gruppenausfahrsignal]
Goto Forum:
  


Current Time: Tue Jul 23 00:51:38 CEST 2024