Search results

IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source page   If you want to reactivate your inactive use case

recommended to use the XML comments for non-content related documentation, e.g. contact information: <!-- ... --> (line 4) It is recommended to use the XML Schema

name="TGV-ICE3">... Please use some more generic coding style in order to not invite the importing software to parse the id values! Please use a generic coding style

Creating instructions for new railML® elements Guideline on Use cases — what is a use case, where to find them and how to contribute to them. Certification

New users Guide Dev:Use case example Shows and explains the structure of a good use case All Experienced users Guide Dev:Use cases How to contribute to

all information that is collected about the ÖBB in the code list, in this case name, country code and company code: <infrastructureManager code="ÖBB"> <name>ÖBB

versions started in 2001. Version 1.0, the first version allotted for productive use, was published in 2005. In 2019, the development was forked into the established

Rostering   Related subschemas: IS RS CO Reported by: IVU For general information on use cases see UC:Use cases

ema/railML.xsd"> ... </railml> Use the last released version number plus the current SVN number: version="2.1r416" Use the last released namespace as default

data Typically, the import is done manually using a file based interface. Common Infrastructure: the import uses elements from mesoscopic and macroscopic

other standards (external link). This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other

railML® website). The code lists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity

practical use and maintenance by the registry is guaranteed. The further procedure is explained on the dev:Codelists#Missing_entries page. Use of a project-specific

railML® website). The code lists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity

status=approved. Implement a seperate semantic constraint for every rule. Use the template with all mandatory arguments according to Template:SemanticConstraint

"Recommended best practice is to use a controlled vocabulary such as RFC 4646 (external link)." railML® semantics This may be used for identifying the default

tools in productive use shall use *.railml for files / exports. *.xml is always allowed since railML® files are xml files. It shall be used for non-certified

as <infrastructure>, <rollingstock>, <timetable>. This attribute is to be used for the version number of the railML® schema the XML file is based on. Major

Infrastructure Rollingstock Timetable (Common) (Codelists) XML tree UML diagrams Use cases Versions & Changes