Search results
Jump to navigation
Jump to search
- UC:Use cases (section railML® Use Cases)page you learn what is a use case and find a list of railML® use cases. While the emphasis of the railML®-wiki lies in documenting single elements in a bottom-up7 KB (287 words) - 16:17, 13 May 2024
- Journalistenschule in Berlin. Ich lebe in Dresden. Meine Mitarbeit in der RailML-Initiative zielt auf die Agenden der technischen Redaktion (Verständlichkeit454 bytes (61 words) - 13:11, 13 March 2024
- The element documentation has been changed. The parents have changed. The attributes have been changed.949 bytes (15 words) - 16:52, 19 April 2024
- that includes simple crossing as its part. Refer to the guide (link to the railML® website) for the extended tutorial. 1 <infrastructure id="is_01"> 2 <topology>18 KB (1,743 words) - 10:48, 15 May 2024
- The element documentation has been changed. The attributes have been changed.780 bytes (11 words) - 16:56, 19 April 2024
- <netElement> and <netRelation> instances are drawn. Transferring this topology into railML we need first the four instances of <netElement>. <netElements> <netElement15 KB (1,510 words) - 19:13, 14 February 2022
- IS:line (section Documentation)section. The attribute <infrastructureManager>@code points to a value in the railML codelist InfrastructureManagers.xml where many national and regional infrastructure9 KB (873 words) - 11:03, 13 May 2024
- IS:mileageChange (section Documentation)element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions2 KB (228 words) - 13:18, 17 April 2024
- CO:positioning (section Documentation)of RailTopoModel®, railML® 3.1 allows to define <netElement> elements with a certain length. This extension is based on the assumption that railML topology11 KB (1,110 words) - 09:59, 29 April 2024
- See intrinsic coordinate in RailTopoModel®'s wiki. The element documentation has been changed. The attributes have been changed.620 bytes (19 words) - 16:25, 19 April 2024
- <includeonly> {|class="wikitable" |colspan="2"|Autoexport aus dem XML-Schema für Element ''{{{element}}}'' |- |Kommentar |{{{kommentar}}} |- |Subschema446 bytes (38 words) - 19:18, 4 January 2023
- <includeonly>Element '''{{{element}}}''' aus Subschema {{{subschema}}} ==Beschreibung== {{{kommentar}}} ==Einbettung== {| |Parents: |{{{parents}}} |- |Children:587 bytes (47 words) - 19:18, 4 January 2023
- # Aufruf mit: # for file in *.xsd; do xsd_unchoice "$file"; done sed -i 's/<xs\:choice[^>]*>/<xs\:sequence>/g' $1 sed -i 's/<\/xs\:choice>/<\/xs\:sequence>/g'232 bytes (29 words) - 19:18, 4 January 2023
- 's/\trail\:/\t/g' $1 sed -i 's/^rail\://g' $1 sed -i 's/;rail\:/;/g' $1 sed -i 's/\trail3\:/\t/g' $1 sed -i 's/^rail3\://g' $1 sed -i 's/;rail3\:/;/g' $1 sed -i 's/\t;/\t/g'402 bytes (63 words) - 19:18, 4 January 2023
- does not appear in railML® 3.2 within the timetable subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions462 bytes (67 words) - 19:18, 4 January 2023
- <?xml version = "1.0" encoding = "UTF-8"?> <xsl:stylesheet version = "2.0" xmlns:xsl = "http://www.w3.org/1999/XSL/Transform"> <xsl:template match="/">3 KB (237 words) - 19:18, 4 January 2023
- Control Table not yet implemented! Typically, the signaller calls the route after which the interlocking sets the elements in the state as required per1 KB (215 words) - 19:18, 4 January 2023
- by one of the railML® working groups (link to the railML® website) or suggested by anyone through a post in the forum (link to the railML® website). If4 KB (579 words) - 16:49, 13 March 2023
- <mediawiki xmlns="http://www.mediawiki.org/xml/export-0.10/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki4 KB (433 words) - 19:18, 4 January 2023
- State Space The railway network owns assets that can be associated with a state. This is expressed as a set of tuples, for instance, (signali / aspectk)5 KB (562 words) - 19:18, 4 January 2023