Search results
Jump to navigation
Jump to search
- Dev:Changes (redirect from CO:Changes)stub please refer to the railML forum (link to the railML® website) and the ticket systems for railML® 2 and for railML® 3, too. →Main Article: Dev:Versions10 bytes (403 words) - 16:31, 18 May 2020
- Common (CO) This pseudo-subschema captures elements at the top of the railML® tree, above the subschemas. The actual planned tasks and enhancements can313 bytes (44 words) - 17:12, 19 January 2024
- Dev:changes/2.4 (redirect from CO:changes/2.4)appeared in this discussion (link to the railML® website) Related Development Tickets: #250 Related Commits: [618] (Note on legacy SVN commits) New attribute(s):23 KB (104 words) - 11:10, 3 May 2022
- Dev:changes/2.3 (redirect from CO:changes/2.3)In this article there is information missing with respect to the tickets #258 and #241. Please help improving the railML® wiki by filling the gaps. Possibly20 KB (238 words) - 18:57, 22 January 2024
- Dev:changes/2.2 (redirect from CO:changes/2.2)to address a certain Template:CO:infrastructureManagerfrom the infrastructure manager codelist. Related Development Tickets: #152 Related Commits: [459]36 KB (103 words) - 13:54, 21 February 2022
- Dev:changes/2.1 (redirect from CO:changes/2.1)straightforward) railML® forum (link to the railML® website) The railML® 2 ticket system For changes with other version upgrades see Dev:changes.713 bytes (102 words) - 18:46, 22 January 2024
- Dev:versions (redirect from CO:versions)development. Decision User requirements from the forum are kept in the railML® ticket system: For railML® 2 they can be found here; for railML® 3 they can be10 bytes (1,043 words) - 11:29, 15 February 2023
- Main Page (section Common (CO))subschemas or do not fit into this structure are subsumed in the class Common (CO). Please contact the coordinator of the respective schema (see https://www9 KB (916 words) - 12:29, 22 February 2024