| train annotations [message #927] |
Fri, 01 March 2013 10:20  |
Andreas Tanner
Messages: 52
Registered: March 2012
|
Member |
|
|
Dear group,
for our passenger information system, we would like to import
annotations for trains and train sections. By this, we mean texts that
appear on various printout products or as part of a timetable
information. Some of them can be deduced from attributes located below
trainPart (passengerUsage, etc.) (like "wheelchair access", or "snack
service available"), but others cannot (like tariff information or
contact telephone of the train driver for assistance to wheelchair users).
The proposal below is for this type of information.
The annotations come as localizable strings and can optionally be typed
by printout product. The different printout types are defined within the
railML instance document.
The annotations can be referenced from trainPart (for global ones), or
from an ocptt (for those valid on a section). Optionally validity can be
restricted with respect to the base validity of the trainPart.
I would appreciate any feedback.
Best regards
--Andreas.
<annotationType id="01" abbreviation="booklet"/>
<annotationType id="02" abbreviation="onStreetSchedule"/>
<annotationType id="03" abbreviation="dutyPrintout"/>
<annotation id="03" abbreviation="XNah">
<annotationText lang="de_DE">Fahrausweise des Nahverkehrs haben
keine Gültigkeit.</annotationText>
<annotationText lang="en_GB">Tickets for local transport are not
valid.</annotationText>
<annotationTypeRefs>01 02</annotationTypeRefs> <!-- optional IDREFS
type --> </annotation>
<annotation id="04" abbreviation="XEinstHilfeTel">
<annotationText lang="de_DE">Einstiegshilfe durch Zugführer im 1.
Fahrzeug. Tel.: 07642/912428</annotationText>
<annotationText lang="en_GB">Assistence for the handicapped by the
driver in the front car. Call 07642/912428</annotationText> </annotation>
<trainPart>
<tpAnnotationTT annotationRef="03" operatingPeriodRef=".."/> <!-- child
of trainPart --> <!-- operatingPeriodRef optional, only reduction of
trainPart validity allowed -->
....
<ocpTTs>
<ocpTT><stopDescription><sdAnnotationTT annotationRef="04" /> <!-- child
of ocpTT/stopDescription --> <!-- no operatingPeriodRef here since it is
available in stopDescription -->
....
|
|
|
|
| Re: train annotations [message #928 is a reply to message #927] |
Sun, 10 March 2013 16:33  |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hello Andreas,
as discussed in the railML meeting in Berlin, I'd like to implement the
annotations in a first step without the annotationTypes.
The ticket for this is: http://trac.assembla.com/railML/ticket/224
This construct is more elaborated than and related with the recently
introduced messageText of a connection. I therefore merge the messageText
into the new annotationRef.
Kind regards,
Joachim
-------------------------------------
Joachim Rubröder
Schema Coordinator: railML.timetable
Andreas Tanner wrote:
>
> Dear group,
> for our passenger information system, we would like to import
> annotations for trains and train sections. By this, we mean texts that
> appear on various printout products or as part of a timetable
> information. Some of them can be deduced from attributes located below
> trainPart (passengerUsage, etc.) (like "wheelchair access", or "snack
> service available"), but others cannot (like tariff information or
> contact telephone of the train driver for assistance to wheelchair users).
> The proposal below is for this type of information.
>
> The annotations come as localizable strings and can optionally be typed
> by printout product. The different printout types are defined within the
> railML instance document.
> The annotations can be referenced from trainPart (for global ones), or
> from an ocptt (for those valid on a section). Optionally validity can be
> restricted with respect to the base validity of the trainPart.
>
> I would appreciate any feedback.
>
> Best regards
> --Andreas.
>
> <annotationType id="01" abbreviation="booklet"/>
> <annotationType id="02" abbreviation="onStreetSchedule"/>
> <annotationType id="03" abbreviation="dutyPrintout"/>
>
> <annotation id="03" abbreviation="XNah">
> <annotationText lang="de_DE">Fahrausweise des Nahverkehrs haben
> keine G�ltigkeit.</annotationText>
> <annotationText lang="en_GB">Tickets for local transport are not
> valid.</annotationText>
> <annotationTypeRefs>01 02</annotationTypeRefs> <!-- optional IDREFS
> type --> </annotation>
>
> <annotation id="04" abbreviation="XEinstHilfeTel">
> <annotationText lang="de_DE">Einstiegshilfe durch Zugf�hrer im 1.
> Fahrzeug. Tel.: 07642/912428</annotationText>
> <annotationText lang="en_GB">Assistence for the handicapped by the
> driver in the front car. Call 07642/912428</annotationText> </annotation>
>
> <trainPart>
> <tpAnnotationTT annotationRef="03" operatingPeriodRef=".."/> <!-- child
> of trainPart --> <!-- operatingPeriodRef optional, only reduction of
> trainPart validity allowed -->
> ...
> <ocpTTs>
> <ocpTT><stopDescription><sdAnnotationTT annotationRef="04" /> <!-- child
> of ocpTT/stopDescription --> <!-- no operatingPeriodRef here since it is
> available in stopDescription -->
> ...
>
>
--
----== posted via PHP Headliner ==----
|
|
|
|
|
|
|
|
Members
Search
Help
Login
Home
