Search results

later referencing that element internally. For a detailed explanation see Dev:identities. XML-Datei-weit eindeutige, maschineninterpretierbare Identität

semantic constraint on the respective list below (Dev:Semantic_Constraints/table2 for railML® 2 and Dev:Semantic_Constraints/table3 for railML® 3). assign

users to find relevant information. This structure sets a frame for the certification. In the railML® 2 wiki, element pages are made by hand with Template:ElementDocu

us. To learn where to find, how to use and how to contribute use cases see Dev:Use cases. While use cases follow a top-down approach, starting out from the

registered trademark, railML® should be a kind of quality sign. As a certification is mandatory since the release of railML 2.2, all tools in productive

schema. If your extension does not fit into this frame this may bar the certification of your tool. Considering #when to extend the schema follows very similar

history and the changes between the respective versions see Dev:changes. →Main Article: Dev:Guides complete railML® 2 trees with links to the corresponding

and Developer Pages   This page provides an overview over pages from the Dev-namespace that offer User Guides, information for developers and connected