Home » railML newsgroups » railml.timetable » Haltezwecke / Stop descriptions
Re: Haltezwecke / Stop descriptions [message #1546 is a reply to message #1536] Fri, 07 April 2017 14:16 Go to previous messageGo to previous message
Philip Wobst is currently offline  Philip Wobst
Messages: 47
Registered: November 2013
Location: Hanover, Germany
Member
Hello Mico,

I have had a look at the data you have provided and have provided an updated file in the cloud (more details and some filters). I would like to suggest to switch to 'activities' instead of 'descriptions' because the activities at a stop are described and and not the stop itself.

I see the following topics that need further review:
1. the current attributes do not allow a 1:1 mapping of the SBB stop activities
2. there are some ambiguities with regard to the attributes
- an activity might be 'ordered' by the RU for a commercial stop
- onOff is not clearly defined to be relevant to customers/goods only
- no possibility to identify activities for the IM
3. in general I suspect that more than one 'activity' can be supplied for a stop - how shall 'conflicting' attributes be treated in such a case?

Best regards,

Philip
 
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
Read Message
Read Message
Read Message
Read Message
Previous Topic: Timetable data elements for railVIVID
Next Topic: addendum to <stopDescription> in railML2.4
Goto Forum:
  


Current Time: Thu Mar 28 16:20:07 CET 2024