Dev:changes/2.4: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
Line 130: | Line 130: | ||
|} | |} | ||
==Infrastructure Subschema== | ==Infrastructure Subschema== | ||
=== OCP example added to wiki page | === OCP example added to wiki page {{IS:Tag|ocp}} === | ||
{{change | {{change | ||
|fact=OCP example Pulsnitz (from example file East Saxony) has been added to railML wiki page [[IS:ocp]] | |fact=OCP example Pulsnitz (from example file East Saxony) has been added to railML wiki page [[IS:ocp]] | ||
Line 141: | Line 141: | ||
|nattr= | |nattr= | ||
|uattr= | |uattr= | ||
|nelem= | |||
|uelem= | |||
}} | |||
=== {{IS:Tag|lineDescr}} and {{IS:Tag|trackDescr}} DEPRECATED === | |||
{{change | |||
|fact={{IS:Tag|lineDescr}} and {{IS:Tag|trackDescr}} are marked DEPRECATED with version 2.4 | |||
|reason=The elements are not being used | |||
|recomendation=For additional description of line or track, please use the attributes {{IS:Tag|track}}@description and {{IS:Tag|line}}@description | |||
|trac={{site|https://trac.railml.org/ticket/112}} | |||
|svn= | |||
|example= | |||
|xsd= | |||
|nattr= | |||
|uattr=<br> | |||
*{{IS:Tag|track}}@description | |||
*{{IS:Tag|line}}@description | |||
|nelem= | |nelem= | ||
|uelem= | |uelem= |
Revision as of 13:49, 30 May 2018
|
| ||||||||
| ||||||||
railML® 3 Wiki – RailTopoModel® Wiki |
railML schema changes between railML® 2.3 and railML® 2.4
This site is intended to collect the schema changes between railML® 2.3 and railML® 2.4 by topics, that influence the XML output. As it starts as a stub please refer to
- railML forum,
- railML's ticket system and
- the diff output (upcoming), too.
For changes with other version upgrades see Dev:changes.
Timetable Subschema
Element <stopDescription> has been expanded by the children <stopActivities>
Fact: | The new element <stopActivities> can be used to group <stopActivity>-elements which describe the purposes of a stop more detailed. The detailed purpose of a stop is described in the attribute type of a <stopActivity>. For the possible values for attribute type, a list of values has been drawn up to illustrate the most common holding purposes of various companies. |
Recommendation: | Use the new <stopActivity>-elements to describe the detailed purposes of a stop. Use if possible the standard values for the attribute type of <stopActivity>-elements. |
ocpTT element sample: | <ocpTT offset="383.220001" alignment="center" ocpType="begin" ocpRef="ocp-35154097"> <times scope="published" departure="00:22:00"/> <sectionTT> <trackRef ref="gleiskante1027"/> <runTimes minimalTime="PT84S"/> </sectionTT> <stopDescription onOff="both" commercial="true"> <stopTimes minimalTime="PT180S"/> <stopActivities> <stopActivity type="reverse"/> <stopActivity type="crewChange"/> </stopActivities> </stopDescription> </ocpTT> |
Updated XSD file(s): | timetableTypes.xsd |
New attributes: |
|
New elements: |
|
Element <trainPartSequence> has been expanded by the children <topologyReference>
Fact: | With the new <topologyReference> element, the underlying topology used to determine the route and calculate journey times can be referenced. A <topologyReference> can be set for a <trainPartSequence>. By specifying the attributes register and entry, the version(s) and/or variant(s) to be used are referenced within the external topology. This presupposes that the reading system also knows the topology register and can interpret the version(s)/variant(s). If the validity periods are not uniquely defined by the specifications register and entry, they must be specified using the attributes startDate and EndDate. If several references are specified, they must have disjoint validity periods and, in combination, cover at least the operating days of the train. |
train element sample: | <train type="operational" id="train-1455532037" processStatus="actual"> <trainPartSequence sequence="1"> <trainPartRef ref="train-part-1" /> <topologyReference register="UNO" entry="183000-01012017" startDate="2017-02-01" endDate="2017-08-31" /> <topologyReference register="UNO" entry="120000-08012017" startDate="2017-09-01" endDate="2017-12-31" /> </trainPartSequence> </train> |
Updated XSD file(s): | timetableTypes.xsd |
New attributes: |
|
New elements: |
|
Element <train> has been expanded by the children <replacements>
Fact: | The new <replacements> element is used to group <replacementOf> elements within <train> elements. Using the element <replacementOf> a relationship is defined between the train described in the XML tree and a train that has been cancelled or partially cancelled. The meaning of the relationship is that the train described in the XML tree replaces the cancelled train or the cancelled parts of a train (specified by <uniqueTrainKey> or <tafTapTsiTrainID>) on the specified operating days (specified by <operatingPeriodRef>) |
train element sample: | <train id="train-zug-BLSP-90111-001" trainNumber="90111" additionalTrainNumber="1" cancellation="false" processStatus="actual" description="Bern-Muensingen-Thun"> <trainPartSequence sequence="1"> <trainPartRef ref="trainPart1001"/> </trainPartSequence> <replacements> <replacementOf> <operatingPeriodRef ref="operating-period-KW47-MoFr-18" /> <uniqueTrainKey trainNumber="111" scope="primary" additionalTrainNumber="1" /> </replacementOf> </replacements> </train> |
Updated XSD file(s): |
|
New attributes: |
|
New elements: |
|
Infrastructure Subschema
OCP example added to wiki page <ocp>
Fact: | OCP example Pulsnitz (from example file East Saxony) has been added to railML wiki page IS:ocp |
Related Development Tickets: | https://trac.railml.org/ticket/112 (external link) |
<lineDescr> and <trackDescr> DEPRECATED
Fact: | <lineDescr> and <trackDescr> are marked DEPRECATED with version 2.4 |
Reason: | The elements are not being used |
Recommendation: | For additional description of line or track, please use the attributes <track>@description and <line>@description |
Related Development Tickets: | https://trac.railml.org/ticket/112 (link to the railML® website) |
Updated attribute(s): |