Home » railML newsgroups » railml.timetable » [railML2] Proposed semantic constraint for <specialService>
Re: [railML2] Proposed semantic constraint for <specialService> [message #3467 is a reply to message #3464] Thu, 13 February 2025 16:46 Go to previous messageGo to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 103
Registered: March 2008
Senior Member
Dear all,

I think Christian's proposal is elegant. The constraint that these dates must be within the date range of the operatingPeriod, could maybe also be included in the same constraint.

The constraint that startDate is less than or equal to endDate applies to a lot of elements, and we could maybe strip down the original TT:001 to just that (but maybe as a CO:* constraint), and apply that constraint to all relevant elements, simplifying the remaining element specific constraints.

Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML2] Wording of semantic constraints TT:015 and TT:016
Next Topic: [railML 2] New semantic constraint for <operatingPeriod>
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Nov 15 19:01:19 CET 2025