Search results

Jump to navigation Jump to search

  • UC:Use cases (section What is a use case?)
    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
    10 bytes (287 words) - 16:31, 3 February 2020
  • UC:Use case example (category Use case (unknown subschema)) (section Use case / Anwendungsfall)
    elements necessary for the use case. This description may also reference other existing use cases. Are there any partial use cases distinguished, which build
    10 bytes (263 words) - 21:42, 23 January 2020
  • Dev:Use cases (section What is a use case?)
    necessary for the use case. This description may also reference other existing use cases. Sub-use cases Are there any partial use cases distinguished, which
    10 bytes (1,035 words) - 21:45, 23 January 2020
  • UC:TT:SlotOrdering (category Use case (TT)) (section Use case / Anwendungsfall)
    This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity. A related use case will
    10 bytes (273 words) - 16:12, 3 February 2020
  • TT:connection
    train is provided in this use case. To determine whether an attribute must be specified or can be omitted, the respective use case must be taken into account
    25 KB (3,398 words) - 20:30, 22 January 2024
  • Dev:identities
    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
    7 KB (807 words) - 19:07, 22 January 2024
  • UC:IL:EulynxDataPreparationInterlocking (category Use case (IL))
    reflect the as-built situation. Please refer to the linked use cases that cover the Eulynx use case. For detailed information please refer to the website https://eulynx
    10 bytes (450 words) - 16:12, 3 February 2020
  • TT:trainPart
    trainPart is in the best case redundant, if it is used as a shortcut to the commercial train number. The recommended practice is to use trainNumber only on
    12 KB (1,930 words) - 15:44, 13 May 2024
  • Dev:Use case example/old (category Use case (unknown subschema)) (section Use case / Anwendungsfall)
    good use case. For an actual example see UC:IS:Schematic Track Plan. To get more information on use cases and how to describe them, see Dev:Use cases. Please
    10 bytes (220 words) - 16:47, 4 December 2023
  • UC:IL:HardwareAndCablePlan (category Use case (IL)) (section Use case / Anwendungsfall)
    cable plan Subschema: Interlocking For general information on use cases see UC:Use cases
    10 bytes (119 words) - 16:12, 3 February 2020
  • UC:IS:RailwayInfrastructureVisualisation (category Use case (IS)) (section Use case / Anwendungsfall)
    Visualisation (RAIV) Subschema: Infrastructure For general information on use cases see UC:Use cases
    10 bytes (180 words) - 16:12, 3 February 2020
  • IS:ocp
    infrastructure elements are aggregated to an <ocp> depends on the context (use case) and the accuracy requirement of the timetable. Timetables that aim more
    18 KB (2,618 words) - 16:53, 19 March 2024
  • Infrastructure
    tracks Remarks and open issues on mileage changes (planned) IS:UseCases — a collection us use cases for the IS-subschema Examples (link to the railML® website)
    3 KB (350 words) - 19:56, 22 January 2024
  • UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets (category Use case (IS)) (section Use case / Anwendungsfall)
    von Schienenanlagen railML data will be used for engineering signalling and interlocking systems. Engineers are used to working with paper plans that schematically
    10 bytes (383 words) - 16:12, 3 February 2020
  • UC:IS:Timetabling (category Use case (IS)) (section Use case / Anwendungsfall)
    subschemas: IL TT RS  Reported by: ProRail For general information on use cases see UC:Use cases
    10 bytes (343 words) - 16:12, 3 February 2020
  • UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (category Use case (IS)) (section Use case / Anwendungsfall)
    Export of planning tool: planning data, handing-over to the supplier (by using a database). interlocking (see also: Interlocking Engineering) This section
    10 bytes (367 words) - 16:12, 3 February 2020
  • UC:TT:TAF/TAP TSI (category Use case (TT)) (section Use case / Anwendungsfall)
    this use case is the process description and the minimum data content for the timetable data exchange. The used data format is EDIFACT. The use case shall
    10 bytes (592 words) - 16:12, 3 February 2020
  • UC:TT:PassengerInformationAtStations (category Use case (TT)) (section Use case / Anwendungsfall)
    subschemas: IS RS  Reported by: PSI For general information on use cases see UC:Use cases
    10 bytes (691 words) - 16:12, 3 February 2020
  • UC:IL:InterlockEngineeringForSignallingWithinJBV (category Use case (IL)) (section Use case / Anwendungsfall)
    together especially when gathering information regarding topology. Future use case should handle integration towards 3D modelling for evaluation of e.g. sight
    10 bytes (558 words) - 16:12, 3 February 2020
  • UC:IS:Railway Simulation Laboratory (category Use case (IS)) (section Use case / Anwendungsfall)
    technologies of global optimization (ATO, ATP, timetabling…) for further possible use in practice. Our Railway laboratory has been equipped with model railway lines
    10 bytes (427 words) - 16:12, 3 February 2020
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://wiki2.railml.org/wiki/Special:Search"