Home » railML newsgroups » railML.infrastructure » Suggestion for improved references with RailML
Re: Suggestion for improved references with RailML [message #215 is a reply to message #214] Mon, 24 November 2008 14:53 Go to previous message
Joachim Rubröder railML is currently offline  Joachim Rubröder railML
Messages: 0
Registered: November 2019
Hi,
references like that would be very useful for the timetable schema as
well.
An example for the timetable period (in V1.1) would look like that:

<xsd:key name="timetablePeriodId">
<xsd:selector xpath="
/timetable/timetablePeriods/timetablePeriod"/>
<xsd:field xpath="@timetablePeriodID"/>
</xsd:key>
<xsd:keyref name="timetablePeriodRefId" refer="
timetablePeriodId">
<xsd:selector xpath="./timetable/train"/>
<xsd:field xpath="@timetablePeriodID"/>
</xsd:keyref>

A drawback is, that the key/keyref has to be located in an element and we
only have one. So we will have to define all our key references in the
root element "railml". But why not?

I think this would be a good feature for our release 2.0 together with the
renamings to "id" and "xyRefId".

Best regards,
Joachim Rubröder

--
Joachim Rubröder
RailML Timetable Coordinator
EMail: coord(at)timetablerailmlorg
 
Read Message
Read Message
Previous Topic: Accuracy for positions required?
Next Topic: Trac Ticket #6 "geographical coordinates for track positions"
Goto Forum:
  


Current Time: Sun May 19 18:22:54 CEST 2024